DIANA
Duplicate Invoice Analysis and Notification Agent
- Position
- Invoice Integrity
- Value chain
- Source to Pay
- Role
- Stops duplicate invoices before payment, and keeps every decision visible to the payables team, who decide.
Operate · Source to Pay
Money leaves on a small number of routes, and every route has a point where it can go twice, go early, or go to an account somebody changed last week. Those points are where the digital coworkers stand, inside the systems you already run.
Every control on this chain is real, written down, and applied by whoever is at their desk when the clock runs out. The ledger does not wait for the person who would have known what to look for.
4×
Best-in-class invoice processing cost is USD 2.78 per invoice against USD 10.89 for the average organisation
Ardent Partners, 2025
1.5%
Median rate of duplicate or erroneous disbursements
APQC benchmarking
21.9%
Share of payables staff time spent managing suppliers
Ardent Partners, 2025
USD 3.05bn
Reported business email compromise losses in 2025
FBI IC3, 2025
Where the pressure shows up
Transactions are opened, compared and reconciled one at a time, so the population is always larger than the day.
Who feels itHead of Accounts Payable · cost per invoice
A near-duplicate hides in history under a different date format, entity or intake route, and clears every check taken on its own.
Who feels itFinancial Controller · duplicate disbursement rate
Onboarding, bank-detail changes and duplicate vendor records all carry control weight, and all queue behind each other.
Who feels itMaster-data owner · payee changes verified independently
Straight-through processing stops at the exception, and the exception goes to a person who was doing something else.
Who feels itAccounts-payable manager · straight-through rate
Status questions, statement reconciliations and remittance chasing consume capacity the record could answer from itself.
Who feels itAccounts-payable manager · staff time on supplier queries
Claims arrive needing policy applied line by line, coding to the right account, and an approval before anyone is reimbursed.
Who feels itFinance leader · claim cycle time
Supplier spend and employee spend leave by separate routes and answer to one governance framework. It has to make every dollar out legitimate, correct, deliberate and on time, holding leakage from duplicates, fraud, policy breaches and mispayment near zero without slowing the business that spends it.
The canonical sequence
Door one · supplier spend
Define and tender
MMARCELO
Award and agree
VVALERIA
Commit
·Held by your team
Confirm delivery
·Held by your team
Validate
DDIANA
Disburse safely
PPETRA
Door two · employee spend
Claims take a shorter route and meet the same payment run. EERICA holds every step of it.
Claim and receipt
EERICA
Line by line
EERICA
Paid with the run
EERICA
Status, statements and remittance questions answered from the record, so neither door queues behind a question
SSAMIR
Who owns this chain today
Read down any position on a chart and it tells you who is accountable for it, what its holder may do without asking, and who picks up the call that is not theirs to make. A digital coworker is written up the same way, and the answers do not change because the holder is not a person.
DIANA
Duplicate Invoice Analysis and Notification Agent
DIANA Invoice Integrity
DIANA
I propose to reject INV‑48219 as a duplicate under reason code DUP‑02, queue the supplier notice for payables and annotate the supplier record. It needs one confirmation that INV‑48174 has been paid. Shall I proceed?
Payables Lead Finance operations
Confirmed against the March statement. INV‑48174 was paid on 12 March. Proceed.
Seen by DIANA
DIANA Invoice Integrity
Rejected INV‑48219 with reason code DUP‑02. Supplier notice queued for payables and the supplier record annotated.
Exception closed by the Payables Lead.
The chain was written up as a chart before any of the six were built for it, which is why none of them can finish another’s work. That separation is the thing a controls signatory is actually buying, and it holds whether the holder is on leave or not.
Six digital coworkers hold posts across this chain, from the tender that sets the price to the payment run that releases the cash, and each is measured on one number. How much it moves for you is sized from your own data in the first session.
Population coverage, not a sample
Every invoice, claim and payment line is screened, not a sample of them.
KPIDDecreaseDuplicate disbursement rate
Cash held before it leaves
A payment the run cannot substantiate waits for a person, and the decision is logged.
KPIPIncreaseDuplicate value stopped before payment
Capacity returned to judgement
Supplier enquiries are answered from the record, with the document trail attached.
KPISDecreasePayables time on supplier questions
Savings that survive to realisation
Buying through the contract becomes the faster path, so negotiated savings are not erased around it.
KPIMIncreaseNegotiated savings realised
Payee changes verified independently
No payment instruction changes on the strength of the request alone, and the check is recorded.
KPIVDecreaseFraudulent payee changes
Evidence produced as the work happens
The record the control test needs is written as the work is done, so sample and population become one.
KPIEIncreaseAudit evidence ready at close
A digital coworker works inside the systems, data, policies and authorisations you already have. It is given the access a person in the same position would be given, and no more. Your auditors test it in the environment they already know.
What the role works inside
Enterprise applications
ERP, procurement, finance, workflow and operational systems.
Master data
Supplier, employee, purchasing, invoice and payment records.
Policies and controls
Business rules, thresholds, approval policies and compliance requirements.
Authorisations
Defined permissions for every action performed by the role.
Governance
Security, privacy, service levels, change governance and escalation.
The control model
Defined actions, inside the authority you set.
Prepares the case and hands the decision up.
Anything outside the authority the role holds.
Both sides put a signature on the same page before anything is built, and the ProxyN lead who signs is accountable for it in the way your sponsor is. Nothing in it gets agreed after the result is known.
What gets signed
Five lines both sides sign before anything is built. Every one is a fact about your operation, not a forecast about ours.
What happens after signing
The order the work runs in, one role at a time. The seventh step is the first step of the next loop.
What we need from you
Twelve months of history from the system of record, read only
The written policy and the approval thresholds the role will work inside
The accountable person for the number, in the room for the first session
Get started
Bring one workflow and the person accountable for it. In the first session we map the process, establish the baseline logic and tell you whether there is a number worth signing. If there is not, we will say so.