Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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

...

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.

...

InforLN Sales invoice wrong Ledger Code / Tax rates

In InforLN there is an invoice having Invoice Name "303-SI1-2000004" having one invoice line that has a ledger code and a tax rate not correctly mapped in the Stellarise Connector settings. No defaults behavior is also set in the Stellarise Connector settings.

Stellarise Connector collects the InforLN Invoice "InvoiceName = 303-SI1-2000004" and realises that the Ledger code or the Tax Rate that should be present in the InforLN-Xero ledgercodes/taxrates map (Connector Settings). 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 correct Ledger Code / Tax rates but not mapped

...

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 correct Ledger Code / Tax rates, not mapped but with default



Goods Purchase Invoices

Xero Purchase Invoice Collection: InvoiceNumber format check

...

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 sent to non recurring Supplier


Prepayments

Xero Prepayment received from Client

...