Negative Balances in AR Aging Report Due to FBRA on Partial Clearings (SAP S/4HANA)

[sarfaraz1608]

Dear SAP Team, 

We’re facing an ongoing issue in our custom AR Aging report. After running FBRA (on 12.02.2025) to reverse incorrect partial clearings from 2022 for Customer 100009, the Aging report now shows negative balances in retro reports (2022 and 2023).

These DZ (clearing reversal) documents are technically correct per FI postings, but the CFO expects no negatives in the Aging Report. If we exclude these DZ docs, the report doesn’t match FS or FBL3N.

Goal: Build aging logic that matches Financial Statements and FBL3N, both retrospectively and prospectively, but avoids showing negative AR balances due to FBRA.

Any advice on handling FBRA and DZ documents in custom aging reports? Can we simulate prior status or apply dynamic logic for cleared history?

[Jeremy_Deo]

Hello dear user,

And thank you for asking your question in the SAP Community blog.

You're raising an issue that comes up often in aging report design when FBRA (Reset Cleared Items) and DZ documents (Customer Payments) are involved.

Let’s explore a practical approach for your custom AR aging report in SAP S/4HANA (Public or RISE).

Resume of your problem

• FBRA reverses clearing documents.
• This reopens historical invoices, but posts the reversal in the current period (e.g., Feb 2025).
• Retroactive aging reports for 2022 and 2023 now show negative balances due to:
• Reopened invoices (again aging)
• DZ (payment) documents still dated in the original cleared year
• CFO expects aging to show only open items, no negatives, aligned to FS/FBL3N.

Key Design Goals

• The report must:
• Match financial statements (FS10N/FBL3N)
• Respect current open items and aging
• Avoid misleading negative values from historic DZs
• Support both retrospective and current aging snapshots

Recommended Approach

1. Use clearing information dynamically

In your aging logic, leverage the fields:

• BSEG-AUGDT (Clearing date)
• BSEG-AUGBL (Clearing document)
• BSEG-AUGGJ (Clearing fiscal year)
• BSEG-AUGCP (Clearing posting period)

To determine the item status as of the aging key date (e.g., 31.12.2023):

• If AUGDT <= Aging Date, treat item as cleared
• If AUGDT > Aging Date or is blank, treat item as open

This allows simulating the cleared/open status as of any date.

2. DZ Documents: exclude or match reversed clearing logic

For DZ documents, which may still appear:

• Link them to the invoice via clearing documents (AUGBL)
• Only consider them if cleared before or on the aging date
• If FBRA reversed the clearing after aging date → the invoice was still cleared at that point → no need to include DZ in aging

3. Negative Balances Handling Rule

Add a rule:

• If the invoice was fully cleared as of aging date → exclude both invoice and payment from aging
• If only partially cleared by aging date → include remaining balance, but not overpayments (to avoid negatives)

4. Use Snapshot Tables (Optional)

For performance or audit purposes, you might:

• Build and store monthly snapshots of AR open items
• Helps with consistent retroactive reporting without recalculating logic every time

5. Report Enhancements (Optional)

Add flags to show:

• Was item fully cleared as of aging date?
• Is DZ reversal impacting retro view?
• Clearing document reversal info (FBRA detection logic)

This helps users understand edge cases and audit trails.

Technical Pointers

• BSEG is your friend, but in S/4HANA ACDOCA is often preferred.
• Use ACDOCA-AUGDT and ACDOCA-CLEAR_DATE fields.
• Consider using CDS Views like:
• I_JournalEntryItemCube
• I_CustomerLineItem with custom logic

I hope this will help answer your questions.

Best regards,

Jeremy

[sarfaraz1608]

Dear Jeremy, Thank you very much for your time and guidance ...