Real-World Example
ABC Collections uploaded a consumer file yesterday. Today, an employee wants to confirm whether all consumers were imported successfully.
Import History should show the uploaded file, when it was processed, whether it completed, and whether any rows failed. If rows failed, the creditor should be able to understand that the import was not fully clean.
Visual Flow
Audit Details
Each history entry should retain the import date and time, filename, source, processing status, total record count, successful count, failed count, and available validation errors. Together, these details provide the audit trail for account onboarding and later processing review.
How It Should Work
- It should show previous uploads and their processing status.
- It should help the creditor understand whether an import succeeded, failed, or partially completed.
- It should provide access to error details when available.
- It should keep counts and error files connected to the exact import batch that produced them.
How It Should Not Work
- It should not show import files from another creditor.
- It should not hide failed imports.
- It should not mark an import complete before background processing is finished.
- It should not replace an older batch’s audit details with results from a later import.
Last modified on July 30, 2026
