E-invoicing routing Id

ReferenceId

A ReferenceId is used to identify a party where a document is send to or received from. In general the party is a company. The ReferenceId is based on the ISO6523 codes translated to SchemeId used in PEPPOL or a eVerbinding CompanyID. Since the new European invoice norm EN-16931 the numeric value is used. This is for documents based on the EN-16931 norm like Simplerinvoicing 2.0 (NLCIUS) or openPEPPOL BISV3Billing.

In the UBL document the ReferenceId is used in two separate parts. The SchemID is placed in the attribute and identifier is placed as text. For example the ReferenceId NL:KVK:00006688 is placed in the document as:

<cbc:EndpointID schemeAgencyID="ZZZ" schemeID="NL:KVK">00006688</cbc:EndpointID>
or with new EN-16931 documents
<cbc:EndpointID schemeID="0106">00006688</cbc:EndpointID>

In the API calls we always use the complete ReferenceId where the id and schemeId are concatenated to <schemeID>:<Id>

Some examples

NL:KVK:00006688
NL:VAT:NL123456789B01
NL:OIN:00000001001490394661
GLN:5055953900605
BE:VAT:BE0476306127
BE:CBE:0476306127

Be aware the id’s used in the ReferenceID and in the UBL should be formated without dots or spaces. For example the VAT must start with the land code and does not contain dot’s or spaces, like: NL123456789B01

Different UBL-usage of party Id’s

The EndpointId is used for transport partyId via e-invoicing networks. Almost all partyId’s are allowed here if they are existing and reachable within the network.

<cac:AccountingSupplierParty> or <cac:AccountingCustomerParty>
    <cac:Party >
        <cbc:EndpointID schemeAgencyID="ZZZ" schemeID="NL:KVK">00006688</cbc:EndpointID>
or
        <cbc:EndpointID schemeID="0106">00006688</cbc:EndpointID>

In the UBL we expect a legal partyId as generic partyId, which can be the NL:KVK, BE:VAT or NL:OIN. This field is mandatory for sending to the governments. This must be an identifier issued by an official registrar that identifies the Seller as a legal entity or person. For the Netherlands this are NL:KVK and NL:OIN.

<cac:Party >
    <cac:PartyLegalEntity>
        <cbc:CompanyID schemeAgencyID="ZZZ" schemeID="NL:OIN">00000001822477348000</cbc:CompanyID>
or        
        <cbc:CompanyID schemeID="0190">00000001822477348000</cbc:CompanyID>

Also a fiscal partyId is needed when VAT is charged, this partyId must be placed in a different field and does not exempt for filling in the Endpoint or PartyIdentification.

Usage note

VAT number prefixed by a country code based on ISO 3166-1 “Codes for the representation of names of countries and their subdivisions”. And schemeID contains *:VAT.

 <cac:AccountingSupplierParty>
    <cac:Party >
        <cac:PartyTaxScheme>
            <cbc:CompanyID schemeAgencyID="ZZZ" schemeID="NL:VAT">NL123456789B01</cbc:CompanyID>
or
            <cbc:CompanyID schemeID="9944">NL123456789B01</cbc:CompanyID>

A general partyId can also be used on several other places.

Usage note

For many systems, the Seller identifier is a key piece of information. Multiple Seller identifiers may be assigned or specified. They may be differentiated by using various identification schemes. If no scheme is specified, it should be known by Buyer and Seller, e.g. a previously exchanged Buyer assigned identifier of the Seller.

<cac:Party >
    <cac:PartyIdentification >
        <cbc:ID schemeAgencyID="ZZZ" schemeID="NL:KVK">54441587</cbc:ID>
or
                <cbc:ID schemeID="0106">54441587</cbc:ID>

For payment a payment ID can be used. A payment ID can also be used as general or transport partyId

    <cac:PaymentMeans>
        <cac:PayeeFinancialAccount>
            <cbd:ID schemeAgencyID="2" schemeID="IBAN">NL13TEST0123456789</urn1:ID>

Endpoint

If no EndPoint or routingId is known we search for the partyId in these e-invoice party fields in this order:

  • //cac:AccountingCustomerParty/cac:Party/cbc:EndpointID
  • //cac:AccountingCustomerParty/cac:Party/cac:PartyLegalEntity/cbc:CompanyID
  • //cac:AccountingCustomerParty/cac:Party/cac:PartyTaxScheme/cbc:CompanyID

Email address of the contact person:

  • //cac:AccountingCustomerParty/cac:Party/cac:Contact/cbc:ElectronicMail
  • //cac:AccountingCustomerParty/cac:AccountingContact
  • //cac:AccountingCustomerParty/cac:BuyerContact

ReferenceId used for sending

The ReferenceId is also used during sending (SendDocument).  You can use the ReferenceId  as cbc:CompanyID or cbc:EndpointID.  If the ReferenceId is used for these fields. The schemeId must be separated from the actual id.

NL:KVK:00006688    becomes  <…. schemeID=”NL:KVK”>00006688

Frequenty used schemeId’s based on ISO6523-1 in the Netherland

List used for Simplerinvoicing 1.2 and 1.1 https://www.galaxygw.com/iso6523/

The complete new list used since EN-16931 can be found at: http://docs.peppol.eu/poacc/billing/3.0/codelist/ICD/

ISO6523-1 code schemeID Description
9925 BE:VAT Belgium VAT number
0060 DUNS Dun and Bradstreet Ltd
9912 EU:VAT National ministries of Economy
0088 GLN GS1
9918 IBAN S.W.I.F.T. Society for Worldwide Interbank Financial Telecommunications s.c.
0106 NL:KVK Vereniging van Kamers van Koophandel en Fabrieken in Nederland
0190 NL:OIN Dutch OverheidsIdentificatieNummer new since EN-16931
9954 NL:OIN Dutch OverheidsIdentificatieNummer
9944 NL:VAT Netherlands VAT number

Download the official PEPPOL documentation here.

Registries with lookup facilities for partyId’s

https://portaal.digikoppeling.nl/registers/

https://www.kvk.nl/zoeken

https://digital.belgium.be/e-invoicing/PeppolSearch.html

Was this article helpful?