Before sending files to Inexchange, they must be tested and validated:

• Create test files in XML format according to BIS Billing 3.0 standard

• Validate the files using the tool Validex

• Correct any errors and warnings

• Ensure that internal testing is completed before implementation 

Validex

Link: SFTI example collection

Debit

Credit

schemeID (ISO 6523 ICD list)

The list below shows commonly used SchemeIDs in the Nordic countries:

• GLN: 0088
• Sweden: 0007 (Company Reg. No.)
• Norway: 0192 (Company Reg. No.)
• Denmark: 0184 (CVR without the prefix DK)
• Iceland: 0196 (Company Reg. No.)

Unit Codes (UNECERec20)

Field: Invoice/AdditionalDocumentReference

When uploading attachments, the files must be Base64-encoded.
All fields must be completed in accordance with the examples shown for each document type below.

• Invoice attachment

  Example from XML-file:

  

• Invoice image

  In order for the attachment to be sent as a invoice image the field DocumentDescription has to be set to the value: COMMERCIAL INVOICE.

  Example from XML-file:

  

  *MPORTANT*Before you enable the option to attach your own invoice image for paper invoices, you must ensure that the address information is positioned according to the envelope window specifications.
  You can find more information about our printing service here.

For Inexchange to identify the invoice recipient and choose the best possible delivery method, the following is required:

•  Recipient Identification

  Field: AccountingCustomerParty/Party/EndpointID

  To identify the recipient, we primarily recommend using GLN. If GLN is unknown, the organization number is used. 

• Delivery via Email

  Field: AccountingCustomerParty/Party/Contact/ElectronicMail

  To enable delivery of the invoice as a PDF to the recipient, an email address must be provided. 

We also recommend that the following fields are always present for the recipient.

• Customer Number

  Field:  AccountingCustomerParty/Party/PartyIdentification/ID

  To specify the customer number, use the field above - without schemeID. If there is more than one segment of PartyIdentification, the customer number should be specified in the topmost one.