How can I add certain Peppol values that Billit JSON does not support

Billit provides a JSON structure with a wide range of fields. However, since some networks have different types of fields that we might not support out of the box, we have enabled the use of custom fields in our e-invoice network.

You can add these fields for both invoices and creditnote. To avoid mistakes, the root element (Invoice, CreditNote, InvoiceLine,CreditNoteLine) must always be declared.

The allowed values can be found in the lists below.

order

KeyValue
Invoice.AccountingSupplierParty.Party.Contact.Namehttps://docs.peppol.eu/poacc/billing/3.0/syntax/ubl-invoice/cac-AccountingSupplierParty/cac-Party/cac-Contact/cbc-Name/
Invoice.AccountingSupplierParty.Party.Contact.Telephonehttps://docs.peppol.eu/poacc/billing/3.0/syntax/ubl-invoice/cac-AccountingSupplierParty/cac-Party/cac-Contact/cbc-Telephone/
Invoice.AccountingSupplierParty.Party.Contact.ElectronicMailhttps://docs.peppol.eu/poacc/billing/3.0/syntax/ubl-invoice/cac-AccountingSupplierParty/cac-Party/cac-Contact/cbc-ElectronicMail/
Invoice.AccountingCustomerParty.Party.Contact.Namehttps://docs.peppol.eu/poacc/billing/3.0/syntax/ubl-invoice/cac-AccountingCustomerParty/cac-Party/cac-Contact/cbc-Name/
Invoice.AccountingCustomerParty.Party.Contact.Telephonehttps://docs.peppol.eu/poacc/billing/3.0/syntax/ubl-invoice/cac-AccountingCustomerParty/cac-Party/cac-Contact/cbc-Telephone/
Invoice.AccountingCustomerParty.Party.Contact.ElectronicMailhttps://docs.peppol.eu/poacc/billing/3.0/syntax/ubl-invoice/cac-AccountingCustomerParty/cac-Party/cac-Contact/cbc-ElectronicMail/
Invoice.Delivery.DeliveryLocation.ID.Texthttps://docs.peppol.eu/poacc/billing/3.0/syntax/ubl-invoice/cac-Delivery/cac-DeliveryLocation/cbc-ID/
Invoice.Delivery.DeliveryLocation.PostalAddress.StreetNamehttps://docs.peppol.eu/poacc/billing/3.0/syntax/ubl-invoice/cac-Delivery/cac-DeliveryLocation/cac-Address/cbc-StreetName/
Invoice.Delivery.DeliveryLocation.PostalAddress.AdditionalStreetNamehttps://docs.peppol.eu/poacc/billing/3.0/syntax/ubl-invoice/cac-Delivery/cac-DeliveryLocation/cac-Address/cbc-AdditionalStreetName/
Invoice.Delivery.DeliveryLocation.PostalAddress.CityNamehttps://docs.peppol.eu/poacc/billing/3.0/syntax/ubl-invoice/cac-Delivery/cac-DeliveryLocation/cac-Address/cbc-CityName/
Invoice.Delivery.DeliveryLocation.PostalAddress.PostalZonehttps://docs.peppol.eu/poacc/billing/3.0/syntax/ubl-invoice/cac-Delivery/cac-DeliveryLocation/cac-Address/cbc-PostalZone/
Invoice.Delivery.DeliveryLocation.PostalAddress.CountrySubentityhttps://docs.peppol.eu/poacc/billing/3.0/syntax/ubl-invoice/cac-Delivery/cac-DeliveryLocation/cac-Address/cbc-CountrySubentity/
Invoice.Delivery.DeliveryLocation.PostalAddress.Country.IdentificationCode.Texthttps://docs.peppol.eu/poacc/billing/3.0/syntax/ubl-invoice/cac-Delivery/cac-DeliveryLocation/cac-Address/cac-Country/cbc-IdentificationCode/
Invoice.TaxPointDatehttps://docs.peppol.eu/poacc/billing/3.0/syntax/ubl-invoice/cbc-TaxPointDate/
Invoice.OrderReference.SalesOrderID.ID.Texthttps://docs.peppol.eu/poacc/billing/3.0/syntax/ubl-invoice/cac-OrderReference/cbc-SalesOrderID/
Invoice.AccountingCustomerParty.Party.PartyIdentification.ID.Texthttps://docs.peppol.eu/poacc/billing/3.0/syntax/ubl-invoice/cac-AccountingSupplierParty/cac-Party/cac-PartyIdentification/cbc-ID/
Invoice.InvoicePeriod.StartDatehttps://docs.peppol.eu/poacc/billing/3.0/syntax/ubl-invoice/cac-InvoicePeriod/cbc-StartDate/
Invoice.InvoicePeriod.EndDatehttps://docs.peppol.eu/poacc/billing/3.0/syntax/ubl-invoice/cac-InvoicePeriod/cbc-EndDate/
Invoice.ContractDocumentReference.ID.Texthttps://docs.peppol.eu/poacc/billing/3.0/syntax/ubl-invoice/cac-ContractDocumentReference/cbc-ID/
Invoice.AccountingCost (in progress)https://docs.peppol.eu/poacc/billing/3.0/syntax/ubl-invoice/cbc-AccountingCost/

orderline