Skip to main content

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, applied count, failed count, skipped count, and available row results. Together, these details provide the audit trail for account onboarding and later processing review. For Individual Offer Update files, the existing results download includes skipped rows with a Skipped: reason in the Errors column. Failed rows carry their validation errors in that same column. Each entry also retains the selected Bill Type, optional hardship classification, and whether the optional certification was accepted. If accepted, it records the uploader and acceptance time. The upload Bill Type is the fallback; individual accounts may use their sub-account type.

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 November 12, 2026