Annex Pay · Accounts payable
Supplier invoices matched, approved and ready to pay.
Annex Pay works your accounts payable from supplier invoice to approved payment. The agent reads each invoice, matches it to the purchase order and the goods receipt, checks terms, duplicates and supplier details, and prepares it for your payment run. Within your limits, a matched invoice is approved once every check passes; a mismatch or anything above them goes to the person who approves. It never moves money: your finance team releases payments through your bank.
How the workflow runs
From supplier invoice to approved payment.
Accounts payable and invoice processing, step by step, on the systems your finance team already uses. Nothing is replaced.
- 01
Input
Supplier invoices by email, portal or e-invoicing, with the purchase orders and goods receipts they relate to, from your accounting system and the inbox where invoices arrive.
- 02
Rules and approval
The three-way match against the order and the receipt, payment terms, duplicate checks and the supplier’s bank details on record. Above your approval limits, or on any mismatch, the person you name approves.
- 03
Output
Invoices matched and coded, approved within your limits, and queued for the payment run your finance team releases, each linked to the order and the receipt behind it.
- 04
When it stops
A quantity or price mismatch, a possible duplicate, changed bank details or a supplier on hold: it stops, says why, and routes the invoice to the person who decides.
Three invoices, one agent
See what the agent checks.
Halden Tools receives invoices from its supplier Brightwell Supply. Choose a situation to see why the same agent approves one, routes a disputed line to a person and stops the third.
Invoice · Brightwell Supply
INV-2041: 120 × A-42 at €48.20, €5,784, net 30.
- Purchase order PO-7731Passed: Matched
- Goods receipt: 120 acceptedPassed: Matched
- Duplicate checkPassed: None found
- Bank details against the supplier recordPassed: Unchanged
Agent response
Approved and queued for the payment run.Order, receipt and invoice agree, the invoice is not a duplicate and the bank details match the supplier record. Within its mandate the agent approves it for the payment run due under net 30. Halden’s finance team releases the payment through its bank.
What it runs on
What it reads from your Company Brain
Annex Pay uses four parts of the shared layer. They are mapped once, for this agent, and every next agent reuses them.
Orders, receipts and invoices (Ledger)
Purchase orders, goods receipts and the invoices against them, each linked to its record, with what is already approved or paid.
Your finance systems (Map)
The accounting system, the supplier master data and the inbox or portal where invoices arrive.
Invoice approval authority (Gate)
What the agent may approve on its own, who approves above that, and the checks every invoice must pass first.
Invoice and payment state (Commit)
Received, matched, approved and queued for payment, recorded in your system of record with the evidence for each.
The platform underneathWorking with the other company’s agentHow a first deployment runs
Pairs withAnnex CollectThe partner pair: your supplier’s receivables agentPairs withAnnex BuyUpstream: the purchase order behind the invoiceQuestions buyers ask
What buyers ask about Annex Pay.
Does Annex Pay make payments or move money?
No. It prepares and approves invoices within your limits; your finance team releases payments through your bank.
What is a three-way match?
Checking an invoice against the purchase order (what was ordered, at what price) and the goods receipt (what actually arrived). Annex Pay approves only what all three agree on, within your limits.
What happens when a supplier’s bank details change?
The invoice stops. Changed bank details go to the person you name, who confirms them with the supplier through a contact already on record before anything is paid.
Can it work with a supplier’s agent?
Yes, if your supplier runs Annex Collect. Your Gate decides what Annex Pay may approve, your supplier’s Gate decides its side, and Annex Network verifies the exchange between them. It is an option, not a requirement: Annex Pay is useful on its own.
Which systems does it read?
Your accounting system, supplier records, purchase orders and goods receipts, and the inbox or portal where invoices arrive. Nothing is replaced.
What does a first deployment involve?
Mapping only what payables need: suppliers, orders, receipts, payment terms and who approves which invoices. Its limits are set with you, and it is tested against scenarios you agree before it approves anything.
Runs on the Annex platform.
Start with payables. Reuse the layer.
Every approved invoice traces back to an order and a receipt. Duplicates and changed bank details stop before payment. Approvals stay inside the authority you set. A customer starts with one role. Every next role reuses the layer.