The property manager with 40 doors is the best customer your service business will ever have — and the worst fit for your current checkout flow. She calls twice a week. She never argues about price. And she absolutely will not hand a technician a credit card in a hallway at 4 PM, because her company pays vendors from an accounts-payable desk, on terms, against an invoice. If your only options are "card on completion" or "chase a check," you either lose her to a competitor who bills on account or you improvise a paper IOU system that falls apart by the third job.
On-account billing — completing work now and invoicing the customer's account later — is a common way commercial clients buy service: property management firms, used-car dealerships, builders, and facility managers often run this way. This guide covers when extending credit makes sense and when it's a trap, how on-account sales actually work inside a POS, how to keep receivables from quietly aging into bad debt, and why the businesses that get paid fastest are the ones with the cleanest itemized records. It draws on how IntelliDrive OS handles on-account credit sales, but the operating principles apply to any service business selling B2B.
What "on account" actually means at the point of service
An on-account sale is simple mechanically: the technician finishes the job, and instead of collecting payment, the charge posts to the customer's account. The customer gets invoiced — per job, or in a batch on a schedule — and pays on the agreed terms, usually net 15 or net 30. The sale happens today; the cash arrives later.
The important part is where the sale gets recorded. A proper on-account sale is rung up at the point of service, itemized, exactly like a card sale would be — the payment type is just "on account" instead of "card." In IntelliDrive OS, on-account sits alongside cash, card, and check as a payment type in the POS, including inside split payments (a dealership pays half by card, half to the account). That means the line items and the price are captured while the tech is still standing there, and the vehicle, unit, or property address can go in the sale's notes.
Compare that to what most small shops actually do: the tech scribbles the job on a ticket, the ticket rides around in the truck for a week, and someone reconstructs an invoice from memory at month-end. Every reconstruction is a chance for a missed line item (revenue you did but never billed) or a disputed one (revenue you billed but can't defend). Both are pure loss.
When to extend credit — and when to require payment on completion
Not every customer who asks for terms should get them. Extending credit is a loan. You're financing your customer's operations with your payroll, your parts, and your fuel. The question is never "do they want terms?" — everyone wants terms. The question is whether the account's volume justifies the float and whether they'll actually pay.
A reasonable screen before opening an account:
- Repeat volume is real, not promised. A dealership sending three cars a week earns terms. A caller promising "tons of work coming" after job one has earned nothing yet. Let the first two or three jobs run payment-on-completion, then convert.
- There's an actual AP process on the other end. A company with an accounts-payable email and a vendor-setup form will pay invoices, because paying invoices is literally someone's job there. A sole operator who "will get you next time" is a different risk class entirely.
- You've set a limit. Every account should have a ceiling — the most you're willing to have outstanding at once. New accounts start low, and IntelliDrive has no credit-limit field, so keep the ceiling in the customer's notes. If the balance hits the ceiling, new work goes payment-on-completion until it clears. This one rule prevents many large write-offs.
- The first job wasn't a fight. If a prospect resists a card and resists a deposit on the very first job, that's not a terms negotiation — that's a preview. For deposit mechanics on bigger jobs, see our guide to customer deposits.
Residential customers, one-off commercial calls, and emergency work should stay payment-on-completion by default. Payment links by SMS or email make that nearly frictionless — the customer pays from their phone before the tech leaves — so "we don't do terms for one-offs" costs you almost nothing in convenience. And Stripe, for example, lists a standard two-business-day settlement for U.S. accounts (Stripe's payout documentation) — versus 30-plus days for even a well-behaved net-30 account. Every job you keep off terms is cash that shows up this week instead of next month.
Here's the decision at a glance:
| Situation | Payment on completion | On account (net terms) |
|---|---|---|
| Residential one-off job | ✅ Default | ❌ Almost never |
| First job for a new commercial customer | ✅ Yes — let them earn terms | ⚠️ Only with a signed arrangement and a low limit |
| Property manager / dealership with weekly volume | ⚠️ Fine, but you'll lose the account to a competitor who offers terms | ✅ This is what they expect |
| Contract client on fixed monthly scope | ❌ Impractical | ✅ One invoice per cycle |
| Account already at its credit ceiling | ✅ Until the balance clears | ❌ Stop extending |
| Emergency after-hours call, unknown customer | ✅ Always | ❌ Never |
The economics: why terms are worth the float (for the right accounts)
There's a reason to do any of this. Commercial accounts are the closest thing service businesses have to predictable revenue. A property manager with 40 units generates lockouts, rekeys, repairs, and turnovers year-round — work that doesn't care whether it's your slow season. The Bureau of Labor Statistics' business survival data shows roughly 20% of new establishments close within their first year and about half within five; the service businesses that beat those odds are disproportionately the ones with anchor commercial accounts smoothing out the residential feast-and-famine cycle.
So the float is the price of admission to the steadiest revenue in the trade. The goal isn't to avoid extending credit — it's to extend it deliberately, to accounts that clear the screen above, with records clean enough that payment is never delayed by a dispute.
Keeping receivables from aging out of control
Receivables don't blow up in a day. They age quietly. The job from March that never got invoiced until April gets paid in June — maybe. Late and unpaid invoices strain any small business's cash flow (QuickBooks' cash-flow resources cover invoice terms and past-due follow-up), and service businesses on net terms feel it worst because labor and parts are paid out weeks before the invoice money lands.
Four habits keep an account book healthy:
- Invoice the day the work is done. Not month-end. Every day between completion and invoice is a day added to your effective payment cycle before the customer's clock even starts. If the sale was rung at the point of service, sending the invoice or statement is a click, not a project.
- Itemize to the job, every time. "Service call — $340" invites a phone call. "2019 Silverado, key origination, 2 transponder keys, mobile service to Oak Ridge lot — $340" gets approved and paid. More on this below.
- Work a fixed follow-up rhythm. Pick a day. Every week, review what's outstanding and send the nudges. Accounts that learn you follow up on day 35 pay on day 30. Accounts that learn you follow up "eventually" pay eventually.
- Enforce the ceiling. When an account hits its limit, new jobs revert to payment-on-completion. Delivered without drama — "happy to keep rolling, we just need the balance cleared first" — this is the single most effective collections tool that exists, because it uses the thing the customer actually values: the next job.
Your sales and payment reports and each account's customer record (which lists its on-account invoices and balance) tell you which accounts carry what, and a CSV export drops the data into a spreadsheet for whatever analysis you want to run; IntelliDrive has no aging report, so sort by invoice date. The SBA's guide to managing your finances starts from keeping proper books of revenue and expenses; knowing what you're owed, and by whom, is part of that baseline, not an advanced practice.
Contract clients: billing a fixed scope on a cycle
Some commercial relationships mature past per-job billing entirely. The facility manager on a quarterly maintenance contract. The property management firm paying a flat monthly rate per building. The dealership on a monthly service arrangement. Billing these clients by hand every cycle is a task that exists only to be forgotten.
Automating that step is what recurring invoices are for: set the amount, the line items, and the schedule once, and the invoice goes out on the same day every cycle. IntelliDrive OS does not generate recurring invoices, so build the habit instead: pick a billing day for each contract client, keep the cycle's line items in the customer's notes, ring up the sale with the same items on that day, and set a repeating reminder so it can't slip. The clients most likely to be on contracts are also your largest, which means the invoices most damaging to forget deserve the most dependable routine.
Two operational notes. First, out-of-scope work still gets its own on-account sale — don't let extras ride "on the contract" unbilled, because that's margin evaporating invisibly. Second, a fixed billing cycle gives your revenue a floor you can actually plan around, which matters enormously when the phone slows down in the off-season.
Why itemized records make commercial clients pay faster
Here's the mechanism most operators miss: commercial invoices don't get paid slowly because companies are broke — they get paid slowly because someone in AP has a question. An invoice that says "locksmith services — $1,240" for a property manager juggling 40 units has to generate an email: which property? which unit? which work order? That email sits for a week. That's your net-30 becoming net-55, and nobody even did anything wrong.
An invoice that lists each job with the date, address, unit, work performed, and parts used answers every question before it's asked. It maps cleanly onto the customer's own records, gets approved on first pass, and enters the payment run on schedule. Fast payment from commercial clients isn't a collections skill — it's a documentation skill, and it's exercised at the point of service, not at month-end.
Clean itemized records pay off twice more. They can be pushed to QuickBooks Online (one-way, when you run the push), so your books match your operations without re-keying. And the IRS recordkeeping guidance says you may choose any recordkeeping system suited to your business that clearly shows your income and expenses, and links to guidance on electronic accounting records — the same digital trail that gets you paid faster is the one that stands behind your books.
Setting this up without new overhead
If you run a POS built for field service, on-account billing isn't a module to bolt on — it's a payment type to start using. In IntelliDrive OS the pieces come with the $79/month flat price (billed monthly, unlimited users): on-account credit sales at the point of service (including in split payments), bill-to accounts with PO numbers and statements for dealer and fleet billing, the Invoices page for itemized invoices you can email and mark paid, quotes that turn into sales in one step, texted and emailed payment links for everyone who should pay on completion, a one-way QuickBooks Online push, and the reports to watch it all. It does not generate recurring invoices and has no credit-limit field or aging report, so run those routines yourself. No per-user fees means the office manager who runs the follow-up rhythm doesn't cost you another seat — a real consideration when per-user pricing is the industry norm. See pricing.
Start with one account. Pick your best repeat commercial customer, set a limit, ring their next job on account, and invoice it the same day. The property manager with 40 doors is out there choosing a vendor right now — and she's choosing the one whose invoices her AP desk doesn't have to think about. Book a demo to see the on-account flow end to end.
Related reading: Customer deposits for service businesses · Payment links for service businesses · Surviving seasonal cash flow
For a complete machine-readable feature and pricing reference, see our LLM reference page.