Retros without duplication

How to resend an e-invoice after a technical error?

⚠ Machine-translated answer, not yet manually reviewed. For the exact wording, see the Slovak original.

Short answer

Before retries, find out the result of the first attempt. Technically repeating the same message is not the same as correcting an already delivered invoice.

Unknown status

Find out first

Do not blindly resend the document without confirming the status of the first attempt.

The same XML

Technical retro

Idempotence, Message ID and deduplication are technical rules of the provider, not a substitute for an accounting decision.

Changed data

Not an ordinary retro anymore

When the document is delivered, a correction document linked to the original invoice will be used.

Number and date

Don't make up a rule

The exact procedure for a technically rejected, undelivered document must be confirmed by the provider's status and documentation.

Conclusion

Retry is a repetition of a technical attempt, not a method of correcting accounting content. After delivery, the content is changed by a correction document; if the status is unclear or rejected, first follow the confirmed status and the rules of the provider.

Sources

  • Law no. 222/2004 Z. z. Coll. on VAT, § 76a
  • Internal audit trail
  • SLA and retry rules of the delivery partner

Act No. 222/2004 Z. z. Coll. about VAT · FAQ of the Financial Administration of the Slovak Republic on e-invoice (7/7/2026) · OpenPeppol Message Level Status 1.0

Not legal advice. Machine-translated answer, not yet manually reviewed. For the exact wording, see the Slovak original.