Invoice in NZD
Bill in New Zealand dollars with 15% GST and an IRD number.
Check a UBL or CII e-invoice against the EN 16931, Peppol and XRechnung business rules.
Or drop an e-invoice XML file here
The E-Invoice Validator checks UBL and CII e-invoices the way a receiver does — well-formed XML first, then the EN 16931 business rules, with Peppol and XRechnung rules added when the file declares them — and explains every failure with the actual figures.
An e-invoice that fails validation is not paid late — it is not received at all. The access point or the buyer’s portal rejects it, often with an error that quotes a rule number and nothing else, and the invoice sits in limbo until someone works out what BR-CO-15 means.
Paste or drop the XML — UBL 2.1 Invoice or CreditNote, or a CII CrossIndustryInvoice from Factur-X or ZUGFeRD — and this checks it the way a receiver would. First that it is well-formed XML, with the line and column of any fault. Then the EN 16931 business rules: mandatory fields, every total reconciled, the VAT breakdown matched against the lines in each category, categories that contradict the parties’ registrations, codes from the right lists. Peppol and XRechnung rules are added automatically when the file declares them.
Every result says what the rule means and what the file actually contains. The invoice is read in your browser — it is never uploaded, which matters for a document full of bank and customer details.
Peppol, XRechnung, Factur-X and ZUGFeRD 2 files.
The line and column of any XML fault.
Every total and VAT breakdown recomputed.
What each rule means and what the file contains.
Parsed and checked in your browser.
UBL or CII XML; the syntax is detected.
Automatic follows the file’s own specification identifier.
Failures, then warnings, each with the actual figures.
Parties, totals and lines as the receiver will read them.
No. The official validation is the CEN and OpenPeppol Schematron. This implements the rules that most often reject real invoices — mandatory terms, arithmetic, VAT categories, code lists, Peppol endpoints and the XRechnung additions — and explains them in plain language. Use both for a new integration.
UBL 2.1 Invoice and CreditNote, and UN/CEFACT CII D16B CrossIndustryInvoice, which covers Peppol BIS, XRechnung, Factur-X, ZUGFeRD 2 and most national CIUS profiles. It recognises ZUGFeRD 1.0 and FatturaPA and says why they are out of scope.
That the invoice total with VAT must equal the total without VAT plus the VAT total. Each rule here is listed with a plain description and the figures that break it.
No. The XML is parsed and checked by JavaScript in your browser.
What people who use the E-Invoice Validator think of it. Reviews come from visitors and are posted as written.
No ratings yet
Yours would be the first.
0 reviews
Newest first
No reviews yet
Be the first to rate the E-Invoice Validator. It takes half a minute and no account.
Write the first reviewBill in New Zealand dollars with 15% GST and an IRD number.
A subscription invoice with the plan, seats, billing period and proration.
Convert invoice PDFs into structured JSON for an API, a database or a pipeline.
Ask for a deposit or advance, with the balance and its trigger stated.
Bill grounds work by visit or project, with plants, materials and waste.
Mark an invoice as past due so it cannot be mistaken for the original.
Clean a list of invoice data: whitespace, duplicates, dates, amounts and names.
A compliant tax invoice with registration numbers, tax breakdown and amount in words.