+49 541 9493-0  Kontakt  

SIEVERS XRechnung

At the beginning of 2025, the use of electronic invoices will become mandatory for German companies. First of all, you must be able to receive e-invoices, and from 2028 at the latest, you must also be able to send them. E-invoices are available in various formats. It is sufficient if you can process one of the formats. There are currently 3 approved e-invoice formats:

With SIEVERS XRechnung, we offer a solution that allows you to meet the legal requirements with extremely little effort: Installation and setup are completed in just a few minutes. You can then send and receive e-invoices with just two clicks. E-invoices are always exported in the latest version of the XRechnung, ZUGFeRD or Peppol format. The following formats can be imported:

The core features of SIEVERS XRechnung are:

Note
This document is for information purposes only. If used for other purposes, SIEVERS-SNC Computer & Software GmbH & Co. KG disclaims all warranties for defects in title and quality. SIEVERS-SNC Computer & Software GmbH & Co. KG disclaims all liability for direct and indirect damages - whether in contract or in law - arising out of or in connection with the use of this manual. This manual is subject to change without notice by SIEVERS-SNC Computer & Software GmbH & Co. KG without prior notice. The programs described may only be used or copied in accordance with the terms of the license. This document has been prepared for the support of end users, sales and service as well as developers and may be given to this group of persons without any changes. Copyright notice
Copyright © 2025 SIEVERS-SNC Computer & Software GmbH & Co. KG, a company of the SIEVERS-GROUP, Hans-Wunderlich Str.8, D-49078 Osnabrück, Germany. Microsoft, Microsoft Dynamics NAV and Business Central and DATEV are registered trademarks. All rights not expressly granted are reserved. Published by SIEVERS-SNC Computer & Software GmbH & Co. KG.

Changelog

In the following sections, there are important changes:

1 Overview

The SIEVERS XRechnung app generates an XML or PDF file that conforms to the XRechnung, ZUGFeRD or PEPPOL standards during the posting process of a sales order, a sales invoice, a sales credit note, a service invoice, a sales return order or credit note. This can be automatically sent to the recipient by email.

In order to enable these functions a setup of SIEVERS XRechnung is necessary. In the following 2. section you will be guided through the setup with the setup wizard.

On the start page, you will find the menu for XRechnung Setup, Export Document Overview and Import Document Overview, depending on your role.

2 Important Preliminary Information

3 Setup

SIEVERS XRechnung Setup on the Homescreen

You start the setup process of the App SIEVERS XRechnung by opening the page XRechnung Setup.

If SIEVERS XRechnung has not yet been set up a notification appears. This notification contains a link to the setup wizard.

Below you will be guided through the setup wizard of SIEVERS XRechnung.

In the first step of the setup wizard, activate the functionality for generating e-invoices by clicking the Active button. You can also select the default data format, specify the search order for standard item identification, enter a default e-mail text code, and decide for sales invoices and credit notes as well as service invoices and credit notes whether lines with zero amounts should be exported. In addition, you can also define an e-mail sender here. For more information about these fields, see the section XRechnung Setup. There are also other setup fields for alternative tax codes.

The goal of the next step is the assignment of your payment methods deposited in Microsoft Dynamics 365 Business Central to the UN/ECE 4461 codes required by XRechnung.

The action Add Payment Means EDIFACT Codes stores the codes supported by SIEVERS XRechnung in a table.

The action Payment Methods offers you the possibility to store the EDIFACT-Codes you generated previously.

In the next step you can use the action Customer to add information regarding your customers.

Note

Save time with ‘Activate selected customers with defaults’

The menu contains the option Activate selected customers with defaults. This option automatically performs the following steps for the selected customers:

  1. Activates SIEVERS XRechnung
  2. Automatically enters the buyer reference (see the sequence below for the field XRechnung buyer reference)
  3. Enter e-mail from customer
  4. First report found from report selection is automatically inserted based on document type

Deactivate selected customers to undo these changes.
These features save a lot of time – please be careful when using them.

Note

To get a better overview for which customers SIEVERS XRechnung is active, you can add the field XRechnung Active to the customer list via Personalize. The field is also displayed in the document overviews such as the sales order list.

Note

The buyer reference is an identification number for public clients of the federal administration. It is mandatory when sending an invoice to a public body, such as a public authority. The buyer reference is not required for invoices to private companies.

Note

If no buyer reference is entered, a buyer reference will automatically be adopted into the XRechnung. The following order of priority applies:

  1. VAT ID/UST ID
  2. GLN
  3. IBAN

If no information suitable as a buyer reference is found, an error message will appear.

Attention

The following restrictions apply in the service to the function XRechnung E-Mail Send at Batch Post:

If the desired function is not available in your version, use the **Send XRechnung Document* function in the document overviews instead after posting.

If you completed the setup steps regarding the customers you can close the overview and proceed to the next step with Next. If you want to make subsequent XRechnung settings to customers, you will find them on the customer card in the XRechnung tab.

If you do not use Business Central 18, you can complete the setup wizard here. Otherwise, the e-mail setup follows at this point. Please read the corresponding section for more information..

4 XRechnung Setup

On the XRechnung setup page, you can set up the basic solution. Among other things, you can

General

Export

Import

5 Generate e-invoices via Sales Order, Invoice, Credit Memo, Return Order or a Service Invoice or Credit Memo

Enter a Sales Order as usual, specify the Payment Method Code in the invoice details and release the Sales Order.

Note

If required, you can add Additional Supporting Documents to exports. Please read section 8. Additional Supporting Documents.

You can enter the start and end date using the line function Set E-Rechnung Start and End Date.

On the right side in the Details area you will find the XRechnung Note. Here you can store further information to be written into the XML file. Note that the characters “<”, “>” and “&” are not allowed.

You can execute a Test for XRechnung via Order. If mandatory fields are missing a log entry will be generated and displayed after the test. This test is also carried out automatically before each invoice posting.

If the test didn’t detect any errors you are able to finalize the order. For this purpose SIEVERS XRechnung has the feature to Post and send XRechnung with which the booking of the document and the sending of an e-mail with the file compliant to the standard XRechnung is done in one action.

Note

The Post and send XRechnung-Button is only visible, if an e-mail address is deposited in the customer card. If you have not deposited an e-mail address, you can also generate the XRechnung via Post.

You can also use this procedure for a sales invoice, credit memo or service invoice or credit memo and generate and send an XML file that conforms to the standard XRechnung.

The document for your XRechnung can be displayed in the Invoice or Sales Credit Memo.

This document contains the necessary information for a digital invoice compliant to the standard XRechnung.
In the field Filename you can find and retrieve the created XML file.
With the action Send E-Mail you can also send the e-mail to the recipient here.

Note

If a document contains a contact email, the XRechnung will be sent to that contact. Otherwise, the regular customer email will be used.

You can access the XRechnung sending history via the field XRechnung No. sent.

6 Create and Send multiple E-Invoices at the same time

After selecting any amount of orders via CTRL-Click on the orders overview page you can trigger processing of multiple orders at the same time via the action Post and Send XRechnung. As a result, these are posted and then an e-mail with the created XRechnung is sent in each case to the address stored at the customer.

Note

Please note that the XRechnung batch posting only works for customers who are active for XRechnung. Orders from customers for whom XRechnung is not active are not posted.

Multiple XRechnung invoice documents can also be send at once from the Posted Sales Invoices overview. To do this, select the action Send XRechnung Document

To facilitate multiselection, you can sort the list of posted invoices by XRechnung-customers.

7 Create E-Invoice Retrospectively

With SIEVERS XRechnung, you can also create e-invoices retrospectively if the sales invoice has already been posted. This also applies to customers for whom XRechnung has not yet been activated.

First, switch XRechnung active for the customers on the XRechnung Customers page. Then open the list of posted sales invoices. Here you will find the sub-item Show XRechnung Document in the menu under Invoice.

Here you are informed that no document yet exists and one can be created. Click Yes.

Now a regular XRechnung document has been created. Open it and send the document, for example, via e-mail.

8 XRechnung Payment Means EDIFACT Codes

On this page you have got the possibility to subsequently change or add new EDIFACT Codes, which ideally should have been assigned with the SIEVERS XRechnung setup wizard.

Furthermore you can restore the initally created EDIFACT Codes with the action Add/Reset Payment Means EDIFACT Codes. Manually created codes will not be touched by this.

9 E-Mails in SIEVERS XRechnung

With SIEVERS XRechnung, you can customise the e-mails used to send XRechnung invoices. These customised e-mail texts can be set up individually for each customer or a general text can be set up for all customers who have not stored an individual text. There are several ways to set up e-mail content. These are (in descending order of priority):

  1. Use of an internal event (please contact your SIEVERS partner for more information)
  2. E-mail body from the XRechnung setup: See Setup E-Mail Body
  3. Standard text codes in the customer or XRechnung setup. This includes a check for start and end dates and language code. See Set up e-mail content using standard text codes
  4. Standard text: ‘Attached you will find the XRechnung for document type document no.’.
  5. Default text overwritten by event (please contact your SIEVERS partner for more information)

Please note that a new setup is available for Business Central from version 18, which allows you to customise emails before sending them. See email setup from Business Central 18.

9.1 Setup E-Mail Body

To set up an email text, open the XRechnung setup and start the process with Setup E-Mail Body.

You can now enter the email text line by line. Tick Is HTML if you have used HTML code in the line. Alternatively, you can also import an HTML file for the content.

Example setup
This is how the example setup looks in an e-mail.

9.2 Set Up E-mail Content Using Standard Text Codes

If you want to create individual e-mails for your customers, you can use the standard text codes from Business Central. Open the text code list in the XRechnung Setup or in the customer via the E-Mail Standard Text Codes field and create as many codes as you like. Use Extended Texts to create the actual texts.

Note

Please note that you enter correct values in the language code and starting and ending date fields, as SIEVERS XRechnung checks these before creating the email.

You can now enter the standard text codes either directly in the corresponding field for the customer or in the XRechnung setup. Setup at the customer is preferred, provided that the language codes and starting and ending dates match. Otherwise, the text code entered will be adopted at the XRechnung setup.

The corresponding field at the customer. Enter the desired standard text code for e-mails here.

9.3 E-Mail Setup in BC18

Business Central 18 introduced the enhanced email capabilities and we already integrated them into SIEVERS XRechnung. This gives you the opportunity to use an email editor when sending an individual email or multiple emails via batch processing.

To be able to use the new capabilities you have to make the following settings:

The XRechnung Setup Wizard in BC18 got expanded with a new step.

Firstly ensure that the enhanced email capabilities are activated in the Feature Management.

Afterwards return to the setup wizard and open the window E-Mail Setup. Add a new email account via new. Then you have to assign the created account to XRechnung. For this open the Email Scenarios via Navigate.

Choose the correct account and search at Assign scenarios for XRechnung.

Afterwards the enhanced email capabilities setup is completed.

Now you have to select for which XRechnung customers the editor should be displayed. You can do this either directly in the customer card or at the customer list in the setup.

Note

Please note that the email editor will be also opened for every customer in case of a batch processing, if you activated Send XRechnung E-Mail at Batch Post.

If you want to send a XRechnung to a customer for whom you have activated the editor, said editor will open after you have clicked on Send XRechnung. If you have set an Email content, this will also be loaded automatically into the text field.

10 Export of Additional Supporting Documents

With SIEVERS XRechnung you can attach additional supporting documents to sales orders, invoices, credit memos and return orders as well as service orders, invoices and credit memos. These are attached to the XRechnung XML and the email.

To do this open the order/credit note/invoice. On the right-hand side you will find the box XRechnung Additional Supporting Documents in the details. The number of attachments is displayed here.

By clicking on the number, in this case 0, you open the overview. With Select File you can add files. The following file formats are allowed:

In total, all attachments must not exceed 14.5 MB in size.

When you added a file you can also enter a description. This will be written into the XML-file.

With Preview all files you have added so far are downloaded and can be checked again before sending.

If necessary, please also note our partner documentation in order to add additional supporting documents via code with an event.

11 Usage Of Alternative Tax Identifiers

In the SIEVERS XRechnung setup, you can select alternatives to the normal VAT ID if your situation requires it.

By default, VAT Reg. No. Usage is set to *Company information**. This will cause the VAT ID from the company information to be used when creating XRechnungen. Furthermore you can select here

Depending on the selection, you must fill in one of the other fields.

For Sellers tax identifier, fill in the corresponding field with the identifier or a reference to the registered tax status.

If you have selected Tax representative, you must enter the VAT ID of the tax representative in the corresponding field. In addition, the Our account no. field in the accounts receivable cards must be filled. This is due to the fact that the unique identification usually runs through the VAT ID. If this is missing, there must be another way of unique identification. This function is performed by the account number. For more information on the subject, search for the keyword BR-CO-26. This is a condition for the use of XRechnung.

12 Use Classic Report Layout in NAV2009

With SIEVERS XRechnung, NAV2009 supports not only RDLC layouts, but also the Classic Layout. To do this, a few settings must be made.

Note

If the Classic Report Layout is used instead of RDLC, no service tier is necessary.

  1. In PDF24, the following settings must be made in the PDF Printer menu:

  1. In NAV, the following settings must be made in the PDF Print menu:

Note

Please note that the file names differ in the PDF24 and NAV settings. In PDF24, the file name must be written without .pdf and in the NAV settings with .pdf.

13 XRechnung Document List

On this list, you can view the export documents that have been created. You can also send an e-mail with the document and access the linked customer.

The following information can be viewed here:

14 XRechnung Document

The generated XRechnung document is shown here. Here you can review the information that has been generated and transmitted. You can also access the associated XML via Filename and the e-mail log via No. Sent. In addition, it is possible to send an e-mail and to display the customer. It is not possible to change the contents of the document retrospectively.

Note

It is possible to customise the name, phone number and email address before generating the XML file. To do this, please contact your SIEVERS partner or the SIEVERS-GROUP directly.

15 Import

With the XRechnung Import, you can import e-invoice XML or PDF files. The following describes how this works and what you need to be aware of.

15.1 XRechnung Import Overview

The XRechnung Import Overview is the central Business Central page that controls the import. Here you have an overview of current imports without assigned purchasing documents and can import new XRechnung or ZUGFeRD invoices. You can view finished imports that have assigned purchasing documents via the Import Archive.

Note

Please ensure that imported files have the following formats:

You can import both the XML file itself or a PDF with embedded XML.

15.2 Import Process

The import process of an XRechnung works like this:

  1. open the XRechnung import overview.
  2. Click on Import XRechnung file in the Menu and select your desired file.
  3. Then check the imported data by clicking on the receipt line in the Import document and correct it if necessary. You should pay particular attention to the following fields:
  4. Generate a purchase document from the document via menu. You can open and process the generated document via show purchase document. If there are surcharges and/or discounts in the file, these must be assigned to the items in the purchase invoice.
  5. Assign the XRechnung import lines to a receipt, receipt lines and a location via the import check worksheet or lines in the import document.
  6. After the purchasing document has been created, the XRechnung is transferred to the import archive. The archived XRechnung document is shown in the XRechnung section of the generated purchasing document and can be accessed from there.
Note

If errors occur, these are listed in the Import log.

When the document is imported, it is assigned to a vendor. The assignment is made using one of these fields:

In addition, the invoice lines are automatically assigned to items and G/L accounts. The assignment of the items is done by matching in this order:

  1. Item references
  2. GTIN
  3. Description
  4. Sellers Item Identification
  5. Item No.
  6. Item Charge

G/L accounts are searched for in the following order using the XRechnung import line:

  1. Description
  2. Seller Item Identification
  3. Text for account
  4. Standard accounts from Purchases & Payables Setup

In principle, the first data record found is assigned.

Note

If this automatic assignment is not desired, it can also be influenced using events. Please contact your SIEVERS partner about this.

15.3 Import Menu

The menu has the following functions:

15.4 Import document

The import document is the overview of a finished imported XRechnung from a PDF or XML. You can see here whether all the data is correct and correct it if necessary. The menu displayed here is identical to the menu from the overview page.

You can view the following data here:

General

This area contains general information. On the right side you can see a possible note in the XRechnung.

Vendor

Company Information

Amounts

Additional supporting documents

Any additional supporting documents are shown here. These are adopted as attachments when the purchasing document is created.

Note

If you have received the function for importing additional supporting documents via software update from SIEVERS, you must create the data exchange definitions again before using it. To do this, execute the Create data exchange definitions action on the corresponding page.
If you have reinstalled SIEVERS XRechnung, this step is not necessary.

Lines

Contains the receipt lines of the XRechnung. Please check these for correctness.

The XRechnung import module attempts to find the item, G/L account or asset based on the following characteristics and to automatically fill in the type and no. from Business Central tables:

If nothing can be found, an error is displayed in the import log. The user must then take manual action and manually assign the unclear lines to the items/G/L accounts/assets maintained in Business Central.

The last line in the screenshot shows a resource that cannot be utilized in purchasing. In order to be able to transfer the file to a purchasing invoice anyway, you can use the Do not insert in purchasing document radio button on the left to exclude this line from being transferred to the invoice.

Also make sure that the Unit of measure code file and Unit of measure code Business Central are assigned correctly.

15.4.1 Import Review Worksheet

You can use the verification worksheet to compare the imported e-invoice lines with the order lines of the purchase order. You can then edit the e-invoice lines as you wish or decide that they should not be transferred to the purchasing document.

You assign the e-invoice import lines to goods receipts and thus also to goods receipt lines and Location Codes via import lines.

This can also be done by lookup in the last purchase delivery lines.

The e-invoice and the purchasing document are then linked.

Click this button if the line should not be transferred.

In both the review worksheet and the goods receipt overview, you can activate a switch that displays all purchase order lines and posted purchase receipt lines for the vendor. This simplifies the assignment of e-invoices.

Show all vendor purchasing delivery lines in the goods receipt overview
Show all purchase order lines and purchasing delivery lines in the review worksheet

15.5 Import Archive List

E-invoices that have been converted to purchasing documents are stored in this archive. From here, you can access the document itself and show the associated posted purchasing document and the import log.

15.6 Import Log

Errors that occur during import are collected in this log and shown separately. In this case, for example, the vendor cannot be found and must be selected manually.

15.7 Generated purchase invoice

A purchase invoice generated correctly by the import looks like this:

As you can see, a regular purchase invoice is generated on the basis of the e-invoice. It is no different from a manually generated invoice.

If additions and deductions need to be assigned, you can do this here. To do this, change the Quantity to assign in the surcharge and budget billing lines.

15.8 Data Exchange Types

You only need to access this page if an import is not possible or if the import works without errors even if the imported data is faulty. In exceptional cases, this may be because data exchange types were not automatically entered when SIEVERS XRechnung was installed. If this is the case, the data exchange types table is empty. If this is the case, you can use Create data exchange definitions to catch up on this step. After that, the import should work without errors.

Example of a filled data exchange type table

15.9 Text-to-Account Mappings

With SIEVERS XRechnung, you can automatically assign invoices to G/L accounts, items or charges. To do this, open the page with the action Map Text to Account via Import Overview.

You can enter the following here:

If you have correctly filled out this line, the next suitable e-invoice will be assigned to the corresponding G/L account.

It will happen regularly that products or lines cannot be identified correctly or that it is a non-item position. For these cases, you should set up default debit and credit accounts. This is what the action Set Up Default Accounts for Non-Item Lines is for. This opens the purchases & payables setup with the default accounts section.

15.10 Automating the import

It is possible to automate the import of files via the job queue to a large extent. Please contact your SIEVERS-GROUP partner for more information.

When the job queue is running, the files are added to the import job queue overview. You can access this via the menu in the import overview. From here, you can start processing the file via Run Import Job Codeunit. This step is only necessary on a temporary basis, as a complete automation is in the works.

16 Additional Notes

16.1 International Standard Code

Please make sure that all units of measure you use in e-invoice have the International Standard Code field maintained. Use the UNECERec20 list for this purpose.

16.2 Specifying a VAT Category Code

If you specify a code in the VAT Category Code (BT-118) that implies VAT exemption, you must also specify a VAT Exemption Reason Text (BT-120). In Business Central, the VAT Clause Code field is used for this purpose. If the field is not filled, an error will occur in the e-invoice validation check.

16.3 XRechnung Periods in Sales and Service

In service orders, service invoices and service credit memos, as well as in the sales documents of the same name, an XRechnung start and end date can be added at line item level.

This data is also adopted in posted sales and service documents and the XRechnung document.

The XRechnung dates in posted service invoices
Start and end date in XRechnung document

17 Frequently Asked Questions

Hopefully, this section will answer your questions. If this is not the case, do not hesitate to contact our support.















18 BC-Fields - BT-Fields Mapping

18.1 Export

You may want to attach custom information to the exported and sent XML files. However, in SIEVERS XRechnung, many XML fields specified by the XRechnung standard are already filled with content. The following table is an overview of all BT fields used in SIEVERS XRechnung and their corresponding Business Central fields.

Attention

Please note that the fields BT-16, BT-49, BT-57, BT-58, BT-73 and BT-74 are not available in NAV 2016!

BC Table BC Field BT Field BT ID XML Element
SNCXXRechnungHeader Document No. ID BT-1 /Invoice/cbc:ID
SNCXXRechnungHeader Document Date IssueDate BT-2 /Invoice/cbc:IssueDate
SNCXXRechnungHeader Due Date DueDate BT-9 /Invoice/cbc:DueDate
SNCXXRechnungHeader Document Type InvoiceTypeCode BT-3 /Invoice/cbc:InvoiceTypeCode
SNCXXRechnungHeader Currency Code DocumentCurrencyCode BT-5 /Invoice/cbc:DocumentCurrencyCode
SNCXXRechnungHeader Currency Code TaxCurrencyCode BT-6 /Invoice/cbc:TaxCurrencyCode
SNCXXRechnungHeader Posting Date TaxPointDate BT-7 /Invoice/cbc:TaxPointDate
SNCXXRechnungCustomer XRechnung Buyer Reference BuyerReference BT-10 /Invoice/cbc:BuyerReference
SNCXXRechnungHeader Document No. ID BT-12 /Invoice/cbc:ID
SNCXXRechnungHeader External Document No. OrderReference BT-13 /Invoice/cac:OrderReference/cbc:ID
SNCXXRechnungHeader DespatchDocumentReferenceText DespatchDocumentReference ID BT-16 /Invoice/cac:DespatchDocumentReference/cbc:ID
Filename AdditionalDocumentReference ID BT-122 /Invoice/cac:AdditionalDocumentReference/cbc:ID
SNCXXRechnungAddSuppDoc Description Document Description BT-123 /Invoice/cac:AdditionalDocumentReference/cbc:DocumentDescription
BankAccount Creditor No. AccountingSupplierParty Party PartyIdentification ID BT-29, BT-90 /Invoice/cac:AccountingSupplierParty/cac:Party/cac:PartyIdentification/cbc:ID
XRechnung Note Note BT-22 /Invoice/cbc:Note
BankAccount Creditor No. AccountingSupplierParty Party PartyIdentification ID BT-29, BT-90 /Invoice/cac:AccountingSupplierParty/cac:Party/cac:PartyIdentification/cbc:ID
BankAccount Our Account No. AccountingSupplierParty Party PartyIdentification ID BT-29, BT-90 /Invoice/cac:AccountingSupplierParty/cac:Party/cac:PartyIdentification/cbc:ID
CompanyInformation E-Mail Address (Not in CII) or GLN AccountingSupplierParty Party EndpointID BT-34 /Invoice/cac:AccountingSupplierParty/cac:Party/cbc:EndpointID
CompanyInformation Address AccountingSupplierParty Party PostalAddress StreetName BT-35 /Invoice/cac:AccountingSupplierParty/cac:Party/cac:PostalAddress/cbc:StreetName
CompanyInformation Address 2 AccountingSupplierParty Party PostalAddress AdditionalStreetName BT-36 /Invoice/cac:AccountingSupplierParty/cac:Party/cac:PostalAddress/cbc:AdditionalStreetName
CompanyInformation City AccountingSupplierParty Party PostalAddress CityName BT-37 /Invoice/cac:AccountingSupplierParty/cac:Party/cac:PostalAddress/cbc:CityName
CompanyInformation Post Code AccountingSupplierParty Party PostalAddress PostalZone BT-38 /Invoice/cac:AccountingSupplierParty/cac:Party/cac:PostalAddress/cbc:PostalZone
CompanyInformation Country/Region Code AccountingSupplierParty Party PostalAddress Country IdentificationCode BT-40 /Invoice/cac:AccountingSupplierParty/cac:Party/cac:PostalAddress/cac:Country/cbc:IdentificationCode
CompanyInformation VAT Registration No. AccountingSupplierParty Party PartyTaxScheme CompanyID BT-31, BT-32 /Invoice/cac:AccountingSupplierParty/cac:Party/cac:PartyTaxScheme/cbc:CompanyID
CompanyInformation VAT Registration No. AccountingSupplierParty Party PartyTaxScheme CompanyID BT-31, BT-32 /Invoice/cac:AccountingSupplierParty/cac:Party/cac:PartyTaxScheme/cbc:CompanyID
CompanyInformation Name AccountingSupplierParty Party PartyName Name BT-28 /Invoice/cac:AccountingSupplierParty/cac:Party/cac:PartyName/cbc:Name
Salesperson Name AccountingSupplierParty Party Contact Name BT-41 /Invoice/cac:AccountingSupplierParty/cac:Party/cac:Contact/cbc:Name
Salesperson Phone No. AccountingSupplierParty Party Contact Telephone BT-42 /Invoice/cac:AccountingSupplierParty/cac:Party/cac:Contact/cbc:Telephone
Salesperson E-Mail AccountingSupplierParty Party Contact ElectronicMail BT-43 Invoice/cac:AccountingSupplierParty/cac:Party/cac:Contact/cbc:ElectronicMail
CompanyInformation Contact Person AccountingSupplierParty Party Contact Name BT-41 /Invoice/cac:AccountingSupplierParty/cac:Party/cac:Contact/cbc:Name
CompanyInformation Phone No. AccountingSupplierParty Party Contact Telephone BT-42 /Invoice/cac:AccountingSupplierParty/cac:Party/cac:Contact/cbc:Telephone
CompanyInformation E-Mail AccountingSupplierParty Party Contact ElectronicMail BT-43 /Invoice/cac:AccountingSupplierParty/cac:Party/cac:Contact/cbc:ElectronicMail
SNCXXRechnungHeader Bill-to Customer No. AccountingCustomerParty Party PartyIdentification ID BT-46 /Invoice/cac:AccountingCustomerParty/cac:Party/cac:PartyIdentification/cbc:ID
SNCXXRechnungHeader Bill-to Address AccountingCustomerParty Party PostalAddress StreetName BT-50 /Invoice/cac:AccountingCustomerParty/cac:Party/cac:PostalAddress/cbc:StreetName
SNCXXRechnungHeader Bill-to Address 2 AccountingCustomerParty Party PostalAddress AdditionalStreetName BT-51 /Invoice/cac:AccountingCustomerParty/cac:Party/cac:PostalAddress/cbc:AdditionalStreetName
SNCXXRechnungHeader Bill-to City AccountingCustomerParty Party PostalAddress CityName BT-52 /Invoice/cac:AccountingCustomerParty/cac:Party/cac:PostalAddress/cbc:CityName
SNCXXRechnungHeader Bill-to Post Code AccountingCustomerParty Party PostalAddress CityName BT-53 /Invoice/cac:AccountingCustomerParty/cac:Party/cac:PostalAddress/cbc:CityName
SNCXXRechnungHeader Bill-to Country/Region Code AccountingCustomerParty Party PostalAddress Country IdentificationCode BT-55 /Invoice/cac:AccountingCustomerParty/cac:Party/cac:PostalAddress/cac:Country/cbc:IdentificationCode
SNCXXRechnungHeader Bill-to Name + Bill-to Name 2 AccountingCustomerParty Party PartyName Name BT-45 /Invoice/cac:AccountingCustomerParty/cac:Party/cac:PartyName/cbc:Name
SNCXXRechnungCustomer XRechnung E-Mail or GLN AccountingCustomerParty Party EndpointID BT-49 /Invoice/cac:AccountingCustomerParty/cac:Party/cbc:EndpointID
SNCXXRechnungHeader Bill-to Contact AccountingCustomerParty Party Contact Name BT-56 /Invoice/cac:AccountingCustomerParty/cac:Party/cac:Contact/cbc:Name
SNCXXRechnungHeader Bill-to Contact Phone No. AccountingCustomerParty Party Contact Telephone BT-57 /Invoice/cac:AccountingCustomerParty/cac:Party/cac:Contact/cbc:Telephone
SNCXXRechnungHeader Bill-to Contact E-Mail AccountingCustomerParty Party Contact ElectronicMail BT-58 /Invoice/cac:AccountingCustomerParty/cac:Party/cac:Contact/cbc:ElectronicMail
CompanyInformation VAT Representative TaxRepresentativeParty PartyName Name BT-62 /Invoice/cac:TaxRepresentativeParty/cac:PartyName/cbc:Name
CompanyInformation Address TaxRepresentativeParty PostalAddress StreetName BT-64 /Invoice/cac:TaxRepresentativeParty/cac:PostalAddress/cbc:StreetName
CompanyInformation City TaxRepresentativeParty PostalAddress CityName BT-66 /Invoice/cac:TaxRepresentativeParty/cac:PostalAddress/cbc:CityName
CompanyInformation Post Code TaxRepresentativeParty PostalAddress PostalZone BT-67 /Invoice/cac:TaxRepresentativeParty/cac:PostalAddress/cbc:PostalZone
CompanyInformation VAT Registration No. TaxRepresentativeParty PartyTaxScheme CompanyID BT-63 /Invoice/cac:TaxRepresentativeParty/cac:PartyTaxScheme/cbc:CompanyID
SNCXXRechnungHeader Shipment Date Delivery ActualDeliveryDate BT-72 /Invoice/cac:Delivery/cbc:ActualDeliveryDate
SNCXXRechnungHeader Start Date InvoicePeriod StartDate BT-73 /Invoice/InvoicePeriod/StartDate
SNCXXRechnungHeader End Date InvoicePeriod EndDate BT-74 /Invoice/cac:InvoicePeriod/cbc:EndDate
SNCXXRechnungHeader Ship-to Address Delivery DeliveryLocation Address StreetName BT-75 /Invoice/cac:Delivery/cac:DeliveryLocation/cac:Address/cbc:StreetName
SNCXXRechnungHeader Ship-to Address 2 Delivery DeliveryLocation Address AdditionalStreetName BT-76 /Invoice cac:Delivery/cac:DeliveryLocation/cac:Address/cbc:AdditionalStreetName
SNCXXRechnungHeader Ship-to City Delivery DeliveryLocation Address CityName BT-77 /Invoice cac:Delivery cac:DeliveryLocation cac:Address cbc:CityName
SNCXXRechnungHeader Ship-to Post Code Delivery DeliveryLocation Address PostalZone BT-78 /Invoice/cac:Delivery/cac:DeliveryLocation/cac:Address/cbc:PostalZone
SNCXXRechnungHeader Ship-to Country/Region Code Delivery DeliveryLocation Address Country IdentificationCode BT-80 /Invoice/cac:Delivery/cac:DeliveryLocation/cac:Address/cac:Country/cbc:IdentificationCode
SNCXXRechnungHeader Ship-to Name Delivery DeliveryParty PartyName Name BT-70 /Invoice/cac:Delivery/cac:DeliveryParty/cac:PartyName/cbc:Name
PaymentMethod EDIFACT Payment Means Code SNC PaymentMeans PaymentMeansCode BT-81 /Invoice/cac:PaymentMeans/cbc:PaymentMeansCode
CompanyInformation IBAN PaymentMeans PayeeFinancialAccount ID BT-84 /Invoice/cac:PaymentMeans/cac:PayeeFinancialAccount/cbc:ID
SEPA Direct Debit Mandate ID PaymentMeans PaymentMandate ID BT-89 /Invoice/cac:PaymentMeans/cac:PaymentMandate/cbc:ID
SEPA Direct Debit Mandate ID PaymentMeans PaymentMandate PayerFinancialAccount ID BT-91 /Invoice/cac:PaymentMeans/cac:PaymentMandate/cac:PayerFinancialAccount/cbc:ID
SNCXXRechnungHeader Payment Terms Description PaymentTerms Note BT-20 /Invoice/cac:PaymentTerms/cbc:Note
SNCXXRechnungLine Description AllowanceCharge AllowanceChargeReason BT-97, BT-104 /Invoice/cac:AllowanceCharge/cbc:AllowanceChargeReason
SNCXXRechnungLine Net Line Amount AllowanceCharge Amount BT-92, BT-99 /Invoice/cac:AllowanceCharge/cbc:Amount
VATPostingSetup Tax Category AllowanceCharge TaxCategory ID BT-95, BT-102 /Invoice/cac:AllowanceCharge/cac:TaxCategory/cbc:ID
SNCXXRechnungLine VAT % AllowanceCharge TaxCategory Percent BT-96, BT-103 /Invoice/cac:AllowanceCharge/cac:TaxCategory/cbc:Percent
SNCXXRechnungHeader VAT Amount TaxTotal TaxAmount BT-110, BT-111 /Invoice/cac:TaxTotal/cbc:TaxAmount
TempVATLine Net Line Amount TaxTotal TaxSubtotal TaxableAmount BT-116 /Invoice/cac:TaxTotal/cac:TaxSubtotal/cbc:TaxableAmount
TempVATLine VAT Amount TaxTotal TaxSubtotal TaxAmount BT-117 /Invoice/cac:TaxTotal/cac:TaxSubtotal/cbc:TaxAmount
VATPostingSetup Tax Category TaxTotal TaxSubtotal TaxCategory ID BT-118 /Invoice/cac:TaxTotal/cac:TaxSubtotal/cac:TaxCategory/cbc:ID
TempVATLine VAT % TaxTotal TaxSubtotal TaxCategory Percent BT-119 /Invoice/cac:TaxTotal/cac:TaxSubtotal/cac:TaxCategory/cbc:Percent
VATPostingSetup VAT Clause Code TaxTotal TaxSubtotal TaxCategory TaxExemptionReason BT-120 /Invoice/cac:TaxTotal/cac:TaxSubtotal/cac:TaxCategory/cbc:TaxExemptionReason
SNCXXRechnungHeader Net Total Amount wo. Charge LegalMonetaryTotal LineExtensionAmount BT-106 /Invoice/cac:LegalMonetaryTotal/cbc:LineExtensionAmount
SNCXXRechnungHeader Net Total Amount LegalMonetaryTotal TaxExclusiveAmount BT-109 /Invoice/cac:LegalMonetaryTotal/cbc:TaxExclusiveAmount
SNCXXRechnungHeader Gross Total Amount LegalMonetaryTotal TaxInclusiveAmount BT-112 /Invoice/cac:LegalMonetaryTotal/cbc:TaxInclusiveAmount
SNCXXRechnungLine Net Line Amount LegalMonetaryTotal ChargeTotalAmount BT-108 /Invoice/cac:LegalMonetaryTotal/cbc:ChargeTotalAmount
SNCXXRechnungHeader Gross Total Amount LegalMonetaryTotal PayableAmount BT-115 /Invoice/cac:LegalMonetaryTotal/cbc:PayableAmount
SNCXXRechnungLine Line No. InvoiceLine ID BT-126 /Invoice/cac:InvoiceLine/cbc:ID
SNCXXRechnungLine Quantity InvoiceLine InvoicedQuantity BT-129 /Invoice/cac:InvoiceLine/cbc:InvoicedQuantity
SNCXXRechnungLine Quantity InvoiceLine InvoicedQuantity UnitCode BT-130 /Invoice/cac:InvoiceLine/cbc:InvoicedQuantity/@unitCode
SNCXXRechnungLine Net Line Amount InvoiceLine LineExtensionAmount BT-131 /Invoice/cac:InvoiceLine/cbc:LineExtensionAmount
SNCXXRechnungLine Description InvoiceLine Item Name BT-153 /Invoice/cac:InvoiceLine/cac:Item/cbc:Name
SNCXXRechnungLine No. InvoiceLine Item SellersItemIdentification ID BT-155 /Invoice/cac:InvoiceLine/cac:Item/cac:SellersItemIdentification/cbc:ID
SNCXXRechnungLine GTIN InvoiceLine Item StandardItemIdentification ID BT-157 /Invoice/cac:InvoiceLine/cac:Item/cac:StandardItemIdentification/cbc:ID
VATPostingSetup Tax Category InvoiceLine Item ClassifiedTaxCategory ID BT-151 /Invoice/cac:InvoiceLine/cac:Item/cac:ClassifiedTaxCategory/cbc:ID
SNCXXRechnungLine VAT % InvoiceLine Item ClassifiedTaxCategory Percent BT-152 /Invoice/cac:InvoiceLine/cac:Item/cac:ClassifiedTaxCategory/cbc:Percent
SNCXXRechnungLine Net Unit Price InvoiceLine Price PriceAmount BT-146 /Invoice/cac:InvoiceLine/cac:Price/cbc:PriceAmount
SNCXXRechnungLine Start Date InvoiceLine InvoicePeriod StartDate BT-134 /Invoice/cac:InvoiceLine/cac:InvoicePeriod/cbc:StartDate
SNCXXRechnungLine End Date InvoiceLine InvoicePeriod EndDate BT-135 /Invoice/cac:InvoiceLine/cac:InvoicePeriod/cbc:EndDate

18.2 Import

18.2.1 Purchase Header

Business Term (BT) Optional UBL (BT) Feld XML Element UBL CII (BT) Feld XML Element CII Intermediate Record XRechnung Record Purchase Header Record Usage
BT-1 ID /Invoice/cbc:ID ID /rsm:CrossIndustryInvoice/rsm:ExchangedDocument/ram:ID Purchase Header - Field 68 Vendor Invoice No. SNCX XRechnung Import Header.”Document No.” and “Vendor Invoice No.” Purchase Header.”Vendor Invoice No.”
BT-2 IssueDate /Invoice/cbc:IssueDate DateTimeString /rsm:CrossIndustryInvoice/rsm:ExchangedDocument/ram:IssueDateTime/udt:DateTimeString Purchase Header - Field 99 Document Date SNCX XRechnung Import Header.”Document Date” Purchase Header.”Document Date”
BT-3 InvoiceTypeCode /Invoice/cbc:InvoiceTypeCode TypeCode /rsm:CrossIndustryInvoice/rsm:ExchangedDocument/ram:TypeCode Purchase Header - Field 1 Document Type SNCX XRechnung Import Header.”Document Type” PurchaseHeader.”Document Type”
BT-5 DocumentCurrencyCode /Invoice/cbc:DocumentCurrencyCode InvoiceCurrencyCode /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:InvoiceCurrencyCode Purchase Header - Field 32 Currency Code SNCX XRechnung Import Header.”Currency Code” Purchase Header.”Currency Code”
BT-9 DueDate /Invoice/cbc:DueDate DateTimeString /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:SpecifiedTradePaymentTerms/ram:DueDateDateTime/udt:DateTimeString Purchase Header - Field 24 Due Date SNCX XRechnung Import Header.”Due Date” PurchaseHeader.”Due Date”
BT-13 X ID /Invoice/cac:OrderReference/cbc:ID IssuerAssignedID /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:BuyerOrderReferencedDocument/ram:IssuerAssignedID Purchase Header - Field 66 Vendor Order No. SNCX XRechnung Import Header.”Vendor Order No.” Purchase Header.”Vendor Order No.”
BT-24 CustomizationID /Invoice/cbc:CustomizationID ID /rsm:CrossIndustryInvoice/rsm:ExchangedDocumentContext/ram:GuidelineSpecifiedDocumentContextParameter/ram:ID Not used Not used Not used Purchase Header - Field 0 Version No. for comparing the version of the file with the current version.
BT-25 ID /CreditNote/cac:BillingReference/cac:InvoiceDocumentReference/cbc:ID IssuerAssignedID /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:InvoiceReferencedDocument/ram:IssuerAssignedID Purchase Header - Field 53 Applies-to Doc. No. SNCX XRechnung Import Header.”Applies-to Doc. No.” Purchase Header.”Applies-to Doc. No.”
BT-27 RegistrationName /Invoice/cac:AccountingSupplierParty/cac:Party/cac:PartyLegalEntity/cbc:RegistrationName Name /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:Name Purchase Header - Field 79 Buy-from Vendor Name SNCX XRechnung Import Header.”Buy-from Vendor Name” Not used Find Buy from Vendor with Name
BT-29 ID /Invoice/cac:AccountingSupplierParty/cac:Party/cac:PartyIdentification/cbc:ID[@schemeID=''0088''] ID /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:ID[@schemeID=''0088''] Purchase Header - Field 2 Buy-from Vendor No. (GLN) SNCX XRechnung Import Header.”Buy-from Vendor GLN” Not used Find Buy from Vendor with GLN
BT-29 ID /Invoice/cac:AccountingSupplierParty/cac:Party/cac:PartyIdentification/cbc:ID[@schemeID!=''0088''] ID /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:ID[@schemeID!=''0088''] Vendor - Field 86 VAT Registration No. SNCX XRechnung Import Header.”Buy-from Vendor VAT Reg. No.” Not used Find Buy from Vendor with VAT Reg. No.
BT-31 ID /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:SpecifiedTaxRegistration/ram:ID[@schemeID=''VA''] Vendor - Field 86 VAT Registration No. SNCX XRechnung Import Header.”Buy-from Vendor VAT Reg. No.” Not used Find Buy from Vendor with VAT Reg. No.
BT-34 EndpointID /Invoice/cac:AccountingSupplierParty/cac:Party/cbc:EndpointID[@schemeID=''EM''] GlobalID /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:GlobalID[@schemeID=''EM''] Purchase Header - Field 13 Ship-to Name SNCX XRechnung Import Header.”Buy-from Vendor E-Mail” Not used Find Buy from Vendor with E-Mail
BT-34 EndpointID /Invoice/cac:AccountingSupplierParty/cac:Party/cbc:EndpointID[@schemeID=''0088''] GlobalID /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:GlobalID[@schemeID=''0088''] Purchase Header - Field 2 Buy-from Vendor No. (GLN) SNCX XRechnung Import Header.”Buy-from Vendor GLN” Not used Find Buy from Vendor with GLN
BT-34 EndpointID /Invoice/cac:AccountingSupplierParty/cac:Party/cbc:EndpointID[@schemeID!=''0088''and@schemeID!=''EM''] GlobalID /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:GlobalID[@schemeID!=''0088''and@schemeID!=''EM''] Vendor - Field 86 VAT Registration No. SNCX XRechnung Import Header.”Buy-from Vendor VAT Reg. No.” Not used Find Buy from Vendor with VAT Reg. No.
BT-35 X StreetName /Invoice/cac:AccountingSupplierParty/cac:Party/cac:PostalAddress/cbc:StreetName LineOne /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:PostalTradeAddress/ram:LineOne Purchase Header - Field 81 Buy-from Address SNCX XRechnung Import Header.”Buy-from Address” Not used Find Buy from Vendor with Address
BT-46 X ID /Invoice/cac:AccountingCustomerParty/cac:Party/cac:PartyIdentification/cbc:ID ID /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:BuyerTradeParty/ram:ID Company Information - Field 90 GLN SNCX XRechnung Import Header.”Company Info GLN” Not used Find Company Info with GLN
BT-48 X CompanyID /Invoice/cac:AccountingCustomerParty/cac:Party/cac:PartyTaxScheme/cbc:CompanyID ID /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:BuyerTradeParty/ram:SpecifiedTaxRegistration/ram:ID Company Information - Field 19 VAT Registration No. SNCX XRechnung Import Header.”Company Info VAT Reg. No.” Not used Find Company Info with VAT Reg. No.
BT-48 X CompanyID /Invoice/cac:AccountingCustomerParty/cac:Party/cac:PartyLegalEntity/cbc:CompanyID[@schemeID!=''0088''] ID /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:BuyerTradeParty/ram:SpecifiedTaxRegistration/ram:ID Company Information - Field 19 VAT Registration No. SNCX XRechnung Import Header.”Company Info VAT Reg. No.” Not used Find Company Info with VAT Reg. No.
BT-49 X EndpointID /Invoice/cac:AccountingCustomerParty/cac:Party/cbc:EndpointID[@schemeID=''EM''] ID /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:BuyerTradeParty/ram:URIUniversalCommunication/ram:URIID[@schemeID=''EM''] Company Information - Field Field 34 E-Mail SNCX XRechnung Import Header.”Company Information E-Mail” Not used Find Company Info with E-Mail
BT-49 X EndpointID /Invoice/cac:AccountingCustomerParty/cac:Party/cbc:EndpointID[@schemeID=''0088''] ID /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:BuyerTradeParty/ram:URIUniversalCommunication/ram:URIID[@schemeID=''0088''] Company Information - Field 90 GLN SNCX XRechnung Import Header.”Company Info GLN” Not used Find Company Info with GLN
BT-49 X EndpointID /Invoice/cac:AccountingCustomerParty/cac:Party/cbc:EndpointID[@schemeID!=''0088''and@schemeID!=''EM''] ID /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:BuyerTradeParty/ram:URIUniversalCommunication/ram:URIID[@schemeID!=''0088''and@schemeID!=''EM''] Company Information - Field 19 VAT Registration No. SNCX XRechnung Import Header.”Company Info VAT Reg. No.” Not used Find Company Info with VAT Reg. No.
BT-50 X StreetName /Invoice/cac:AccountingCustomerParty/cac:Party/cac:PostalAddress/cbc:StreetName LineOne /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:BuyerTradeParty/ram:PostalTradeAddress/ram:LineOne Company Information - Field 4 Address SNCX XRechnung Import Header.”Company Info Address” Not used Find Company Info with Address
BT-56 X Name /Invoice/cac:AccountingCustomerParty/cac:Party/cac:PartyName/cbc:Name PersonName /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:BuyerTradeParty/ram:DefinedTradeContact/ram:PersonName Company Information - Field 2 Name SNCX XRechnung Import Header.”Company Info Name” Not used Find Company Info with Name
BT-59 X Name /Invoice/cac:PayeeParty/cac:PartyName/cbc:Name Name /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:PayeeTradeParty/ram:Name Purchase Header - Field 5 Pay-to Name SNCX XRechnung Import Header.”Pay-to Name” Not used Find Pay to Vendor with Name
BT-60 ID /Invoice/cac:PayeeParty/cac:PartyIdentification/cbc:ID[@schemeID=''0088''] ID /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:PayeeTradeParty/ram:ID Purchase Header - Field 4 Pay-to Vendor No. (GLN) SNCX XRechnung Import Header.”Pay-to Vendor No. GLN” Not used Find Pay to Vendor with GLN
BT-60 ID /Invoice/cac:PayeeParty/cac:PartyIdentification/cbc:ID[@schemeID!=''0088''] ID /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:PayeeTradeParty/ram:ID Purchase Header - Field 70 VAT Registration No. SNCX XRechnung Import Header.”Pay-to Vendor VAT Reg. No.” Not used Find Pay to Vendor with VAT Reg. No.
BT-61 CompanyID /Invoice/cac:PayeeParty/cac:PartyLegalEntity/cbc:CompanyID[@schemeID=''0088''] ID /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:PayeeTradeParty/ram:SpecifiedLegalOrganization/ram:ID Purchase Header - Field 4 Pay-to Vendor No. SNCX XRechnung Import Header.”Pay-to Vendor No. GLN” Not used Find Pay to Vendor with GLN
BT-61 CompanyID /Invoice/cac:PayeeParty/cac:PartyLegalEntity/cbc:CompanyID[@schemeID!=''0088''] ID /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:PayeeTradeParty/ram:SpecifiedLegalOrganization/ram:ID Purchase Header - Field 70 VAT Registration No. SNCX XRechnung Import Header.”Pay-to Vendor VAT Reg. No.” Not used Find Pay to Vendor with VAT Reg. No.
BT-84 ID /Invoice/cac:PaymentMeans/cac:PayeeFinancialAccount/cbc:ID[@schemeID=''IBAN''] IBANID /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:SpecifiedTradeSettlementPaymentMeans/ram:PayeePartyCreditorFinancialAccount/ram:IBANID Vendor Bank Account - Field 24 IBAN SNCX XRechnung Import Header.”Vendor IBAN” Not used Find Buy from Vendor with Bank Account
BT-86 X ID /Invoice/cac:PaymentMeans/cac:PayeeFinancialAccount/cac:FinancialInstitutionBranch/cbc:ID BICID /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:SpecifiedTradeSettlementPaymentMeans/ram:PayeeSpecifiedCreditorFinancialInstitution/ram:BICID Vendor Bank Account - Field 13 Bank Branch No. SNCX XRechnung Import Header.”Vendor Bank Branch No.” Not used Find Buy from Vendor with Bank Account
BT-92 Amount /Invoice/cac:AllowanceCharge/cbc:Amount[../cbc:ChargeIndicator/text() = ‘’true’’] ActualAmount /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:SpecifiedTradeAllowanceCharge/ram:ActualAmount Item Charge Assignment (Purch) - Field 11 Amount to Assign SNCX Allow. Charge Import Line.Amount Not used Used to create new purchase line
BT-92 X CurrencyID /Invoice/cac:AllowanceCharge/cbc:Amount/@currencyID [../cbc:ChargeIndicator/text() = ''true''] Purchase Header - Field 114 Tax Area Code SNCX XRechnung Import Header.”Tax Area Code” Not used
BT-97 AllowanceChargeReason /Invoice/cac:AllowanceCharge/cbc:AllowanceChargeReason[../cbc:ChargeIndicator/text() = ‘’true’’] Reason /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:SpecifiedTradeAllowanceCharge/ram:CategoryTradeTax/ram:Reason Item Charge - Field 2 Description SNCX Allow. Charge Import Line.”Allowance Charge Reason” Not used Used to create new purchase line
BT-107 X AllowanceTotalAmount /Invoice/cac:LegalMonetaryTotal/cbc:AllowanceTotalAmount AllowanceTotalAmount /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:SpecifiedTradeSettlementHeaderMonetarySummation/ram:AllowanceTotalAmount Purchase Header - Field 122 Invoice Discount Value SNCX XRechnung Import Header.”Invoice Discount Value” Not used Used to insert Invoice Discount via lines
BT-107 X CurrencyID /Invoice/cac:AllowanceCharge/cbc:Amount/@currencyID [../cbc:ChargeIndicator/text() = ''false''] Purchase Header - Field 114 Tax Area Code SNCX XRechnung Import Header.”Tax Area Code” Not used
BT-109 TaxExclusiveAmount /Invoice/cac:LegalMonetaryTotal/cbc:TaxExclusiveAmount TaxBasisTotalAmount /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:SpecifiedTradeSettlementHeaderMonetarySummation/ram:TaxBasisTotalAmount Purchase Header - Field 60 Amount SNCX XRechnung Import Header.Amount Not used
BT-110 TaxAmount /Invoice/cac:TaxTotal/cbc:TaxAmount TaxTotalAmount /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:SpecifiedTradeSettlementHeaderMonetarySummation/ram:TaxTotalAmount G/L Entry - Field 43 VAT Amount SNCX XRechnung Import Header.”VAT Amount” Not used
BT-113 X PrepaidAmount /Invoice/cac:LegalMonetaryTotal/cbc:PrepaidAmount TotalPrepaidAmount /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:SpecifiedTradeSettlementHeaderMonetarySummation/ram:TotalPrepaidAmount Prepayment Inv. Line Buffer - Field 3 Amount SNCX XRechnung Import Header.”Prepayment Amount” Not used Used for checking the total amount. Prepayed amount must be processed manually
BT-113 X CurrencyID /Invoice/cac:LegalMonetaryTotal/cbc:PrepaidAmount/@currencyID Purchase Header - Field 114 Tax Area Code SNCX XRechnung Import Header.”Tax Area Code” Not used
BT-115 X PayableAmount /Invoice/cac:LegalMonetaryTotal/cbc:PayableAmount DuePayableAmount /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:SpecifiedTradeSettlementHeaderMonetarySummation/ram:DuePayableAmount Purchase Header - Field 61 Amount Including VAT SNCX XRechnung Import Header.”Amount Including VAT” Not used Used to check document totals
BT-115 X CurrencyID /Invoice/cac:LegalMonetaryTotal/cbc:PayableAmount/@currencyID Purchase Header - Field 114 Tax Area Code SNCX XRechnung Import Header.”Tax Area Code” Not used
/Invoice/cac:AccountingSupplierParty/cac:Party/cac:Contact/cbc:ID Purchase Header - Field 11 Your Reference SNCX XRechnung Import Header.”Your Reference” PurchaseHeader.”Your Reference”

18.2.2 Purchase Line

Business Term (BT) Optional UBL (BT) Feld XML Element CII (BT) Feld XML Element CII Intermediate Record XRechnung Record Purchase Line Record Usage
BT-127 X Note /Invoice/cac:InvoiceLine/cbc:Note Content /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:IncludedSupplyChainTradeLineItem/ram:AssociatedDocumentLineDocument/ram:IncludedNote/ram:Content Not used Not used Not used
BT-129 InvoicedQuantity /Invoice/cac:InvoiceLine/cbc:InvoicedQuantity BilledQuantity /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:IncludedSupplyChainTradeLineItem/ram:SpecifiedLineTradeDelivery/ram:BilledQuantity Purchase Line - Field 15 Quantity SNCX XRechnung Import Line.Quantity Purchase Line.Quantity
BT-130 UnitCode /Invoice/cac:InvoiceLine/cbc:InvoicedQuantity/@unitCode UnitCode /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:IncludedSupplyChainTradeLineItem/ram:SpecifiedLineTradeDelivery/ram:BilledQuantity@unitCode Purchase Line - Field 5407 Unit of Measure Code SNCX XRechnung Import Line.Unit of Measure Code BC Purchase Line.”Unit of Measure Code” Find correct Business Central UOM
BT-131 X LineExtensionAmount /Invoice/cac:InvoiceLine/cbc:LineExtensionAmount LineTotalAmount /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:IncludedSupplyChainTradeLineItem/ram:SpecifiedLineTradeSettlement/ram:SpecifiedTradeSettlementLineMonetarySummation/ram:LineTotalAmount Purchase Line - Field 29 Amount SNCX XRechnung Import Line.Amount Not used
BT-131 CurrencyID /Invoice/cac:InvoiceLine/cbc:LineExtensionAmount/@currencyID Purchase Line - Field 91 Currency Code SNCX XRechnung Import Line.”Currency Code” Not used Check against Currency Code from Header
BT-136 Amount /Invoice/cac:InvoiceLine/cac:AllowanceCharge[cbc:ChargeIndicator[text()=‘’false’’]]/cbc:Amount ActualAmount /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:IncludedSupplyChainTradeLineItem/ram:SpecifiedLineTradeSettlement/ram:SpecifiedTradeAllowanceCharge/ram:ActualAmount Purchase Line - Field 28 Line Discount Amount SNCX XRechnung Import Line.”Line Discount Amount” Purchase Line.”Line Discount Amount”
BT-136 CurrencyID /Invoice/cac:InvoiceLine/cac:AllowanceCharge/cbc:Amount/@currencyID Purchase Line - Field 91 Currency Code SNCX XRechnung Import Line.”Currency Code” Not used Check against Currency Code from Header
BT-146 InvoiceLine Price PriceAmount /Invoice/cac:InvoiceLine/cac:Price/cbc:PriceAmount ChargeAmount /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:IncludedSupplyChainTradeLineItem/ram:SpecifiedLineTradeAgreement/ram:NetPriceProductTradePrice/ram:ChargeAmount Purchase Line - Field 22 Direct Unit Cost SNCX XRechnung Import Line.”Direct Unit Cost” Purchase Line.”Direct Unit Cost”
BT-146 CurrencyID /Invoice/cac:InvoiceLine/cac:Price/cbc:PriceAmount/@currencyID Purchase Line - Field 91 Currency Code SNCX XRechnung Import Line.”Currency Code” Not used Check against Currency Code from Header
BT-149 X BaseQuantity /Invoice/cac:InvoiceLine/cac:Price/cbc:BaseQuantity BasisQuantity /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:IncludedSupplyChainTradeLineItem/ram:SpecifiedLineTradeAgreement/ram:GrossPriceProductTradePrice/ram:BasisQuantity Purchase Line - Field 5415 Quantity (Base) SNCX XRechnung Import Line.”Quantity (Base)” Not used
BT-152 X Percent /Invoice/cac:InvoiceLine/cac:Item/cac:ClassifiedTaxCategory/cbc:Percent RateApplicablePercent /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:IncludedSupplyChainTradeLineItem/ram:SpecifiedLineTradeSettlement/ram:ApplicableTradeTax/ram:RateApplicablePercent Purchase Line - Field 25 VAT % SNCX XRechnung Import Line.”VAT %” Not used Used to check imported VAT % against the inserted “Purchase Line”.”VAT %” after BC Standard validation
BT-153 Name /Invoice/cac:InvoiceLine/cac:Item/cbc:Name Name /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:IncludedSupplyChainTradeLineItem/ram:SpecifiedTradeProduct/ram:Name Purchase Line - Field 11 Description SNCX XRechnung Import Line.Description Not used Business Central Master Data is used for Description
BT-154 Description /Invoice/cac:InvoiceLine/cac:Item/cbc:Description Description /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:IncludedSupplyChainTradeLineItem/ram:SpecifiedTradeProduct/ram:Description Purchase Line - Field 12 Description 2 SNCX XRechnung Import Line.”Description 2” Not used Business Central Master Data is used for Description
BT-155 X ID /Invoice/cac:InvoiceLine/cac:Item/cac:SellersItemIdentification/cbc:ID SellerAssignedID /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:IncludedSupplyChainTradeLineItem/ram:SpecifiedTradeProduct/ram:SellerAssignedID Purchase Line - Field 5705 Cross-Reference No. SNCX XRechnung Import Line.”Sellers Item Identification” Not used Used to find “Purchase Line”.Type and “Purchase Line”.”No.” with Item Reference Table
BT-157 ID /Invoice/cac:InvoiceLine/cac:Item/cac:StandardItemIdentification/cbc:ID[@schemeID=''0088''] GlobalID /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:IncludedSupplyChainTradeLineItem/ram:SpecifiedTradeProduct/ram:GlobalID Purchase Line - Field 6 No. SNCX XRechnung Import Line.GTIN Not used Used to find “Purchase Line”.Type and “Purchase Line”.”No.” with GTIN

18.3 Additional Document References

Optional BT Field BT ID XML Element
x Invoice AdditionalDocumentReference ID BT-18, BT-122 /Invoice/cac:AdditionalDocumentReference/cbc:ID
x Invoice AdditionalDocumentReference Attachment EmbeddedDocumentBinaryObject BT-125 /Invoice/cac:AdditionalDocumentReference/cac:Attachment/cbc:EmbeddedDocumentBinaryObject
x Invoice AdditionalDocumentReference Attachment EmbeddedDocumentBinaryObject mimeCode BT-125 /Invoice/cac:AdditionalDocumentReference/cac:Attachment/cbc:EmbeddedDocumentBinaryObject/@mimeCode
x Invoice AdditionalDocumentReference Attachment EmbeddedDocumentBinaryObject filename BT-125 /Invoice/cac:AdditionalDocumentReference/cac:Attachment/cbc:EmbeddedDocumentBinaryObject/@filename