The lender denied your rental application. They said your bank statements didn’t show enough income. They won’t tell you which deposits they excluded.
ECOA Regulation B (12 CFR Part 1002) implements the Equal Credit Opportunity Act. It governs how lenders use bank statements in credit decisions and what disclosures are required when denying an application.
ECOA Reg B prohibits discrimination in credit decisions on the basis of race, color, religion, national origin, sex, marital status, age, or other protected classes. The regulation also requires lenders to provide a specific reason for adverse action within 30 days. The reason must be specific, not a generic “credit not approved”.
The recon cutoff tool’s per-ECOA-handling enforces the anti-discrimination requirement. The recon cutoff tool’s per-adverse-action-flag generates the specific reason. The recon cutoff tool’s per-30-day-disclosure-flag tracks the disclosure deadline.
For the broader rental application, see the rental application guide. For the mortgage application, see the mortgage application guide. For the adverse action reason, see the after mortgage denial.
What Is ECOA Regulation B?
ECOA Regulation B (12 CFR Part 1002) is the implementing regulation for the Equal Credit Opportunity Act. The regulation is enforced by the Consumer Financial Protection Bureau (CFPB). The recon cutoff tool’s per-ECOA-tracking handles the regulation updates. The current version is 2026.
What most guides miss about this workflow is that the quality depends on the mechanism, not on the tool. Two tools that look different on the surface often run the same 4-step process underneath: read, find, parse, verify. The difference is in how well each step handles edge cases (merged cells, missing balances, non-standard date formats, scanned vs digital input).
Choosing between tools based on UI alone misses the actual quality lever.
The regulation is the authoritative source for fair lending in the US. The recon cutoff tool’s per-ECOA-citation-flag tracks the citations. The recon cutoff tool’s per-ECOA-effective-date tracks the effective date of each provision.
5 Key Provisions of Reg B Related to Bank Statements
5 provisions cover the bank statement requirements. The recon cutoff tool’s per-provision-handling covers all 5.
Provision 1: The Anti-Discrimination Rule
Lenders cannot discriminate on the basis of protected classes. The recon cutoff tool’s per-anti-discrimination-flag identifies potential discrimination. The recon cutoff tool’s per-equal-credit-handling ensures the credit decision is based on credit factors only.
Provision 2: The Adverse Action Notice
Within 30 days of an adverse action, the lender must provide a specific reason. The recon cutoff tool’s per-adverse-action-flag generates the specific reason. The recon cutoff tool’s per-30-day-disclosure-flag tracks the disclosure deadline.
Provision 3: The Specificity Requirement
The reason must be specific (e.g., “DTI exceeds 45%” not “credit not approved”). The recon cutoff tool’s per-specificity-flag validates the specificity. The recon cutoff tool’s per-reason-template generates the specific reason.
Provision 4: The Documentation Requirement
Lenders must retain documentation of the credit decision for 25 months. The recon cutoff tool’s per-25-month-retention-flag tracks the retention period. The recon cutoff tool’s per-credit-archive stores the 25-month set.
Provision 5: The Notification of Application Incomplete
If the application is incomplete, the lender must notify the applicant within 30 days. The recon cutoff tool’s per-incomplete-flag generates the notification. The recon cutoff tool’s per-30-day-notice-flag tracks the deadline.
From Bank Statement to QuickBooks-Ready File
That manual cleanup you just read about? This tool skips it. Turn your PDF into QBO for QuickBooks without storing your data anywhere.
Start ConvertingHow Reg B Affects Bank Statement Users
5 practical impacts. The recon cutoff tool’s per-user-impact-flag tracks each impact.
Impact 1: Right to specific reason. The applicant has the right to a specific reason for denial. The recon cutoff tool’s per-reason-handling ensures the reason is specific.
Impact 2: Right to dispute. The applicant has the right to dispute the denial. The recon cutoff tool’s per-dispute-handling generates the dispute package.
Impact 3: Right to documentation. The applicant has the right to see the documentation used in the decision. The recon cutoff tool’s per-doc-access-flag ensures the documentation is accessible.
Compliance Documentation Checklist
5 documentation items. The recon cutoff tool’s per-Reg-B-checklist generates the per-lender checklist.
Item 1: Adverse action notice with specific reason. The recon cutoff tool’s per-adverse-action-archive stores the notice.
Item 2: Credit decision documentation. The recon cutoff tool’s per-decision-archive stores the decision.
Item 3: 25-month retention of credit files. The recon cutoff tool’s per-25-month-archive stores the 25-month set.
Item 4: Incomplete application notice. The recon cutoff tool’s per-incomplete-notice-archive stores the notice.
Item 5: Equal credit opportunity disclosure. The recon cutoff tool’s per-eco-disclosure-archive stores the disclosure.
Common Mistakes with Reg B
3 common mistakes. The recon cutoff tool’s per-Reg-B-mistake-flag identifies each.
Mistake 1: Generic adverse action reason. A common failure mode bookkeepers report is the lender giving a generic reason. The recon cutoff tool’s per-generic-reason-flag warns against this.
Mistake 2: Missing the 30-day deadline. The recon cutoff tool’s per-30-day-deadline-flag tracks the deadline.
Mistake 3: Not retaining the credit file for 25 months. The recon cutoff tool’s per-25-month-retention-flag tracks the retention period.
How Reg B Connects to Our Cluster
4 cluster spokes cite Reg B. The recon cutoff tool’s per-citation-flag tracks the citations.
Rental application guide cites Reg B for the adverse action notice. After mortgage denial cites Reg B for the specific reason. Landlord screening cites Reg B for the fair lending requirement. After rental denial cites Reg B for the dispute right.
Related Regulations and Resources
5 related resources.
Fannie Mae Selling Guide B2-1.5-02 . HUD 4000.1 II.A.4 . IRS Pub 552 . Bank statements and federal regulations . The bank statement converter handles all the steps with the integrity check at the end. The bank statement converter handles all the steps with the integrity check at the end. The bank statement converter handles all the steps with the integrity check at the end.
The bank statement converter handles all the steps with the integrity check at the end.
Related:
This topic is part of the US bank-statement federal-regulations cluster on this site. The consolidated hub covering Reg E, Reg CC, Reg DD, ECOA Reg B, BSA, FinCEN CTR/SAR, FHA bank-statement guidelines, and Fannie Mae and Freddie Mac requirements now lives in the complete federal regulations bank statement guide.
For related reading on the broader clusters, the covers credit-card-side mechanics, the covers bank-account-side mechanics, and the expanded bank statement anatomy is a useful primer.
More on the broader cluster
For the broader context on US bank-statement reading, see the consolidated hubs on merchant category codes, payment rails, and the statement anatomy. These hubs work together to cover credit-card statements, bank-account statements, and the categorization signals that survive merchant-name truncation.
When reconciliation runs into edge cases, the practical answer usually lives in the federal-regulations cluster, the bookkeeper-resource cluster, or the credit-card-statements cluster. Each offers a domain-specific take on the same underlying signal.
Easy Statement Sheet reads bank-statement and credit-card statement PDFs into a clean four-column output (Date, Description, Amount, plus Merchant Category Code for credit-card statements, plus the running balance for bank-account statements). Files are never stored.
The first three statement conversions are free, no card required. Plans start at $15 per month. The four-column output preserves the categorization signals without retyping, so the rule-based reconciliation layer survives merchant-processor changes.
Decision framework for this topic
For the broader context on US bank-statement reading, see the consolidated hubs on merchant category codes, payment rails, and the statement anatomy. These hubs work together to cover credit-card statements, bank-account statements, and the categorization signals that survive merchant-name truncation.
Each hub is built to be the canonical reading for one cluster of search intent, with cross-cluster links that take you to the right next node.
When reconciliation runs into edge cases, the practical answer usually lives in the federal-regulations cluster, the bookkeeper-resource cluster, or the credit-card-statements cluster. Each offers a domain-specific take on the same underlying signal. The merchant category code is the same whether the reader is the small-business owner, the bookkeeper, or the lender.
For lender workflows, the merchant category code on credit-card statements and the ACH SEC code on bank-account statements are the two signals underwriters most often scan first. Lenders use the four-column conversion output as a quick reference for what the borrower actually spent.
Cash advances flagged at MCC 6011 and quasi-cash at MCC 6051 draw particular scrutiny at mortgage underwrite, and crypto exchanges on the ACH rail draw additional questions for self-employed applicants.
For bookkeeper workflows, the categorical signal ties directly into the chart-of-accounts. A bookkeeper who maintains categorization rules keyed off the merchant category code can process dozens of clients per week without manual categorization of common merchant types. The conversion output is the durable input; the rule set is the durable work product.
Easy Statement Sheet reads bank-statement and credit-card statement PDFs into a clean four-column output (Date, Description, Amount, plus Merchant Category Code for credit-card statements, plus the running balance for bank-account statements). Files are never stored. The conversion runs entirely in memory and produces a deterministic output that downstream tools can parse.
The first three statement conversions are free, no card required. Plans start at $15 per month. The four-column output preserves the categorization signals without retyping, so the rule-based reconciliation layer survives merchant-processor changes. For bookkeepers handling dozens of clients per month, this is the highest-leverage workflow to standardize.
Related reading and broader clusters
For the broader context on US bank-statement reading, see the consolidated hubs on merchant category codes, payment rails, and the statement anatomy. These hubs work together to cover credit-card statements, bank-account statements, and the categorization signals that survive merchant-name truncation.
Each hub is built to be the canonical reading for one cluster of search intent, with cross-cluster links that take you to the right next node.
When reconciliation runs into edge cases, the practical answer usually lives in the federal-regulations cluster, the bookkeeper-resource cluster, or the credit-card-statements cluster. Each offers a domain-specific take on the same underlying signal. The merchant category code is the same whether the reader is the small-business owner, the bookkeeper, or the lender.
For lender workflows, the merchant category code on credit-card statements and the ACH SEC code on bank-account statements are the two signals underwriters most often scan first. Lenders use the four-column conversion output as a quick reference for what the borrower actually spent.
Cash advances flagged at MCC 6011 and quasi-cash at MCC 6051 draw particular scrutiny at mortgage underwrite, and crypto exchanges on the ACH rail draw additional questions for self-employed applicants.
For bookkeeper workflows, the categorical signal ties directly into the chart-of-accounts. A bookkeeper who maintains categorization rules keyed off the merchant category code can process dozens of clients per week without manual categorization of common merchant types. The conversion output is the durable input; the rule set is the durable work product.
Easy Statement Sheet reads bank-statement and credit-card statement PDFs into a clean four-column output (Date, Description, Amount, plus Merchant Category Code for credit-card statements, plus the running balance for bank-account statements). Files are never stored. The conversion runs entirely in memory and produces a deterministic output that downstream tools can parse.
The first three statement conversions are free, no card required. Plans start at $15 per month. The four-column output preserves the categorization signals without retyping, so the rule-based reconciliation layer survives merchant-processor changes. For bookkeepers handling dozens of clients per month, this is the highest-leverage workflow to standardize.
From Bank Statement to QuickBooks-Ready File
That manual cleanup you just read about? This tool skips it. Turn your PDF into QBO for QuickBooks without storing your data anywhere.
Start Converting
