Introduction

The purpose of this document is to explain how invoicing in Business NXT through the Visma.net AutoInvoice integration works using the PEPPOL BIS 3.0 Billing format.

This includes:
  • how the invoices are created and sent
  • how the invoice content is used to deliver the invoice
  • default and alternative mappings for fields used in PEPPOL BIS 3.0 Billing
  • PEPPOL BIS 3.0 Billing rules, and a description of how they work and which fields or calculation of field content that causes a particular rule to fail in sending
  • Rules listed in terms of format section and also alphabetically by Business NXT field names, cross referenced to mapping descriptions

For the official documentation of the PEPPOL BIS 3.0 Billing format, rules and codelists, go here.

As it is closely connected to the PEPPOL BIS 3.0 Billing format, the structure of this documentation is based on the structure of the format itself. Each chapter represents a main section of the format, and each header a subsection within it.

Format fields listed in the sections are presented in bold. All content fields start with cbc: followed by the field name. If the content field is found within a secondary subsection, or the field is one of the multiple cbc:ID fields in the format, the cbc: is preceded by a cac: field on the line above it that indicates what the cbc: contains. cac: fields have no content in themselves. At the end of each line, there will be an (O) or (M) . These indicate whether the field is optional or mandatory. Missing mandatory content will cause the invoice to fail. Note though that if an (M) is found within an (O), it means that the field is only mandatory if the section is included, and that we don't include the section in the output unless the mandatory field has content.

Under the field name is the mapping information, presented in italics. This is followed by an explanation of the field and related functionality in Business NXT, if any exists. Note that Business NXT fields are displayed by VBS identification, i.e. TableName.ColumnName. This makes it easier to identify both table and field in a single value in a readable format. Order related fields are shown as mapped from the Order document table, as this is where the data is taken from when the XML data is created, although the data must be set in corresponding fields in the Order table before the order is invoiced.
Note:
To display table and field names with VBS identification, select API identifiers under Management > Application settings in the menu . All fields referenced in this documentation are also listed in the Business NXT field reference topic, displaying field names in selected Business NXT language next to the VBS identification.