Contents
Summary
Company records can be sent from iPaaS.com to Microsoft Dynamics 365 Business Central, where each company is written as a customer company record. This family covers two collections: Add Dynamics 365 Business Central Company FROM iPaaS.com creates a new customer company in Business Central, and Update Dynamics 365 Business Central Company FROM iPaaS.com refreshes an existing one. Both populate the company number and name, the email address, the primary billing address details (address, city, county, post code, country, and phone), and the customer price group resolved from the company's categories.
The Add collection also sets the posting groups, payment terms, and tax area that govern how the company's transactions post in Business Central; the Update collection deliberately leaves those values unchanged so settings established at creation are not overwritten. Whether an incoming company is created or updated is decided by whether the iPaaS.com company is already linked to a Business Central company, not by which event fired. The two collections are designed to work together: new companies flow through Add, and subsequent changes flow through Update.
ID Format
Manual Sync ID Format
When transferring a company from the iPaaS.com Manual Sync page, enter the iPaaS.com company record ID of the company to transfer.
Example: 1532
External ID Format
After a successful transfer, iPaaS.com saves the company number as the external ID on a dedicated external-ID record. This external ID routes every later update to the same Business Central company rather than creating a duplicate. The company is identified in Business Central by its company number — the No. field on the company's customer card. As a fallback, when no external-ID record exists yet and the iPaaS.com company id matches an existing Business Central company number, the records are linked automatically instead of creating a duplicate.
Deleted Record Support
Delete is not supported in this direction. These collections create and update customer company records in Business Central; they do not delete them. Delete mappings are not included in the default templates, and deleting a company in iPaaS.com does not remove the corresponding Business Central company. Subscribers who need to retire a Business Central company should manage that directly in Business Central.
Custom Field Support
Both the Add and Update collections support custom fields. To set a Business Central company field that is not already in the standard mapping list:
In Business Central, customize the relevant Web Service so it accepts the field on the company request. Subscribers or their MiSP can contact iPaaS.com Support for assistance customizing Business Central Web Services.
In iPaaS.com, create a custom field whose name matches the Business Central field name you want to populate.
Map the new custom field to a static or dynamic value in the appropriate collection.
Each custom field's name and value is included in the company record sent to Business Central as-is. The name must be a valid company field in your Business Central environment, or Business Central rejects the request.
Mapping Collection Status
Status: Enabled (both collections)
Trigger Events: Company Create, Company Update. These collections dispatch automatically once subscribers or their MiSP subscribe to the iPaaS.com company outbound triggers. Enable them in the subscription configuration's Outbound Data Flows section by subscribing to the company create and update events. Until those subscriptions are enabled, no automatic transfers occur, and a Manual Sync can be run at any time. Whether an incoming company is created through the Add collection or updated through the Update collection is decided by whether the iPaaS.com company is already linked to a Business Central company, not by which event fired.
Neither collection has a mapping filter applied, so every company record sent through either collection is processed.
Duplicate or Conflicting Mappings
These two collections operate on the same Business Central customer company and are designed to complement each other — Add creates, Update refreshes. Other collections also write company data:
Add Dynamics 365 Business Central Company FROM iPaaS.com and Update Dynamics 365 Business Central Company FROM iPaaS.com both write companies from iPaaS.com into Business Central. They are partitioned by whether the company is already linked, so a single company is not created twice.
Add/Update Dynamics 365 Business Central Company TO iPaaS.com and its child collections write in the opposite direction, capturing companies from Business Central into iPaaS.com rather than creating them in Business Central.
Before enabling these collections together, review their Add/Update settings and decide which system is the source of truth for company data, so the same company is not written in conflicting directions.
Collision Handling
This integration does not provide configurable collision-handling methods for the company collections. There is no subscriber-selectable conflict-resolution option on these collections. Companies are instead matched to their Business Central record by the saved external ID (the company number) — see Duplicate Matching.
Duplicate Matching
Before a company is created or updated, the integration checks whether the iPaaS.com company is already linked to a Business Central record. When it is not yet linked, the integration looks up the company in Business Central by its company number and, if a match is found, links the iPaaS.com company to that existing Business Central record instead of creating a duplicate. Matching is performed on the company number, so keep the iPaaS.com company id aligned with the intended Business Central company number.
Supported Child Collections
Neither collection has child collections. The company's primary billing address values are written directly onto the company record in Business Central from the iPaaS.com company's primary billing address; there is no separate address child collection in this direction.
System Caveats
Microsoft Dynamics 365 Business Central Caveats
Posting groups, payment terms, and tax area must already exist (Add): the Customer Posting Group, Gen. Bus. Posting Group, Payment Terms Code, and Tax Area Code values the Add collection sends are validated by Business Central against records that must already exist in your company. The collection ships with example values that will not match your company — replace each with a value configured in your Business Central setup before the first transfer, or the transfer fails when Business Central rejects the unknown value. See the mapping table for the specific placeholder values.
Posting groups, payment terms, and tax area are preserved on update (Update): the Update collection intentionally leaves those four values unchanged so the settings established when the company was created are not overwritten. To change them from iPaaS.com, adjust the company directly in Business Central or change these mappings.
Update target must exist (Update): the Update collection updates an existing Business Central company. When the company cannot be found in Business Central, the update is rejected. New companies are created through the Add collection.
Company number length: Business Central limits the company number to 20 characters; the company number must be present and within that limit, or the transfer is rejected.
Country/region code: the country value must be 10 characters or fewer and must match an existing country/region code in your Business Central company, or Business Central rejects the record.
Single price group from categories: iPaaS.com supports multiple category assignments whereas Business Central allows only one — the customer price group is set from the first category in the list, and only when that category resolves to a configured price group in Business Central.
iPaaS.com Caveats
Primary billing address required for address fields: the address, city, county, post code, country, and phone fields populate (Add) or refresh (Update) only when the iPaaS.com company has an address flagged as the primary billing address. Without one, those fields are left unset on a new company or unchanged on an existing company.
Company name and email are required: Business Central requires a company name, and the email address is treated as a required field. A company sent without a name cannot be written.
Custom fields must be valid Business Central fields: a mapped custom field stores a value only when its name is a valid company field in your Business Central environment; otherwise Business Central rejects the request.
Setup Requirements
Microsoft Dynamics 365 Business Central Configuration
Enable Web Services for Customers, Customer Card, Contact Card, and Customer Price Group so the integration can read and write company records.
Create the Customer Posting Group, Gen. Bus. Posting Group, Payment Terms Code, and Tax Area Code records that the Add collection will reference, and confirm the codes used in the mappings exist in your company.
Configure country/region codes so they match the country values coming from iPaaS.com.
Configure the customer price groups that the company's categories resolve to.
If custom fields are mapped, customize the relevant Web Service to accept them.
Authentication uses Microsoft Dynamics 365 Business Central API credentials; ensure they are stored securely in the iPaaS.com credential manager.
For the full installation walkthrough, see the Installation Instructions.
iPaaS.com Configuration
Subscribe to the company create and update events in the Outbound Data Flows section to enable automatic transfers.
Ensure company records carry a valid name, email, and a primary billing address.
Configure categories on companies if the customer price group mapping is needed.
Create custom fields whose names match the Business Central company field names for any custom-field mappings in use.
Subscribers or their MiSP can contact iPaaS.com Support for assistance configuring Business Central Web Services.
Business Central enforces company field requirements through your company configuration and does not publish them in a public API specification; validate them in a staging environment before relying on them in production.
Integration Flow
A company is created or updated in iPaaS.com.
Once the company outbound triggers are enabled, the create or update event dispatches the company to Business Central; alternatively, a subscriber triggers a Manual Sync using the iPaaS.com company record ID.
The integration checks whether the iPaaS.com company is already linked to a Business Central company. When it is not yet linked, it looks up the company in Business Central by company number and links the records if a match is found, instead of creating a duplicate.
iPaaS.com authenticates with Business Central and routes the company to the Add collection (new company) or the Update collection (existing company).
The company identity and contact fields are mapped: company number, name, and email.
The primary billing address fields — address, city, county, post code, country, and phone — are taken from the company's primary billing address in iPaaS.com when one is flagged.
The company's categories are resolved to a Business Central customer price group code, using the first category that resolves to a configured price group.
For a new company, the Add collection sets the posting groups, payment terms, and tax area from its configured values; for an existing company, the Update collection leaves those values unchanged.
The company record is created or updated in Business Central.
Transfer status and any errors are recorded in the iPaaS.com Dashboard under Integration Monitoring and the Error Logs.
Mappings
Add Dynamics 365 Business Central Company FROM iPaaS.com
iPaaS.com data type: Company
This collection creates a new customer company in Business Central. It has no mapping filter, so every company sent through it is processed.
Mapping Type | Source Field (iPaaS.com) | Destination Field (Microsoft Dynamics 365 Business Central) | Description |
Dynamic Formula |
| No | Required. Sets the Business Central company number from the iPaaS.com company record ID. It is the key used to match, link, and later update the company, and is saved as the external ID. The number must be present and is limited to the Business Central 20-character maximum. |
Field |
| Name | Required. Sets the company name from the iPaaS.com company name. Business Central requires a company name. |
Field |
| Required. Sets the company email from the iPaaS.com company email address. | |
Dynamic Formula |
| Address | Recommended. Sets the address line from the company's primary billing address in iPaaS.com — the first address flagged as primary billing. Left unset when the company has no primary billing address. |
Dynamic Formula |
| City | Recommended. Sets the city from the company's primary billing address. Left unset when the company has no primary billing address. |
Dynamic Formula |
| County | Recommended. Sets the county from the region on the company's primary billing address. Left unset when the company has no primary billing address. |
Dynamic Formula |
| CountryRegionCode | Recommended. Sets the country/region code from the country on the company's primary billing address. The value must be 10 characters or fewer and must match an existing country/region code in your Business Central company. Left unset when the company has no primary billing address. |
Dynamic Formula |
| PostCode | Recommended. Sets the post code from the postal code on the company's primary billing address. Left unset when the company has no primary billing address. |
Dynamic Formula |
| PhoneNo | Recommended. Sets the phone number from the phone on the company's primary billing address. Left unset when the company has no primary billing address. |
Dynamic Formula |
| CustomerPriceGroup | Recommended. Resolves the iPaaS.com company's categories to the matching Business Central customer price group code. Set only when the categories resolve to a configured price group, which must already exist in your Business Central company. Because Business Central allows a single price group per company, the first category in the list is used. By default the price group is cleared when the matching category is removed in iPaaS.com. |
Static |
| GenBusPostingGroup | Required (placeholder — replace during implementation). Sets the general business posting group, which controls how the company's transactions post. |
Static |
| CustomerPostingGroup | Required (placeholder — replace during implementation). Sets the customer posting group, which controls how the company's transactions post to the general ledger. |
Static |
| PaymentTermsCode | Required (placeholder — replace during implementation). Sets the payment terms for the company. |
Static |
| TaxAreaCode | Required (placeholder — replace during implementation). Sets the tax area for the company. |
Note on the posting group, payment terms, and tax area values. The four static codes above are hard prerequisites: Business Central validates each against an existing record, and the first transfer fails when the code does not exist in your company. Either confirm a record with the matching code exists in your Business Central setup, or change the static value to a code that does. The example screenshots below show where each record type is maintained in Business Central.
Update Dynamics 365 Business Central Company FROM iPaaS.com
iPaaS.com data type: Company
This collection updates an existing customer company in Business Central. It has no mapping filter, so every company sent through it is processed. The company must already exist in Business Central — when it cannot be found, the update is rejected.
Mapping Type | Source Field (iPaaS.com) | Destination Field (Microsoft Dynamics 365 Business Central) | Description |
Dynamic Formula |
| No | Required. Preserves the existing Business Central company number on update by reusing the value already on the Business Central record rather than replacing it. It is the key used to match the company and stays within the 20-character limit. |
Field |
| Name | Required. Updates the company name from the iPaaS.com company name. Business Central requires a company name. |
Field |
| Required. Updates the company email from the iPaaS.com company email address. | |
Dynamic Formula |
| Address | Recommended. Updates the address line from the company's primary billing address in iPaaS.com. Left unchanged when the company has no primary billing address. |
Dynamic Formula |
| City | Recommended. Updates the city from the company's primary billing address. Left unchanged when the company has no primary billing address. |
Dynamic Formula |
| County | Recommended. Updates the county from the region on the company's primary billing address. Left unchanged when the company has no primary billing address. |
Dynamic Formula |
| CountryRegionCode | Recommended. Updates the country/region code from the country on the company's primary billing address. The value must be 10 characters or fewer and must match an existing country/region code in your Business Central company. Left unchanged when the company has no primary billing address. |
Dynamic Formula |
| PostCode | Recommended. Updates the post code from the postal code on the company's primary billing address. Left unchanged when the company has no primary billing address. |
Dynamic Formula |
| PhoneNo | Recommended. Updates the phone number from the phone on the company's primary billing address. Left unchanged when the company has no primary billing address. |
Dynamic Formula |
| CustomerPriceGroup | Recommended. Resolves the iPaaS.com company's categories to the matching Business Central customer price group code. Set only when the categories resolve to a configured price group, which must already exist in your Business Central company. Because Business Central allows a single price group per company, the first category in the list is used. |
Dynamic Formula |
| GenBusPostingGroup | Preserved on update (by design). Leaves the general business posting group unchanged so the value set when the company was created is not overwritten. To update it from iPaaS.com, replace this with a value or formula that returns an existing Gen. Bus. Posting Group code. |
Dynamic Formula |
| CustomerPostingGroup | Preserved on update (by design). Leaves the customer posting group unchanged so the value set at creation is not overwritten. To update it from iPaaS.com, replace this with a value or formula that returns an existing Customer Posting Group code. |
Dynamic Formula |
| PaymentTermsCode | Preserved on update (by design). Leaves the payment terms unchanged so the value set at creation is not overwritten. To update it from iPaaS.com, replace this with a value or formula that returns an existing Payment Terms code. |
Dynamic Formula |
| TaxAreaCode | Preserved on update (by design). Leaves the tax area unchanged so the value set at creation is not overwritten. To update it from iPaaS.com, replace this with a value or formula that returns an existing Tax Area code. |
Note on preserved values. The four return null; formulas above are intentional, not unfinished mappings. They keep the posting groups, payment terms, and tax area that were established when the company was created in Business Central, so a routine company update from iPaaS.com does not disturb the accounting setup. To bring any of these under iPaaS.com control, replace the formula with one that returns a valid Business Central code.
Error Handling
For the complete catalog of error messages this integration can produce, see the Error Messages article. The errors most relevant to the company transfer are:
Unrecognized posting group, payment terms, or tax area (Add): Business Central rejects the company when the Customer Posting Group, Gen. Bus. Posting Group, Payment Terms Code, or Tax Area Code value does not match an existing record. Resolution: subscribers or their MiSP should confirm a matching record exists in Business Central or change the static value to an existing code, then re-transfer.
Missing company number: The company number is required and is the key that links each transfer to its Business Central company. Resolution: ensure the iPaaS.com company carries a value that maps to a present company number before transferring.
Company number too long: The company number must be 20 characters or fewer. Resolution: shorten the iPaaS.com company id used as the number so it fits the limit.
Update target not found (Update): The Update collection requires the company to already exist in Business Central. When it cannot be found, the update is rejected. Resolution: create the company through the Add collection first, or confirm the company number matches an existing Business Central record.
Country/region code not recognized: The country value must be 10 characters or fewer and must match an existing country/region code. Resolution: align the iPaaS.com country value with a configured Business Central country/region code.
Errors and transfer status for every company transfer are recorded in the iPaaS.com Dashboard under Integration Monitoring and the Error Logs.
Validation Rules
Company number: must be present, 20 characters or fewer, and is the key used to match and link the company.
Required fields: the company name and email must be present; Business Central requires a company name.
Posting groups, payment terms, tax area (Add): the configured codes must exist in Business Central before the first transfer.
Update target (Update): the company must already exist in Business Central or the update is rejected.
Country/region code: must be 10 characters or fewer and match an existing Business Central country/region code.
Price group: set only when the company's categories resolve to a configured Business Central price group; the first resolving category is used.
Testing and Validation
Test Scenarios
Valid company creation. Send a new company from iPaaS.com with a name, email, and a primary billing address, with the posting group, payment terms, and tax area static values set to codes that exist in Business Central. Confirm the customer company is created with the correct number, name, email, and address.
Required code validation. Send a company while the Add collection still carries an example posting group, payment terms, or tax area code that does not exist in Business Central. Confirm the transfer fails, then confirm that correcting the code and re-transferring succeeds.
Price group mapping. Send a company whose categories resolve to a configured Business Central price group. Confirm the customer price group is assigned from the first resolving category.
Company update preserves accounting setup. Update an existing company from iPaaS.com (for example, change the name or address). Confirm the name and address change while the posting groups, payment terms, and tax area set at creation remain unchanged.
Update target missing. Run the Update collection for a company that does not exist in Business Central. Confirm the update is rejected and that creating the company through the Add collection first resolves it.
Duplicate matching. Send a company whose number matches an existing Business Central company that is not yet linked. Confirm the records are linked instead of a duplicate being created.
Manual Sync. From the Manual Sync page, transfer a specific company using its iPaaS.com company record ID and confirm the correct company is written.
Validation Checklist
The iPaaS.com company carries a present, unique value that maps to a company number 20 characters or fewer.
The company name and email are present.
The posting group, payment terms, and tax area codes used by the Add collection exist in Business Central.
Country/region codes in iPaaS.com match configured Business Central country/region codes.
Customer price groups exist in Business Central for the categories in use.
Custom fields, if mapped, name valid Business Central company fields and the Web Service is customized to accept them.
The required Web Services are enabled in Business Central.
Additional Notes
The Add and Update collections divide the work by link state: a company that is not yet linked to a Business Central record is created through Add, and a linked company is refreshed through Update. The company number is the matching key throughout.
The Update collection deliberately preserves the company number and the posting groups, payment terms, and tax area. Routine updates from iPaaS.com change the name, email, address, and price group only; the accounting setup established at creation is left intact unless those mappings are changed.
iPaaS.com supports multiple category assignments per company, but Business Central accepts a single customer price group — only the first resolving category is used. This is a current limitation at the time this documentation was written.
Delete is not supported in this direction; deleting a company in iPaaS.com does not remove the Business Central company.
Related Documents
Connections and Settings (pending publication)
Known Limitations (pending publication)