Invoice delivery infrastructure

Every invoice, verified before it ever leaves the building.

InvoiceDirect fiscalises, signs, and routes your invoices — by email or the PEPPOL AS4 network — so finance teams stop manually chasing deliveries that should have arrived the first time.

Fiscalised for ZIMRA · Signed and validated for the PEPPOL network · Live in minutes with Odoo

MANIFEST — inv/2026-09/4578 DELIVERED
01 · SOURCE

Your ERP

Invoice raised in your accounting system, or dropped in as a PDF.

OdooSageQuickBooksD365
02 · FISCAL CHECK

ZIMRA validation

Checked for a live FDMS verification code and device fields before dispatch.

B993-BD3C-88A8-0A3C
03 · SIGN & VALIDATE

UBL + XML-DSIG

Built as UBL 2.1 BIS Billing 3.0, schema-checked, then signed.

EN16931XML-DSIG
04b · RAIL — PEPPOL AS4

4-corner network

Routed via SMP lookup, encrypted ebMS3.0 transport.

05 · CONFIRMED

Receipt logged, webhook fired

If either rail fails, InvoiceDirect retries and falls back to the other automatically.

Example fiscal verification codes issued on this route: E960606B-FCB6-F08A A31C7D02-9E4F-11B3 7B84F0A1-2C6D-40E7
Built to standard
ZIMRA FDMS PEPPOL BIS 3.0 UBL 2.1 EN16931 AS4 ebMS 3.0 XML-DSIG / XML-Enc ISO 6523
Two rails, one invoice

Not every customer is on the PEPPOL network yet. Deliver to both.

InvoiceDirect treats email and PEPPOL AS4 as equal, first-class delivery rails — not a network mode with an email afterthought. Every recipient gets the rail that actually reaches them.

P
Rail B

PEPPOL AS4 network

  • 4-corner model routing with live SMP/SML lookup
  • UBL BIS Billing 3.0, XML-DSIG signed, XML-Enc encrypted
  • Certificate lifecycle managed for you, per organisation
  • Falls back to email automatically if the network can't be reached
Why finance teams keep it

Compliance built into the pipe, not bolted onto the invoice.

The checks that usually happen in someone's inbox — "did this actually fiscalise?", "did the customer get it?" — happen before dispatch, every time.

01

Fiscal gate, not an honour system

Every PDF is scanned for its ZIMRA FDMS verification URL, verification code, and fiscal device fields before it's allowed to send.

02

Usage-based billing, tiered by volume

A monthly base fee plus per-invoice tiers that step down as volume grows — priced against what you actually send, per organisation.

03

Multi-tenant by design

Run one platform, many organisations — each with its own senders, templates, PEPPOL certificates, and rate profile.

04

Hexagonal ERP adapters

A single port interface behind every ERP connector, so adding the next accounting system doesn't touch delivery logic.

05

Retry and fallback, automatic

A failed PEPPOL delivery doesn't sit in a queue — it drops to email. A bounced email gets retried on schedule.

06

Webhooks for every status

Sent, delivered, bounced, fiscal-check-failed — pushed to your systems the moment they happen, signed for verification.

Plugs into what you already run

ERP integration, without rebuilding your accounting stack.

Invoices are fetched, or pushed in, through a pluggable adapter — your billing system stays the source of truth.

Odoo
Live
Sage Intacct
Live
QuickBooks
Live
Dynamics 365
Live
Pricing

Usage-based, shaped around your invoice volume.

Rate profiles are tiered per organisation — a base fee plus a per-invoice rate that steps down as volume grows.

Rate profile

Contact us for pricing

Tell us your monthly invoice volume and which rails you need — email, PEPPOL, or both — and we'll put together a rate profile.

Talk to sales
ROUTE · VERIFIED

Stop being the fallback delivery method for your own invoices.

Connect your ERP, add a sender, and the first fiscalised invoice can be on its way — by email or PEPPOL — inside a working session.

Get started free Read the routing docs