The connector you're about to build already exists.
Forty-plus ERP connectors and five integration patterns, already engineered, under one roof. Scroll to follow one invoice: out of the ERP, through the rule packs and go-live checks, onto the Peppol network.
Plug the ERP in. Any ERP.
Odoo, SAP, Dynamics, Tally — and the twenty-year-old systems nobody wants to touch. Provision a sandbox tenant, pull real samples, and the connector does the rest.
- Four-step guided setup — ERP, tenant, connect, samples
- Sandbox first; promote to live when checks pass
- Connector health monitored per tenant
Five mandates. One connector layer.
Belgium and Malaysia live today. UAE, Oman and Qatar on the calendar. One integration, every geography — PINT AE, PINT MY, Peppol BIS 3.0 and whatever comes next.
- Belgium — Peppol BIS 3.0 · live
- Malaysia — PINT MY · live
- UAE · Oman · Qatar — on the roadmap, rule packs ready
Every rule applied, in one pass.
Inside the bridge the invoice crosses four layers. Field-by-field mapping decisions are audit-logged — approve in bulk, override with evidence, activate a version.
- ERP adapters — normalise any source schema
- Country rule packs — versioned per mandate
- Validation engine — every sample must pass
- Network delivery — signed, tracked, retried
Every check green before anything real is sent.
Mapping activated. Customer signed off. Network registration done. Data-processing agreement accepted. Only then does the connection switch on.
- Activate the mapping
- Customer signs off
- Register on the e-invoicing network
- Switch on the connection
Delivered. Cleared. Audit-logged.
The invoice lands at the tax authority — and your Command Centre already knows. That journey, for every tenant you manage, on one screen.
Five stages. Every market. Watch it run.
Extract from any ERP, normalize to one canonical model, validate against the local rule-pack, emit the profile the authority demands, deliver through your accredited stack. The red ones? Caught before they ever reach a tax authority.
Sending an invoice, then and now.
The new way to send invoices is to send them.
Master inventory of every tenant under ASP management.
Onboarding progress, connector health, mapping reviews, escalations and per-tenant actions — sandbox and live, side by side.
Mandates change. Your integration shouldn't.
An API your engineers will actually like.
- Idempotent by default — retry anything, duplicate nothing.
- Webhooks for every lifecycle event — sent, passed, blocked, cleared.
- Sandbox that behaves like production — same rule packs, same validations.
Stop building connectors. Start sending invoices.
Bring one real invoice from your ERP. We'll walk it across the bridge together — sandbox to cleared — in a 30-minute call.