How outbound documents are routed

When Centara sends an electronic document — a PEPPOL sales invoice, a credit memo, or a purchase order — every party on the document (your company, the customer, the vendor, the delivery address) must carry an identifier plus a scheme ID that says what kind of identifier it is. The recipient’s access point uses the identifier to look up the party in the PEPPOL directory and route the document.

This page explains which fields Centara reads to build those identifiers, in what order, and what to set on a Customer Card, Vendor Card, or Company Information to make routing work.

The three identifier types

Three identifiers can address a party. Centara picks one per party, per document.

Identifier	PEPPOL scheme	When to use
GLN (Global Location Number)	0088	The party has registered a GLN in the GS1 system. This is the “native” PEPPOL identifier and the one recipients with their own access point publish to the network.
Registration Number	Country-specific (e.g. 0196 for Iceland) — comes from Country/Region."VAT Scheme"	The party doesn’t publish a GLN but is identified by its national company-registry number (kennitala in Iceland, organization number elsewhere).
VAT Registration No.	Country-specific from Country/Region."VAT Scheme"	Last-resort fallback for parties identified only by a VAT number, common cross-border.

The scheme ID is what tells the recipient how to interpret the identifier. 0088 always means GLN. The country-specific schemes come from the Country/Region table — set VAT Scheme on each country you trade with, otherwise the document will leave with an empty scheme ID and be rejected.

Sender (your company)

Source: Company Information.

Centara picks the sender identifier in this order:

1. If Use GLN in Electronic Document is on and GLN is filled → use GLN with scheme 0088.
2. Else if Registration Number is filled → use Registration Number with the country’s VAT scheme.
3. Else if VAT Registration No. is filled → use VAT Registration No. via the standard PEPPOL tax-scheme path.
4. Fallback: use GLN with scheme 0088 even if the toggle is off.

The same logic is used for both sales-side (invoice, credit memo) and purchase-side (purchase order) outbound documents — the sender block doesn’t change with document direction.

Practical setup: if your company has a GLN, fill it in and turn on Use GLN in Electronic Document. If you don’t, leave both empty and rely on Registration Number; the country code on Company Information must be set so the right scheme is picked up.

Customer (outbound sales invoice / credit memo)

Source: Customer Card.

The logic depends on which path generated the document:

Standard BC sales path

When the document originates from a standard Sales Invoice / Sales Credit Memo, Centara delegates the customer-party block to BC’s own PEPPOL Management codeunit. Microsoft’s rules apply — typically: GLN if present, else VAT Registration No., else BIS-3 defaults.

LS Central POS-originated invoice

When the document originates from an LS Central transaction (POS receipt converted to a PEPPOL invoice), Centara applies its own priority on the Customer Card:

1. If GLN is filled and Use GLN in Electronic Document is on → GLN with scheme 0088.
2. Else if Registration Number is filled → Registration Number with the country’s VAT scheme.
3. Otherwise the customer block leaves with no endpoint and the document is rejected.

Note the difference from the sender side: there is no fallback to VAT Registration No. on the LS Central customer path. If a customer has neither a GLN nor a Registration Number, the LS Central PEPPOL transmission cannot address them.

Delivery party (LS Central only)

For LS Central invoices, the DeliveryID is taken from Customer.GLN regardless of the toggle, with scheme GLN. If the customer has no GLN, the delivery party is left empty. The toggle gates the endpoint — not the delivery block.

Vendor (outbound purchase order)

Source: Vendor Card.

For outbound PEPPOL purchase orders, Centara picks the vendor identifier in this order:

1. If GLN is filled → GLN with scheme 0088.
2. Else if Registration Number is filled → Registration Number with the country’s VAT scheme.
3. Else if VAT Registration No. is filled → VAT Registration No. with the country’s VAT scheme.

Asymmetry vs. Customer: the Vendor side does not check a “Use GLN in Electronic Document” toggle — if the GLN is on the Vendor Card, it is used. If you have a vendor whose GLN you’ve recorded internally but who is not addressable by GLN on PEPPOL, clear the field on the Vendor Card; leaving it filled will misroute the document.

The buyer block on the purchase order (your own company) follows a simplified version of the sender logic: GLN if Use GLN in Electronic Document is on, otherwise Registration Number.

Setup that affects routing

Setting	Effect
Company Information → GLN	Your company’s GLN. Read on every outbound document.
Company Information → Use GLN in Electronic Document	Gates whether the GLN is used as the sender endpoint. Off → fall through to Registration Number.
Country/Region → VAT Scheme	The scheme ID applied to Registration Numbers and VAT Registration Numbers for parties in that country. Empty here means an empty scheme on the document — typically rejected by the recipient.
Sales & Receivables Setup → EndpointID for PEPPOL	When set to Registration No., the Party Legal Entity block on LS Central PEPPOL invoices is filled with the customer’s name and Registration Number. Blank leaves the legal-entity block out. Affects LS Central invoices only.
Customer → Use GLN in Electronic Document	Gates the customer GLN on the LS Central POS path. Off → fall through to Registration Number.

There is currently no equivalent “Use GLN in Electronic Document” toggle on the Vendor Card or on Purchases & Payables Setup — vendor routing is GLN-first whenever the field is populated.

Common scenarios

Sending a sales invoice to a PEPPOL recipient who has a published GLN. Set Customer.GLN and turn on Customer."Use GLN in Electronic Document". Set your own Company Information.GLN and the matching toggle. Result: endpoint scheme 0088 on both ends.

Sending a sales invoice domestically in Iceland with no GLN exchange. Fill Customer."Registration Number" (the kennitala) and leave GLN-related fields empty. Make sure Country/Region “IS” has VAT Scheme = 0196. Result: endpoint scheme 0196.

Sending a purchase order to a vendor. Fill Vendor.GLN if the vendor publishes one and you want GLN-based routing. Otherwise leave it empty and rely on Vendor."Registration Number" or Vendor."VAT Registration No.". Remember: the Vendor side has no toggle — a populated GLN will be used unconditionally.

Cross-border invoice to a customer identified only by VAT Reg. No. Use the standard BC sales path (not LS Central), set the customer’s VAT Registration No., and rely on Microsoft’s PEPPOL Management to address the party. The LS Central path will not fall back to VAT Reg. No. on the customer side.

See also

• Customer Card — Centara fields
• Vendor Card — Centara fields
• Sales & Receivables Setup — Centara fields
• Purchases & Payables Setup — Centara fields