A financial controller checks whether the records behind a loan request are complete, consistent, and supported; a CFO weighs whether the borrowing fits the company’s plans and cash capacity. What does a financial controller do before a loan? They help make the financial picture reliable enough for the lender and management to discuss terms without treating a clean set of books as proof that the debt is affordable.
Which loan records should a controller check first?
A controller starts with the records that show what the business owns, owes, earns, and spends. That usually means reviewing the general ledger, recent financial statements, bank activity, accounts receivable and payable, payroll records, and existing debt documents. The exact set depends on the lender’s request and how the company keeps its books.
The first test is whether the statements reconcile to the underlying records. Cash balances should agree with bank statements, outstanding customer invoices should match the receivables ledger, and debt balances should be supported by loan statements or agreements. A difference does not automatically mean the business has a problem, but it needs a clear explanation before anyone relies on the figures.
Next, the controller looks for gaps in timing or classification. A large payment recorded in the wrong period can make one month look stronger and another weaker. An owner expense posted as a business cost, or a business charge recorded outside the books, can also distort the picture. The controller identifies the issue, checks its source, and documents the adjustment rather than quietly changing a number.
Management should be able to trace a reported balance back to a source document and understand who prepared or reviewed it. That trail matters when a lender asks how a figure was calculated. It also helps the company spot routine weaknesses, such as invoices entered late or payments recorded only when someone has time to update the system.
A clean reconciliation is a starting point, not a loan recommendation. The controller can make the records more dependable and explain their limits. Management still has to decide whether the proposed borrowing serves a real business need and whether the expected cash available for repayment can withstand ordinary changes in sales, costs, or collection timing.
How is a controller’s review different from bookkeeping or a CFO’s work?
A controller oversees the quality and consistency of financial records, while bookkeeping records transactions and maintains the books. A CFO uses financial information to guide decisions about capital, growth, risk, and strategy. In a small company, one person may cover parts of more than one role, but the work remains distinct.
Bookkeeping is the operational foundation. It includes entering bills and receipts, matching transactions, maintaining customer and vendor records, and keeping routine accounts current. Those tasks can be handled by an in-house bookkeeper or an outsourced accounting provider. The company still needs a clear process for reviewing the work and resolving exceptions.
Controller work adds oversight and financial reporting discipline. The controller checks reconciliations, establishes close procedures, reviews account balances, and helps ensure that statements are prepared consistently. Before a loan discussion, that work can reveal whether reported earnings include unusual items, whether liabilities are missing from the books, or whether the company’s cash balance is affected by funds set aside for another purpose.
A CFO looks beyond whether the reports are reliable. The CFO asks how much financing the company needs, what it will fund, how repayment fits the forecast, and how the loan affects other plans. A Cfo Virtual services may compare debt with equity or internal cash, prepare a financing narrative, and discuss the implications of covenants or collateral with management and advisers.
The dividing line is useful when a company already has a finance team. A controller can coordinate daily accounting and strengthen reporting, while a fractional or interim CFO can help management make higher-level financing decisions. Neither role replaces legal or tax advice, and a company should be clear about who owns each deliverable rather than assuming every finance professional handles every task.
How does a controller work with an existing finance team?
A controller works best when responsibilities are explicit. An internal bookkeeper may enter transactions, an outsourced accounting firm may prepare monthly statements, and a controller may review reconciliations and close results. The arrangement can vary, but each task should have an owner, a reviewer, and a way to resolve questions before a lender receives the information.
The controller can begin by mapping how information moves through the company. Who approves spending? Who enters bills? Who checks bank activity? Who confirms that invoices are collectible? These questions are practical, not bureaucratic. If the same person initiates and approves a transaction without review, management may need a compensating check that fits the company’s size and systems.
Coordination also means agreeing on a reporting calendar. A loan process can bring requests for updated statements, debt schedules, customer balances, or explanations of large transactions. If the accounting provider closes the books on one schedule and management expects reports on another, the controller can identify the dependency and set realistic handoffs before deadlines create pressure.
Existing staff should not have to guess whether a number is final. The controller can label draft reports, document later adjustments, and keep a record of open items. When a lender asks for a revised statement, that history helps the team explain what changed and why, instead of sending several versions with no clear account of the differences.
The right level of oversight depends on the company’s volume, complexity, and finance capacity. A small operation may need help with reconciliations and a disciplined close. A business with multiple entities, inventory, or more involved revenue arrangements may need stronger review and reporting controls. The controller should adapt the process to the actual risks rather than impose a large-company system that nobody can maintain.
What should the cash forecast tell you before borrowing?
A useful cash forecast shows when money is expected to arrive and when obligations must be paid. It turns the loan question from "Can the company qualify?" into "Can the company use and repay this financing under plausible conditions?" A controller can prepare and maintain the forecast, while management and a CFO decide what the scenarios mean for the financing choice.
The forecast should reflect collection timing, payroll, vendor payments, taxes, existing debt service, and planned spending. Revenue recorded in the accounts is not the same as cash in the bank. If customers pay later than expected, the business may face a short-term squeeze even when its income statement shows sales and a positive margin.
It should also distinguish regular operating cash from one-time events. A major customer payment, asset sale, or owner contribution may improve the balance temporarily without changing the company’s normal ability to cover debt payments. The controller can make those items visible and document the assumptions, so decision-makers do not mistake a temporary cash increase for recurring capacity.
Management should test what happens when assumptions move. What if a customer pays late, a planned project costs more, or sales take longer to convert into cash? The goal is not to predict every event. It is to see which assumptions matter most, how much flexibility remains, and whether the repayment plan depends on conditions the company cannot control.
Forecast quality has limits. A new product, seasonal operation, concentrated customer base, or volatile cost structure can make past patterns less useful. The controller should identify where the forecast relies on estimates and update it when actual results differ. A polished spreadsheet cannot remove uncertainty, but a transparent forecast lets management see it before taking on an obligation.
How can investor reporting and debt preparation connect?
Investor reporting and loan preparation draw on many of the same underlying records, but they answer different questions. Investors may focus on growth, use of capital, and progress against a plan. A lender will also examine repayment capacity, existing obligations, collateral, and the terms that could restrict future choices.
A controller can help make recurring reports consistent across audiences. Revenue definitions, expense categories, cash balances, and business-unit results should not shift without explanation from one report to another. If management uses a measure that is not directly visible in the accounting statements, the calculation and its relationship to the books should be clear.
That consistency matters when the company is raising equity while considering a loan. The financing options may compete for the same future cash or affect ownership and control in different ways. A controller can provide reliable historical information and current reporting; a CFO can compare the capital structure implications and help management frame the decision.
Debt documents also create information duties after closing. A lender may require periodic statements, compliance certificates, or notice of specified events. The company should understand which reports are due, who prepares them, and how the relevant figures are calculated. The controller can organize the reporting process, but legal or financial advisers should clarify the meaning and consequences of contract terms.
Look past the headline rate. Fees, repayment schedule, collateral, guarantees, covenants, and restrictions can change the practical cost and flexibility of a loan. The controller helps establish the financial facts used in that review; the CFO and management weigh the terms against cash needs and plans. A favorable-looking rate does not settle whether the agreement fits.
When should a company add controller support before a loan?
Controller support is especially useful when management cannot explain how key balances tie to source records or when monthly reports arrive too late to guide decisions. Other warning signs include unreconciled accounts, recurring adjustments after statements are issued, unclear responsibility for bookkeeping, and difficulty producing a current list of receivables, payables, and debt.
A company with an existing accounting team may need targeted oversight rather than a new full-time executive. A controller can review the close process, establish a schedule for reconciliations, clarify review responsibilities, and prepare lender-ready schedules from the accounting records. The scope should say what the controller will produce and what remains with management or the outsourced provider.
For a business facing a more strategic choice, controller work alone may not answer the central question. If the company is weighing debt against equity, planning a major expansion, or considering a sale, it may also need CFO-level analysis. That support can connect the forecast, capital needs, investor reporting, and transaction considerations without confusing decision-making with routine bookkeeping.
Fit depends on the company’s stage, sector, systems, and immediate need. A business with straightforward transactions may need reliable reconciliations and a forecast. A company with multiple entities, complex contracts, inventory, or acquisition activity may need more specialized review. Ask prospective providers how they will work with current staff, what information they need, and which decisions are outside their scope.
Agree on a practical starting point, such as reviewing the latest close, identifying unsupported balances, or mapping the lender’s information request to existing reports. A short diagnostic can show whether the gap is mainly bookkeeping, controller oversight, or strategic finance. Do not assume that a broad service label guarantees a particular credential, deliverable, timetable, or outcome.
Which records matter if the loan supports expansion?
For an expansion loan, records should connect the proposed spending to the company’s operating plan. A controller can organize the current financial baseline, distinguish committed costs from estimates, and show how the expected spending appears in cash flow. The forecast should make assumptions visible, especially where the plan depends on hiring, inventory, equipment, or customer collections.
Working capital deserves close attention. A company may need to pay suppliers or staff before it collects from customers, so growth can increase the cash tied up in operations. Accounts receivable aging, payment terms, inventory records, and vendor obligations can help explain the timing. The company should not treat projected sales as immediately available cash.
Existing obligations also affect flexibility. The controller can assemble a debt schedule with balances, payment dates, and relevant contractual requirements, using the loan documents as the source. Management can then see how a proposed payment would sit alongside current commitments. Questions about guarantees, collateral rights, or legal interpretation belong with qualified advisers.
If the expansion includes an acquisition, the financial review broadens. Management may need to assess the target’s records, working capital, liabilities, and reporting practices, then plan how the businesses will combine their accounting operations. A controller may support due diligence and post-acquisition integration, while a CFO and legal advisers guide the broader transaction decisions.
The records do not establish that the expansion will succeed. They help the company test whether the financing plan rests on assumptions it can monitor and revise. If the forecast relies on a rapid sales ramp or a single customer, management should know how that dependence affects repayment before signing. The more the plan departs from historical operations, the more carefully assumptions need to be labeled.
What should the controller document before a lender reviews the file?
A controller should leave a clear trail from the figures in a lender package back to the accounting records and source documents. That trail can include the report date, the period covered, the person who prepared it, and whether the figures are final or still subject to adjustment. The point is not to bury a lender in paperwork; it is to make each important balance explainable.
For balances that require judgment, the notes should identify the method and the open question. A receivable might be overdue while management is still discussing a payment plan with the customer. An inventory balance may include items whose condition has not been reviewed. Recording the issue does not settle its accounting treatment, but it prevents an unresolved assumption from passing as a verified fact.
Adjustments should also be traceable. If the team changes an account after the monthly statements were first prepared, the controller can record what changed, why it changed, and which reports were updated. This matters when two versions of a statement circulate internally or when a lender asks why a previously supplied figure differs from the current one.
A practical lender file might contain the requested statements, reconciliations for significant accounts, a current debt schedule, and concise explanations for unusual movements. The exact contents should follow the lender’s request and the company’s circumstances. Sending unrelated reports can make it harder to find the answer, while omitting the support for a key figure can trigger follow-up questions.
The controller should not turn documentation into a claim that the numbers have been independently audited or that a loan is appropriate. Internal review has a defined scope, and the company should describe it accurately. If a lender requires an audit, a specific assurance level, or a legal certification, management should confirm who is qualified to provide it and what the requirement means.
How would this review work for a hypothetical expansion loan?
Consider a hypothetical company that wants to borrow to add production capacity. Its owner expects additional orders, but the equipment requires an upfront payment and the customers may pay after delivery. Before discussing loan terms, a controller would first check that the current cash, debt, payables, and customer balances agree with the supporting records.
The controller would then separate the existing business from the proposed expansion in the forecast. The current operation provides a baseline; the expansion adds estimated equipment costs, operating expenses, and expected collections. The assumptions would be marked as estimates rather than recorded as actual results, and management could see which timing differences create pressure on cash.
Next, the finance team would review whether the accounting process can track the new activity. If equipment purchases, inventory, or customer deposits are handled inconsistently, reports may not show the expansion’s costs clearly. The controller could assign responsibilities for recording and reviewing those transactions, while coordinating with the bookkeeper or outsourced accounting provider.
A CFO or the owner would compare the forecast with the proposed loan’s payment schedule and other terms. If repayment appears to depend on customers paying on time, management could test a slower collection scenario and consider what options remain. The controller supports that analysis with dependable records; the decision-maker weighs the business case, risk tolerance, and terms.
The useful result is not a promise that the lender will approve the loan or that the expansion will meet its targets. It is a clearer view of what the records support, what remains uncertain, and which assumptions deserve attention before the company commits. If the books cannot yet support that discussion, improving the close and forecast may be the first financing task.