How to Split One Project Across Two Billing Periods Without Losing Track of What You Already Billed

Some projects do not fit neatly inside a calendar month. The work starts in week three, runs past the month end, and you are suddenly staring at a time log that crosses two billing periods. Most freelancers handle this by guessing. They end up either double-billing something small or quietly eating hours they already earned.

This is fixable. It just requires one habit you set up before the confusion starts.

Why This Breaks in the First Place

The problem is not the project. The problem is that most people treat a time log as a single running total. They look at the whole number at invoice time and round to something that feels right. When a project crosses a billing cutoff, that total includes hours you may have already billed in a previous invoice, hours you plan to bill now, and hours you are holding for later.

Those three buckets look identical inside a timer. Nothing in the log tells you which is which unless you built that structure in at the start.

Set a Billing Cutoff Tag Before the Month Ends

In Time-Trak, the fastest fix is to use your project notes or entry descriptions to mark a cutoff point. Before the month closes, filter your logged hours by date range and note the total. Write it down somewhere attached to the project, even just in the project description field. Something like: "Billed through Oct 31: 14.5 hours at $95."

That note costs you two minutes. It saves you from reconstructing a billing history three weeks later when the client asks a question.

Invoice by Date Range, Not by Project Total

When you go to generate an invoice, do not pull the full project total. Pull hours by date range. In Time-Trak you can filter entries by date before you build the invoice. Use that filter every time a project runs across a period boundary.

Invoice one covers hours logged from project start through the billing cutoff. Invoice two starts the day after. You never mix the two pools, and you never have to remember what you already sent.

Keep a Simple Billing Ledger for Long Projects

For any project running more than six weeks, keep a one-line billing ledger. A plain text note works fine. List each invoice you sent, the date range it covered, the hours included, and the total charged. Three columns. Took you thirty seconds per invoice to maintain.

When the project closes, you have a clean record of every billing event. If a client questions anything, you can walk them through it date by date. No reconstructing. No second-guessing your own memory.

What Automatic Screenshots Add Here

One thing that gets messy with split billing is proving what happened in which period. A client who was billed in October and again in November sometimes wonders if they are paying for the same work twice. Automatic screenshots in Time-Trak give you a timestamped record of actual activity during each period. If the question comes up, you can show exactly what was happening on exactly which days. That is a different kind of evidence than a time entry description. It is harder to argue with.

The Setup That Prevents All of This

If you know upfront that a project will run across a billing period, build the phase structure before you start. Create two phases in Time-Trak, one for each billing window. Log hours to the correct phase as you work. When invoice time comes, each phase gives you a clean total with no math required.

It takes five minutes at project kickoff. It removes every question at invoice time.

Split billing is not complicated. It just requires that you decide how you are going to handle it before the month flips, not after you are already staring at a number that does not add up.

Track your time, bill every minute.

Time-Trak is a native Mac and Windows time tracker with a floating timer, automatic screenshots, and one-click invoicing.

Free during beta.

macOS + Windows · Floating widget · Auto screenshots