Peppol mapping
When you send a sales invoice through Peppol, Robaws converts that invoice into a Peppol BIS 3 UBL file. This article shows, per UBL field (BT number), which data from Robaws is used. Useful when your customer or accountant asks where a particular piece of data on the e-invoice comes from. Is the link with Peppol not active yet? Then activate it first.
Where the data comes from
The data in the UBL comes from three sources:
- Your company file in Robaws — name, address, general telephone number, general email address, VAT number, KvK/CBE number and the Peppol bank account. You manage this data yourself.
- The registered Peppol identification — the Peppol address (participant ID) by which your company is known on the network. This is set when Peppol is activated, after a mandatory KYC check by our back office. Would you like to change that registration? Get in touch via billing@robaws.com.
- The invoice and the customer file — all document data and the data of your customer.
General invoice data
UBL element (BT) | Data in Robaws |
|---|---|
ID (BT-1) | Invoice number |
IssueDate (BT-2) | Invoice date |
TaxPointDate (BT-7) | Invoice date |
DueDate (BT-9) | Due date |
DocumentCurrencyCode (BT-5) | Currency code of the invoice, for example EUR |
TaxCurrencyCode (BT-6) | The default currency of your environment. This field is only sent along if the invoice currency differs from the default currency. |
InvoiceTypeCode (BT-3) | 380 for an invoice, 381 for a credit note |
CustomizationID (BT-24) | urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0 |
ProfileID (BT-23) | urn:fdc:peppol.eu:2017:poacc:billing:01:1.0 |
InvoicePeriod (BG-14) | Invoice period, if you use it |
Your own data as the sender
UBL element (BT) | Data in Robaws |
|---|---|
AccountingSupplierParty/Party/PartyName/Name (BT-28) | Name of the company on the company file |
AccountingSupplierParty/Party/PartyLegalEntity/RegistrationName (BT-27) | Same as BT-28 |
AccountingSupplierParty/Party/PartyIdentification/ID (BT-29) and PartyLegalEntity/CompanyID (BT-30) | The primary identification of your company — see 'Which identification is used' below |
AccountingSupplierParty/Party/PartyTaxScheme/CompanyID (BT-31) | VAT number of your company |
AccountingSupplierParty/Party/EndpointID (BT-34) | The registered Peppol address of your company |
AccountingSupplierParty/Party/PostalAddress/StreetName (BT-35) | Street and house number from the company file |
AccountingSupplierParty/Party/PostalAddress/PostalZone (BT-38) | Postcode from the company file |
AccountingSupplierParty/Party/PostalAddress/CityName (BT-37) | Municipality from the company file |
AccountingSupplierParty/Party/PostalAddress/Country/IdentificationCode (BT-40) | ISO alpha2 country code from the company file |
AccountingSupplierParty/Party/Contact/Name (BT-41) | Same as BT-28 |
AccountingSupplierParty/Party/Contact/Telephone (BT-42) | General telephone number from the company file |
AccountingSupplierParty/Party/Contact/ElectronicMail (BT-43) | General email address from the company file |
Which identification is used (BT-29, BT-30)?
Robaws selects the identification in this order:
- Is a GLN filled in? Then that is used, with schemeID 0088.
- If not, it depends on the country of your VAT number:
Country | Number | schemeID |
|---|---|---|
Netherlands | KvK number | 0106 |
Belgium | CBE number (or the VAT number if the CBE number is empty) | 0208 |
Data of your customer
UBL element (BT) | Data in Robaws |
|---|---|
AccountingCustomerParty/Party/PartyName/Name (BT-45) | Name of the customer: Title + Name + Legalform |
AccountingCustomerParty/Party/PostalAddress/StreetName (BT-50) | The 'Street' field of the customer's address |
AccountingCustomerParty/Party/PostalAddress/PostalZone (BT-53) | Postcode of the customer's address |
AccountingCustomerParty/Party/PostalAddress/CityName (BT-52) | Municipality or city of the customer's address |
AccountingCustomerParty/Party/PostalAddress/Country/IdentificationCode (BT-55) | ISO alpha2 country code of the customer's address |
AccountingCustomerParty/Party/Contact/ElectronicMail (BT-58) | The invoicing email address of the customer |
Payment data and references
UBL element (BT) | Data in Robaws |
|---|---|
PaymentMeans/PayeeFinancialAccount/ID (BG-17, BT-82) | The IBAN of the Peppol bank account on your company file |
PaymentMeans/PayeeFinancialAccount/FinancialInstitutionBranch/ID (BT-86) | The BIC of the Peppol bank account (optional) |
PaymentTerms (BT-20) | The payment condition of the invoice |
BuyerReference (BT-10) | Customer reference of the invoice |
OrderReference/ID (BT-13) | The PO number of the invoice. If that is empty, the customer reference. If both are empty, 'NA' is sent. |
Any questions?
Do you come across a difference between what you see in Robaws and what appears on the e-invoice? Then get in touch with support@robaws.com. Is it about your Peppol registration itself (name, KYC data or the Peppol address)? Then email billing@robaws.com.
Updated on: 09/09/2026
Thank you!