Reporting
Automated Sales Reporting
A sales report should help you decide what needs attention. It becomes less useful when somebody spends the morning collecting exports, correcting totals and asking which version is right. Automated sales reporting can prepare that repeat work while keeping the meaning of each number clear.
Key takeaways
Agree what each sales measure includes.
Keep a traceable record behind every total.
Deliver a checked report with visible exceptions.
Automated sales reporting collects agreed sales records, checks them, calculates defined measures and delivers a dated report. Start with one CRM, one reporting period and a few useful measures. Keep open pipeline separate from won sales, flag missing information and let a responsible person review exceptions before sharing.
- Define sales measures
- Collect dated records
- Check and reconcile
- Review the draft
- Deliver and track corrections
Define what you mean by a sale
Before connecting anything, write a short definition for each number. Does won sales mean deals moved to Closed Won during the period, orders accepted, or money received? Those are different events. Choose the one the operational report needs and name it clearly. An operational sales dashboard is not a substitute for your accounting records.
Define the reporting timezone, start and end dates, currency, owner and exclusions. Decide whether ownership is taken at the time of the sale or from the current CRM owner. A later reassignment should not quietly change a previously approved team report. Keep cancellations and refunds visible under the rules your business already uses.
Choose a stable source for each field
For a first version, use the CRM as the source of deal ID, stage, owner, amount and closing date. Add payment or order information only if the report actually needs it. Match systems using stable deal or order IDs, with a reviewed mapping where identifiers differ. Similar customer names are not a safe match.
Use a supported connection or a controlled export. Save when the source was collected and when it last updated. If a feed fails, show the failure and withhold the affected measure rather than presenting yesterday’s number as today’s. Restrict the report to the information its audience is allowed to see.
Work through a weekly sales example
Suppose an illustrative CRM export contains 24 rows for deals closed this week. Two rows repeat existing deal IDs because two exports overlap. After deduplication, there are 22 distinct closed deals: 8 won and 14 lost. Won amounts total 12,000 in the chosen currency. The closed-deal win rate is 8 divided by 22, or 36.4%.
The report also shows 17 open opportunities worth 31,000 as a separate end-of-week pipeline snapshot. Do not add that amount to won sales or use those open opportunities in the closed-deal win-rate denominator. One open opportunity has no next-action date; place it in the follow-up list. These figures illustrate the rules, not a customer result or a promised improvement.
The reviewer should be able to open the eight won records, check their dates and add their amounts to reproduce 12,000. Keep the excluded duplicate IDs and reason in the run log. A chart that looks plausible is not sufficient evidence that the calculation is correct.
Catch errors before sending the report
Check required fields, valid dates, known owners and allowed stages before calculation. Reject amounts that cannot be interpreted reliably. If records use different currencies, report them separately unless an approved conversion rule and dated rate are available. Never silently total unlike currencies.
Compare the number of source records with included records and exclusions. Review unusually large changes against the underlying deals. Distinguish a real change in business from a changed filter, missing export or CRM cleanup. Set thresholds from your actual reporting history rather than inventing a universal percentage that must be wrong.
Send a report people can act on
Keep the first report small: won value, closed-deal win rate, open pipeline and records needing attention may be enough. Put the period, collection time and measure definitions beside the results. A manager needs to know which decisions the report supports and which records need checking.
Salesforce and HubSpot offer reporting features that may already cover part of this work. Check your actual access and available fields before adding another tool. A custom connection is useful when important data lives elsewhere or your review and delivery rules do not fit the existing report. Choose based on the workflow, not the number of charts.
Make reruns and corrections predictable
Give each run a unique ID and record which reporting period it covers. A retry should update the same draft or create a clearly labelled revision, not send the same email repeatedly. Track delivery separately from calculation so a temporary email failure does not recalculate and duplicate the report.
Agree how late changes are handled. For example, reopen the draft before approval, but issue a revision note after an approved report has been delivered. Keep the original and corrected totals with a reason. That makes a changed number understandable instead of creating two unexplained versions.
Test one report before expanding
Run the automation beside the existing manual report for a complete reporting cycle. Compare record IDs, exclusions, totals and recipients. Include a duplicate export, missing amount, changed owner, failed connection and rerun in the trial. Only turn on unattended delivery when the agreed cases behave correctly.
Send us your current report, the tools holding the data and the decisions it should support. We can help define a small custom reporting workflow, including the checking that still needs a person. The downloadable brief below gives you a clear starting point.
Your ready-to-use checklist
0 of 6 checked
Make the next step clear.
Sales reporting planning brief
Free templateConnect this with the rest of your workflow
Sources and notes
Sources checked on October 30, 2026.
- Salesforce: build a sales dashboard
An official example of defining opportunity report filters and closed-deal measures.
- HubSpot: create sales analytics reports
Native sales reporting options to compare with the needs of your own workflow.
