Canonical data model and decision engine for automated three‑way invoice reconciliation in travel agencies
A practical, ready‑to‑implement companion to the parent article that supplies concrete artifacts engineering and ops teams need: canonical JSON/CSV schemas for Booking, SupplierInvoice and Payment records (required vs optional fields, keys and sample values); a decision matrix and pseudocode for the three‑way match engine (exact → fuzzy → tolerance → exception), with boolean rules and ordered operations; a complete exception taxonomy with standard codes, owning team, SLA per code, required evidence and resolution steps; recommended matching tolerances by supplier/product/currency; and short notes on integration points (OCR/IDP staging, matching engine, ERP posting).