Sales management
Reconcile ARR, total contract value and pipeline amount with AI
Build a value-basis register before comparing recurring sales, one-time fees and the amount used in pipeline reports.
Annual recurring value, full-term contract value and cash collected are different measures.
Editorial workflow guide · AI-assisted preparation · Not a hands-on product test. How we work
Define the value before interpreting the number
Start with the approved line items, billing periods, term length, one-time charges and currency. Ask the reporting owner which value belongs in the opportunity amount and which separate measures the team tracks. A number labeled revenue can mean several things; AI should not pick its meaning from the largest available field.
Prepare a register containing metric name, business definition, included charges, period, source fields and calculation owner. Keep the forecast amount separate from the full opportunity amount. Neither is proof that the customer has signed, paid or received the service. Use only the approved commercial record, not a rep’s shorthand estimate.
Sponsor
SPONSORED
AI FOR YOURSales team.Less busywork.More selling.
Your team knows sales.
We help put AI to work.
Work a recurring-plus-setup example
In a fictional offer, a 24-month service costs $1,000 each month with a separate $3,000 setup fee. On the stated simplified basis, annual recurring value is $12,000; the full-term recurring value is $24,000; adding setup gives $27,000 total contract value. All figures are illustrative and exclude discounts, taxes, proration and usage changes.
If the pipeline report uses first-year value including setup, its approved amount could instead be $15,000. The register should explain that choice rather than overwriting it with $27,000. A $3,000 deposit would be another measure. Do not sum these overlapping values as if they represented separate sales.
Check the product-specific fields
HubSpot documents ARR and MRR as derived from recurring line items and term lengths, while TCV includes recurring and one-time line items. Those calculated values do not use the deal Amount field. ARR and MRR also have subscription requirements. Confirm the actual properties and eligible features in your account before assuming an amount edit updates every measure.
Treat ramped prices, open-ended terms and usage-based charges as additional review cases. A simple monthly rate multiplied by twelve may not describe them correctly. Keep unknown term lengths visible and inspect any platform default rather than treating the default as buyer agreement. Accounting recognition is a separate finance decision outside this preparation workflow.
Return a reconciliation the manager can explain
Use one row per measure with source version, formula, value, period, currency, exclusions and reviewer. Include a bridge explaining differences between the approved pipeline amount and the calculated contract measures. Route inconsistent or missing line items to the responsible owner before drawing a trend conclusion.
Rehearse with a one-time-only sale, the recurring example, an unknown term and a canceled optional add-on. Check that the packet never counts the same charge twice. This is a proposed sales-reporting review, not a tested billing integration or accounting method. The result should make the basis of a number inspectable before AI writes the management narrative.
A prompt to adapt
Build a value-basis register from these approved line items and reporting definitions. Separate recurring annual value, full-term value, one-time fees, pipeline amount, forecast weighting and payments. Show formulas and exclusions. Preserve unknowns; do not change records, infer accounting recognition or count overlapping measures twice.
Use fictional or anonymized examples while testing. Add your approved business rules before using a draft.Source documents
Primary sources support the references above. These workflows are editorial suggestions; confirm current product availability, pricing, permissions, and integration details directly.
Questions or corrections?
See our editorial policy for how we distinguish workflow suggestions, vendor statements, and tested results.