Watch an agent
check a document.
Pick an invoice, a contract, a payment request or a customer application. The agent reads it, applies your company’s rules, checks the other records and tells you what it found. Then you decide.
Pick a document. The agent reads it.
Every field it takes, every rule and record it checks, with the source. When it finds something, it stops and hands the decision to you.
- Read
- Check
- Findings
- Your decision
- Record
Fictional documents, companies and rules. The agent here is scripted in the page: nothing is read from you or sent anywhere. Your own documents are checked in the process review, with names and amounts hidden.
What the person does with a supplier invoice
Without the agent
- Open the invoice, the contract and the price annex side by side
- Find the warehouse receipt in email or the stock system
- Search accounting for an earlier payment of the same invoice
- Compare the bank details with the supplier card by eye
- Look up what the treasury policy says about changed accounts
- Write to the supplier and note somewhere why the payment waits
With the agent
- Read what the agent found, each point with its source
- Call the supplier back on the number on file: the agent cannot
- Approve, or return with the comment the agent drafted
- The decision record is written for you
The steps that remain are the ones that need judgement or a call to a real person. The agent never approves, pays, signs or sends.
What always stays with a person
- Every approvalThe agent proposes. Approve or return is pressed by a person, and the record says who.
- Money, signatures and anything sent outThe agent never pays, signs or sends. It drafts the comment; a person sends it.
- Calls to real peopleConfirming a new bank account by phone, asking a manager to sign: people do it, the agent reminds them.
- Exceptions to a ruleA person may approve against a flag. The flag stays in the record, next to the reason.
How we work
Agents and desks come last. First the company’s own knowledge is collected, cleaned and checked by its people.
- CollectEmail, chats, documents, spreadsheets and systems, each piece with its origin.
- CleanDuplicates merged, conflicts and out-of-date facts flagged for a person.
- Verify with peopleFacilitation sessions where your people confirm, correct and set priorities.
- Map and MegabrainOne model of how the company runs, which desks and agents then work from.
What the agent checks
- RulesYour company’s rulesApproval limits, payment terms, signing rights, what to do when bank details change. Written down once, applied to every document, each with the policy it comes from.
- RecordsOther recordsThe contract and its price annex, the warehouse receipt, earlier payments, the supplier card, the company register. The agent names every record it looked at.
- LimitsAmounts and rightsWho may approve this amount, who may sign this contract, how much credit a new customer starts with. Above a limit, the agent names the person who decides.
- GapsWhat is missingAn empty approval line, a missing clause, a signature by someone without the right to sign, a licence about to expire.
How your own documents get checked
Hide them before sending, or show the documents on your screen. On a real desk, documents are read inside your environment and identifying details are masked before any outside model. How we handle data
- Choose the documentsInvoices, contracts, payment requests, applications: the ones your people check by hand today.
- Send a few examples, with names and amounts hiddenOr show them on your screen. We need the shape of the document and the checks, not your figures.
- Tell us the rulesThe policies, limits and approval rules your people apply, and the records they look at.
- We map the checksWhich checks an agent can prepare, which records it needs to read, and where a person decides.
- You see it on your kind of documentAs part of the process review: the map, the checks and the first desk it would go to.
Which document do your people check by hand?
Bring it to the process review. We map the checks, the rules behind them and where a person decides. We reply within one working day.
Questions people ask
Is a real AI model reading the document on this page?
No. This page is a scripted example on fictional documents, so it works the same for every visitor and nothing you do here is sent anywhere. On a real desk the agent reads your documents inside your environment, under the same rules.
Can I try it on my own document?
Not on this page. Your own documents are checked as part of the process review: you send a few examples with names and amounts hidden, or show them on your screen, and we show which checks an agent can prepare.
Where do the rules come from?
From your own policies: approval limits, payment terms, signing rights, credit rules. Each rule is written down once with its source, and the agent names that source every time it applies the rule.
What happens when the agent finds a problem?
It stops and prepares the decision: what it found, the source of each point, what it proposes and a draft comment. A person approves or returns the document. The agent never pays, signs or sends.
Can a person approve against the agent’s flag?
Yes. The person decides. The flag stays in the decision record next to the decision, so an audit later sees both.
What does the decision record hold?
Who decided, when, what was decided, the comment, whether the agent’s proposal was followed, the rules applied and the records checked.
Which documents can an agent check?
Any document your people check against rules and other records: supplier invoices, contracts, payment requests, customer applications, delivery notes, licences. The process review shows which ones are worth starting with.