diff --git a/How-startups-manage-investor-reporting%3A-the-monthly-close.md b/How-startups-manage-investor-reporting%3A-the-monthly-close.md new file mode 100644 index 0000000..39fbab8 --- /dev/null +++ b/How-startups-manage-investor-reporting%3A-the-monthly-close.md @@ -0,0 +1,136 @@ +
Many startups manage investor and keep the posts coming. reporting through one repeatable routine: the monthly close. Each month, the team reconciles bank and card accounts, checks revenue and expenses, updates the cash balance, and compares actual results with the forecast before anything goes to investors. Learning how startups manage investor reporting means learning that routine first.
+ +What the monthly close has to produce + +
A monthly close is the set of steps that finishes one month of accounting so its numbers can be trusted. I like to think of it as a checkpoint. Before anything goes to investors, the books for the month should be complete, the bank balances should match, and revenue and expenses should sit in the right period. Many first-time founders assume the close is only an accounting task, but it feeds the cash balance, the forecast, and the update your investors read.
+ +
Start by listing the outputs you actually need. For most early teams, that means closed books for the month, an updated cash balance, a short list of the biggest changes from plan, and a one-page update for investors. Each output should have a named source and a clear reason to exist. If a number does not feed a decision, it does not belong in the package. Ask yourself a few questions before you choose a template:
+ + +Who will read the update, and what will they decide from it? +Which figures do they already expect to see every month? +Which numbers change how you spend money this month? +Which figures would surprise you if they moved without warning? + + +
Write these answers down before you build anything. They show you which parts of the close are essential and which are habits. Many founders find that a large share of their monthly spreadsheet can be dropped once they know who reads it and why. A shorter package that gets read is more useful than a long one that gets skimmed.
+ +
Imagine a hypothetical three-person startup that sells a small sensor. The founders want one page each month showing cash on hand, units shipped, the three largest expense changes, and hiring plans. Those few items are enough for the first months. Detail can come later, once an investor asks for it and you know which question it answers.
+ +
Share the list with whoever prepares the close. That list becomes your reference point. When someone asks why a line is in the package, you can point back to the output and the decision it supports, instead of pointing to a habit nobody remembers starting.
+ +Build a close calendar with clear owners + +
A close calendar turns a good intention into a routine. It lists each task, who does it, when it starts relative to month end, and what evidence shows it is finished. Without one, the same questions come up every month: did anyone check the card transactions, and who entered the vendor bills? Most of the work is not hard, but it is easy to skip when nobody owns it.
+ +
Begin by choosing a close window, counted in business days after month end. Pick one that gives your bookkeeper or CPA enough time to finish, then keep it steady for several months before you change it. A deadline that moves every time a payment runs late makes one month hard to compare with the next, and it hides the real cause of the delay.
+ + + +TaskUsual ownerEvidence to keep + + +Bank and card reconciliationBookkeeper or accountantStatements matched to the ledger +Accruals for bills received lateFinance leadInvoices with the service period noted +Payroll and tax postingsPayroll provider or accountantPayroll register and tax deposit records +Revenue scheduleFinance leadContract terms and recognition schedule +Cash balance updateFounderBank balance dated to the close date + + + +
The table does not hand every task to the founder. You can own the decisions while someone who sees the ledger every week handles the reconciliations. A useful question is whether the person who spends the money also approves the entries. If the answer is yes, add a second reviewer, even if that reviewer is a part-time advisor or your outside accountant.
+ +
Decide what counts as finished. A reconciliation with an unexplained difference is not done, and a revenue schedule without a link to the signed contract is only a draft. Write these rules into the calendar so a task can be marked complete only when its evidence is attached. The habit feels slow at first, but it spares you from explaining later why last month's numbers changed.
+ +
Finish each close with a short review while the calendar is still open. Ask what took longer than planned, what was missing when it was needed, [And keep the posts coming.](https://Venturegrowthpartners.com/locations/massachusetts-boston-fractional-cfo-services/) what should move earlier next month. Keep the meeting brief. The point is to improve the process, not to find someone to blame when a file arrives late.
+ +Reconcile the books before you trust any metric + +
Reconciliation means matching what your accounting records say with what the bank or card provider reports. When the two disagree, something is missing, duplicated, or recorded in the wrong period. A startup that skips this step can produce revenue and cash figures that look reasonable but cannot be traced to a source, and investors tend to notice when they try.
+ +
Know which basis your books use before you build any report. Under cash basis accounting, income and expenses are recorded when money moves. Under accrual accounting, they are recorded when they are earned or incurred. Some startups begin on cash basis because it is simpler, then move to accrual reporting when they raise money or sign larger contracts. Ask your accountant which basis your statements use and why.
+ +
Revenue needs extra care for software and service businesses. Under ASC 606, a company recognizes revenue as it satisfies its obligations to a customer, which is often over time rather than on the day the invoice is paid. A yearly prepayment usually sits as deferred revenue and moves into income month by month. If your update shows the full annual payment as income in one month, the numbers will mislead both you and your investors.
+ +
Accruals and prepaid expenses follow the same logic. A bill for work done in one month but received in the next belongs to the earlier period. A prepaid annual software license belongs to each month it covers. At every close, ask a few simple questions: Is every bank account reconciled? Are there last month's bills still missing? Does any large payment cover a period beyond this one?
+ +
Keep a short open-items list with each difference, its amount, its status, and the person working on it. A difference you cannot yet explain can stay open as long as it is labeled honestly. What makes investors uneasy is a number that hides an unexplained gap, because it suggests the team does not know where the gap came from.
+ +Explain every variance between actuals and the forecast + +
A variance is the gap between what you planned and what actually happened. Variance analysis is the habit of explaining that gap in plain language. For investors, the explanation often matters more than the gap itself, because it shows whether your forecast reflects how the business really works or is only a set of hopeful numbers.
+ +
Start by choosing the lines that matter most. For many early companies, those are revenue, payroll, hosting or software costs, marketing spend, and any one-time item. Compare each line with the forecast and write one sentence that explains the difference. If you cannot explain a line in one sentence, the assumption behind it may be too loose to rely on.
+ +
Driver-based thinking helps. Instead of forecasting revenue as one figure, you tie it to drivers such as the number of paying customers, the average price, and how many customers leave each month. When actual results differ, you can see which driver moved. Imagine a hypothetical subscription business that planned a certain number of new customers and signed fewer. A useful note names the driver, such as slower sales, rather than saying only that revenue came in low.
+ +
Ask a few questions for each variance. Was it timing, meaning a cost or payment landed in another month? Was it a real change, such as a hire that slipped or a price that changed? Or was it an error in the forecast itself? Each answer leads to a different action. Timing differences usually reverse, while real changes may require updating the plan.
+ +
Keep the explanations in a running record. Over several months, that record shows which assumptions you tend to get wrong and where your planning needs more care. In a financing conversation, that history is useful because it shows you understand the drivers and are improving the model, not just reporting totals and hoping no one asks.
+ +Roll the 13-week cash forecast forward each month + +
A 13-week cash forecast is a week-by-week view of expected cash coming in and going out over the next quarter. Its job is to show the lowest balance your cash may reach and the week when that could happen. A profit forecast follows accounting results, but this one follows money moving through the bank, which is what decides whether you can keep operating.
+ +
Rolling the forecast forward means you keep the same structure each month, replace the weeks that have passed with actual results, and add a new week at the end so the horizon stays at thirteen weeks. This habit keeps the forecast honest. A forecast that is never compared with reality slowly turns into a document nobody trusts, including you.
+ +
Work through the update in a fixed order:
+ + +Start with the actual bank balance, dated to the close date. +Replace the past weeks with actual receipts and payments, and note any timing differences. +Update expected customer receipts using their payment terms, not their verbal promises. +Place payroll, rent, tax deposits, and vendor payments on the dates they are actually due. +Find the week with the lowest projected balance, and decide what you would do before it arrives. + + +
The step about customer receipts deserves the most care. A customer who says they will pay next week may pay later, so a forecast should use dates you can support with invoices, contracts, and past payment patterns. If a large customer has a history of paying late, model that late payment instead of hoping it changes.
+ +
The lowest point matters more than the average. A business can look healthy across a month and still run short in one week, because a large payroll run lands before a big collection clears. Ask which actions would close that gap: delaying a discretionary purchase, speeding up invoices, or deciding to raise money before the balance gets uncomfortably close to zero.
+ +
This is where the forecast connects to investor reporting. Investors often ask about runway, which is the time left before cash runs out at the current pace. Runway depends on the same cash forecast you use to run the company, so the number you share should match it. Two versions of cash in circulation are a common cause of lost trust.
+ +Build the investor update from the close, not from memory + +
An investor update is a short written report that tells investors how the company performed, what changed, and what you need from them. It works best when every figure comes from the close you just finished. This is where how startups manage investor reporting becomes visible to the people who fund them, and a figure written from memory or from an unreconciled dashboard creates a gap that is hard to close later.
+ +
Decide the structure once, then keep it steady. Readers learn where to look when the layout stays the same month after month. A common structure includes a short summary, key figures with their definitions, the cash position and runway, the largest changes from plan, and specific asks. Here is a checklist you can adapt:
+ + +A summary in two or three sentences +Revenue and cash balance, with the date and source of each +Runway, calculated the same way every month +The largest variances from plan, each with a one-line explanation +Hiring, product, or customer milestones that changed this month +The specific help you need, such as introductions or referrals + + +
Define every metric once and keep the definitions in the update or a shared glossary. If monthly recurring revenue means one thing in one month and something slightly different the next, the trend will mislead everyone. Write down what is included, what is excluded, and where the figure comes from. A definitions line takes minutes to write and can save long email threads later.
+ +
Be honest about what remains uncertain. An update can say that a renewal is still open or that a vendor invoice could change the cost estimate. That kind of statement builds trust. Avoid promising outcomes, such as a fundraise that will close or a sale that will happen, because neither is guaranteed, and the update should never suggest otherwise.
+ +
Send the update on a regular schedule and file a copy next to the close records. When an investor asks a question months later, you can answer from the record instead of rebuilding the story from memory. Consistency is what turns a monthly email into a track record that can support a future raise, a loan application, or a sale process.
+ +Coordinate with your CPA and keep the close ready for diligence + +
If you already have a CPA or controller, the monthly close belongs to them as much as to you. They know the tax position, the audit trail, and the rules for recording transactions. Strategic financial support adds forecasting, investor reporting, and planning. The two work best when each knows which decisions belong to whom, rather than both quietly editing the same ledger.
+ +
Ask a few questions early. Who owns the general ledger and the chart of accounts? Who approves journal entries? Who prepares the cash forecast, and who checks it? Who answers investor questions about the numbers? Write the answers down. That step prevents a common problem, where a figure changes after the update has gone out and nobody can say who changed it or why.
+ +
A short handoff routine helps. Before the close, share the open items and the variances you expect to explain. After the close, your accountant confirms the figures that will go into the update. The routine feels like extra work at first, but it removes the surprise of an adjustment that arrives after an investor has already acted on the old number.
+ +
Diligence is the test these habits prepare you for. When an investor, lender, or buyer reviews your financials, they ask for support: bank statements, revenue schedules, reconciliations, and written explanations for large changes. A close that produces a folder of matched statements and variance notes is much easier to review than one that depends on memory. The same is true if you later consider a sale or hire a controller.
+ +
Think about systems too. A spreadsheet can carry an early company, but changing the chart of accounts or moving to a new accounting platform gets harder when history is spread across loose files. Many companies adopt cloud accounting or an ERP system once volume grows. Keep a record of each chart of accounts change and each system migration, so the history of your numbers stays readable.
+ +Worked example: one hypothetical month from bank match to investor update + +
Here is one way these steps fit together. Imagine a hypothetical software startup called Pine Route that bills customers monthly and starts the close with a cash balance of $600,000. The figures below are invented for illustration. They do not describe any real company, customer, or outcome, and your own numbers will look different.
+ +
On the first day of the close, the bookkeeper matches the bank and card accounts. She finds one card charge recorded twice and one customer payment not yet posted. She removes the duplicate, posts the payment, and adds both items to the open-items list. Once the cash balance in the books matches the bank, that figure is ready to go into the update.
+ +
Next, the founder reviews the revenue schedule. One customer paid a yearly plan in advance, so most of that payment sits as deferred revenue and enters income month by month. The cash forecast counted the full payment as a receipt, which is correct, but the revenue plan had assumed it would show as income that month. The variance note names that timing difference, so no one mistakes it for lost business.
+ +
Then the forecast rolls forward. Actual payroll and vendor payments replace the forecast amounts for the weeks that have passed. A large customer who usually pays late moves two weeks later in the model. The updated forecast shows the lowest projected balance falls in a week after a payroll run, so the founder writes down a decision: delay one discretionary vendor payment, or chase an overdue invoice, if the balance drops close to the floor the team has set.
+ +
At the close, $600,000 in cash and a hypothetical net outflow of $60,000 per month give a simple runway of ten months at that pace. The update reports that figure with the same definition as last month, lists two variances with one-line explanations, flags one renewal as pending, and asks for one introduction. The folder holds the reconciliations, the revenue schedule, and the forecast version used.
\ No newline at end of file