Governance & AI 6 min 2026-11-21

Deterministic multi-currency treasury: ISO 20022 camt.053, MT940, and Norma 43 vs screen scraping

Scraper-free bank reconciliation architecture enforcing exact running-balance checks, MOD 97-10 IBAN validation, and immutable dual-currency ISO 4217 records.

Why web screen-scraping bank feeds corrupt B2B quarterly closes

Countless bookkeeping apps advertise "automated bank feeds" powered underneath by brittle browser screen-scrapers or unstable aggregators whose sessions expire mid-quarter. Whenever two-factor prompts time out, three days of transactions silently drop out, long SEPA remittance strings get truncated, or USD corporate card charges land merged into EUR columns without explicit FX fees.

In production financial engineering, bank data is never scraped out of portal HTML—it is ingested from certified banking standards backed by mathematical balance proofs.

Treasury Invariant: Unless Opening Balance + Sum(Credits) - Sum(Debits) equals the statement's declared Closing Balance to the exact cent in BCMath, zero movements from that file are allowed into the auxiliary ledger.

Official ISO 20022 messaging and zero-float ISO 4217 dual currency

Following our public Engineering Standards Baseline, Sunnyface enforces three code-level treasury locks:

  1. Structured banking standards (ISO 20022 camt.053, SWIFT MT940, and AEB Norma 43): Native ingestion of European bank statement standards alongside SHA-256 visually verified closed PDF statements, validating every account IBAN algebraically via ISO 13616 and ISO 7064 (MOD 97-10) inside an isolated fiscal vault per Tax ID.
  2. Immutable ISO 4217 dual currency in BCMath scale 6 (0 float): Binary floating-point (IEEE-754) is banned across the codebase. Every foreign-currency invoice and bank line stores both its immutable original ISO 4217 currency and amount (USD, GBP, CHF, EUR) and its functional-currency equivalent (EUR or RSD) computed via verified BCMath scale-6 exchange rates and scale-4 accounting bases.
  3. Hard hold on missing settlement FX: Whenever a foreign SaaS or supplier bill arrives without a verified bank settlement value or official accrual FX rate, the document stops deterministically in the exception inbox rather than guessing an approximate rate that breaks reconciliation later.
[Official ISO 20022 camt.053 / SWIFT MT940 / AEB Norma 43 File]
                               │
                               ▼
       [Algebraic IBAN MOD 97-10 Gate · Isolated Tax-ID Vault]
       • BCMath proof: Opening + Credits - Debits = Closing
       • Dual ISO 4217 currency (Scale-6 FX · Scale-4 Bases · 0 float)
                               │
                               ▼
     [Deterministic 1:1 / 1:N Match vs SHA-256 Verified Bills]
         ├──▶ Cent-exact match ──────▶ [Sage / A3 / Exact Entry]
         └──▶ Orphan debit, no PDF ──▶ [Missing-Invoice Chase Alert]

Bank statement reconciliation at 0 € vs optional live PSD2 (+5 €/mo)

Structured treasury reconciliation is not locked behind enterprise tiers: reconciling via structured bank statement upload (ISO 20022 camt.053, Norma 43, MT940, CSV/PDF) comes included at 0 € from our entry 49 €/mo plan in SME & Company Pre-Accounting (pyme-control and cierre-autonomo, up to 350 docs/mo). For companies preferring a live automated bank feed (Open Banking / PSD2, subject to country bank coverage), it is available as an optional +5 €/mo per connected account on 49 €/mo, and 1 connected account is included free on the 99 €/mo plan (empresa-conectada, +5 €/mo per additional account), 149 €/mo multi-entity groups, and firm plans (199 € / 399 €/mo).

Associated production module

Deploy this workflow to production without building from scratch

Our plug-and-play modules and tailored workflows embed these battle-tested rules, ready to connect directly into Sage or your enterprise ERP.