Integration · 2026-11-03
Markdown exportConvert many invoices with a bulk run
Upload PDFs or a ZIP in your profile, check the cost, and start the run. You get one summary mail, correct failed invoices online, and download all files as one ZIP. No programming is needed.
One run for many invoices
Upload many invoice PDFs once, and get one ZIP back. You do not need to send emails or to program anything.
A bulk run fits a batch that you create at fixed times, for example several hundred invoices from a mail merge. It converts every invoice with the same strict validation as External API V1.
Bulk runs are included with every active Enterprise subscription. You find them in your profile, in the Bulk run section.
Run a bulk run
- Open Profile, then Bulk run, and choose the output format. The format is fixed for the run.
- Drop the invoice PDFs, or ZIP files that contain PDFs, into the upload area. The browser unpacks ZIP files. Every other file is skipped and listed.
- Wait until every file is uploaded, then read the cost check.
- Start the run. You can close the page, because the run continues on the server.
- When the run ends, you receive one summary mail. It does not attach the files.
- Open the link in the mail, correct the failed invoices online if necessary, and download the ZIP.
Correct failed invoices online
You only work on the exceptions.
The Bulk run section shows every failed invoice with its reason, and groups the invoices by reason. Many invoices with one reason usually mean one flaw in the template. Then correct the template, and add only those PDFs to a new run.
For a single invoice, choose Review and correct. It opens the review with the extracted data, the PDF and the findings. Nothing is extracted again. When the corrected invoice passes validation, the service issues the file and adds it to the ZIP and the manifest. A correction that still fails costs nothing.
When online correction is not available
An invoice without extracted data cannot be corrected online, for example when the run was cancelled before it started or when credit was missing. Add its PDF to a new run.
What the ZIP holds
results/: one converted file per converted invoice. A ZUGFeRD result is a PDF, every other format is an XML file.manifest.csv: one row per uploaded invoice, with its result, reason and charge.invoices.csv: invoice number, parties and amounts as each converted file states them, so that you can compare them with your source list.totals.csv: totals per currency and document type.
How long files stay
From the end of the run, the converted files, the uploaded PDFs and the review data stay for 7 days. The account receives one reminder a day before the deletion if it has not downloaded the ZIP or if invoices can still be corrected.
You can delete the files earlier with Delete files now in the profile. The run list and the manifest stay. They hold file names, checksums, states and reason codes, but no invoice content.
Limits
| Limit | Value |
|---|---|
| Invoices per run | 1,000 |
| Size per PDF | 20 MB |
| Invoices converted at the same time, per run | 3 |
| Files kept after the run ends | 7 days |
Billing
A bulk run uses the same allowance as External API V1 and Email Import: first the included conversions, then prepaid API credits. The cost check shows the result before the start.
An invoice is charged only when its converted file is released. An invoice that is not converted costs nothing. A corrected invoice costs one unit when its file is issued, and repeating the same request never charges twice.
Choose the channel
| Channel | Best fit | What you need |
|---|---|---|
| Bulk run | Batches at fixed times, for example several hundred invoices from a mail merge. | A browser. No automation. |
| Email Import | Single invoices from a mailbox. An account can send up to 20 import emails per hour. | Verified senders. One reply per email. |
| External API V1 | A steady server-to-server flow. | Your own integration. |
Next steps
Bulk runs need an active Enterprise subscription.