All 220 guides
Every guide opens with a route check: the stage, the data, the validation to expect, and the first check to make. Page 2 of 11, guides 21 to 40.
Scanned invoices and OCR risks
Why a scanned invoice plus OCR is a reading guess, and how that guess fails on totals, identifiers and lines.
When a PDF is still the right answer
Small, one-off or human-checked transactions where a structured exchange adds cost without benefit.
Invoice data fields and master data: the complete field guide
Parties, lines, totals, references and identifiers, and the master data that keeps them consistent across systems.
Dates on an invoice: issue, supply and due
Three different dates, three different meanings, and why confusing them breaks tax and payment logic.
Field mapping that survives change
A mapping table with owner, source, target, rule and test, reviewed when either system changes.
Invoice lines: quantity, price, allowances and charges
Line structure, allowances, charges and the line total, and how a small line error becomes a large total error.
Master data governance for invoicing
One owner per master record, one change process, and one audit trail for party, product and tax data.
Payment terms and bank details on an invoice
Due date, payment means and account details, and the fraud risk when bank details change without a check.
Product and service coding on invoice lines
Buyer and seller codes, standard classifications, and what to do when the two code sets do not agree.
References: orders, contracts and delivery notes
How references tie an invoice to the transaction that created it, and why a missing reference blocks matching.
Seller and buyer party fields: identifiers that must match
Legal name, address, tax identifier and electronic address, and what happens when one of them does not match the receiver record.
Tax identifiers and VAT numbers on an invoice
What a tax identifier proves, what it does not prove, and how to check it without inventing a verification service.
Totals, tax and payable amounts: the arithmetic chain
Net, tax, allowances, charges and payable, in the order a validation rule checks them.
EN 16931 semantic model explained: meaning before syntax
The European standard for the core invoice model, its business terms, business rules and the separation of meaning from encoding.
Business rules and validation in EN 16931
How business rules turn the model into testable checks, and what a rule failure actually tells you.
CIUS profiles and extensions: national and sector rules on top of the core
Core Invoice Usage Specifications, what they may restrict, and what they must not break.
Common EN 16931 misreadings
Compliance with a syntax is not compliance with the model, and a valid file is not a valid business invoice.
Core invoice model: the business terms that matter
The central business terms of EN 16931, grouped by party, line, total and tax, with what each term means.
Directive 2014/55/EU and receiver obligations
What the directive requires of public buyers, and what it does not require of every seller.
EN 16931 and Peppol BIS Billing: how the profile implements the model
How Peppol BIS Billing 3.0 implements the core model, and where its rules add to the standard.