Invoice verification for AP teams
Every control passes.
The money is gone.
One field on a familiar invoice changes: the bank account line. Every approval still passes. InvoiceQA reads the document, recomputes the numbers and verifies the payee before payment leaves the account.
No account. Your file is read once, never stored, deleted within 24 hours.
How it works
Drop in a PDF
No account, no e-mail. The file is read once, never stored, and the result is deleted within 24 hours, automatically.
The machine reads, then distrusts
An AI agent inspects the document and works through it check by check. Then 28 deterministic checks recompute every number and test every reference. Reading the document and checking it are separate steps. The checks recompute everything from the extracted figures.
A verdict you can act on
Safe to pay, needs review or hold, with every finding traced to the check that produced it, in plain sentences.
What it checks
Arithmetic
Line items, subtotal, VAT and total reconcile to the öre. Recomputed, never trusted.
VAT & tax
Rates tested against the Swedish bands (25, 12, 6, exempt) and reverse charge where it applies.
Currency
A stated exchange rate is recomputed against the foreign amount and the invoice date.
References
OCR check digit, organisation number, bankgiro and IBAN. A document that states two different accounts of the same kind is flagged on the spot.
Payee history
The account on the invoice against the account of record in your ERP and the accounts your bank actually settled to. ERP data through a connector such as Zwapgrid and settlement data through Open Payments. Running now in the demo workspace.
Duplicates
The same supplier, amount and date twice, or a reference already used. Needs your invoice history. See it live in the demo.
Verification calls
When bank details change, a voice agent calls the supplier on the number in your ERP, never the one printed on the invoice, and challenges them to confirm the previous account. Hear a real call, or place one in the demo.
Bankgiro verification
The stated account tested against the bank's own records through Open Payments.
Two invoices. Three quiet edits.
Both are the same invoice from the same fictional supplier. The first was issued. The second arrived in the inbox. The differences are marked: the bankgiro, the telephone number, the e-mail address. Nothing else moved. Every approval control passes both.
| Field | As issued | As received |
|---|---|---|
| Bankgiro | 5402-9681 | 991-1231 |
| Telephone | 08-410 305 82 | 08-410 552 17 |
| ekonomi@manbriskonsult.se | faktura@manbris-konsult.com |
A well-formed bankgiro, and 991-1231 is one, says nothing about who receives the money. With payment history connected, InvoiceQA holds the payment the moment the stated account deviates from the account of record.
Then it picks up the telephone
When bank details change, a recorded, automated call asks the supplier to confirm the previous account: the number two years of payments actually settled to. A genuine supplier knows it. Someone who intercepted an invoice knows only the new number they wrote on it, and confirming that would prove nothing.
This is a real call from the preview, placed to the demo line, answered and confirmed there. Even then, the payment stays held until a person releases it.
Transcript
- InvoiceQA: Hello, this is InvoiceQA, the payment verification service, calling on behalf of Nordkap Industri AB. This call is recorded. We have received invoice 2026-1042 from Månbris Konsult AB, and before it is paid, we need to confirm a change of payment details with you. First question: has your company recently changed the bankgiro account where it receives payments? Please say yes or no.
- Supplier: Yes.
- InvoiceQA: Thank you. To verify, I need the previous account, the bankgiro number your company was paid into before the change. Please read it out now, digit by digit.
- Supplier: reads the previous account, digit by digit
- InvoiceQA: Thank you, that matches our records. The new bankgiro number stated on the invoice is: 9, 9, 1 - 1, 2, 3, 1. Once more: 9, 9, 1 - 1, 2, 3, 1. Is this the account your company now uses? Please say yes or no.
- Supplier: Yes.
- InvoiceQA: Thank you. Your confirmation has been recorded. The payment stays on hold until the accounts team completes a final review. Goodbye.
Calls in this preview go to a demo line, never to a supplier's real number. In a connected workspace the call goes to the number held in your ERP, never the number printed on the invoice.
A connected company,
in miniature
Nordkap Industri AB is fictional. The machinery is not. Its supplier ledger and two years of settled payments are seeded, the bank data was pulled live from the Open Payments sandbox, and every verdict on the shelf came out of the same engine that reads your uploads. This is what the full product does against your ERP, running here on demonstration data, open to anyone.
What happens
to your file
- Read once, never stored
- Result deleted within 24 hours, automatically
- No account created, no e-mail collected
- Zero third-party requests on this page
The PDF you upload is read by an AI model so the text and figures can be extracted. Taranuka AB is the data controller, and the model provider acts as a sub-processor for that reading only. The file itself is never stored. A fingerprint of the file is kept for the same period so an identical document is not read twice. Anyone who uploads the very same file within that window sees the same result.
This page loads no third-party scripts, no fonts from a CDN, and no analytics. That is a checkable claim, not a slogan. Open the network tab.
Get full access
Accounts, connected workspaces and verification calls on your own invoices are in development. If you want them early, or if you run an AP team and would shape the product as a design partner, Taranuka AB wants to hear from you.