|
|
| (70 intermediate revisions by 4 users not shown) |
| Line 1: |
Line 1: |
| − | == Xero Integration == | + | =This Content Has Moved House= |
| | | | |
| − | Emersion is committed to integration to the Xero Billing Platform found at www.xero.com.
| + | This article has been moved to our new home for documentation and help content, the new Emersion Knowledge Base. |
| | | | |
| − | Emersion supports:
| + | We are sorry for the untidiness while we are shifting locations and we appreciate your patience during the transition to our new home. |
| − | * invoices being pushed out
| |
| − | * receive payments processed in Xero
| |
| − | * processing credit notes inbound
| |
| | | | |
| − | This basic flow describes the integration further.
| + | [https://resources.emersion.com/display/EKB/Xero Take me to the new articles] |
| | | | |
| − | * A new invoice is generated in Emersion under an account active for Xero. This requires the customer account to be present in both Xero and Emersion. A one to one relationship with one company in Xero and one in Emersion must exist.
| + | [[file:new_home_sm.jpg|900px]] |
| − | * This invoice is then created via the integration in Xero.
| |
| − | * The new invoice in Xero is generated with no cardlines and just a description to hold it in place, it is generated in '''Draft''' status.
| |
| − | * The invoice receives cardlines and charges as usual.
| |
| − | * Once the invoice in Emersion is marked as '''Approved''', all pending cardlines will be sent to the appropriate Xero invoice as line items, and marked as '''Approved''' in Xero.
| |
| − | ** If there are any payments allocated against the invoice in Emersion, they will be transferred to the invoice in Xero.
| |
| − | | |
| − | === Integration Supported ===
| |
| − | | |
| − | A new invoice is generated in Emersion under an account active for Xero – this invoice is then generated in Xero and we take the id from Xero and store it locally for use later on. The new invoice in Xero is generated with no cardlines and just a description to hold it in place, it is generated in DRAFT status.
| |
| − | | |
| − | Normal processes occur in Emersion with the invoice gaining cardlines and charges as usual.
| |
| − | | |
| − | Once the invoice in Emersion is marked as APPROVED, all of the cardlines will be sent to the appropriate Xero invoice as line items, and marked as APPROVED in Xero. If there are any payments allocated against the invoice in Emersion, they will be transferred to the invoice in Xero.
| |
| − | | |
| − | As any payments after this fact are allocated against the invoice in Emersion, so too will they be transferred to Xero for the same value against the right invoice. The payment locally will be updated with the Xero payment ID, so we don’t end up doubling up the payment.
| |
| − | | |
| − | If any payments are made in Xero against the invoice, and these payments don’t exist in Emersion, and the payment is against an invoice that originated in Emersion, then the details and payment against the invoice is stored in Emersion.
| |
| − | | |
| − | === Assumptions ===
| |
| − | | |
| − | Emersion knows of ONE bank account that payments, when sent to Xero, go into. The Emersion API is not going to be designed to handle payment submission to a choice of bank accounts or more than one account in Xero marked as ‘receive payment allowed’.
| |
| − | | |
| − | Emersion will only pull over payments to Emersion from Xero in the API, under the following rules:
| |
| − | The payment does not exist in Emersion already.
| |
| − | The invoice that the payment is done against in Xero exists in the Emersion system.
| |
| − | Any overpayments (that in Xero, generate an unrelated new invoice and a credit) will not be pulled over as we have no knowledge of the invoice that is generated by an overpayment (Split payment) in Xero.
| |
| − | | |
| − | == Configuration of Xero and Emersion ==
| |
| − | | |
| − | This requires subscription to the Xero Integration. Please contact sales@emersion.com.au for a quote for this feature.
| |
| − |
| |
| − | Before Xero and Emersion integration is configured,
| |
This article has been moved to our new home for documentation and help content, the new Emersion Knowledge Base.
We are sorry for the untidiness while we are shifting locations and we appreciate your patience during the transition to our new home.
