Quid
Product · Controls & PO matching

Problems caught before the payment run.

Quid checks every invoice against the purchase order and your supplier history before you pay. Duplicates, changed bank accounts and price differences are held until someone confirms.

app.quid.ai
Payment run · Friday · Example Supplies GmbHInvoice RE-3350 · €8,420.00
Payment held
Bank account differs from the one on file.Change arrived by email; account name doesn't match the supplier. Payment held until someone confirms.
Account on fileDE89 •••• •••• 3000
Account on this invoiceDE12 •••• •••• 7781
Account nameDoesn't match supplier
How the change arrivedEmail
Confirm with supplierKeep holding
Built for
Heads of financeOverpayments caught before they leave the bank.
ControllersEvery check recorded, with its reason and approver.
Accounting teamsOnly the invoices that need a look.
Operations and buyersInvoices checked against what you ordered.

Most overpayments are found after the money's gone.

  1. 01The same invoice arrives twice, through two channels.
  2. 02A "new bank details" email looks genuine.
  3. 03A supplier raises a price without telling you.
  4. 04You're invoiced for more than you ordered.
  5. 05Approvals stall when someone is away.
How it works

Every invoice checked before it's paid.

  1. 01Match to the orderQuantities and prices compared with the purchase order.
  2. 02Compare with historyPrices compared with what you paid that supplier before.
  3. 03Check for duplicates and bank changesAcross every inbox and entity.
  4. 04Route for approvalTo the right approver, with out-of-office cover.
  5. 05Hold or releaseProblems are held with the reason attached; the rest are ready to pay.
app.quid.ai · Invoice vs purchase order PO-5521
LineOrderedInvoicedResult
Encoder boards50 × €123.0050 × €123.00Matches
Cable harness50 × €18.5050 × €18.50Matches
Motor controllers50 × €118.0050 × €125.08Price up 6%: held
Fasteners10 boxes12 boxes2 more than ordered: held
Capabilities

The checks that run on every invoice.

DuplicatesStopped across inboxes, channels and entities.
Changed bank accountsA new account (e.g. IBAN) holds the payment until confirmed.
Unusual pricesEach line compared with what you paid last time.
Purchase order matchingQuantities and prices checked against the order.
Approvals with coverRouted to the right person, with out-of-office cover.
Audit trailEvery decision kept with its reason, document and approver.
40% → 5%of finance time on AP at a robotics company
30+ hrsreturned per week, on average
95%of invoices booked automatically

How controls compare.

CapabilityQuidManual AP + accounting system uploadBasic OCR tools
Duplicates stopped before payment✓If someone spots it–
Changed bank accounts held✓If someone spots it–
Prices compared with past orders✓ Every lineSpot checks–
Checked against the purchase order✓By hand–
Reason and approver kept for audit✓Email threads–

Controls questions.

Which checks run on each invoice?

Duplicates, changed bank accounts, unusual prices and a check against the purchase order, before the payment run.

What happens to a held payment?

It stays out of the payment run, with the reason attached, until someone on your team confirms or rejects it.

What if an approver is away?

Approvals have out-of-office cover, so invoices don't wait for one person.

Can an auditor see why an invoice was paid?

Yes. Every decision is kept with its reason, the source document and the approver.

How long does it take to go live?

Live within a few weeks, not months.

Book a demo

A thirty minute call to walk through how Quid would fit your entity structure and your existing stack.

Book a demo