BSAD table — Cleared Customer Items (Accounts Receivable)

A row in BSAD represents one customer line item that has been cleared, meaning it has been matched off against a payment, a credit memo, another invoice, or a write-off. It carries the original posting key fields (document number, fiscal year, line item, posting date, amount) plus the clearing-specific fields: which clearing document closed it and on what date. BSAD is populated the moment a line item leaves the open state in BSID; the line does not stay in both tables, it moves. This makes BSAD the table to query for 'this invoice was paid three weeks late, prove it' or 'why does this customer show zero open items when the invoice is still unpaid in the source system' type questions during reconciliation and audit support.

MANDT is implicit in most tools but never skip it if querying at database level. Always restrict on BUKRS and KUNNR before anything else; BSAD is a cluster of every cleared item ever posted for every customer in the client, and a query with only a date range on BUDAT or AUGDT will scan enormous volumes. If the question is about a specific clearing event, filter on AUGBL and AUGDT together, not AUGDT alone, since clearing runs post many documents on the same date. If the question is about a specific invoice, filter on BELNR plus GJAHR plus BUKRS, not BELNR alone, because document numbers repeat across fiscal years and company codes.

Symptom: a customer disputes that invoice 1900000123 was ever paid. Select BSAD where BUKRS = the company code, KUNNR = the customer, BELNR = '1900000123', GJAHR = the invoice year. If a row returns, read AUGBL and AUGDT: that is the clearing document and date. Follow AUGBL into BKPF to see what kind of document closed it (incoming payment, credit memo, transfer posting) and BSEG to see the offsetting bank or clearing account.

On S/4HANA, the line item detail that BSAD held is now sourced from the universal journal, ACDOCA, with clearing status derived from the same fields SAP always used but stored differently underneath. BSAD, BSID, BSIK and BSAK are kept as compatibility views for existing reports and interfaces; reads still work and return the same shape of data, but the physical table no longer exists as a separate database object the way it did in ECC. New custom development should query ACDOCA directly with the appropriate clearing fields rather than building fresh logic on the compatibility view.

Accounts receivable accounting owns the business meaning of clearing status. FI configuration owns the clearing rules and tolerance groups that decide how items get matched. Basis or the data team owns performance concerns when a query against BSAD or its S/4 equivalent is slow. Disputes about whether an item was correctly cleared belong to the AR team first, escalated to functional FI consulting only when the clearing logic itself looks wrong.

BSID is the direct counterpart holding open (uncleared) customer items; an item moves from BSID to BSAD the moment it clears. BKPF and BSEG hold the full document header and line item detail behind both. Clearing transactions such as incoming payment posting and manual clearing write these tables. KNC1 holds the summarized customer transaction figures used for high-level balance checks without reading line items. On S/4HANA, ACDOCA is the underlying source for all of this.