How dock companies get paid without an invoicing system
You do not need invoice numbers or a QuickBooks sync to collect. You need the job to close, the work shown, and a button to pay.
· 5 min read · updated August 20, 2026
Somewhere in the growth of most dock companies, somebody suggests the business needs a real invoicing system. Numbered invoices. Aging buckets. A sync to QuickBooks. Statements at month end.
For this trade that’s nearly always a mistake — an expensive apparatus built for a problem you don’t have. Accounts receivable exists to manage a gap between doing work and being paid for it, across many obligations, over long terms, with partial payments and disputes. A dock install is one visit, three or four figures, and a homeowner with a card. The gap A/R was invented for barely exists.
What accounts receivable is actually for, and why a dock install isn’t it
A/R is a real answer to a real problem: a contractor carrying six-figure progress billings on a build, over months, against a procurement department. Every part of that apparatus — the numbering, the aging buckets, the statements — exists because the gap is long and the obligations are many.
Your gap is the time between the crew leaving the property and the customer opening an email.
Charge on completion: the whole system in one sentence
The job closes, the customer gets an email with the line-by-line detail, the crew’s photos and a button to pay. If it’s paid, it’s done. If it isn’t, it’s on a short list of jobs with a balance. That’s the entire billing system a dock company needs.
What you give up, and what you stop maintaining
Being honest about it: you give up invoice numbers and the accounting sync that keeps them agreeing with something else. In exchange you give up maintaining them, reconciling them and paying for that sync. What you do not give up is collecting. This piece originally said you gave up statements, aging reports and reminders too — that was true when it was written and is not true now. LakeOps ages what is owed, sends statements, and will chase on a schedule and add a late fee if you switch those on. Not issuing invoices was never meant to mean not collecting.
The one thing that genuinely matters — knowing who owes you what — is a list, not a subsystem. Completed jobs, minus what’s been paid, sorted by size.
Most billing arguments aren’t about the amount — they’re about what got done
The customer wasn’t there. They showed up at the weekend and saw a dock. A bill that says “Spring Install — $1,240” invites a phone call.
A bill that lists six dock sections, a 4,000-pound lift and a canopy, with the crew’s photographs of each, doesn’t. Tracking every piece on its own is a billing feature before it’s an operations feature.
Send it the day the work is done, not at month end
The dock is the freshest thing in the customer’s mind on Tuesday and forgotten by the thirtieth. Nothing in a reminder sequence recovers what you lose by waiting three weeks to ask.
And when only half of it got done
Charge-on-completion has one obvious failure mode and it is worth being explicit about: the fork barge sets the dock and the crane barge is not coming until Thursday. Bill that on Tuesday and you have asked a customer to pay for a lift that is still on a trailer in your yard. The rule has to be that the bill waits for the last piece — in LakeOps the job physically cannot close while a piece is still open, and a piece that will not be done gets skipped with a reason instead, which is not billed.
The cost of waiting is silence, so fill it. At the end of a day, any customer whose work was started and not finished gets a short note: what is in the water, what is still to come, nothing to pay yet. No figure on it — the moment a number appears in a progress note it becomes a bill in the reader’s head, and the real one three days later then looks like a second charge.
Offer bank transfer ahead of card, and why it matters on a four-figure bill
A bank transfer costs a fraction of what a card costs on a four-figure bill, which is why the payment page offers it first. The customer doesn’t care which one they use. Put your own processor statement next to a season of dock bills and you’ll care a great deal.
Where your accountant still fits
None of this replaces your accountant — it just stops pretending the field software is one. The handoff is the completed-work report: one row per piece, with the customer, property, service, quantity, price, on-site minutes, what was collected and what’s outstanding. CSV for the bookkeeper, and it prints for the file.