This article catalogs error messages that subscribers or their MiSP may encounter while running the iPaaS.com integration for Microsoft Dynamics 365 Business Central. Each entry lists the message text as it appears, the condition that causes it, and the recommended resolution. When a transfer is rejected, the details are available in the iPaaS.com Dashboard under Integration Monitoring and in the Error Logs.
Some integration behaviors are not errors and are not listed here. For example, when a record is not found at the source it may be treated as deleted, and some values fall back to defaults — these behaviors do not produce an error message. They are described in the Known Limitations article and in the per-entity mapping documentation instead.
Areas covered: Sales Order FROM iPaaS.com · Sales Invoice FROM iPaaS.com · Payment FROM iPaaS.com · Journal Line FROM iPaaS.com · Company Relationship TO iPaaS.com
Supported Flows
Add/Update Business Central Sales Order FROM iPaaS.com
Add/Update Business Central Sales Invoice FROM iPaaS.com
Add/Update Business Central Payment FROM iPaaS.com
Add/Update Business Central Journal Line FROM iPaaS.com
Add/Update Business Central Company Relationship TO iPaaS.com
Error resolution for additional flows may be added at a later date.
Add/Update Business Central Sales Order FROM iPaaS.com
Duplicate Transaction Risk
Unable to link this sales order to its existing Business Central record by transaction number. This may result in duplicate transaction records.
Description: This error occurs when the integration finds a matching sales order in Business Central for the transaction number but cannot confirm the link between the iPaaS.com transaction and that Business Central record. Because the link could not be confirmed, a subsequent transfer could create a duplicate sales order.
Resolution: Confirm that the sales order exists in Business Central and that the transaction number on the iPaaS.com transaction is correct and unique. Make sure no two source transactions share the same transaction number. If the order and transaction number are correct and the error persists, subscribers or their MiSP can contact iPaaS.com Support.
Customer Creation Failed
The customer required by this sales order could not be created in Business Central, so the order was not transferred.
Description: Before the sales order is written, the integration creates or links the customer it depends on. This error occurs when that customer cannot be created in Business Central, commonly because of a missing required field or invalid customer data.
Resolution: Verify that the customer record in iPaaS.com has the required fields populated, including a customer name and a customer number of 20 characters or fewer. Correct the customer data and retry the transfer. See also the customer number errors below.
Company Creation Failed
The company required by this sales order could not be created in Business Central, so the order was not transferred.
Description: When a sales order is tied to a company, the integration creates or links that company before writing the order. This error occurs when the company cannot be created in Business Central, commonly because of a missing required field or invalid company data.
Resolution: Verify the company data in iPaaS.com, ensure the required fields are populated, and retry the transfer. If the company data is valid and the error persists, subscribers or their MiSP can contact iPaaS.com Support.
Duplicate Transaction Line Risk
Unable to link this order line to its existing Business Central record by transaction number. This may result in duplicate transaction line records.
Description: This error occurs when the integration finds a matching order line in Business Central but cannot confirm the link between the iPaaS.com order line and that Business Central line. Because the link could not be confirmed, a subsequent transfer could create a duplicate order line.
Resolution: Confirm that the sales order and its lines exist in Business Central and that the item SKU and quantity on each line match correctly. If the lines are correct and the error persists, subscribers or their MiSP can contact iPaaS.com Support.
Product Creation Failed
The product for SKU {SKU} could not be created in Business Central, so the order was not transferred.
Description: When an order line references a product that does not yet exist in Business Central, the integration creates that product before transferring the order. This error occurs when the product cannot be created, commonly because of a missing required field or invalid SKU data. The
{SKU}value shows the item that could not be created.Resolution: Verify that the product exists in iPaaS.com with a valid SKU (the product number is required) and that the required product fields are populated. Correct the product data and retry the transfer. See also the product number error below.
Customer Number Required
The customer number is required.
Description: This error occurs while the integration is creating the customer for a sales order or invoice and the customer record has no customer number. Business Central requires a customer number to create the record.
Resolution: Populate the customer number on the iPaaS.com customer record, or map a value to the customer number in the mapping collection so every customer carries one, then retry the transfer.
Customer Number Too Long
The customer number must be 20 characters or fewer.
Description: This error occurs while the integration is creating the customer and the customer number exceeds the 20-character limit that Business Central enforces.
Resolution: Shorten the customer number to 20 characters or fewer in iPaaS.com, or adjust the mapping so the value sent to Business Central stays within the limit, then retry the transfer.
Product Number Required
The product number (SKU) is required.
Description: This error occurs while the integration is creating a product for an order line and the product has no product number (SKU). Business Central requires a product number to create the item.
Resolution: Populate the product number (SKU) on the iPaaS.com product, or map a value to the product number in the mapping collection, then retry the transfer.
Add/Update Business Central Sales Invoice FROM iPaaS.com
The errors in this section are returned by Business Central when it rejects the invoice. The message text comes from Business Central and is recorded in the iPaaS.com Error Logs as received. Most are resolved by correcting Business Central setup or the values mapped from iPaaS.com.
Invalid Tax Code or G/L Account
Invalid tax code or G/L account number is supplied
Description: This error occurs when Business Central rejects a tax code or G/L account number passed from iPaaS.com because the value does not match an active record in Business Central.
Resolution: Confirm that the tax codes and G/L account numbers used by the integration exist and are active in Business Central, and that any static values in the mapping point to valid accounts. Align the tax code and G/L account values between iPaaS.com and Business Central, then retry the transfer.
Missing Inventory Account
Inventory Account is missing in Inventory Posting Setup Location Code: {LocationCode}, Invt. Posting Group Code: {PostingGroup}
Description: This error occurs when Business Central cannot find an Inventory Account in Inventory Posting Setup for the given location code and posting group, which prevents inventory-related postings. The
{LocationCode}and{PostingGroup}values show the combination that is missing setup.Resolution: In Business Central, open Inventory Posting Setup and configure a valid Inventory Account for the specified location code and posting group. Confirm the item is assigned to the correct Inventory Posting Group, then retry the transfer.
Invalid Location Value
Cannot convert the literal 'MAIN' to the expected type 'Edm.Guid'. (locationId)
Description: This error occurs when Business Central expects a unique location identifier but receives a location code such as "MAIN" instead. The value in quotes shows the location code that could not be matched to a Business Central location.
Resolution: Confirm that the location used by the transfer matches a location defined in Business Central and that the mapping resolves the location to the correct Business Central record rather than passing a raw location code. If the location is correct in both systems and the error persists, subscribers or their MiSP can contact iPaaS.com Support.
Missing Customer Posting Group
Customer Posting Group must have a value in Customer: No.={CustomerNo}
Description: This error occurs when the customer used in the transaction has no Customer Posting Group assigned, which prevents Business Central from completing the financial posting. The
{CustomerNo}value identifies the customer.Resolution: In Business Central, open the customer record and assign a valid Customer Posting Group, then retry the transfer.
Unbalanced G/L Entry
Balance must be equal to '0' in G/L Account: No.={AccountNo}
Description: This error occurs when a financial transaction is not balanced — debits do not equal credits — which Business Central requires for all postings. The
{AccountNo}value identifies the affected G/L account.Resolution: Review the transaction so that debit and credit amounts balance, and confirm the posting setup including the Customer Posting Group and General Posting Setup. Correct any missing or incorrect account values in the mapping. If the entry balances and the error persists, subscribers or their MiSP can contact iPaaS.com Support.
Invalid Item Filter
The filter "…" is not valid for the No. field on the Item table
Description: This error occurs when an item number contains characters that Business Central cannot interpret when it looks the item up, so Business Central rejects the lookup. Item numbers that contain forward slashes or other special characters are the most common cause.
Resolution: Confirm that the item number in iPaaS.com does not contain special characters that conflict with how Business Central looks up items. Adjust the item number to remove the conflicting characters where possible. If the item number must contain those characters and the error persists, subscribers or their MiSP can contact iPaaS.com Support.
Add/Update Business Central Payment FROM iPaaS.com
The errors in this section are returned by Business Central when it rejects the payment and are recorded in the iPaaS.com Error Logs as received.
Customer Ledger Entry Not Found
There is no Cust. Ledger Entry within the filter
Description: This error occurs when no customer ledger entry in Business Central matches the criteria the payment is trying to apply against, so the payment cannot be applied or reconciled.
Resolution: Confirm that the customer number, document number, and amount on the payment match an existing open entry in Business Central. Make sure the related invoice is posted and still open (not already applied). Correct the values in the mapping if the references are wrong, then retry the transfer.
Invalid Payment Amount Sign
The "amount" should be a negative number
Description: This error occurs when a payment amount is sent as a positive value but Business Central expects a negative value for the payment or receipt entry.
Resolution: Adjust the mapping so the amount is sent with the sign Business Central expects, and confirm the source value is not already negative (which would otherwise be reversed twice). If the sign is correct and the error persists, subscribers or their MiSP can contact iPaaS.com Support.
Add/Update Business Central Journal Line FROM iPaaS.com
The errors in this section are returned by Business Central when it rejects the journal line and are recorded in the iPaaS.com Error Logs as received.
Missing Journal Identification
You must specify a journal batch ID or a journal ID to get a journal line
Description: This error occurs when a journal line is created or retrieved without identifying which journal it belongs to, so Business Central cannot determine the target journal.
Resolution: Confirm that the journal exists in Business Central and that the journal identifier is populated in the mapping collection so every journal line is tied to a journal. After the journal reference is mapped, retry the transfer. If the journal is correct and the error persists, subscribers or their MiSP can contact iPaaS.com Support.
Invalid Account Reference
The field Account No. of table Gen. Journal Line contains a value ({AccountNo}) that cannot be found in the related table ({TableName})
Description: This error occurs when a journal line references an account number that does not exist in the related Business Central table — for example a vendor, customer, or G/L account — which fails validation. The
{AccountNo}and{TableName}values show the value that could not be found and where Business Central looked for it.Resolution: Confirm that the referenced account number exists in the correct table in Business Central, and update the mapping or source data in iPaaS.com to use a valid account number. Keep the master data consistent between iPaaS.com and Business Central, then retry the transfer.
Add/Update Business Central Company Relationship TO iPaaS.com
Contacts Web Service Missing the Company Link Field
Could not find a property named 'CompanyNo' on type 'NAV.Contacts'
Description: This error occurs while the integration reads a company's relationships from Business Central. The integration links each related person to its company using the Company No. field on the Business Central Contacts Web Service. When the Contacts Web Service does not expose that field, Business Central rejects the request and no relationships are captured for the company.
Resolution: Customize the Business Central Contact Card (Contacts) Web Service to expose the Company No. field, then retry. The company-relationship capture requires this field to match each person to its company. Subscribers or their MiSP can contact iPaaS.com Support for assistance customizing Business Central Web Services.