Fixing wrongly selected accounts for items in QuickBooks Online
It sometimes happens that, when you are entering an item in ERPAG (in most cases during the initial setup or data import), you mistakenly select the wrong account. Usually, such oversight is noticed much later, so it may seem that the correction will be complicated. The best way to explain this is through an example.
2. Correction in QuickBooks Online The foundation of QuickBooks Online is a relational database, which means that by changing some of the data, the change also affects most of the account entries connected to that data. In our example, we had a Purchase Order in ERPAG, as it is shown in the screenshot below.
And we synced that PO with QuickBooks Online:
We got the Bill with its transactions:
We subsequently noticed that the account was incorrect. It was supposed to be ‘’Inventory Final Products’’. In order to resolve the problem in the QuickBooks Online item setup, we changed the account to the appropriate one.
After the change, the results in QuickBooks Online are appropriate.
This way, we’ve solved the problem, but this solution is not very practical if we have a lot of similar issues that should be resolved – changing the accounts one by one changing would take forever.
Since our primary goal is practical implementation, the best solution is to make changes through ERPAG.
3. Correction through ERPAG
There are two ways to make adjustments to an item in ERPAG.
Individually, in the item setup:
Through the bulk action, for multiple items at once:
After setting up the account in product and services, all you need to do is to activate “Accounts (Update)” in the sync section.
And that’s it!
ERPAG will check all items in QuickBooks (that have SKUs identical to the ones in ERPAG), and set up their accounts in QuickBooks Online according to the ones that were chosen in ERPAG.
JSON/XML Designer in ERPAG is a visual tool that will allow users to transform data from the ERPAG database into JSON or XML format. This can be further used for future integration with API services. This tool provides a user-friendly interface where users can define...
The biggest change we developed is Automatization and Customization. This change is a huge milestone for us, and we will publish individual instructions for using the new features in the upcoming period. This module is divided into individual wholes: JSON Designer -...
ERPAG has the ability to use Blockly Script to send or receive data via the HTTP protocol. Integration of two systems via API (Application Programming Interface) is always a complex process, especially for someone with little experience. In this blog we will explain a...
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.