Overview
This article catalogs the error messages the Microsoft Dynamics 365 Business Central integration can record in the iPaaS.com Error Logs, grouped by flow. Each entry carries a stable error code you can search for on this page, the message a subscriber sees, what causes it, and how to resolve it. When a transfer is rejected, the details are available in the iPaaS.com Dashboard under Integration Monitoring and in the Error Logs.
Some resolutions refer to your Managed Integration Service Provider (MiSP) — the partner who manages your integration's mappings, configuration, credentials, and reconciliation. 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.
iPaaS.com categorizes errors by families. You can learn more about that categorization at Understanding iPaaS.com API Error Codes.
Supported Flows
Sales Order FROM iPaaS.com
Sales Invoice FROM iPaaS.com
Payment FROM iPaaS.com
Journal Line FROM iPaaS.com
Company Relationship TO iPaaS.com
Sales Order Tracking Number TO iPaaS.com
Error resolution for additional flows may be added at a later date.
Error Collection
Sales Order FROM iPaaS.com
Duplicate Transaction Risk
BC-BIZL-1001 - Unable to link this sales order to its existing Business Central record by transaction number. This may result in duplicate transaction records.
Description: The integration found a matching sales order in Business Central for the transaction number but could not 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, with no two source transactions sharing the same transaction number. If a duplicate results, your MiSP can help reconcile it.
Customer Creation Failed
BC-BIZL-1002 - 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, then retry the transfer. See also the customer number errors below.
Company Creation Failed
BC-BIZL-1003 - 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 data is valid and the error persists, your MiSP can review the company mapping.
Duplicate Transaction Line Risk
BC-BIZL-1004 - Unable to link this order line to its existing Business Central record by transaction number. This may result in duplicate transaction line records.
Description: The integration found a matching order line in Business Central but could not 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 each line's item SKU and quantity match correctly. If a duplicate line results, your MiSP can help reconcile it.
Product Creation Failed
BC-BIZL-1005 - 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, then retry the transfer. See also the product number error below.
Customer Number Required
BC-VALD-1001 - 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
BC-VALD-1002 - 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
BC-VALD-1003 - 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.
Company Relationship TO iPaaS.com
Customer Record Not Found
BC-NFND-1001 - Customer record not found. Please create the customer manually in iPaaS.com using the following Business Central id: {id}
Description: While reading a company's relationships from Business Central, the integration looks up the related customer in iPaaS.com by its Business Central id. This error occurs when no matching customer exists in iPaaS.com, so the relationship cannot be linked. The
{id}value shows the Business Central customer id that was not found.Resolution: Create the customer in iPaaS.com so it exists before the company relationship is transferred — transfer the customer first, or confirm the customer mapping brings the record into iPaaS.com. Once the customer exists with the matching Business Central id, retry the transfer.
Sales Order Tracking Number TO iPaaS.com
Shipping Method Not Found
BC-NFND-1002 - Shipping Method ({LocationCode}) needs to be created manually in iPaaS.com first
Description: When a Business Central sales order's tracking (shipment) is captured into iPaaS.com, the integration resolves the shipment's location code to a shipping method in iPaaS.com. This error occurs when no shipping method matching that location code exists in iPaaS.com yet, so the tracking record cannot be linked to one. The
{LocationCode}value shows the location code that could not be matched.Resolution: Create the shipping method in iPaaS.com so it exists before the tracking number is captured — transfer the shipping method from Business Central first, or confirm the shipping-method mapping brings it into iPaaS.com. Once a shipping method matching the location code exists, retry the transfer.
External Business Central API Errors
Business Central API Call Failed
BC-EXTN-1001 - Business Central returned an error and the request was rejected.
Description: The integration calls Business Central's API to create or update records for the Sales Invoice, Payment, Journal Line, and Company Relationship flows. When Business Central rejects a request, its error response is recorded in the iPaaS.com Error Logs under this code, with the specific Business Central message included. The most common Business Central messages, their causes, and how to resolve them are listed below.
Resolution: Read the specific Business Central message included with the error and follow the matching guidance in the table below. Most are resolved by correcting Business Central setup or the values mapped from iPaaS.com, then retrying the transfer.
Flow | Business Central message | Cause | Resolution |
Sales Invoice FROM iPaaS.com | Invalid tax code or G/L account number is supplied | A tax code or G/L account number passed from iPaaS.com does not match an active record in Business Central. | Confirm 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 values between iPaaS.com and Business Central, then retry. |
Sales Invoice FROM iPaaS.com | Inventory Account is missing in Inventory Posting Setup Location Code: {LocationCode}, Invt. Posting Group Code: {PostingGroup} | Business Central cannot find an Inventory Account in Inventory Posting Setup for the given location code and posting group. | In Business Central, open Inventory Posting Setup and configure a valid Inventory Account for the location code and posting group. Confirm the item is assigned to the correct Inventory Posting Group, then retry. |
Sales Invoice FROM iPaaS.com | Cannot convert the literal 'MAIN' to the expected type 'Edm.Guid'. (locationId) | Business Central expected a unique location identifier but received a location code such as "MAIN". | Confirm 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. |
Sales Invoice FROM iPaaS.com | Customer Posting Group must have a value in Customer: No.={CustomerNo} | The customer used in the transaction has no Customer Posting Group assigned. | In Business Central, open the customer record and assign a valid Customer Posting Group, then retry. |
Sales Invoice FROM iPaaS.com | Balance must be equal to '0' in G/L Account: No.={AccountNo} | The financial transaction is not balanced — debits do not equal credits. | Review the transaction so 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. |
Sales Invoice FROM iPaaS.com | The filter "…" is not valid for the No. field on the Item table | An item number contains characters Business Central cannot interpret when it looks the item up (forward slashes or other special characters are the most common cause). | Remove the conflicting special characters from the item number in iPaaS.com where possible, then retry. |
Payment FROM iPaaS.com | There is no Cust. Ledger Entry within the filter | No customer ledger entry in Business Central matches the criteria the payment is applying against. | Confirm the customer number, document number, and amount on the payment match an existing open entry in Business Central, and that the related invoice is posted and still open. Correct the mapped references if they are wrong, then retry. |
Payment FROM iPaaS.com | The "amount" should be a negative number | A payment amount is sent as a positive value but Business Central expects a negative value for the entry. | Adjust the mapping so the amount is sent with the sign Business Central expects, and confirm the source value is not already negative. |
Journal Line FROM iPaaS.com | You must specify a journal batch ID or a journal ID to get a journal line | A journal line is created or retrieved without identifying which journal it belongs to. | Confirm 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, then retry. |
Journal Line FROM iPaaS.com | The field Account No. of table Gen. Journal Line contains a value ({AccountNo}) that cannot be found in the related table ({TableName}) | 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). | Confirm 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, then retry. |
Company Relationship TO iPaaS.com | Could not find a property named 'CompanyNo' on type 'NAV.Contacts' | The integration links each related person to its company using the Company No. field on the Business Central Contacts Web Service, and that field is not exposed by the Web Service. | Customize the Business Central Contact Card (Contacts) Web Service to expose the Company No. field, then retry. iPaaS.com Support can assist with customizing Business Central Web Services. |