Mid‑office

Mid‑office turns orders into clean documents and ledger events. It generates invoices, posts receipts and fees, reconciles BSP/ARC and supplier statements, handles taxes (GST/VAT) and exceptions, and produces the journals finance expects.

Design starts with the order model. Capture supplier references (order ID, PNR/record locator where relevant), ticket and EMD numbers, traveller and payer, commissions, markups, fees and taxes at the moment of booking. Do not rely on later screen scraping or emails to fill the gaps.

Automated posting follows an event stream: order confirmed, ticket issued, refund completed, schedule change applied. Webhooks from the connectivity layer are the right backbone so the mid‑office stays in step without polling.

BSP/ARC reconciliation matches remittance and sales reports to internal orders. High match rates depend on capturing ticket numbers, coupons, taxes and commission fields consistently at source. Exceptions such as exchanges, ADM/ACM and partial coupons need explicit paths and audit trails.

Supplier statement reconciliation looks similar: match supplier invoices and credits to orders and receipts, surface deltas for investigation, and post settlements with the right tax treatment. Property and supplier mapping quality has a direct impact here.

Taxes require jurisdiction, rate and basis per fee or component. Store these explicitly, not as a blob of text, and render them clearly on invoices. For multi‑market businesses, support multiple tax regimes without forking the order model.

Credit and wallet logic must be authoritative at the time of sale. Enforce limits, reserve balances during booking and restore instantly on cancellation or receipt posting. The ledger should mirror customer‑visible balances to avoid support churn.

Success metrics are boring on purpose: high auto‑post rates, few unmatched lines, short exception queues, and predictable month‑end close. Achieve them through structure, not heroics — one schema, clear events and disciplined mapping.