43.1 Regulatory reporting, corrections and examiner updates

Reporting is a managed compliance process

The CRCM outline explicitly includes completing required regulatory reports, making timely submissions and resubmitting where required. It also includes coordinating ongoing reports to auditors and examiners, including enforcement and governance updates. These tasks require more than knowing that HMDA and CRA exist. A compliance manager needs a controlled process from source data to certification, transmission, acknowledgment and correction.

A reporting inventory identifies each report, authority, coverage conditions, recipient, frequency, deadline, responsible owner, data sources and review or certification requirements. Coverage can change with assets, activity, products or exemptions. Maintain the inventory through acquisitions and system changes rather than copying last year’s submissions without checking whether the bank remains in scope.

Annual, quarterly and event-driven requirements

HMDA’s annual LAR submission generally is due March 1 following the reporting year, with specific quarterly reporting for high-volume institutions. CRA data reporting has its own asset coverage and annual March 1 deadline. Do not assume every small bank reports CRA data or every HMDA reporter qualifies for every partial exemption. Determine scope for each obligation and preserve the basis.

Regulation Z Section 1026.58 requires covered card issuers to submit offered credit card agreements to the CFPB on a quarterly basis, with exceptions including the de minimis exception for issuers with fewer than 10,000 open accounts. Count under the rule rather than using the number of agreements or branches. Submission and public posting have related but distinct provisions, and consumers’ access to their own agreements requires separate controls.

Section 1026.57 has annual reporting concerning agreements with higher education institutions or affiliated organizations and relevant college credit card activity. It is not the same quarterly agreement-submission process. A bank with a college affinity program should evaluate that rule even when staff responsible for ordinary card agreements believe their inventory is complete.

Event-driven reporting can include service-company notices and security incident notices. Its clock begins from the defined event, not the next monthly reporting meeting. A calendar alone cannot catch such duties without an intake and escalation process.

Validate the population and fields

Before submission, reconcile the reporting population to source systems. Document inclusion and exclusion logic, identifiers, data transformations, review exceptions and final totals. An edit check that finds no formatting errors does not prove correct coverage or values. For example, a valid date field can contain the wrong action date, and a properly formatted loan amount can come from the wrong balance.

Assign reviewers who can challenge substantive classifications and source evidence. Check manual overrides and interface changes, not only automated outputs. Obtain the required certification or authorized submission approval. Preserve the version transmitted, receipt or acceptance evidence and any subsequent communications. A report uploaded to a system but rejected is not automatically a completed submission.

Corrections and resubmissions

When an error is discovered, determine its scope, governing correction standard and agency instructions. HMDA resubmission uses the applicable FFIEC process and field-level thresholds; not every exception requires recreating the entire LAR, and a threshold is not permission to leave a known material defect unexplained. Assess whether the issue affects other years, products or reports.

A corrected report should reconcile to the earlier submission and explain changes where required. Track agency acceptance and validate the underlying system fix. Updating a local spreadsheet without transmitting a required correction does not complete remediation. Conversely, changing the public data without preserving the original and correction evidence damages the audit trail.

Ongoing reports to examiners and auditors

A request or order can require periodic status reports, evidence of completed action, exception counts, restitution amounts and board updates. Read the actual requirement and coordinate inputs from responsible units. Validate claims such as completed, tested or refunded against records. Distinguish implementing a procedure from demonstrating effectiveness and issuing a refund from reconciling successful receipt or lawful disposition.

A useful update states the required action, current status, evidence, unresolved gaps, responsible owner, target date and any requested change. Escalate delays before the deadline and follow the authority’s process for extensions; an internal decision to defer is not an agency-approved extension. Maintain consistent facts across board reports, examiner responses and audit records.

Suppose HMDA review identifies wrong income coding after an annual submission, while an order requires monthly remediation updates. The bank should determine the correction scope, submit required revisions, repair the source logic and report accurate progress under the order. It cannot mark the matter closed merely because a draft corrected file exists. Objective testing and acceptance evidence address different parts of completion.

Regulation Z card agreement submissions and college card reporting are primary examples alongside HMDA and CRA. A good reporting program connects legal coverage, data integrity, submission evidence and ongoing regulatory communication.