Laundromat revenue: reconcile paid cycles, free starts and collected cash

A washing machine's cycle count does not automatically equal the number of paid washes. Service tests, promotional starts, restarted failed cycles and customer refunds can all create differences. Build a bridge between machine activity and the payment records before estimating revenue from cycle totals.

Define the event used by each system. A controller may count starts, completions or paid authorizations, while a payment platform may record wallet top-ups rather than individual washes. Preserve those definitions in the reconciliation. If the machine log resets during a repair, record the reset and the last supported reading rather than treating the new counter as the beginning of the month.

ENERGY STAR's commercial-washer guidance distinguishes equipment arrangements such as route operation and direct ownership. Confirm who owns the machines, collects receipts and pays operating costs under the actual agreement. A location's machine revenue and its share of receipts can be different amounts.

For each machine, record opening and closing counters, paid cycles, approved free starts, service tests, failed starts and restarts. Link free or corrective events to an operator authorization or service record. A count adjustment should identify the reason and person responsible so repeated exceptions remain visible.

Keep machine types and programs separate. A large washer, a small washer and an extended program may have different prices and resource use. Using one average price for all starts can hide a change in customer mix or a price update. Retain the effective date of each price configuration and any promotion.

Review downtime beside activity. Lower cycle counts can reflect weak demand or a machine that was unavailable. The action differs: marketing cannot repair a failed machine, and replacing an idle but working unit may not create demand. Keep the operational reason with the count so the revenue review does not lose that context. If a payment terminal stores transactions during an outage, identify the pending population and reconcile its later submission before declaring those cycles unpaid.

Assume a hypothetical group of machines records 800 completed cycles. Supporting logs identify 740 paid cycles, twenty promotional starts, fifteen service tests and twenty-five free restarts after failed attempts. The categories reconcile to 800. At an assumed $4.50 price for every paid cycle in this simplified example, gross paid-cycle sales are $3,330.

Of the 740 paid cycles, 480 are card-funded and 260 are coin-funded. Card charges therefore total $2,160 and coin receipts should total $1,170 before any separate corrections. Suppose the card processor statement shows $13.50 of refunds and $54 of fees, giving a $2,092.50 payout. The bank deposit is lower than gross card sales for identified reasons.

The example assumes the card system charges per wash. If customers instead load a stored balance, card receipts and wash usage occur at different times. Reconcile opening stored balances plus loads less usage and refunds to closing balances, then ask accounting to apply the appropriate revenue and liability policy. Do not label every wallet top-up as a completed wash.

Match the machine reading with the coin-collection time. If the counter is read on the final evening but coins are collected two days later, the collection includes a different activity period. Record the later starts or use a supported cutoff adjustment. A calendar mismatch can look like cash loss even when every coin is present.

Separate machine takings from change-machine cash and operating floats. Moving notes into a changer and withdrawing coins for customer change transfers cash within the business; it does not create another wash sale. Record collections, bank deposits, refunds paid from the float and authorized cash movements with clear identifiers.

Use an appropriate collection and count process with independent review where practical. Investigate differences by machine and interval, including jams, price configuration, missed collections and counter resets. The purpose is to explain a discrepancy from evidence, not to infer misconduct from one unmatched total.

Once paid activity reconciles, compare revenue with the machine's water, energy, detergent where supplied, maintenance and payment costs. The Department of Energy's laundry guidance identifies operating and equipment choices that affect resource use. Use actual utility tariffs and measured consumption where available rather than assuming every cycle uses the same amount.

A water bill covers the billing interval and may include other uses or a fixed charge. Dividing the whole bill by this month's washer starts can produce a misleading unit cost when the periods differ. Match dates and separate fixed charges, other known use and uncertain allocations. Label estimated consumption instead of presenting it as a meter reading.

Review repeated free restarts as a service and cost issue. They can consume resources without revenue and may indicate a machine problem that customers experience before it appears in repair spending. Compare the affected machine's event log with complaints and maintenance work before changing prices across the whole store.

Retain machine counter readings, price versions, activity classifications, payment statements, cash counts, refunds and deposits. The monthly bridge should connect gross paid activity to net receipts while explaining timing differences and customer balances. Keep missing information in a named exception list with a next action.

If software exports change, confirm that their event definitions still match the previous period. A new field labeled transactions may represent payments rather than cycles. Test a few known machine events against the report before trusting a new total, and preserve the old export that supported the closed period.

Use the completed reconciliation to identify a specific operating decision: repair a machine with repeated restarts, correct a price setting, improve collection timing or investigate a genuine cash difference. Revenue should reach the books from an explainable chain of activity and payment evidence, with the customer balance and refund obligations still visible.