Home / How It Works
How It Works: One Exception, Start to Settled
This page follows a single document that fails its check: a supplier invoice with a quantity mismatch. The stages are the resolution path every exception takes on MaxxLogix — flagged, opened, evidenced, decided, recorded — whatever the document type.
Flagged: the match disagrees
The invoice arrives, is read, and its data is extracted: supplier, invoice number, line items, quantities, totals. Then validation runs the invoice against its related records using N-Way Match™ — the purchase order and the goods receipt. The order says 120 units. The invoice bills 120. The receipt, signed at the dock, records 100.
Two of the three documents agree; the third doesn't. The invoice fails the check, and it fails with a specific reason attached: quantity billed exceeds quantity received by 20 units. Nothing is paid, nothing is guessed — the document is flagged, and only this document is.
Opened: the exception becomes a work item
The flagged invoice leaves the straight-through path and an exception opens in Outcome Workspace™. It's routed by rule — quantity mismatches on supplier invoices go to the buying team's queue — and it arrives as a work item with an owner, a status, and an age, not as an email hoping to be noticed.
Everything else from that supplier, and every other invoice that passed its checks, keeps moving. The exception waits in the open, where its ageing is visible to the team and its manager alike.
Evidence: the disagreement, side by side
The buyer who picks up the work item doesn't start by hunting. The workspace presents the case assembled: the invoice itself, the data extracted from it, the purchase order line, and the goods receipt — side by side, with the conflicting quantities in view and the flag's reason stated at the top.
That assembly is the difference between resolution and archaeology. The question is already framed — billed 120, received 100 — and the buyer's work begins at the decision, not at the search for the paperwork behind it.
Decided: a person settles it, with a reason
The buyer checks with the supplier, who confirms the shipment went out short: 100 units delivered, the remaining 20 following on a later truck. The facts are now clear, and the buyer decides: pay the invoice for the 100 units received, hold the balance against the follow-up shipment, and record exactly that as the reason.
The decision is a single action in the workspace, made by a named person, on the evidence on the screen. The corrected value flows on to payment; the exception closes — not because someone deleted it, but because it was settled.
Recorded: the outcome keeps the whole story
The outcome is written to the Outcome Repository™: the invoice, its data, the mismatch, the evidence, the buyer's decision, and the reason behind it. What got done with this document includes how its problem was solved — retrievable by an auditor, a colleague, or the same buyer when the follow-up invoice arrives claiming the remaining 20.
And the pattern doesn't vanish into one file. Outcome Analytics™ counts this exception with all the others: mismatch rates by supplier, resolution times by queue. If the same supplier ships short again next month, that is no longer one buyer's suspicion — it is a trend, on the record, ready to act on.
Same discipline, every exception type
A missing signature page, a low-confidence read, an approval above threshold — each follows the same five stages, because the discipline doesn't depend on what failed. Flag with a reason. Open as work with an owner. Assemble the evidence before asking the question. Let a person decide and say why. Record the outcome whole. That consistency is what makes exceptions manageable at volume — and what makes a platform different from a pile of point tools.
Put your exceptions through resolution
The stages above run on MaxxLogix — Outcome Cloud™, Outcome Workspace™, N-Way Match™, and the rest of the platform, with capacity published in SI Units and no surprise overages. See it at maxxlogix.com.
Visit MaxxLogix