When pushing deposit transactions with NetSuite, you may encounter various errors that prevent successful processing. Below is a guide to common errors, their causes, and how to resolve them.
1. Duplicate Payout Push Errors
Example Errors:
"This payout has already been pushed to JE632."
Cause:
The user has attempted to push a deposit again before the previous one has finished processing.
Resolution:
Wait for the initial transaction to complete before attempting another push.
Verify in NetSuite whether the transaction is still in progress.
If an adjustment is required, allow the first push to process fully before reattempting.
2. Already Deposited Payment Errors
Example Errors:
"Failed: The payment CD76381 seems to have been already deposited."
Cause:
A Customer Deposit/Payment or Cash Sale has already been deposited, and the system is preventing it from being pushed again.
This is typically because a user is manually including a payment that has already been deposited before pushing or there is another process in NetSuite conflicting with Blue Onion's reconciliation
Resolution:
Ensure that the user is not manually selecting the payment before pushing transactions.
If necessary, undeposit the transaction in NetSuite to allow for reprocessing.
3. Invalid Account Reference Errors
Example Errors:
"Invalid account reference key 227 for subsidiary 1."
"Invalid account reference key 359 for subsidiary 1."
"Invalid account reference key 422 for subsidiary 1"
Cause:
The referenced account either does not exist in NetSuite, is inactive, or is not mapped correctly to the subsidiary.
Most often this is for negative values mapped to a revenue account either via your default mapping in the GL Account Mapping or from manually entered variances.
Resolution:
Update the GL Account Mapping to not map to a revenue account for the payment type in question. COGS and expense accounts are OK.
Check the chart of accounts in NetSuite to ensure the account exists.
Verify that the account is active and assigned to the correct subsidiary.
4. Missing Subsidiary Value
Example Errors:
"Please enter a value for subsidiary."
Cause:
A required subsidiary value is missing in the transaction push.
Resolution:
Assign the appropriate subsidiary in your software before pushing the transaction.
If the error persists, please reach out to us at Customer Success.
5. Transaction Mismatch Errors
Example Errors:
"A difference of 87.98999999999069 was found while summing payments from record 'Shop Pay - Shopify armrimmune Payout 11/29/2024 - USD 515063.37'."
Cause:
The total payments recorded in our deposit do not match the expected payout amount in NetSuite. This can only be resolved by us and we are notified when these occur.
Resolution:
Reach out to Customer Success if you need an update on status of your resolution
6. Transaction Push Dependency Errors
Example Errors:
"This push failed because of the transaction push 35441."
"This push failed because of the transaction push 35439."
Cause:
The transaction cannot be processed because a prerequisite transaction has failed.
This typically occurs when deposits need to be split into multiple deposits to fit under NetSuite file size limitations and a sibling deposit had an error.
Resolution:
Identify the referenced failed transaction.
Resolve the issue with the dependent transaction before retrying the push.
Once the prerequisite transaction is successfully processed, retry the push.
Conclusion
By understanding these common NetSuite integration errors, you can quickly diagnose and resolve issues to ensure smooth financial operations. If problems persist, consider reaching out to your NetSuite administrator or customer support for further assistance.