Every Board Number Should Come With Its Receipts

Emily Goh · 2026-11-15

It is the night before the board meeting. The deck says new ARR for the quarter is $1.8M. The CFO's model says $1.6M. Someone on the sales team remembers a bigger number from the forecast call. At 10pm, three people are in a thread trying to work out which one is right, and nobody can say for sure where any of them came from.

So, how do you make board reporting accurate? Give every number on the board deck a receipt. A receipt is five things: a written definition of what the number counts, a named owner, the date and source it was pulled from, the records that make it up, and a note of anything excluded or still failing. If a director asks "where does this come from?", you can answer in one sentence and show the rows. Accuracy is less about better slides and more about being able to prove each number before it goes in front of the board.

Why board numbers go wrong

Board numbers rarely go wrong because someone made a typo. They go wrong in quieter ways.

The definition shifted. "New ARR" included expansion last quarter and excludes it this quarter, and nobody wrote that down.

The pull date moved. Sales pulled on the 30th, Finance pulled on the 2nd after two late deals closed.

The records do not match the rule. A few deals marked Closed Won have no signed contract. They count in the CRM report and not in Finance's model.

Each of these makes the number "right" for whoever pulled it and wrong for everyone else. That is why the night-before thread happens. Everyone is defending their own version, and nobody has the receipt.

What a receipt looks like

A receipt does not need to be fancy. For each number on the deck, write down:

1. The definition. One or two sentences in plain English. For example: "New ARR = annual contract value of deals moved to Closed Won this quarter, signed contract on file, excluding renewals and expansion." If your team has never agreed what Closed Won means, start there. We wrote a guide on how to define Closed Won.
2. The owner. One named person who signs off on the definition. Not a team. A person.
3. The source and pull date. Which system, which report, which day.
4. The records. The list of deals, accounts or invoices that add up to the number. Kept somewhere you can open during the meeting.
5. The exceptions. What was left out and why. Say, three deals worth $140K are excluded because the contract is not on file yet.

That last line matters most. A board does not expect perfect data. It expects you to know where the gaps are. A footnote that says "$140K excluded pending contracts" builds more trust than a clean number that falls apart under one question.

Trace before you present

The receipt only works if you can walk from the slide back to the rows. We call this traceability, and it is the difference between a number you can defend and a number you hope nobody asks about. Our post on why you can't defend a number you can't trace goes deeper.

A simple test: pick any number on the deck and ask someone who did not build it to find the records behind it in five minutes. If they cannot, the number is not ready.

Do this check about two weeks before the meeting, not the night before. Two weeks gives you time to fix records, chase missing contracts, or decide to footnote instead. We walked through that timeline in the QBR where nobody argued about the data. The same steps work for a board deck.

Receipts change the conversation

Something useful happens when every number comes with its receipt. The board meeting stops being about whether the number is right and starts being about what to do next.

If a director asks why pipeline coverage dropped, you can show the deals that slipped and the reason recorded on each. Nobody has to guess. Nobody has to defend their spreadsheet. And if a number turns out to be off, the receipt shows where the gap is: the definition, the pull date, or the records. That is a fix, not a fight.

It also takes pressure off the person presenting. A RevOps lead or CFO who walks in with receipts is not hoping the numbers hold. They know which ones are solid and which ones carry a footnote.

What you can do this week

You do not need to rebuild your board pack. Start small:

1. List every number on your last board deck. All of them, even the small ones in the appendix.
2. Pick the five that drive decisions. Usually ARR, pipeline, win rate, churn and cash.
3. Write a one-line definition and an owner for each. If two teams disagree on a definition, that is the first conversation to have, not the last.
4. Pull the records behind each one and check a sample against the definition. Note anything that fails.
5. Add a small footnote line to each slide: source, pull date, and any exclusions.
6. Put the date for your next data check on the calendar, two weeks before the next board meeting.

By the next meeting, your five most important numbers will each have a receipt. That is enough to change how the meeting feels.

Where Gohvio fits

Gohvio helps with the checking part. You upload your own guardrails, the definitions your teams actually use, as a document. A person approves them, and each change is recorded with who changed it and when. Gohvio checks your CRM data against those guardrails and shows what is broken, what it does to pipeline and forecast, and the rows behind every finding. It is read-only, so it never changes your CRM.

That gives you the definition, the change history and the rows behind each finding, which is most of a receipt, before the deck is built.

Stop debating your data. Start making evidence-based decisions.