Why Batavia plumbers get paid late for work already done

It is a Tuesday in Batavia. You started with a water heater swap on the east side, caught a kitchen backup around eleven, and lost the afternoon to a slab leak that turned into a four hour job. At 5:40 you are washing your hands in somebody's utility sink and the homeowner asks what they owe you.

You tell them you will send an invoice.

That invoice does not exist yet. It exists as three lines on a work order, a photo of the old heater, and a note about the expansion tank you added because the old one was shot. It becomes an actual bill on Sunday night, when you sit down with the laptop and try to reconstruct four days of work from memory.

The bottleneck sits between finishing a job and the customer having a bill in hand.

What the delay actually costs

Three things, and only one of them is obvious.

The obvious one is cash. Your payment terms do not start when you finish the work. They start when the invoice lands. Every day it sits in the truck gets added to the front of your terms, and you are the one carrying it. You already paid the supply house for that water heater.

The second is money you never bill at all. When you write an invoice from a four day old memory, you write down what you are sure of. The expansion tank you are certain about. The extra ball valve, the second trip for a fitting, the forty minutes of cleanup after the slab leak: those you half remember, so you round down or leave them off. That revenue never shows up as a bad debt. It just never gets written down, which means you cannot see it and cannot fix it.

The third is how likely you are to get paid at all. A homeowner who gets an invoice the same evening reads it as part of the job that just happened. A homeowner who gets one eleven days later reads it as an interruption to a week that has moved on. The bill has to compete with everything else on their desk, and now collecting it is a second job made of texts, voicemails, and a phone call you do not want to make.

There is also a clock the state runs that does not care about your weekend. Under the Illinois Mechanics Lien Act, a contractor who wants to protect a lien claim against other parties with an interest in the property has to bring an action or record the claim within four months of completing the work (770 ILCS 60/7). Four months sounds generous until you notice the first six weeks usually go to "I will send it this weekend" and the next six to polite follow-up. Your own situation is a question for a lawyer, not for me. The point is that the clock starts the day you pack up the truck, not the day you get around to billing.

What closing out a job looks like with a system in place

Before you pull out of the driveway, you close the job on your phone. What you did, what you used, how long you were there. Talking it out works, typing works.

From there:

• The system builds an invoice from your own price book. Your rates, your markups, your line items. It does not invent pricing and it does not pull a number from anywhere you have not set.
• Photos you already took attach to the job record, so the water heater you replaced is documented without a second step.
• The draft comes back to you for approval, usually before you are out of the subdivision. You fix a description, adjust the hours, add the line you forgot.
• You approve it. It sends under your name with a pay link, card or bank transfer, so the customer can pay from the same message that told them what they owe.
• If it is unpaid by the date you set, reminders run on a schedule you decide. They stop the moment the money lands.
• Paid, unpaid, and how long each customer takes to pay all land in one view, so slow payers are something you know rather than something you sense.

None of this asks your techs to learn a new trade. It sits between the phone, the job records, and whatever you already use to bill. The Chicago area pool service company I work with runs the payment half of this pattern: invoicing and payments go through Stripe on their own site, so the customer pays from the same place they got the bill and the record updates without anyone retyping it.

What stays with you

The number stays with you, always. Whether to eat the trip charge for a customer whose water heater failed twice in a year, whether the homeowner on a fixed income gets a payment plan, whether a job that went sideways gets billed in full. Those decisions come from knowing the customer and the job, and no system should be quietly making them on your behalf.

The uncomfortable conversations stay with you too, and they should. My rule is that reminders handle politeness and repetition, and a person handles anything that has become a conversation. Around the third unanswered reminder, that account belongs on your list, not the system's. An invoice that has gone quiet for a month is a relationship question, and relationship questions get a human voice.

Callbacks come out of the automated path entirely. If somebody replies to an invoice with "the drain is slow again," that has to reach you, not a reminder sequence. You set that rule during the build and the system follows it.

When this is not worth building

If you already invoice from the truck and collect before you leave the driveway, you do not have this problem. Keep doing what you are doing.

If most of your revenue is new construction on a general contractor's terms, your problem is somebody else's pay cycle, not your paperwork. Faster, better documented submissions help at the margin. They will not shorten a sixty day term.

And if your pricing lives in your head instead of in a price book, that has to be written down before any of this works. That part is your work, not mine. Once it exists, the rest is buildable. Builds start at $500 one time, then a flat monthly from $99 after an included run-in period, cancellable whenever it stops earning its keep. More detail on the plumbing page and on what I do for businesses around Batavia.

Where to start

The first step is a free 20 minute process audit. We walk through one normal week, find where invoices stall and where money goes unbilled, and put hours and dollars against each gap. If a system pays for itself, build it. If it does not, you keep the map either way. Start here.