To receive invoices Modality 2- Through the adaptation of your accounting management software, you must send the service registration request form that you will find in EACAT Procedures > provider Consorci AOC, Service CAOC – Request for services > Procedure "Request for registration and modification of AOC services" in order to receive the data. Once you have the registration data, you must follow the technical documentation for integration via sFTP in the e-FACT Hub integration guide .
To receive invoices Method 3- Through a private platform provider of electronic invoice services or accounting software for local bodies, you must send the service registration request form that you will find at EACAT Procedures > provider Consorci AOC, Service CAOC – Request for services > Procedure "Request for registration and modification of AOC services" in order to receive the data. Since the accounting solution you will use is already integrated in eFACT by other entities, with the registration credentials you can already establish the connection.
- Integration request :
In case you are interested in integrating your tools with e-FACT to issue invoices, you can send us the following document through the contact form .
- Integration documentation:
Depending on whether you have to integrate with e-FACT to send invoices or if you integrate to receive invoices, you need to download the corresponding document depending on the type of integration you need to do:
- SENDING INVOICES : You will find the technical documentation for integration via WebService in the space for integrators via WS for suppliers of the eFACT. Once you have integrated into PRE for the service, in order to be able to move to PRODUCTION, you must complete the eFACT homologation tests that you will find at https://consorciaoc.github.io/Homologacio-Serveis/
- RECEIPT OF INVOICES: You will find the technical documentation for integration via sFTP in the e-FACT Hub integration guide .
These changes in the method of joining the e-FACT via the Receiver's Portal on its own platform must be done in coordination with the invoicing manager of each entity and with the technicians of the e-FACT service. This is due to aspects related to the status of the invoices that appear on the receiver's portal and will no longer be able to be managed from this portal. Invoices are either managed from the receiver's portal or through the entities' applications (by integration).
It is necessary that before moving definitively to the management of invoices by the entity's own means, the invoices that are on the receiver's portal, have a final status ("Paid" or "Rejected"). Invoices that are not in these states will be orphaned and .
At any time, from the Receiver's portal, you can download the invoice file, attachments and proof of entry into the register.
To facilitate the transition to the new modality in the entity, the e-FACT service offers the possibility, in cases of own integration, that the integration is first validated in the entity's PRE environment.
It is important that when the request to change mode is made, mark that it is a “ Modification ”, and the date on which you plan to have the system in production (“ Apply modification on the day ”):
Upon receipt of this change request, you will be sent your pre-production environment credentials to perform integration into the pre-production environment, relevant testing, integration validation and invoice/statement management flow.
Once the production date has been “reconfirmed” with the AOC technicians, production credentials will be sent to you to receive invoices in your system. Remember that invoices: are either sent to the receiver's portal or go to the integrated system.
If the recipient of the invoice sends through integration the status change of an invoice to the STATIN folder of the HUB but it is not processed correctly, the extension in the nomenclature of the sent files should be reviewed, since the HUB , does not currently support state changes with the lowercase (xml) extension. In this sense, the extension of the file will need to be informed in this way XML , and the references and names of attached files correspond to those previously sent in order to match those of the HUB.
Likewise, we attach some recommendations regarding the nomenclature of state change files:
Where the receiver_id corresponds to the identifier associated with the AA.PP. recipient of the invoice and originator of the status file in question, and the issuer_id to the identifier of the issuer of the invoice for which the status is being reported. Finally, reference_1 corresponds to a unique identifier associated with the generated file, for tracking purposes within the e-FACT platform.
And in order to associate it with the invoice, within the XML, the hub_id of the invoice, date of the invoice and the CIF indicated on it must be indicated.