Document
Invoice identity
- ID
- Kind
- Type code
- Issue date
- Due date
- Currency
Peppol · EN 16931 · UBL · OIOUBL · Finvoice
E-invoice XML viewer & checker
Open an e-invoice XML file or paste the XML text to read the invoice in a clearer view and run InvoiceCraftly’s current preflight checks. Inspect seller and buyer details, line items, VAT, totals and payment information for supported Peppol BIS Billing 3, OIOUBL 3 and Finvoice 3.0 invoices.
Use the same page when you need a Peppol invoice checker, a UBL invoice viewer, or help understanding why an e-invoice may need review. The result separates the checks InvoiceCraftly actually ran from formal EN 16931 or Peppol validation layers that have not run.
- Choose an XML file or paste the XML text.
- See the recognized e-invoice format and mapped invoice details.
- Review deterministic preflight findings and the validation layers that were or were not checked.
E-invoice XML
Open a file or paste XML
Invoice details
Invoice details found in the XML
Review the fields InvoiceCraftly can read from the recognized structure before looking at the preflight result.
Seller
Supplier details
- Name
- Business identifier
- Tax/VAT ID
Buyer
Customer details
- Name
- Business identifier
- Tax/VAT ID
Totals
Mapped amounts
- Line net
- Net
- Tax
- Gross
- Payable
Payment
Mapped payment fields
- Payment means
- Instruction ID
- Reference
- Account
- Account name
- BIC
Line items
Mapped invoice lines
E-invoice preflight
Check the invoice before you resend it
InvoiceCraftly runs bounded deterministic checks over the mapped invoice details and shows other validation layers separately.
Findings
Optional next step
Create a new editable invoice draft
For supported simple outgoing invoices, review the mapped fields and create a new editable InvoiceCraftly draft with a new invoice number. The source XML stays unchanged.
Included in the draft
Review separately
Review note
Draft creation isn’t available for this XML
You can still review the mapped fields and preflight findings. Draft creation stays unavailable when the editor cannot preserve important source meaning safely.
Peppol invoice checker
Check Peppol BIS Billing 3 XML
For supported Peppol BIS Billing 3 UBL invoices, InvoiceCraftly identifies the profile, shows mapped invoice details and runs its current preflight over mapped fields and arithmetic. Official Peppol business rules are shown separately if they have not run.
EN 16931
Understand the difference between preflight and formal validation
EN 16931 validation can include business rules and code lists beyond the checks on this page. A clear InvoiceCraftly preflight means the checks shown here found no issue; it does not turn an unrun formal validation layer into a pass.
UBL · OIOUBL · Finvoice
Inspect supported structured invoice formats
The viewer maps supported Peppol BIS Billing 3 UBL, OIOUBL 3 Invoice/CreditNote and Finvoice 3.0 structures. Generic UBL can also be recognized at a basic structure level even when a profile is not classified.
Rejected e-invoice
Why an e-invoice can be rejected
An e-invoice can fail for different reasons: malformed XML, missing or inconsistent invoice data, EN 16931 or Peppol business rules, code-list requirements, recipient identifiers, or delivery-network checks. This page helps with the parts InvoiceCraftly can currently prove from the uploaded XML and makes the unrun layers visible instead of guessing.
If the invoice is for Norway, you can also check whether a recipient can be found for EHF/Peppol routing. Recipient capability is separate from the invoice XML itself.
XML safety
The file is screened before invoice fields are read
The XML input is screened before mapping invoice fields. See Security for the safeguards and Privacy for how invoice data is handled.
Evidence
Only checked layers are reported as checked
The result distinguishes XML parsing, structure recognition, InvoiceCraftly preflight, formal Peppol business rules and network or recipient acceptance.
Next step
Use supported invoice details as a draft
For a simple supported outgoing invoice, you can review the mapped fields and open them as a new editable InvoiceCraftly draft. Complex source meaning is not silently discarded.
Peppol, EN 16931 and e-invoice XML FAQ
Can I check a Peppol invoice XML file?
Yes. The tool can recognize supported Peppol BIS Billing 3 UBL invoices, show mapped invoice details, and run InvoiceCraftly’s current deterministic preflight checks. It separately states when official Peppol business rules were not run.
Is this a complete EN 16931 validator?
Not yet. The page covers format recognition, mapped fields and bounded deterministic preflight. It does not claim complete EN 16931 Schematron, code-list, recipient or network validation unless those layers explicitly say they ran.
Can I use it as a UBL invoice checker?
The tool recognizes supported UBL invoice structures, including Peppol BIS Billing 3 and OIOUBL 3, and can show the fields InvoiceCraftly knows how to map. Generic UBL can be recognized at a basic structure level even when a specific profile is not classified.
Why was my e-invoice rejected?
A rejection can come from XML structure, business rules, code lists, recipient requirements or network delivery. InvoiceCraftly can explain issues that its current preflight can prove from the mapped file, while other validation layers remain clearly marked as not run or not checked.
Which e-invoice formats can InvoiceCraftly read?
The current viewer maps supported Peppol BIS Billing 3 UBL, OIOUBL 3 Invoice and CreditNote, and Finvoice 3.0 structures. Other UBL documents can sometimes be recognized without full semantic mapping.
Can InvoiceCraftly fix the XML?
This consolidated viewer and checker explains current findings and can create an editable draft from supported simple outgoing invoices. Corrected XML download remains a later step because fixes must preserve invoice meaning and be validated again.