Description
Normalize recurring contract value to MRR and ARR.
Business accounting and analytics distinguish gross, net, allocated, recognized and forecast amounts. Currency, period, eligibility and interaction-allocation conventions determine a reported contribution; reconciling one term does not verify revenue, payment rights or future commercial outcomes.
Normalize recurring contract value to MRR and ARR.
When to use this tool
Use Term Contracted Recurring Revenue Month Factor when reconciling the stated business amount, share, bridge or forecast convention.
How to use the tool and how it works
- Enter contractValue, oneTimeFees, termMonths, monthlyServices. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read recurringContractValue, normalizedMrr, normalizedArr. Use the output convention below.
Normalize recurring contract value to MRR and ARR. Require contractValue >= oneTimeFees >= 0, monthlyServices >= 0 and termMonths > 0; recurring value subtracts one-time fees, MRR divides by months and adds services, ARR = 12*MRR.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| contractValue | Contract Value | Required. Finite number. |
| oneTimeFees | One Time Fees | Required. Finite number; minimum 0. |
| termMonths | Term Months | Required. Finite number; strictly above 0. |
| monthlyServices | Supplied additional service revenue on the same period/currency basis as contract MRR. | Required. Finite number; minimum 0. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| recurringContractValue | Recurring Contract Value | Required. Finite number. |
| normalizedMrr | Normalized Mrr | Required. Finite number. |
| normalizedArr | Normalized Arr | Required. Finite number. |
{
"input": {
"contractValue": 1200,
"oneTimeFees": 200,
"termMonths": 10,
"monthlyServices": 20
},
"output": {
"recurringContractValue": 1000,
"normalizedMrr": 120,
"normalizedArr": 1440
}
}Limitations and assumptions
- Monthly services are assumed additional to the contract amount; normalized billing metrics are not verified recognized revenue or forecasts.
- Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
- Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.
Alternative or Complementary methods
Use complete verified accounts and governing commercial terms, and apply the appropriate accounting and financial judgment for actual reporting, payment or investment decisions.
References
Similar or alternative tools
- Recurring Revenue Proration Day Basis
Prorate an amount using calendar or supplied basis days.
- Gross Net Revenue Recognition Bridge
Bridge gross billings to recognized revenue under supplied deductions.