Customer invoice Enterprise

  • File Information - BIS Billing 3.0
    1. Standard Setup
      1. File Information
      2. File Transfer
      3. Information for Inexchange

    To ensure that your invoice files meet the requirements according to Peppol BIS Billing 3.0, we ask you to review the following resources and instructions. 

    Mandatory Testing Before Implementation

    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 

    Validation Tool

    File Examples

    Schema

    schemeID

    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

    Attachments

    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.

    Invoice Delivery

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

    Other Recommendations

    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.

      image (22).png

  • File Transfer
    1. Standard Setup
      1. File Information
      2. File Transfer
      3. Information for Inexchange

    The communication between the customer's system and Inexchange takes place via SFTP.
    The customer receives login credentials for an SFTP area at Inexchange and also gets a path where files should be placed.

    User Credentials for SFTP

    You will receive the following information from Inexchange:

    • Host name

    • Port

    • Username

    • Password

    • Directory

    Testing SFTP Communication

    Once the SFTP area is set up and you have received login credentials, you need to:

    1. Test login – ensure that you can connect to the SFTP server.

    2. Upload a test file – confirm that the file transfer works as expected.

  • Information for Inexchange
    1. Standard Setup
      1. File Information
      2. File Transfer
      3. Information for Inexchange

    Before the service can be set up, we need to receive certain information from you as a customer.

    Company Information and Company Structure

    We need an Excel list of the companies to be included in the implementation. The list should contain the following information and clearly indicate which company is the parent company:

    • Company name

    • Company registration number

    • VAT registration number

    Access to Inexchange

    In order for us to provide access to your companies in Inexchange, we need the information below for the person who will be the Super User:

    • First and last name

    • Email address

    Contact and Feedback

    Sometimes we need to get in touch with you, and it is important that the information reaches the right person. Please provide contact details for the following areas:

    • General contact

      • First and last name

      • Email address

    • Technical error messages

      • Email address

    • Delivery and content errors

      • Email address