Processes for service firms: record time, evidence the work, invoice without rework
Consultancies, planning offices, agencies, technical service providers and professional practices do not sell parts. They sell working time, commitments and results. All revenue therefore rests on details that are captured on the side: when someone worked on which project, in which role, billable or not. We map the chain from scope agreement through time recording and the activity report to the invoice, and rebuild it so the figures are created where the work actually happens.
In a service business the operating result is built from details that people record last: after the meeting, after the deadline, after the client call. That is why time recording is rarely a question of usability and almost always a question of workflow. Anyone reconstructing a week later from calendar, notes and memory books more coarsely, forgets activity descriptions and, in case of doubt, fails to mark billable hours as billable. The loss occurs quietly, because it never shows up in any report as a loss. We start where the recording happens, instead of building ever more reports at the end of the chain that merely make an incomplete basis look better.
The billing run, step by step
Which workflows cost service firms the most time
Ask a service business where the bottleneck is and the word process rarely comes up. What comes up is: “Billing drags on.” Or: “I cannot tell you right now where that project stands.” Both are symptoms of the same cause. The details that produce the activity report and the invoice are not captured where they arise, but reconstructed later. Reconstruction is the most expensive form of recording: it consumes the time of experienced people, it triggers queries with the client, and it means that contested items get dropped rather than clarified. The six workflows below appear in consultancies, planning offices and agencies just as much as in technical services and professional practices — under different names, but with the same mechanics.
Quotes and scope agreement
Quotes are assembled from text blocks, the last similar quote and a calculation in a spreadsheet. What was actually commissioned — scope, hourly rates, contacts, billing form, reporting duties — stays in that file and in a mailbox. At billing time somebody searches again for which version applies and what was agreed as additional work.
Time recording
Hours are gathered at the weekend or shortly before month end from calendar, notes and memory. The later the entry, the coarser it turns out: collective lines booked to the wrong project, missing or unusable activity descriptions, hours with no billable marker. After the fact none of this can be separated cleanly without asking the client.
Activity reports
Many clients require an activity report as an annex to the invoice. Produced by hand, the same time records are evaluated twice: once for the invoice total, once for the annex. Inconsistent activity descriptions lead to queries, and every query pushes payment into the client's next approval cycle.
Billing by time or fixed fee
Time and materials, fixed fees, retainers and milestones run side by side in the same firm, often within the same project. Each form needs different details. When billing follows a different logic than recording, manual work appears: rebooking hours onto fixed fees, carrying retainers forward by hand, checking interim invoices against the final one.
Follow-ups and deadlines
Dates for responses, sign-offs, renewals and chasing open quotes sit in personal calendars and mailboxes. If someone is away, the follow-up is away too. A deadline that nobody knows except the person responsible does not, in practice, exist in the business — even if it is written into the contract.
Filing per engagement or project
Correspondence, approvals, interim results and reports spread across mailboxes, the shared drive and local folders. The filing works as long as the person who set it up is available. During cover, handover or an audit, people search. Without a clear structure, the question of who may access what cannot be answered reliably either.
The billing run: why hours only become an invoice days later
Month end in a service business is rarely an accounting task; it is a round of clarification. First missing hours are collected, then bookings are corrected onto the right projects, then the project lead decides what is billable and what is written off as goodwill, then reports are produced as annexes, then the draft goes for approval, and only after all that is the invoice written. Every one of these steps waits for people who are simultaneously busy with client work. That is why the billing run can almost never be shortened by typing faster, only by moving the clarification earlier: to the point of capture rather than to month end. That is the lever we address first — it shortens not only the run, but also the time to payment.
Capture where the work happens
Time recording is accepted when it fits into the working day rather than sitting beside it. In practice that means: entry on the phone, in the meeting and at the desk with a few clicks, the person's own projects first, activity descriptions from a maintained list rather than from memory, and a clear marker of whether an item is billable. Where existing industry software can already do this, we set it up there rather than creating a second place for it. Where it cannot, we add a lean capture step and hand the data over through an interface, so no second version of the truth appears.
- Entry on the same day instead of reconstruction at month end
- Activity descriptions from an agreed list, extendable in free text
- Billable, non-billable and goodwill marked while booking, not afterwards
- A note to the project lead when hours have been missing for several days
The activity report as a by-product
Once activity descriptions are usable at the moment of booking, the report is no longer a separate task but an output of the same data. We set up the presentation so that scope and structure match what each client wants to see: by day, by person, by work package or condensed into items. Internal notes stay internal. The invoice draft comes from the same basis, so report and invoice cannot drift apart — the single most common trigger for queries and delayed payment.
- Report and invoice from one data basis instead of two separate evaluations
- Structure per client without changing the way people record time
- Internal notes stay internal, including in consolidated reports
- Interim invoices, retainers and remaining budget carried forward traceably
| Client | Structure of the report | Items |
|---|---|---|
| Client A | by day and by person | 38 |
| Client B | by work package | 9 |
| Client C | condensed into items | 4 |
When project status exists only in the project lead's head
Where technology helps — and where it changes nothing
Worth automating
- Included: Passing recorded hours into billing without a second entry
- Included: Producing the client's activity report from existing bookings
- Included: Flagging missing hours, pending approvals and expiring retainers
- Included: Creating follow-ups from contract data instead of personal calendars
- Included: Filing incoming documents against the right project record
Stays with people
- Not included: Deciding whether a contested item is billed or written off
- Not included: The professional assessment of a matter and the advice itself
- Not included: Rare special cases that occur once a quarter and differ every time
- Not included: The conversation when a project runs over budget or the scope changes
- Not included: Approving an invoice that somebody puts their name to
This distinction is not modesty, it is experience. Cases that occur rarely and look different every time can certainly be modelled, but the effort for maintenance and exceptions outweighs the benefit. Cases that occur daily and always run the same way are the opposite: there, every minute saved pays back many times over. In the process analysis we therefore check frequency and uniformity first — and we say plainly when a workflow is too rare to automate. Such a statement is part of the result, not a way of avoiding it.
Confidentiality, access rights and retention
Service firms work with other people's documents. In advisory work and professional practices, duties of confidentiality apply that also bind service providers granted access to those documents on instruction. That has direct consequences for how a system is built: access must not apply across the board, cover arrangements need a controlled and traceable release, and exporting engagement data to a private device must never be a side effect of a convenient feature. We therefore design rights along the engagement or project rather than along the department — slightly more setup effort, and considerably more robust day to day. We agree the points below in writing before implementation.
- A rights model per engagement or project instead of blanket access to whole folders
- Controlled cover: a time-limited release that is granted and withdrawn traceably
- Logged access to particularly sensitive documents
- Separation of internal notes from what is shared with the client
- Data processing agreed in writing before we receive access to live data
- Processing and storage in Germany, encrypted transfer between systems
- Retention and deletion as a deliberate rule, not a side effect of available storage
No legal and no professional-conduct advice
How a project runs with us
Initial call
In about 30 minutes (project experience) we clarify where the friction sits: in recording, in reporting, in billing or in the overview of running projects. We ask about your billing forms, the industry software in use and how many people book time. You then receive an assessment of whether an analysis is the right step, plus a written scope with price.
Process analysis during normal operations
We accompany the workplaces where time is recorded, checked and billed, and capture the chain: scope agreement, booking, review, activity report, invoice, payment. We look at real cases — an ordinary one, a laborious one and one that led to a dispute. The result is a written report with prioritised measures and estimated prices. Details are on the process analysis page.
Connect systems instead of replacing them
In most cases the existing industry or practice software stays, because it fits the subject matter. What is missing is the connection to time recording, the accounting system and filing. We build that connection as an interface with a clearly defined direction, so it stays visible which system holds the truth. Where master data is maintained in several places, data integration belongs with it.
Automate recurring manual work
Only once the data flows is process automation worthwhile: producing invoice drafts and activity reports, reminding people about missing hours, creating follow-ups from contract data, flagging expiring retainers. Every automation gets a fallback and a visible alert when a run does not happen — silent automation is more dangerous than none at all.
Order the filing, the evidence and the reporting
In parallel we bring the project or engagement record into a form a stand-in can understand: a consistent structure, digital documents instead of paper stacks, rights per record. For steering, a small number of dependable metrics replaces a report pack nobody reads. What has been set up is written down in the process documentation.
Rollout and operation
A new way of recording time is either adopted or worked around — and that is decided in the first two weeks. Rollout and training are therefore part of the project: short instructions, support during the early period, a named point of contact for questions. Afterwards we can take over ongoing operation of the transfers we set up and get in touch before you notice anything.
In about 30 minutes (project experience) we clarify where the friction sits: in recording, in reporting, in billing or in the overview of running projects. We ask about your billing forms, the industry software in use and how many people book time. You then receive an assessment of whether an analysis is the right step, plus a written scope with price.
We accompany the workplaces where time is recorded, checked and billed, and capture the chain: scope agreement, booking, review, activity report, invoice, payment. We look at real cases — an ordinary one, a laborious one and one that led to a dispute. The result is a written report with prioritised measures and estimated prices. Details are on the process analysis page.
In most cases the existing industry or practice software stays, because it fits the subject matter. What is missing is the connection to time recording, the accounting system and filing. We build that connection as an interface with a clearly defined direction, so it stays visible which system holds the truth. Where master data is maintained in several places, data integration belongs with it.
Only once the data flows is process automation worthwhile: producing invoice drafts and activity reports, reminding people about missing hours, creating follow-ups from contract data, flagging expiring retainers. Every automation gets a fallback and a visible alert when a run does not happen — silent automation is more dangerous than none at all.
In parallel we bring the project or engagement record into a form a stand-in can understand: a consistent structure, digital documents instead of paper stacks, rights per record. For steering, a small number of dependable metrics replaces a report pack nobody reads. What has been set up is written down in the process documentation.
A new way of recording time is either adopted or worked around — and that is decided in the first two weeks. Rollout and training are therefore part of the project: short instructions, support during the early period, a named point of contact for questions. Afterwards we can take over ongoing operation of the transfers we set up and get in touch before you notice anything.
Entry point · net plus VAT
- Review at the workplaces where time is recorded and invoices are produced
- Duplicate entry between time recording, industry software and accounting named
- Written report with prioritised measures and estimated prices
- A clear statement on which workflows are not worth automating
The entry point is the process analysis. For one clearly defined workflow at a single site — for example the chain from time recording to invoice — it is 1,900 € net. Larger reviews spanning several areas or sites are agreed in writing beforehand, so the price is fixed before we start. Implementation begins at 4,900 € net per automation or interface, as a fixed price after the analysis. Ongoing support begins at 190 € net per month. All prices net plus VAT; details on the pricing overview.
Prices as of September 2026. Ongoing services are booked individually and can be cancelled monthly; there is no minimum term.
Typical starting situations in service firms
Illustrative scenarios from typical project sequences (project experience), anonymised and without client details. No outcomes are promised.
Metrics that hold up in a service business
Billable share
How much of the recorded working time is actually billable, split by team and type of project? This figure only holds up if the marker is set while booking rather than estimated later. It shows early whether a project is cut the right way — and it is expressly unsuited to assessing individual people.
Unbilled work
Work delivered but not yet invoiced is tied-up capital. If nobody can say how much of it there is, the billing run becomes a black box. Made visible, it turns into a steering figure: it shows which projects are waiting for an approval and where an interim invoice would make sense.
Result per project
With fixed fees and retainers, the margin is decided during delivery, not at the point of order. Hours used against hours calculated — continuously, not at the end. This is not team surveillance but the basis for a timely conversation with the client, while there is still something to agree.
Time to invoice
The span between work delivered and invoice issued is the figure that describes the billing run most honestly. It can be derived from existing data with no extra effort and shows whether a measure has actually arrived in daily work or only exists on paper.
| Billing form | What recording has to deliver | Typical friction | Starting point |
|---|---|---|---|
| Time and materials | Hours, project, role, activity description, billable marker | The report is prepared by hand, descriptions are inconsistent | Agree an activity list, generate the report from the same data basis |
| Fixed fee | Full recording nonetheless, plus allocation to the work package | Effort stops being booked, so the result per project stays unknown | Keep recording, make usage against the calculation visible continuously |
| Retainer or call-off | Carrying the remaining balance forward, visible to both sides | The balance is kept in a side list and drifts apart | Automate the carry-forward, alert when the threshold is undercut |
| Milestone or interim invoice | Linking sign-off to payment, with a documented trail | Interim invoices and the final invoice are reconciled by hand | Record sign-offs with documentation, model the offset during invoicing |
The most expensive hour in a service business is the one that was delivered but never recorded. It appears in no report — and is missing from the result all the same.
Which service your case needs is decided in the process analysis report. Often it is interfaces between industry software, time recording and accounting, process automation for invoice drafts and reminders, and document digitisation for the project or engagement record. Where an ageing specialist application stands in the way, legacy replacement belongs in the picture. The services and industries pages give an overview; where we work on site is set out under regions.
Does your billing run stretch across several days?
Describe briefly how time is recorded today, which industry software is in use and which billing forms you use. In the initial call we tell you frankly whether a process analysis is worthwhile — or whether a smaller change to the way time is captured is already enough.