To have an overview of what Stellarise Connector for InforLN and Xero does, this is a list of the different use cases that may happen during the integration process and the description of the expected outcome.
Contacts
InforLN Contact does not exist in Xero - Xero Name does not exist, Xero Contact Number does not exist
In Infor LN there is "Foreign Customèr S.R.L" having Business Partner ID set to "30000010" but in Xero this does not exist.
After the connector has searched in Xero for the "Contact Number = 30000010" and the "(small case, numbers and letters only , ignoring accents)Name = foreigncustomersrl", the Connector then creates "Foreign Customèr S.R.L" in Xero, having Contact Number set to 30000010 and all the InforLN information described by Design.
InforLN Contact does partially exist in Xero - Xero Name does exist, Xero Contact Number does not exist
In InforLN there is "Foreign Customèr S.R.L" having Business Partner ID set to "30000010" and in Xero you have "foreign customer s.r.l" but without Contact Number.
After the connector has searched and found in Xero the "(small case, numbers and letters only , ignoring accents)Name = foreigncustomersrl", the Connector then updates the existing Xero Contact reporting all the InforLN information described by Design and assigning the Xero Contact Number to "30000010".
InforLN Contact does partially exist in Xero - Xero Name does exist, Xero Contact Number does not exist
In InforLN there is "Foreign Customèr S.R.L" having Business Partner ID set to "30000010" and in Xero you have "foreign customer Italia" having Contact Number set to "30000010".
The connector searches and finds "Contact Number = 30000010". Then updates the existing Xero Contact reporting all the InforLN information described by Design.
InforLN Contact already exists in Xero and they are both the same
In InforLN there is "Foreign Customèr S.R.L" having Business Partner ID set to "30000010" and in Xero you have the same.
The Connector realises the match by ContactNumber or Name and checks for differences (e.g. tax number, bank account, primary contact, address, etc.): both Infor and Xero give the same checksum, the Connector does nothing and moves on.
InforLN Contact already exists in Xero and they differ for one or more details
In InforLN there is "Foreign Customèr S.R.L" having Business Partner ID set to "30000010" and Tax Number "1234567890". In Xero you have the same but the Tax Number is "0987654321".
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
InforLN Sales invoice serie "2xxx" but does not exist in Xero.
In InforLN there is an invoice having Invoice Name "303-SI1-2000001" but in Xero there is not such invoice.
Stellarise Connector does not find the Xero invoice by "InvoiceNumber = 303-SI1-2000001" so it creates it with "InvoiceNumber = 303-SI1-2000001" and all the InforLN information defined by Design.
InforLN Sales invoice serie "2xxx" and it does exist in Xero.
In InforLN there is an invoice having Invoice Name "303-SI1-2000001" and in Xero it exists as well.
Stellarise Connector finds the Xero invoice by "InvoiceNumber = 303-SI1-2000001" so it goes into Xero and to update it with the InforLN information defined by Design.
InforLN Sales invoice serie "4xxx" (pro-forma orders)
In InforLN there is an invoice having Invoice Name "303-SI1-4000001" and in Xero it may exist or not.
In Xero there is not such distiction between a normal invoice or a LineaLight invoice from pro-forma order. The invoice will be created following the serie "2xxx" logic.
InforLN Sales invoice single line
In InforLN there is an invoice having Invoice Name "303-SI1-2000003" having one invoice line that has a ledger code and a tax rate correctly mapped in the Stellarise Connector settings.
Stellarise Connector creates or updates the Xero invoice by "InvoiceNumber = 303-SI1-2000003". It will only have one invoice line, having unit price, discount, tax amount and total amount matching with the InforLN invoice. 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 multiple lines
In InforLN there is an invoice having Invoice Name "303-SI1-2000004" having multiple invoice lines that have a ledger code and a tax rate correctly mapped in the Stellarise Connector settings.
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 wrong Ledger Code / Tax rates
InforLN Sales invoice correct Ledger Code / Tax rates but not mapped
InforLN Sales invoice correct Ledger Code / Tax rates, not mapped but with default
InforLN Sales invoice created now, but the "Process until" setting in Stellarise Connector is set to "Until yesterday"
Xero Sales Invoice exists but not in InforLN
In Xero there is "InvoiceNumber = INV-00049" but in Infor this does not exist.
By Desgin, 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 Purchase Invoice: "source" field <> Stellarise
InforLN Sales invoice wrong Ledger Code / Tax rates
InforLN Sales invoice correct Ledger Code / Tax rates but not mapped
InforLN Sales invoice correct Ledger Code / Tax rates, not mapped but with default
Goods Purchase Invoices
Xero Purchase Invoice Collection: InvoiceNumber format check
Xero Purchase Invoice with related Business Partner
Xero Purchase Invoice without related Business Partner
Service Purchase Invoices
Xero Purchase Invoice with related Business Partner
Xero Purchase Invoice without related Business Partner
Payments
Xero Payment received from Client
Xero Payment received from Client and related to Prepayment
Xero Payment sent to recurring Supplier
Xero Payment sent to non recurring Supplier
Prepayments
Xero Prepayment received from Client
Xero Prepayment made for recurring (Xero supplier does exist in Infor) and non recurring Supplier (Xero supplier does not exist in Infor)