Appendix 4 - AdE errors file specifications
This chapter describes the file returned from AdE containing the errors.
The naming convention of the file is as follows:
[filetype].[sender_code].[acquirer_code].[date].[uuid].csv
in particular:
field | format | notes |
filetype | Alphanumeric - 5 char | fixed value "ADEACK" |
sender_code | Alphanumeric - 5 char | sender ABI code or PagoPA 5 char assigned code (if ABI not available) |
acquirer_code | Alphanumeric, max 255 char | ABI code or fiscal code of the acquiring subject |
date | YYYY-MM-DD | file creation date |
uuid | UUID v4 | random uuid which grants file name uniqueness |
Fields in the AdE error file
Field | Type | Notes |
merchant_id | Alphanumeric, max 255 char | Unique identifier of the physical store of the Acquirer |
terminal_id | Alphanumeric - max 255 char | Identification of the Merchant's terminal/POS |
fiscal_code | Alphanumeric - min 11 max16 char | Fiscal code for legal person and for natural person (self-employed workers). |
acquirer_id | Alphanumeric - max 255 char | Unique Acquirer ID. In the case of card transactions, it represents the homonymous value conveyed on the international circuits. |
outcome | Numeric - 1 char | Elaboration outcome: 1 – Fiscal Code error * 2 – Multiple error 3 – Fiscal Code warning 4 – Other warnings |
error_list | Alphanumeric - max 255 char | It consists of a list of strings separated by "|", the single string is formed by the concatenation between the reference of the "Field number" and the type of report shown in the "Type of error" or "Type of warning" tables |
* In case of error the aggregate is not ingested by Agenzia delle Entrate.
Warnings do not block record ingestion by Agenzia delle Entrate.
Type of error table
The error reported for 1 – Fiscal Code error outcome.
| Error code | Description | Error Mitigation |
|---|---|---|
06 | Fiscal Code not existing | Retrieve the correct fiscal code from merchant and fix sender data base. You can check the faq. |
07 | Fiscal Code not valid , no longer usable because updated in other fiscal code | Retrieve the correct fiscal code from merchant and fix sender data base. You can check the faq. |
The error reported for 2 – Multiple error outcome.
Records discarded due to errors on multiple fields. This is provided when one or more of the errors listed above occurs, except the one on the fiscal code’s check. All detected errors are reported in the detail string divided by the character “|”.
Type of warning table
In case of existing Fiscal Code there could be non-blocking warnings on the merchants data.
| Report code | Description | Error Mitigation |
|---|---|---|
01 | Fiscal Code existing but not valid on the date of the operation (for physical subjects, is the case of the deceased; for different subjects from the physical subjects, it is the case of the extinct subject) | Retrieve the correct data and fix sender data base and send the new data at the next transmission |
02 | Not existing VAT | Verify the data, you can check by online service |
03 | VAT ceased on the date of the operation | Verify the data, you can check by online service |
04 | VAT and Fiscal Code are not coherent | Verify the data, you can check by online service |
Example of AdE error file
Information in AdE error file is in clear text and refers to the one originally sent with the Batch Service.
Last updated