Set / Select Customer Identifier

Regular Case : 1 Value per Identifier type

Typical regular scenario for customer would be:

  • 1 VAT number
  • 1 Siren Number
  • 1 Siret Number
    • 1 Siret Number as an invoicing address
    • (other Siret number serving as other location types such as delivery location are not relevant)
  • 1 CTC number. CTC can have a specific structure per customer, this is leading.

As Peppol Routing is concerned, some scenario's below:

  • When all identifiers are present, no preference is indicated, and all identifiers are registered on Peppol for receiving: Billit will give preference to (ranking) : 1. CTC. 2. Siret (if present) 3. Siren 4. VAT.
  • Your preference can be included. See next section.

How to include your Customer Identifiers in API Content

Identifiers you should include:

  • If the company has a VAT number, it should always be included (not for Annuaire, but for tax compliance reasons).
  • If the customer has registered with a specific identifier, you should include this identifier(s).

Examples in Json API when posting an invoice, for the customer segment:

    "Customer": {
        "Nr": "000700999,
        "Name": "BAUDIN TEST CHATEAUNEUF",
        "VATNumber": "FR25842499999", 
				"PartyType": "Customer",


        "Addresses": [
            {
                "AddressType": "InvoiceAddress",
                "Name": "BAUDIN TEST CHATEAUNEUF",
                "Street": "Rue de la Brosse 999",
                "Zipcode": "45110",
                "City": "CHATEAUNEUF SUR LOIRE",
                "CountryCode": "FR"
            }
        ]
  		 "Identifiers": [
        {
        "IdentifierType": "SIRET", 
        "Identifier": "84249114400999"
        }
}
    "Customer": {
        "Nr": "000700999,
        "Name": "BAUDIN TEST CHATEAUNEUF",
        "VATNumber": "FR25842499999", 
				"PartyType": "Customer",


        "Addresses": [
            {
                "AddressType": "InvoiceAddress",
                "Name": "BAUDIN TEST CHATEAUNEUF",
                "Street": "Rue de la Brosse 999",
                "Zipcode": "45110",
                "City": "CHATEAUNEUF SUR LOIRE",
                "CountryCode": "FR"
            }
        ]
  		 "Identifiers": [
        {
        "IdentifierType": "SIREN", 
        "Identifier": "842491144"
        }
}
    "Customer": {
        "Nr": "000700999,
        "Name": "BAUDIN TEST CHATEAUNEUF",
        "VATNumber": "FR25842499999", 
				"PartyType": "Customer",


        "Addresses": [
            {
                "AddressType": "InvoiceAddress",
                "Name": "BAUDIN TEST CHATEAUNEUF",
                "Street": "Rue de la Brosse 999",
                "Zipcode": "45110",
                "City": "CHATEAUNEUF SUR LOIRE",
                "CountryCode": "FR"
            }
        ]
  		 "Identifiers": [
        {
        "IdentifierType": "SIREN", 
        "Identifier": "842491144"
        },
				{
        "IdentifierType": "CTC",
        "Identifier": "842491144_12345"
         }
	}
    "Customer": {
        "Nr": "000700999,
        "Name": "BAUDIN TEST CHATEAUNEUF",
        "VATNumber": "FR25842499999", 
				"PartyType": "Customer",


        "Addresses": [
            {
                "AddressType": "InvoiceAddress",
                "Name": "BAUDIN TEST CHATEAUNEUF",
                "Street": "Rue de la Brosse 999",
                "Zipcode": "45110",
                "City": "CHATEAUNEUF SUR LOIRE",
                "CountryCode": "FR"
            }
        ]
  		 "Identifiers": [
        {
        "IdentifierType": "SIREN", 
        "Identifier": "842491144",
        "Preferred": true
        },
				{
        "IdentifierType": "CTC",
        "Identifier": "842491144_12345",   
				"Preferred": false
        }
	}

Advanced Scenario : multiple possible Values for one Customer

It is possible that customer hase one VAT and Siren number, but needs to be addressed with more then one identifier. This information is typically delivered by your customer to you.

Most common examples for France are:

  • Customer has multiple Siret numbers serving as an invoicing identifier, and is registered on Annuaire/Peppol with these identifers.
  • Customer has multiple CTC identifiers serving as an invoicing identifier, and is registered on Annuaire/Peppol with these identifers.

If you have to send invoices to multiple of the identifiers (being different customers), then this can be defined in Billit.

There is some comparison possible with multiple GLN numbers (info https://docs.billit.be/docs/send-to-customer-with-gln-number) .

What needs to be done:

  • Step 1 : make sure the customers are defined in the MyBillit user interface. Get the PartyID of each customer.
  • Step 2 : extend the API-content:
    • include the required identifiers in the API-content.
    • include the PartyID of the customer. This allows to select the right customer. The customer data will no longer be updated via the posting of a new invoice.

Example:

    "Customer": {
        "Nr": "000700999,
        "Name": "BAUDIN TEST CHATEAUNEUF",
        "VATNumber": "FR25842499999", 
        "PartyID": 1109011,  //ID at Billit, goal is to select the correct customer
        "Nr": "7456", // Customer number, is free text, not a primary key
				"PartyType": "Customer",
        "Addresses": [
            {
                "AddressType": "InvoiceAddress",
                "Name": "BAUDIN TEST CHATEAUNEUF",
                "Street": "Rue de la Brosse 999",
                "Zipcode": "45110",
                "City": "CHATEAUNEUF SUR LOIRE",
                "CountryCode": "FR"
            }
        ]
  		 "Identifiers": [
        {
        "IdentifierType": "SIREN", 
        "Identifier": "842491144",
        "Preferred": true  // this customer identifier must have priority for Peppol routing
        },
				{
        "IdentifierType": "CTC",
        "Identifier": "842491144_12345",   
				"Preferred": false
        }
	}