What is the difference between CustomizationID and ProfileID in Peppol?

CustomizationID (BT-24) identifies the syntax specification — the set of rules the invoice conforms to. ProfileID (BT-23) identifies the business process — for standard billing it is urn:fdc:peppol.eu:2017:poacc:billing:01:1.0. Both must be present and different.

Can I use a custom ProfileID for internal purposes?

No. The ProfileID must be a registered Peppol process identifier. Custom values will be rejected by every Peppol Access Point. Use invoice notes or references for internal metadata instead.

Does R007 apply to credit notes too?

Yes. Credit notes use the same billing process identifier (urn:fdc:peppol.eu:2017:poacc:billing:01:1.0). The rule applies to any UBL document type sent over the Peppol billing process.

The Peppol URN changed — do I need to update it?

No. urn:fdc:peppol.eu:2017:poacc:billing:01:1.0 is the stable identifier for standard billing and has not changed since Peppol BIS 3.0 was released. Do not substitute a newer year in the URN.

Can Invoice Navigator fix R007 automatically?

Yes. Invoice Navigator auto-fixes R007 with 0.95 confidence by replacing the ProfileID value with the correct billing URN. The original invoice metadata is preserved and the fix is logged in the Evidence Pack.

Error codes · Peppol BIS 3.0

PEPPOL-EN16931-R007Fixable here

Business process identifier has wrong format

This is the rejection, word for word: „[PEPPOL-EN16931-R007] PEPPOL-EN16931-R007 fires when the ProfileID (BT-23, cbc:ProfileID) in your invoice does not follow the required Peppol URN format. For standard billing it must be exactly urn:fdc:peppol.eu:2017:poacc:billing:01:1.0. Any typo, missing segment, or old identifier from earlier Peppol releases triggers this error at the Access Point before transmission.“

The Peppol Schematron rule PEPPOL-EN16931-R007 asserts that /Invoice/cbc:ProfileID matches the pattern urn:fdc:peppol.eu:2017:poacc:billing:01:1.0 (billing process 01) or an equivalent registered process such as ...:billing:02:1.0 for reminders. The rule is separate from CustomizationID (BT-24), which specifies the syntax specification and must be urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0. Confusing the two identifiers is the single most common cause of R007.

What to have readyThe missing value from your purchase order, contract or bookkeeping.

What we doSet cbc:ProfileID to urn:fdc:peppol.eu:2017:poacc:billing:01:1.0. Do not put the CustomizationID value here. Invoice Navigator auto-fixes R007 with confidence 0.95 by replacing the ProfileID with the correct billing process URN.

Choose the rejected invoiceor drop it here

XRechnung XML or ZUGFeRD PDF. Checking is free · corrected file €1.90 · the first every 30 days is free · no sign-up.

If you enter it yourself in your invoicing software

Before

<Invoice xmlns="urn:oasis:names:specification:ubl:schema:xsd:Invoice-2">
  <cbc:CustomizationID>urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0</cbc:CustomizationID>
  <cbc:ProfileID>urn:fdc:peppol.eu:2020:poacc:billing:01:2.0</cbc:ProfileID>
  <cbc:ID>INV-2026-0842</cbc:ID>
</Invoice>

After

<Invoice xmlns="urn:oasis:names:specification:ubl:schema:xsd:Invoice-2">
  <cbc:CustomizationID>urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0</cbc:CustomizationID>
  <cbc:ProfileID>urn:fdc:peppol.eu:2017:poacc:billing:01:1.0</cbc:ProfileID>
  <cbc:ID>INV-2026-0842</cbc:ID>
</Invoice>

What the finding looks likeExample

FindingValue missing · PEPPOL-EN16931-R007

Location/Invoice/cbc:ProfileID

From youThe missing value

ThenPassed

ProofSHA-256 and /verify link after the check