A supplier invoice becomes a CRM record.
A click-through walkthrough of document intake: a supplier invoice or order lands in the inbox, its fields are extracted and mapped, anything that fails a rule goes to a human reviewer, and a record is created at the end. Everything here is precomputed from a fictional batch of 25 documents — no live AI, no customer data, no customer project.
Document in
A supplier invoice or order confirmation arrives in the intake inbox.
Extraction
Fields are read from the document and mapped to the CRM record schema.
Review
Anything that fails a rule is checked by a person before it becomes a record.
CRM record
Approved documents appear in the record list, ready for the next step of your process.
How to read this demo
This page replays one intake run for a fictional distributor, Meridian Distribution Co., on a batch of 25 fictional supplier documents. Pick one of the sample documents below to step through its intake, then look at the review queue, the batch outcome and the record list it produced.
Nothing on this page is live AI and nothing here is a customer project. Every result was computed ahead of time from the fictional batch, so the page is a fixed replay — you can step through it at your own pace. The record list is a simulated CRM view; no live CRM product is shown as integrated.
What the workflow does
- Reads the document — vendor, document number, issue date, PO reference, line items and total.
- Checks it against rules — duplicate document numbers on file, PO references that match no open order, and line-item totals that do not match the stated total.
- Routes failures to a reviewer — the exception queue shows why each document was flagged and what the reviewer decided.
- Creates records — every approved document becomes a row in the record list.
Pick a sample document
Eight of the 25 documents in the batch are set up for a closer look. Each is fictional — sample documents with invented numbers, vendors and amounts. The other 17 ran the same intake path; their results are in the review queue and the record list below.
Select a document above to step through its intake — the document on the left, the extracted fields on the right, and the outcome underneath.
The review queue
In this batch, three documents were flagged by intake rules instead of flowing straight through. Each entry shows the rule that fired and the resolution that was logged by the reviewer.
Batch outcome
What this run of the workflow produced on its batch of fictional documents.
Figures are this demo's outputs on fictional data.
The record list that came out
Every approved document became a record. This is a simulated CRM record list for the demo — copy and records are fictional, and no live CRM product is depicted as integrated.
| Account | Document | Issue date | PO reference | Amount | Status | Reviewed by |
|---|
Record fields shown: account name, source document number, issue date, linked PO reference, amount, status, and reviewer for documents that passed through the queue. Amounts are plain figures on fictional documents.
This is the kind of workflow an Automation & Integration Sprint delivers.
Describe the documents your team handles and we will scope it against your systems.