Integration exception queue / Interface design
Find the exception.
Find the exception.
Trace the source row.
We built the import desk around an exception queue, paired source evidence and a processing audit.
The supplied 24-row sample CSV gives the interface actual local records to inspect.
Explore the work ↓- PROJECT TYPE
- Interface design & front-end development
- DOMAIN
- Integration exception queue
- DESIGN FOCUS
- Making import exceptions traceable to source records
01 / THE DESIGN DECISION
The prepared run must reconcile.
The example starts at 9,360, identifies 900 in duplicates and shows how a mapped row of 240 changes the prepared run from 8,220 to 8,460. We kept the runs and original evidence distinct. Nothing is posted to a bank account or live ledger.
02 / THE BUILD
The pages we designed.
The build brings import exception desk, duplicate source evidence and processing audit into one workspace.
Duplicate source evidence
View the screen ↓Processing audit
View the screen ↓03 / PROJECT NOTES
Project scope.
We designed and built 3 pages for this self-initiated project, including the layouts, responsive behaviour and front-end interactions. The interface uses sample business records.
The screenshots show authored interface states. Live accounts, operational integrations and production transactions are outside this portfolio build.
The gallery shows our rendered pages with identifying details masked.
06 / ON SCREENA closer look.
A closer look.
Page by page.
Start with the overview, then explore the details. These are screenshots of the original interface, with names, contact details and identifying information blurred for privacy.
3 views Select any view to explore
Have a similar project?
Let’s discuss the work.
Tell us what your customers or team need to do. We can help define the pages, records and interactions around that task.