When working with the Sage Intacct integration, you may encounter error messages that prevent invoices, payments, or data from syncing successfully. These errors usually point to a configuration issue in OfficeRnD or Sage Intacct.
This article explains the most common errors, why they happen, and how to fix them quickly.
Before you start
Make sure that:
Your Sage Intacct integration is connected and active.
All required entities (customers, items, accounts) exist in Sage Intacct.
You have the necessary permissions in both OfficeRnD and Sage Intacct.
Item and product errors
Item ID:5903db74c76102af73f50d07 is not found
What it means: The item is not mapped in the Inventory tab and cannot be synced.
How to fix: Map the item in the Inventory tab of the integration configuration page.
Inventory-57bc0b4bf7ef27f00caeb401 is not mapped
What it means: The system expected a mapping for this inventory item, but no mapping exists.
How to fix: Map the item in the Inventory tab of the integration configuration page.
API data read error. Item with Id (Stripe)"Not Found"
What it means: The item with this ID does not exist.
How to fix: Verify that the item ID is correct and that the item exists.
Customer and contact errors
Field Contact name: 'John Doe(C2287)' cannot contain more than one continuous space. Remove multiple spaces before you save.
What it means: The contact name contains two consecutive spaces.
How to fix: Delete the extra space in the name.
The Customer 664a6f423ebfbac6077ee51a is not valid.
What it means: The customer ID does not exist in the system. The customer might have been deleted, inactive, or not yet created.
How to fix: Verify the customer ID in OfficeRnD.
Invoice and document errors
Your Sales invoice transaction definition is configured to affect AR. Define the posting account for this transaction.
What it means: The link between the transaction type and the GL account (for example, "1200 – Accounts Receivable") hasn't been set up.
How to fix: Please select the correct account.
A transaction with the number 'INV-61182' already exists.
What it means: Invoice numbers must be unique — you cannot reuse an existing number.
How to fix: Check if the transaction already exists or use a different unique number.
Failed to add a charge: Invalid payment - invoice INV674 has already been paid in full.
What it means: The invoice is already fully paid.
How to fix: Verify the payment status.
Document ID 'Sales Invoice-INV14' does not exist.Unable to process record
What it means: The document might have been deleted, not yet created, or the ID is incorrect.
How to fix: Verify the document ID in Sage.
Document number 'INV803' is already used. Error preparing values Could not create a Document record.
What it means: The document number is already in use.
How to fix: Verify existing records and use a new, unique document number.
Account and GL coding errors
Base currency has to be the same as the location's base currency.
What it means: The transaction currency does not match the location's base currency.
How to fix: Check the location's base or transaction currency in Sage.
The amount received is greater than the amount to apply. Reduce the amount received, reduce the credit amount to apply, or add an overpayment. Then try again.
What it means: The payment amount entered is greater than the invoice balance.
How to fix: Reduce the payment amount or credit amount applied.
A valid payment account type has not been specified
What it means: The payment record is missing the account type or has an incorrect account type.
How to fix: Select a valid payment account type.
Invalid transaction key 259, No line items found.
What it means: The transaction is invalid because it contains no line items.
How to fix: Ensure the transaction includes at least one valid line item.
Select another GL account. Currently, we cannot create the transaction '68927edaac7f8422d527f378'
What it means: The selected GL account is restricted or inactive.
How to fix: Choose a valid active GL account.
Connectivity and API errors
ThrottlerException: Too Many Requests
What it means: The API received too many requests in a short period.
How to fix: Check API rate limits or implement retry logic with delays.
Failed to establish a new connection:
What it means: Connectivity issue between systems.
How to fix: Check the connection from Sage and OfficeRnD.
The Service is Temporarily Off-line.
What it means: The service is unavailable or under maintenance.
How to fix: Retry later or check the service status page.
Timeout Error in calling API
What it means: The API request to Sage/OfficeRnD timed out.
How to fix: Check the connection between Sage and OfficeRnD.
Reading data through API from Read Payments Sage - {{INTEGRATION_ID}}', 'Sage Auth: SAGE API Error occurred. Error -Invalid URL '{{SAGE_ENDPOINT}}': No schema supplied. Perhaps you meant http://{{SAGE_ENDPOINT}}?
What it means: Connectivity issue due to an invalid or missing schema in the URL.
How to fix: Check the connection settings and correct the Sage endpoint.
Other validation errors
Another record with the value '2537' already exists.
What it means: A record with this value already exists.
How to fix: Verify the existing record in Sage.
Your transaction date (07/31/2025) is within a period that's been closed. You can add, modify, or delete a transaction only if the date of that transaction is within a period that's open. Enter a date that occurs on or after the date of the relevant entity, listed below. Note that different entities can have different dates
What it means: The transaction falls in a closed accounting period.
How to fix: Use a transaction date within an open period.
FAQs
Can I retry a failed sync?
Yes. Once you’ve fixed the cause of the error, you can retry the sync from OfficeRnD.
How do I know if an error is from OfficeRnD or Sage Intacct?
If the error mentions missing or invalid data (for example, “Customer not found”), it usually comes from Sage Intacct. If it’s about connection or mapping, check your OfficeRnD integration settings.
What if none of the fixes work?
Contact OfficeRnD support with the error message and context so we can help resolve it.