XML
UBL, industry schemas, and the variations suppliers build on top of them.
Structured invoices, whatever the format
Suppliers send structured invoices in the format their own system produces. Nuntiq recognises the format, maps it to your fields, and resolves what the file leaves ambiguous. The original is archived exactly as it arrived.
Many formats in. One invoice out.
However the file reaches Nuntiq, the work is the same: recognize what the format is, map it to your fields, and resolve what the format left ambiguous.
EDI
Segment-based messages from established trading relationships.
CSV
Flat exports, one file per invoice or many invoices per file.
JSON
Whatever shape the sending system happens to produce.
Hybrid PDF
Factur-X and ZUGFeRD, with structured data embedded in the document.
Recognized and mapped
Nuntiq identifies the format,
then maps it to your fields.
Ambiguity resolved
Dates, decimals and number formats.
One Invoice
The same fields, whatever the source format was.
- SupplierMeridian Supply BV
- Invoice numberINV-2026-04817
- Invoice date12 May 2026
- CurrencyEUR
- Total17,242.50
- Lines24
- CSV, XML, JSON and EDI files
- Hybrid PDF/A-3 invoices such as Factur-X and ZUGFeRD
- Prebuilt templates for common industry formats
- Per-supplier overrides on top of a shared template
- Automatic format recognition on arrival
Every supplier sends a different file. That is fine.
Structured invoicing was supposed to end the format problem. Instead it produced a dozen standards and a long tail of supplier-specific variations on each one. Nuntiq treats that as the normal state of affairs rather than an exception to be negotiated away.
Common industry formats ship with the platform as ready-made templates. When a supplier deviates, you override the specific fields that differ instead of maintaining a separate copy of the whole mapping, and those overrides survive updates to the underlying template.
For a format nobody has seen before, upload a sample file and Nuntiq proposes the field mapping for review. Your team confirms and adjusts. Nobody writes an XPath from a blank page.
Onboard a supplier before lunch
Give a supplier an account, send the invitation, and they are sending invoices the same afternoon. No project plan, no credentials pasted into an email.
Suppliers rotate their own keys, Nuntiq reminds them before anything expires, and every file stays tied to the account that sent it. Tight for audit. Quiet for AP and IT.
- Live in minutes, not weeks or months
- Credentials shared securely
- Supplier self-service key rotation
- Every file traced to its sender
The invoice date is right
Ambiguous and unusual date formats are resolved on the way in, so the date stored against the invoice is the date the supplier meant.
Everything downstream follows
Payment terms, discount windows, ageing and period reporting all depend on that one field being correct.
Nothing to set up per supplier
Onboarding never starts with a conversation about date formats, and you can still set one explicitly when you want to.
No date format left ambiguous
Slash dates, written dates, unusual layouts: the same numbers can mean two different things and the file does not say which. Read one the wrong way and the invoice date is off by months, which quietly moves every date derived from it.
Nuntiq resolves the invoice date automatically, from the evidence on the document rather than from a setting somebody remembered to fill in.
The file you received is the file we keep
Every inbound file is stored exactly as it arrived and cannot be modified or deleted afterwards, for as long as your retention policy requires. Structured invoices are read, not rewritten, so any value in the system can be traced back to the byte that produced it. When a supplier disputes what they sent, the original settles it.