From approved work to invoice: an agency project-to-cash workflow

The Friday scramble usually begins much earlier than Friday. A consultant logs time to the wrong task. A manager approves the week without noticing. Finance receives a spreadsheet with no explanation of the exception, then asks delivery to reconstruct what happened. The invoice is late because the evidence lost its context before billing began.

A connected workflow preserves that context while changing the record’s status deliberately. Logging says the work happened. A timesheet packages it for a period. Approval says it is valid. Uninvoiced review decides whether and how it should be billed. The invoice communicates the claim to the customer. Payment and accounting complete a different part of the financial story.

A useful work log carries the person, date, duration, project, task, billable state, and enough description to understand the work. It should be easy to enter close to the moment of delivery. Asking people to recreate an entire week from memory weakens both project reporting and the invoice evidence.

The timesheet serves a different purpose. It gathers individual entries into a reviewable period and makes completeness visible: missing days, total hours, leave, non-billable work, and late changes. Closing or submitting the period creates a stable object for review without pretending each underlying entry is identical.

Approval should answer whether the record is complete, accurate, and attributable to the right project. It should not silently decide every commercial question. A valid hour on a fixed-fee project affects cost and progress even when it never becomes a separate invoice line.

The uninvoiced-work review is the commercial gate. It brings approved time and expenses together with the project’s billing model, rates, caps, milestones, retainer balance, prior invoices, and write-off decisions. Exceptions belong here: a courtesy adjustment, a non-rebillable expense, an hour above a cap, or work held for the next billing cycle.

A draft invoice should inherit the customer, currency, billing address, tax treatment, payment terms, project reference, and reviewed lines from controlled records. Finance still needs an explicit review before issue. Automation removes rekeying; it does not remove accountability.

Keep the link from invoice line to source. When a client asks why 17.5 hours appeared, the answer should not depend on the person who assembled the invoice remembering which spreadsheet tab they used. The same trace helps the team avoid billing the same approved record twice.

After issue, the workflow must track what happened: sent, due, partly paid, paid, disputed, void, or written off according to the firm’s system and policies. The accounting handoff also needs visible success or failure. A green ‘synced’ label with no external reference or error trail is not a control.

An invoice status is still not a revenue-recognition policy. IFRS 15 recognizes revenue as promised goods or services transfer to the customer, including over-time recognition where the criteria are met. Billing schedules and cash timing can differ. Keep project evidence, invoice events, accounting outcomes, and payment events connected but distinct.

The most useful operating measures expose friction: time from period end to submission, time awaiting approval, approved value waiting to be billed, exception count, draft-to-issue time, rejected accounting handoffs, and days to payment. A single invoice total says little about where the process is stuck.

Begin with one real project. Follow one hour and one expense from source to settlement. Name the owner and exit condition at every gate. The weak handoff will become obvious quickly—and it is usually more valuable to repair that handoff than to add another month-end spreadsheet.