...
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)
This can be pretty much covered by the test cases for the Sales Invoices. In addition
InforLN Purchase Invoice: "source" field different from Stellarise
...
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 discarded.
InforLN Sales Purchase invoice wrong Ledger Code / Tax rates - No mapping
InforLN Sales invoice correct Ledger Code / Tax rates but not mapped
InforLN Sales In InforLN, there is the invoice "303-PI1-2000001" having an invoice line with account code assigned of "4000"
InforLN Purchase invoice correct Ledger Code / Tax rates, not mapped but with default
"RTF" to "Sales Invoice:"
Goods Purchase Invoices (Xero to InforLN)
Xero Purchase Invoice Collection: InvoiceNumber format check
...
Xero Purchase Invoice without related Business Partner
Service Purchase Invoices (Xero to InforLN)
Xero Purchase Invoice with related Business Partner
...