Error/Issue | Explanation | Resolution |
Accounting Connection is not valid: Please review the error and make adjustments in your accounting software if necessary. | There is likely an issue with your credentials or connection settings. | Reconnect the integration using a valid username and credentials. |
Accounting period closed: Rho is unable to sync a transaction to a closed period. Please skip syncing this transaction and manually record the transaction in your GL software. | No more transactions can be synced because the accounting period is closed. This is a manual setting in your accounting software. | Manually reconcile the transaction in your accounting software, as syncing a transaction to a closed period is not possible. |
Attachment size too large: please upload a smaller attachment or compress the file and try again. | The attachment added to a transaction is too large and was rejected by the accounting software. | Compress the attachment and re-upload it. Replace it with a smaller file. Retry syncing after making the changes. |
This Bill has been deleted. Please skip the transaction from syncing or unarchive the Bill associated with this transaction. | An attempt was made to sync an archived or deleted bill which is not allowed. | Unarchive or restore the bill in your accounting software. Retry syncing the transaction. Alternatively, skip the transaction during syncing if it should remain deleted. |
This Bill is not yet ready to sync. You can sync this bill after it has settled or skip syncing this transaction. | The bill is not yet processed and cannot be synced when in a draft state. | Click on Send to Payments to process the bill. Once the bill is in the Processed state, retry syncing. |
Accounting attribute is invalid, missing, or cannot be applied to this transaction. Please check your GL software and sync again. | A value selected in Rho such as, an accounting attribute) doesn't exist, is inactive in the accounting software, or isn't applicable to the transaction type. | Change the value of the attribute to a valid one (either active or appropriate for the transaction type) Or skip the transaction and enter manually into your accounting software. |
Invalid accounting attribute reference: Please change the highlighted attribute and try again or review the available accounting attributes in your GL software. | The selected attribute isn't valid for the transaction (e.g., wrong account type for the bill). | Adjust the field specified in the error message to a valid attribute, then retry syncing the transaction. |
This Bill is not yet ready to sync. You can sync this bill when it moves to Processed state. Please process the bill or skip syncing this transaction. | The bill is not ready for syncing yet, you can only sync bills when they are ready for payment. | Ensure the bill is processed by clicking Send to Payments. Once processed, retry syncing the transaction. Alternatively, skip the transaction if syncing is not required. |
Journal does not exist, please create it in your ERP before re-attempting sync. | The specified journal does not exist in your Business Central account. | Create the appropriate journal in your Business Central account, then retry syncing the transaction. |
We need to know the default ledgers you want to use for all transactions. Please go here and select a default ledger. | The account's mapping rules aren’t set up properly or need to be added. | Navigate to Accounting tab > Mapping Rules > Ledgers. Map the appropriate Rho accounts to your accounting software's Chart of Accounts. |
We need you to fill in the missing field before we can sync this transaction. | A necessary field (e.g., Invoice Number, Invoice Date, Due Date, Vendor) is missing. | Fill in the missing field as indicated, then retry syncing the transaction. |
You’ve selected to skip this transaction when syncing, to change the status remove the skip selection here and sync the transaction again. | The transaction was marked to be skipped during syncing and so cannot be synced. | Uncheck the Skip Sync option for the transaction. Retry syncing. |
This transaction was already synced from Rho but has since been deleted in your accounting software. Please Skip syncing this transaction and record the transaction manually in your accounting software. | The transaction was previously synced but then deleted in your accounting software. | To record the transaction you will need to manually enter the transaction in your accounting software. |
Selected value does not exist in ERP: Please review the attributes you are trying to assign are active in your GL software. | A selected attribute in Rho is invalid, inactive, or incompatible with your accounting software. | Update the attribute in Rho to a valid, active value appropriate for the transaction type, then retry syncing. Otherwise recreate the attribute in your ERP. |
Sorry, we're experiencing an issue on our end. Please wait and try again later. If this issue persists please contact the Client Service team using the Help & Support button. | An internal system error has occurred. | Contact the Client Service team via the Help & Support button for assistance. |
Split transactions do not add up to total transaction amount. please adjust one or more of the amounts for transactions you are splitting. | The sum of the split amounts does not equal the total transaction amount. | Adjust the split amounts so that they sum up correctly to the total amount, then retry syncing. |
This feature is not included in your subscription plan for accounting software. Please visit your accounting software to ensure you have the right subscription for your current needs. | Your current subscription plan with your ERP does not include the attempted feature. | Review your subscription plan for your ERP and consider upgrading to access additional features if necessary. |
This transactions has been locked in your accounting software and thus can not be edited via Rho. Please skip sync this transaction and make any manual adjustments directly in your accounting software | The transaction is locked in your accounting software and cannot be modified via syncing. | Any changes must be made manually within your accounting software. |
This transaction has already been recorded in your accounting software. If you need to make changes, please do so directly in your accounting software. | The transaction has been paid and is no longer editable. | Any edits need to be done manually directly in your accounting software. |
This transaction was already synced from Rho but has since been deleted in your accounting software. Please skip sync this transaction and record this transaction manually in your accounting software if needed. | The transaction has been voided in your accounting software. | Skip syncing the transaction and record any adjustments you need directly in your accounting software. |
Transaction has no amount. Skip the transaction during syncing using the Skip button. | The transaction amount field is empty. | Enter the transaction amount. If the amount is not available, skip the transaction during syncing. |
Transaction has not settled. Please wait and try syncing again once transaction has settled or skip syncing this transaction. | The transaction is pending and not yet settled. | Wait for the transaction to settle. Once settled, retry syncing. Alternatively, skip the transaction during syncing. |
Transaction line count does not equal to ERP. Review lines before retrying or skip transactions during syncing using the Skip button. | The number of splits in Rho does not match the number in Business Central. | Adjust the number of splits in Rho or Business Central to match. Ensure each split corresponds correctly. Retry syncing the transaction. |
Reimbursements must have a single vendor for all transactions. Please adjust your vendor selections and re-sync | All associated transactions must have the same vendor for reimbursements. | Ensure all related reimbursements have the same vendor. Update the vendor information as necessary. Retry syncing. |
Unable to push transaction, no Account found for the transaction. | No account is set on the transaction. | Add the appropriate Account to the transaction, then retry syncing. |
Unable to push transaction, no Location found for the transaction. | No location is set on the transaction. | Add the appropriate Location to the transaction, then retry syncing. |
Unable to push transaction, no Vendor found for the transaction. | No vendor is set on the transaction. | Add the appropriate Vendor to the transaction, then retry syncing. |
Business Validation Error: You can’t use an Accounts Payable account on the detail portion of a Bill.(QuickBooks Online) | QuickBooks Online does not allow using an Accounts Payable (AP) account in a bill's line items because bills are meant to increase liabilities (AP), not directly expense them. | Ensure the account selected for the bill's line item is not an Accounts Payable account. Adjust the account selection within QuickBooks Online, then retry syncing. |
Associated bill must be pushed before payment record. Please sync associated bill and then resync the payment. | The associated bill needs to be synced before the payment can be synced. | Sync the associated bill first. Then sync the payment transaction. |
You must enter at least one line item for this transaction. | No line items have been added to the transaction. | Add at least one line item with details like description and amount. Retry syncing. |
Associated reimbursement must be pushed before the payment record. Please sync the associated reimbursement and then resync the payment. | The associated reimbursement needs to be synced before the payment can be synced. | Ensure that the payment has settled. Sync the reimbursement first. Then sync the disbursement. |
Missing mapping rule for Node _0000. Please go to Mapping Rules in the Accounting tab and create a rule. | A primary Cash (Checking) account does not have a mapping rule. | Navigate to Accounting tab > Mapping Rules > Ledgers. Set up the desired Chart of Accounts (CoA) mapping. Retry syncing. |
Troubleshooting Tips
If you're experiencing problems with values from your accounting software not appearing in Rho, or if bills are not being pulled into Rho as expected, please follow the troubleshooting steps below to resolve the issue.
Values from the Accounting Software Are Not Being Pulled into Rho
To refresh and sync attributes from your accounting software:
Navigate to the Accounting tab and select Dashboard.
Click on the three dots menu () and select Refresh attributes.
Note: It's important to refresh attributes whenever changes are made in your mapping rules or accounting software.
Bills from the Accounting Software Are Not Appearing in Rho
If you've enabled the option to pull bills from your accounting software, but they are not showing up in Rho, try the following steps:
Check the Bill Amount
Ensure that the bill amount is not $0, as bills with a zero amount will not be pulled into Rho.
Verify the Bill Creation Date
Bills older than 30 days may not be pulled unless you set a different initial pull date during configuration.
Enable Bill Pulling
Go to Bill Pay and select Settings.
Ensure that Use Accounts Payable from [Accounting Software] is set to On.
Click Save.
Confirm Vendor Setup
Verify that the vendor exists and is active in Rho.
Ensure there is a mapping rule set up for the vendor or that a default vendor is configured.
Check the Bill Status
Draft bills will appear under Bills.
Payments will appear under Payments.
Remove Any Filters
Check if any filters are applied that might prevent bills from displaying. Remove or adjust these filters as necessary.
Perform a Manual Sync
Bills are synced at specific times each day. To sync immediately:
Navigate to Bill Pay and select Bills/Payments.
Click on Sync bill from [Accounting Software].
Click Refresh within the same tab.