Plain definition
Average revenue per account, often called ARPA, divides a defined period’s revenue by customer accounts rather than individual users. It is useful where one account can contain many seats, locations, or users. ARPA and ARPU answer different questions: an account can expand through more users while ARPA changes little, or ARPA can rise through pricing while user count is unchanged.
Like other subscription metrics, ARPA is not automatically recognised revenue or cash collected. Its usefulness depends on an explicit account definition: paid customer, billing entity, active subscription, or another rule applied consistently.
Illustrative example
Monetary examples use Saudi riyals (SAR). The same principles apply in other currencies.
Suppose a software company recognises of recurring subscription revenue in a month from 100 active customer accounts. ARPA is . The same revenue across 1,200 users would produce ARPU of , but those measures should not be substituted for one another.
If ARPA rises, management should ask whether existing accounts bought additional users, list prices increased, discounts ended, or smaller accounts churned. Each explanation carries a different retention and sales implication.
| Monthly recurring subscription revenue | |
|---|---|
| Active customer accounts | |
| Monthly ARPA |
An account with multiple legal entities or subscriptions needs a documented counting rule to avoid double counting.
Why it matters
ARPA connects account-level commercial strategy with revenue concentration and expansion. A total revenue trend alone cannot show whether a few accounts are becoming more important.
Practical consequence
Define the account, revenue scope, and denominator timing. Reconcile the account count to billing records and separate new, retained, expanded, downgraded, and churned accounts. Report ARPA by meaningful segment and pair it with account retention and concentration, so a higher average is not mistaken for broad-based growth.