Mapping: Debtor, Item, Clearing

Which SAP field becomes which Bilendo column — and how a clearing travels.

The Debtor Is the Contract Account

Items, the dunning procedure, payment method, and SEPA mandate are tied to the contract account, and a business partner can have several. Therefore: customer_number = ContractAccount, and the business partner becomes the grouping element (external_parent_id).

Bilendo	SAP	Rule
`customer_number`	`ContractAccountPartner.ContractAccount`	unchanged
`external_parent_id`	`ContractAccountPartner.BusinessPartner`	Groups the accounts of a partner
`customer_name_1`	`A_BusinessPartner.BusinessPartnerFullName`	Person: last name, first name
`customer_street` … `customer_country`	`A_BusinessPartnerAddress` (default address)	ISO 2-letter country code
`company_code`	`CAStandardCompanyCode`	Company code of the account
`external_payment_term`	`PaymentCondition`	Key
`dunning_stop`	`CABusPartnerAddlLockExstcCode` / `CABusPartnerPostgLockExstcCode` set	Lock on the debtor (additional lock or posting lock)
Custom field "Dunning procedure" (mapped)	`CADunningProcedure`	→ Bilendo dunning area (see Dunning Procedure)
Custom field "Dunning grouping" (mapped)	`CADunningNoticeGroup`	→ Bilendo dunning group
Custom field "Payment method"	`CAPaymentMethodForIncgPayment`	Direct debit indicator

The Open Item

Identity in Bilendo: contract · document number · company code · posting line. An item that is delivered again is updated.

Bilendo	SAP (BPItem)	Rule
`receipt_number`	`CADocumentNumber`	Key component
`company_code`	`CompanyCode`	Key component
`external_position`	`CABPItemNumber` + `CARepetitionItemNumber` + `CASubItemNumber`	Concatenated, key component
`erp_reference`	`CAContract`	Utility contract, key component
`imported_customer_number`	`ContractAccount`	Points to the debtor
`invoice_number`	`CAReferenceDocument`	Invoice number from the customer's perspective
`receipt_date` / `external_creation_date`	`DocumentDate` / `CAPostingDate`	Posting date is the delta anchor
`due_date`	`CANetDueDate`	In case of deferral, `CADeferralDate` applies
`amount` / `currency`	`CAAmountInTransactionCurrency` / `TransactionCurrency`	Receivable positive, payment negative
`open_amount`	`CAOpenAmountInTransactionCrcy` (invoice view)	0 for full clearing
`external_doctype` / `external_doctype_hint`	`CADocumentType` / `CAMainTransaction`+`CASubTransaction`	Customer's mapping table
`dunning_stop`	`CAItemIsExcludedFromDunning` · deferral · collections case	Bilendo doesn't dun what SAP excludes
`delete_indicator`	`CAReversedDocumentNumber` set	Reversal withdraws the item
— (do not deliver)	`CAStatisticalItemCode` ≠ empty	Statistical items are not receivables — exception: installment payments via the CDS view

Clearing

Hard clearing: FI-CA clears the item → the item travels again in the next delta with external_clearing_number1 (CAClearingDocumentNumber), external_clearing_date, and fully_cleared_indicator. Bilendo replaces it; it leaves the dunning run.
Soft clearing: payment on account, partial payment before clearing → the receivable and the payment travel with the same assignment number erp_association (= CAReferenceDocument, otherwise the item key); Bilendo offsets them to a remaining balance of 0.
Reset of a clearing: CAClearingPostingIsReset → the item travels again without clearing fields; Bilendo reopens it.
Direct debit: a collected item is not overdue — it travels with a dunning block until a returned direct debit arrives.