How to use the Accounts Receivable Aging Report.
Choose the aging date and bucket boundaries before grouping receivables. Use the remaining balance after payments and credits, and state whether aging starts at the due date.
Make the workflow fit your task.
Choose an as-of date, due-date convention and nonoverlapping aging buckets. Use outstanding balances after recorded payments and credits, calculate days past due, and reconcile bucket totals to the open ledger. Show future-due balances separately.
- What you provide
- Invoice balances, due dates and reporting date.
- What you get
- Aging buckets with deterministic totals.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
As of September 30: invoice A due September 20 has USD 100 open; invoice B due October 5 has USD 200 open.
Completed example
Using days past due: A is 10 days overdue, in the 1–30 bucket. B is current. Current: USD 200. 1–30 days: USD 100. Total open: USD 300.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Should aging use the original invoice amount after a partial payment?
Use the remaining open amount for receivables exposure, while retaining the original amount if needed for context.
Why is an invoice due today classified as overdue in one report?
The reports may use different boundary rules or time cutoffs. State whether zero days past due belongs in current.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑