SnowBossPro Blog — Snow Removal Invoicing

Per-Push Billing: How Invoicing Software Charges Each Plow

Per-push billing is the most common way snow contractors charge, and it is deceptively hard to get right on paper. Every time a crew clears a property counts as one billable push, and a heavy storm may justify two or three pushes on the same account in a single day. Get the count wrong and you either shortchange yourself or overbill a client who will dispute it. snow removal invoicing software solves this by making the push itself the billable unit — each logged plow becomes exactly one charge at the account's agreed per-push rate, with nothing counted twice and nothing forgotten.

Every Logged Push Is One Line Item

When a driver marks an account complete on the mobile app, the software records a push: which property, what time, which crew, and often a proof photo. That completed push maps directly to a per-push charge at the rate stored on the account. If the account is billed at 55 dollars a push, the invoice line is 55 dollars, generated without anyone typing it. Multiple pushes in one storm produce multiple lines, each stamped with its own time, so a customer who questions the bill sees exactly when each clearing happened.

This is where per-push billing usually falls apart in a spreadsheet. Crews remember the big storms and forget the 2-inch overnight events. The invoicing software does not forget, because the invoice is built from the log, not from memory.

Handling Multiple Pushes Per Storm

Serious storms require re-pushes — you clear a lot at midnight, it snows another four inches, and you clear it again at 6 a.m. Per-push invoicing captures both as separate billable events on the same day. The office can review the sequence before sending, catch any duplicate a crew accidentally logged, and send a clean invoice that reflects real work. That defensibility is worth money: property managers scrutinize multi-push storms, and a time-stamped, photo-backed line item ends the argument fast.

Batch It After the Storm

The payoff comes after the event. Instead of invoicing 80 accounts one at a time, you batch-invoice every account that got a push, and the system charges cards on file automatically. Balances update instantly. What used to be a week of billing becomes a few minutes, and the money starts arriving while the snow is still on the ground.

Proof Behind Every Push

Per-push billing invites scrutiny because the customer is counting your clearings, so each push needs to be defensible. The mobile log captures the time of each completion and a proof photo of the cleared surface, and both attach to the invoice line for that push. When a client questions whether you really pushed twice during an overnight storm, you are not arguing from memory — you are pointing at two time-stamped photos hours apart. That documentation turns a potential dispute into a closed question and protects the revenue the push represents.

Over a season, photo-backed push logs also protect you from liability claims. A record showing you cleared a lot at a specific time is exactly the evidence that matters if a slip-and-fall claim ever lands on the account.

Set Rates Once, Bill Them Forever

The efficiency of per-push billing comes from setting the rate once and letting the software apply it automatically. Each account carries its per-push price, drawn from the estimate the customer accepted, so every push at that property bills the agreed amount without anyone re-checking a rate sheet. New account, new rate; the platform remembers it. That consistency means storm three bills exactly like storm one, and a busy office never has to look up what a given driveway charges at 4 a.m.

Reviewing a Storm Before It Bills

Automation earns trust by leaving you the final check. After a storm, per-push invoices land in a review queue showing account, push count, times, rate, and photos, so you can catch a driver's accidental duplicate log or add a salt charge before anything sends. The software assembles the tedious part — hundreds of correct push lines — and you make the judgment calls. That balance is what makes it safe to bill same-day at scale rather than sitting on invoices for a week to double-check them by hand.

Catching a mistake in review is far cheaper than clawing back an overcharge from an annoyed commercial client later, which is why the queue matters as much as the automation.

Per-Push Cash Flow

Per-push is the model most exposed to slow billing, because revenue only exists once each clearing is invoiced. Every push you fail to bill promptly is money aging while your costs are already paid. Pairing per-push billing with auto-invoicing and card-on-file collapses that gap: the logged push becomes an invoice and the stored card is charged, often the same night. For a per-push operation, that speed is the difference between a big storm funding the next one and a big storm you are still collecting on in March.

Start Billing Per Push Today

Getting per-push billing running is not a heavy project. You import your accounts, set each one's per-push rate — often straight from the estimate the customer accepted — and store a card on file at signup. From the next storm forward, every logged push bills itself at the right rate. There is no complicated configuration standing between you and same-day per-push invoicing, which is why most contractors are billing correctly within their first storm on the platform.

A 14-day trial lets you run a live storm end to end before committing, so you can watch push logs turn into charged invoices with your own accounts. Testing per-push billing during actual snowfall is the only proof that matters, and it is exactly what the trial is for.

For the previous piece in this series, read What Is Snow Removal Invoicing Software? A Billing Guide.