Find the exception.
Trace the source row.

Import exception desk — identifying labels masked
Import exception desk
THE PROJECT

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.

PROJECT TYPE
Interface design & front-end development
DOMAIN
Integration exception queue
DESIGN FOCUS
Making import exceptions traceable to source records
THE DESIGN DECISION

The prepared run must reconcile.

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

The pages we designed.

The build brings import exception desk, duplicate source evidence and processing audit into one workspace.

Screen

Import exception desk

We built the import desk around an exception queue, paired source evidence and a processing audit.

View the screen ↓
Screen

Duplicate source evidence

Four matching identifiers. Supplier, invoice, date and amount match. Leo Grant checked the source and confirmed a repeated import entry.

View the screen ↓
Screen

Processing audit

Organises processing events, source inspected and duplicates reviewed in a connected view.

View the screen ↓

Expanded project screenshot
FROM THIS PROJECT TO YOURS

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.

Discuss your project Explore custom software development

Search Anteomnio

A few places to start

↑ ↓ to explore · Enter to openFull search page