Home / How It Works
How It Works: One Item's Journey Through the Platform
This page follows a single piece of work through Outcome Cloud™ — from the moment it lands to the moment its outcome is on the record and shared with the systems around it. The example is a supplier invoice, but the same five stages carry applications, claims, contracts, and requests.
It lands in the repository
The invoice arrives by email at 9:04 a.m. and is captured straight into Outcome Repository™ — given an identity, stored once, and never forwarded, downloaded, or saved-as again. From this moment it has exactly one home, and everything that happens to it will happen in that home and be written to its record.
Items that arrive as data — a portal submission, a record from a connected system — land the same way: one identity, one record, one place to look.
It is read and understood
Inside the platform, MaxxOwl™ SI reads the document where it sits: classifies it as an invoice, extracts vendor, dates, line items, and totals as structured data, and validates that data against your rules — including matching it against the purchase order and goods receipt with N-Way Match™. The document and its data now travel together, because on this platform they were never separated.
Anything that fails a check does not leave the platform to be chased down. It is marked as an exception, with the reason attached, and carried into the next stage.
It is routed by workflow
Outcome Workflows™ takes the validated invoice and routes it by rule: the amount chooses the approval path, the department chooses the approver. Each step is a task with an owner and a clock, and the route is visible to anyone with a reason to look — no status meetings, no "just checking in" emails.
Because the workflow runs in the same home as the repository, the task carries the document and its data with it. Nobody opens a second system to find what they are approving.
People decide in the workspace
The approval — and the exception the matching flagged, a quantity that disagrees with the receipt — arrive together in Outcome Workspace™. The finance reviewer sees the invoice, its extracted data, and the mismatch side by side, resolves the exception, and approves. One decision, made in context, recorded with a name and a timestamp.
This is the platform's division of labour: the system reads, checks, routes, and remembers; people handle the judgement calls — and they handle them in the same place the work lives.
The outcome is recorded — and connected
The invoice is ready for payment, and the outcome — what got done with it — is written to its record: what was matched, what was flagged, who decided, and how long each stage took. Through Business Connectors™, that result flows back to the systems the operation runs on, so the record there agrees with the record here.
And the journey stays reportable. Outcome Analytics™ draws on records like this one — volumes, exception rates, cycle times, outcomes by process — because the platform kept the evidence as it went.
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 platform — arrives as structured data already and lands in Outcome Repository™ the same way, joining the same workflows at the same stages. Documents and data, one platform.
Same journey, every kind of work
Every item your operation runs on can be walked through the same five stages. The rules, matches, and approvers change from process to process; the platform doesn't. That consistency is what makes the outcomes comparable — and what makes one home different from a tangle of tools.
Give your work one home
The stages above run on MaxxLogix — Outcome Cloud™, Outcome Repository™, Outcome Workflows™, and the rest of the platform, with capacity published in SI Units and no surprise overages. See it at maxxlogix.com.
Visit MaxxLogix