Create a subscriptions

Learn how to setup Subscriptions, used for receiving data from other Business Central companies.

5 minute read

After setting up the Topic, create a Subscription for each Party in the receiving company or companies. Each Subscription corresponds to a Party from which data is received.

In a multiple Business Central environment using Azure Service Bus, run the Topic in the sending company before setting up the Subscription.

Subscription Card

Select the 🔎 icon, enter Subscriptions (IDM), and select the related link.
Enter the Party code for the sending company and select the related Topic.
Pryme Intercompany Project only:
- Inv. Setup template defines the default invoice template for intercompany projects. Leave blank to add templates manually.
- Res. price template specifies the transfer pricing list for projects.
Review and adjust tables under Subscription Tables. Delete tables that should not be imported. Re-add deleted tables if needed (limited to tables present in the Topic).
Use Subscription Fields to modify field-level data processing, mapping, and rules.

Subscription Fields

Subscription fields control how data is imported and processed. When importing a table, field-level mapping is possible, provided the field is included in the Topic message.

When changing or mapping a field, use the Comment field to document the changes. The Relation Table Caption specifies the related table. If a related table exists, the imported value must be present in the receiving company’s table; otherwise, the record will not be imported.

A field can be mapped in four different ways:

Type	Description
Value	One-to-one mapping.
Filter	Conditional updates based on filters.
Fixed	Assigns a fixed value to all imported transactions.
Currency	Manages local currency conversions.

Currency Mapping

Currency mapping ensures proper handling of differing local currencies (LCY) between companies. Setup requires configuring the Currency Code for each Party and the LCY Code in the General Ledger Setup.

If the currency code in the subscription message is blank, the Currency Code from the Party code will be used.
If the currency code in the subscription message matches the Currency Code on the Party code, the currency field will be set to blank.

Note!

When a record is received from another company through a Topic, a Subscription record is created. This record tracks its origin and whether it was created by another company or updated. If a record was originally created by another company, any local changes will not be sent to other companies. If a record, such as a payment term, was created outside the Intercompany (IC) process, there will be no agreement on ownership. Consequently, changes made across companies will be synchronized and transferred. To resolve such conflicts, update the Subscription record manually by setting the Data owned by party field.

Subscription Fields in Pryme Intercompany Project

In the Pryme Intercompany Project app, specific fields must be mapped to ensure correct values in the receiving company’s projects.

Project (Table 167 – Job)

Target Field No	Target Field Name	Mapping Value	Comment
5	Bill-to Customer No.	Fixed	Always map to the sending company’s customer number in the receiving company.
20	Person Responsible		Verify if it matches the sending company.
23	Job Posting Group		Verify if it matches the sending company.
1011	Invoice Currency Code	Currency	Use Currency if an intercompany transfer pricing list exists in another currency.
2000	Sell-to Customer No.	Fixed	If the customer table is not part of Master Data, map to the sending company’s customer number.
14045651	Resource Invoice Type	Value	Map to T&M if a fixed price agreement exists.
14045655	Item Invoice Type	Value	Map to T&M if a fixed price agreement exists.
14045656	Expense Invoice Type	Value	Map to T&M if a fixed price agreement exists.
14045674	Project Manager PGS		Verify if the resource matches the sending company.
14045753	Timesheet Currency Code	Currency	Use Currency if an intercompany transfer pricing list exists in another currency.

Job Task (Table 1001 – Job Task)

Target Field No	Target Field Name	Mapping Value	Comment
14045764	Contract Type PGS	Value	Map to T&M if a fixed price agreement exists.
14045709	Project Manager PGS		Verify if the resource matches the sending company.

Permissions (Table 14045676 - Permissions PM)

This table is not mandatory. If permission from the sending company is unnecessary, delete the table.

Target Field No	Target Field Name	Mapping Value	Comment
1	No		Verify if the resource matches the sending company.

Time (Table 156 – Resource)

Target Field No	Target Field Name	Mapping Value	Comment
51	Gen Prod Posting Grp		Verify if it matches the sending company.
58	VAT Prod Posting Grp		Verify if it matches the sending company.

Note!

The Intercompany Project app does not include cost price as part of its default setup. Handle cost prices using one of the following approaches:

Manually input the cost price for external resources in the receiving company.
Automate using Resource Group / Resource Subgroup. Create a dedicated group/subgroup for IC resources and add transfer pricing rates. Map IC resources to the designated group/subgroup.

Project Ledger Entries (Preview Feature)

This feature transfers resource, expense, and item ledgers between companies. Testing should be conducted in a Sandbox environment before production use. Contact support to enable it in a production environment.

Job Journal Line (Table 210)

Target Field No	Target Field Name	Mapping Value	Comment
1008	Currency Code	Currency	See Currency Mapping.
14045810	Expense Payment Type	Value	Map expense payment types for intercompany transactions.

Test the Setup

After creating the Topic and corresponding Subscription, test the setup:

Send one entry from the sending company.
Run the subscription manually in the receiving company using Run Subscription.
When successful, configure a Job Queue for automated subscription processing.

For details on job queue setup, see Set Up Job Queues.

Update a Subscription After Changing the Topic

If changes are made to the Topic field definitions, update the Subscription manually:

Select the 🔎 icon, enter Subscriptions (IDM), and select the related link.
Navigate to Update Source Fields under the Action tab.
Open the Subscription Card.
Select Subscription Fields in the table to update.
Locate the field to add.
In Source Field No, add the Table No (same as Target Field No).