Accounts Payable
Invoice Verification, line by line.
Verify what should be paid. Focus on what shouldn’t.
Donnerstag connects each supplier invoice to the purchase order, receipt, contract, proof of delivery, bill of lading, and any other source your validation process requires, checks every relevant line against approved rules and clears what matches, leaving discrepancies quantified, evidenced and ready to dispute.
From invoice to verified, resolved and correctly paid.
An invoice checked line by line.
Matched lines clear to pay; the flagged lines are quantified against the rule they break.
Running
Line
Expected
Invoiced
Status
Matched
Matched
Price variance
Qty variance
Matched
01
The invoice in context
The supplier, document reference and total, with the purchase order, receipt and contract already linked.
02
Match result
How the approved rules matched this invoice against the records behind it. Clean lines clear to pay.
03
Auto-verified & cleared to pay
Each line that agrees with the PO, receipt and contract inside tolerance, released for payment.
04
The discrepancy, quantified
The flagged line, the rule it breaks and the amount at stake, ready to dispute.
What Invoice Verification does before anyone touches it.
Invoices are read, matched line by line against the purchase order and receipt, and anything agreeing within tolerance clears without a person.
Capture the invoice
Read invoices from PDF, e-invoice and EDI, and structure header and line data into usable fields.
3-way match
Link each invoice to its purchase order, goods receipt, contract, proof of delivery, bill of lading and any other required source, and check they agree.
Line-level checks
Verify price, quantity, rate, charges and surcharges against what was agreed and received.
Duplicate detection
Catch resubmitted and near-duplicate invoices before they reach the payment run.
Tolerances
Clear small, expected differences automatically instead of turning them into exceptions.
Exception typing
Classify what fails (price, quantity, unsupported charge, duplicate) and route each accordingly.
Most invoices clear without a person.
The team stops keying and matching invoices and spends its time on the discrepancies that actually protect cash.
Auto-verified & cleared to pay
Exceptions to resolve
The share that protects cash.
Each exception arrives typed, quantified and evidenced against the applicable rule, not as a whole invoice to re-check by hand. These are common examples; the exception types follow your own validation rules.
Price
Price variance
The invoiced price or charge exceeds the purchase order or contract rate.
Resolution:
Short-pay the difference or challenge the line with the contract attached.
Quantity
Quantity variance
The invoiced quantity exceeds what the goods receipt confirms was delivered.
Resolution:
Pay the received quantity and dispute the balance with the GRN attached.
Charge
Unsupported charge
A freight, handling or surcharge line has no basis in the agreement.
Resolution:
Withhold the charge and request support from the supplier.
Duplicate
Duplicate submission
The invoice matches one already received or paid.
Resolution:
Block the payment and notify the supplier with the original reference.
How a discrepancy reaches the right payment.
Select an action to see what it does, and the authority it runs under.
01
Isolate
Separate the flagged lines from the clean ones.
02
Type
Classify the failure and quantify the impact.
03
Evidence
Attach the PO, receipt and contract clause.
04
Decide
Approve, short-pay, hold or challenge.
05
Pay
Release what is owed and record the outcome.
Act on a discrepancy
The resolution determines what gets paid.
Depending on the rules, permissions and authority model, a resolved or unresolved case drives the appropriate payment action.
Prepare
Route the action
The system prepares or routes the payment action, requiring review where judgment is needed.
Execute
Within boundaries
Authorised actions execute inside defined permissions, where the approved rule allows it.
Hold
Nothing leaves early
An unresolved discrepancy holds the line or invoice out of the payment run until it is decided.
You determine what is suggested, what requires approval and what may run automatically.
Discrepancies become disputes.
A flagged line hands off to a managed dispute case with the rule, amount and evidence already attached.
See the whole book. Drill to any invoice.
An overview of invoice verification at operation level, then open to the invoice, line, rule and evidence behind every figure.
Running
Line
Expected
Invoiced
Status
Matched
Matched
Price variance
Qty variance
Matched
Keep every invoice answerable.
Know what cleared, what didn’t, and why.
What cleared?
The lines verified and released to pay.
What didn’t?
The flagged line, its type and amount.
Why?
The applicable rule and the variance found.
What supports it?
The PO, receipt, contract and documents.
Who owns it?
The AP analyst or workflow responsible.
How did it end?
Paid, short-paid, held, credited or accepted.
What Accounts Payable gains
Every unverified line is money at risk. These are the outcomes the operation is built to produce.
Prevent incorrect outflows
Stop unsupported charges, duplicates and overcharges before money leaves, where the process and authority allow.
Verify every line
Line-level checking becomes practical at volume instead of sampling or trusting the header total.
Faster clean invoices
Invoices that match clear straight through, so suppliers are paid on terms.
Evidenced disputes
Each discrepancy arrives with the rule, the amount and the supporting records already attached.
Fewer manual checks
Verification, evidence gathering and routing happen in one running operation.
Traceable payment control
Every approval, hold and short-pay stays connected to the rule and decision behind it.