Back to Blog

[.green-span]Bank Statements vs Accounting Data for Underwriting: A Lender's Decision Guide[.green-span]

BY
Lendflow Research Team
•
November 16, 2026
Use bank data to verify cash and accounting data to explain timing. Reconcile the two and escalate the gaps you can't explain.
Strategy
Technology
Marketing

Bank statements vs accounting data for underwriting: the short answer

Bank statements prove what cash actually moved through a business account. Accounting data shows what the business booked as revenue, what it owes, and what customers owe it. When you weigh bank statements vs accounting data for underwriting, use both: bank data as the anchor, the books to explain timing.

That choice affects a lot of applications. The Fed Small Business Credit Survey reports: "Thirty-eight percent of firms applied for a loan, line of credit, or merchant cash advance in the prior 12 months, nearly unchanged from the 2024 survey." The survey covers small employer firms and relies on self-reported answers.

Cash flow underwriting means judging a borrower's ability to repay from the money moving in and out of its accounts. Bank and accounting data sit beside credit bureau files and other SMB underwriting data sources in a full credit review.

  • Bank statements show cash: Deposits, debits, and balances come straight from the bank.
  • Accounting data shows earnings: The books reveal margin, receivables, and debts the bank can't see yet.
  • Both together explain gaps: Matching the two shows whether reported revenue turns into real cash.

Verify cash and obligations with each data source

Each source answers a different question. Bank data comes from a third party, the bank, so the business didn't create it.

Accounting data is produced by the business or its bookkeeper. Its quality depends on how carefully the books are kept.

Bank statements prove cash movement

A bank statement lists settled deposits, debits, and daily balances for each month. Underwriters scan it for NSFs (non-sufficient funds events, when a payment bounces because the account is short). They also look for recurring debits like payroll, rent, and daily or weekly payments to other funders.

The limit is that a deposit is just a deposit. A statement can't tell a customer payment from a transfer between the owner's accounts, a loan, or new capital from the owner. Bank data belongs to the wider group of non-bureau inputs covered in our guide to bureau vs. alternative data.

Format matters too. A PDF statement is a static file that can be edited before upload. Connected bank data is pulled through an API (a secure link between two systems) from the bank, usually via a data aggregator.

  • PDF statements: Easy to request, but they freeze at the last statement date.
  • Connected bank data: Pulled at the source, and you can refresh it before funding.

Accounting data proves booked revenue, receivables, and payables

Accounting data usually means three reports. The P&L (profit and loss statement) shows revenue minus expenses over a period, and the balance sheet shows assets, debts, and equity. Aging reports sort AR (accounts receivable, money customers owe) and AP (accounts payable, money the business owes) by how overdue each item is.

These reports show margin and obligations that may not reach the bank for weeks. They are only as good as the bookkeeping, though. Books can run months behind, skip bank reconciliation, or mix personal and business spending.

Accounting method changes what the numbers mean. The cash method records income when money arrives, while the accrual method records it when it's earned. IRS Publication 538 states: "Most individuals and many small businesses (as explained under Excluded Entities and Exceptions, later) use the cash method of accounting."

For a cash-basis business, you can usually expect booked revenue and deposits to track closely. For an accrual-basis business, they can drift apart by weeks or months.

Compare bank statements vs accounting data side by side

This table rates each source on six factors a credit team cares about. The ratings are general guidance based on how each source is produced and delivered.

Data sourceWhat it verifiesRefresh frequencyManipulation riskBorrower frictionBest use
Bank statement PDFsDeposits, debits, balances, and NSFs for the months providedStatic; current only to the last statement dateHigher; files can be edited before uploadMedium; borrower must find and upload filesSmall, fast decisions when a connection isn't possible
Connected bank dataThe same transactions, pulled from the bank through an aggregatorOn demand; can refresh before funding and during the loanLower; data comes from the sourceLow; one login and consent stepDefault anchor for cash flow underwriting and monitoring
Accounting exportsBooked revenue, margins, receivables, and payablesStatic; current only to the last closeMedium; the business prepares the reportsMedium to high; may need a bookkeeperLarger or longer loans that need a view of profit and debts
Connected accounting dataThe same ledger data, pulled from the accounting platformOn demand; as current as the booksMedium; the pull is direct, but entries are self-reportedLow; one login and consent stepReceivables-based lines and ongoing financial checks

Any PDF statement can be altered before upload—train reviewers to detect fake bank statements and move borrowers to connected data where you can.

Fund short-term deals faster when bank statements are enough

Bank data has research behind it. The FinRegLab cash-flow underwriting study reports: "We find that incorporating the cash-flow data leads to statistically significant improvements in classification performance across all borrower segments, with a 0.011 improvement in AUC in the overall sample."

AUC is a score from 0.5 to 1 that measures how well a model separates loans that repay from loans that default. The study used about 38,000 approved loans from two US fintech lenders, roughly 2015 to 2024. Adding bank data to a credit-score model moved AUC from 0.652 to 0.663, a modest gain overall.

The gain was larger for thin-file borrowers. For young firms with low-score owners, AUC rose 0.023 points.

The study tested bank data on top of credit scores, and it did not compare bank data with accounting data. The lenders had minimum FICO cutoffs of 600 and 660, and the study was funded by the US Department of Commerce MBDA, Visa, and Plaid.

Bank statements alone often cover the risk in these cases:

  • Short terms: Loans repaid within months depend on near-term cash, which bank data shows directly.
  • Small tickets: Lower exposure rarely justifies the friction of collecting full financials.
  • Daily or weekly remittance: An MCA (merchant cash advance) is repaid from future sales, so steady deposits matter most.
  • Cash-basis businesses: When the books follow cash timing, deposits usually land close to booked revenue.
  • Speed-sensitive offers: Connected bank data can support a decision in a single session.

For MCA underwriting, automation does much of the scanning. Compare bank statement analysis tools that flag NSFs, other funders' debits, and balance dips.

Size larger and longer loans with accounting data

Require accounting data when the risk depends on what bank data can't show. That includes profit, unpaid invoices, and debts that haven't been debited yet.

  • Larger or longer loans: Multi-year terms need proof of margin as well as deposit volume.
  • Receivables-based lines: AR aging shows which invoices support the line and how old they are.
  • Accrual or inventory businesses: Revenue and cash can sit months apart when firms bill on terms or carry stock.
  • Debt visibility: The balance sheet and AP aging reveal obligations that don't appear as bank debits yet.
  • Fast growth or lumpy contracts: A few large contracts can make three months of deposits look misleadingly weak or strong.

Lines of credit lean hardest on this data. Our guide to line of credit underwriting covers how lenders size and review revolving credit.

Match data requirements to each product

Each product carries a different risk, so each needs a different data package. The table below is a Lendflow-suggested starting point, not an industry norm, so tune it against your own loss data and credit policy.

ProductSuggested minimum data at applicationSuggested add-ons when risk risesSuggested monitoring cadence
Term loan3 to 6 months of connected bank data plus a credit bureau pullP&L, balance sheet, and tax return for larger or longer termsRefresh bank data before funding; review financials each year
Line of creditConnected bank data plus a recent P&L and AR aging reportBalance sheet, AP aging, and connected accounting dataRefresh bank data and AR aging monthly or at each draw
MCA3 to 4 months of bank data, ideally connectedCard processor statements and a check for other open advancesReview deposits and remittances daily or weekly

Catch mismatches early by reconciling deposits and reported revenue

P&L revenue and bank deposits rarely match, and that's normal. The goal is to explain the gap, then escalate only what you can't explain.

Why deposits and revenue differ

Most gaps come from a short list of causes. Knowing them speeds up every file review.

  • Timing: Accrual books record a sale when it's invoiced, and the cash lands later.
  • Change in receivables: If AR grew, revenue runs ahead of deposits; if AR shrank, deposits run ahead.
  • Transfers: Money moved between the owner's own accounts inflates deposits.
  • Loan and advance proceeds: Funding from other lenders lands as deposits and never counts as revenue.
  • Owner contributions: Capital the owner adds looks like income on a statement.
  • Refunds and chargebacks: Returns reduce cash, and the books may log them in a different month.
  • Sales tax: Collected tax hits the account, yet the business owes it to the state.
  • Processor fees: Card processors often deposit sales net of fees, while the books record gross sales.

Reconciliation checklist for underwriters

Work through these steps in order for every file that includes both sources.

  1. Pull bank data and the P&L for the same period.
  2. Confirm whether the books use the cash or accrual method.
  3. Remove transfers between the business's own accounts.
  4. Remove loan proceeds, MCA advances, and owner contributions.
  5. Remove refunds, reversals, and returned deposits.
  6. Add back processor fees if the books record gross sales.
  7. Remove collected sales tax if the books record revenue net of tax.
  8. Adjust for the change in receivables over the period.
  9. Compare adjusted deposits with reported revenue and record the gap.
  10. Escalate any gap outside your policy band for manual review.

Here's how that works on a hypothetical accrual-basis business with $300,000 in quarterly P&L revenue. It shows $310,000 in deposits, including a $25,000 owner transfer and $40,000 in loan proceeds.

StepAmount
Total deposits$310,000
Remove owner transfer and loan proceeds−$65,000
Add back processor fees+$9,000
Remove sales tax collected−$12,000
Add increase in receivables+$50,000
Expected revenue$292,000
Reported P&L revenue$300,000
Unexplained gap$8,000 (about 2.7%)

Set a tolerance band and escalation triggers

Write a tolerance band into your credit policy and test it against your own loss history. Gaps inside the band can move forward without extra review.

  • Gap outside the band: Ask for the general ledger or AR detail before deciding.
  • Gap growing month over month: Treat a widening gap as a trend worth a full review.
  • Revenue far ahead of deposits: Escalate when no rise in receivables explains the difference.

Decide faster with both sources in one workflow

According to Lendflow, customers on Lendflow's platform see these results from a connected data workflow:

  • $1.5B+ in offers: Made on the platform in the prior 12 months (as of March 2025).
  • 42% faster speed to funding: The average for pre-qualified offers hosted on Lendflow.
  • 80% smaller teams: Lendflow embedded finance customers convert similar funding volumes with leaner teams.

The workflow follows one rule: bank data is the anchor, and accounting data is the explainer. Manual uploads stall reviews—connect bank and accounting platforms through APIs so data arrives ready to analyze. Lendflow says its Data Orchestration lets lenders connect with top integration partners in minutes.

Some borrowers will still send PDFs. Retyping statements slows every file—use Lendflow Doc Analyzer to automate document analysis and pull transactions into your review.

Next, route each deal by product. A decision waterfall is an ordered set of rules or capital partners, and a declined deal moves to the next option. Lendflow's credit underwriting and decisioning tools help you build waterfalls so no deal leaves money on the table.

Finally, refresh connected data before funding and on your monitoring schedule. Stale files hide new debts—pull live data so decisions reflect the borrower's current position.

Bank-data connections also carry a regulatory note. Privacy Law Network's 1033 rule status report says "on October 29, 2025 the Eastern District of Kentucky enjoined the CFPB from enforcing it until the Bureau completes its reconsideration." In August 2026, the CFPB sent a revised proposal to the White House for review, and Consumer Finance Monitor notes that this step is "generally one of the final steps before the proposal is published in the Federal Register for public comment." FinRegLab's 2025 study notes the 2024 rule wouldn't apply to business checking or transaction accounts, so check the current status before you build on it.

FAQ about bank statement and accounting data underwriting

These answers cover the questions credit teams ask most often. Each one points back to a section above for more detail.

Bank statements vs accounting data for underwriting: which is better?

Neither source replaces the other, so a sound approach is to anchor on bank data and add accounting data as loan size, term, or complexity grows.

Why is P&L revenue higher than bank deposits?

The usual cause is accrual timing, where the business booked sales it hasn't collected yet and receivables grew. Processor fees netted from deposits and refunds can widen the gap.

Which deposits should lenders exclude from revenue?

Exclude transfers between the business's own accounts, loan and MCA proceeds, owner contributions, and reversed or returned deposits. Also remove collected sales tax if the books report revenue net of tax.

How many months of bank statements do lenders need?

According to the FinRegLab cash-flow study cited above, three months is common practice among fintech lenders, which rarely pull more than six. Consider six to twelve months for larger loans or seasonal businesses.

What are red flags on a bank statement?

Watch for frequent NSFs, low or negative daily balances, and daily or weekly debits to other funders. Also flag large round-number deposits with no clear source and totals that don't add up.

Build a connected underwriting workflow with Lendflow

You don't have to choose between bank statements and accounting data. Book a demo or talk to our team to see how Lendflow connects both sources and routes every deal through one decision workflow.