The short answer

QuickBooks Online has not offered native Peppol sending to UK organisations. A UK business on QuickBooks reaches the network through a certified Access Point that connects to QuickBooks, with the invoice still raised in QuickBooks exactly as it is today.

The complication specific to QuickBooks is not the connection. It is that QuickBooks distinguishes carefully between transaction types, and only some of them belong on the network at all.

Not every QuickBooks transaction is an invoice

This is the point that separates QuickBooks from Xero in practice, and it catches people who assume everything in the sales ledger is eligible.

QuickBooks models sales differently depending on how the money arrives. An Invoice is raised on terms and expects payment later. A Sales Receipt records an order that was already paid at the point of purchase, which is what a direct to consumer Shopify or WooCommerce order usually is. They are different objects with different places in your accounts receivable.

Peppol carries invoices and credit notes. A Sales Receipt has no place on the network, because there is nothing for the buyer to approve and nothing outstanding to pay. If most of your revenue is paid-at-checkout ecommerce recorded as Sales Receipts, most of your revenue is simply outside the scope of e-invoicing, and that is a legitimate answer rather than a gap to fix.

Goes over Peppol
  • Invoices raised on payment terms to business customers
  • Credit notes against those invoices
  • Public sector and wholesale billing
Stays outside it
  • Sales Receipts from paid direct to consumer orders
  • Purchase orders you raise to your own suppliers
  • Internal journals and adjustments

Getting this right early avoids a common false start, where a business scopes an e-invoicing project across their whole sales ledger and discovers halfway through that two thirds of it was never in scope.

What the flow looks like

Assuming the transaction is an invoice, the route is the same shape as any other Peppol send.

Sending a Peppol invoice from QuickBooks Online
01
QuickBooks
Invoice raised against the customer record as normal
→
02
Access Point
Maps the transaction to the required structure, validates it and resolves the recipient
→
03
The network
Delivered to the buyer's provider with a confirmed outcome returned
→
04
Buyer's system
Lands as structured data in their approval workflow

Where QuickBooks is fed from an ERP or inventory system rather than being the origin of the invoice, the same applies one step further back. Our QuickBooks integration page covers that flow, including how transactions are posted with the correct customer, account codes and tax treatment in the first place.

Where QuickBooks data meets Peppol requirements

QuickBooks is accommodating about incomplete records. The specification is not. These are the four mappings that decide how a project goes.

Customer record
A name and billing address is enough to raise an invoice in QuickBooks
→
Buyer identifier
Registration number and network address, held in a structured field rather than a note
VAT codes
Custom codes accumulate over time and often duplicate each other
→
Tax category codes
A defined set with fixed meanings. Each code you use must resolve to exactly one
Products and services
QuickBooks allows a line with a description and no item behind it
→
Item code and unit
A structured reference and a coded unit of measure on every line
Custom fields
Where PO numbers usually end up, if they are captured at all
→
Buyer reference
Mandatory for many buyers. Missing references are the most common rejection

The customer list is almost always the long pole. Everything else is configuration. That is data entry across years of records.

Class and Location

QuickBooks Class and Location dimensions do for QuickBooks what tracking categories do for Xero: they let you report by channel, department, region or entity without restructuring your chart of accounts.

They do not travel to the buyer. They are not Peppol fields and the recipient never sees them. What makes them relevant is that the rules assigning Class and Location typically encode exactly the knowledge a compliant invoice needs: which entity is selling, which cost centre applies, which channel the order came from. A business that already applies these consistently has most of the mapping logic sitting there already. A business applying them by hand has a data quality signal worth acting on.

Multi-entity and the identifier question

Worth flagging because it surprises people. Peppol identifies the legal entity, not the software account.

If you run several QuickBooks companies for several trading entities, each entity that issues invoices in its own name needs its own registration and its own network address. One connection does not cover a group. Equally, if several brands invoice under one legal entity, they share one identifier regardless of how many Locations you use to separate them in reporting.

This is a structural question rather than a technical one, and it is worth answering before anything gets registered, because unpicking it afterwards means asking buyers to update records at their end.

What to do now if you are on QuickBooks

1
Work out what is actually in scope
Split your revenue between invoices on terms and Sales Receipts from paid orders. Only the first group is affected, and knowing the proportion tells you how big this really is for you.
2
Audit the customer list
For every business customer you invoice on terms, check you hold a registration number in a consistent structured field. This is the task that takes weeks, so starting it early is the single most useful thing you can do.
3
Rationalise VAT codes
List every code in use and confirm someone can explain each. Legacy and duplicate codes cause validation failures that are tedious to trace once you are live.
4
Fix buyer reference capture
If a customer gives you a PO number it needs to reach the invoice every time, not most of the time. This is a process fix rather than a technical one and it pays off immediately in fewer payment queries.

Not sure how much of your ledger is in scope?

We are a certified Peppol Access Point and we connect QuickBooks Online to ERP, inventory and ecommerce order flows. A short call is usually enough to size the work.

Talk to the team

Common questions

Does QuickBooks Online support Peppol?
Not natively for UK organisations. Businesses on QuickBooks connect through a certified Access Point, with the invoice still raised in QuickBooks as normal.
Which transactions can go over Peppol?
Invoices and credit notes. Sales Receipts cannot, because the order is already paid and there is nothing for the buyer to approve. Purchase orders you raise to your own suppliers are a separate matter again.
Do Class and Location reach the buyer?
No. They are QuickBooks reporting dimensions rather than Peppol fields. They matter indirectly, because the logic that assigns them usually also knows the references a compliant invoice needs.
What blocks QuickBooks projects most often?
Customer records. Registration numbers are frequently missing or held in free text, and cleaning a list that has grown over years is usually the longest task in the project.
What about Xero?
A different starting position, since Xero has native e-invoicing in some regions. We cover it in Peppol for Xero.
Peppol QuickBooks E-invoicing Finance