This section describes the enumerated types used throughout the invoice request and response documents. The UBL standard does not define enum types as part of its standard. Therefore, we use defined enums where possible, based on publicly used standards, extending these standards with our custom values only when necessary.
Batch file status code
This enumerated type provides further clarification for the response file
error handling for the
<ApplicationResponseBatch>/<FileStatus>.
| Status Code | Description | Expected Actions |
|---|---|---|
| S | No issue, file processed | Success |
| E | File processing error (Decryption error, can't open file) | Manual Intervention |
| D | Duplicate file | No action needed |
Status reason code
This enumerated type provides further clarification for the cbc:StatusReasonCode
field. We use a combination of the Status Reason codes
and Status Clarification Reason codes
from Peppol BIS 3.0 standard,
supplemented with our own definitions where necessary.
| Status Reason Code | Description | Expected Actions (Entity Specific) |
|---|---|---|
| NON | No issue | Success |
| REF | Incorrect References (incorrect or missing buyer tax information) | Failure + Revise/Rebill |
| TER | Past time constraint to process the invoice. Note: Google extension | Failure + Revise/Rebill |
| SVE | Invoice Request Syntax Violation, Invalid format, missing information | Manual Intervention |
| CER | Communication/Transient Error - vendor will retry the request. Note: Google extension | Wait & See |
| OTH | Reason for status is not defined by code | Manual Intervention |
| PEN | Invoice generation pending. Note: Google extension | Wait & See |
| COM | Permanent Communication Failure - vendor will NOT retry the request. Note: Google extension | Manual Intervention |
| REJ | Backend system rejection, fatal | Manual Intervention |