Description
Xero has been identified as the Master data storage for Payment records, meaning that Stellarise Connector needs to transform and allocate Xero Payment into InforLN and not vice-versa. In such a way, the expected result is to have InforLN populated with Payment records coming from Xero and correctly allocated to the invoices.
Logic
Every time the Stellarise Connector starts to run, it needs to work out all the Xero Payments that are created or updated from the last run to Now, as described by the Data Collection chapter.
- Payments: using the extracted Payments subset, Stellarise Connector Creates the Payment records in InforLN, reporting the Xero Invoice Number to InforLN, so to have a relation between InforLN and Xero where it exists. In Xero is not possible to create a Payment without an invoice reference.
There is the possibility to create Prepayments, but these are not used by Linea Light. - Proforma invoices: in the Linea Light Xero account, proforma invoices are normal invoices with a payment attached to it.
Normally the invoice name starts with “419” or “420” depending on the creation year. Naming convention is anyway not relevant for the project itself.
Payments defined against a proforma invoice follow the same process as normal Invoice/Payments.
Possible caveats
In Xero you can unreconcile a payment from an invoice to potentially solve an accounting issue. Will this feature if used still work its way through to InforLN? The short answer is yes, but it will be manual. These edge cases, if/when they happen, need to be manually addressed in InforLN; indeed, regardless the InforLN sales invoice immutability, the payments against it can be amended but it’ll be anyway a manual activity to be made in InforLN to keep both the systems aligned.