Real-World Example
ABC Collections needs a payment report for April. The creditor chooses the payment report, selects April 1 through April 30, and generates the report.
The report should include only ABC Collections payment records from that date range. It should not include May payments, another creditor’s payments, or records outside the selected filters.
Visual Flow
How It Should Work
- It should let the creditor choose a report type and filters.
- It should generate a report only from records the creditor can access.
- The exported information should match the selected report criteria.
- Report fields, totals, and date ranges should remain consistent with the related dashboard or export view.
- Reports may use dashboard, compliance, account, negotiation, payment, or communication data when supported by the selected report type.
- Large reports should be queued immediately, show a preparing notification, and download automatically when generation succeeds.
- Closing the page should not cancel generation; the completed file should remain available in Report History for 30 days.
How It Should Not Work
- It should not include data from another creditor.
- It should not ignore the selected filters.
- It should not create a report with missing or misleading totals.
- It should not mark a report complete before file generation succeeds.
Last modified on July 30, 2026
