The Membership Revenue Bridge is this site’s reconciliation framework connecting paying-account movements, actual billings, and collected membership revenue. It separates joins, cancellations, reactivations, and payment failures, then explains refunds, fees, and timing. Buyers and sellers use it to test recurring revenue without mistaking a dashboard count or billing total for collected cash.
- Define paying members, billing periods, and account movements before calculating growth.
- Keep customer exits and failed-payment events distinguishable.
- Reconcile billings to collections, settlements, and the accounting ledger.
- Examine cohorts and service costs before drawing a valuation conclusion.
How does the bridge define its paying-account population?
The framework connects three records that tell different stories: membership status, customer charges, and cash collection. It makes differences visible rather than forcing every report to show the same number.
The Membership Revenue Bridge is an original reconciliation of opening paying accounts and account changes, followed by a separate explanation of membership billings, collection adjustments, settlement timing, and accounting revenue.
An account-status report answers who belongs to the defined population. A billing report answers what was charged.
Processor and bank records answer what money was collected or transferred. The valuation hub explains why evidence about recurring earnings needs that distinction. Use the bridge when a seller’s account total is being treated as proof of future revenue without examining the other records.
Write a definition appropriate to the system and analysis, then apply it consistently. The label active can include several operational states unless the report’s rules specify otherwise.
Check what each status means. Canceled plans may have paid days left; paused plans, free accounts and payment failures may follow different rules. State whether the report counts people, vehicles, plans or accounts. Switching units can show growth without gaining paying customers.
Save the status rules and report dates. If the system changes how it groups accounts, keep the old rules and explain the change. The buyer hub connects this work with purchase diligence. A buyer needs to know who was counted before using the total in a forecast or comparing it with another wash.
How do account movements reconcile?
Start with paying accounts at the beginning of the period and show each change through the ending count. Investigate any gap rather than hiding it in an unexplained adjustment.
For a fictional month, assume 1,200 opening paying accounts, 100 new paying accounts, 30 reactivations, 70 voluntary exits, and 40 separate exits caused by unrecovered payment failure. Closing paying accounts are 1,200 plus 100 plus 30 minus 70 minus 40, or 1,220.
Count each exit once. If an unpaid account is later marked canceled, do not subtract it again from the same bridge. A returning account should not also count as a new join unless the report clearly explains that choice. Restrict access to account identifiers, but keep enough evidence for an authorized reviewer to rebuild the count.
| Movement | Accounts |
|---|---|
| Opening paying accounts | 1,200 |
| New paying accounts | +100 |
| Reactivated accounts | +30 |
| Voluntary exits | −70 |
| Other payment-related exits, without overlap | −40 |
| Closing paying accounts | 1,220 |
Retain a movement report with the opening and closing dates. Explain any correction to the original classification.
Why is the revenue bridge separate from the account bridge?
Account movements do not determine revenue by themselves. Charges depend on the actual pricing, billing dates, service periods, discounts, plan tiers, and collection outcomes.
A closing count multiplied by one advertised monthly price can be useful as a rough scenario, but it should not be labeled historical revenue. Accounts may have different rates, join during the period, receive refunds, or pay on different dates. Some plans may cover more than one vehicle under specific terms.
Request the charge records and group them by billing period. Show which refunds or other changes belong to those charges and which relate to older bills. When billed sales rise, check what customers actually paid and which groups drove the change. A billed dollar is not automatically cash the owner can spend on payroll, supplies or debt.
Save the pricing schedule used for the period alongside the charges report. Record the effective dates of changes so a later reviewer can reproduce the billing explanation.
How do charges turn into collections and settlements?
Separate the collection outcome from the processor’s transfer schedule. The gross amount customers paid can differ from the net deposit because of fees, refunds, other deductions, or timing.
In a second fictional example, $37,000 of charges minus $500 of refunds and $1,500 of uncollected amounts produces $35,000 of collections under the stated simplified assumptions. If $800 of processing expense is withheld, the associated net amount is $34,200 before any additional timing or balance differences.
These dollar amounts do not follow from the earlier account-count example. You need the charge records because rates and billing dates differ. Match processor payout batches to bank deposits and show money that crosses the month end. Ask the accountant to explain when revenue is earned and how it appears in the ledger; cash received and reported revenue can differ for valid reasons.
Keep refunds and failed collections distinguishable for the stated period in the supporting schedule. Identify which settlement or accounting period contains each adjustment.
How should retention and service economics be examined?
Compare like-for-like groups over stated periods. An overall retention figure can hide the behavior of customers who joined under different prices, promotions, or service conditions.
Group accounts by joining month or a useful plan feature. Show when an introductory price ends, then track paying accounts and cash collected. New groups that have not faced renewal have less history. Use matching observation windows before comparing results.
The ICA’s public Q4 2025 summary discusses membership retention as an industry theme. It does not establish this wash’s retention or guarantee future collections. Use dated industry context to motivate the review, then support the conclusion with the site’s own cohort history.
Analyze visits and service costs alongside recurring collections. Unlimited-plan access can produce different patterns of usage, so the contribution of a member is not described completely by the monthly fee.
Keep member visits separate from paid retail washes. State which visits you divide labor, chemical and utility costs by, so another reviewer can check the cost per visit. Compare the work delivered, open hours, busy periods and downtime where records allow it. More members may need more staff or wash capacity even when the plan prices stay the same.
The operations hub explains cost per visit and the records needed to test savings claims. A member returning for another wash has not made another retail payment. Show whether cash collected from members supports the cost of serving them, and state how shared and fixed costs enter the review.
What changes when the business is sold?
Evaluate membership obligations and system transfer together with the financial reconciliation. An acquisition agreement should establish what the purchaser receives and which existing customer commitments continue.
Identify plan terms, prepaid service, outstanding refunds, software and payment contracts, data permissions, and account-transfer requirements. Arrange access and communications through appropriate professionals. The IRS discussion of a business sale explains why transaction scope and allocation deserve attention; it does not decide the contractual transfer of customer plans.
For a financed purchase, the SBA’s 7(a) overview identifies changes of ownership among program uses. Ask the lender what supporting records it needs under current requirements. The bridge can organize evidence, but it does not approve the financing or establish an acquisition valuation.
Make a written transfer issues list for the proposed sale. Name each contract, the person reviewing it, the decision needed and any item still waiting on evidence or approval. Keep the revenue review separate from permission to use the systems or contact customers. A balanced worksheet does not show that those permissions have been granted.
What should the finished bridge contain?
Build a file another reviewer can follow, with clear counts, dates and cutoff. Explain differences and missing evidence rather than hiding them to make totals look cleaner.
- Record the reporting period and definitions for accounts, charges, visits, and collections.
- Reconcile opening accounts and mutually exclusive movements to closing accounts.
- Explain pricing, promotions, refunds, payment failures, and recovered amounts.
- Connect collection records, settlement batches, bank deposits, and ledger treatment.
- Review cohorts and service economics, then document transfer requirements separately.
The seller hub connects this file with sale preparation and approved sharing. Keep the original exports and each revised worksheet so changes in account groups or assumptions stay visible. The bridge helps a buyer assess the evidence; it should not make the count look bigger.
Keep a dated list of unexplained differences and save each revised version. Name the person responsible for each question and retain the source report that raised it. The reviewer should see both the amounts that tie out and the gaps that still need evidence.