Overview
This article lists the error messages that the Acumatica integration can report, organized by the data flow that produces them. Each entry shows the message text, the condition that causes it, and the steps subscribers or their MiSP can take to resolve it.
When a transfer fails, the message is recorded against the affected record. To review it, open your integration Dashboard, go to Integration Monitoring, and open the Error Logs. Use the wording of the message to locate the matching entry below.
Some errors are produced by editable mapping logic and can be adjusted by subscribers or their MiSP directly in the iPaaS.com mapping editor. Others are produced by the integration itself or by Acumatica and are resolved by correcting data or configuration rather than by editing a mapping. Each entry notes which kind it is.
Supported flows
Stock Item To iPaaS
Customer To and From iPaaS
Sales Order From iPaaS
Authentication and Connection
Transaction Tracking Number To and From iPaaS
Stock Item To iPaaS
A polling run could not be completed
An error occurred while polling Acumatica products, and the run could not be completed.
Cause: The integration encountered an unexpected condition while retrieving stock items from Acumatica, typically a connection problem, an authentication problem, or invalid data returned by Acumatica.
Resolution: Confirm that the Acumatica instance is reachable and that the subscription credentials are still valid, then allow the next scheduled poll to run or trigger a Manual Sync. If the condition persists, review the Error Logs for the underlying Acumatica response and validate that the affected stock items are complete in Acumatica. This message is produced by the integration and is not subscriber-editable.
Acumatica returned no data for a stock item request
API RESPONSE IS NULL
Cause: A request for stock item data completed without returning the expected record, which can happen when the item no longer exists, when the request is throttled, or when the Acumatica session has expired. The integration records this as
API RESPONSE IS NULLin the Error Logs.Resolution: Re-authenticate the subscription if the session has expired, confirm the item still exists in Acumatica, and allow the transfer to retry. This message is produced by the integration and is not subscriber-editable.
Customer To and From iPaaS
A polling run could not be completed
An error occurred while polling Acumatica customers, and the run could not be completed.
Cause: The integration encountered an unexpected condition while retrieving customers from Acumatica, typically a connection problem, an authentication problem, or invalid data returned by Acumatica.
Resolution: Confirm the Acumatica instance is reachable and the subscription credentials are valid, then allow the next scheduled poll to run or trigger a Manual Sync. Review the Error Logs for the underlying Acumatica response if the condition persists. This message is produced by the integration and is not subscriber-editable.
Acumatica returned no data for a customer request
API RESPONSE IS NULL
Cause: A request for customer data completed without returning the expected record, which can happen when the customer no longer exists, when the request is throttled, or when the Acumatica session has expired. The integration records this as
API RESPONSE IS NULLin the Error Logs.Resolution: Re-authenticate the subscription if the session has expired, confirm the customer still exists in Acumatica, and allow the transfer to retry. This message is produced by the integration and is not subscriber-editable.
Sales Order From iPaaS
The order has no line items
The order could not be created or updated in Acumatica because it has no line items.
Cause: A sales order was sent to Acumatica without any line items. Acumatica requires at least one line item to create or update an order, so the transfer is stopped.
Resolution: Confirm the source order contains at least one valid line item before the transfer runs. Verify that line items are present and correctly mapped in the source system, then reprocess the order. This message is produced by the integration and is not subscriber-editable.
The order could not be created or updated
The order could not be created or updated in Acumatica.
Cause: Acumatica rejected the order because one or more required values were missing or invalid, such as the customer, line item details, amounts, or other mandatory fields.
Resolution: Confirm that all required order values are populated and valid, including at least one line item, before the transfer runs. Review the Error Logs for the specific values Acumatica rejected, correct the source data or mapping, and reprocess. This message is produced by the integration and is not subscriber-editable.
Acumatica rejected the order with a validation error
Acumatica rejected the order. The Error Logs contain the validation detail returned by Acumatica.
Cause: Acumatica returned a validation error while saving the order. The detail is captured from Acumatica's response and recorded in the Error Logs.
Resolution: Open the matching entry in the Error Logs and read the validation detail Acumatica returned, then correct the corresponding source data, mapping, or Acumatica configuration and reprocess the order. This message is produced by the integration and is not subscriber-editable.
The order's credit terms use multiple installments
No applications can be created for documents with multiple installment credit terms specified.
Cause: The credit terms code applied to the order, supplied through the FinancialTerms mapping, is defined in Acumatica with multiple installments. Acumatica does not allow a payment to be applied to an order that uses a multiple-installment term, so it rejects the payment.
Resolution: Map FinancialTerms to a credit terms code that is defined in Acumatica with a single installment type. This message is returned by Acumatica. The FinancialTerms mapping that supplies the value is subscriber-editable in the iPaaS.com mapping editor.
The access token is no longer valid
The access token is invalid. Please generate a new one and retry after a few moments.
Cause: Acumatica accepted the request but returned no content, which indicates the access token in use is no longer valid.
Resolution: Re-authenticate the subscription to generate a new access token, then allow the transfer to retry after a few moments. This message is produced by the integration and is not subscriber-editable.
Authentication and Connection
These messages can surface during any flow when the integration establishes or refreshes its connection to Acumatica.
A required OAuth setting is missing from the subscription
The OAuth connection could not be completed because a required connection setting is missing from the subscription.
Cause: One of the required OAuth values — Client Id, Client Secret, Scopes, Redirect Url, or Grant Type — is not set in the subscription preset, so the integration cannot complete the OAuth handshake. The Error Logs entry names the specific setting that is missing.
Resolution: Open the Acumatica subscription settings and confirm that Client Id, Client Secret, Scopes, Redirect Url, and Grant Type are all populated, then re-authenticate. This message is produced by the integration and is not subscriber-editable.
The grant type is not valid for the connection
The OAuth connection could not be started because the configured Grant Type is not valid.
Cause: The Grant Type set in the subscription preset is not one the integration can use to exchange the temporary authorization code for a permanent token.
Resolution: Set Grant Type in the subscription settings to a value supported by your Acumatica OAuth configuration, then re-authenticate. This message is produced by the integration and is not subscriber-editable.
The token could not be obtained or refreshed
The access token could not be obtained or refreshed. The refresh token may have expired. Please re-authenticate using the authenticator button.
Cause: The integration could not obtain a new access token from Acumatica, or the stored refresh token has expired and can no longer be used to obtain one.
Resolution: Re-authenticate the subscription using the authenticator button to obtain a fresh token, then allow the transfer to retry. This message is produced by the integration and is not subscriber-editable.
Transaction Tracking Number To and From iPaaS
The tracking number is not linked to a transaction
Transaction Tracking Number is not linked to any Transaction.
Cause: The tracking record references a transaction that the integration cannot find in iPaaS.com. The parent transaction must already exist and be linked before its tracking number can be processed.
Resolution: Confirm the related transaction has transferred and is linked in iPaaS.com before the tracking record is processed. This message comes from the editable collection filter on the Transaction Tracking Number To iPaaS collections and is subscriber-editable in the iPaaS.com mapping editor.
The shipping method does not exist in iPaaS.com
Shipping Method (X) needs to be created manually in iPaaS first. (X is the shipping method name from the record.)
Cause: The shipping method named on the record does not yet exist in iPaaS.com. The integration does not create shipping methods automatically, so processing stops until the method exists.
Resolution: Create the named shipping method in iPaaS.com, then reprocess the record. This message comes from the editable collection filter on the Transaction Tracking Number To iPaaS collections and is subscriber-editable in the iPaaS.com mapping editor.
BoxId is required
Required: BoxId.
Cause: The BoxId custom field is empty. A box identifier is required before a shipment package can be created in Acumatica.
Resolution: Populate the BoxId custom field with a value that exists in your Acumatica installation before the record is processed. This message comes from the editable collection filter on the Transaction Tracking Number From iPaaS collections and is subscriber-editable in the iPaaS.com mapping editor.
WarehouseId is required
Required: WarehouseId.
Cause: The WarehouseId custom field is empty. A warehouse identifier is required before a shipment can be created in Acumatica.
Resolution: Populate the WarehouseId custom field with a value that exists in your Acumatica installation before the record is processed. This message comes from the editable collection filter on the Transaction Tracking Number From iPaaS collections and is subscriber-editable in the iPaaS.com mapping editor.
An order number is required
Required: OrderNbr
Cause: The shipment has no associated order number. Acumatica needs the order number to link the shipment to its sales order.
Resolution: Confirm the OrderNbr mapping resolves to a valid, active order number in Acumatica before the shipment is created or updated. This message is produced by the integration and is not subscriber-editable.
A tracking number is required
Required: Tracking #
Cause: The tracking number is missing. The tracking number is required to build the record's external identifier, so processing cannot continue without it.
Resolution: Confirm the tracking number field is populated with a valid value before the shipment is created or updated. This message is produced by the integration and is not subscriber-editable.
The shipment status is missing
Status is null/empty from mappings
Cause: The shipment status is missing from the mapping — the status value resolved to empty. A status is required so that the shipment can be created and tracked with the intended state in Acumatica. The integration records this as
Status is null/empty from mappingsin the Error Logs.Resolution: Confirm the status mapping resolves to a valid value before the shipment is processed. This message is produced by the integration and is not subscriber-editable.
The order already has a shipment with a conflicting status
A shipment was attempted with status X, but the order already has a shipment with a different status that is not supported. The shipment may already be completed in Acumatica. (X is the status that was attempted.)
Cause: A shipment was attempted for an order that already has an existing shipment in a different, conflicting status — for example, the existing shipment is already completed. Acumatica does not allow a new shipment in this situation.
Resolution: Review the existing shipment in Acumatica before attempting another. Only attempt shipments for orders in an eligible status, and avoid creating duplicate shipments for orders that are already completed or finalized. This message is produced by the integration and is not subscriber-editable.
The line link identifier has the wrong format
The line link identifier on the tracking record is not in the expected format. It must be supplied as TransactionId followed by TransactionLineId, separated by a vertical bar.
Cause: The iPaaS_LineItemId value on the tracking record is not in the expected
TransactionId|TransactionLineIdformat, so the integration cannot locate the matching transaction line.Resolution: Confirm the iPaaS_LineItemId custom field is populated on the tracking record in the
TransactionId|TransactionLineIdformat so the line can be matched. This message is produced by the integration and is not subscriber-editable.
The transaction line could not be found
The transaction line could not be found. Make sure the line link identifier is populated on the tracking record.
Cause: The integration could not find a transaction line for the identifier on the tracking record, usually because iPaaS_LineItemId is missing, incorrect, or not linked to the tracking record.
Resolution: Confirm iPaaS_LineItemId is correctly populated on the tracking record and corresponds to a valid transaction line before reprocessing. This message is produced by the integration and is not subscriber-editable.
The shipment could not be found
The shipment could not be located in Acumatica. Make sure the shipment exists and includes lines from the related sales order.
Cause: Acumatica returned no shipment for the supplied shipment number, usually because the shipment was never created, the shipment number is incorrect, or the related sales order has no lines assigned for shipment.
Resolution: Confirm the shipment exists in Acumatica and that the related sales order includes shipment lines before reprocessing. This message is produced by the integration and is not subscriber-editable.
A tracking record could not be processed
The tracking record could not be processed. Review the Error Logs for the related shipment and order to identify the missing information.
Cause: The integration could not complete the tracking record because required shipment or line information could not be resolved.
Resolution: Open the matching entry in the Error Logs, confirm the related shipment, order number, and line link information are present and correct, then reprocess the record. This message is produced by the integration and is not subscriber-editable.
Related engineering note
A small number of the messages above are reproduced here in cleaned-up wording. The integration's raw text for several of them currently exposes internal detail (for example, all-capitals or single-word messages, or Acumatica diagnostic output). Those wording issues are tracked separately for engineering and do not change the cause or resolution described above.