Peppol for freelancers and small businesses: the minimum you need
The short version of Peppol for a one-person or very small operation — what you actually have to do, what you can safely ignore, and why you don't need heavy software to comply.
Most writing about Peppol assumes a finance department. It talks about ERP connectors, procurement platforms, and validation pipelines, and if you are a freelancer or run a firm of three people, it reads like a problem you are not equipped for. You are. The requirement that actually lands on a small business is narrow, and the work to meet it is small once you see it clearly.
Here is the honest minimum.
What you actually have to do
If a customer or a national mandate requires Peppol, you need to do one thing: deliver your invoices as structured electronic documents over the Peppol network, instead of as a PDF attached to an email. That is the whole obligation. The invoice itself — the amounts, the VAT, the line items — is the same invoice you already raise. What changes is the delivery format and the pipe it travels through.
A structured invoice is a machine-readable file (UBL) that follows the Peppol BIS Billing 3.0 profile, which is the practical form of the European standard EN 16931. It carries the same information as your PDF, but in fields a computer can read without a human retyping anything. That is the point of the whole system, and it is also why a scanned PDF does not count.
What you can ignore
This is the part nobody tells small businesses, so it is worth being blunt about.
- You do not need an ERP. Peppol is a delivery requirement, not a reason to replace your accounting or billing tools. If Stripe raises your invoices today, it can keep doing so. Our post on whether you need an ERP for Peppol goes into why the two are unrelated.
- You do not need to run your own access point. You cannot connect to the Peppol network directly anyway — everyone reaches it through a certified access point, which is a service, not something you install. Access points explained covers how that works.
- You do not need to understand UBL. It is generated for you from the invoice you already have. You will never open the file.
- You do not need a monthly software contract. Low invoice volume does not fit a subscription, and it should not have to.
The mandate is real, but the surface area you personally touch is one step: getting each invoice onto the network.
Why the software can be thin
The reason a small operation does not need heavy tooling is that most of the weight in "Peppol software" is bookkeeping you already do in Stripe. Stripe is your system of record — it holds the customers, the invoice numbers, the payment status, the PDFs. None of that has to move. What is missing is a thin layer that takes a finalised Stripe invoice, turns it into the structured document, checks the recipient is reachable, and hands it to a certified access point.
That is what Peppost does, and deliberately nothing more. You connect Stripe once through a standard OAuth step — it never sees your secret keys — and your finalised invoices and credit notes become sendable. Peppost is send-only: it does not register your own customers as receivers or turn you into a receiving participant, and it will not pretend to be your accounting system. It adds the delivery layer and stops there.
Why pay-per-send fits a small operation
If you send four invoices a month, a subscription is the wrong shape — you would pay for a platform that sits idle most of the time. Peppost is prepaid credits instead: one credit per send, no monthly fee, and credits never expire, so a quiet month costs nothing. New accounts get a few free sends, and the whole flow works in Stripe test mode, so you can rehearse a real send before spending anything. The recipient is looked up in the Peppol directory before a credit is spent, so an unreachable customer never costs you a credit either. The credits and billing guide has the mechanics, the pricing page has the numbers, and the FAQ answers the common what-ifs.
The whole checklist
- Confirm which customers or mandates actually require Peppol. Often it is one or two clients, not all of them.
- Make sure your own company details in Stripe are complete — legal name, VAT number, registered address. These become the supplier fields in the structured invoice, and Peppol validation is strict about them.
- Connect Stripe, do one test send, then send your next real invoice.
That is the entire project. If you want the ground-up explanation of the network itself before you start, what is Peppol is the place to begin, and the getting-started guide walks the setup end to end.