Document automation · Interactive example
Document checks
Read the sample invoice, run the checks, then fix the one value that needs a person.
Doc check
Document automation
- 1Read the invoice
- 2Run the checks
- 3Fix and re-check
YOUR NEXT STEP
Read the invoice that just arrived
Read the sample invoice, run the checks, then fix the one value that needs a person.
SHARED INBOX · 1 NEW
The invoice as it arrived
billing@alderfinch.example
Invoice INV-2291 · payment due 17 Nov 2026
A fictional supplier and invoice. The original is never changed.
EXTRACTED FIELDS
What the document says
- Supplier
- —
- Invoice number
- —
- Invoice date
- —
- Due date
- —
- Subtotal
- —
- VAT 20%
- —
- Total
- —
YOUR RULES FOR SUPPLIER INVOICES
- Line items add up to the subtotal
Not checked yet
- Total equals subtotal plus VAT
Not checked yet
- Within 10% of the previous invoice
Not checked yet
WHAT ACCOUNTING RECEIVES
Nothing yet
The invoice is waiting in the inbox. Nothing has been read or checked.
Activity
The sample is ready. Your actions will build a shared history here.
This is a fictional example of what we can build, not a client’s interface. Changes reset when you reload or reset the demo.
What this could become for you
An invoice arrives. Only the problem needs a person.
A document pipeline that reads incoming files, checks them against your rules and sends only the exceptions to your team.
Explore ai agents & integration →A first version from $6,000.
- 01Agree one workflow
Pick the workflow that costs the most time and agree the systems, the scope and how the result is checked.
- 02Build and review
See working software every week, including what happens when a step fails.
- 03Launch and hand over
It goes live on your accounts, with the code, infrastructure and documentation handed over.
Turn incoming documents into checked records.
What documents arrive, what needs checking and where should approved records go?