Sync adjustments to QuickBooks Online
Overview
Find out how to synchronize adjustments with QuickBooks Online.
Adjustments increase or decrease your level of stock and in turn the value of your inventory.
For example, if you create a positive adjustment because you find unrecorded stock, your inventory’s value goes up. And if you create a negative adjustment because your stock has been stolen or damaged, your inventory’s value goes down.
So it’s essential to sync your adjustments to QuickBooks Online. When you sync a positive adjustment, a matching journal entry is created in your general ledger that debits your default inventory account and credits your default expense account. When you sync a negative adjustment, a matching journal entry is created that does the opposite.
The matching journal entry is given a unique reference, shown in the Reference column on the Adjustments & COGS > Adjustments tab of your QuickBooks Online integration dashboard. Note that, if the reference on the dashboard exceeds 21 characters, it will be truncated to 21 characters in QuickBooks Online.
You can only sync adjustments with
a Completed date,
an Accounting Adjustment Date date, and
a positive or negative Total.
Sync adjustments
Log in to Cin7 Omni.
From the Accounting menu in the navigation, open your QuickBooks Online integration.
Open the Adjustments & COGS > Adjustments tab.
-
In the right-hand column of checkboxes, either
select the adjustment(s) to sync, or
to select all adjustments, select the checkbox in the header.
Select Upload Selected (or Upload All).
You’ll receive a notification if any adjustment fails to sync. Find and fix the adjustment on the Errors > Adjustments tab and then re-sync it.
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB