CORE — 01
Canonical invoice model
One internal schema covers every market. Country specifics live in versioned rule-packs — so a regulation change is a config release we ship, not a migration you run.
Connector infrastructure · built once, configured per market
40+ connectors. 5 patterns. Nothing left to build.
Extract from any client ERP. Normalize to one canonical invoice model. Validate against the local rule-pack. Emit the profile the mandate demands. Deliver through your accredited stack. A new ERP is a mapping; a new mandate is a config release — never a project.
01 Architecture
The connector pipeline, end to end.
Live flow · one invoice at a time
Extract — out of any ERP
Forty-plus named connectors and five integration patterns pull invoice data out of whatever the client runs — cloud APIs, direct database views, watched folders, a signed on-prem agent, or a parsing inbox. And the API, database and agent patterns carry the return leg: delivery statuses, errors and — on receiving markets — incoming AP invoices flow back into the ERP through the same scoped, audited channel.
DIRECT APIDB / ODBCFILE WATCHERBRIDGE AGENTEMAIL CAPTURE
Named connectors40+
Integration patterns5
Toward the ERPRead · write-back on 3 of 5
Normalize — one canonical model
One internal schema covers every market. Country specifics live in versioned rule-packs — so a regulation change is a config release we ship, not a migration you run.
UBL 2.1CANONICAL MODELVERSIONED RULE-PACKS
Internal schemaExactly one
Regulation changeConfig release
Migration you runNone
Validate — every rule, pre-submission
Schema and authority business rules run before anything is submitted, with field-level diagnostics and rule IDs — the red packets you see dropping out of the wire. The same engine runs in sandbox and production: what passes in test passes live.
XSDEN 16931PINT AEPINT MYBIS 3.0
Rule sets maintained40+
DiagnosticsField + rule ID
Sandbox parityIdentical engine
Emit — the profile the authority demands
PINT AE, PINT MY, Peppol BIS 3.0 — and whatever comes next. Stage four is configuration, not code: a new mandate is a new rule-pack we ship, never a new integration you build.
PINT AEPINT MYBIS 3.0+ NEXT
Profiles live today3
New mandate =Config release
Your integrationUnchanged
Deliver — through your accredited stack
Idempotent submissions, automatic retries with backoff, webhook lifecycle events and an immutable audit trail — delivered through your AP / ASP accreditation. The Success API closes the loop: delivered and cleared confirmations land back in the ERP. Nothing is silently lost, ever.
WEBHOOKSSUCCESS APIAS4SML / SMPAUDIT TRAIL
SubmissionsIdempotent
RetriesAutomatic, backoff
Audit trailImmutable
STAGES 1–3 ARE JURISDICTION-INDEPENDENT. STAGE 4 IS CONFIGURATION. STAGE 5 IS YOUR ACCREDITATION. THAT'S THE WHOLE TRICK. — CLICK A STAGE TO OPEN IT.
CORE — 02
Validation engine
Schema and authority business rules run pre-submission, with field-level diagnostics and rule IDs. The same engine runs in sandbox and production — what passes in test passes live.
CORE — 03
Delivery & observability
Idempotent submissions, automatic retries with backoff, webhook lifecycle events and an immutable audit trail. Nothing is silently lost — ever.
THE OPERATOR'S SEAT — THE SAME PIPELINE, SEEN FROM THE COMMAND CENTRE.
02 Integration patterns
Five proven ways into any ERP.
The API, database and agent patterns run both directions: invoices are read out of the ERP, and delivery statuses — plus incoming AP invoices on receiving markets — are written back through the same scoped, audited channel. File watcher and email capture are one-way capture paths, with statuses in the dashboard and webhooks. The pattern is chosen during a one-day discovery based on the client's infrastructure, security posture and IT maturity — never a custom project. Cloud API patterns go live in days; legacy patterns honestly take 2–4 weeks.
Not sure which pattern fits a client? The decision matrix below maps pattern to client profile — or bring the client to a call and we'll tell you in ten minutes. Book it →
03 Decision guide
Which pattern for which client?
| Pattern | Best for | Client effort | Typical setup | Examples |
|---|---|---|---|---|
| Direct API | Modern cloud ERPs with open APIs | API key only | 1–2 days | SAP S/4HANA, Dynamics 365, NetSuite, Odoo, Zoho |
| Database / ODBC | On-prem ERPs without usable APIs | Scoped DB views — read + write-back | 2–3 days config · 2–4 wks end-to-end | SAP ECC, custom SQL-based ERPs |
| File watcher | ERPs that already export files | SFTP / folder access | 1–2 days | Legacy ERPs, AS/400-era systems |
| Local bridge agent | Air-gapped / strict-firewall networks · full AP + AR sync | One signed installer | 2–3 days config · 2–4 wks end-to-end | On-prem behind corporate firewalls |
| Email capture | Long-tail clients without IT | Forward invoices to an inbox | Same day | PDF / spreadsheet invoicing |
Setup times assume access granted — credentials, DB views or folder permissions in hand. Enterprise security reviews and client-side master-data cleanup extend legacy timelines; that's the honest 2–4 week number.
04 One integration · the whole catalog
40+ connectors. Click yours.
Every tile opens the trace: which pattern reaches that system, how long it honestly takes, and what the client has to hand over.
Direct API
Database / ODBC
File watcher
Bridge agent
Email capture
Any pattern
No match — but the five integration patterns mean we can almost certainly connect it. Ask us →
COVERAGE ISN'T A FEATURE. IT'S THE INFRASTRUCTURE.
05 Compliance coverage
Compliance changes by country. The pipeline doesn't.
One matrix our engineers maintain so yours don't have to.
| Country | Model | Format profile | Exchange | Authority | Status |
|---|---|---|---|---|---|
| UAE | 5-corner CTC (DCTCE) | PINT AE | Peppol via ASPs | MoF + FTA | Rule-pack live |
| Malaysia | CTC clearance + Peppol | MyInvois + PINT MY | MyInvois API + Peppol | LHDN · MDEC | Rule-pack live |
| Belgium | 4-corner | Peppol BIS Billing 3.0 | Peppol Access Points | FPS Finance / BOSA | Rule-pack live |
| Oman | 5-corner CTC | Oman PINT (expected) | Peppol via accredited SPs | Oman Tax Authority | In development · pilot Aug 2026 |
| Qatar | Hybrid CTC (expected) | TBD — draft law May 2026 | TBD | MoF + GTA | Tracking regulation |
Verified 10 June 2026 against the sources cited on each country page. Not legal or tax advice.
06 Reliability
The unglamorous parts, done properly.
UPTIME
99.9% uptime target
Monitored 24/7 with transparent status reporting. Mandate deadlines don't move for maintenance windows, so neither do we.
CORRECTNESS
Idempotent & replayable
Every submission is idempotency-keyed; failed deliveries retry with backoff; every state transition is journaled. Nothing is silently lost.
ISOLATION
Tenant isolation
Strict per-partner isolation, immutable audit logging, encryption in transit and at rest. Full security posture →
07 Platform FAQ
The questions engineers ask first.
Days, not months. The canonical model, validation engine and delivery layer already exist — a new connector is only the extraction mapping. Most new ERPs are first reached through the database, file or agent patterns the same week.
Only what you approve. Invoices are read out through API pulls, scoped database views, file pickup, the signed agent or inbox parsing — and on the API, database and agent patterns the return leg writes delivery statuses, errors and — on receiving markets — incoming AP invoices back into the ERP. Every write is scoped to agreed tables and fields, fully audited, and involves zero schema changes. Finance teams sign off because every write is one they asked for.
We ship a versioned rule-pack release platform-side and notify partners of the change and effective date. Your integrations and your clients' connectors don't change — that's the entire argument for the canonical-model architecture.
08 Prove it
Bring us your hardest ERP.
Thirty minutes with our engineering team. Name the system, the version, the hosting and the firewall situation — we'll name the pattern and the honest timeline before the call ends.