> For the complete documentation index, see [llms.txt](https://docs.silkline.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.silkline.ai/configuration/integrations/dynamics.md).

# Dynamics 365 Business Central

Overview of the Silkline Dynamics 365 Business Central integration

## Overview

Silkline's Dynamics 365 Business Central integration syncs procurement and master data between Silkline and Business Central. **Silkline is the source of truth for orders** — orders are created in Silkline and written to Business Central automatically. Business Central owns the receiving and invoicing lifecycle, and Silkline reads back only that **fulfillment progress**. Vendors, items, and salespeople/purchasers are read into Silkline from Business Central (**read-only**).

## Directionality

| Business Central       | Silkline  | Direction                                            |
| ---------------------- | --------- | ---------------------------------------------------- |
| Purchase Orders        | Orders    | Write (Silkline → BC); limited fulfillment read-back |
| Vendors                | Suppliers | Read only (BC → Silkline)                            |
| Items                  | Materials | Read only (BC → Silkline)                            |
| Salespeople/Purchasers | Users     | Read only (BC → Silkline)                            |
| Locations              | Locations | Read only (BC → Silkline)                            |

Order **writeback is automatic**: creating or editing an order in Silkline pushes it to Business Central with no manual step (when writeback is enabled). Silkline is the source of truth for orders and reads back only **fulfillment progress** (received/invoiced quantities and order closure). Master data — vendors, items, and salespeople/purchasers — is read from Business Central on a regular schedule.

## Prerequisites

{% hint style="info" %}
APIs are enabled by default for Business Central Online. If you're running Business Central on-premises, you'll need to [enable API access](https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/api-reference/v2.0/enabling-apis-for-dynamics-nav) first.
{% endhint %}

To complete your Dynamics 365 Business Central integration, you will need:

* **Administrator** access to your Microsoft Entra ID (Azure AD) tenant
* **Administrator** access to your Business Central environment
* A Microsoft Entra ID **App Registration** with the following:
  * **Tenant ID**
  * **Client ID** (Application ID)
  * **Client Secret**
* Your Business Central **Base URL**
* The Business Central **company** you want to sync (you select it by name when configuring the integration in Silkline)

## Instructions

{% stepper %}
{% step %}

#### Create an App Registration in Microsoft Entra ID

1. Sign in to the [Azure Portal](https://portal.azure.com).
2. Navigate to **Microsoft Entra ID → App registrations → New registration**.
3. Name your app (e.g., "Silkline Integration").
4. Set **Supported account types** to "Accounts in this organizational directory only".
5. Click **Register**.
6. On the app's overview page, copy the **Application (client) ID** and **Directory (tenant) ID**.
   {% endstep %}

{% step %}

#### Create a Client Secret

1. In your app registration, go to **Certificates & secrets → Client secrets → New client secret**.
2. Add a description (e.g., "Silkline") and choose an expiration period.
3. Click **Add** and copy the secret **Value** immediately — it is only shown once.
   {% endstep %}

{% step %}

#### Grant API Permissions

1. In your app registration, go to **API permissions → Add a permission**.
2. Select **Dynamics 365 Business Central**.
3. Choose **Application permissions** and add:
   * `API.ReadWrite.All`
   * `app_access`
4. Click **Grant admin consent** for your organization.
   {% endstep %}

{% step %}

#### Register the App in Business Central

1. In Business Central, search for **Microsoft Entra Applications** and open the page.
2. Click **New** and paste in the **Application (client) ID** from Step 1.
3. Set **State** to **Enabled**.
4. Assign appropriate permission sets (e.g., `D365 AUTOMATION`).
   {% endstep %}

{% step %}

#### Get your Business Central Base URL

Your base URL follows this format:

```
https://api.businesscentral.dynamics.com/v2.0/{tenantId}/{environment}/api/v2.0
```

Replace `{tenantId}` with your Entra tenant ID and `{environment}` with your environment name (typically `production` or `sandbox`).
{% endstep %}

{% step %}

#### Create the Integration in Silkline

Follow the [Managing Integrations](/configuration/integrations/managing-integrations.md) guide to create a new Dynamics 365 Business Central integration in Silkline. On the creation form, provide:

* **Business Central Base URL**: The full API URL (from the previous step)

You'll choose the **Company** after adding credentials (next steps).
{% endstep %}

{% step %}

#### Add Credentials

After creating the integration, open it and navigate to the **Secrets** section. Enter:

* **Entra ID Tenant ID**: The directory (tenant) ID (from Step 1)
* **App Registration Client ID**: The application (client) ID (from Step 1)
* **Client Secret**: The client secret value (from Step 2)
  {% endstep %}

{% step %}

#### Select your Company

In the integration's connection settings, click **Fetch companies** next to **Company** and choose your Business Central company from the list.
{% endstep %}
{% endstepper %}

## Required Configuration

Beyond the credentials above, Business Central (and Silkline) must be configured for purchase order writeback to succeed.

### Purchase order numbering

Silkline owns the purchase order number — when Silkline writes a new order to Business Central, **Silkline supplies the number**; Business Central does not assign it. This requires:

* **In Business Central:** the `P-ORD` No. Series must have **Manual Nos.** set to **Yes** (so the integration can supply the number) and **Default Nos.** set to **Yes** (so users creating POs directly in Business Central still get auto-assigned numbers). Without **Manual Nos.**, purchase order creation fails.
* **In Silkline:** the organization must configure an **order-number prefix** (in Order Configuration). Without a prefix, orders display as "PENDING".

### Users and order requesters

Silkline **Users** are synced from Business Central **Salespeople/Purchasers** (not Employees). For orders to write back successfully:

* **Each salesperson/purchaser needs an email** in Business Central — records with neither a primary nor a secondary email are skipped and won't appear as Silkline users.
* **Order requesters must be synced salespeople/purchasers.** On writeback, Silkline resolves the order's requester to that person's Business Central purchaser code; if the requester isn't a synced salesperson/purchaser, the writeback fails. Make sure anyone who will be set as an order requester exists as a Salesperson/Purchaser in Business Central.

### Taxes (VAT/GST environments)

For order-line taxes to write back, your Silkline **Tax Codes** must mirror your Business Central **VAT/GST Product Posting Groups**:

1. Enable the Tax Module (**Settings → Taxes**).
2. Create a Silkline tax code for each Business Central group you use, naming each **exactly** the same as the Business Central code (e.g. `GST`, `FRE`, `EXP`).
3. Assign a **single** tax code to each order line — a Business Central line accepts only one VAT/GST posting group, so if a line has more than one Silkline tax code, **only the first is written**. Set the order's **tax-inclusive** option to match whether your prices include tax.

Business Central then calculates each line's tax from the code. *(US sales-tax environments — Tax Areas + Tax Groups — are not yet supported for tax writeback.)*

### Currency

Set your Silkline organization's **base currency to match your Business Central company's Local Currency (LCY)** — writeback assumes they are the same. For an order in a **foreign currency**, Business Central needs a **Currency Exchange Rate** configured for that currency (**Currencies → Exch. Rates**); without one, the purchase order can't be created and Silkline reports a clear "no exchange rate configured" error.

### Payment terms (optional)

Silkline can offer Business Central's **Payment Terms** as a dropdown on orders, default each supplier's terms from its Business Central vendor card, and write the selected term back to the purchase order header. This requires a one-time setup:

{% stepper %}
{% step %}
**Make the order's Payment Terms field a dropdown**

In **Settings → Orders**, open the core **Payment Terms** field and set its type to a labeled select.

{% hint style="warning" %}
Configure the **core** Payment Terms field on the Orders settings page — not a new field created on the Configurable Fields page. A separately created field with the same name is not connected to supplier defaults or order writeback.
{% endhint %}
{% endstep %}

{% step %}
**Link the field to Business Central**

On the field's integration link, choose **Payment Terms** as the link type and run a pull. The field's options fill from your Business Central payment terms list.
{% endstep %}

{% step %}
**Re-pull suppliers**

On the next supplier sync, each vendor's payment term arrives as the matching dropdown option, so new orders for that supplier pre-fill it.
{% endstep %}
{% endstepper %}

With the field linked, an order's selected term is written to the Business Central purchase order header on every push. Without this setup, the field stays free text: supplier defaults still show the Business Central term's name, but payment terms are not written to Business Central.

### Purchase order creation timing (optional)

By default, Silkline creates the Business Central purchase order as soon as the order exists in Silkline, and updates it on every change — so the PO sits in Business Central through the whole Silkline approval workflow.

To hold orders back instead, set **Create Purchase Orders At** in the integration's connection settings to the Silkline order status — **Draft**, **Review**, **Approved**, or **Open** — at which the purchase order should first be created. An order that hasn't reached that status is not pushed. Once the purchase order exists in Business Central, every subsequent Silkline change syncs to it, including closure and cancellation. An order that is canceled or closed before ever reaching the threshold is never pushed.

{% hint style="info" %}
If you **release** a purchase order in Business Central, Silkline edits to that order fail to sync until the purchase order is reopened — Business Central rejects changes to released documents. Choosing a later creation status (such as **Approved**) keeps most edits ahead of the release, so this rarely comes up.
{% endhint %}

### Excluding vendors (optional)

In Business Central, employees are often also stored as vendor records. To keep them out of your Silkline supplier list, exclude vendors by a Business Central **dimension** value in the integration's **Vendor Exclusion** settings — see [Supplier (Vendor) Mapping](#supplier-vendor-mapping).

## What Gets Synchronized

* **Orders → Purchase Orders** — orders are created in Silkline and written to Business Central (header, lines, and dimensions). Silkline reads back only **fulfillment progress**: received/invoiced quantities, and it closes an order when its Business Central PO is fully received.
* **Vendors → Suppliers** — read only.
* **Items → Materials** — read only.
* **Salespeople/Purchasers → Users** — read only. Business Central **Employees** are not synced.
* **Locations → Locations** — read only. Used as predefined ship-to locations; an order's ship-to location is written to each Business Central purchase order line as its **Location Code**.

## Detailed Data Mappings

The tables below use Business Central field names and cover both directions — the **Notes** call out anything that applies to only one direction.

### Purchase Order Mapping

Silkline is the source of truth for orders — most fields are **written** to Business Central. Only the fulfillment fields (received/invoiced quantities and the fully-received status) are read back.

| Business Central Field       | Silkline Field          | Notes                                                                                                                                                                                                                                                                                                                                  |
| ---------------------------- | ----------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| ID                           | External ID             | Business Central's unique purchase order identifier                                                                                                                                                                                                                                                                                    |
| Number                       | Order Number            | Silkline owns the number and writes it on **create** (never renumbered on update). See [Required Configuration](#purchase-order-numbering).                                                                                                                                                                                            |
| Vendor ID                    | Supplier                | Resolved to/from the matching Silkline supplier                                                                                                                                                                                                                                                                                        |
| Purchaser                    | Requester               | **Write only.** Set from the requester's Business Central salesperson/purchaser **code**; the whole writeback fails if a requester can't resolve to a code                                                                                                                                                                             |
| Currency Code                | Currency                | ISO currency code (e.g. `USD`). A blank code = local currency (LCY) and maps to the organization's base currency                                                                                                                                                                                                                       |
| Document Date / Posting Date | Created At              | The order's creation date as a calendar day — in the integration's configured document time zone, or UTC when none is set (Posting Date is **write only**). Business Central derives the Due Date and GST/VAT Date from these. The header's separate **Order Date** field is not writable through the API and always shows the UTC day |
| Requested Receipt Date       | Estimated Arrival Date  | Skipped if set to a placeholder date (see [Known Limitations](#placeholder-dates-are-ignored))                                                                                                                                                                                                                                         |
| Discount Amount              | Order Adjustments (net) | **Write only.** The net of all order adjustments (discounts minus fees); if adjustments net to a fee, `0` is sent                                                                                                                                                                                                                      |
| Prices Including VAT         | Tax Inclusive           | **Write only.** Aligns Business Central's tax basis with Silkline so tax isn't applied twice                                                                                                                                                                                                                                           |
| Payment Terms Code           | Payment Terms           | **Write only.** Written when the Payment Terms field is a dropdown linked to Business Central (see [Required Configuration](#payment-terms-optional)); free-text values are not written                                                                                                                                                |
| Status / Fully Received      | Order State             | Business Central status is **not** ingested into the Silkline order state — the two are independent (see below)                                                                                                                                                                                                                        |

Ship-to and bill-to addresses, payment terms, and the last-modified timestamp are **not** pulled from Business Central — Silkline owns these values on the order, so a pull never overwrites them.

#### Purchase Order Status

Silkline order state (Draft → Review → Approved → Open → Closed) and Business Central PO status are **independent lifecycles**. On **writeback**, Silkline never sets the Business Central status (it's read-only on the API; new POs are created in Business Central's default Draft status). On **ingest**, the Business Central status is not read into the Silkline order state — **with one exception: when a Business Central PO is released and fully received, Silkline closes the corresponding order.**

{% hint style="info" %}
Business Central's PO status vocabulary is inverted from its own web UI — a PO shown as "Open" in the UI is `Draft` on the API.
{% endhint %}

### Purchase Order Line Item Mapping

Only lines of type **Item** are synced — Comment, Account, and other line types are skipped.

| Business Central Line Field   | Silkline Order Item Field | Notes                                                                                                                                                                                                                                                           |
| ----------------------------- | ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| ID                            | External ID               | Unique line identifier. On writeback: present → update the line, absent → create it                                                                                                                                                                             |
| Sequence                      | Line Number               | Silkline's line number is written as the Business Central line sequence (honored on create); falls back to index on read                                                                                                                                        |
| Item ID                       | Part                      | Resolved to/from the matching Silkline material                                                                                                                                                                                                                 |
| Description                   | Material name             | **Write only.** Silkline writes the linked material's name here; on ingest this field is not read — a line shows its material's name from the linked Silkline material                                                                                          |
| Description 2                 | Description               | The line's free-text description/comment. Round-trips both directions                                                                                                                                                                                           |
| Quantity                      | Units                     | Number of units ordered                                                                                                                                                                                                                                         |
| Direct Unit Cost              | Unit Cost                 | Price per unit                                                                                                                                                                                                                                                  |
| Expected Receipt Date         | ETA                       | The order item's ETA **is written** to Business Central. Silkline's Need Date has no Business Central counterpart and is not written. Not read back                                                                                                             |
| VAT/GST Product Posting Group | Tax Code                  | **Write only.** The line's Silkline tax code; its name must match the Business Central posting-group code (e.g. `GST`). If a line has more than one, the first is sent                                                                                          |
| Location Code                 | Ship-To Location          | **Write only.** The order's ship-to location, resolved to its Business Central location and written as every line's Location Code. Requires the location to have been read into Silkline first; omitted if the order has no ship-to location or it isn't mapped |
| Received Quantity             | Units Received            | **Read only**                                                                                                                                                                                                                                                   |
| Invoiced Quantity             | Units Billed              | **Read only**                                                                                                                                                                                                                                                   |

The line ETA, purchasing quantity, purchasing unit cost, and purchasing unit of measure are **not** pulled from Business Central — they are managed in Silkline.

### Supplier (Vendor) Mapping

Business Central **Vendors** are read into Silkline **Suppliers** (read only).

| Business Central Vendor Field | Silkline Supplier Field | Notes                                                                                                                                                                                      |
| ----------------------------- | ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| ID                            | External ID             | Unique vendor identifier                                                                                                                                                                   |
| Display Name                  | Name                    | Falls back to vendor number, then "Unknown Vendor"                                                                                                                                         |
| Number                        | Key                     | Vendor number / code                                                                                                                                                                       |
| Phone Number                  | Primary Phone           | Vendor's phone number                                                                                                                                                                      |
| Website                       | Primary Domain          | Vendor's website URL                                                                                                                                                                       |
| Payment Term                  | Default Payment Terms   | The matching dropdown option when the Payment Terms field is linked to Business Central (see [Required Configuration](#payment-terms-optional)); otherwise the term's display name as text |
| Last Modified Date/Time       | Updated At              | Last modification timestamp                                                                                                                                                                |

If a vendor has any address fields populated, a primary supplier address is created (Address Line 1, City → Locality, State → Administrative Area, Country → Country Code, Postal Code). If a vendor has an email address, a primary contact is created from it. Any Supplier configurable field linked to a Business Central **dimension** is populated from the vendor's matching default dimension value.

#### Excluding vendors (e.g. employees)

In Business Central, employees are often also stored as vendor records (for reimbursements and similar). To keep them out of your Silkline supplier list, exclude vendors by a Business Central **dimension** value, configured in the integration's **Vendor Exclusion** settings:

* **Dimension** — the Business Central dimension that distinguishes the vendors to skip (for example, `VENDTYPE`).
* **Excluded values** — the value(s) to exclude (for example, `EMP` for employees).

Vendors whose default dimensions match are skipped during ingest. Leave both unset to import all vendors.

### Material (Item) Mapping

Business Central **Items** are read into Silkline **Materials** (read only).

| Business Central Item Field          | Silkline Material Field | Notes                                                                                      |
| ------------------------------------ | ----------------------- | ------------------------------------------------------------------------------------------ |
| ID                                   | External ID             | Unique item identifier                                                                     |
| Display Name                         | Name                    | Falls back to item number, then "Unknown Item"                                             |
| Number                               | Material Number         | Internal item number                                                                       |
| Display Name 2                       | Description             | Secondary description (a variant's own description takes precedence when present)          |
| Base Unit of Measure Code            | Unit of Measure         | Unit type (EA, PCS, etc.)                                                                  |
| Type                                 | Inventory Type          | `Inventory` → Inventory, `Non-Inventory` → Non-Inventory, `Service` → Non-Receivable       |
| Item Variant Code                    | Revision                | Set only for environments that model revisions as Item Variants (one Material per variant) |
| Variant Blocked / Purchasing Blocked | Is Archived             | A blocked variant is archived so it can't be selected on new orders                        |
| Last Modified Date/Time              | Updated At              | Last modification timestamp                                                                |

### Location Mapping

Business Central **Locations** are read into Silkline **Locations** (read only). They serve as predefined ship-to locations on orders; an order's ship-to location is written back as the [Location Code on each purchase order line](#purchase-order-line-item-mapping).

| Business Central Location Field                     | Silkline Location Field | Notes                                                                                                                                                                                                                        |
| --------------------------------------------------- | ----------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| ID                                                  | External ID             | Unique location identifier                                                                                                                                                                                                   |
| Code + Name                                         | Name                    | Named `Code (Name)` — e.g. `A40 (Services - A40)` — or just the code when the location has no name. Business Central allows duplicate location names, so leading with the (unique) code keeps Silkline location names unique |
| Address Line 1/2, City, State, Country, Postal Code | Address                 | Combined into a single free-text address string                                                                                                                                                                              |

### Organization User (Salesperson/Purchaser) Mapping

Business Central **Salespeople/Purchasers** are read into Silkline **Users** (read only) — they carry the purchaser code used for order writeback. Business Central **Employees** are not synced.

{% hint style="info" %}
An **email is required.** A salesperson/purchaser with neither a primary nor a secondary email is skipped, since Silkline needs an email to create a user.
{% endhint %}

| Business Central Field    | Silkline User Field | Notes                                                  |
| ------------------------- | ------------------- | ------------------------------------------------------ |
| ID                        | External ID         | Unique salesperson/purchaser identifier                |
| Email                     | Username            | Falls back to the secondary email (Email 2)            |
| Blocked / Privacy Blocked | Is Archived         | Either flag marks the user archived                    |
| Job Title                 | Organization Title  | Salesperson/purchaser's job title                      |
| Display Name              | First / Last Name   | Split on the last space — the last word is the surname |
| Phone Number              | Phone Number        | Contact phone number                                   |

## Known Limitations

### Vendors that exist in another connected system

Business Central tells vendors apart by vendor number, so two vendors can share a display name. When another connected system also syncs those vendors, Silkline links them to a single record where it can tell which vendor is meant, and skips the import with an explanation where it cannot. See [When Two Integrations Sync the Same Parts or Suppliers](/configuration/integrations/managing-integrations.md#when-two-integrations-sync-the-same-parts-or-suppliers).

### Orders created directly in Business Central are not imported

Silkline is the source of truth for orders: an order created directly in Business Central is **not** imported into Silkline. Silkline creates orders and writes them to Business Central automatically on change, and reads back only fulfillment progress (received/invoiced quantities and order closure). Master data (vendors, items, salespeople/purchasers) is pulled from Business Central **on a regular schedule**.

### Business Central status and Silkline order state are independent

Neither drives the other, except that a released, fully-received Business Central PO closes the corresponding Silkline order (see [Purchase Order Status](#purchase-order-status)). Silkline never sets the Business Central status on writeback (it's read-only on the API and requires bound actions Silkline doesn't perform).

### Order adjustments collapse to Business Central's single discount

Business Central represents order-level adjustments as one header **Discount Amount**. On writeback, Silkline sends the **net** of all order adjustments (discounts minus fees). Note on tax: Business Central applies the discount to the pre-tax amount and calculates VAT/GST on the discounted total, while Silkline applies the discount after tax — so Silkline's order total may read slightly higher than Business Central's, by the tax on the discount. Two consequences: individual adjustment names are not preserved in Business Central, and if the adjustments **net to a fee** (surcharges exceed discounts) it cannot be represented — Business Central has no positive-adjustment field, so `0` is sent. Silkline keeps the full, named adjustments and does not re-import them on a pull.

### Tax codes are matched to Business Central by name (VAT/GST environments)

An order line's Silkline **tax code** is written to the Business Central purchase line so Business Central calculates the tax. Matching is **by name** — the Silkline tax code's name must exactly equal the Business Central **VAT/GST Product Posting Group** code. If a line carries more than one tax code, only the first is sent. Business Central's order-level **total tax** is not imported as a Silkline adjustment — Silkline manages tax through its own Tax Module, so importing it would double-count. **US sales-tax** environments are not yet supported for tax writeback.

### Need Date is not synchronized

Business Central purchase order lines have a single date field (Expected Receipt Date), which the order item's **ETA** is written to. Silkline's **Need Date** has no Business Central equivalent — it is never written to Business Central and never overwritten by a sync. The ETA is written **to** Business Central but is **not** read back — a receipt date changed directly in Business Central is not reflected in Silkline.

### Line description uses Business Central's Description 2

Business Central purchase order lines have two text fields: `Description` (the material's catalog name) and `Description 2` (free-text). Silkline maps them separately: the linked material's name is written to `Description`, and Silkline's free-text line description round-trips through **`Description 2`**. On ingest, Silkline reads only `Description 2` into the line description — it does not read `Description`, since a line's material name already comes from its linked Silkline material.

### Ship-to location is written to lines, not the purchase order header

An order's ship-to location is written as the **Location Code on each purchase order line**. Business Central's automation API exposes no header-level ship-to *location* field (only free-text ship-to address fields), so Silkline does not set the purchase order's header Ship-to. The line Location Code conveys the location.

### Item revisions come from Item Variants (where available)

Business Central's standard Item API has no revision field. Where an environment models part revisions as **Item Variants**, Silkline reads each variant as its own Material — the variant code becomes the Material's **Revision**, and a variant that is **Blocked** (or **Purchasing Blocked**) in Business Central is marked **archived** in Silkline (so it can't be selected on new orders). Items that have no variants sync as a single Material with no revision, and environments whose connector does not expose Item Variants have no revisions synced at all.

The archived state of a synced material is managed by the sync: block or unblock the variant in Business Central to change it. Archiving or un-archiving the material directly in Silkline is overwritten on the next sync.

### Salespeople/purchasers without email are skipped

A salesperson/purchaser with neither a primary nor a secondary email is skipped during sync, as Silkline requires an email to create a user.

### Placeholder dates are ignored

Business Central uses sentinel values (`1970-01-01` and `0001-01-01`) when no date has been set. These placeholder dates are ignored on both ingest and writeback.

## Frequently Asked Questions

### How often does the data sync?

**Order writeback is automatic** — editing an order in Silkline pushes it to Business Central (when writeback is enabled). Silkline reads back only fulfillment progress on orders, so there's no need to pull orders manually. Master data (vendors, items, users) is pulled from Business Central **on a regular schedule**.

### What happens if a vendor is deactivated?

Vendors in Business Central do not have an active/archived status in the same way as some other systems. All vendors are imported as active suppliers in Silkline.

### What happens when a salesperson/purchaser is deactivated?

When a salesperson/purchaser is marked **Blocked** (or Privacy Blocked) in Business Central, they are marked as archived in Silkline on the next sync.

### My Business Central has multiple companies — which one is used?

The integration uses the **Company ID** specified in the integration configuration. If you need to sync data from multiple companies, create a separate integration for each one.