1
File
Upload a PDF, PNG, JPEG, WebP, or a ZIP of those files. HEIC is not supported.
E-invoicing
File in. Validated electronic invoice out.
A document arrives as a PDF, scan, or photo. Bizalma extracts the data, builds a canonical EN 16931 model, validates it, and returns JSON, UBL XML, a validation report, CSV, and the original file.
Level 1 Level 2
The path
2
Extraction
Automated reading of parties, amounts, dates, and lines from the file.
3
EN 16931 model
A canonical invoice model aligned to the semantic standard.
4
Validation
Checked against EN 16931 and, if selected, Peppol BIS. The report lists each rule that did not pass, with IDs tied to business terms.
5
Exports
Download JSON, UBL XML (the electronic invoice), the validation report, CSV, and the original file.
Ambiguous cases go to you or a supervisor. Review is part of the service, not an add-on.
We do not send documents to Peppol, eAddress, or VID. The service produces files and data; delivery stays with you.
Two output levels
You choose the output level for the organisation. Each document keeps the level in force at upload. A later change applies only to new files.
Level 1
EN 16931 core
The default. The XML conforms to the schema and to EN 16931 business rules. Use it for incoming invoices you import into an accounting system.
Level 2
Peppol BIS dispatchable
Opt-in. The instance additionally conforms to Peppol BIS rules. Reaching this level depends on data that a PDF usually does not contain — the electronic addresses of the parties and a buyer or order reference. We derive what we can. We do not warrant that any document will reach Level 2.
Every processed document includes a validation report stating the level actually reached. JSON, UBL XML, and CSV are available only where the document reached at least EN 16931 core. A document outside the scope of EN 16931 — a cash receipt or a delivery note — receives a verdict of not applicable. That is a valid outcome, not a failure.
Limits and formats
| Limit | Value |
|---|---|
| Maximum size per file | 25 MB |
| Accepted formats | PDF, PNG, JPEG, WebP, ZIP archive (HEIC is not supported) |
| Maximum extracted content per archive | 1 GB |
| Maximum files per upload batch | 500 |
| Maximum documents per export package | 500 |
Processing capacity is shared and rate-limited per organisation. Sustained throughput is not guaranteed.
What stays with you
Delivery
We produce files and data. Sending the electronic invoice through Peppol, eAddress, or VID is yours.
Archive
The service is not an archive. Statutory retention of source documents remains yours.
Legal original
On incoming invoices, the extracted data and the XML are a derived representation. The authoritative version is the source file.
Verification
Extraction can produce errors. You must verify the result before relying on it — in accounting, tax, payment, or onward sending.
Who it is for
Accounting firms
One inbox for every client
Incoming invoices in every format — PDF, scans, photos — into one organisation. Served companies live inside the firm, not as separate logins.
Companies invoicing the public sector
Latvia B2G is already mandatory
When a public-sector buyer needs a structured electronic invoice, we produce the EN 16931 file. You keep issuing PDFs.
Companies with a legacy ERP
Keep the system you have
When a counterparty requires a structured invoice and replacing the ERP is expensive, we produce the file from the PDF you already issue.