How to integrate with e-FACT to receive invoices?

To receive invoices Method 2 - By adapting 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 eFACT Hub integration guide .

To receive invoices Modality 3- Through a private platform provider of electronic invoice services or accounting software for local bodies, you must submit 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.

How to integrate with e-FACT to issue invoices?
  • Integration request :

If 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:

Once you have requested registration to e-FACT, you will be notified of a series of data to be able to access the different environments and integrate. Here you will find the guide and other documents to carry out the integration:

Documentation in Catalan:

Documentation in Spanish:

How to change from the receiver's portal modality to own information systems?

These changes in the method of joining e-FACT via the Receiver's portal to their own platform must be done in coordination with the invoicing manager of each entity. This is due to aspects related to the status of the invoices that appear on the receiver's portal and which will no longer be able to be managed from this portal because it will go into a custody-only mode (without being able to effect any change of status or the invoices entered before the change or the new ones) . This is why from this custody portal you can only download the invoices, but not manage their statuses and they will remain in the last status they had before the change of modality. As a general rule and to cover the duties of the entity as receiver of the invoice, it will have to communicate the status changes of the invoices that have remained unmanaged before the change of modality, by other means that other than through e-FACT . For example, contacting the issuer of the invoice by email or phone.

To facilitate the transition to the new modality in the entity, the e-FACT service offers the possibility, in cases of self-integration, that the PRE environment of the entity in question is first changed to the new modality and validate there that the new operating configuration is operational.

The request for the PRE environment must be prior to the request to change the mode of joining the service and must be done by sending the pre-production platform membership form through from the contact form on this portal.

This change to pre-production will allow us to perform the relevant tests to be able to integrate correctly without compromising the production configuration. This different configuration of pre-production and production is recommended for a period of duration not exceeding three months.

Once the tests have been completed, in order to change the method of joining e-FACT to PRO, you will need to send us the service registration and modification form through EACAT, indicating "Modality 2: through of the entity's own information systems".

Why doesn't the status change XML sent to the HUB make the change?

If the recipient of the invoice sends through integration the status change of an invoice to the HUB's STATIN folder 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.

Also, we attach some recommendations regarding the nomenclature of the status change files:

<receiver_id>@<sender_id>@<reference_1>< strong=""></receiver_id>@<sender_id>@<reference_1><>

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.