TDD
Note: Support for TDD is currently only available on the testing environment. The planned release date for production is December 10
What is TDD
TDD is short for Tax Data Document, it’s a (partial) copy of an invoice or creditnote that is sent to a tax authority for VAT purposes.
Important: as of this time, automatic TDD submission is only supported for Slovakian Domestic transactions.
The official Peppol documentation for SK-TDD can be found here: Slovak Republic Tax Data Document. Additional information about the architecture and surrounding processes can also be found in the Peppol Slovakia Solution Architecture document.
Note: the current official publications are at version 1.0.0 for the TDD document and 1.2 for the architecture. Our implementation follows the upcoming 1.1.0 and 1.2.1 versions of these documents.
The TDD process in ion-AP
Automatic TDD submission
By default, ion-AP automatically performs TDD creation and submission for Slovakian domestic transactions, unless specifically disabled for an organization (see the section on manual submission).
When an invoice, creditnote, or self-billed invoice or creditnote is sent, both sender and receiver are Slovakian organizations (based on their country code), and the supplier is tax-registered (i.e. there is VAT information in the invoice), a TaxData document is automatically created and sent to the Slovakian Tax Authority (C5/C6).
TDD Documents can have multiple types; Submit (S), Resubmit (R), and Disregard (D).
By default, generated TDD Documents have type code S. However, since it is possible that an invoice with the same invoice ID is sent multiple times (usually on the request of a receiving end-user, for instance if they did not process the initial invoice correctly), ion-AP does check whether the original invoice number is unique. If not, the generated TDD’s typecode is R instead of S.
Disregard TDD documents (D) are not created automatically. You can however request that a Disregard update is sent, through the web interface or API, should this be necessary.
You can also manually request that a TDD is sent again. In that case, the new TDD will also have type code R (Resubmit). In theory this should not be necessary, unless C5 reported an issue with the original TDD.
Given the current regulations, the scope for automatic TDD documents is currently always D (Domestic).
As per the most current specification, TDD documents are only applicable to send transactions. ion-AP’s receive transaction API has support for TDD as well, but there is currently no use-case where TDD submission on receive transactions are relevant. If this changes in the future the handling will be updated.
Manual TDD Submission
You can disable automatic TDD submission for an organization in the organization details configuration page, or through the API using the disable_automatic_tdd boolean value.
When disabled, TDD documents are not automatically created, but you take responsibility for sending them yourself. Please refer to the main TDD architecture and document specification on how to do this.
To submit a TDD document manually, you can use the standard send_document API endpoint, or the Send Document web UI page.
ion-AP will automatically match the submitted TDD to a send transaction, by matching the invoice ID and invoice UUID to that in the TDD. If there are multiple potential matches, the TDD will be attached to the most recent transaction.
Standalone TDD Submissions
In order to send a TDD document without a corresponding Send Transaction (for instance when the invoice itself is sent through other means), you must create and send the TDD document yourself, and add the query parameter standalone_tdd=1 to the send_document API call.
Since there is no main transaction to connect the TDD transaction to, the TDD transaction will be treated, and visible as, a standard document send transaction in the API and interface.
Viewing and updating TDD Status
Web interface
Like MLS transactions, TDD transactions are considered ‘child transactions’ of a main transaction in the API and web interface. You can request full details about TDD transactions directly, but they are not shown in the send-transactions overview.
For transactions where a TDD has been submitted, the details page shows a summary overview of the corresponding TDD Transaction(s).
If a send transaction has multiple TDD transactions, they are all shown in this view.
The view shows their type code, when they were sent, their send status, and the MLS response from C5. You can request full details about the TDD transaction by clicking ‘view transaction’ in the overview.
If you for any reason need to resubmit the same TDD, or send a Disregard TDD message to C5, you can click the corresponding buttons on the right side.
API
In the API, there is a new (optional) read-only field in
send-transactions, called tdd_send_transactions. This field would
also be added to receive-transactions, but as of yet there is no TDD
submission for receive transactions in the SK TDD specification.
Note: Since there can be more than one TDD submission for a transaction, this field contains a list of objects. It is ordered by creation date, so the last entry in the list is generally the current status.
Example:
"tdd_send_transactions": [
{
"id": 789,
"scope": "D",
"type_code": "S",
"created_on": "2026-08-24T14:15:22Z",
"sent_on": "2026-08-24T14:15:22Z",
"parent_receive_transaction_id": 543,
"state": "SENT",
"mls_response_code": "AP",
"error": "",
"links": {
"self": "https://test.ion-ap.net/api/v2/receive-transactions/789"
}
}
],
As you can see, it shows the transaction ID, the scope and type, when it was created and sent (if it has been sent), its parent transaction, and the send state and MLS response code. The optional field error contains an error if there was something wrong with the TDD or its submission.
There are also two additional action endpoints on the main send transaction where TDD is relevant:
/api/v2/send-transactions/1234/tdd-resubmit
This recreates the TDD and sends it to C5 again, using type code R
/api/v2/send-transactions/1234/tdd-disregard
This recreates the TDD and sends it to C5 again, using type code D