Sign in

Blog · Board and management reporting

Self-service reporting: define, build and check a report

Self-service reporting gives business users a repeatable way to rebuild agreed reports from current files. Follow a monthly regional sales example with exact formulas, source checks and review responsibilities.

The short answerSelf service reporting lets business users produce recurring reports from their own files using agreed definitions, periods and checks. A dependable workflow starts with a complete export, calculates consistent comparisons, reconciles totals to the source and assigns a reviewer. Users can rebuild the report each period while finance or another metric owner remains responsible for its meaning.

Self service reporting lets business users rebuild an agreed report from current files and verify its numbers before sharing it. Start with a consistent export, calculate the same measures each period and reconcile the totals. A monthly regional sales report works only when its definitions and review responsibilities travel with the figures.

Agree what the recurring report answers

Write a short specification before opening the workbook: net sales by region, September 2026 against August 2026, in USD, using posting date and the region assigned to the transaction. Net sales include posted credits and exclude sales tax. Decide how late adjustments will affect previously issued reports.

Name the metric owner, preparer and reviewer. They can be different people, but none of those responsibilities should be implicit. For a sales report, finance approves the sales definition, sales operations prepares the comparison and regional leaders explain business movements.

The wider distinction between exploration and recurring reports belongs in self-service analytics and AI analytics. This workflow focuses on rebuilding and checking a defined report.

Start with a complete sales export

The following fictional US distributor's Raw worksheet has headers in A1:D1 and records in rows 2 through 10. Each invoice occupies one row in this example; the amounts are net sales after any posted adjustments. Store posting dates as actual dates and amounts as numbers.

Invoice ID Posting date Region Net sales (USD)
A1 08/12/2026 East 60,000
A2 08/25/2026 East 60,000
A3 08/20/2026 Central 80,000
A4 08/28/2026 West 100,000
S1 09/10/2026 East 70,000
S2 09/24/2026 East 62,000
S3 09/22/2026 Central 76,000
S4 09/15/2026 West 56,000
S5 09/29/2026 West 56,000

Keep the original export intact as evidence. Remove display subtotals before calculation, document any exclusions and check for blank regions. For an invoice-line export, the unique key must include the line ID; repeated invoice numbers alone would be normal.

Build the regional comparison

Create a Report worksheet. Its table starts at A1, with region in A, August sales in B, September sales in C, dollar change in D and growth in E. Enter East, Central and West in A2:A4.

In B2, sum the selected region and August posting dates:

=SUMIFS(Raw!$D$2:$D$10,Raw!$C$2:$C$10,$A2,Raw!$B$2:$B$10,">="&DATE(2026,8,1),Raw!$B$2:$B$10,"<"&DATE(2026,9,1))

In C2, change the date bounds to September:

=SUMIFS(Raw!$D$2:$D$10,Raw!$C$2:$C$10,$A2,Raw!$B$2:$B$10,">="&DATE(2026,9,1),Raw!$B$2:$B$10,"<"&DATE(2026,10,1))

Microsoft's SUMIFS documentation specifies a sum range followed by criteria ranges and criteria. Each range here covers the same records. Using the first day of the following month as the exclusive upper bound also accommodates dates carrying a time value.

In D2 and E2, enter:

=C2-B2
=IF(B2=0,"N/A",D2/B2)

Fill B2:E2 through row 4. Label a zero baseline as unavailable for percentage growth rather than presenting it as zero growth.

Region August sales (USD) September sales (USD) Change (USD) Growth
East 120,000 132,000 12,000 10.0%
Central 80,000 76,000 -4,000 -5.0%
West 100,000 112,000 12,000 12.0%
Total 300,000 320,000 20,000 6.7%

In row 5, sum columns B, C and D. E5 is =D5/B5. The company growth rate is $20,000 divided by $300,000, rounded to one decimal place; retain unrounded results in the workbook.

Check the report before releasing it

Prove the movement with the regional bridge:

Total sales change = 12,000 - 4,000 + 12,000 = 20,000 USD.

Then compare the report with the source owner's control totals. In this example, finance confirms August at $300,000 and September at $320,000. Subtract each control total from the corresponding report total: both differences must be $0.

Those checks serve different purposes. The regional bridge proves the arithmetic within the report; the finance reconciliation checks whether the report represents the intended source population. A report can sum perfectly and still exclude a region.

Check duplicate IDs on Raw by entering this in E2 and filling through E10:

=COUNTIFS($A$2:$A$10,A2)

Microsoft documents COUNTIFS as counting records that meet specified criteria. Every ID in this one-row-per-invoice example returns 1. Investigate higher counts before removing anything: a credit or a legitimate invoice line needs its own appropriate key.

Make the next reporting cycle repeatable

Keep the report specification beside the output: source filename, export timestamp, period, currency, net sales definition and preparation date. Record whether the ledger is closed or provisional. Keep a dated copy of each issued version so later corrections do not silently rewrite the result managers saw.

On the next refresh, replace the input through the same documented process and extend every formula range to cover all new rows. Confirm the region list includes any new territory. Reconcile again before asking anyone to explain a variance.

The practical self service reporting strategy is to agree definitions centrally and make production repeatable for business users. Use the completed report as an input to management reporting, where the wider monthly package and management decisions belong.

Where it goes wrong

  • Partial against complete periods. Compare closed months or clearly label both cutoff dates and the provisional result.
  • Changed region assignments. Choose transaction-time regions or a consistent restatement policy; otherwise territory changes look like sales performance.
  • Subtotals counted as records. A second total embedded in the export can inflate the report even when the formulas are correct.
  • Ranges left behind. A fixed range that worked last month can omit new records. Check the last source row each refresh.
  • Unreviewed explanations. Central's decline is visible, but the table cannot establish its cause. Assign the follow-up to the regional owner.

Covirage is not affiliated with Microsoft.

Build the report from your own file in Covirage

Upload your monthly sales workbook; Covirage maps the columns, and its tools compute and check regional comparisons against the supplied control figures. The external AI model explains the results with every figure traced to its rows. Create a free Covirage account, which takes about a minute, then set up your business and bring a sample of your own data.

See self-service analytics for the supporting workflow.

Questions people ask

What are the benefits of self service reporting?

Business users can rebuild familiar reports when new files arrive and investigate movements without rewriting the request each time. The benefit depends on keeping definitions and checks consistent; faster production is useful only when readers can verify the result.

Who should approve a self-service report?

The metric owner approves the definition, while a named reviewer checks the current figures and source reconciliation. For regional sales, finance can own net revenue and the sales operations owner can investigate regional movements before circulation.

How often should a recurring report be refreshed?

Use the cadence of the decision and the availability of complete source files. A monthly revenue report should state whether the period is closed or provisional. Refreshing it more frequently does not resolve missing postings or incomplete credits.

Is self-service reporting the same as self-service analytics?

Reporting repeatedly answers an agreed set of questions, such as sales by region against the previous month. Analytics can investigate new questions behind those results. A recurring report can therefore provide the starting point for a separate analysis.