When syncing data between Hike POS and QuickBooks Online (QBO), you may occasionally encounter errors that prevent products, sales, purchase orders, or register closures from syncing successfully.
This guide explains common QBO sync errors, their possible causes, and the steps you can follow to resolve them.
Before you begin: Identify the exact error message displayed in Hike POS and locate the corresponding error below. Follow the recommended troubleshooting steps and try syncing the affected record again.
If the error persists after following the suggested steps, please contact Hike POS Live Chat Support for further assistance.
Entity: Product
Possible cause: The Sales and Inventory Asset account codes assigned to the product in Hike POS may be invalid or may not exist in QBO.
How to resolve:
Open the affected product in Hike POS.
Review the Sales and Purchase account codes assigned to the product.
If the account codes are invalid, either remove them or replace them with valid account codes from QBO.
Save the product and try syncing it again.
Entity: Product
Possible cause: The product SKU is already being used by another product in QBO. This can happen when a SKU is changed in Hike POS to a value that already exists in QBO.
How to resolve:
Check the SKU of the affected product in Hike POS.
Search for the same SKU in QBO and identify whether another product is already using it.
Ensure that each product has the correct and unique SKU across Hike POS and QBO.
Update any duplicate SKUs as necessary.
Save the changes and try syncing the product again.
Entity: Product
Possible cause: Inventory tracking is enabled in Hike POS, but the Track quantity on hand setting is disabled in QBO.
How to resolve:
Log in to your QBO account.
Open the settings for products and services.
Enable the Track quantity on hand setting.
Save the changes.
Return to Hike POS and check whether the affected product syncs automatically.
Entity: Product
Possible cause: The Track quantity on hand setting in QBO may have been disabled after the product was initially synced.
How to resolve:
Open QBO and review the Track quantity on hand setting under the product and services settings.
Ensure that inventory tracking is enabled.
Save the changes and check whether the product syncs successfully.
If the error persists, contact Hike POS Live Chat Support for further assistance.
Entity: Product
Possible cause: This error may occur when the Track quantity on hand setting in QBO has been disabled after the product was synced.
How to resolve:
Log in to QBO and check whether Track quantity on hand is enabled.
If the setting is disabled, enable it and save the changes.
Return to Hike POS and check whether the product syncs successfully.
If the error continues, contact Hike POS Live Chat Support.
Entity: Product
Possible cause: The product name already exists in QBO, or another product synchronisation process may still be running in the background.
How to resolve:
Check the affected product in QBO and verify whether another product or service already uses the same name.
If the name is already in use by a different product, review the product names and make the necessary corrections to ensure the products can be identified correctly.
If other products are still syncing in the background, allow the process to complete and refresh the product sync status in Hike POS.
If the product continues to show a sync error, contact Hike POS Live Chat Support.
Entity: Sales
Possible cause: QBO may have returned an empty or unexpected response during the synchronisation process.
How to resolve:
Try syncing the affected sale again.
Check whether the sale has successfully synced to QBO.
If the error persists, contact Hike POS Live Chat Support and provide the sale details and the exact error message.
Entity: Sales
Possible cause: The sale may contain a product or product configuration that is not supported by the integration.
How to resolve:
Review the products included in the affected sale.
Check whether any product has an unusual configuration or is unavailable in the connected accounting system.
Try syncing the sale again.
If the error persists, contact Hike POS Live Chat Support for further investigation.
Entity: Sales
Possible cause: The customer associated with the sale may have been deleted from QBO, leaving an outdated customer mapping in Hike POS.
How to resolve:
Open QBO and check whether the customer associated with the sale still exists.
If the customer has been deleted, contact Hike POS Live Chat Support and provide the affected sale and customer details.
Our support team can review the customer mapping and assist with the required correction.
Entity: Sales
Possible cause: One or more line items associated with the sale may have a quantity of zero in QBO. A valid quantity is required for the sale to sync correctly.
How to resolve:
Open QBO and review the products associated with the affected sale.
Check whether any of the associated products have a quantity of zero.
Review the product quantities and stock information to identify the discrepancy.
If the error persists after checking the quantities, contact Hike POS Live Chat Support.
Entity: Sales
Possible cause: One or more line items associated with the sale may have a quantity of zero in QBO.
How to resolve:
Open QBO and review the products associated with the affected sale.
Check whether any of the associated products have a quantity of zero.
Review the product quantities and stock information to identify the discrepancy.
Try syncing the sale again after the issue has been addressed.
If the error continues, contact Hike POS Live Chat Support.
Entity: Sales
Possible cause: The sale transaction date is earlier than the inventory start date configured for an associated product in QBO.
How to resolve:
Open QBO and locate the product associated with the affected sale.
Check the product's inventory start date and compare it with the transaction date of the sale in Hike POS.
Review and correct the inventory start date in QBO, where appropriate, so that it is consistent with the transaction date.
Try syncing the sale from Hike POS to QBO again.
For more information, refer to the QuickBooks Online guidance on transaction dates and inventory start dates.
Entity: Sales
Possible cause: The invoice number assigned to the sale in Hike POS is already being used by another transaction in QBO.
How to resolve:
Log in to QBO and search for the invoice number mentioned in the error message.
Check whether another invoice already uses that number.
If the number is already assigned to a different transaction, review the invoice records and correct the duplicate invoice number in QBO, where appropriate.
Try syncing the sale again.
Important: Before changing an invoice number, ensure that you have identified the correct transaction and considered any accounting or record-keeping implications.
Entity: Sales
Possible cause: Two customers in Hike POS may have the same name, and neither customer has an email address. However, only one corresponding customer may exist in QBO, making it difficult to match the correct records.
How to resolve:
Review the customer records in Hike POS and identify whether multiple customers have the same name.
Check the corresponding customer records in QBO.
Add the correct email addresses to the relevant customer records in Hike POS and QBO to help distinguish and match the customers.
Try syncing the sale again.
If the customer mapping remains incorrect, contact Hike POS Live Chat Support.
Entity: Sales
Possible cause: The error may be related to an account that was deleted from QBO and is referenced by the transaction.
How to resolve:
Open QBO and check whether the account mentioned in the error still exists.
If the account has been deleted, avoid making changes to the transaction until you have confirmed the correct accounting treatment.
Contact Hike POS Live Chat Support and provide the affected sale and the complete error message.
Our support team can review the issue and advise on the next steps.
Entity: Sales
Possible cause: A product associated with the sale may have been deleted from Hike POS, preventing the sale from syncing correctly to QBO.
How to resolve:
Review the products included in the affected sale.
Check whether the product mentioned in the error still exists in Hike POS.
If the product has been deleted, contact Hike POS Live Chat Support for assistance with the affected sale.
Entity: Sales
Possible cause: A rounding discrepancy may be causing the transaction amount to differ from the calculated unit price multiplied by the quantity.
How to resolve:
Review the affected sale in Hike POS.
Check the unit price, quantity, and total amount of the affected line item.
Verify whether a rounding difference exists between the calculated amount and the transaction amount.
If the values appear correct but the error persists, contact Hike POS Live Chat Support for assistance.
Entity: Sales
Possible cause: The Cash rounding expense product in QBO may not have a valid income account assigned.
How to resolve:
Log in to QBO and open the product or service named Cash rounding expense product.
Review its income account configuration.
Select Sales as the income account, as appropriate for your accounting setup.
Save the changes.
Return to Hike POS and try syncing the sale again.
If the sale still does not sync, contact Hike POS Live Chat Support for assistance with further synchronisation.
Entity: Sales
Possible cause: The default Discount product has been added to the sale in QBO. Due to integration API limitations, Hike POS does not support syncing sales containing certain default products mapped on the integration page.
How to resolve:
Open the affected sale in QBO.
Check whether the default Discount product has been added to the transaction.
Review the transaction and its discount treatment before making any changes.
If the error persists, contact Hike POS Live Chat Support for guidance on how to proceed.
Entity: Purchase Order
Possible cause: The supplier associated with the purchase order may have been deleted from QBO, leaving an outdated supplier mapping in Hike POS.
How to resolve:
Open QBO and check whether the supplier associated with the purchase order still exists.
If the supplier has been deleted, contact Hike POS Live Chat Support and provide the affected purchase order details.
Our support team can review the outdated supplier mapping and assist with the required correction.
Entity: Purchase Order
Possible cause: The supplier associated with the purchase order has an incorrectly formatted website URL.
How to resolve:
Open the supplier profile associated with the affected purchase order in Hike POS.
Locate the website URL field.
Correct the URL so that it uses a valid format, such as https://www.example.com.
Save the supplier profile.
Try syncing the purchase order again.
Entity: Purchase Order
Possible cause: The Discount service item used for the purchase order discount may not have an expense account assigned in QBO.
How to resolve:
Log in to QBO and open the Discount product or service item used for the purchase order discount.
Review the item's expense account configuration.
Assign the appropriate purchase expense account.
Save the changes.
Return to Hike POS and try syncing the purchase order again.
If the error persists, contact Hike POS Live Chat Support.
Entity: Purchase Order Bill
Possible cause: A product associated with the purchase order or its bill may have a negative quantity, causing a mismatch between the transaction line details.
How to resolve:
Review the affected purchase order and its associated bill.
Check the product quantities and identify whether any product has a negative quantity.
Review the affected line items and correct any quantity discrepancies where appropriate.
Try syncing the purchase order or bill again.
If the error continues, contact Hike POS Live Chat Support.
Entity: Purchase Order
Possible cause: The purchase order includes a discount, but the Discount service item used for the discount does not have the required expense account details in QBO.
How to resolve:
Log in to QBO and locate the Discount product or service item used for the purchase order.
Review the item's purchase expense account configuration.
Assign the appropriate purchase expense account.
Save the changes.
Return to Hike POS and try syncing the purchase order again.
Entity: Register Closure
Possible cause: The register closure may not have been updated correctly earlier, resulting in a value outside the range supported by QBO.
How to resolve:
Review the affected register closure in Hike POS.
Check whether any amounts appear incorrect or fall outside the supported range.
If the values appear correct but the error persists, contact Hike POS Live Chat Support and provide the register closure details.
Our support team can review the closure and assist with the next steps.
If you have followed the troubleshooting steps above and the error still occurs, please contact the Hike POS Live Chat Support team.
To help us investigate the issue efficiently, please provide:
The exact error message displayed in Hike POS.
The affected entity, such as Product, Sales, Purchase Order, Purchase Order Bill, or Register Closure.
The relevant product SKU, sale number, purchase order number, or register closure details, as applicable.
A screenshot of the error message, if available.
Any troubleshooting steps you have already completed.
Our support team will review the details and assist you with the next steps.
Note: Some synchronisation errors require technical intervention and cannot be resolved through customer-side changes alone. In such cases, our team will investigate and provide further guidance.