
Import exception desk
We built the import desk around an exception queue, paired source evidence and a processing audit.
View the screen ↓
We built the import desk around an exception queue, paired source evidence and a processing audit.
The supplied 24-row CSV gives the interface actual local records to inspect.
An import exception needs to be traceable to the source row and the processing decision. A warning without that context is difficult to resolve.
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.
The build brings import exception desk, duplicate source evidence and processing audit into one workspace.

We built the import desk around an exception queue, paired source evidence and a processing audit.
View the screen ↓
Four matching identifiers. Supplier, invoice, date and amount match. Leo Grant checked the source and confirmed a repeated import entry.
View the screen ↓
Organises processing events, source inspected and duplicates reviewed in a connected view.
View the screen ↓Explore the interface, from the first impression to the finer details.
Choose a view to enlarge ↓Tell us what your customers or team need to do. We can help define the pages, records and interactions around that task.