Your accounting system does not talk to the FTA. It talks to your ASP, usually over a REST application programming interface (API) or a file drop. The ASP handles the Peppol side: AS4 transport, the network address lookup, and the certificates that sign each message.
Alongside the invoice, the ASP builds and sends a
Tax Data Document (TDD) — a separate XML report that carries the tax data extracted from the invoice to the FTA. Both the sender's and the receiver's providers file one. Version 1.0.4 of the
TDD specification became mandatory for service providers on 4 August 2026, with tighter validation rules than earlier releases.
Your side of the integration is usually the same list: export invoices with all 51 fields populated, store a Peppol identifier against every business customer, map your product and tax codes to the PINT AE code lists, keep credit notes referencing the original invoice, and read the Message Level Responses so a rejected invoice does not sit unnoticed for a month.