Before the checks
The invoice is stored once
Every invoice, from any channel, is stored in an inbox first, keyed by its source and the source’s event ID. A source that sends the same invoice twice changes nothing the second time. An update older than the copy Coverbase holds is stored and skipped. An invoice with no invoice number is refused and shows Stopped retrying on the Sources tab.The supplier is found
Coverbase looks for the vendor by the supplier ID the source sends first. Without a match, it compares the legal name, ignoring case, punctuation and suffixes such as Inc, Ltd, LLC, GmbH and SA. It never picks between two vendors:- One match. The invoice goes on.
- Two or more matches. The invoice waits. The Sources tab says “More than one vendor matches supplier …”. Set the supplier ID on the right vendor, then replay the event.
- No match. The invoice waits until a vendor carries that supplier ID.
The PO is found
The PO number on the invoice is compared as letters and digits only, after removing a leading label such asPO, P.O., PO#, Purchase order or No., and the zeros padding the front. PO# 4500-12, po450012 and 000450012 are the same PO.
- The PO is on record. The checks run.
- The PO is closed. The PO number check fails with “The PO is closed, so nothing more should be billed against it.” and a PO is closed case opens for AP. A closed PO is never matched.
- The invoice names a PO that has not arrived. The invoice shows Waiting for PO and no case opens, because POs often arrive after their invoices. The checks run as soon as the PO arrives from your procurement system. If no PO arrives within the grace period (72 hours by default), the checks run without it and a PO not found case opens for AP. If the PO turns up later, the invoice still links to it and the checks run again.
- A line names a different PO that has not arrived. That line is never matched against the invoice’s main PO. The PO number check fails on that line, the line waits for its own PO, and the checks run again when that PO arrives. The other lines are checked against their PO as usual.
- The invoice has no PO number at all. It fails the PO number check with “The invoice has no PO number.” and opens a No PO number on the invoice case for AP. This reason does not count against the supplier, because your buyer may never have issued a PO.
Duplicates are caught
An invoice is a duplicate of another when it has the same supplier, the same invoice number, the same total and the same currency. Invoice numbers are compared ignoring punctuation, case and the zeros padding the number, soHPL-0660413 and HPL660413 are the same number. The invoice date is ignored, because email and EDI copies of one invoice often disagree on it by a day. A credit note is never a duplicate of an invoice, even under the same number. See Duplicates for what happens next.
Near misses are not marked duplicate automatically. They fail the Not a duplicate check and go to a person. See Possible duplicates.
Mapping invoice lines to PO lines
Each invoice line is mapped to the PO line it bills before any line is checked. Coverbase tries these in order and stops at the first that works:
A case where every check passed but both lines were matched by description, so a person confirms them.
Description mappings
When you accept an invoice whose lines were matched by description, Coverbase remembers it for that supplier. The next invoice from them with the same line description maps to the PO line carrying the same part number, shown as mapped by reviewer, and counts as verified. This needs a part number on the PO line both times. Coverbase learns only from your organization’s own accepted invoices. If a suggested line is wrong, pick the right PO line under Line mapping in the Accept invoice dialog. The checks run again with your mapping before the invoice is accepted, and the line is then mapped by reviewer. See Accept invoice.The checks
Every check appears on the case, under Recommended next step: failures and warnings first with what was expected and what was invoiced, then the checks that passed.Units of measure
When the invoice bills in a different unit from the PO, Coverbase converts it only when the unit codes themselves say how many pieces each holds:- Count units: each (
EA,PC,STKand similar), pair (PR, 2), dozen (DZ, 12), hundred (HUN, 100) and gross (GR, 144). - Pack codes that state their own count, such as
BX12,CS-24,12/BXorBOX OF 10.
BX12 at 25.20 per box is 240 each at 2.10.
A pack code with no count, such as CS or BX, is never guessed, because its size lives in the supplier’s catalog. The line’s quantity and price are not compared. Quantity ordered fails with “The invoice bills in a different unit from the PO and the two cannot be converted. Ask the supplier to bill in the PO’s unit.” and a Billed more than ordered case goes to the supplier. A line where either side names no unit is read in the other side’s unit.
What happens next
Each failing reason opens one case. The recommendation, shown as Recommended next step, follows from the reasons:Exception reasons

A missing goods receipt: the invoice is right, so the supplier is told no action is needed and operations owns the case.
Reading emails and PDFs with AI
An invoice forwarded to your intake address, or uploaded as a PDF through the intake API, has no structured fields. AI reads them, and the checks above decide whether to trust what it read.The message is stored
AI reads the invoice
What it read is checked for shape
- A statement, a remittance advice, a quote or a message with no invoice creates no invoice. The message shows Stopped retrying on the Sources tab straight away, without asking the model again, for a person to look at.
- An invoice with no invoice number, or with an invoice number that is not printed anywhere in the message, is refused the same way.
- A PO number that is not printed in the message is treated as a guess and dropped, so the invoice is matched as citing no PO.
- Numbers and dates are read the way the document prints them, so
1.186,50in a German invoice is 1186.50 and12.11.2026is 12 November 2026. - A missing currency is not assumed. It is taken from the PO and flagged, and Invoice data complete fails until a person confirms it. A line with no readable quantity is stored as zero and fails the same check.
- A supplier is found the same way as for any invoice, and never guessed between two vendors. When no supplier name was read, Coverbase uses the supplier named by whoever uploaded the PDF, else the sender’s email address.
It is matched like any invoice
Low confidence goes to a person
Its confidence is shown
It waits for the ledger
Coverbase AI on a mismatch
With Explain mismatches with Coverbase AI on, Coverbase AI looks at invoices from the last 14 days that did not match and have no explanation yet. It reads the invoice and PO lines (description, part number, quantity, unit price) and the failed checks, and writes:- An explanation of under 80 words of what differs and why, naming the lines.
- For each invoice line no method placed, the PO line it thinks it bills, with its reasoning, or none when nothing fits.
Duplicates, credit notes and corrected invoices
Duplicates
Coverbase keeps every copy and decides which is the invoice:
A possible duplicate: the same invoice booked twice by the ledger.

The drawer of a duplicate invoice, with both copies listed.
Possible duplicates
Some invoices look like a copy but are not exact. Coverbase does not decide those. The Not a duplicate check fails, a Possible duplicate case opens for AP, and the case names the earlier invoice:Credit notes
A credit note is matched against its PO like an invoice, and its quantities subtract from what has been billed on each PO line. Suppliers print credit notes with negative or positive quantities, and both are read as a credit. So a credit note for returned goods makes room for the supplier to bill them again. A credit note under the same number as the invoice it reverses is not a duplicate of it. On a statement, a credit note is its own line, and the statement shows a credit notes total.Corrected invoices
A corrected invoice, whether the supplier sent it from the portal or your ledger sent a revision, becomes a new version of the same invoice. The earlier version shows Replaced by correction and stays on record. Every open case on it moves to the new version, and the checks run on the new version straight away. A difference the correction fixed resolves its case. The first-pass result belongs to the original billing. A correction never turns a first-pass mismatch into a first-pass match. If your ledger sends a changed invoice under the same ID without marking it a revision, Coverbase refuses it rather than overwrite a booked invoice. The event shows Waiting for a reference on the Sources tab, with “It conflicts with a record we already hold.” Send it again as a revision, then replay it.When matching runs again
Worked examples
These come from the test corpus Coverbase runs through the same intake, matching and case code your invoices go through. Every supplier, part number and amount in them is invented. Tolerances are the defaults unless the example says otherwise.Simple matches
Exact 2-way match for a service PO
Exact 2-way match for a service PO
Exact 3-way match
Exact 3-way match
Mismatches
Unit price above the PO price
Unit price above the PO price
Billed more than received
Billed more than received
PO number written three ways
PO number written three ways
4500012345.Billed by the box, ordered by the each
Billed by the box, ordered by the each
BX12 states its count. 20 boxes of 12 is 240 each, and 25.20 per box is 2.10 each.Compare a unit with no count. PO-4500052490 orders 600 EA of EP-FOAM-33 earplugs at 0.48. Invoice CR-33251 bills 3 CS at 96.00 and never says how many are in a case. Coverbase does not guess. Quantity ordered fails with “The invoice bills in a different unit from the PO and the two cannot be converted. Ask the supplier to bill in the PO’s unit.” A Billed more than ordered case goes to the supplier, and no price case opens, because a price per case cannot be compared with a price per each.Invoice billed to the wrong legal entity
Invoice billed to the wrong legal entity
Duplicates and credits
Same invoice number written differently
Same invoice number written differently
Credit note reversing an invoice
Credit note reversing an invoice
Complex cases
One invoice across two POs
One invoice across two POs
Invoice arrives before the PO and the receipt
Invoice arrives before the PO and the receipt
Reading emails and PDFs
German invoice with European number format
German invoice with European number format
2.568,00 EUR, dated 12.11.2026, PO number printed without a prefix.What Coverbase does. Matched.Why. The numbers and the date are read the way a German document prints them. The lines quote no PO line, so they are matched by part. Stk is a count unit, the same as EA.Statement sent instead of an invoice
Statement sent instead of an invoice
Low confidence reading that agrees with the PO
Low confidence reading that agrees with the PO