Most lenders reviewing a term sheet expect accrual-based statements, because accrual accounting matches revenue to the work performed and gives credit teams a basis for comparing periods. Cash accounting versus accrual accounting is therefore less a bookkeeping preference than a readiness question: what a lender can underwrite depends on which method your numbers can support, and on how well you can explain the distance between the two.

What lenders read into each method

A credit team treats your accounting method as an early signal about how the business is managed. Cash statements show when money actually moved, which is why owners like them for taxes and day-to-day survival. Accrual statements show what the business earned and owed during the period, Cfo Services which is what underwriters use to compare one quarter against another. The method itself is not a verdict. The questions start when the two views disagree and nobody can explain why.

Under the cash method, revenue is recorded when payment lands and expenses when they are paid. It is simple, it matches how many small businesses file with the IRS, and the agency permits it under gross receipts tests, so plenty of companies run this way. For a lender, its weakness is timing: a strong collection month can look like growth, and a delayed payment can make a healthy month look weak.

The accrual method records revenue when it is earned and expenses when they are incurred, whatever the cash timing. For contract revenue, the guidance in ASC 606 governs when recognition happens, which matters once you bill by milestone, retainer, or subscription. Because periods line up, a lender can read margins, seasonality, and growth from the statements instead of reconstructing them from bank feeds.

The comparison a lender runs is less about right and wrong than about what each view answers. This is roughly how the two line up in a credit review:

What a credit review asksCash statements sayAccrual statements say

When revenue countsWhen cash is receivedWhen it is earned When expenses countWhen bills are paidWhen they are incurred Comparability across periodsWeak, driven by payment timingStrong, periods align Most useful forLiquidity, tax filing, collectionsUnderwriting, covenants, diligence Where it can misleadCollection timing hides performanceCash shortages stay invisible

Neither method is misleading on its own. The friction appears when a business files taxes on a cash basis, reports internally on accrual, and sends a lender whichever version was easiest to print. Underwriting then compares documents that were never designed to agree, and the borrower spends the negotiation explaining bookkeeping instead of the business.

There are real exceptions. Asset-based lenders care mostly about collateral and collections, so aging reports can matter more to them than the method itself. A small line of credit may never require accrual statements. Ask any lender early what reporting their credit agreement will require, because that answer sets the routine that follows.

Run a monthly close that produces both views

Build one set of books and derive the second view from it, in the same order every month. Flipping between two parallel systems is how numbers drift apart. The routine below assumes bookkeeping on a cash or modified basis for tax, with the accrual view produced as a monthly adjustment layer; some teams run it the other way around, and the order of the work barely changes.

Reconcile every bank, credit card, and loan account. Post all vendor bills received, paid or not. Invoice everything delivered during the month. Record revenue recognition entries for contracts. Run the accrual conversion entries as a saved journal group. Print both versions of the statements plus the bridge. Review variances with whoever owns the numbers before anything goes out.

Reconciliation comes first because everything after it inherits errors from it. A bank feed that misses a wire transfer at month end quietly corrupts both views. Payroll entries and payroll tax liabilities belong in this early pass too, since they are where timing gaps start. Weekly reconciliation is worth the habit once a single lost transaction could change a decision; monthly is the floor.

Pick a close date and defend it. Teams that close by a fixed target date each month produce a full year of consistent periods, and consistency is what makes trends readable. A close that slides by two weeks defeats its own purpose, because a lender will eventually ask for interim statements, and you do not want to be reporting from statements that are still warm.

Division of labor matters more than headcount. One person can run this routine if a second set of eyes reviews the journal entries, even an outside accountant working a few hours a month. The pattern a credit team looks for is not a large finance department; it is evidence that someone checked the work, month after month, on a schedule.

Keep the close checklist itself. A written checklist, dated and initialed each month, turns the close from a memory exercise into a process. When diligence later asks how your numbers were produced, that stack of completed checklists answers the question better than any narrative can.

Fix revenue recognition before converting anything

Most of the gap between the two views comes from timing, so fix recognition patterns before you touch method changes or restatements. If revenue lands in the wrong month, converting the method just makes the wrong month official. Recognition is also where a credit review pushes hardest, because it is the area where results can be moved by choice.

Two balances do most of the damage. Deferred revenue is money collected before the work is done, common with subscriptions, retainers, and prepaid contracts; under accrual it sits as a liability until earned. Unbilled revenue is work already performed that has not been invoiced yet, common with milestone billing and reimbursable project costs. Cash statements show neither, which is exactly why lenders ask about both.

Cut-off is the third lever: which period an invoice or a cost belongs to. A service delivered in December and invoiced in January belongs to December under accrual, whatever the cash did. Review cut-off around every period end, and pay extra attention at year end, where the tax filing and the accrual view will otherwise disagree on principle.

For contract revenue, ASC 606 gives the framework worth naming: identify the contract, identify the performance obligations, determine the price, allocate it across obligations, and recognize revenue as each one is satisfied. Most growing businesses do not need the full machinery of a public company. They need a written policy for each revenue type, applied the same way every month.

The cadence that works is a monthly review of the two balances against the contracts that drive them, and a quarterly walk through any contract that spans more than one period. Ask one question each time: does the balance still reflect reality, or has the project moved while the books stood still?

Scale the effort to the business. A retailer selling through card payments has little recognition risk, because delivery and payment are nearly simultaneous. A cfo services firm billing in arrears, a contractor working to milestones, or a software company collecting annual prepayments lives or dies on this discipline. The routine should be heaviest exactly where revenue timing is most negotiable.

Keep a bridge schedule that reconciles the two views

The bridge schedule is the one document that makes cash and accrual coexist in a lender's mind. It starts from accrual net income, removes non-cash items, and walks through the changes in receivables, payables, inventory, prepaid expenses, and deferred revenue, ending at operating cash. Produced monthly from actuals, it answers the question every credit team eventually asks: where did the cash go?

Lenders trust earnings that convert into cash, and distrust earnings that pile up in receivables. The bridge is where that pattern becomes visible. When accrual income rises quarter after quarter while operating cash stays flat, the schedule shows the receivables line absorbing the difference, and the conversation moves to collections. That is a better conversation than defending the income.

Build it from the balance sheet, not from memory. Each line is simply the change in a balance from one period to the next: receivables grew, so cash went down; payables grew, so cash went up. Because it is arithmetic on balances you already track, the bridge costs little to maintain once the close is stable, and it is one of the first exhibits a quality of earnings review will request.

Run it quarterly while no transaction is in view, and monthly once a financing or a sale becomes plausible. The quarterly rhythm catches drift while it is still small. The monthly rhythm, in the period before a lender sees anything, is a rehearsal: you find the awkward lines in private instead of in a data room.

Tie the bridge to the statements or do not send it. A bridge that roughly reconciles is worse than none, because it invites the question of what else is approximate. If the two documents refuse to tie, the discrepancy itself is the finding; investigate it before anyone external does.

The same schedule serves a sale process later. A buyer's diligence team uses the identical walk to test earnings quality, so the discipline is not wasted if you borrow this year and sell in a few years. One document, two audiences, same monthly routine, which is the reason to build it well the first time.

Wrap the statements in a forecast and a budget

Historical statements tell a lender what happened; the credit decision leans on what happens next. A routine that pairs the two is what makes accrual statements underwriting-ready: an annual budget approved before the year starts, a reforecast every quarter, and a cash forecast run weekly. The statements are the evidence, the forecast is the argument.

The 13-week cash forecast is the working tool. Thirteen weeks is long enough to see a shortfall coming and short enough that the estimates stay honest. Update it weekly from actual receipts and disbursements, not from a formula, and keep a column comparing last week's forecast with what actually landed. That comparison is how the forecast stays credible when a lender tests it.

Build the forecast in versions rather than as a single line:

Base case: current behavior and current collection patterns. Soft case: collections slow and new business softens. Hard case: a major customer leaves or a facility is drawn early.

Lenders tend to respect a borrower who shows the downside unprompted, because it signals that management has looked at it rather than hoped past it.

Working capital belongs in the same package. Watch whether receivable days are drifting, whether inventory turns are slowing, and whether payables are being stretched to cover a gap. No single reading is damning; the direction across quarters is what a covenant or a credit review will eventually measure. The monthly close should surface these balances in the same packet every time.

Refresh on a fixed calendar. The budget is annual, reforecasts are quarterly, the cash forecast is weekly, and the variance review is monthly: budget against actual, forecast against actual, and a short written note on anything that moved. The note matters more than the spreadsheet, because it shows the business understands its own numbers rather than merely producing them.

Limits deserve a sentence. A forecast does not predict, and a lender knows that; what it demonstrates is a mechanism for noticing deviation early. If the business cannot yet support a full forecast, start with the weekly cash view alone and add the rest as the close stabilizes.

Document the controls a diligence team will test

Statements persuade when a reader believes the process behind them, and process is something you can document. The close checklist, the journal entry log with support attached, the payment approval rule, the reconciliation sign-offs: these are the artifacts a diligence team samples and tests. Controls that exist only in someone's head do not survive contact with a credit committee.

Segregation of duties is the awkward one in a small team, and the workarounds are known. Whoever initiates payments should not be the only one approving them; whoever prepares a reconciliation should not be the only one reviewing it. Where headcount makes that impossible, an outside accountant or a fractional finance lead can hold the review role for a few hours a month.

Keep a journal entry log as a habit, not a scramble. Every adjusting entry gets a sentence of explanation, a document behind it, and an approval. A rush of tidy entries assembled in the final month is a weak story; entries assembled in the ordinary course, month after month, cfo services are a strong one.

Audit readiness is a spectrum, and lenders sit at different points on it. A bank credit team may be satisfied with reviewed or even compiled statements plus a conversion schedule; a private credit fund or a buyer may ask for audited statements or a quality of earnings report. Ask what the specific lender expects before commissioning any level of assurance, because the wrong level is expensive in both directions.

Test your own controls in a slow quarter. Pull a handful of journal entries, a few payments, and one reconciliation at random, then check that the support is attached and the approvals exist. Internal sampling finds the gaps while they are still cheap to fix, and it rehearses exactly what diligence will do later.

Refresh the documentation when people change. A control described with a former employee's name is a control that no longer exists. The review that belongs on the calendar is annual: walk the checklist, the approval rules, and the access rights in the accounting system, and update anything reality has outgrown.

Time any method change against the transaction calendar

Sequence beats speed here. The further a financing or a sale sits on the horizon, the cheaper it is to fix the accounting; the closer it gets, the more any change looks like interference. The cash accounting versus accrual accounting decision is partly a calendar decision, and the stages below tolerate different amounts of change.

Positioning, roughly a year or more out, is where a conversion belongs. Move the bookkeeping, set the revenue policy, build the bridge history, and let several clean accrual periods accumulate. If the tax method also changes, involve a CPA early: an accounting method change runs through IRS procedures, commonly a Form 3115 filing, and the tax and reporting calendars need to agree.

Negotiation, once a lender or buyer is engaged, is the wrong time to change anything material. Comparability is the currency of this stage; a borrower who switches methods mid-negotiation hands the other side a reason to re-run their analysis and reopen settled questions. Changes here should be presentation only: cleaner schedules, better exhibits, clearer notes.

Closing has its own reporting rhythm. The credit agreement will set post-closing requirements: monthly or quarterly statements, covenant certificates, sometimes an annual review or audit. Read those requirements before signing, because the routine you built should produce them without heroics. A covenant certificate is a poor place to discover your close runs late every month.

If the timeline forces an imperfect hand, bridge it in writing rather than improvising. A lender can work with a borrower who says: our history is cash basis, here is the conversion schedule for the trailing periods, and here is the accrual close going forward. What is hard to work with is a package whose numbers change shape between meetings.

The caution is worth stating plainly. Better accounting improves the quality of what a lender can evaluate; it does not by itself produce an approval. Deals turn on cash flow, collateral, market conditions, and terms. What this routine buys you is fewer avoidable questions, which is the part of a transaction you can actually control.

A worked example: a staffing firm building a credit package

A hypothetical example shows the routine compressed. Picture a staffing firm with annual accrual revenue of $8.0 million, filing taxes on a cash basis, preparing to approach a bank for a working capital line. Payroll runs weekly, clients pay in 45 to 60 days, and reimbursable expenses are invoiced in batches. The numbers that follow are invented for illustration, but the pattern is common.

The monthly close produced both views. Accrual net income for the year came to $640,000; the cash statement showed something noticeably thinner. The bridge schedule explained the difference: receivables grew by $400,000 over the year, prepaid software and insurance absorbed $40,000, depreciation added back $80,000, payables contributed $60,000, and deferred fees added $20,000. Operating cash worked out to $360,000.

Read together, the story was respectable: the firm earned well and financed its own growth in receivables. Read as cash alone, the same year looked stagnant. That is the gap a lender would have tripped over, and the bridge closed it before anyone had to guess. The first fix was operational, not accounting: invoice each timesheet batch on delivery instead of at month end, and review the aging weekly.

The firm then staged the package. Positioning meant several months of dual-view closes, a written revenue policy for contract staffing and fee income, and the 13-week cash forecast updated every Monday. Negotiation meant no method changes, only cleaner exhibits. Closing meant checking the credit agreement's monthly reporting requirements against the close calendar before signature, and reading the covenant definitions against the accrual policy.

The questions from the credit team were predictable, because the documents had already answered most of them: collectability of the largest clients, seasonality of placements, and what happens to collections if one client slows payment. Each answer pointed to an existing schedule. That is the practical payoff of the routine, and its honest limit: preparation shapes the conversation, it does not decide the outcome.