Business Central-konfiguration

Uppdaterad 25 mars 2026

This guide covers how to connect Microsoft Dynamics 365 Business Central to Junipeer and the configuration details specific to Business Central as an ERP system.

Overview

Microsoft Dynamics 365 Business Central is a cloud-based ERP system used by small to mid-sized businesses globally. It offers comprehensive financial management, supply chain, sales, and project capabilities. Business Central is particularly common among organizations already invested in the Microsoft ecosystem.

In a Junipeer integration, Business Central is typically the destination system — orders from the e-commerce platform are synced to Business Central as invoices, and payout data flows in for payment reconciliation.

Connecting Business Central to Junipeer

Business Central uses OAuth 2.0 authentication through Microsoft's identity platform (Azure AD / Entra ID).

Prerequisites

Before connecting, ensure:

  1. Your Business Central environment is accessible via API (Business Central SaaS environments have API access enabled by default; on-premises installations may require additional configuration)

  2. You have an account with sufficient permissions — at minimum, read/write access to customers, items, sales orders, sales invoices, and payment journals

  3. Your Azure AD / Entra ID tenant allows third-party application consent

Authorization

  1. During the Get Started onboarding wizard (Step 2 — Connect Systems), select Business Central as your ERP

  2. You will be redirected to Microsoft's login page

  3. Log in with your Business Central account credentials

  4. Grant the requested permissions to Junipeer

  5. If prompted, select the correct environment (Production or Sandbox) and company within Business Central

  6. You will be redirected back to Junipeer with the connection established

If the authorization fails, check with your IT administrator that third-party app consent is allowed in your Azure AD tenant settings.

Typical flows

For a Business Central integration, the most common flows are:

  • Orders: e-commerce platform → Business Central (synced as sales invoices or sales orders)

  • Customers: e-commerce platform → Business Central

  • Products/Articles: Business Central → e-commerce platform (Business Central is often the item master) or bidirectional

  • Stock/Inventory: Business Central → e-commerce platform

  • Payouts: payment provider → Business Central (reconciliation)

Business Central-specific considerations

Environment and company selection

Business Central supports multiple environments (Production, Sandbox) and multiple companies within each environment. Make sure you connect Junipeer to the correct environment and company. If you operate multiple companies, each one requires a separate Junipeer integration.

Test your integration in a Sandbox environment before connecting to Production. Business Central Sandbox environments are free to use and allow you to verify your configuration without affecting live data.

Number series

Business Central uses number series for customers, items, invoices, and other entities. When Junipeer creates records, it uses the default number series configured in Business Central. Ensure that:

  • Number series are configured and have available numbers

  • There is no overlap between manually created records and the series used by Junipeer

  • If you use manual numbering for some record types, communicate this to Junipeer support so the integration can be configured accordingly

VAT and tax handling

Business Central has a flexible VAT posting setup based on combinations of VAT Business Posting Groups and VAT Product Posting Groups. For EU cross-border scenarios (OSS), Business Central can often handle the VAT determination automatically based on customer and item posting groups, without the explicit per-country sales account mapping that some other ERP systems require.

Verify that your VAT posting setup covers all the countries you sell to. Missing VAT posting group combinations will cause invoice creation to fail.

Currency management

Business Central supports multiple currencies with automatic exchange rate updates. Ensure that:

  • All currencies used in your e-commerce platform are set up in Business Central

  • Exchange rates are kept up to date (Business Central can update these automatically from external services)

  • The local currency (LCY) settings match your primary operating currency

Payment journals

Payment reconciliation in Business Central works through payment journals. Junipeer creates payment journal entries to mark invoices as paid. Ensure that the payment journal template and batch are configured in your integration settings.

Differences from Fortnox

If you are familiar with Junipeer's Fortnox integration, here are the key differences when using Business Central:

  • Authentication: Fortnox uses API keys; Business Central uses OAuth 2.0 through Azure AD.

  • VAT handling: Fortnox requires explicit per-country sales account mapping for OSS; Business Central uses VAT posting group combinations and can often determine the correct VAT automatically.

  • Multi-company: Fortnox is single-company; Business Central supports multiple companies per environment, each requiring its own Junipeer integration.

  • Environments: Business Central offers Sandbox environments for testing; Fortnox does not have a built-in sandbox (testing must be done carefully in the production environment or a separate Fortnox account).

For troubleshooting common errors, see the Error Codes reference or your connector pair's troubleshooting section.

Var den här artikeln till hjälp?