What to do first

These changes move the grade. The checks each one affects are listed under “Each check.”

1. Assign an owner to $34.3M of ARR. 2,083 active accounts have no rep. The top rep holds 25.6% of ARR. The parent field is the least-covered tag. Filling in owners lifts the results for “Those tags actually cover the book” and “One owner does not hold the book.” Moves Segmentation toward B.
2. Add a definitions tab. Write one line each for MRR, GRR, new and reactivation, the terms not yet written down. Keep the existing definitions for ARR, NRR, churn, expansion and cohort. Written definitions let a reader reproduce the KPI table from the stated rules. This raises the Unified, Finance-Approved Foundation score.
3. Normalize 2 tag fields. Segment and status carry case or spacing variants of the same value. One normalization pass removes them. Moves Segmentation up one band.
4. Fill in what the diligence view needs. The diligence-ready view lists unit or price data, or payments data, as missing. It also lists the two open owner findings above. Adding a units/price or payments table addresses the first item. Exporting tags as of each month would also let tag stability over the year be scored.
5. Re-grade after each month-end close. A monthly re-grade catches broken ties, duplicates and status drift before they reach the board pack. It keeps Audit-Grade Accuracy where it is.

Where the grade comes from

Inputs: 2 file(s), 8 sheet(s), 782,747 rows. Hazards handled: none. Checks run: 39 of 41. 2 could not be checked (listed below).

• Unified, Finance-Approved Foundation: 87.3 (B+)
• Audit-Grade Accuracy: 100 (A+)
• Cohort-Centric Design: 99.97 (A+)
• Multi-Dimensional Insights: 77.5 (B-)
• Anomalies: 100 (A+)

Accuracy, cohorts and anomalies carry the grade. The two lower pillars both come down to who owns each account and how terms and tags are written down.

Each check

Each item below is one part of the rubric. The heading is the check in plain words. The short code is the citation.

Unified, Finance-Approved Foundation

Bookings with no product or no owner

Unified, Finance-Approved Foundation. Cited as CP-05, owner.

This check measures how much of the latest book has no product and how much has no owner.

In this file, every account has a product (0% unassigned). However, 2,083 accounts, 24.9% of the book, have no owner. A buyer would ask who manages renewals and expansion on those accounts today. Check score 30.

Next step. Assign a product and an owner to the unassigned book before the next export.

The words in the definitions were written down

Unified, Finance-Approved Foundation. Cited as CP-07.

This check looks for the standard terms in the definitions text. It does not test whether those words match the numbers.

In this file, 5 of the 9 terms are defined: ARR, NRR, churn, expansion and cohort. MRR, GRR, new and reactivation are missing. A buyer would ask how new and reactivated revenue are separated, and how gross retention is calculated. Check score 56.

Next step. Write a short definition for each headline term the summary uses, in the same words the rubric expects.

Came through clean: Enough history to follow a customer (CP-01); Months where the whole book went quiet (CP-02); A customer goes quiet without a churn mark (CP-03); Revenue with no customer behind it (CP-04); Bookings with no product (the product half of CP-05); The product file covers the same months as billing (CP-06); Billed customers appear on the customer list (CP-08).

Audit-Grade Accuracy

Every check in this pillar passed. The bridge foots on its own. The customer detail matches the bridge ending. The movements rebuild from the customer rows. The headline KPIs reproduce under standard definitions.

Came through clean: The bridge foots on its own (CR-01); Customer detail matches the bridge ending (CR-02); Movements rebuild from the customer rows (CR-03); Product lines tie to billing (CR-04); The amount matches the status word (CR-05); Statuses tell a legal story over time (CR-06); Headline KPIs can be reproduced (CR-07); The bridge and the KPI table agree (CR-08); Product and segment totals add up (CR-09); Duplicate dollars that break the tie (CR-10).

Cohort-Centric Design

Start dates, contract end dates and history depth all support cohort analysis. One small point: a returning customer appears to have come back under a new account key instead of its original one. This did not change the pillar’s band, but a buyer tracing that customer’s history would ask about it.

Came through clean: Customers have a start date (CO-01); The start date matches the first revenue month (CO-02); Too many customers share one start month (CO-03); A returning customer kept the same key (CO-04); Contract end dates exist and fall after the start (CO-05); Retention looks earned, not just unexpired (CO-06); A trailing year has a year of history behind it (CO-07).

Multi-Dimensional Insights

One owner does not hold the book

Multi-Dimensional Insights. Cited as SG-06.

This check measures the top owner’s share of the latest book and the share with no owner.

In this file, the book is split across 3 reps. The top rep holds $35.2M, or 25.6%. Another $34.3M, or 24.9%, has no rep. A buyer would ask how coverage holds if one rep leaves, and who is working the unassigned accounts. Check score 30.

Next step. Reassign concentrated accounts and fill the unassigned ones so the book is not one rep’s.

Those tags actually cover the book

Multi-Dimensional Insights. Cited as SG-02.

For each tag, this check measures how much of the latest book sits on accounts with a real value.

In this file, the 6 tags cover 79.2% of the book on average. Parent is the least-covered field, and rep is the other field with gaps. A buyer would ask whether ARR can be cut by owner, or rolled up to the parent company, without manual work. Check score 55.

Next step. Fill the blank tags on the accounts that carry the book, starting with product and owner.

The same idea is spelled one way

Multi-Dimensional Insights. Cited as SG-04.

This check groups tag values that match once case and spacing are removed, and scores how many spellings each idea has.

In this file, 2 fields, segment and status, carry more than one spelling of the same value. A buyer filtering by segment would ask whether those variants are being counted as separate groups. Check score 80.

Next step. Pick one spelling for each category and apply it across the file.

Came through clean: The cuts a buyer expects are present (SG-01); A tag is a category, not free text (SG-03); Parent accounts are used (SG-05).

Anomalies

No spikes, unmarked drops, duplicates or unusual formats were found. The talking points tested against the file all held.

Came through clean: One customer spikes for a month and reverts (AN-01); A customer drops to zero and comes back unmarked (AN-02); One month moves the whole book (AN-03); Amounts do not match the file’s own format (AN-05); Duplicate rows (AN-06); The book sits in a few customers (AN-07); Prices did not move where an escalator was promised (AN-08); A sentence in the talking points does not match the file (AN-09).

What we could not check

• A new product line copies a price the account already had (AN-04). There was no month in which the whole book moved, so there was nothing for this check to test.
• Tags stay stable over the year (SG-07). The file stores one tag per account rather than one per month, so changes over time cannot be measured.

How this was graded

Weights: Unified, Finance-Approved Foundation 25%, Audit-Grade Accuracy 30%, Cohort-Centric Design 15%, Multi-Dimensional Insights 15%, Anomalies 15%. Bands: A ≥ 90, B ≥ 75, C ≥ 60, D ≥ 45. Bridge convention detected: monthly sum (monthly_sum). Rules version caeb8e512330. Readiness views: decision-ready not yet, diligence-ready no, AI-ready yes. The decision-ready and diligence-ready views are held back by the two open owner findings. The diligence-ready view also needs unit or price data, or payments data.

Next step

The Strategic Revenue Intelligence Assessment walks through these findings with a FinQore analyst. It shows what a decision-ready and diligence-ready cube looks like for your business. Your files are retained in FinQore infrastructure for the stated retention period and deleted on request.