...
The Connector realises the match by ContactNumber or Name and checks for differences (e.g. tax number, bank account, primary contact, address, etc.): Infor and Xero differ. The Connector updates the Xero Contact updating its information with the details reported in Infor.
Sales Invoices and Credit Notes
InforLN Sales invoice serie "2xxx" but does not exist in Xero.
...
Stellarise Connector creates or updates the Xero invoice by "InvoiceNumber = 303-SI1-2000004". It will only have one invoice line, having unit price, discount, tax amount and total amount calculated as the sum of all the the InforLN invoice lines. Invoice Line Description just reports "RTF" if the InforLN Invoice "RelatedPurchaseInvoice" field is empty, the content of the InforLN Invoice "RelatedPurchaseInvoice" field if it is assigned.
InforLN Sales invoice from Sales Order
InforLN Sales invoice manual (services)
InforLN Sales invoice Ledger Code / Tax rates not mapped in Stellarise Connector
...
Stellarise Connector collects then all the timeframe matching InforLN Invoices, but "InvoiceName = 303-SI1-2000006" is one of them. and realises that the Ledger code or the Tax Rate that should be present in the InforLN-Xero ledgercodes/taxrates map (Connector Settings) but it is not. Anyway, there is a default Ledger Code / Tax rate defined against it: Stellarise Connector will then assign this default values to the Xero invoice, that will then be successfully created in Xero.
Xero Sales Invoice exists but not in InforLN
In Xero there is "InvoiceNumber = INV-00049" but in Infor this does not exist.
By Design, the Connector does not send back Sales Invoices to InforLN. InforLN is the source of truth of the Sales Invoices, all the Sales Invoices should be created in there. This does not give any problem in terms of Invoice synchronisation, but it will in terms of Payments: indeed the Connector is designed to collect all the recently-changed payments in Xero and trying to sync them back to InforLN. In this case InforLN will fail, raising an exception in the Stellarise Connector Audit Table.
Purchase Invoices (InforLN to Xero)
Purchase Invoices from InforLN to Xero use cases can be mostly covered by the test cases for the Sales Invoices, since they share moslty the same communication logic. The following use cases In addition to the :
InforLN Purchase Invoice: "source" field different from empty
In InforLN, there are some purchase invoices modified in a given period of time. Some of them are legitimate and some aren't because they were created by Stellarise Connector in the previous run.
When Stellarise Connector runs the next time, it must discard the ones that it has previously generated. To do this, the InforLN API provides an extra "Source" field, reporting the origin of the invoice. If it is empty, then it has been originated by InfoLN so it can be sent to Xero, otherwise the invoice is simply ignored.
Purchase Invoices with Attachments
In InforLN there is a purchase invoice 303-PI1-600001 that needs to be created in Xero. In InforLN, this invoice has a PDF attachment as well.
After the Connector has transferred the details of the Purchase Invoice to Xero, creating the Xero Purchase Invoice "303-PI1-600001", the following task that the connector performs is to check if there is a file attachment for the given Purchase Name in InforLN. InforLN reponse reports that there is a file called "600001.pdf" alongisde with its binary content. Preserving the filename, the Connector then attach it to the "303-PI1-600001" Xero Purchase Invoice.
Invoice Line description from "RTF" to "Related to:"
In Xero there is the invoice "303-SI1-200001", initially produced by the Connector. The Invoice has the designed single invoice line having the "Description" field filled with the string "RTF", suggesting that this invoice is waiting for a related purchase invoice to appear.
When the Connector runs, it picks up from InforLN the Purchase "303-PI1-600001", which has the field "RelatedSalesInvoice" set to "303-SI1-200001". The Connector creates then the Purchase Invoice "303-PI1-600001" in Xero, InforLN Sales Credit Notes
In InforLN, Sales Credit Notes follow the same logic as per Sales Invoices. The only difference is the minus sign on the amounts that the Connector then ignores when transferring the Credit Note to Xero (Xero automatically assigns the negative amount thanks to the fact that the entity is a Credit Note).
Xero Sales Invoice exists but not in InforLN
In Xero there is "InvoiceNumber = INV-00049" but in Infor this does not exist.
By Design, the Connector does not send back Sales Invoices to InforLN. InforLN is the source of truth of the Sales Invoices, all the Sales Invoices should be created in there. This does not give any problem in terms of Invoice synchronisation, but it will in terms of Payments: indeed the Connector is designed to collect all the recently-changed payments in Xero and trying to sync them back to InforLN. In this case InforLN will fail, raising an exception in the Stellarise Connector Audit Table.
Purchase Invoices (InforLN to Xero) and Credit Notes
Purchase Invoices from InforLN to Xero use cases can be mostly covered by the test cases for the Sales Invoices, since they share moslty the same communication logic. The following use cases In addition to the :
InforLN Purchase Invoice: "source" field different from empty
In InforLN, there are some purchase invoices modified in a given period of time. Some of them are legitimate and some aren't because they were created by Stellarise Connector in the previous run.
When Stellarise Connector runs the next time, it must discard the ones that it has previously generated. To do this, the InforLN API provides an extra "Source" field, reporting the origin of the invoice. If it is empty, then it has been originated by InfoLN so it can be sent to Xero, otherwise the invoice is simply ignored.
Purchase Invoices with Attachments
In InforLN there is a purchase invoice 303-PI1-600001 that needs to be created in Xero. In InforLN, this invoice has a PDF attachment as well.
After the Connector has transferred the details of the Purchase Invoice to Xero, creating the Xero Purchase Invoice "303-PI1-600001", the following task that the connector performs is to check if there is a file attachment for the given Purchase Name in InforLN. InforLN reponse reports that there is a file called "600001.pdf" alongisde with its binary content. Preserving the filename, the Connector then attach it to the "303-PI1-600001" Xero Purchase Invoice.
Invoice Line description from "RTF" to "Related to:"
In Xero there is the invoice "303-SI1-200001", initially produced by the Connector. The Invoice has the designed single invoice line having the "Description" field filled with the string "RTF", suggesting that this invoice is waiting for a related purchase invoice to appear.
When the Connector runs, it picks up from InforLN the Purchase "303-PI1-600001", which has the field "RelatedSalesInvoice" set to "303-SI1-200001". The Connector creates then the Purchase Invoice "303-PI1-600001" in Xero, updating the invoice line Description field of the previously created Xero Sales Invoice "303-SI1-200001", from the existing "RTF" string to the string: "related to: 303-PI1-600001", from the existing "RTF" string to the string: "related to: 303-PI1-600001".
InforLN Purchase Credit Notes
In InforLN, Purchase Credit Notes follow the same logic as per Purchase Invoices. The only difference is the minus sign on the amounts that the Connector then ignores when transferring the Credit Note to Xero (Xero automatically assigns the negative amount thanks to the fact that the entity is a Credit Note).
Service Purchase Invoices (Xero to InforLN) and Credit Notes
The use case Xero Purchase Invoice Collection: InvoiceNumber format check can be reused for Service Purchase Invoices from InforLN to Xero. In addition:
Xero Purchase Invoice addressed to a Xero Contact that has a related InforLN Business Partner HAVING Supplier role
This Invoice "2020 JAN electricity" was manually generated in Xero through Receipt Bank, it does not exists in InforLN. Its Contact is set to a Xero Contact called "EDF Energy group".
The connector picks the Xero Bill "2020 JAN electricity" up and analyses if the Contact "EDF Energy group" has the InforLN Business Partner Code attached to it. There is, its "30000024", this means "EDF Energy group" is considered as a recurring supplier by Desgn. Once this invoice is sent back to InforLN, it is then created as Purchase Invoice assigned to the Business Partner "30000024".
Xero Purchase Invoice addressed to a Xero Contact that has a related InforLN Business Partner NOT HAVING Supplier role
This Invoice "2020 Feb electricity" was manually generated in Xero through Receipt Bank, it does not exists in InforLN. Its Contact is set to a Xero Contact called "Enel Energy group". "Enel Energy group" does exist in InforLN, but it is only tagged as Customer, not as Supplier.
The connector picks the Xero Bill "2020 Feb electricity" up and analyses if the Contact "Enel Energy group" has the InforLN Business Partner Code attached to it. There is, its "30000025", this means "Enel Energy group" should be considered as a recurring supplier by Design. Once this invoice is sent back to InforLN, it is then created as Purchase Invoice and... ASK MARCELLO
Xero Purchase Credit Notes
The Purchase Credit Note "CN-0002" was manually generated in Xero, it does not exists in InforLN. Its Contact is set to "ABC Customer ltd", existing in InforLN as Business Partner.
The connector picks this Credit Note up and tries to transfer it to InforLN. "ABC Customer ltd" is correctly found as Business Partner; this credit note will then be created as a Purchase Invoice against the "ABC Customer ltd" .
Other Purchase Invoices (Xero to InforLN) and Credit Notes
Xero Purchase Invoice Collection: InvoiceNumber format check
...
The connector picks it up and analyses if the Contact "Mario Rossi expenses" has the InforLN Business Partner Code attached to it. It does not, this means "Mario Rossi expenses" is considered as a non-recurring supplier. Once this invoice is sent back to InforLN, it is then created as an Expense Item, reporting "Mario Rossi expenses" as a reference.
Service Purchase Invoices (Xero to InforLN)
The use case Xero Purchase Invoice Collection: InvoiceNumber format check can be reused for Service Purchase Invoices from InforLN to Xero. In addition:
Xero Purchase Invoice addressed to a Xero Contact that has a related InforLN Business Partner
This Invoice "2020 JAN electricitya reference.
Xero Purchase Credit Notes
The Purchase Credit Note "CN-0001" was manually generated in Xero through Receipt Bank, it does not exists in InforLN. Its Contact is set to a fictional Xero Contact called "EDF Energy groupMario Rossi expenses".
The connector picks the Xero Bill "2020 JAN electricity" up and analyses if the Contact "EDF Energy group" has the InforLN Business Partner Code attached to it. There is, its "30000024", this means "EDF Energy group" is considered as a recurring supplier. Once this invoice is sent back to InforLN, it is then created as Purchase Invoice assigned to the Business Partner "30000024".this up and tries to transfer it to InforLN. Since in InforLN there is no Business Partner called "Mario Rossi expenses", this credit note will be created as an "Expense Record" with a negative sign, related to the "Mario Rossi" employee
Payments
| Info |
|---|
During the description of the following use cases:
|
...