Month-End Is a Reconstruction Without Professional Services Automation Software.

In a firm that sells hours, the last day of the month has a ritual. The operations lead opens the project tool, opens the timesheets, opens last month's invoices, and starts reconciling. Which hours were billable. Which were on a fixed-fee project. Which were logged to the wrong client. Which were never logged and have to be reconstructed from calendars. It takes two days, it is done by the most expensive person in operations, and the number it produces is a best guess with a straight face. The cause is that the same hour lives in three places.

Everything on screen is a mock demo of Zoho Projects and Zoho Books with sample data. Six minutes, one record. Here is one consultant's week. Forty hours. Look at where they are recorded. The project plan says thirty-two hours on the retainer client and eight on an internal project, because that was the plan. The timesheet says twenty-eight on the retainer client, six on a fixed-fee project that was not in the plan, and six unassigned, because that is what happened. The invoice, raised by someone in finance from an email, says thirty hours on the retainer client, because that is what the account lead remembered.

Three honest documents. Three different weeks. At month-end somebody has to decide which one is true, and whichever they pick, one of the other two is now wrong and will be discovered later. And that is one consultant. Multiply by fifteen people and four weeks and the reconciliation is six hundred small decisions, each made by someone who was not in the room when the hour happened. The fix is one decision, and it is the same one every integration problem comes down to: which record owns the fact. The hour is owned by the timesheet entry.

Not the plan, which is a forecast. Not the invoice, which is a consequence. The timesheet entry is the one thing the consultant actually wrote at the time, against a client and a task, and everything else reads from it or is derived from it. That sounds obvious, and no firm we meet has done it, because it forces two other things. The invoice has to be built from the timesheet, never typed. And the plan has to be compared against the timesheet, never overwritten by it. Both are wiring decisions, not tools.

In Zoho terms, the consultant logs time in Zoho Projects against a task on a client's project. The task knows whether the project is billable and at what rate. At the end of the month, the invoice is created in Zoho Books from the logged hours on that project. Nobody types a quantity. The consultant's twenty-eight hours become twenty-eight hours on the invoice, at the rate on the project, with the task names as the lines. If the client disputes a line, the answer is a timesheet entry with a date and a task.

If the account lead wants to write off four hours, they write them off on the timesheet, marked non-billable with a reason, and the invoice reflects it because it reads the timesheet. The two-day reconciliation disappears because there is nothing to reconcile. The invoice is the timesheet, priced. The client sees the difference too. An invoice whose lines are dated tasks is one that gets paid without a call, because every question a client would ask is already answered on the page. The other reader is the delivery plan. The plan said thirty-two hours on the retainer client this week.

The timesheet says twenty-eight. The plan is not overwritten; it is compared, and the four-hour gap shows up on the project as variance, on the day it happens, not at month-end. That is where utilisation comes from. Hours logged against billable work, over hours available, per consultant, per week, read from the timesheet. And margin: the hours logged against a fixed-fee project, at cost, against the fee. Both are ratios of records that already exist. Neither needs a spreadsheet, because the timesheet is the source and the plan is the expectation, and the system holds both.

The most expensive person in operations gets two days back a month, and the number the partners see is the same number the system used to build the invoices. There is a quieter benefit. When the plan and the timesheet are compared every week, the plan gets better, because the person who wrote it sees where it was wrong within days rather than at the end of the quarter. This is not an argument for a category of software. Professional services automation tools exist and some are good. Most firms that buy one still have three copies of the hour, because the tool did not make the decision for them; it gave them a fourth place to record it.

The decision is the product. One record owns the hour. The invoice is built from it. The plan is compared against it. Make that decision on Zoho Projects and Zoho Books and it holds; skip it on any tool and month-end stays a reconstruction. The same is true of a spreadsheet, incidentally. A very good spreadsheet that reconciles the three copies is a fourth copy with an owner, and it will be wrong the week that owner is away. If your month-end takes two days and the number at the end is a best guess, the question is not which tool to buy.

It is which record owns the hour. We settle that with the firm in a no-risk discovery: you pay only if you go ahead. The link is below.