Admin + Billing SOP Kit FAQ | Deposits, Invoicing, Collections
LIGHTMEN SYSTEMS (BY LIGHTMEN PAINTING)

Admin + Billing SOP Kit FAQ: deposits, invoicing, collections.

The goal isn’t to “win arguments.” The goal is to remove arguments from your week. Here are the edge cases people hit when they finally enforce billing like a system.

Deposits Milestone invoicing Autopay Refunds / cancels Collections cadence
FAQ

Answers to the stuff that actually happens.

These answers are written to be enforced. If you want “whatever works,” you already have that — and it’s why your A/R feels haunted.

Deposits

Do I really need a deposit policy?

Yes. Deposits protect schedule integrity and stop you from financing jobs. The kit standardizes what “scheduled” means and gives language that doesn’t invite negotiation.

See the install steps →

Invoicing

When should I invoice—start, milestones, or end?

The clean pattern is: deposit + milestone invoicing + final invoice tied to documented closeout. “Invoice at the end” turns you into a bank.

Pair this with Job Closeout Checklist →

Proof

What does “paid” actually mean?

“Paid” is when funds are received/cleared (or autopay processed), not when someone says “it’s coming.” The kit includes a definition so your team stops treating promises like payments.

Cancellations

What if a client cancels after we’ve scheduled them?

You need a consistent boundary: what’s refundable vs not, and what fees apply once scheduling/resources are committed. The point is clarity—so cancellations don’t become emotional arbitration.

This is where templates matter: Digital Assets Pack →

Refunds

How do refunds work without inviting abuse?

Refunds should follow a written policy and documented event trail. The kit gives guardrails so you can be fair without training clients to escalate for discounts.

Collections

What’s the best collections cadence?

Calm reminder → firm reminder → final notice → escalation. The kit standardizes timing and messaging so collections becomes a schedule, not a showdown.

Want it installed clean? Book help →

Discounts

How do I stop “random discounts” from happening?

Define who can discount, when, and with what documentation. If you don’t set a floor, discounting becomes the universal fix for awkward moments.

Systems

Does this work with Jobber (or any CRM)?

Yes. This is process-first. You can implement it using statuses, tags, reminders, and templates. The rules stay the same even if the software changes.

Tracking

What should I measure to prove it’s working?

Closeout-to-invoice time, A/R aging, discount frequency, refund/cancel rate, and missed deposit events. If you don’t measure, you’ll blame “the market” for process leaks.

Next-step upsell: KPI Dashboard →

Fast truth: clients don’t “hate policies.” They hate surprise. Policies reduce surprise.
Discovery

If billing is the problem, these usually connect.

Two related assets, one next-step upsell, plus your universal entry point—kept tight on purpose.

Related
Job Closeout Checklist

Billing gets easier when closeout delivers notes/photos/sign-off consistently.

Open →

Related
Digital Assets Pack

Copy/paste language for reminders, policies, and clean client messaging.

Open →

Next step
KPI Dashboard

Track A/R, payment cycle time, and leakage indicators so improvements are measurable.

Open →

Router

Choose your next page.

Match your intent. Move fast. Don’t wander.

I’m deciding