Business NXT documentation

Home
Connected services
Business NXT can be integrated to a number of Visma.net services to support streamlined workflows between the different financial systems.
Visma.net AutoInvoice
Visma.net AutoInvoice works behind the scenes on all ingoing and outgoing electronic documents, and gives you full control over your invoicing and ensures a streamlined workflow.
Extended mapping information
When sending invoices to Visma.net AutoInvoice, there's a default set of mapping rules that apply to the output data.
Default mapping for PEPPOL BIS 3.0 - invoicing
The default field-to-field mapping is used for electronic invoicing though Visma.net AutoInvoice using the PEPPOL BIS 3.0 billing format.
AccountingCustomerParty - Invoice customer information
This section contains information about the receiver of the invoice.
Endpoint and Party identification for invoice customer

Connected services
Business NXT can be integrated to a number of Visma.net services to support streamlined workflows between the different financial systems.
- Single sign-on
- Master Data Management
  Master Data Management (MDM) is a concept in Visma for sharing common data across multiple applications. Master data is information which is key for running a business.
- Visma.net Approval
  Visma.net Approval is used to approve for example invoices, expense claims and cost requests online, wherever and when it suits you.
- Visma.net AutoInvoice
  Visma.net AutoInvoice works behind the scenes on all ingoing and outgoing electronic documents, and gives you full control over your invoicing and ensures a streamlined workflow.
  - Settings for Visma.net AutoInvoice
    In order to use Visma.net AutoInvoice for electronic order documents such as invoices and order confirmations, you need to create a user account in Visma.net AutoInvoice and connect that user account to Business NXT.
  - Extended mapping information
    When sending invoices to Visma.net AutoInvoice, there's a default set of mapping rules that apply to the output data.
    - Default mapping for PEPPOL BIS 3.0 - invoicing
      The default field-to-field mapping is used for electronic invoicing though Visma.net AutoInvoice using the PEPPOL BIS 3.0 billing format.
      - 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.
      - Invoice - Document information
        This section includes all document references, including document no, dates and currency information.
      - AccountingSupplierParty - Invoice sender information
        This section contains information about the sender of the invoice.
      - AccountingCustomerParty - Invoice customer information
        This section contains information about the receiver of the invoice.
        Endpoint and Party identification for invoice customer
        Party name and postal address for invoice customer
        PartyTaxScheme - Company VAT registration information
        PartyLegalEntity - Invoice customer legal registration information
        Information about the receiver’s registration in national legal registry.
        Contact - Invoice customer contact information
      - PayeeParty - Factoring company information
        The PayeeParty is only included if the document is identified as a factoring invoice.
      - Delivery - Goods delivery information
      - PaymentMeans - Payment information
        This section contains information about supplier or factoring bank account available to use for payment of the invoice.
      - AllowanceCharge - Document level discounts and additions
        This section shows any freights or discounts on header level. All amounts in this section are presented as net amounts.
      - TaxTotal - Summation of VAT related amounts
        This section displays sums of all VAT amounts in the invoice, as total and per VAT code.
      - LegalMonetaryTotal - Invoice total amounts
        This section includes the invoice amount and all sums of header and line amounts.
      - InvoiceLine - Invoice line information
        The invoice line section includes all relevant information about the invoice line.
      - Relevant validation rules and causes
        In this section all rules relevant for Business NXT that may cause errors will be described.
      - Mapping lists
      - Business NXT field reference
        This section lists all Business NXT columns mentioned in the documentation with the VBS identification used and the name displayed in Business NXT in the selected language.
    - Default mapping requiring configuration
    - Overriding other mapping options
- Visma.net AutoPay
  Visma.net AutoPay offers a streamlined workflow that can be managed directly in your Visma financial management solution.
- Visma.net AutoReport
  Visma.net AutoReport can be used to automatically generate and send for example tax reports to the tax authorities.
- Visma.net Expense
  Visma.net Expense simplifies life on the road and provides your organisation with a modern and efficient expense and reimbursement solution.
- WebFaktura
  WebFaktura is a solution designed for accounting offices that want to provide a simple electronic invoicing service for their clients.
- Pre-approval of invoices for payment
  You can set up Visma.net Approval and Visma.net AutoPay for approval of invoices and payments in Business NXT in one go.
- Tables for connected services
  The tables in this section are used for some Business NXT integrations with Visma.net services.
- Payroll
  Payroll is a cloud-based service that makes it easy both for employers and employees to manage time registration, expenses, salaries and more, using automatic flows.

Endpoint and Party identification for invoice customer

cbc:EndpointID (M)

Default mapping: OrderDocument.InvoiceCustomerNo->Associate.CompanyNo

Alternative mapping: OrderDocument.InvoiceCustomerNo->Associate.AutoInvoiceEndpointID + OrderDocument.InvoiceCustomerNo->Associate.AutoInvoiceEndpointScheme

This value represents the receiver company’s electronic address. As default, the organisation no is used, and the system uses the country no in the Associate table to determine the scheme to use as attribute when presenting the address in the field. If the country not has not been set, the Country no. in Company information is used. The default may be overwritten by using the alternative mapping, but if so, both fields must be used, otherwise the scheme will be “unknown” and the invoice sending may fail. Possible values for Endpoint scheme when overriding the electronic address may be found in the online field help (most relevant options), or for a full and up to date list, see the ISO 6523 ICD list.

Note that the content should be numeric only. If you have been given an address in this format: 0192:999999999, the numbers before the colon represents the scheme, while the numbers after represent the company’s ID. While any non-numeric characters and spaces are stripped by the system prior to inclusion in the invoice, it is recommended to keep the field content numeric only.

cac:PartyIdentification (O)

cbc:ID (M)

Default mapping: OrderDocument.InvoiceCustomerNo->Associate.CompanyNo

Alternative mapping: OrderDocument.InvoiceCustomerNo->Associate.EanLocationNo

Alternative mapping: OrderDocument.InvoiceCustomerNo

Receiver company identification. If nothing is set in EAN location no, PartyIdentification will be the same as Endpoint. Note that this may also be overridden by the setting "Do not use EAN for PartyIdentification" in Associate processing, which if set means that EAN location no is not looked at for PartyIdentification, but copies the value set in EndpointID. If neither EAN location no or Company no is set, Customer no will be used.

Note:

If an invoice is sent for electronic delivery using customer no as PartyIdentification and the invoice is not identified as B2C, the alternative mapping of AutoInvoice endpoint ID and AutoInvoice endpoint scheme must be set for the invoice to pass the XML content validation.