Compliance

This section defines how compliance to the TDD specification is measured and what are the requirements and expectations for the relevant parties.

Compliance to AE TDD is measured for the sender (C1) and the receiving (C4) parties. The sender and receiving parties may outsource their roles to service providers but not the responsibility.

Sending compliance to TDD

TDD issuer (C1 and C4)

An TDD issuer shall not send messages that are not compliant to the specification identified by the specification identifier (tdt-001).

Sending Access Points (C2 and C3)

A sending access points shall upload the TDD transaction to the network according to the Peppol service provider agreement.

Receiving compliance to TDD

Tax authority

The tax authority receiving the TDD shall interpret the content according to this specification.

Receiving access point (C5)

A receiving access point shall transfer the invoice to the buyer according to the Peppol service provider agreement.

Enveloping compliance

Enveloping of BIS message in Peppol Business Message Envelope (SBDH)

When a BIS message is enveloped, the value of the SBDH element Sender/Identifier SHALL match the Party/EndpointID element value of the sender party, including the value of its schemeID attribute.
When a BIS message is enveloped, the value of the SBDH element Receiver/Identifier SHALL match the Party/EndpointID element value of the receiver party, including the value of its schemeID attribute.

Example:

BIS message:
    <cbc:EndpointID schemeID="0088">7315458756324</cbc:EndpointID>

SBDH envelope:
    <Identifier Authority="iso6523-actorid-upis">0088:7315458756324</Identifier>

See Policy for use of Identifiers for more information on how to represent identifiers in envelope and messages.