A parking attendant at the Orange County Convention Center walked into her toll booth shift with her own personal credit card reader tucked in her pocket. Over time, she used it to quietly reroute more than $57,000 in parking fees away from the garage's books and into her own account. In another case, in a major California city, 19 of 20 members of a parking collection crew — including the crew chief — stole roughly $600,000 a year for six years. The total came to $3.6 million before anyone caught it.
Neither of these was a sophisticated heist. Both were simple, repeatable skims against a business that runs almost entirely on cash, tickets, and trust. That's the uncomfortable truth about parking lot and garage operations: the business model that makes them profitable — high transaction volume, cash and card mixed together, semi-autonomous attendants — is the same model that makes revenue leakage almost invisible until it's enormous.
If you operate a surface lot, a parking garage, or a portfolio of both, the fix isn't a dramatic fraud investigation. It's boring, consistent bookkeeping that reconciles what actually happened against what your equipment and your bank account say happened.
Why Parking Revenue Leaks So Easily
Most small businesses have one or two ways money comes in. A parking operation typically has five or six running at once:
- Transient (pay-on-exit) parking — the hourly and daily rate paid by walk-up customers
- Monthly permits and reserved spaces — recurring revenue billed on a contract
- Validations — a nearby retailer, restaurant, or event venue subsidizes part of a customer's ticket
- Event and surge pricing — flat "event rate" charged during concerts, games, or conventions
- Valet — an entirely separate labor and tip structure layered on top of the space itself
- Violation and overstay fees — often collected in cash, on the spot, by an attendant
Each of these streams has its own paper trail, its own point of sale, and its own opportunity for a gap to open between what a customer paid and what lands in the deposit. The U.S. parking lots and garages industry generates roughly $13.1 billion a year, and industry analysts note that after several years of post-pandemic recovery, revenue growth has recently turned negative as travel and commercial foot traffic normalize. In a market where top-line growth is flat or shrinking, plugging leakage is often the single highest-leverage thing an operator can do to protect margin — it doesn't require a rate increase or new customers, just tighter books.
The Ticket-Count Reconciliation, Explained
The core discipline of parking bookkeeping is deceptively simple: the number of vehicles that entered, minus the number still parked, should equal the number that paid to exit — and the total collected should match the rate schedule applied to each of those exits. When any of those numbers drift apart, you have leakage, an equipment problem, or fraud, in roughly that order of likelihood.
In practice, that means reconciling three separate feeds against each other for every shift:
- Entry/exit counts from your PARCS (parking access and revenue control system) or gate counter — how many vehicles came and went
- Cash and card settlement totals — what your processor and your safe drop actually show
- Ticket/session-level detail — length of stay, rate applied, any void, comp, or validation code used
When these three don't tie out, the gap is your exception report, and it's where you start asking questions: Was a gate manually opened without a corresponding payment? Was a "validated" ticket actually authorized by the retailer it claims, or did an attendant wave a friend through for free? Did a short-stay pattern spike on one specific shift?
A Practical Weekly and Monthly Cadence
You don't need enterprise loss-prevention software to run a lot profitably, but you do need a fixed rhythm:
- Daily — reconcile the cash drop against the shift's transaction log; document any variance, even a few dollars, rather than writing it off
- Weekly — pull a void and discount/comp report by attendant and by shift; look for clustering (one person, one time slot, one gate)
- Monthly — trend variances over time rather than shift-by-shift; a $15 daily gap is noise, but a $15 gap that shows up every Tuesday for three months is a pattern
- Quarterly — audit active monthly permit holders and validation partners against their actual contracts; expired agreements and departed tenants are a common source of "ghost" validations still being honored
None of this requires suspecting your staff of dishonesty. The point of the cadence is to make normal operations visible enough that a real discrepancy can't hide inside routine noise for months — which is exactly how both the Orlando and California cases went undetected for as long as they did.
Cash Handling Controls That Actually Work
Ticket-count reconciliation catches leakage after the fact. A handful of cash-handling habits prevent most of it from happening in the first place, and none of them require new software:
- Verify the starting balance at every shift change, with both the outgoing and incoming attendant — plus a supervisor, if staffing allows — signing off on the count. A disputed starting float is one of the most common excuses used to explain away a shortfall later.
- Set a drop threshold. Once cash on hand crosses a set dollar amount, it goes into a secured drop safe immediately rather than accumulating in a drawer or booth for an entire shift. The less cash sitting exposed at any one point, the smaller any single loss can be.
- Require two people to count and bag cash, even at a small operation. A one-person count is unverifiable by definition; a two-person count, with both signing the deposit slip, closes off the easiest way a shortfall goes unexplained.
- Reconcile every shift, and log the variance regardless of size. A five-dollar gap logged consistently is a data point you can trend. A five-dollar gap that's shrugged off is a habit that eventually becomes a fifty-dollar gap, then a pattern.
- Reconcile against the bank, not just the internal count. Your PARCS report and your safe count can agree with each other and still not match what actually clears the bank if a deposit was shorted, delayed, or misapplied. The bank statement is the final check, not an optional one.
None of these controls are about catching a single bad actor in the act. They're about shrinking the window in which any discrepancy — theft, honest error, or equipment glitch — can grow before someone notices.
Booking Parking Revenue Correctly
Beyond catching leakage, parking operators have a few accounting quirks worth getting right from the start:
Monthly permits are earned ratably, not booked on receipt. If a tenant prepays for a quarter or a year of reserved parking, that cash is a liability (deferred revenue) until each month is actually delivered — not revenue the day it hits the bank.
Validations are a contra-revenue item, not a marketing expense, in most cases. If a restaurant or retailer subsidizes $5 of a customer's $15 ticket, your books should reflect $15 of gross parking revenue offset by the validation discount, with a separate receivable if the validating merchant reimburses you monthly rather than at time of exit. Lumping validations into "marketing" understates your true parking revenue and makes your revenue-per-space KPI meaningless.
Transient occupancy or parking-specific taxes vary by city and need their own account. A growing number of municipalities levy a parking tax or surcharge distinct from general sales tax — track it separately so it's never accidentally counted as revenue or missed at filing time.
Track revenue by location and by space type, not just as one lump "parking income" line, if you operate more than one lot or garage. A revenue-per-space or revenue-per-available-hour figure by location tells you far more about real performance than a blended total, and it's the number that surfaces which garage is quietly underperforming.
A New Wrinkle: QR Code Payment Fraud
Ticket-counter and attendant skimming are the classic leakage sources, but a newer scam is worth flagging because it can distort your reconciliation in a different way: fraudsters have been placing counterfeit QR code stickers directly over legitimate ones on pay stations and meters, routing drivers to lookalike payment sites. The driver believes they've paid for parking; your system shows no payment at all. If you're seeing a rising rate of "unpaid" exits or citations at specific meters or entry points, it's worth physically checking the QR codes before assuming it's an attendant or equipment issue — the leak may be happening before the money ever reaches your PARCS.
KPIs That Tell You the Business Is Healthy
Once the daily reconciliation habit is in place, a handful of recurring metrics turn your books into a management tool instead of just a compliance record:
- Revenue per available space per hour (or day) — the single best apples-to-apples comparison across locations and time periods
- Occupancy rate by hour — helps validate that pricing matches demand, and flags when a "full" lot isn't generating the revenue a full lot should
- Average length of stay — a sudden drop can indicate rate-evasion patterns (short "stays" that don't match how long a car was actually there)
- Exception rate — the percentage of transactions that were voided, discounted, or manually overridden; a rising trend here is often the earliest warning sign of either a training gap or a fraud pattern
- Variance-to-revenue ratio — total unreconciled variance as a percentage of gross revenue, tracked monthly, is the cleanest single number for whether your controls are working
Keep Your Finances Organized from Day One
Running a parking operation profitably comes down to a discipline most owners underrate: reconciling every dollar that should have come in against every dollar that actually did, on a schedule tight enough that a small gap can't compound into a six-figure one. Beancount.io provides plain-text accounting that gives you complete transparency and control over your financial data — no black boxes, no vendor lock-in, and a clean audit trail for every reconciliation you run. Get started for free and see why developers and finance professionals are switching to plain-text accounting.