Finding a Customer's Peppol ID Using Enterprise Numbers — Odoo & ERP article by Rui Codex

To find a customer's Peppol ID, check whether they are listed in the Peppol Directory under their enterprise number, then confirm the identifier with them before sending. A Belgian enterprise number can be used to build the ID only if the customer registered under that scheme, so a directory search remains the reliable check. If no entry appears, the customer may still accept invoices by other channels.

Key takeaways

  • A Peppol ID is a scheme code and a value, and the enterprise number is only one possible value.
  • The Peppol Directory is the public place to confirm whether a customer can receive Peppol documents.
  • A missing directory entry does not prove that a customer cannot receive e-invoices.
  • Always confirm the exact identifier with the customer before you configure a send.

What is a Peppol ID made of?

A Peppol participant identifier has two parts: a scheme code and a value, written together with a colon between them. The scheme tells the network what kind of number the value is. The value is the number issued by the registry or identifier system that the scheme refers to.

The scheme codes come from the ISO 6523 International Code Designator list, which Peppol uses in its specifications. The current code list and the rules for each scheme are published in the Peppol documentation at the Peppol BIS Billing 3.0 documentation, and you should check it rather than rely on codes copied from older posts.

This structure explains most of the confusion. A Belgian company is commonly identified under the Belgian enterprise number scheme, but a company may also be registered under a different scheme, such as a global location number. The same company can therefore appear with a different identifier than the one you expected.

Can you build the ID from an enterprise number?

Yes, but only as a candidate. For Belgian companies, the enterprise number scheme uses the ten-digit enterprise number after the scheme code. That gives you a value to test, not a confirmed identifier.

The enterprise number route fails when the customer chose a different scheme at registration, when it operates through a different legal entity, or when it has no Peppol registration at all. A group may also register one subsidiary but not the parent. Treat the enterprise number as the search key for the directory, not as the final answer.

Tip: Remove the dots from the enterprise number as displayed on invoices, for example 0123.456.789 becomes 0123456789, before you search. Many lookup errors come from formatting alone.

Start with the public Peppol Directory at the Peppol Directory. Search by the company name or by the identifier, then open the entry and compare the scheme and value with the number your customer gave you.

Follow these steps in order:

  1. Search by the enterprise number in the identifier field, using the scheme and value format.
  2. If nothing appears, search by the legal name and check for similar names or subsidiaries.
  3. Open each candidate entry and check the legal name, the country and the scheme.
  4. Record the full identifier exactly as it appears, including the scheme code.
  5. Confirm that identifier with the customer in writing, because the directory reflects what a participant registered, not what your customer intends to use today.

The directory is a reference for discovery. It does not tell you which document formats a customer accepts, and it does not verify that a customer's accounts team has approved e-invoicing. Those details need a direct conversation or the customer's written supplier instructions.

When do lookups fail, and what then?

A lookup fails for ordinary reasons more often than for dramatic ones. The most common causes are a wrong scheme, a registration under a parent or branch entity, a typo in the number, or a customer that simply has not registered. Each cause needs a different response.

Tip: Do not guess a Peppol ID from the VAT number or the company name and send an invoice to it. A wrong identifier can route a document to an unintended recipient or fail silently.

If the customer is not in the directory, ask for their Peppol ID directly, or ask which channel they accept. Some customers receive invoices by email or through a portal, and your integration should support that fallback instead of blocking the sale.

Hypothetical examples of lookups

Here are two hypothetical scenarios:

Scenario one. A supplier searches the directory with a customer's enterprise number and finds one entry under the expected scheme. The legal name matches the invoice address. The supplier confirms the identifier by email and configures it once, which is the simplest path.

Scenario two. The same supplier finds no entry for the enterprise number. A search by name shows a holding company and an operating subsidiary, each with a separate identifier. The accounts contact confirms that the subsidiary is the invoice recipient, so the supplier uses that entry and keeps the holding company out of the send.

Checklist before you send

Before you store a customer's Peppol ID in your system, work through this list:

  • The scheme code and value match the customer's written confirmation.
  • The legal name in the directory matches the invoicing entity.
  • The identifier is stored with its scheme, not only the number.
  • A fallback channel is defined for customers without an entry.
  • The record has a named owner who can correct it when the customer changes entity or registration.

Keeping identifiers current

Customers change legal entities, merge, or move registrations. Review stored identifiers on a fixed schedule, and re-check them when a customer reports a rejected or missing invoice. Logging each change with a date and a source makes later audits far easier.

Connecting lookups to your systems

In practice, the lookup belongs inside the order-to-invoice flow rather than in a manual spreadsheet. A well-built integration stores the scheme and value against the customer record, validates them when the customer is created, and flags exceptions to the finance team. Teams that connect their ERP and CRM usually do this once in the integration layer, as described in our overview of ERP and CRM integration services. For e-invoicing specifically, see our page on Peppol e-invoicing integration.

Rui Codex is led by a founder with 200+ projects delivered and 12+ years of hands-on experience. If you want to talk through how identifier lookups fit into your system landscape, you can request a project consultation, or email info@ruicodex.com. You can also review delivered work in our published case studies.

Frequently Asked Questions

Is the enterprise number the same as a Peppol ID?

No. The enterprise number is a registry number, and a Peppol ID combines a scheme code with a value. The enterprise number can be used as the value under the matching scheme, but the customer may be registered under a different scheme or entity, so you should confirm the full identifier.

What should I do if the customer is not in the Peppol Directory?

Ask the customer for their Peppol ID or their preferred invoice channel in writing. A missing entry means the customer is not discoverable through the directory, not that they cannot receive invoices. Keep an email or portal fallback in place until the customer confirms the details.

Can I search the Peppol Directory by company name?

Yes, you can search by name, but results can include subsidiaries, branches and similar names. Always compare the legal name, country and scheme with your invoicing records before choosing an entry, and never assume the first match is correct.

How often should stored Peppol IDs be checked?

Check them on a regular schedule and whenever a customer reports a rejected or missing invoice. Customers that merge, restructure or change registration may need a new identifier, so assign an internal owner who can update the record when the customer confirms a change.

Conclusion

Finding a customer's Peppol ID is a matter of combining the enterprise number, the correct scheme and a direct confirmation from the customer. The Peppol Directory is the right place to check, but it reflects registrations rather than invoicing preferences. Build a fallback for customers who are not listed, and store identifiers with their scheme so that later corrections are easy. To discuss how this fits your invoicing setup, request a project consultation with our team.

Sources

Tags: Peppol ID Peppol Directory e-invoicing enterprise number Belgium API Integration ERP integration Workflow Automation

Need Help Implementing This?

Our team can help you put these insights into practice. From AI automation to custom software development, we build solutions that deliver real results.

Send a project request