Overview
Find out how to synchronize credit notes with Xero.
Credit notes must be synced to Xero to keep your books in order.
When you sync a new credit note, a matching credit note is created in your Xero general ledger. You can only sync a credit note with:
- A Sales Reference
- A Credit Note Date
- A non-zero Total
- A contact linked to Xero
Additionally, on the Admin page of the credit note, its Accounting Status must be set to Not Imported Yet Or Reset For Re-import, although all credit notes meet this condition by default; once the credit note has been synced, its Accounting Status gets set to Imported.
The matching credit note is given a unique reference. That reference, shown in the Reference column on the Sales > Credit Notes tab of your Xero integration dashboard, is a combination of (a) a unique serial number, (b) the original credit note’s reference, and optionally (c) a custom prefix.
Alternatively, instead of syncing credit notes individually, you can combine the credit note in a batch. Find out how to batch credit notes.
Sync credit notes
- Log in to Cin7 Omni.
- From the Accounting menu in the navigation, open your Xero integration.
- Link new contacts (if any) to Xero (see how to link contacts to Xero).
- Open the Sales > Credit Notes tab.
- In the left-hand column of checkboxes, either:
- Select the credit note(s) to sync, or
- To select all credit notes (and other listed transactions), select the checkbox in the header.
- Select Upload Selected (or Upload All).
You’ll receive a notification if any credit note fails to sync. Find and fix the credit note on the Errors > Credit Notes tab and then re-sync it.
Once you’ve synced a credit note, you must apply the matching credit note to an invoice in Xero.
FAQs
Can I sync credit notes automatically?
No, credit notes should be synced manually.
- 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