Skip to main content

Acumatica Error Messages

Reference for the error messages the Acumatica integration can report, the cause of each, and how subscribers can resolve them.

Overview

This article lists the error messages that the Acumatica integration can report, organized by the data flow that produces them. Each error carries a stable code you can search for on this page, followed by 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.

iPaaS.com categorizes errors by families. You can learn more about that categorization at Understanding iPaaS.com API Error Codes.

Some resolutions refer to your Managed Integration Service Provider (MiSP) — the partner who set up and manages your iPaaS.com integration. Some errors are produced by editable mapping logic and can be adjusted directly in the iPaaS.com mapping editor; others are produced by the integration or by Acumatica and are resolved by correcting data or configuration. Each entry notes which kind it is.

Supported Flows

  • Connection and Authentication

  • Stock Item To iPaaS

  • Customer To and From iPaaS

  • Sales Order From iPaaS

  • Transaction Tracking Number To and From iPaaS

Error Collection

Connection and Authentication

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

ACUM-AUTH-1001 - Unable to complete OAuth process in ProcessAuthorization. {setting} is not specified in the Preset of Subscription Settings

  • 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

ACUM-AUTH-1002 - Unable to start OAuth process in ProcessAuthorization as grant type: ({grantType}) specified in subscription preset is not correct for oauth to convert temporary code into a permanent token

  • 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 temporary code could not be exchanged for a token

ACUM-AUTH-1003 - Unable to complete OAuth process in ProcessAuthorization. Failed to convert temporary code into a permanent token

  • Cause: Acumatica did not return a permanent token when the integration exchanged the temporary authorization code, so the connection could not be completed.

  • Resolution: Re-authenticate the subscription using the authenticator button and complete the Acumatica sign-in. If it continues to fail, your MiSP can review the OAuth configuration. This message is produced by the integration and is not subscriber-editable.

The access token could not be generated from the subscription presets

ACUM-AUTH-1004 - Unable to generate Access Token by Presets provided in subscription using ROPC flow in CallWrapper while establishing connection. Failed to generate access token by presets provided

  • Cause: The integration could not obtain an access token using the credentials supplied in the subscription presets, so the connection could not be established.

  • Resolution: Confirm the credential presets on the subscription are correct and active in Acumatica, then re-authenticate. If it continues to fail, your MiSP can review the connection. This message is produced by the integration and is not subscriber-editable.

The token could not be obtained or refreshed

ACUM-AUTH-1005 - Unable to regenerate new Access Token by Refresh Token in CallWrapper while establishing connection. Failed to regenerate access token using the refresh token. 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.

The access token is no longer valid

ACUM-AUTH-1006 - 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.

Stock Item To iPaaS and Customer To and From iPaaS

Acumatica returned no data for a request

ACUM-NFND-1001 - API RESPONSE IS NULL

  • Cause: A request for stock item or customer data completed without returning the expected record, which can happen when the item or customer no longer exists, when the request is throttled, or when the Acumatica session has expired.

  • Resolution: Re-authenticate the subscription if the session has expired, confirm the record still exists in Acumatica, and allow the transfer to retry. This message is produced by the integration and is not subscriber-editable.

Acumatica rejected a customer request

ACUM-EXTN-1001 - Error Response is: {message returned by Acumatica}

  • Cause: The integration called Acumatica and Acumatica returned an error response. The specific detail from Acumatica is captured in the Error Logs. This single code covers Acumatica-rejected requests across flows; the most common customer-write conditions are listed below.

  • Common causes and resolutions:

    • 'Cash Discount Account' cannot be empty. — The Customer Class assigned through the CustomerClass mapping requires a Cash Discount Account in Acumatica, but none is set. Map CustomerClass to a 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). CustomerClass is subscriber-editable in the mapping editor.

    • Statement Cycle ID 'X' cannot be found in the system. — The StatementCycleID mapped to the customer names a Statement Cycle that does not exist in Acumatica. Map StatementCycleID to an existing Statement Cycle, or create the named cycle in Acumatica's Statement Cycles setup. StatementCycleID is subscriber-editable in the mapping editor.

  • Resolution: Open the matching entry in the Error Logs, read the detail Acumatica returned, and correct the source data, mapping, or Acumatica configuration accordingly, then reprocess. Where the value is supplied by a mapping (as in the common causes above), it is subscriber-editable in the iPaaS.com mapping editor.

Sales Order From iPaaS

The order has no line items

ACUM-VALD-1001 - Transaction can not be Created/Updated in Acumatica of Type {ActionType} because there is no LineItem/Detail found for SaleOrder!

  • 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. (A line whose product SKU does not exist in iPaaS.com is skipped by the mapping filter; if every line is skipped, the order arrives with no line items — see the Acumatica Known Limitations article.)

  • Resolution: Confirm the source order contains at least one valid line item, and that each line's product exists in iPaaS.com and Acumatica, before the transfer runs. This message is produced by the integration and is not subscriber-editable.

The order could not be created or updated

ACUM-EXTN-1003 - Transaction could not be Created/Updated in Acumatica of this Type: {ActionType}

  • 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

ACUM-EXTN-1002 - {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. The most common conditions are listed below.

  • Common causes and resolutions:

    • 'CustomerID' cannot be empty. — The order could not be resolved to an Acumatica customer (it matches by email). Confirm the order's customer exists in Acumatica with a matching email before the order transfers; if the customer was just created, allow a short interval for Acumatica to index it, then reprocess.

    • 'Payment Method' cannot be empty. (variant: 'Cash Account' cannot be empty.) — The payment did not resolve to a valid Acumatica Payment Method, or the method has no Cash Account. Map PaymentMethod to a Payment Method that exists in Acumatica and has a Cash Account configured (Payment Methods, screen CA2040PL). PaymentMethod is subscriber-editable in the mapping editor.

    • The financial period for [date] does not exist. (variants: 'Post Period cannot be empty.', '[period] is inactive.') — Payments post to the current business date, and the covering financial period is not generated or not active. In Acumatica, generate the Master Financial Calendar (screen GL201000) and activate the current period (Manage Financial Periods, screen GL503000, Open action), then reprocess.

    • No applications can be created for documents with multiple installment credit terms specified. — The credit terms code from the FinancialTerms mapping is defined in Acumatica with multiple installments. Map FinancialTerms to a single-installment credit terms code. FinancialTerms is subscriber-editable in the mapping editor.

  • Resolution: Open the matching entry in the Error Logs, read the validation detail Acumatica returned, correct the corresponding source data, mapping, or Acumatica configuration, and reprocess the order.

Transaction Tracking Number To and From iPaaS

The tracking number is not linked to a transaction

ACUM-NFND-1007 - 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

ACUM-NFND-1008 - Shipping Method ({Type}) needs to be created manually in iPaaS first

  • 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

ACUM-VALD-1006 - 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

ACUM-VALD-1007 - 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

ACUM-VALD-1002 - 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

ACUM-VALD-1003 - Required: Tracking #

  • Cause: The tracking number is missing. It 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

ACUM-VALD-1004 - Status is null/empty from mappings

  • Cause: The shipment status resolved to empty. A status is required so the shipment can be created and tracked with the intended state in Acumatica.

  • 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 external identifier has the wrong format

ACUM-VALD-1005 - Invalid ID format: expected shipmentNo|trackingNo

  • Cause: The external identifier for the shipment tracking record is not in the expected shipmentNo|trackingNo format, so the integration cannot parse it.

  • Resolution: Confirm the record's external identifier is in the shipmentNo|trackingNo format before reprocessing. This message is produced by the integration and is not subscriber-editable.

The transaction line could not be located by the line link identifier

ACUM-NFND-1002 - Unable to locate sequence_number on the transaction line by iPaaS_LineItemId. Please make sure that iPaaS_LineItemId is populated with a format TransactionId|TransactionLineId.

  • Cause: The iPaaS_LineItemId value on the tracking record is not in the expected TransactionId|TransactionLineId format, or does not match a transaction line, so the integration cannot locate the line.

  • Resolution: Confirm iPaaS_LineItemId 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.

The transaction lines could not be located

ACUM-NFND-1005 - Unable to locate TransactionLines by TransactionId [{TransactionId}]. Please make sure that iPaaS_LineItemId is populated on the Tracking record.

  • Cause: The integration could not find any transaction lines for the identifier on the tracking record, usually because iPaaS_LineItemId is missing or incorrect.

  • Resolution: Confirm iPaaS_LineItemId is correctly populated on the tracking record and corresponds to a valid transaction before reprocessing. This message is produced by the integration and is not subscriber-editable.

The shipment could not be located by shipment number

ACUM-NFND-1003 - Unable to locate Acumatica shipment details by ShipmentNbr {ShipmentNbr}. Please make sure that the Shipment has lines from the related SalesOrder {OrderNbr}.

  • Cause: Acumatica returned no shipment for the supplied shipment number, usually because the shipment was never created, the 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.

The shipment could not be located by order number

ACUM-NFND-1004 - We were not able to locate shipment by order number: {OrderNbr}. Please make sure that shipment for the order number exists in Acumatica before attempting to update it.

  • Cause: No shipment could be found in Acumatica for the order number on the record, so the update cannot proceed.

  • Resolution: Confirm a shipment for the order number exists in Acumatica before the record is updated, then reprocess. This message is produced by the integration and is not subscriber-editable.

The shipment could not be located when retrieving it

ACUM-NFND-1006 - We were not able to locate shipment by shipment number: {shipmentNo}. Please make sure that shipment exists in Acumatica before attempting to retrieve it.

  • Cause: No shipment could be found in Acumatica for the supplied shipment number when the integration attempted to retrieve it.

  • Resolution: Confirm the shipment exists in Acumatica before the record is retrieved, then reprocess. This message is produced by the integration and is not subscriber-editable.

The order already has a shipment with a conflicting status

ACUM-BIZL-1001 - A shipment was attempted with status {Status} but the order already has a shipment with another status which is not supported. The shipment may already be completed in Acumatica.

  • 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.

General

A batch operation could not be completed

ACUM-EXTN-1004 - Recieved an exception during batch run on of {Action}. {first exception message}

  • Cause: The integration runs several Acumatica calls together as a batch; one of the calls in the batch failed and the first underlying error is surfaced.

  • Resolution: Open the matching entry in the Error Logs and read the underlying error, then correct the corresponding source data, mapping, or Acumatica configuration and reprocess. This message is produced by the integration and is not subscriber-editable.

Related Documents

Related Articles
Did this answer your question?