Pay on site vs invoice later: which gets a trade shop paid

It's a Tuesday afternoon. Your tech has just cleared a kitchen drain and swapped a leaking supply line, and he's packing the auger back into the van. The homeowner follows him to the driveway and asks what she owes. He knows the drain price. The supply line part he'd have to look up. He isn't comfortable naming a number he might get wrong, and there's no card reader on his phone anyway, so he says the office will send a bill.

The office sends it Thursday. She pays it the Tuesday after, or the one after that. Run every service call that way for a week and the work gets done quickly while the money trickles in.

Most small shops I talk to never chose between collecting on site and invoicing later. They do whichever one the tech is comfortable with that day.

The short answer

Collect on site for residential service calls where the price comes out of your price book: drain clearing, a faucet, a water heater flush, a diagnostic and repair. Invoice later for commercial accounts, property managers, insurance work, big installs billed in stages, and any job where the final scope is still in question when the truck leaves.

Most shops need both. Decide it by job type, write the rule down, and set things up so the tech isn't the one deciding at the door.

Pay on site vs invoice later, side by side

What the wrong choice costs

Invoicing later on a job where you could have collected costs more than the wait. You float the parts and the labor until the bill gets opened. Items that happened at the house drop off the invoice, because whoever writes it on Thursday only puts down what they're sure of. And a bill that arrives days after the work gets read as an interruption, which turns collecting it into its own job of texts and calls. I went through that pattern in detail in why Batavia plumbers get paid late.

Forcing payment on site where it doesn't fit causes different trouble. A property manager who pays on net terms doesn't want your tech asking a tenant for a card. On a staged install, collecting the balance at the door before the inspection passes is asking for a dispute. And a tech without a price book ends up making up numbers in the driveway, and a made-up number usually comes out low.

What setting up both looks like

These are the steps I take when I build this for a service shop.

1. Tag each job type with how it gets paid. Service calls from the price book get "collect on site." Commercial accounts, property managers and staged installs get "invoice." The tag comes from the job type and the customer record, so nobody has to remember it.
2. Put the price book on the tech's phone. At job close the tech picks the work done and the parts used, and the total builds itself from your rates. Nobody has to name a number they aren't sure of.
3. Send the payment to the customer's phone. On a collect-on-site job, closing it texts the customer a receipt-style summary with a pay link, and they pay by card or bank transfer while the tech is still there. The tech never handles the card.
4. Let the link fall back to an invoice. If she wants to wait for her husband to look it over, the same link stays open as the invoice, and reminders start on the schedule you set. They stop the moment it's paid.
5. Draft the invoice-later jobs at close. The office gets a draft the same afternoon, built from what the tech logged, and approves and sends it with a pay link. Nothing waits on Thursday.
6. Keep one list of open balances by age, so you can see what you're carrying.

For the wording on those reminders, the payment reminder messages post has short texts for before and on the due date, and the overdue invoice email post covers what to send once a bill is late.

A Chicago-area pool service company I work with takes payment through Stripe on their own site, so the customer pays in the same place they see the charge, and nobody retypes the payment into another system afterward. A plumbing or HVAC shop has more job types than a pool route. The payment side works the same way.

What stays human

The price is yours. Whether the second trip gets billed or the trip charge gets waived for a customer whose basement just flooded is a call made by someone who knows the job and the customer. The price book gives the tech a starting number, and the discounts are up to you.

The words at the door belong to the tech, and it helps to hand them a line. Something like "The total's on your phone now, and you can pay it right there or whenever you're ready today" makes asking about as hard as handing over a receipt. Some techs will still hate asking, and that's something you work through with them on a ride-along.

Disputes stay human too. If a customer replies to the pay link with "it's still dripping," that message goes to a person and the reminders stop. You set that rule once, during the build.

So do terms. Deciding which commercial customers get net 30 and which ones pay at completion is a judgment about the relationship, and it's yours.

When this won't change much

If your shop already collects at the door on every service call and invoices the rest the same day, you have this solved. If most of your revenue is new construction on a general contractor's pay schedule, the bottleneck is their cycle, and faster paperwork only helps a little. And if prices live in your head instead of a price book, writing them down comes first. That part is yours. Once the price book exists, the rest can be built.

Where to start

If payments land whenever someone gets around to billing, the free 20 minute process audit is where I'd start. We go through one normal week of jobs, sort them by how each one should get paid, and find where the money is waiting. Builds start at $500 one time, then a flat monthly from $99 after an included run-in period, cancellable. More on the plumbing page and the HVAC page. Book the audit here.