Skip to content
BizBinder
Early access open Get early access

Guide

Staying organized · 8 min read

Catch up on your invoicing — the weekly sweep that gets you paid

A finished job is not money until you invoice it. The pile of unbilled work is not late paperwork — it is work you have already done for free until an invoice exists, and every day it waits is a day added in front of your own payment terms, not inside them.

The short answer

A finished job is not money until you invoice it — the unbilled pile is free labor until then, and every day you wait sits in front of your payment terms, not inside them. Clear a backlog oldest first, invoicing what you can prove and asking about the rest. Then run one weekly sweep, sorting every finished job into invoice now, chase a detail, or wait on sign-off.

A finished job feels done the moment you pack up the van. It is not done, in any sense your bank account cares about, until an invoice exists for it. Between those two moments sits a pile that grows quietly: three jobs this week, two more from last week that never made it onto an invoice, one from a month ago you keep meaning to get to. None of that is late paperwork. It is work you have already done, for free, until you bill it.

Why the pile builds

The backlog rarely comes from one big mistake. It comes from four small, ordinary ones, repeated:

  • There is no single list of finished jobs. If "done" only lives in your head, or is scattered across a few texts and a paper diary, a job can be genuinely finished and still invisible to whatever process is supposed to invoice it.
  • Nothing marks a job "done." Without a clear point where a job moves from "in progress" to "ready to bill," a finished job just sits in the same pile as everything else you're still working on, with no signal telling you to act on it.
  • One missing detail blocks the whole invoice. An extra the client asked for on site, a photo you meant to take, a purchase order number you never got — a single gap is enough to make you put the invoice down and mean to come back to it later.
  • The job is waiting on someone else's sign-off. A main contractor who hasn't confirmed the work, a client who wants to "have a look" before you bill — the job is finished on your end but stuck until someone else acts.

The first two causes are about tracking; see keeping track of jobs without a spreadsheet for a system where a finished job has one obvious place to land. The last two are about the invoice itself. What to put on an invoice covers the fields worth confirming before you send it.

What the pile actually costs

The real cost is not a fee or a missed opportunity — it's timing. Your payment terms start on the day you send the invoice, not the day the job finished. Every day you wait to invoice is a day added in front of those terms, not absorbed inside them. A job with 14-day terms, invoiced three weeks late, doesn't get paid three weeks after it finished — it gets paid five weeks after, because the delay you added sits before the clock even starts.

Age also weakens the invoice itself. A photo, a job sheet, and your own memory of what happened are all sharper the week a job finishes than they are two months later, and so is the client's memory of agreeing to it. A late invoice asks for the same money with a weaker argument behind it, sent to someone who remembers the job less clearly than you do. This is the same gap aged receivables measures on the other side of the invoice. The older an unpaid bill gets, the harder it is to collect. An unbilled job is the same problem one step earlier: it hasn't even started aging as a receivable, because it was never billed at all.

None of this is abstract once you add it up. Money already earned, sitting unbilled, is money your own cash flow can't use yet — it isn't in your bank account, it isn't even an invoice a client could pay, it's just work that happened.

Clearing the backlog once

Treat the backlog as a one-time cleanup, separate from the weekly habit that stops it coming back. Work oldest first. An old job is losing the most ground, in both the terms-timing sense above and in how clearly you and the client both remember it.

For each job on the list, ask one question: can I invoice this right now? If yes, do it before moving to the next one. If a detail is missing — an extra, a photo, a sign-off, a purchase order number — invoice what you can actually prove happened, and ask the client for the rest rather than guessing at a number. "Everything except the extra shelf is on this invoice; can you confirm the shelf was $65 in materials so I can send a second line for it?" gets you paid for most of the job now and closes the gap on the rest, instead of holding the whole invoice hostage to one missing fact.

The weekly sweep that stops it returning

Clearing the backlog once fixes today. Stopping it from rebuilding needs a habit, and the habit that survives a busy week is a fixed slot — same day, same time, every week — where you look at one list: every job marked finished since the last sweep.

Sort each job on that list into exactly one of three states:

  • Invoice it now. Nothing is missing. Send it before you move to the next job on the list.
  • Blocked on a detail you need to chase. Note what's missing and who has it, and ask for it this week rather than letting it drift to next week's sweep.
  • Blocked on someone else's sign-off. Nothing to invoice yet, but the job stays visible on the list until that sign-off arrives — it doesn't disappear just because it's waiting.

A fixed weekly slot is short enough to survive a busy week without turning into "I'll do it when things calm down," and long enough that it isn't another daily chore competing with actual jobs. If a fixed slot in your week is the part you're missing, the printable week planner gives that slot a place to live next to your actual jobs, rather than being a task that only exists in your head.

Not sure whether invoicing is your weakest link, or something else in your admin is? The admin health check scores you across quoting, invoicing, getting paid, staying organized, and follow-up, and points you at whichever stage is actually thinnest — worth running before you assume the weekly sweep above is the only fix you need.

When to change the billing cycle instead

A weekly sweep clears a backlog that built up by accident. Some backlogs are actually a mismatch between how the work happens and how often you bill for it — in which case the fix isn't a better habit, it's a different billing cycle.

Per-job billing suits work with a clear finish line — a repair, an install, a one-off visit — where "done" is obvious and the invoice can follow immediately. Weekly billing suits ongoing or multi-visit work where waiting for a single, final "done" would mean carrying weeks of unbilled labor before you ever send a bill. Monthly billing suits a genuinely recurring arrangement — a maintenance round, a retainer — where a client already expects one invoice at the end of the month rather than one per visit. Pick the cycle that matches how the work actually finishes, not whichever one you defaulted into.

Check where you stand right now

Before you commit to a weekly sweep or a different billing cycle, it's worth seeing exactly how much is sitting unbilled today, and how old the oldest piece is — the free unbilled work check totals it up, weighted by money rather than a plain average, and hands back a sweep order: oldest job first.

Once the backlog is cleared and the weekly sweep is running, the next thing worth tightening is what happens after you invoice — see how to get paid faster for the reminder cadence that keeps a sent invoice from becoming a slow one, and work in progress for the accounting term for everything sitting in this pile before it becomes a receivable.

Common questions

How do I catch up on invoicing when I am really behind?

Make one list of every finished job with no invoice, oldest first, then work down it. Invoice what you can prove from memory, a job sheet, or a message thread. For anything missing a detail, ask the client rather than guessing, and send that invoice the moment the answer comes back.

Does a late invoice still count toward my payment terms?

Your payment terms start the day you actually send the invoice, not the day the job finished. That is exactly the problem: a job invoiced three weeks late is paid three weeks later than it should have been, even with the same terms — the delay sits in front of the clock, not inside it.

What if I cannot remember exactly what a job involved?

Invoice the part you can back up with a photo, a text, a job sheet, or your own memory of the visit, and say so plainly if a detail is missing rather than guessing at a number. A client who gets an honest, slightly incomplete invoice tends to fill in the gap; one who gets a guess that is wrong has a reason to argue the whole thing.

How often should I actually do this — daily, weekly, monthly?

Weekly is the shortest interval that survives a busy week without becoming another thing to remember every day, and the longest interval that still catches a job before the details fade. A fixed slot, the same time every week, beats trying to remember to "get to it" between jobs.

Want the unbilled pile in one place, not scattered across memory?

BizBinder does not chase the missing detail for you, and it does not decide how often you should bill. What it does is put every job marked done with no invoice yet on one list on the page you land on — so the pile you're clearing is a real list, not something you're reconstructing from memory.