Bulk import and mapping profiles

Bulk import (/en/account/bulk-import) reads a raw-data export — CSV, XLSX or arbitrary XML — and produces a batch of e-invoices from it. Once set up, every further export from the same source system runs through without further effort.

The wizard

Step	What to do
1 · File & target format	upload the file, choose the target format, optionally select a stored mapping profile
1.5 · Choose the row element	with XML only, and only where the choice is not unambiguous: the reader proposes an element and names the alternatives
2 · Map the columns	map header and line-item fields to columns; also the separator, decimal separator, date format and the key column that groups rows into invoices
3 · Start the run	optionally “archive results”; optionally save the mapping as a named profile

The run is queued and processed in the background; the status page (/en/account/bulk-import/status) shows progress and delivers the results as a ZIP.

The key column is the decisive step

A raw-data export typically has one row per invoice line item, not per invoice. The key column says which rows belong to the same invoice — usually the source system’s invoice number.

Mapping profiles

Stored column mappings sit under Mapping profiles (/en/account/mapping-profiles), where they can only be listed and deleted — they are created in the mapping step of the wizard. Profiles belong to the tenant.

Limits

Bulk import is an Enterprise capability

It counts as an ERP integration. On all cloud plans it runs as a complete trial over 10 rows — not as a preview, but as a real run with a real result. The hard ceiling above that, in the Enterprise installation, is 5,000 rows.

Every invoice produced also consumes one unit of the invoice quota; once that is exhausted, the run stops at that point.

The difference from batch processing

	Bulk import	Batch processing
Input	ERP raw data: CSV, XLSX, arbitrary XML	finished e-invoice XML
What happens	invoices are produced	existing ones are validated or converted
Mapping needed	yes, through a mapping profile	no

Where the field mapping is documented in detail

Source types, the row selector, value tables, constants and expressions are described in the REST documentation of the product repository. The ERP-side settings — partner roles, qualifiers, segment definitions — are under ERP settings.