How is submitted content validated?
File checks; when you submit files, we automatically verify:
- File type: does the file match the expected type?
- XML/UBL: for UBL files, we check compliance with UBL 2.1 and, where applicable, PEPPOL rules.
- Structure and encoding: is the file readable, complete and correctly encoded?
Monitoring statusses (input collection):
STATUS | DESCRIPTION |
Pending | The file has been received and is awaiting the start of preprocessing |
Unpacking | The system is currently decompressing or extracting the contents of the compressed file (ZIP). These statuses apply exclusively to SFTP-based workflows when the input file is a compressed archive (e.g., .ZIP) |
Unpacked | The archive has been successfully unpacked. These statuses apply exclusively to SFTP-based workflows when the input file is a compressed archive (e.g., .ZIP) |
Splitting | The file is being divided into multiple parts based on predefined rules. These statuses apply exclusively to SFTP-based workflows where multiple documents are included within a single input file (e.g., a |
Splitted | Splitting is complete; all parts are ready for further processing. These statuses apply exclusively to SFTP-based workflows where multiple documents are included within a single input file (e.g., a .CSV or .XML containing data for several documents) |
Extracting | The data is being extracted from the file for transformation. |
Extracted | The data extraction is complete and validated. |
Converting | The extracted data is being converted to a target format. |
Converted | Data conversion is complete and ready for scheduling. |
Failed | The preprocessing step encountered an error and cannot proceed. |
If a file isn’t technically compliant
It is rejected. You’ll see a clear error in the API and in the Customer Portal so you know exactly what to correct. This ensures only valid files continue, reducing downstream issues. You also receive prompt feedback whenever problems occur.
How errors are presented
- Clearly flagged in the front end at document or file level (badges/status indicators).
- Detailed in the event history, including technical error codes and human-readable messages.
- Available via API and webhooks for integration with your back-end systems.
- Exportable as feedback files for automated reconciliation and handling.
This helps you quickly see why a file was rejected or delayed and what to do next.