Beyond batch: real-time treasury and tax between ERPs and banks

For twenty years, corporate finance lived with a delay. The ERP (SAP S/4HANA, Oracle or Odoo) closed the day’s books. A scheduled job sent flat CSV or MT940 files to the bank over SFTP. The team waited until the next morning to learn what the bank had accepted and what had failed.

That way of working is breaking down across the GCC, Europe, the Middle East and Africa. Two changes have turned batch files into a direct business risk.

Why overnight files stopped working

• Tax is now checked in real time. Saudi Arabia’s ZATCA Phase 2, the UAE’s PINT-AE framework and the EU’s VAT in the Digital Age (ViDA) require each invoice to be validated as XML and stamped cryptographically, in real time or close to it, before it is legally issued or settled.

• Payments now carry rich data. ISO 20022 replaces short reference fields with fully structured remittance details, in payment instructions (pain.001) and in cash management messages (camt.053 and camt.054).

When companies add real-time tax clearance and ISO 20022 on top of old batch middleware, the result is cash held up in transit, reconciliation done by hand, and billing that stops whenever a check fails.

Why standard connectors fall short in production

Standard integration connectors handle the simple case well. They are not built to keep financial records consistent when thousands of transactions arrive at once. In an established enterprise, three problems appear again and again:

• Data lost in translation. Custom ERP tables rarely map cleanly onto strict ISO 20022 schemas or UBL 2.1 e-invoices without a careful, rule-based mapping layer.

• Duplicates on retry. When a bank or a tax gateway times out under load, a simple retry can send the same payment twice or submit the same invoice twice.

• Two systems, two truths. The ERP marks an invoice as posted while the tax authority rejects its stamp. The finance team is left reversing entries by hand across systems that do not talk to each other.

How we build it

At XSIS, we treat integration as engineering, not configuration. A reliable real-time treasury and compliance engine rests on four parts.

1. Every event, captured once

We do not poll the ERP database. We capture each change as it happens, through a transactional outbox or the ERP’s own event mesh. Every financial event gets a stable key based on where the document came from, so it is processed exactly once across bank and tax systems.

2. Checks before anything leaves

Before a message reaches a bank or a tax portal, a separate validation engine checks the XML against its schema, applies the cryptographic signature (CSID or X.509) and creates the required QR code and hash chain. All of this takes under 50 milliseconds.

3. One internal format for every bank

A versioned internal data model sits between the ERP and the outside world. Adding a new bank, or moving from MT to MX messages, does not mean rewriting ABAP or PL/SQL code in the ERP.

4. Bank statements matched automatically

Bank statements (camt.053) and instant payment notices (camt.054) are read and matched against open receivables by clear rules. More than 99% of items reconcile with no manual step, and only real exceptions go to a person.

Where to start

You do not need to replace your ERP to end batch delays. Start with our Brownfield Diagnostic Bridge: in 1 to 2 weeks, we map where data is lost between your ERP, your middleware and your banks. You then move the most painful reconciliation loops to real time first.