Engineering Specification · Non-Negotiable Code Baseline

Engineering baseline and minimum technical invariants.

Which mathematical rules, open data schemas, and cryptographic locks we enforce in code before putting any B2B module into production.

This page is not marketing copy. It is the cold engineering specification governing our pre-accounting, document verification, and EU customs engine: every row maps to a hard constraint enforced by static analysis and automated architecture tests on every build.

PHP 8.4 Strict · PHPStan Max
Zero-Float IEEE-754 (BCMath)
1 Tax ID = 1 Isolated Vault

01 · Production Admission Criteria

Why we forbid common shortcuts in administrative software.

Artificial intelligence extracts structure and context from messy documents, yet it never decides arithmetic, exchange rates, fiscal ownership, or bank statement integrity.

INV-01 · DETERMINISM

Exact arithmetic outside generative models

No monetary amount, tax quota, or check digit relies on probabilistic inference. Every extracted document passes through deterministic BCMath examination pipes that halt posting on a single-cent discrepancy.

INV-02 · INTEROPERABILITY

Official structured formats over fragile scrapers

We implement open specifications governed by European and international bodies (ISO, CEN, OASIS, EU UCC) instead of brittle bank screen-scraping or coordinate-bound OCR templates.

INV-03 · CONTAINMENT

Cryptographic boundaries and per-tax-ID isolation

Every legal entity operates inside its own isolated document vault, learned vendor ruleset, and immutable ledger under its normalized tax ID, backed by signed S2S transport and zero inline JavaScript.

02 · Open Specifications & Engine Enforcement Matrix

Complete technical table of code-enforced standards.

Direct mapping between each official reference specification, its operational scope across the platform, and the real-world production failure it prevents.

Official Standard / Physical Law Platform Scope Engine enforcement and real-world failure prevented
01 Exact Arithmetic (Zero-Float IEEE-754 · BCMath scale 4/6)
Zero-Float IEEE-754 BCMath scale 4 / 6 decimal(19,4) -> int cts
Finance, Billing, Warehouse & Control Plane

Engine requirement: Architecture tests strictly forbid float types, float casts, or float literals in monetary amounts, tax brackets, or unit rates. Intermediate calculations execute as numeric strings at scale 4 (and scale 6 for FX rates) via pure BCMath, converting to integer cents solely on immutable final ledger entries.

Real failure prevented: Zero silent €0.01 binary IEEE-754 rounding drift when aggregating hundreds of delivery-note lines, multi-rate VAT bases, or withholdings.

02 ISO 20022 (camt.053) + SWIFT MT940 + AEB Cuaderno 43
ISO 20022 camt.053 SWIFT MT940 AEB Cuaderno 43
Treasury & SEPA Bank Reconciliation

Engine requirement: Structured ingestion of official SEPA/ECB and European corporate bank statements, verifying opening balances, booked entries, and closing balances deterministically without brittle HTML screen scraping.

Real failure prevented: Eliminates broken bank feeds whenever a bank updates its web portal, duplicate transaction imports, and orphan charges missing supplier invoices at quarter-end.

03 ISO 4217 (Immutable Dual Currency & FX Posting Lock)
ISO 4217 Original + Functional Currency Verified FX Lock
Multi-Currency Finance, Imports & IT Exports

Engine requirement: Every foreign-currency document immutably stores both its original ISO 4217 currency amount and its jurisdiction functional equivalent (EUR or RSD), enforcing a hard posting block whenever a verified accrual-date exchange rate is absent.

Real failure prevented: Prevents booking USD or GBP invoices at face value as EUR or retroactively mutating exchange equivalents on already reconciled periods.

04 ISO 13616 + ISO 7064 (MOD 97-10)
ISO 13616 IBAN ISO 7064 MOD 97-10 Encrypted at Rest
SEPA Mandates & Supplier Bank Coordinates

Engine requirement: Algebraic verification of country-specific IBAN length and modulo 97-10 check digits prior to accepting any SEPA mandate or bank account, encrypting the full IBAN at rest and exposing only the last 4 digits in UI.

Real failure prevented: Prevents SEPA direct-debit rejections caused by transposed digits and eliminates plaintext storage of sensitive banking coordinates.

05 CEN EN 16931 + OASIS UBL 2.1
CEN EN 16931 OASIS UBL 2.1 EU Fiscal Semantics
Pre-Accounting, Procurement & ERP Handoff

Engine requirement: Alignment of internal invoice data contracts with European semantic e-invoicing norm EN 16931 and OASIS UBL 2.1 syntax: explicit separation of seller, buyer, line breakdowns, exemption reasons, reverse charge, withholdings, and totals.

Real failure prevented: Prevents flattening complex intra-EU reverse-charge or mixed-VAT invoices into ambiguous totals incompatible with Sage, A3, SnelStart, or Exact.

06 ISO 6346 + EU UCC / CAU (Reg. EU 952/2013) + WCO HS / TARIC
CAU UE 952/2013 ISO 6346 Container EORI · WCO HS / TARIC
European Union Customs & Port Transit Vertical

Engine requirement: Algorithmic check-digit verification on maritime container numbers (ISO 6346), EU EORI format validation, WCO HS / TARIC commodity codes, and SHA-256 sealed visual traceability for AEO (OEA) operators within the EU Customs Territory.

Real failure prevented: Catches container ID typos, gross/net mass mismatches, or package count discrepancies across Bill of Lading, Packing List, CMR, and SAD/DUA drafts before port holds occur.

07 ISO 3166-1 + Physical Law 1 Tax ID = 1 Isolated Vault
ISO 3166-1 alpha-2 1 Tax ID = 1 Isolated Vault HMAC-SHA256 Anchor
Per-Entity Isolation, Multi-Entity Groups & Accounting Firms

Engine requirement: Canonical normalization of ISO 3166-1 country codes and tax identifiers (NIF, CIF, KVK/BTW, PIB). Every fiscal identity occupies an isolated vault, ruleset, and ledger: even inside a Multi-Entity Umbrella Inbox or Advisory Firm portfolio, two legal entities never mix entries.

Real failure prevented: Prevents cross-contaminating a subsidiary ledger with invoices addressed to a sister company or leaking vendor rules across unrelated firm clients.

08 FIDO2 / W3C WebAuthn + RFC 2104 (HMAC-SHA256) + CSP Strict + ISO 8601
FIDO2 / WebAuthn RFC 2104 · TTL 300s CSP Zero Inline · ISO 8601
Access Security, S2S Transport & Audit Trail

Engine requirement: Passwordless hardware/biometric Passkeys (W3C WebAuthn), server-to-server webhooks signed via RFC 2104 HMAC-SHA256 with a 300s anti-replay window, strict Content Security Policy with zero inline JS audited in tests, and UTC ISO 8601 timestamps.

Real failure prevented: Blocks credential phishing, webhook replay attacks across nodes, inline-script XSS vectors, and timezone ambiguity in forensic audit trails.

03 · Per-Module Technical Mapping

Which specification subset guards each operational vertical.

Every module lighthouse page displays a sober technical ribbon listing the exact standards active inside that vertical.

Vertical 01 · Finance (4 Doors)

Pre-Accounting, Multi-Entity Groups & Advisory Firms

ISO 20022 camt.053 · EN 16931 UBL 2.1 · ISO 4217 BCMath · SEPA ISO 13616

Active across Freelancers & Mixed Income (€49), Single-Entity SMEs (€49 / €99), Multi-Entity Groups (€149), and Multi-Client Firms (€199 / €399).

Vertical 02 · Warehouse & Procurement

Delivery Note Intake & Historical SKU Matching

EN 16931 · ISO 4217 BCMath · 1 Tax ID = 1 Isolated Vault

Scale-4 BCMath reconciliation across purchase orders, partial deliveries, and consolidated invoices prior to payment.

Vertical 03 · EU Customs

EU Transit Dossiers & Port Community Corridors

UCC / CAU UE 952/2013 · ISO 6346 · EORI/TARIC · ISO 4217

Exclusively engineered for EU Customs Territory corridors across Rotterdam · Antwerp · Algeciras · Valencia.

Architecture & Compliance Review

Does your engineering or compliance team need to verify a specific circuit?

Share your current ERP, bank statement format, or documentary workflow and our systems architects will reply with exact technical scope.

Sunnyface · Since 2002

No sales chatbots or scripted reps here. Tell us what software you run today, where your documents bottleneck, and we will give you an honest architectural assessment on how to connect it.

Full name and role
Company or firm
Corporate email
What software do you run today? (e.g. Sage, custom ERP, WMS, customs)
Where is your main document bottleneck today?

Direct engineering reply. Zero spam lists or cold sales calls.