Batch processing
Account required. Without signing in, the tile leads to the sign-in page; the page itself sits in the account area and is presented in its interface.
What for. “Upload several e-invoices at once and validate or convert them together. Processing runs in the background; the result is made available as a ZIP.”
- Action — Validate (EN 16931) or Convert
- Target format — evaluated only when converting, and here it knows the nine e-invoice formats only
- Files — several XML files at once
No file: “Please upload at least one XML file.” Too many: “Too many files — at most {n} per batch.”
How many files per run
Section titled “How many files per run”| Plan | Files per run |
|---|---|
| Free | 5 |
| Startup | 10 |
| Team | 25 |
| Business | 50 |
| Enterprise | unlimited — the installation’s hard ceiling still applies |
What applies is always the smaller of two values: the plan limit and the installation’s hard ceiling (default 50).
A status page that refreshes itself every two seconds (“This page refreshes automatically.”):
| Display | Meaning |
|---|---|
| Queued / Processing … / Completed | the state of the run |
| “{x} of {y} processed” + a progress bar | progress |
| {n} valid / {n} failed | after completion |
| a table of file · result · time | per file: when validating, the detected format with Compliant or the error count; when converting, the name of the generated file |
| “Results as ZIP” | only after completion |
What this tool is not
Section titled “What this tool is not”It takes XML, not PDFs and not ERP raw data. For an ERP raw-data export — CSV, XLSX or arbitrary XML — bulk import is the right tool; it knows stored mapping profiles, which a batch does not need.