Revenue Trend

Test whether revenue follows a believable shape across the year.

  • General ledger alone
  • Compares with last year

How the result is read

A period carrying a wildly disproportionate share is either a genuine push or revenue pulled forward. The comparison is against the same period last year, never against an even twelfth — an even split is the wrong expectation for any business with a season.

The worksheet, on the demo engagement

Revenue Trend, as the application draws it for Harrow Precision Engineering Ltd, the fictional demo engagement — one row per fiscal period per segment.

Revenue by segment, prior year against current
27.7k19.4kHardware21.4k19.9kSoftware1.2k0Spare parts13.9k12kServices14.8k7.1kDec only (all seg)
  • CY
  • PY
Total Revenue
64,200
YoY
+25.1%
December
23% of FY
Result grid5 rows
SegmentCYPYDelta %% of totalFlag
Hardware27,70019,400+42.8%43.1%YoY swing
Software21,40019,900+7.5%33.3%
Spare parts1,200—n/m1.9%
Services13,90012,000+15.8%21.7%
Dec only (all seg)14,7667,100+108%23.0% of FYperiod-end conc.

In the application

Revenue Trend is filed under Revenue & receivables, index letter C. "Run all analyses" runs it with every other analysis the ledger can answer. The worksheet states the population it tested on its face — or "Not applicable" with the reason when a column it depends on is empty — and the Excel workbook the engagement exports files it under C, beside an index of the source files with their SHA-256 fingerprints.

Run your next audit file test without the Excel crash.

One free engagement to evaluate, valid 60 days. The ledger never leaves the machine.

  • 20 minutes
  • Runs on a fictional engagement
  • No client data required

Cookie settings

This site sets no cookies. It keeps one preference in your browser's localStorage — the currency you chose on the pricing pages — and its analytics are cookieless, so there is nothing to opt in or out of.

View Cookie Policy