Centro stella dei pagamenti elettronici
  • Centro Stella
    • Instructions for Agenzia delle Entrate Mandate
      • How to join
        • 01. Sign the Agreement
        • 02. Integrate PagoPA Environments
          • Open routes
          • Request the mutual authentication certificates
          • Obtain an API key
          • Wait for activation email
          • Check if you are enabled for PagoPA UAT environment
        • 03. Configure the Batch Service
          • Prepare the Java KeyStore
          • Install the software
            • How to install JAR version
              • Download JAR file
              • Prepare the working directories
              • Define environment variables
            • How to install Docker version
              • Download Docker image
              • Define environment variables
              • Choose working directory to mount
          • Run the software
            • Run from JAR
            • Run with Docker
        • 04. Test and monitor integration
          • Test UAT
          • Test PROD
        • 05. Go live!
      • Releases / Changelog
        • Note regarding the modifications from 2.2.0 to 2.2.3
        • Note regarding the modifications from 2.1.2 to 2.2.0
        • Note regarding the modifications of the yaml file from 2.0.0 to 2.1.0
        • Note regarding the modifications of the yaml file from 1.5.1 to 2.0.0
        • Note regarding the modifications of the yaml file from 1.4.1 to 1.5.0
        • Note regarding the modifications of the yaml file from 1.3.2 to 1.4.1
        • Note regarding the modifications of the yaml file from 1.2.5 to 1.3.2
      • Appendixes
        • Appendix 1 - Environments
        • Appendix 2 - Input file specifications
        • Appendix 3 - AdE output file specifications
          • Appendix 3 - AdE output file specifications v1.2.5
        • Appendix 4 - AdE errors file specifications
        • Appendix 5 - Logback configuration
        • Appendix 6 - Configuration properties
        • Appendix 7 - Console log overview
        • Appendix 8 - Database connection for Spring Batch
        • Appendix 9 - FAQ & Troubleshooting
        • Appendix 10 - Python and Poetry installation
        • Appendix 11 - List of output and log files
      • Api Integration
  • Glossary
  • RTD documentation
    • Input file specifications
Powered by GitBook
On this page
  • Fields in the AdE error file
  • Example of AdE error file
  1. Centro Stella
  2. Instructions for Agenzia delle Entrate Mandate
  3. Appendixes

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

07

Fiscal Code not valid , no longer usable because updated in other fiscal code

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

03

VAT ceased on the date of the operation

04

VAT and Fiscal Code are not coherent

Example of AdE error file

merchantid12345;terminalid12345;CF00000000000000;99999;1;1206
merchantid67890;terminalid67890;CF00000000000001;99999;4;1302|1304
merchantid65748;terminalid65748;CF00000000000002;99999;3;1201
merchantid09213;terminalid09213;CF00000000000003;99999;1;1206

Information in AdE error file is in clear text and refers to the one originally sent with the Batch Service.

PreviousAppendix 3 - AdE output file specifications v1.2.5NextAppendix 5 - Logback configuration

Last updated 2 years ago

Retrieve the correct fiscal code from merchant and fix sender data base. You can check the .

Retrieve the correct fiscal code from merchant and fix sender data base. You can check the .

Verify the data, you can check by online

Verify the data, you can check by online

Verify the data, you can check by online

service
service
service
faq
faq