Dealership Adverse Action Notice Issuance Log

This log records when an adverse action notice was issued for a declined or conditionally approved credit applicant. It helps the dealership document the decision, the notice delivery method, and whether required disclosure language was included. The result is a clearer audit trail for ECOA and FCRA review.

It is typically completed by the finance office, compliance staff, or another employee responsible for credit decision follow-up. The person entering the record should have access to the application reference, decision outcome, and notice delivery details. A reviewer can then verify the entry for accuracy and completeness.

Update it each time an adverse action notice is issued, ideally on the same day the notice is sent. If a notice is delayed or an exception occurs, record that immediately so the audit trail stays intact. This template is designed for per-application tracking rather than periodic batch reporting.

No. This is a tracking log, not the notice itself. It documents that the notice was issued and what content or delivery checks were completed, but it does not generate the legal notice language. You should still use your approved notice template and retain it where required.

At minimum, capture the decision date, outcome, notice issue date, delivery method, reason codes, and whether the credit reporting agency disclosure was included. If your process uses an exception or delay, document why and who reviewed it. Keep the entries focused on what was actually used for the adverse action process.

Yes. You can add fields for store location, lender program, or internal queue status if those details help your workflow. Keep any added fields aligned with data minimization so you do not collect PII that is not needed for the log. Conditional logic can hide optional fields until a delay or exception is selected.

Common issues include leaving out the delivery confirmation, using free-text instead of reason codes, and failing to record who reviewed the entry. Another frequent problem is mixing the log with the actual notice content, which makes the record harder to audit. The template works best when each field has one clear purpose.

Yes. It can be connected to CRM, loan origination, or document management tools through application reference numbers and retention location fields. That makes it easier to link the log to the underlying application file and the stored notice. If you integrate it, preserve the audit trail for edits and approvals.

An ad hoc spreadsheet often misses required details, uses inconsistent reason descriptions, and makes review harder. This template organizes the record around the decision, issuance, content check, and follow-up steps so the process is repeatable. It is easier to standardize across staff and easier to audit later.