Home / How It Works
How It Works: One Invoice, Three Engines
The engines are easiest to compare on the same document. Follow one supplier invoice as it is processed by IDP Outcomes™, checked by N-Way Match™, and measured by Outcome Analytics™ — and see what each engine contributes along the way.
IDP Outcomes™: the invoice is read and understood
The invoice arrives as an email attachment. IDP Outcomes™ takes it from there, and inside the engine, MaxxOwl™ SI does the reading: classification identifies it as an invoice rather than a statement or credit note, and extraction lifts out the vendor, invoice number, dates, line items, tax, and total as structured data.
What this engine contributes is comprehension. The document stops being a picture of numbers and becomes data the rest of the line can trust and act on — each extracted value carrying the confidence the next engine will weigh.
Notice what does not happen here: nobody re-keys the invoice into a spreadsheet, and nobody renames a file so the "right" folder can find it. The read happens once, at the front of the line, and every later stage works from that single read.
N-Way Match™: the invoice has to agree
Understanding an invoice is not the same as approving it. N-Way Match™ compares what the invoice says against what the records say: the purchase order that authorised the spend and the receipt that confirms the goods arrived. Quantities, prices, and totals are checked across all three.
What this engine contributes is agreement — records agree before money moves. In our example, one line item is priced above the order. That disagreement becomes an exception, routed to a person in Outcome Workspace™ with the invoice, the order, and the exact mismatch on one screen. The decision — query the vendor, accept the difference — is made there and written back to the record.
And when everything agrees, the match is silent: the invoice passes straight through with no human touch at all. People see the invoices that disagree, not the hundreds that don't — which is where their attention actually earns its keep.
Outcome Analytics™: the invoice is measured
Once the invoice is settled, Outcome Analytics™ takes its measure — not of the document, but of the outcome. How long did each stage take? Where did the exception occur, and how was it resolved? How does this invoice compare with the vendor's last fifty?
What this engine contributes is evidence. Volumes, exception rates, and cycle times are reported from the recorded outcomes themselves, so a pattern — one vendor whose prices drift from their orders, one process stage that always waits — shows up in the numbers while it is still small enough to fix.
Because the measurement comes from the same records the other engines wrote, there is nothing to reconcile: the report and the work are the same facts, seen from two distances.
The recorded outcome
Three engines, one line, one record. When the invoice finishes, Outcome Cloud™ holds the whole story: the document itself, the data read from it, the match it passed, the exception a person resolved, and the timings Analytics reports on. Nothing lives in a separate silo, because the engines were never separate systems — they are focused capabilities on one platform, each accountable for its pass, all writing to the same record.
That is the point of the family. An outcome is not a document that was stored or a task that was moved; it is what got done with it — matched, approved, and ready for payment, with the evidence attached.
Swap the invoice for an application, a claim, or a contract and the passes stay the same: one engine reads it, one checks it against what it should agree with, one measures how the process performed. The document changes; the pattern doesn't — and neither does the place the outcome is recorded.
← Back to the overview: the Intelligent Outcome Engines™ family
Run your documents down the line
IDP Outcomes™, N-Way Match™, and Outcome Analytics™ run on MaxxLogix — one pattern, one platform, outcomes on the record. See the engines at maxxlogix.com.
Visit MaxxLogix