Skip to main content

Submit e-invoice file (partner)

POST 
/v1/partner/inbound-files

Upload one or more structured e-invoice data files (XML, EDI, CSV, JSON, TXT). optionally together with the supporting attachments that belong to them, such as the human-readable PDF. Each data file is queued for format identification and mapping against the global and customer file formats configured for this tenant; the resulting invoices appear exactly as they would from any other channel.

Use this endpoint when you already emit a standard e-invoicing document (UBL, CII, Factur-X / ZUGFeRD, XRechnung, EDIFACT, or an agreed CSV layout). Use POST /partner/invoices instead when you want to submit invoice data as JSON.

Request is multipart/form-data: inline base64 is not accepted here. Limits: 25 files per request, 50 MB per file.

Files are classified as data (the e-invoice document to be mapped) or attachment (supporting files linked to the resulting invoice). Classification is inferred from the file extension: .xml, .edi, .csv, .json and .txt are treated as data, everything else as attachment. Send the file_kinds field to override that per file.

Responds 202 Accepted: the files are stored and queued. Mapping happens asynchronously, so no invoice token is available yet. Reconcile later using your own document references.

Request​

Responses​

Files accepted and queued for mapping. A Warning header ending in "used default" means the receiving_inbox or external_identifier you sent matched nothing and the default inbox of the customer was used.

Response Headers
    Warning

    Present when a named inbox or identifier matched nothing, e.g. 199 nuntiq "unknown receiving_inbox x@y, used default".