Stock Item To iPaaS

Customer To and From iPaaS

Sales Order From iPaaS

Authentication and Connection

Transaction Tracking Number To and From iPaaS

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.

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 NULL in 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.

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.

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 NULL in 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.

Cause: The Customer Class assigned to the customer — supplied through the CustomerClass mapping — is configured in Acumatica to require a Cash Discount Account, but no such account is set. Acumatica rejects the customer write until the class has a Cash Discount Account.

Resolution: Map CustomerClass to a Customer Class that does not require a Cash Discount Account (for example, LOCAL), or configure a Cash Discount Account on the Customer Class in Acumatica (Customer Classes, screen AR201000). This message is returned by Acumatica. The CustomerClass value is supplied by a mapping and is subscriber-editable in the iPaaS.com mapping editor.

Cause: The StatementCycleID mapped to the customer names a Statement Cycle that does not exist in the subscriber's Acumatica installation, so Acumatica cannot resolve it and rejects the customer write.

Resolution: Map StatementCycleID to a Statement Cycle that already exists in Acumatica, or create the named cycle in Acumatica's Statement Cycles setup before the transfer runs. This message is returned by Acumatica. The StatementCycleID value is supplied by a mapping and is subscriber-editable in the iPaaS.com mapping editor.

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.

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.

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.

Cause: The order could not be resolved to an Acumatica customer. The order references its customer by email address, and no Acumatica customer with a matching email was found — usually because the customer has not been transferred to Acumatica yet, or was created moments earlier and Acumatica has not finished indexing it for the email match.

Resolution: Confirm the order's customer exists in Acumatica before the order transfers, with an email address that matches the order. Transfer or create the customer first, then reprocess the order; if the customer was just created, allow a short interval for Acumatica to index it before retrying. This message is returned by Acumatica.

Cause: The shipping method named on the order does not exist in the subscription. The integration resolves the order's shipping method before writing the order and stops when it cannot find a match.

Resolution: Create the named shipping method in the subscription before the order transfers, then reprocess the order. This message is produced by the integration and is not subscriber-editable.

Cause: A line on the order references a SKU that does not exist as a product in the subscription, and correspondingly as a Stock Item in Acumatica. The integration cannot resolve the line to a product, so the order is stopped.

Resolution: Ensure the product exists in the subscription — synchronize Stock Items so the SKU is present — and that a matching Stock Item exists in Acumatica, then reprocess the order. This message is produced by the integration and is not subscriber-editable.

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.

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.

Cause: A payment on the order could not be posted because the payment method did not resolve to a valid Acumatica Payment Method, or the resolved method has no Cash Account configured. Acumatica requires both a Payment Method and a Cash Account to record a payment.

Resolution: Map PaymentMethod to a Payment Method that exists in Acumatica and has a Cash Account configured (Payment Methods, screen CA2040PL), then reprocess the order. This message is returned by Acumatica. The PaymentMethod value is supplied by a mapping and is subscriber-editable in the iPaaS.com mapping editor.

Cause: The order's payment posts to the current business date, and the Acumatica financial period covering that date is either not generated or not activated. A payment cannot post to a period that does not exist or is inactive.

Resolution: In Acumatica, generate the Master Financial Calendar (screen GL201000) so it covers the payment's posting date, then activate the corresponding periods for the company (Manage Financial Periods, screen GL503000, using the Open action). Because payments post to the current business date, the current period must exist and be active. Reprocess the order once the period is open. This message is returned by Acumatica.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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 mappings in 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.

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.

Cause: The iPaaS_LineItemId value on the tracking record is not in the expected TransactionId|TransactionLineId format, 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|TransactionLineId format so the line can be matched. This message is produced by the integration and is not subscriber-editable.

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.

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.

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.