Learn
Accounts-payable concepts behind invoice automation — what matching an invoice against an order and a receipt actually proves, why duplicates are the single most common real error, and what a tolerance is for. Useful whether or not you run Business Central.
What Three-Way Matching Actually Is
The order, the receipt and the invoice — what each one proves on its own, and why matching all three is the only version that catches anything.
What a Posted Goods Receipt Actually Proves
Why the receipt is the strongest evidence in accounts payable, what 'uninvoiced received quantity' means, and what a receipt cannot tell you.
Why Duplicate Invoices Are the Most Common AP Error
How the same bill arrives twice, why one check is never enough, and the one case where treating a repeat as a duplicate destroys the correct copy.
How Vendor Identification Actually Works
Why the ladder runs tax number, GLN, bank details, then name — and why a contradiction between two strong signals must never be resolved by score.
Tolerances in Accounts Payable, Explained
What a tolerance is actually for, why quantity tolerance should be zero, and how a percentage-plus-cap rule stops small tolerances becoming large ones.
PO-Backed and Non-PO Spend, Explained
Why the same invoice automation cannot make the same promise about both, and what control genuinely replaces a posted receipt when there isn't one.
Reason Codes, Not Confidence Scores
Why a percentage tells a reviewer nothing actionable, what a good exception message contains instead, and why the code set should be closed.
Templates and Semantic Extraction
Why coordinate-mapped invoice reading needs a setup per vendor and breaks on layout changes, and what reading by meaning does differently.
Charge Lines: Freight, Handling and Surcharges
Why a charge line is an authorization question rather than a matching one, and what happens when it is quietly folded into the invoice total.
Credit Memos, Prepayments and Recurring Contracts
Three document kinds that are not ordinary invoices, what each one must be checked against, and why classifying wrongly is worse than not classifying.