Versions Compared

Key

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

...

The use case Xero Purchase Invoice Collection: InvoiceNumber format check can be reused for Serice Service Purchase Invoices from InforLN to Xero. In addition:

...

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".



Payments


Info

During the description of the following use cases:

  • The Bank Account Number will be always sent from Xero to InforLN as the "Account Number", i.e. excluding the sort-code part. This assumption is due to InforLN limitations and has been taken during the Design phase.
  • The Contact Name is always passed from Xero, even if there is no InforLN correspondence. This because this string can then be used as a reference.


Xero Payment received from Client

There is a straight Xero Payment having ID 1234-1234-1234-1234 against an invoice, the related Customer exists in InforLN and the amount is not related to any pre-payment.

The connector picks the Xero Payment "1234-1234-1234-1234" up and checks for the Customer InforLN Code. When this preliminary check is done, then the connector sends the payment to InforLN. Particularly, paying attention to the following field:

DocumentType: 1, In InforLN means "Allocated Sales Payment"

BusinessPartner: 300000366, InforLN customer code to allocate the payment against.

InvoiceNumber: 303-SI1-1234567890, the Invoice to allocate the payment against.

XeroPaymentID

XeroPprepaymentID

XeroContactName


Xero Payment received from Client and related to Prepayment

...

Xero Payment sent to non recurring Supplier


Prepayments

Xero Prepayment received from Client

...