Skip to main content

Send an e-invoice data file with its images

POST 
/v1/inbound-files

Structured invoice files (UBL / Peppol, CII, other XML, JSON, CSV, EDI, TXT) mapped by the tenant's inbound file formats, with attachments (PDF, PNG, JPEG, TIFF) that are linked to the invoices they describe.

Multipart (max 25 files of 50 MB) or JSON with upload_ids from POST /uploads. Types are read from the bytes; other types answer 415.

An attachment is linked to the invoice whose data file names it (the file format maps that name to attachment_reference). The match looks at this sender's attachments not yet linked, sent within 30 days, preferring the data file's own batch, then the closest name, then the newest. An attachment may come in the same call, before the data file or after it (the invoice then waits for its image as the file format's image policy says), so a call with attachments only is accepted. A data file that names no attachment gets a generated PDF, and an attachment nothing names stays unlinked until it expires.

All files are stored, then registered together, then each data file is queued. A queue failure answers 503 queue_failed; send the same request again: only what was not queued is queued (never processed twice). A data file this sender already sent within 24 hours is not queued again (duplicate) unless allow_duplicate=true.

Follow it with GET /inbound-uploads?upload_batch_id=, or the inbound_file.processed webhook. Partners use POST /partner/inbound-files.

Request​

Responses​

Stored and queued