E-Invoice Formats
TaprNext automatically detects and processes structured electronic invoice formats.
Format Detection
Section titled “Format Detection”The system follows a detection flow based on file type:
- PDF files: Checked for embedded XML (ZUGFeRD/Factur-X)
- XML files: Processed as plain or structured formats
- Images: Processed via AI OCR
Supported Formats
Section titled “Supported Formats”ZUGFeRD / Factur-X
Section titled “ZUGFeRD / Factur-X”PDF with embedded XML for Germany, Austria, and France. Versions 2.1.1 and 2.2 supported. Achieves 100% accuracy through structured data extraction.
XRechnung
Section titled “XRechnung”Pure XML format for German B2G and B2B invoicing. Versions 2.x and 3.x supported. Delivers 100% accuracy with structured data.
PEPPOL BIS
Section titled “PEPPOL BIS”UBL-based EU-wide format (version 3.0). Processes with 100% accuracy through structured extraction.
OASIS standard international format (version 2.1). Achieves 100% accuracy with structured data.
Which format is sent
Section titled “Which format is sent”If you do not pick a document format, Tapr sends Peppol BIS Billing 3.0 UBL whenever the receiver accepts it. That remains the default when the receiver also advertises a national profile such as XRechnung or a French CIUS. A national profile, or the France Factur-X hybrid, is used only when you select it on the invoice. Any other Factur-X hybrid document type is refused.
Sending a Factur-X PDF as plain UBL or CII
Section titled “Sending a Factur-X PDF as plain UBL or CII”When a Factur-X / ZUGFeRD PDF is uploaded on the AR side and the send stays on plain UBL or CII (the usual case, including the BIS 3.0 default), Tapr converts the embedded XML and attaches the original PDF to the converted XML as an additional document reference, so the customer still gets your PDF. If that source PDF cannot be read, the send fails rather than going out without it.
Selecting the France Factur-X document type forwards the uploaded PDF as the hybrid instead of converting it.
Country-specific rules
Section titled “Country-specific rules”Tapr validates against the PEPPOL rule set for the document type you send, and maps validator errors to the invoice field to fix.
French e-invoicing (CTC) terms are included only when that document type is selected. The invoice then needs a Business Process Code (BT-23, in the Sending section) and the coded notes those rules require (for example payment notes) on the Notes tab. On Peppol BIS 3.0 a Business Process Code blocks the send, and more than one document-level note is rejected unless both the seller and the buyer are German.
When the selected format is XRechnung, send also requires Buyer Reference (the Leitweg-ID), Payment IBAN, and the seller contact name, phone, and email. Invoice Manager requires Buyer Reference when you save edits to a sales invoice. Invoices created by New Invoice, Upload, AR Email, ERP fetch, SFTP or API can arrive without it, so check it before sending.
Extraction Comparison
Section titled “Extraction Comparison”| Format | Accuracy | Speed | Data Quality |
|---|---|---|---|
| ZUGFeRD | 100% | <1 sec | Full structured |
| XRechnung | 100% | <1 sec | Full structured |
| PEPPOL BIS | 100% | <1 sec | Full structured |
| UBL | 100% | <1 sec | Full structured |
| Plain PDF | 90-98% | 3-10 sec | AI interpretation |
| Scanned PDF | 85-95% | 5-15 sec | OCR + AI |
| Image | 80-92% | 5-15 sec | OCR + AI |
E-Invoice Benefits
Section titled “E-Invoice Benefits”For receivers: Structured formats eliminate AI errors, enable instant processing, populate all fields completely, and provide format compliance validation.
Encouraging Vendor Adoption
Section titled “Encouraging Vendor Adoption”Share your PEPPOL participant ID and accepted formats list with vendors to encourage electronic invoicing adoption.