Skip to main content

Violations

A violation identifies a problem that stops a document. Retrieve it with GET /transfer-documents/{id}. The response includes a violations array, empty when no problems were found.

Problems found while reading a file or converting a CSV are reported on the uploaded file, and Transfer does not send the failed file or row. Other rows can continue processing.

The violation object​

{
"code": "INPUT_FIELD_MISSING",
"field": "split_payment",
"value": null,
"message": "Input field \"split_payment\" not found in the header",
"context": {"row": 2},
"occurred_at": "2026-05-05T15:30:07+00:00"
}
FieldMeaning
codeA stable identifier you can use in your application. See Codes.
fieldThe affected input field or XML element, when applicable.
valueThe value that caused the problem, when applicable.
messageA human-readable explanation, in English.
contextAdditional details, such as the CSV row number or expected format.
occurred_atWhen the problem was found, in UTC.

For CSV files, context.row identifies the affected row. The header is row 1; data starts at row 2. For multi-line invoices, it identifies the invoice's first row.

Where violations land​

Violations appear on different documents depending on where processing failed:

  1. Parsing: file-level problems, such as separator, encoding, or size, stop the uploaded file.
  2. Mapping: conversion problems are reported on the uploaded file, with one violation per failed row. That row is not sent.
  3. Transmission: a destination rejection stops the invoice's document and includes the details returned by the destination.

To include parsing and mapping failures, query all documents:

What you wantRoute
Everything that failed, including your filesGET /transfer-documents?status=failed
Only what the destination refusedGET /target-documents?status=failed
The violations of one documentGET /transfer-documents/{id}

See Tracking via API.

Codes​

Use the code to identify the problem and the English message for details about the affected field or value.

CodeStepWhen it happensWhat to do
CSV_EMPTYParsingThe CSV file is empty. A file with only a header does not raise this code.Upload a file with a header and at least one data row.
CSV_ENCODINGParsingThe file cannot be read as UTF-8, and the automatic conversion could not repair it.Save the file as UTF-8 and upload it again.
CSV_CONFIG_NOT_FOUNDParsingYour account has no CSV configuration.Contact A-Cube to check your account configuration.
CSV_PARSE_ERRORParsingRows have different column counts, or quoting or escaping is invalid.Check the separator, quotes, escape character, and column count in every row.
CSV_SEPARATOR_MISMATCHParsingThe separator in the file is not the one the format expects. The message names the detected and the expected separator.Use the separator of your destination's format.
CSV_SIZE_EXCEEDEDParsingThe file has more than 500 data rows, blank rows excluded.Split the file into files of at most 500 rows.
CSV_E2E_ID_INVALIDParsingYour CSV has an End-to-end ID column, and the column is missing, an invoice has no value, a value is not valid, or two invoices of the file share a value. Transfer sends none of the file's invoices.Correct the End-to-end ID column and upload the file again.
FILE_FORMAT_UNSUPPORTEDParsingTransfer does not accept files of this format for your destination, for example a .txt file. The upload ends failed, or partial when other files of the same upload were sent.Upload the file in one of the formats of your destination.
ZIP_INVALIDParsingTransfer cannot open the ZIP archive, for example because it is damaged. No file of the archive is processed, and the upload ends failed.Create the archive again and upload it.
ZIP_INDEX_INVALIDParsingYour account expects an index.csv in each ZIP archive, and it is missing or invalid, for example two rows with the same e2e_id. The message names the problem. No file of the archive is sent, and the upload ends failed.Correct index.csv and upload the archive again.
INPUT_FIELD_MISSINGMappingA required CSV column or UBL element is missing. The message identifies it.Add the column with its exact name, or add the missing element.
INPUT_DATE_FORMATMappingA date does not match the format of the destination. The message states the expected format.Use the date format of your destination's format.
INPUT_VALUE_NOT_ALLOWEDMappingA value is outside the allowed set. The message lists the allowed values.Use one of the allowed values.
INPUT_VALUE_NEGATIVEMappingA unit price or a line amount is negative in a UBL document.Correct the amounts: prices and totals of a line must be zero or positive.
MAPPING_VALIDATIONMappingA required input field is empty or missing. The message names the field.Fill the field.
OUTPUT_SIZE_EXCEEDEDMappingThe generated document exceeds the destination's size limit.Reduce the number of lines or the attachment size.
PROCESSING_ERRORMappingThe conversion failed without a more specific code.Read the message, and contact A-Cube if it is not actionable.
VALIDATION_ERRORTransmissionThe destination rejected the fiscal data or XML structure.Correct the field named in each entry and upload the document again.
FIELDS_MISSINGTransmissionAn element the destination requires is not in the XML. The message names it.Add the missing element to the XML.
FILE_TOO_LARGETransmissionThe XML is over the size limit of the destination, listed on its destination page.Reduce the size of the document, or remove its embedded attachments.
DOCTYPE_UNSUPPORTEDTransmissionThe destination does not accept the document type of the file (Peppol).Check the document type and upload the file again.
TRANSMISSION_ERRORTransmissionA-Cube's service for the destination could not be reached or gave no usable answer (Peppol).Upload the file again later, and contact A-Cube if it happens again.
UNSPECIFIED_ERRORTransmissionTransfer received a processing error without usable details.Read the message and contact A-Cube if you cannot resolve it.
INTERNAL_ERRORTransmissionA-Cube's service for the destination reported an internal problem, or Transfer met an unexpected error (Peppol).Upload the file again and contact A-Cube if it happens again.
E2E_ID_ALREADY_USEDTransmissionAnother of your documents already has this End-to-end ID, so Transfer did not send this one. context.e2e_id holds the ID. The document that owns the ID is not affected.Check the document that owns the ID. To send a new invoice, give it a new End-to-end ID.

Rejections after Transfer​

Violations describe failures before the destination receives the document. A later rejection by the destination, such as SdI, adds no violation and leaves the document transmitted. See Outcome after Transfer.

Resending the failed rows​

Correct the failed rows and upload a new CSV containing only the failed invoices. Resending the whole file can transmit successful invoices twice.

Name the new file so that the duplicate check of your destination does not skip it.