E-Invoice Reader - XRechnung, ZUGFeRD & Factur-X to JSON
Pricing
from $5.00 / 1,000 invoice reads
E-Invoice Reader - XRechnung, ZUGFeRD & Factur-X to JSON
Read XRechnung (UBL or CII), ZUGFeRD and Factur-X invoices by URL and get clean JSON: parties, VAT ids, dates, totals, tax per rate, line items, IBAN, plus arithmetic checks. $5 per 1,000 invoices; non-invoices are free.
Pricing
from $5.00 / 1,000 invoice reads
Rating
0.0
(0)
Developer
Forge Creations
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
7 days ago
Last modified
Categories
Security
Limited permissionsShare
E-Invoice Reader: XRechnung, ZUGFeRD & Factur-X to JSON
Paste links to electronic invoices. You get one clean JSON record per invoice, the same shape whatever the format:
- Formats: XRechnung (UBL 2.1 and UN/CEFACT CII), ZUGFeRD 2.x, Factur-X (the XML inside the PDF/A-3 is read), ZUGFeRD 1.0, PEPPOL BIS Billing 3.0 and other EN 16931 UBL invoices
- Fields: profile, invoice number, type (invoice, credit note, corrected invoice...), issue / due / delivery dates, currency, buyer reference (Leitweg-ID), order reference, seller and buyer (name, VAT id, tax number, address, email), totals, tax per rate, line items, IBAN / BIC / payment reference and terms, notes
- Checks: line amounts vs line total, net = lines - allowances + charges, tax per rate, gross = net + tax, amount due, required fields. Each check says what it compared.
Germany requires every business to be able to receive e-invoices since 2025, and issuing becomes mandatory step by step through 2028. France follows from 2026. This tool turns those files into data your bookkeeping, n8n, Make or Zapier flow can use.
Pricing
| What | Price |
|---|---|
| Invoice read | $0.005 ($5 per 1,000 invoices) |
| Apify start fee | $0.00005 per run |
PDFs without an embedded invoice, other XML, unreadable files and failed downloads are not charged. Set a maximum charge in run options to cap spending.
Input
| Field | Default | Notes |
|---|---|---|
| fileUrls | required | Links to .xml or .pdf invoices, 30 MB max each |
| includeLineItems | true | Turn off for headers and totals only |
Output (one row per file)
source_url, status, file_type, embedded_xml, syntax, profile, profile_id, invoice_number, type_code, type, issue_date, due_date, delivery_date, currency, buyer_reference, order_reference, seller, buyer, totals, tax_breakdown, lines, payment, notes, checks, checks_passed, checks_note
status is ok, or one of no_einvoice_xml, unsupported_format, unsupported_file, unreadable, download_failed (all free).
Limits
- The checks are arithmetic and presence checks. They are not a full EN 16931 / XRechnung Schematron validation; use the official validator when you need legal conformance.
- Plain PDF invoices without embedded XML are not read. For those, use PDF & Image to Text and PDF Tables to CSV & JSON from the same developer.
- Italian FatturaPA and pre-2014 ZUGFeRD drafts are reported as unsupported.
- XML is parsed with external entities and network access disabled.
Support
Open an issue on the Issues tab with a sample file (remove personal data) and the run ID.