Pre-seed · UK fintech infrastructure

The universal standard for invoice exchange.

Every business sends invoices. No two systems agree on how. NOMOINVOICE is the canonical layer in the middle — the SWIFT for invoices — so any supplier can bill any buyer, on any system, cleanly.

Many-to-ONE-to-Many Peppol-aligned Built for mid-market
One standard, every system
XeroNetSuiteDynamics 365SageQuickBooksSAP
The architecture

Many-to-ONE-to-Many

Suppliers send invoices in any format. We normalise every one into a single canonical schema. Buyers receive clean, structured, validated data into whatever system they already run — no bespoke integrations at the edges.

PDF invoice Xero Email / CSV EDI / XML Portal upload NetSuite Dynamics 365 SAP Sage Intacct QuickBooks SUPPLIERS — ANY FORMAT BUYERS — ANY SYSTEM NOMO CANONICAL
In — Many
Suppliers push invoices via email-in, API, connector, or portal. No format requirements, no onboarding friction.
Middle — ONE
Every invoice is parsed, validated, and normalised against the NOMOINVOICE canonical JSON schema.
Out — Many
Buyers receive clean, structured invoices straight into their accounting or ERP system of record.
The problem

The invoice problem is an integration problem.

Invoice exchange is the plumbing of B2B commerce — and it has no shared standard. The cost is real, it is large, and it is mostly hidden inside headcount.

01

No shared standard

PDFs, scans, spreadsheets, portal uploads, EDI, proprietary XML. Every supplier sends a different shape; every buyer expects a different one.

60–80%of mid-market invoices need manual touch
02

The N×N integration tax

Connecting every accounting and ERP system to every other one is a bespoke, brittle, never-ending engineering bill. No generalist can win it.

£8–£15fully-loaded cost per invoice with human touch
03

The hidden cost of exceptions

Reconciliation, rekeying, chasing, correcting. It sits inside finance headcount, invisible on the P&L — which is exactly why it has been tolerated.

£400k+avoidable cost at 50k invoices / year
How it works

Five steps. One clean invoice.

01

Ingest

Invoices arrive by email-in, API, connector, or upload — in any format.

02

Extract

An AI-native pipeline turns any document into structured data, with confidence scoring.

03

Validate

Totals, VAT, duplicates, sanctions, and buyer-specific business rules — all checked.

04

Normalise

Output is written against the NOMOINVOICE canonical schema. One shape, always.

05

Deliver

Clean invoices land in the buyer's system via connector, API, or webhook.

The standard

One schema. Every invoice.

The core of NOMOINVOICE is its universal invoice JSON schema — header fields, line-level detail, tax, and extension blocks for regulated industries and multi-entity groups.

It is designed to map cleanly to Peppol BIS Billing 3.0 and EN16931, so a normalised invoice can be emitted as a compliant e-invoice with no further transformation.

  • Versioned, open, and stable — built to be depended on
  • Peppol-aligned by construction, not retrofitted
  • Per-invoice audit trail and data lineage on every field
invoice.canonical.json
{
  "schema": "nomoinvoice/v1",
  "invoice_id": "INV-2026-04812",
  "issue_date": "2026-04-17",
  "currency": "GBP",
  "supplier": {
    "name": "Northwind Ltd",
    "vat": "GB429114007"
  },
  "lines": [{
    "description": "Consulting — Q2",
    "qty": 1, "unit_price": 4200.00,
    "tax_code": "S", "tax_rate": 0.20
  }],
  "total": 5040.00,
  "peppol_ready": true
}
Why now

The standard is becoming law.

Structured e-invoicing is moving from best practice to legal requirement across the UK and EU. The regulation does the market education — NOMOINVOICE is the path of least resistance.

2026

UK consultation underway

HMRC and DBT are consulting on mandatory e-invoicing, with public-sector pilots already running.

2029

UK VAT mandate expected

A phased structured e-invoicing mandate, expected to align technically with Peppol and EN16931.

2030

EU ViDA in force

VAT in the Digital Age requires structured cross-border e-invoices, with several member states mandating earlier.

Strategic consequence

We don't have to sell a vision. Regulation sells it for us.

Every UK mid-market finance team will need Peppol-compliant structured invoice data within our first three years. We just have to be the easiest, cheapest, most reliable way to get there — especially for the firms that can't afford enterprise AP suites.

The team

Operators who have lived the problem.

Built by people who have run the AP function, raised the capital, and sat in the CFO seat at exactly the kind of company NOMOINVOICE is built for.

SK

Steve Kalinda

FOUNDER & CEO

10+ years of enterprise AP/AR operations across SAP, NetSuite and Dynamics. 6 years in startups, including an acquisition and a $10M+ raise. Has lived the invoice problem from both sides.

JK

Jakob Kupferberg

CO-FOUNDER & CSO

Corporate strategy, ESG positioning and investor narrative. Cambridge-educated with a UN background — the policy and credibility layer as UK e-invoicing rules take shape.

AA

Ani Akosa

CO-FOUNDER & CFO

FCCA chartered accountant and Global Finance Director at Arcadis. Brings lived CFO experience at the multi-entity, high-volume mid-market customer NOMOINVOICE serves.

Pre-seed · launching soon

Be first on the network.

NOMOINVOICE is opening its first cohort of mid-market pilots. Join the waitlist for early access, integration previews, and launch updates.