Audience: Accounting Manager, Payment Authorizer, and ERP Admin
Summary: Reviews the most common sync errors for Intacct and MineralTree, how they occur, and how to resolve them.
Click on the error message you've received to learn how to resolve it:
- “Payment date cannot be before Bill creation date.”
- “The Check number 10001 entered against the bank BOA9187 already exists. Make desired changes and press Save to continue.”
- “Use of empty Location is invalid. A valid Multi‑Entity Location must be specified.”
- “Field 'XXXXXXXXX' is one of many fields that can't be changed in a partially editable transaction.”
“Payment date cannot be before Bill creation date.”
This error appears when an invoice in Intacct has a future invoice date, but the bill is paid early in MineralTree. MineralTree uses the current date as the payment date, which Intacct rejects because it falls before the bill creation date.
How to resolve
- In Intacct, navigate to: Accounts Payable > Setup > Configure Accounts Payable
- Locate the setting that prevents payments from being dated earlier than the bill date.
- Temporarily disable this setting.
- Re‑sync the payment from MineralTree.
“The Check number XXXX entered against the bank XXXX already exists. Make desired changes and press Save to continue.”
Intacct may have duplicate transaction number validation enabled. If another payment already exists with the same check number, either in the same entity or a related child entity, the sync will fail.
How to resolve
1. Check Intacct settings
This validation setting is located here:
2. Search for duplicate check numbers
- Search MineralTree for another payment using the same check number.
- If you using a multi‑entity structure, review all related entities for duplicates.
3. Validate check number ranges across entities
If the same bank account is used across multiple MineralTree companies (e.g., MTA, MTB, MTC), assign unique check number ranges to avoid conflicts:
- MTA → 10000
- MTB → 20000
- MTC → 30000
You can view or update check number sequences under: Company Profile > Manage Accounts
4. If a duplicate exists
You may resolve the conflict by:
- Voiding the payment and resubmitting it with a new check number
- Reconciling the duplicate payment directly with your vendor
NOTE: Before taking action, confirm whether another payment with the same check number exists in any related entity.
“Use of empty Location is invalid. A valid Multi‑Entity Location must be specified.”
Intacct requires a Location when syncing at the root or entity level. If the invoice does not include a location, the sync will fail.
How to resolve
- Edit the invoice in MineralTree.
- Select a Location at the line level.
- Re‑sync the invoice.
“Field 'XXXXXXXXX' is one of many fields that can't be changed in a partially editable transaction.”
This error occurs when an invoice has been modified in MineralTree, but the corresponding invoice in Intacct is in a non‑editable state (e.g., posted, partially paid, or locked).
How to resolve
- Review the invoice status in Intacct to determine whether it is editable.
- Decide whether the field listed in the error needs to sync.
- If Intacct does not allow editing the field in its current state, the API will also reject the update.
- To proceed, either:
- Update the data in MineralTree to match Intacct
- Move the invoice to an editable state in Intacct, then re‑sync
Customer Support
If the steps above do not resolve the issue, please contact MineralTree Customer Support:
Phone: 855‑672‑9669
Email: mtsupport@mineraltree.com
- Email: mtsupport@mineraltree.com