Payments in Xero
Both QuickBooks Online users and Xero Accounting users have the ability to add payments to supplier invoices. Payments can be added within the accounting application and then synchronised to Cin7 Core or added in Cin7 Core and synced to the accounting software. QuickBooks Online users will sync payments automatically, but Xero users will have to ensure the correct payment settings are enabled.
Users will need the Integration: Accounting - Xero permission in order to use this feature.
This article explains how different types of payment are handled by Cin7 Core and Xero.
Prerequisites
Connect Xero to Cin7 Core (required)
Ensure your Chart of Accounts is set up correctly (see Xero Integration - Setting up Accounts in Xero).
Payment Settings
Cin7 Core users with Xero integration have three options for applying payments to invoices:
Pull payments from Xero
Push payments to Xero
Synced both ways (default setting).
For payments applied in Cin7 Core to be applied to Cin7 Core or Xero invoices, payments must be set to push payments to Xero or synced both ways.
Change Xero payment settings:
Navigate to Integration → Xero.
Check that Xero payments are set to either Sync both ways or Pushed to Xero.
Save your changes.
Payments and Refunds
Note: Payments can only be synced if there is a synced invoice to apply the payment to. For example, if an error occurs during syncing of INV-1246, the payment applied to that invoice will not be synced.
Payments applied in Cin7 Core will be exported to Xero during synchronisation if your Xero payment settings are set to Pushed to Xero or Synced both ways. Payments applied in Xero will be exported to Cin7 Core during sync if your Xero payment settings are set to Pulled from Xero or Synced both ways.
Cin7 Core takes the due payment amount from invoices in Xero and exports payments from Cin7 Core to Xero for that invoice until the invoice is fully paid. Payments are consolidated based on the invoice ID in Xero, type of transaction (payment or refund), and account code.
During export, if payments exceed the total invoice amount, these are not exported. Undoing, deleting or changing a payment in Cin7 Core deletes the corresponding payment in Xero.
Payments are applied to invoices.
Credit Notes authorized in Cin7 Core will be exported to Xero, but will not be allocated against invoices. Credit Notes created in Xero are NOT picked up by Cin7 Core. Therefore the correct way to manage credit note refunds would be to enter the credit note in Cin7 Core, let it sync to Xero, and refund this credit note to customer credit. After that, apply this customer credit to invoice as a payment in Cin7 Core.
Customer Credits and Supplier Deposits
Customer Credits and Supplier Deposits are handled slightly differently from regular payments and refunds.
Note: To use this feature, you should have created accounts in Xero with the correct settings and mapped them to the equivalent Cin7 Core accounts in Settings → Reference Books → Financials → Account Mapping. It is important that your Customer Credit/Supplier Deposit accounts are set to accept payments.
Account |
Account Type |
System Account |
Accepting Payments |
Supplier Deposits/Prepayments |
Current Asset |
None |
Accepts payments |
Customer Credits |
Current Liability |
None |
Accepts payments |
Customer credits are amounts owed to customers, which can be used against future payments. In Xero, they are accounted for by a Customer Credits liability account. When a customer credit is applied to a sale quote, it is synced to Xero as a Money Received object. Learn more about Customer Credits.
Supplier Deposits are money that you have paid to a supplier, which can be used against future purchases. In Xero, they are accounted for by a Supplier Deposits asset account. When a supplier deposit is applied to a purchase order, it is synced to Xero as a Money Spent object. Learn more about Supplier Deposits.
Duplicate Payments
In some cases, users can accidentally create duplicate payments. For example, a payment has been applied in Cin7 Core but has yet to be synced to Xero. Another user processes the payment in Xero using bank reconciliation. When the payment from Cin7 Core eventually syncs to Xero, the payment will be duplicated, and an error occurs.
Cin7 Core stops these errors from happening by treating identical payments (payments for the same amount, on the same invoice, on the same day) as duplicates and removes them automatically.
Another cause of duplicate payments can be when your Cin7 Core account is connected both to Xero and to another eCommerce channel. When payments will be pulled from the eCommerce channel and payments are also applied in Xero and pulled to Cin7 Core, this can cause duplicates in Cin7 Core.
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB