Time to Invoice Without Retyping: How Friday Stopped Being Invoice Night

#Friday A, 5:47pm

The timer stopped at 5:02 but the week did not. Every consultant knows this Friday. The client work is done, the week is over, and now comes the part nobody bills for: turning the week into an invoice.

Here is how it usually goes. I know, because this was my Friday for years before I built owntime.

You open the tracker and look at the week. You have entries scattered across clients, some with notes, some without. You open the spreadsheet you built three years ago. You start retyping. Client, project, date, hours, rate. The columns do not quite match the tracker, so you do the rate math by hand. Then you remember the two hours on Tuesday that you billed at the older rate, and you fix that row. Then you hunt for the expense receipt from Thursday.

Somewhere around 9pm, the invoice goes out. It is right, mostly. You have spent four hours to bill forty, and the four hours are not on any invoice, which is fitting, because nobody should be billed for watching you retype your own week.

I am not describing a hypothetical. That spreadsheet was real, and my Friday night routine was retyping the week into it until my eyes crossed. The reason I ended up building owntime, rather than just complaining about Harvest like a normal person, is that I wanted my own Friday back. Everything in this post is the workflow I actually run now.

#The real cost is not the four hours

Every consultant knows that Friday. What most do not do is add up what it costs.

The four hours are real. But the deeper cost is the tax on every transition. You track time so you can bill it. Every step between "time is tracked" and "invoice is sent" is a step where hours leak, rates get misremembered, and the story of the week gets retold wrong.

There is a second cost that is harder to see. When invoicing is a Friday-night chore, it stops happening weekly. It becomes biweekly, then monthly, then "when I get around to it." And every week you delay, the connection between the work and the bill gets fuzzier. Clients start asking "what was this for?" and you start guessing.

The fix is not discipline. The fix is removing the retyping.

#Friday B, 5:15pm

Same consultant, same kind of week. Different ending.

The timer ran all week. Tuesday's two hours at the older rate are already tagged with the right project and the right client, so the rate came along automatically. The Thursday receipt is attached to an expense entry, marked billable.

At 5:15pm, the consultant opens owntime, goes to the invoice view, and picks the entries that are not billed yet. Groups them by project. Adds the tax. Hits export.

The PDF that comes out has the letterhead, the invoice number, the terms, and the line items that match the tracked time exactly, because they came from the tracked time. There is nothing to reconcile, because there was never a second copy of the truth.

Invoice sent by 5:20. Friday evening belongs to Friday evening again.

#What makes the workflow hold together

The "time to invoice without retyping" idea only works if the parts between tracking and billing are trustworthy. Here is the chain, link by link.

One source of truth. The entries are the invoice. When you select unbilled entries, you are selecting the same records you tracked, not a re-typed copy. No transcription, so no transcription errors.

Rates that travel with the work. Rates live on the client and the project. Start a timer under the Acme project and the entry knows it bills at Acme's rate. Bill that entry next month and the rate is still right, because it was attached at the source, not remembered at invoice time.

Grouping that matches how clients think. Some clients want one invoice per project. Some want one per day, especially on daily-rate retainers. The grouping is a choice at invoice time, not a structural commitment you made in March.

The money details that always got forgotten. Tax is a field, not a post-invoice scramble. Letterhead, invoice number, terms, they are all in the template. Recurring retainers can be set up as a template that reminds you to bill on schedule. Credit notes and partial payments have a place to live, so the books do not end up as a folder of PDFs and a hope.

Expenses ride along. The Thursday receipt is an expense entry with the receipt file attached, marked billable. It flows onto the invoice next to the time lines. No separate expense invoice, no "can you also reimburse me" email.

#The money half, because time tracking was never the point

The reason anyone tracks time is to get paid for it. owntime treats invoicing as the point and tracking as the input.

A quick tour of the money half, so you can see whether it covers your actual Friday:

• Estimates that become invoices. Send an estimate, the client accepts, and it converts to an invoice. The accepted number is the billed number.
• Recurring retainers. A monthly retainer becomes a draft invoice on schedule. You review, you send. The draft is the reminder that the month ended.
• Expenses with receipts. Billable expenses attach their receipt file and land on the invoice. Your accountant gets the paper trail without asking.
• Credit notes and partial payments. Clients pay in two chunks, or a project gets discounted after the fact. Both have a home in the flow, so the invoice history stays true.
• Unbilled as a first-class view. The invoice view starts from what is not billed yet. You never have to reconstruct "which of these did I already send?" from memory.

None of this needs a server. It is all local, in the same SQLite file as your timesheet. That matters on Friday night, when you realize you forgot to include Tuesday and the fix is one click, not a support ticket.

#The honest limits of this workflow

Now the parts that do not work, so you are not surprised later.

Payments are not processed in owntime. The invoice carries a payment link that lands in your own Stripe or payment account. The client clicks through. It is one extra step compared to a fully hosted processor, and it is a deliberate one: owntime does not touch your money, so it does not need to be a payments company.

No mobile app yet. If your Friday involves invoicing from a phone in a parking lot, owntime will not do that today. It is a Mac desktop app.

No team-wide rollups. If five people need to see one combined invoice ledger, each person's file is separate. Team rollups are planned as an export, not a shared live view.

These are real gaps. They are also the reason the tool can be buy-once and local-first, and the trade is stated plainly on the pricing page instead of hidden in a footnote.

#Try it on your own next Friday

You do not have to take the workflow on faith. The fourteen day trial is the full app, no email wall, and your trial clock starts when you first open it, not when you download it.

So here is the experiment. Next Friday, instead of opening the spreadsheet, open owntime. Track the week in it, or import this week from your current tracker with the dry-run preview. At 5pm, go to the invoice view, select the unbilled entries, and see what comes out.

If the PDF matches your week without a single retyped row, you have seen the whole thesis. If it does not, you have lost ten minutes, not an evening.

Friday evening is the test. Most tools pass the Tuesday demo and fail the Friday. owntime was built backward from the Friday.

Try owntime free for 14 days · See pricing, one time · Import your current tracker's history