Check supplier credit notes for reconciliation
Overview
Find and fix supplier credit notes causing discrepancies between Cin7 Omni and Xero or QuickBooks Online.
Supplier credit notes must have the following information to sync to Xero or QuickBooks Online:
A Completed Date
A Supplier Credit Note Date
If a supplier credit note has one but not the other, Cin7 Omni and Xero or QuickBooks Online won’t reconcile. You must find these supplier credit notes and add the missing information for reconciliation.
Find supplier credit notes to fix
First, find supplier credit notes with a Completed Date and no Supplier Credit Note Date:
From the Purchases menu in the navigation, open Supplier Credit Notes.
Set Supplier Credit Note Status to Completed But Not Invoiced. The supplier credit notes in the results have a Completed Date but no Supplier Credit Note Date.
Then find supplier credit notes with a Supplier Credit Note Date and no Completed Date:
From the Purchases menu in the navigation, open Supplier Credit Notes.
Set Supplier Credit Note Status to Search All.
Order the results by Accounting status (click the Accounting column header). In the results, any purchase order with an Accounting status but no Completed Date has a Supplier Credit Note Date but no Completed Date.
Fix supplier credit notes
For each of these supplier credit notes missing either a Completed Date or Supplier Credit Note Date, open the transaction and add the missing data and save. Then sync your supplier credit notes to Xero or sync your supplier credit notes to QuickBooks Online.
- 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