...
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: 1234-1234-1234-1234, The unique identifier of the Payment ID.
XeroPprepaymentID: "", no Prepayment are defined.
XeroContactName: "ABC Customer ltd", the String name of the Customer
Xero Payment received from Client and related to Prepayment
...
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: 5678-5678-5678-5678, The unique identifier of the Payment ID.
XeroPprepaymentID: "abcde-abcde-abcde-abcde", the Prepayment ID that this payment is relating to.
XeroContactName: "ABC Customer ltd", the String name of the Customer
Xero Payment sent to recurring Supplier
There is a straight Xero Payment having ID 4321-4321-4321-4321 against a Purchase Invoice, the related Supplier exists in InforLN. By Design definition, this means that the Supplier is IS a recurring supplier.
The connector picks the Xero Payment "4321-4321-4321-4321" up and checks for the Supplier InforLN Code. When this preliminary check is done, then the connector sends the payment to InforLN.
Particularly, paying attention to the following field:
DocumentType: 2, In InforLN means "Allocated Purchase Payment"
BusinessPartner: BP00000001, InforLN supplier code to allocate the payment against.
InvoiceNumber: abcdefg-303-PI1-1234567890, the Invoice to allocate the payment against.
XeroPaymentID: 4321-4321-4321-4321, The unique identifier of the Payment ID.
XeroPprepaymentID: "", the Prepayment ID is empty because the payment is not referring to any purchase prepayments.
Xero Payment sent to non recurring Supplier
XeroContactName: "Linea Ligth srl", the String name of the recurring SupplierXero Payment sent to non recurring Supplier
There is a straight Xero Payment having ID 5678ID 6453-56786453-56786453-5678 against an invoice6453 against a Purchase Invoice, the related Customer Supplier DOES NOT exists in InforLN and the amount IS related to a previously made pre-payment. By Design definition, this means that the Supplier IS NOT a recurring supplier. In this Use Case, Xero Preprayment ID will alwys be empty. By Design indeed, Prepayments to non recurring suppliers are practically impossible, meaning that it is not happening in the real life. If it should happen in future, they will be manually addressed in InforLN.
The connector picks the Xero Payment "56786453-56786453-56786453-56786453" up and checks for the Customer Supplier InforLN Code. When this preliminary check is done, then the connector sends the payment to InforLN; it does not exist, so pass the information to InforLN as a normal Payment, but without specifying the Supplier Code.
Particularly, paying attention to the following fieldfields will be sent:
DocumentType: 12, In InforLN means "Allocated SalesPurchase Payment"
BusinessPartner: 300000366 "", no InforLN customerBusiness codePartner to allocate the payment againstspecified, this means that in InforLN this payment will be recorded as an "Expense Record".
InvoiceNumber: 303 abcdefg-303-SI1PI1-1234567890, the Invoice to allocate the payment against.
XeroPaymentID: 56784321-56784321-56784321-56784321, The unique identifier of the Payment ID.
XeroPprepaymentID: "abcde-abcde-abcde-abcde", the Prepayment ID is always thatempty thisfor paymentPurchase isPayments relating torelated to Non-recurring-Suppliers.
XeroContactName: "Federico Rossi Expenses", the String name of the non-recurring Supplier
What to expect in InforLN: regardless the fact that DocumentType == 2 means "Allocated Purchase Payment" in InforLN, the simple fact that the BusinessPartner is empty will be interpreted by InforLN as a simple "Expense Record" rather then a real Payment.
Prepayments
Xero Prepayment received from Client
...