Integration of states

How to solve webhooks for e-invoice statuses?

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

Short answer

Design webhooks as repeatable and verified events. Specifically, the names of states and fields are determined by the provider's API, not by law or uniformly by Peppol.

Verification

Signature or token

The webhook must come from a trusted source.

Idempotency

Same event multiple times

A duplicate webhook must not change the result.

Mapping

Internal states

Translate the partner's status names into your own model.

Log

Payload and result

Save what came and how the system decided.

Conclusion

Process webhooks for e-invoices as verified, idempotent and logged events.

Sources

  • Law no. 222/2004 Z. z. Coll. on VAT, § 76a
  • Technical documentation of the partner
  • Internal audit trail

OpenPeppol Message Level Status 1.0

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