Home / How It Works
How It Works: One Document, Start to Finished
This page walks a single document through the loop — from the moment it arrives to the moment the work it represents is finished and on the record. The example is a supplier invoice, but the same five stages apply to applications, claims, contracts, and case files.
Intake: arrival is a system event, not a favour
The invoice arrives attached to an email at 9:04 a.m. In a manual process it would sit in a shared inbox until someone claimed it. In the loop, arrival is intake: the document is captured the moment it lands, given an identity, and queued for processing alongside every other arrival — email attachments, uploads, scans, and system feeds all enter the same way.
Nothing is sorted by hand, and nothing waits on a person noticing it. From this point on, the document's location and status are always known.
Classification & extraction: the document is read
Next, the processing engine — MaxxOwl™ SI on the MaxxLogix platform — reads the document. Classification comes first: is this an invoice, a credit note, a statement? The engine decides from the document's layout, language, and content — not from a file name or a folder somebody chose.
Extraction follows: vendor, invoice number, dates, line items, tax, and totals are lifted out as structured data. Skewed scans and multi-page attachments are handled as part of the read, and every extracted value carries a confidence level that the next stage puts to work.
Validation: data is checked before it is trusted
Extracted data is only useful if it can be trusted, so the loop checks it before anyone acts on it. Totals are recomputed. Dates and formats are normalised. Required fields must be present. Then the document is matched against its related records — for an invoice, the purchase order and the goods receipt — using N-Way Match™, so a price or quantity that disagrees is caught here, not at payment time.
Anything that fails a check becomes an exception: it leaves the straight-through path and is routed to a person together with the document, the extracted data, and the specific reason it was flagged.
Workflow: work moves by rule, not by inbox
A validated invoice moves into workflow. Approvals follow your rules — by amount, by department, by exception type — and each approval is a task in a queue, not a thread in someone's email. Reviewers work in Outcome Workspace™, where the document and its data sit side by side and a decision is a single action, recorded with a name and a timestamp.
If a step stalls, the workflow knows. Reminders and escalations are part of the route itself, not a manager's memory.
Outcome: the finish is recorded, not assumed
When the last approval lands, the loop closes. The invoice is ready for payment, the record is filed, and the outcome — what got done with it — is written to the record: who approved it, what was matched, how long each stage took, and what, if anything, needed human judgement along the way.
That record is the point. It is what Outcome Analytics™ reports on: volumes by document type, exception rates, stage-by-stage cycle times, and the outcomes each process produces. Improvement stops being a guess, because the loop keeps its own evidence.
The other front door: forms and portals
Not everything arrives as a document. A request submitted through a form or a portal — MaxxLaunch™ on the MaxxLogix platform — arrives as structured data already, and joins the same workflow at the validation stage. From there the loop treats both doors identically: checked, routed, worked, and recorded. Documents and data, one loop.
Same loop, every document type
Every document type your operation runs on can be walked through the same five stages. The rules, matches, and approvals change from process to process; the loop doesn't. That consistency is what makes the outcomes comparable — and what makes a platform different from a pile of point tools.
← Back to the overview: intelligent document processing with workflow automation
Put your documents through the loop
The stages above run on MaxxLogix — Outcome Cloud™, MaxxOwl™ SI, Outcome Workspace™, and the rest of the platform, with capacity published in SI Units and no surprise overages. See it at maxxlogix.com.
Visit MaxxLogix