Confirmation

What is a technical e-invoice delivery acknowledgement?

Short answer

A technical acknowledgement records that specific XML reached the target channel or system. It should identify the document, time and status and, where available, the transaction identifier and source of the acknowledgement. It does not by itself prove that the customer substantively approved the invoice.

Content

Identifier and time

The confirmation shall be linked to a specific invoice.

Source

Partner or system

The important thing is who issued the certificate.

Limit

No commercial approval

Service is not acceptance of service or payment.

Save to XML

Confirmation belongs to the audit package.

Detailed explanation

A confirmation is only meaningful if it can be linked to a specific document. It is therefore advisable to also store the XML hash, the invoice number, the recipient and the message’s technical identifier. In the event of an audit or dispute, you will then be able to provide not only the invoice but also its delivery trail.

As set out in the Act

The date and time of delivery are among the details that must be verifiable. A technical confirmation is a practical way of retaining this evidence.

Practical examples

The partner returns the transaction ID and the time of delivery.
The ERP system stores the ‘delivered’ status together with the XML hash.
In the event of a complaint, the confirmation is compared with the customer’s claim.

Most common mistakes

“A delivery confirmation means that the recipient agrees.” No, it is technical evidence.
“A screenshot of the screen is enough.” An exportable record or report is better.
“I don’t need a confirmation if I have the XML.” XML proves the content, not the entire delivery process.

Conclusion

Store the technical delivery acknowledgement with the XML as transport evidence, while keeping it separate from business approval.

Legal basis

Act No. 222/2004 Coll. on VAT, Section 76a
Partner Delivery Status
Internal audit package