---
title: "Vendor replication"
slug: "bc-vendor-replication"
description: "Learn to synchronize vendor master data efficiently using a single internal document for both publication and subscription connections in D365 BC."
tags: ["BC", "BIS", "Business Central", "Business Integration Solutions", "Walkthrough"]
updated: 2026-06-25T09:59:07Z
published: 2026-06-25T09:59:07Z
canonical: "docs.staedean.com/bc-vendor-replication"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.staedean.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Vendor replication

This walkthrough provides an overview of how to synchronize vendor master data.

This is a simple replication demonstrating how you can use the same internal document for both publication and subscription connections when the table structure is the same, saving time and effort.

## Prerequisites

You can create two companies for demonstration purposes. In the following scenario:

- CRONUS International Ltd.: publishing company
- CRONUS Sales: subscription company

| Template | Description | Type | Company |
| --- | --- | --- | --- |
| TI_RM_VENDOR.OUT | STAEDEAN Template: Publish Vendors for Synchronization | Publication | CRONUS International Ltd. |
| TI_RM_VENDOR.IN | STAEDEAN Template: Subscribe Vendors for Synchronization | Subscription | CRONUS Sales |

## Publish vendors template

### Story

This connection uses the following pipeline elements:

- The **Timer Event** triggers the pipeline.
- The **XML Generator** activity creates an XML file based on the internal document.
- The **File Writer** endpoint stores the created XML file at a specified file location.

![Vend Out](https://cdn.document360.io/da662430-6a41-47b1-8c7e-7e4ac37a9756/Images/Documentation/DM_VendorOut_Pipeline.png)

### Setup

1. Select the publishing company. ![Company - CRONUS International](https://cdn.document360.io/da662430-6a41-47b1-8c7e-7e4ac37a9756/Images/Documentation/DM_CRONUSInternationalLtd.png)
2. Import the Publication-TI_RM_Vendor.OUT.zip configuration package. ![VO Import](https://cdn.document360.io/da662430-6a41-47b1-8c7e-7e4ac37a9756/Images/Documentation/DM_VendorOut_Import.png)
3. Open the TI_RM_VENDOR.OUT connection. On the connection page, edit the **File Writer** settings and enter the folder name. ![VO Settings](https://cdn.document360.io/da662430-6a41-47b1-8c7e-7e4ac37a9756/Images/Documentation/DM_VendorOut_Settings.png)

### Process

1. Process the connection.
2. Check the output folder location.

### Result

![VO Settings](https://cdn.document360.io/da662430-6a41-47b1-8c7e-7e4ac37a9756/Images/Documentation/DM_VendorOut_Result.png)

One XML file with a complete overview of your vendors is created and available at the specified location.

## Subscribe vendors template

### Story

This connection uses the following pipeline elements:

- The **File Reader** endpoint reads the published file from the file system.
- The XML file contains a complete list of vendors. The **Splitter** activity creates one message per vendor for proper traceability.
- The **Record Generator** activity creates records and updates the D365 BC tables based on the internal document.

> [!NOTE]
> **Note**
> 
> In this scenario, the table structure is the same as in the publishing company, and the various posting groups (Gen. Bus. Posting Group, VAT Bus. Posting Group, and Vendor Posting Group) already exist in the system. Therefore, the same internal document as the publishing connection is used.

![VI Pipeline](https://cdn.document360.io/da662430-6a41-47b1-8c7e-7e4ac37a9756/Images/Documentation/DM_VendorIn_Pipeline.png)

### Setup

1. Select the subscription company. ![Company - CRONUS Sales](https://cdn.document360.io/da662430-6a41-47b1-8c7e-7e4ac37a9756/Images/Documentation/DM_CRONUSales.png)
2. Import the Subscription-TI_RM_VENDOR.IN.zip configuration package. ![VI Import](https://cdn.document360.io/da662430-6a41-47b1-8c7e-7e4ac37a9756/Images/Documentation/DM_VendorIn_Import.png)
3. Open the TI_RM_VENDOR.IN connection. On the connection page, edit the **File Reader** settings and enter the folder name. ![VI Settings](https://cdn.document360.io/da662430-6a41-47b1-8c7e-7e4ac37a9756/Images/Documentation/DM_VendorIn_Settings.png)

> [!NOTE]
> **Note**
> 
> The **File Reader** endpoint includes typical Replication Management properties: **Leave File on File System**, **Read New Files Only**, and **Last Processed at**. In many cases, the internal document from the publication connection can reuse for the subscription connection.

### Process

1. Process the connection.
2. If processing succeeds, select **History** to check the result. Select the message entry, then select **Actions** > **Show Record**.

### Result

![VI Settings](https://cdn.document360.io/da662430-6a41-47b1-8c7e-7e4ac37a9756/Images/Documentation/DM_VendorIn_Result.png)

The vendors are imported. You can also use the **Transaction Log** to see more details for each import.

## Related

- [Customer replication](/bc-customer-replication.md)