Overview
Find out how to synchronize supplier credit notes with Xero.
Supplier credit notes must be synced to Xero to keep your books in order.
When you sync a new supplier credit note, a matching supplier credit note is created in your Xero general ledger. You can only sync a supplier credit note with:
- A Supplier Credit Note Date
- A Supplier Credit Note No
- A non-zero Total
- A contact linked to Xero
Additionally, on the Admin page of the supplier credit note, its Accounting Status must be set to Not Imported Yet Or Reset For Re-import, although all supplier credit notes meet this condition by default; once the supplier credit note has been synced, its Accounting Status gets set to Imported.
The supplier credit note is given a unique reference. That reference, shown in the Reference column on the Purchases > Supplier Credit Notes tab of your Xero integration dashboard, is a combination of (a) a unique serial number and (b) the original supplier credit note’s reference.
Sync supplier 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 Purchases > Supplier Credit Notes tab.
- In the left-hand column of checkboxes, either:
- Select the supplier credit note(s) to sync, or
- To select all supplier 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 supplier credit note fails to sync. Find and fix the supplier credit note on the Errors > Credit Notes tab and then re-sync it.
Once you’ve synced a supplier credit note, you can apply the matching supplier credit note to a bill in Xero.
FAQs
Can I sync supplier credit notes automatically?
No, supplier 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