Connection and Authentication

Stock Item To iPaaS.com and Customer To and From iPaaS.com

Customer Company To iPaaS.com

Customer (Contact) To iPaaS.com

Sales Order From iPaaS.com

Sales Order To iPaaS.com

AR Invoice To iPaaS.com

Transaction Tracking Number To and From iPaaS.com

General

Description: 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.

Description: 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.

Description: 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 Authenticate icon on the subscription 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.

Description: 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.

Description: 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 Authenticate icon on the subscription to obtain a fresh token, then allow the transfer to retry. This message is produced by the integration and is not subscriber-editable.

Description: 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.

Description: The subscription uses the Authorization Code grant type and has no stored access token or session, either because it has never been authorized or because its stored session was cleared. Transfers cannot call Acumatica until it is authorized.

Resolution: Authorize the subscription using the Authenticate icon on the subscription, then allow the transfer to retry. This message is produced by the integration and is not subscriber-editable.

Description: Acumatica answered the request with its error page instead of data. This most often happens when the Acumatica user's or license's API session limit has been reached (other integrations or applications signed in as the same user, or under the same license, and did not sign out), or when the session behind the stored token was ended, for example by restarting the Acumatica application.

Resolution: Allow the transfer to retry; it connects with a new token. If it keeps failing, the most common cause is that the Acumatica user's or license's API sessions are full: wait about an hour for unused sessions to expire, or restart the Acumatica site from the Apply Updates form (screen SM203510) to release them all (this also signs out every Acumatica user), then retry. Using a dedicated Acumatica user for this integration avoids sharing the sign-in limit with other applications. This message is produced by the integration and is not subscriber-editable.

Description: Connection Validate on the subscription, or the connection the integration opens before a transfer, could not be confirmed with Acumatica. The text after the code gives the reason, for example that Acumatica rejected the credentials (with the HTTP status), that the API URL or version was not found, that no access token was available after authentication, that the subscription has not been authorized yet, or that Acumatica did not serve the API session.

Resolution: Act on the reason shown: verify the API Url and Version, the Username, Password, Client Id, Client Secret, Scopes and Grant Type in the subscription settings, re-authenticate with the Authenticate icon on the subscription, or, when Acumatica did not serve the API session, sign out older API sessions in Acumatica or wait for them to expire, then run Connection Validate again. If it keeps failing, your MiSP can review the connection. This message is produced by the integration and is not subscriber-editable.

Description: 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.

Description: An Acumatica customer that was not yet linked matched an existing, unlinked iPaaS.com Customer with the same email, but iPaaS.com did not confirm the link. The transfer stops instead of creating a second Customer with that email.

Resolution: Reprocess the customer from the Error Logs; the match is retried on the next transfer. If the error repeats, ask your MiSP to check the iPaaS.com Customer named in the message and its external IDs. This message is produced by the integration and is not subscriber-editable.

Description: The Add/Update Acumatica Customer FROM iPaaS.com collection received an iPaaS.com Customer that was created from an Acumatica contact. Contacts are only transferred into iPaaS.com, so nothing is written to Acumatica for it.

Resolution: No action is needed for the contact; the error is recorded whenever that Customer is sent to the collection. The Customer belongs to an Acumatica contact, which is maintained in Acumatica and transferred into iPaaS.com by Add/Update Acumatica Contact TO iPaaS.com. Make changes to the contact in Acumatica rather than to its iPaaS.com Customer. This message is produced by the integration and is not subscriber-editable.

Description: A company transfer, for example a Manual Sync of a Customer ID, asked Acumatica for a customer that it did not return. The Customer ID may be mistyped, or the customer may have been deleted.

Resolution: Check the Customer ID on the Acumatica Customers form (screen AR303000), then transfer the company again with the exact Customer ID. This message is produced by the integration and is not subscriber-editable.

Description: An Acumatica customer that was not yet linked matched an existing, unlinked iPaaS.com Company with the same name, but iPaaS.com did not confirm the link. The transfer stops instead of creating a duplicate Company.

Resolution: Reprocess the company from the Error Logs; the match is retried on the next transfer. If the error repeats, ask your MiSP to check the iPaaS.com Company named in the message and its external IDs. This message is produced by the integration and is not subscriber-editable.

Description: An address of the Acumatica customer matched an address already on the iPaaS.com Company, but iPaaS.com did not confirm the link. The transfer stops instead of adding the address a second time.

Resolution: Reprocess the company from the Error Logs. If the error repeats, ask your MiSP to check the iPaaS.com address named in the message. This message is produced by the integration and is not subscriber-editable.

Description: A contact transfer, for example a Manual Sync, asked Acumatica for a contact that it did not return. The Contact ID may be mistyped, or the contact may have been deleted.

Resolution: Check that the contact exists in Acumatica, then transfer it again with its Contact ID followed by the contact suffix (for example, 5|contact). This message is produced by the integration and is not subscriber-editable.

Description: The contact's business account is an Acumatica customer that is not yet in iPaaS.com, so the integration transferred it as a Company first, and that transfer failed. The reason the Company transfer failed follows the message when one is available. An account that the Add/Update Acumatica Company TO iPaaS.com filter skips does not cause this error; the contact is then transferred without a company relationship.

Resolution: Correct the cause of the Company failure (for example, a blank customer name in Acumatica, or a company name already used by another iPaaS.com Company), then transfer the contact again. This message is produced by the integration and is not subscriber-editable.

Description: An Acumatica contact that was not yet linked matched an existing, unlinked iPaaS.com Customer with the same email, but iPaaS.com did not confirm the link. The transfer stops instead of creating a second Customer with that email.

Resolution: Reprocess the contact from the Error Logs; the match is retried on the next transfer. If the error repeats, ask your MiSP to check the iPaaS.com Customer named in the message and its external IDs. This message is produced by the integration and is not subscriber-editable.

Description: The contact's address matched an address already on its iPaaS.com Customer, but iPaaS.com did not confirm the link. The transfer stops instead of adding the address a second time.

Resolution: Reprocess the contact from the Error Logs. If the error repeats, ask your MiSP to check the iPaaS.com address named in the message. This message is produced by the integration and is not subscriber-editable.

Description: The contact's relationship to its Company matched a relationship already on its iPaaS.com Customer, but iPaaS.com did not confirm the link. The transfer stops instead of adding the relationship a second time.

Resolution: Reprocess the contact from the Error Logs. If the error repeats, ask your MiSP to check the iPaaS.com relationship named in the message. This message is produced by the integration and is not subscriber-editable.

Description: 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.

Description: 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.

Description: 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:

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.

Description: The order was placed by an iPaaS.com Customer that came from an Acumatica contact, or its email belongs to an Acumatica contact, and that contact has no business account, or its business account is not a customer (for example a vendor). Acumatica places every sales order on a customer account and does not accept a contact on its own, so the order is stopped before anything is sent.

Resolution: In Acumatica, assign the contact to a customer account (Contacts, screen CR302000, Business Account field), or link the order in iPaaS.com to a Company that is linked to an Acumatica customer account, then reprocess the order.

Description: The order is linked to an iPaaS.com Company that has not been linked to an Acumatica account, it has no Customer or only a Customer that is not linked to Acumatica either, and its email matches no Acumatica account and no single Acumatica contact. No Acumatica customer is created for an order with a Company. The message names the Customer when there is one, and says why the email did not help: no email, no match, or an email shared by several contacts (none is picked, because picking one would be a guess).

Resolution: iPaaS.com Companies are not written to Acumatica; a Company is linked when its Acumatica account transfers TO iPaaS.com. In Acumatica, make sure a customer account with the Company's name exists in the customer class that the Add/Update Acumatica Company TO iPaaS.com filter selects (COMPANY in the shipped filter), and let it transfer, which links the Company. Alternatively, link the order to a Customer, or give it an email that belongs to one Acumatica account or contact. Then reprocess the order.

Description: The order's iPaaS.com Customer is not in Acumatica yet, so the integration transfers it first, and that transfer failed. The order is not written. The reason from the customer transfer follows the message.

Resolution: Resolve the customer error shown with the message (see Customer From iPaaS.com in this article for its code), then reprocess the order. This message is produced by the integration and is not subscriber-editable.

Description: With Sales Order Duplicate Checking set to true, the integration found an Acumatica order whose number equals the transaction number and tried to link the transaction to it, but iPaaS.com did not confirm the link. The transfer stops rather than create a duplicate order.

Resolution: Reprocess the order. If it fails again, your MiSP can check the transaction's external IDs for the Acumatica order named in the message. This message is produced by the integration and is not subscriber-editable.

Description: While linking a transaction to an existing Acumatica order (Sales Order Duplicate Checking), the integration matched a transaction line to an order line by SKU, but iPaaS.com did not confirm the link. The transfer stops rather than duplicate the line.

Resolution: Reprocess the order. If it fails again, your MiSP can check the line's external IDs. This message is produced by the integration and is not subscriber-editable.

Description: An order transfer, for example a Manual Sync, asked Acumatica for a sales order that it does not have. The order type or number may be mistyped, or the order may have been deleted. The same code is reported, with the message "{id}" is not a sales order id. Use the order type and number separated by "|", for example SO|000080., when the value entered is not an order type and number.

Resolution: Check the order on the Acumatica Sales Orders form (screen SO301000), then transfer it again with its order type and number separated by "|" (for example, SO|000080). This message is produced by the integration and is not subscriber-editable.

Description: The order's business account is not yet in iPaaS.com, so the integration transferred it first through Add/Update Acumatica Customer TO iPaaS.com or Add/Update Acumatica Company TO iPaaS.com, and that transfer failed. The reason it failed follows the message when one is available. {OrderId} is the Acumatica record id (a GUID) of the order, as shown in the Transaction's external IDs in iPaaS.com. An account that neither collection's filter captures does not cause this error; the order is then captured without a customer or Company, with its contact's email.

Resolution: Correct the cause of the account failure (shown in the message and with the account's own error in the Error Logs), then transfer the order again. This message is produced by the integration and is not subscriber-editable.

Description: An Acumatica order that was not linked yet matched exactly one existing, unlinked iPaaS.com Transaction of the same type with the same number, but iPaaS.com did not confirm the link. The transfer stops instead of creating a second Transaction. {OrderId} is the Acumatica record id (a GUID) of the order, as shown in the Transaction's external IDs in iPaaS.com.

Resolution: Reprocess the order from the Error Logs; the match is retried on the next transfer. If the error repeats, ask your MiSP to check the iPaaS.com Transaction named in the message and its external IDs. This message is produced by the integration and is not subscriber-editable.

Description: The order is being captured into an iPaaS.com Transaction that already exists, and one of its lines matched a line already on that Transaction, but iPaaS.com did not confirm the link. The transfer stops instead of adding the line a second time.

Resolution: Reprocess the order from the Error Logs; the match is retried on the next transfer. If the error repeats, ask your MiSP to check the iPaaS.com line named in the message and its external IDs. This message is produced by the integration and is not subscriber-editable.

Description: The order is being captured into an iPaaS.com Transaction that already exists, and one of its addresses matched an address already on that Transaction, but iPaaS.com did not confirm the link. The transfer stops instead of adding the address a second time.

Resolution: Reprocess the order from the Error Logs; the match is retried on the next transfer. If the error repeats, ask your MiSP to check the iPaaS.com address named in the message and its external IDs. This message is produced by the integration and is not subscriber-editable.

Description: The order is being captured into an iPaaS.com Transaction that already exists, and one of its taxes matched a tax already on that Transaction, but iPaaS.com did not confirm the link. The transfer stops instead of adding the tax a second time.

Resolution: Reprocess the order from the Error Logs; the match is retried on the next transfer. If the error repeats, ask your MiSP to check the iPaaS.com tax named in the message and its external IDs. This message is produced by the integration and is not subscriber-editable.

Description: The order is being captured into an iPaaS.com Transaction that already exists, and one of its payments matched a payment already on that Transaction, but iPaaS.com did not confirm the link. The transfer stops instead of adding the payment a second time.

Resolution: Reprocess the order from the Error Logs; the match is retried on the next transfer. If the error repeats, ask your MiSP to check the iPaaS.com payment named in the message and its external IDs. This message is produced by the integration and is not subscriber-editable.

Description: An AR invoice transfer, for example a Manual Sync, asked Acumatica for a document that it does not have. The document type or reference number may be mistyped, or the document may have been deleted. The same code is reported, with the message "{id}" is not an AR invoice id. Use the document type and reference number separated by "|", for example Invoice|000002., when the value entered is not a document type and reference number.

Resolution: Check the document on the Acumatica Invoices and Memos form (screen AR301000), then transfer it again with its document type and reference number separated by "|" (for example, Invoice|000002 or Credit Memo|000010). This message is produced by the integration and is not subscriber-editable.

Description: 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.

Description: 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.

Description: 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.

Description: 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.

Description: 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.

Description: 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.

Description: 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.

Description: 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.

Description: 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.

Description: 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.

Description: 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.

Description: 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.

Description: 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.

Description: 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.

Description: The tracking number belongs to an iPaaS.com transaction that is not in Acumatica yet, so the integration transfers the transaction first, and that transfer failed. The tracking number is not written. The reason from the transaction transfer follows the message.

Resolution: Resolve the order error shown with the message (see Sales Order From iPaaS.com in this article), then reprocess the tracking number. This message is produced by the integration and is not subscriber-editable.

Description: The integration could not build a shipment package for the tracking number, so nothing was written to Acumatica. The BoxId and WarehouseId custom field values on the tracking record decide the package and the shipment's warehouse.

Resolution: Check that the BoxId and WarehouseId custom fields on the iPaaS.com tracking record hold a valid Acumatica box and warehouse for the order, then reprocess. This message is produced by the integration and is not subscriber-editable.

Description: The integration found the existing Acumatica shipment package or iPaaS.com tracking record that matches the tracking number and tried to link them, but iPaaS.com did not confirm the link. The transfer stops rather than duplicate the tracking number.

Resolution: Reprocess the record. If it fails again, your MiSP can check the external IDs of the record named in the message. This message is produced by the integration and is not subscriber-editable.

Description: 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 requests Acumatica rejects in any flow; the most common conditions are listed below.

Common causes and resolutions:

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.

Description: 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.

iPaaS.com <> Acumatica: Background

Acumatica Installation Instructions

Acumatica Connections and Settings

Acumatica Mapping Functions

Acumatica API Endpoints

Acumatica Known Limitations