The e-FACT service of the AOC Consortium will eliminate the receipt of invoices via FTP/sFTP from October 1, 2025. Public Administrations (AAPP) will have to adopt the new integration mechanism using REST API to guarantee continuity in the receipt of electronic invoices.
A REST (Representational State Transfer) API is a type of architecture for designing web services that allows communication between systems over the HTTP protocol. It is especially popular because it is lightweight, easy to understand, and scalable. It is an interface that connects applications or services efficiently, using simple web standards.
Who does this change affect?
This change only affects Public Administrations that receive invoices through the e-FACT service via FTP/sFTP . Entities that manage invoice statuses from EACAT will not be affected by this migration.
The affected AAPPs must:
- Implement the integration mechanism via REST API.
- Ensure that your technology providers make the necessary adaptations to abandon FTP/sFTP.
Options available until the deadline
- Receipt of invoices via REST API (mandatory method from October 2025):
- Public administrations can request integration via the REST API by filling out the integration request form at eFACT .
- All technical documentation is available on the AOC Consortium's GitHub.
2. Receipt of invoices via FTP/sFTP (until September 2025):
- Currently available, but this service will stop working on October 1, 2025.
What should Public Administrations do?
- Start integration via REST API:
It is essential to start the process as soon as possible to ensure that the receipt of invoices is not affected. You can now request integration via REST API by filling out the integration request form in e-FACT and sending it via thee-FACT support form with the subject "REST API Migration". Once the request is received, we will provide you with the connection token to carry out the integration tests in the test environment. - Coordinate with the technology provider:
Communicate this change to your technology provider and ensure they use the technical documentation as a guide to implementing the new system. Once testing is complete in the test environment, the final production environment token will be delivered, and the system will be fully operational.
Technical support and documentation
The AOC Consortium puts at your disposal:
- Technical documentation on GitHub.
- Technical support , which will accompany you throughout the process.