In this guide 6 sections
Usually because each team uses a different definition, not because someone made a mistake. Sales counts the order, accounts counts the invoice, and returns are netted in different months. The fix is one written definition per measure, agreed with the accountant. GullySystem’s reporting work starts with that workshop, before any dashboard.
Different definitions, not different mistakes
Monthly reviews often start with three figures for sales. Each is correct by its own rule. Time then goes on reconciling them instead of deciding anything.
Sales usually counts an order when the customer confirms it. Accounts records the sale when the invoice is raised. A third view nets out returns, sometimes in a different month. Both teams are following a sensible rule, and both will defend their figure in the meeting, because each one ties back to records they keep.
None of these is wrong. The trouble is that nobody wrote down which one the business uses for which decision.
Where the gaps usually come from
A handful of rules cause most disagreements. Each is a choice, and each choice moves the total.
Timing adds a further gap. A CRM figure taken on the last day of the month will not match a Tally figure finalised a week later. Late credit notes cause the same problem, because a return agreed in March but entered in April moves the figure from one month to the next.
- Order date against invoice date
- Returns netted in the month of sale or the month of return
- Tax included in one view and excluded in another
- Interbranch transfers counted as sales in one system
- Cancelled orders left inside a CRM total
- Credit notes entered late in the books
How to trace one disagreement
Take one month and one branch. Pull both figures and list the documents behind each.
Match them document by document. Orders with no invoice, invoices with no order and returns booked elsewhere each form their own pile. The size of each pile shows which rule causes the gap.
This is slow the first time. It is also the only way to tell a definition problem from a data entry problem.
- Orders not yet invoiced
- Invoices with no matching order
- Returns booked in another period
- Entries with no branch tag
Agree one definition per measure
Bring the accountant and the department heads together. Someone who can settle a dispute between departments must attend.
Write each definition as a single sentence. Net sales might mean invoiced value excluding tax, less returns booked in the same month. Record which reports use it and who owns it.
Keep both numbers where both matter. Sales may still track orders for its pipeline. Each figure simply carries its own name, so nobody compares the two by mistake.
Build the rule in so it holds
Documents get ignored. A definition kept in a document drifts once people rebuild spreadsheets by hand. It holds better inside a reporting model that every report reads from.
Records that break the rule should be listed, not dropped. An invoice with no branch tag belongs on an exception report. Then the entry can be corrected at source.
Sales definition sheet
A single page with one row per measure: its name, a one-sentence definition, the source system, the owner and the reports that use it. Start with sales, returns and collections. Ask the accountant to sign off each row.
Open a blank worksheet to printQuestions owners ask
Will a dashboard tool fix this on its own?
No. Any tool will show two numbers if two definitions feed it. The definition is agreed first, then built into the model behind the dashboard.
Which figure is the right one?
The one the business agrees to use for that decision. Invoiced sales tie back to the books, so many owners review on that basis. Your accountant can advise which figure suits your statutory reporting.
How often should definitions be reviewed?
Whenever the way you sell or bill changes. A new branch, a new channel or a new returns policy are common triggers. A named owner keeps the list current.