Car wash membership revenue cutoff: reconcile the closing handover

At closing, trace membership billing, service periods, payment and bank settlement separately. Match those records with the allocation agreed in the deal documents. Keep IDs and timestamps, explain exceptions and obtain accounting and legal review. A paid invoice or later deposit does not automatically decide who owes the service or receives the funds.

Which cutoff dates and identifiers should the review preserve?

Monthly billing can span the closing date. A customer may pay before handover, use the wash afterward and have the payment reach the bank on another day, so keep those events separate.

The valuation hub connects this review with the deal’s economic assumptions. Buyers need to understand past earnings and the duties they will assume. The closing statement needs the specific allocation agreed by the parties. Those are separate questions even when they concern the same payment.

Prepare a schedule that keeps both questions visible. A closing cash adjustment does not automatically change past revenue. An earnings classification also does not prove who is entitled to funds under the sale agreement. Have qualified advisers review each treatment and the definitions supporting it.

Record the account ID, unique invoice or billing obligation, service dates, charge attempts, payment status, refunds, processor movements and bank payout reference. Keep the original export timestamp and relevant system time zone. Those details let reviewers connect entries without treating several attempts as several sales.

Define the exact cutoff and whether the effective time differs from signing time. A date-only file may not explain activity on both sides of a same-day handover. Keep the source timestamp. Do not invent an event order from a displayed calendar date when the records cannot support it.

Map pauses, cancellations, free access, promotions and plan changes. An active customer list does not by itself show each account’s service period or payment. Identify missing fields and request the records needed to resolve them.

How do paid invoices and payouts differ from customer activity?

Check what the installed system means by paid and how that status was set. Confirm payment and settlement evidence, including manually recorded external payments, instead of treating the label alone as proof of cash received.

Stripe’s invoicing integration documentation explains that invoice.paid also covers payments marked out of band. This provider-specific example shows why status alone need not prove funds reached a merchant account. It does not identify this wash’s platform or prove its cash receipts. Check the actual system and records.

Link invoices and payments with consistent IDs. Several attempts against one obligation should not become several sales. Give each refund, reversal or later recovery a dated entry linked to the original transaction. Keep those links intact when summarizing activity around closing.

A processor payout may combine transactions and balance movements from different customer dates. Its net amount reflects provider balance activity, while the reference helps trace who received cash. It does not define the customer’s service period.

Stripe’s payout reconciliation documentation separates balance movements from payouts. It notes that manual payouts need matching against transaction history. Check the installed provider’s records, since fields and settlement schedules may differ between platforms. Explain missing links rather than substituting a daily average.

Identify later receipts for earlier activity and earlier payments covering later service. Record where the funds went and how the agreement treats them. Keep the lag between payment and bank settlement visible. A daily revenue average does not explain those separate dates or contractual rights.

How should service obligations, tax recognition and agreed allocations be distinguished?

Review the customer offer and the access or service owed during the period. Separate unlimited use, defined wash quantities, pauses and refund terms rather than assuming every membership is a prepaid cash balance.

IRS Publication 538, revised January 2022, gives general accounting-method and advance-payment tax context. This dated material is not current deal-specific advice or a mandatory closing formula. Have an accountant review which treatment applies. A general publication does not set the allocation in the purchase agreement.

Keep tax treatment, book entries and the contract allocation separate. Each may answer a different question about one payment. Explain the differences. One presentation does not settle all three.

Consider a fictional $30 payment for a defined 30-day service period. An expressly assumed agreement assigns 12 days before closing and 18 afterward. That produces $12 and $18 under those assumed terms.

This is an agreed calculation, not a universal rule, market practice or actual customer contract. It does not establish the cost of providing the remaining service. It also does not decide whether either amount is recorded as revenue in the books.

Define included dates, rounding, leap periods and exceptions before calculating real accounts. Reconcile totals to the included customers and payment amounts. A correct formula applied to the wrong customer set still gives an unreliable closing adjustment. Preserve the definitions so another reviewer can check the calculation.

How should refunds, recoveries and overlapping adjustments be reviewed?

Record the original obligation, customer request, event date, amount and resulting access status. Separate requested refunds from approved ones, showing whether money was returned or the claim remains open.

Keep unpaid obligations separate from successful later recoveries. Review who controls collection after handover and how the agreement allocates funds or related fees. Several attempts appearing in an export do not become recurring cash. Link each outcome to the original obligation.

The prepaid-code closing guide reviews prepaid-product obligations separately. Keep those balances distinct from monthly memberships unless actual terms support combining them. Different service promises should not disappear in one unsupported deferred-revenue total. Show the product definitions used in the schedule.

Map member balances to the agreement’s working-capital definition and assumed obligations. Identify separate revenue adjustments and specific holdbacks. If an amount appears in several schedules, explain whether the terms intentionally add those treatments together. Check for duplication rather than relying on different labels.

The quality-of-earnings guide connects past records with earnings conclusions. Keep adjustments traceable to the closing schedule without automatically turning them into further price adjustments. Adjusted earnings and a balance-sheet allocation each need their own basis. Explain that basis beside the amount.

Keep estimated service costs separate from allocated receipts. The equipment reserve guide illustrates another cash need requiring its own supported model. Do not mix unrelated capital needs into a membership-cutoff calculation. An unexplained net figure can hide which obligation or adjustment it represents.

What should the reconciliation workflow and handover file contain?

Agree on a process another reviewer can repeat before the final export. Keep raw files and links from source records to adjustments, while limiting customer data to approved reviewers and the diligence purpose.

1. Fix the effective cutoff, time zone and included product population.
2. Match each billing obligation to service dates and payment evidence.
3. Trace processor movements and bank payouts without replacing customer dates.
4. Apply the agreement’s reviewed allocation and exception treatment.
5. Reconcile totals and remove unsupported or duplicate adjustments.

Assign each exception an owner, requested evidence and deadline. Keep open amounts separate from agreed amounts on the draft statement. A late export should not silently replace previously reviewed accounts. Explain which entries changed and why the population now differs.

Keep the agreed schedule, original exports, reviewer conclusions and a log of later settlements or refunds relevant to the cutoff. Record the approved correction process and its actual deadline under the sale documents. Do not replace that deadline with a generic assumed review period.

Confirm who handles member access and customer support while the records are matched. A disputed allocation does not permit changes to customer promises without the applicable review and approval. Keep service responsibilities visible alongside the accounting questions.

The file should let another reviewer trace an obligation through payment, service period and closing treatment. Label verified, estimated and open amounts. This evidence supports a documented handover. One invoice status, deposit date or generic proration formula does not settle the whole transaction.