When teams say they are launching e-invoicing, they often mean one of two different things:
- sending invoices out through Peppol
- receiving invoices in structured form through Peppol
Those are related but not identical rollouts. The right starting point depends on customer demand, internal ownership, and where operational pressure is highest.
Why outbound often goes first
Outbound invoicing is often the simpler first step because the product controls the document creation point. That makes it easier to:
- shape the source data
- control when documents are sent
- expose statuses in the existing workflow
- limit the number of moving parts at launch
When inbound should lead
Inbound can be the stronger first use case if customers primarily want automation on accounts payable or document intake. In that case, the product value sits in structured receipt, routing, and downstream processing.
A better rollout rule
Choose the direction that gives you the clearest first operational win. Then design the second phase so the data model, statuses, and support workflows do not need to be rebuilt later.
This is where platform thinking helps. A strong operating model around Peppol makes it easier to expand from one flow to both.
For rollout planning, also read How to test Peppol integrations before production and How supplier onboarding for Peppol actually works.