When to use bulk export
You're preparing period packages for many clients at once (year-end hand-offs, quarterly VAT batches), and per-client exports one by one add up. Bulk export collapses that into a single request and a single ZIP, structured so each client's file routes cleanly into your downstream workflow.
For the date semantics of the period filter, see period-filtered bulk export. For the client connection itself, see invite your tax advisor (the client-side flow that gives you access).
What you get
One ZIP named advisor_bulk_export_<N>clients.zip, with one subfolder per client and exactly one file in each:
advisor_bulk_export_3clients.zip
├── Acme Ltd_7f3a9c2e/
│ └── invoices.csv
├── Foobar Trading_1b4d5f6a/
│ └── invoices.csv
└── Baz Consulting_5a2b9d8c/
└── invoices.csv
- The folder name is the client's company name (sanitised for filesystem safety) plus the first 8 characters of the client ID, so two clients named "Acme Ltd" never collide.
- The file is
invoices.csvorinvoices.pdf, depending on the format you chose. One format per run; mixed formats mean two runs.
The three formats
- Invoice CSV: the 18-column invoice list: number, dates, vendor, net / VAT rate / VAT / gross, currency plus base-currency amounts at ECB rates, status, and category.
- Posting-batch CSV: a simplified hand-off file for import into accounting software. It carries a payment-evidence column (payment date + masked IBAN of the paying account) and appends a warning list of invoices marked paid without payment evidence. It's a simplified format, so verify with your software's import mapping before relying on it at scale.
- PDF: the printable A4 invoice list per client, with a bold totals row and invoice count.
What is NOT inside
- No receipt images or original documents. The bulk ZIP is invoice lists only. For a client's original files, use the All-Receipts ZIP from that client's Reports tab.
- No XLSX accounting reports. Those are per client too: the Accounting Reports workbook on the client's Reports tab.
The date range
date_from / date_to are optional. When set, they filter by invoice date (the date printed on the invoice, not the upload date) and apply uniformly to every selected client. You can't mix "Client A's Q1 with Client B's Q2" in one run; use two runs. When omitted, the export covers everything. Details and edge cases: period-filtered bulk export.
Caps and behaviour
- Hard cap: 25 clients per request. More than 25 rejects the whole request with the limit stated, so split into batches (25 + 25 + …).
- Synchronous: the ZIP downloads directly in the response. There's no email step and no waiting queue.
- Strict authorisation: every company in the request must be a client connected to you. A single foreign ID fails the entire request, and nothing is silently skipped.
- Fully recorded: each client's export lands in your export history with format, period, and invoice count, and everything is audit-logged.
The per-client alternative
For a single client, the Advisor Period page offers the same three formats as individual export buttons, plus a pre-export checklist (flags, missing vendors/categories) and the export history table. Bulk export is simply the many-clients version of the same generators.
Troubleshooting
A client's file has fewer invoices than expected. Check the date range, which filters by invoice date. A March invoice uploaded in May belongs to Q1.
I need more than 25 clients. Run multiple batches. An async variant for larger books is planned but not shipped.
I got a permission error for the whole request. One of the selected companies isn't (or is no longer) connected to you as a client. Remove it and re-run. The request intentionally fails as a whole rather than skipping.
Related
- Period-filtered bulk export: date-range semantics in depth
- Download all receipts as a ZIP: original files, per client
- Accounting reports as Excel (XLSX): the per-client report workbook
- Invite your tax advisor: how the client connection is created
- Export formats available today: the full export matrix