Mapping: Customer, Line Item, Clearing

Customer + company code is the customer master, company code · document · fiscal year · line item is the line item — and a partial payment is a new document.

• Hard clearing: the item travels again in the next delta with external_clearing_number1 (ClearingAccountingDocument), external_clearing_date and fully_cleared_indicator from IsCleared. Bilendo replaces it; it leaves the dunning run.

• Reversal of a clearing: ClearingIsReversed — the item comes back without clearing fields and is reopened. A dedicated field; nothing needs to be guessed here.

• Residual item formation: the payment clears the original item and posts a new one for the remainder. InvoiceReference + InvoiceReferenceFiscalYear + InvoiceItemReference point to the origin and travel along as erp_reference — otherwise Bilendo ends up with two unconnected receivables.

• Partial payment without clearing: the receivable and the payment share the assignment number; Bilendo nets them to a remaining amount of 0.

• Direct debit: an item in collection is not overdue — PaymentMethod plus HasPaymentOrder means a dunning block until a return debit occurs.

Which of the two partial-payment worlds applies to you is the question where a wrong assumption immediately produces wrong amounts — that's why it's part of the "Business Definitions" questionnaire.