E-Invoice Data Mapping

JustOn Billing & Invoice Management generates electronic invoices on the basis of a standard mapping that aligns invoice data with the EN 16931 Semantic Model. The standard mapping covers the most common use cases for XRechnung UBL, Peppol BIS Billing UBL and ZUGFeRD CII output. For cases where the standard output does not match your specific business or tenant requirements, you can define custom field mappings without any code change.

In addition, you can control how invoice line items that reduce the invoiced amount are represented – either as itemized invoice lines or as document-level allowances and charges.

Default Mapping

The following table lists the e-invoice fields that JustOn Billing & Invoice Management sets by default in Peppol BIS Billing, XRechnung and ZUGFeRD files (see E-Invoice Formats), as well as their corresponding source objects and fields.

Custom Mapping

In some scenarios the standard mapping is not sufficient – for example, when a recipient requires additional business terms, when invoice data is stored in custom fields, or when a business term must hold a different static value than the one provided by JustOn Billing & Invoice Management. Custom e-invoice field mapping lets you override the standard mapping per business term, per format and per business entity, without any code change.

Custom field mappings let you override how JustOn Billing & Invoice Management fills individual fields in the outgoing e-invoice XML. Each override is addressed by its EN 16931 business term – for example, BT-22 for the invoice note or BT-20 for the payment terms – so you work with the e-invoice standard rather than with JustOn's internal data model.

For details on managing custom field mappings, see Configuring Custom E-Invoice Field Mappings.

Supported E-Invoice Formats

Custom field mapping is available for the following output formats:

• XRechnung UBL
• Peppol BIS Billing UBL
• ZUGFeRD

Avalara ELR country mandates use a mapping mechanism of their own, see Customizing Country Mandate.

Implementation Details

When JustOn Billing & Invoice Management generates an e-invoice, it first produces the standard output and then applies the active custom mapping on top: each active override replaces the value of the corresponding business term with either a Salesforce field value or a static value from the mapping configuration.

A custom mapping therefore always takes precedence over the standard mapping. This also applies to Avalara ELR country mandates, even though the mechanism differs: in this case, JustOn Billing & Invoice Management determines the value source per field, and for a field with a custom mapping, it does not evaluate the standard mapping at all.

A mapping configuration is always scoped to a combination of business entity and e-invoice format. Only one mapping configuration can be active at a time per combination, so activating a new configuration automatically supersedes the previous one for that pair.

Within a configuration, there can be multiple configuration entries. Each configuration entry holds one business term override setting, which is uniquely identified by its business term and target element. The same business term can therefore appear more than once in a configuration, but only when it targets different elements. Each configuration entry (within the mapping configuration) can be activated or deactivated individually.

Market-Specific Overrides

The standard mapping follows the business rules of EN 16931 and Peppol BIS Billing. Some of these rules omit or set a value depending on the invoice data. A country or market, however, may enforce values that go beyond these rules or override them.

For example, the business rule BR-O-02 prohibits the seller VAT identifier (BT-31) and the buyer VAT identifier (BT-48) on e-invoices that contain an invoice line with the VAT category code O (Services outside scope of tax). Consequently, JustOn Billing & Invoice Management omits both values in this case. The Portuguese clearance mandate PT-B2B-CLEARANCE, by contrast, always requires them.

Since a custom mapping always takes precedence over the standard mapping (see Implementation Details), it lets you provide such values: the custom mapping writes the value regardless of the rule that made the standard mapping omit it. Where to configure the custom mapping depends on the format:

Document-Level Allowances and Charges

Invoices may include offsetting positions, like bonuses or surcharges – invoice line items with a negative amount on invoices, invoice line items with a positive amount on credits. These invoice line items are balanced against the invoice amount.

By default, JustOn Billing & Invoice Management writes every invoice line item as an itemized invoice line (BG-25), including offsetting positions. As of v2.121, you can optionally have offsetting positions written as document-level allowances or charges instead. This may be necessary for specific target markets, because some mandates reject invoices whose invoice lines mix positive and negative amounts.

Data Mapping and Total Recalculation

With the option enabled, JustOn Billing & Invoice Management applies the following rules:

• Each offsetting position produces one dedicated allowance or charge.

  Invoice Class	Offsetting Position	Represented As
  Invoice	invoice line item with a negative net amount	BG-20 (DOCUMENT LEVEL ALLOWANCES)
  Credit	invoice line item with a positive net amount	BG-21 (DOCUMENT LEVEL CHARGES)

• All other invoice line items remain itemized invoice lines (BG-25).

• Allowance and charge amounts are always positive. The direction is expressed by the allowance/charge distinction alone, never by the sign of the amount.
• Each allowance or charge carries the VAT category code and the tax rate of the invoice line item it originates from.
• Invoice line items with a net amount of zero always remain invoice lines.

The offsetting positions are mapped as follows:

Moving offsetting positions out of the invoice lines changes the composition of the invoice totals (BG-22). JustOn Billing & Invoice Management recalculates the three affected sums so that the produced e-invoice remains arithmetically consistent:

All other invoice totals – among them BT-109, BT-112 and BT-115 – as well as the VAT breakdown (BG-23) keep the default mapping. Relocating an offsetting position does not change any amount: the net amount that leaves the invoice lines returns as an allowance or a charge, so the relation BT-109 = BT-106 - BT-107 + BT-108 continues to hold, and the VAT breakdown already accounts for the relocated amounts in the correct tax category.

Configuring the Option

The option is set per e-invoice format and per business entity, which lets you use it for one format while others keep the itemized representation. Where you set it depends on the format: