Self-billing is an invoicing model where the buyer prepares the invoice on behalf of the supplier, based on an agreement between the two parties. In structured e-invoicing, that changes much more than the XML format.

Why self-billing changes the workflow

In a normal invoicing flow, the supplier creates the invoice and sends it to the buyer. In self-billing, the buyer-side process becomes the starting point for the document.

That creates extra questions around:

  • who owns the commercial source data
  • how supplier approval or dispute handling works
  • how corrections and credit notes should be managed
  • how audit trail and tax responsibilities are reflected in the flow

This is why self-billing should not be treated as a small variant of a standard outbound invoice process.

What product teams need to design

If self-billing enters the roadmap, it helps to make decisions early about:

  • which system is the source of truth for quantities and prices
  • which events trigger invoice creation
  • how exceptions are handled when the supplier disagrees
  • what support teams can see when a correction is needed

Without that design work, the document format can be technically correct while the commercial workflow remains fragile.

Why self-billing matters in e-invoicing projects

Self-billing is one of the clearest examples of why e-invoicing projects are not only about transport and validation. They are also about business ownership, approvals, and operational clarity.

That is especially important for ERP, marketplace, and finance products where the invoicing workflow needs to feel trustworthy to both parties.

A practical takeaway

Self-billing is relevant because it forces teams to design the surrounding business process, not just the message payload. If that work is skipped, rollout complexity usually reappears later as support and reconciliation friction.

Useful follow-ups are What Is a Peppol credit note? , What Is a Peppol invoice response? , What finance teams need from an e-invoicing platform , and Common mistakes in Peppol integration projects .