Most agency forecasts are a monthly act of reconstruction: export the hours, guess which are billable, remember which client has an allowance and find the hosting invoice.
Genedar removes the reconstruction. Costs attach to assets, assets attach to projects, projects carry billing rules and hours arrive matched to a project number.
Hours are booked in genedar, in a week or day view. A server-side timer starts and stops and rounds to 15 minutes. Time goes on project tasks that belong to a billing item: the base order, a change request or a fee.
Suggestions come from your git commits and your calendar. A meeting gets the project you last booked under the same subject, in genedar or in Harvest.
A task has a budget in hours, with an optional lock at the budget. Warnings at 50, 80 and 100 percent arrive in the app and by email. The remaining hours show while you book. Late bookings are allowed and flagged for the project manager.
A task lists who may book on it. An external person sees and books only their own task.
A board for assignments per person and project, moved by drag and drop, with each person shown as full, open or over. Booked time stays visible per project with the task, notes and source behind each daily total. Office days and absences (vacation, sick) are kept per person. Public holidays follow where each person works: the German state, or a company calendar such as a Spanish office's.
Time management corrects hours, notes and billability directly in the Team list, or selects entries booked on the wrong task or project and moves them in one go. Invoiced entries stay locked. A task without booked hours can be deleted.
Book time, find bookable projects and tasks, page, filter, summarize or export entries, update filtered entries in a confirmed bulk run, and start or stop the timer through the assistant and the MCP server.
Harvest projects, people, tasks and worked hours arrive against the shared project number; Harvest Forecast adds time off, so utilisation is measured against real capacity.
Hours meet included allowances with an optional carry-over window, prepaid pools, overage rates and change requests.
The invoice is built from commercial rules and delivery evidence that already exist. A project cannot be archived while one of its invoices is still open, so nothing unpaid disappears with a finished engagement.
The project's Billing card copies all billing emails in one click and builds a ready-made invoice request email for the accounting team, with the billing address and payment term already filled in.
Every line of a billing month is the same card in every month state, so there is one thing to learn and one place a number can come from.
A billing month used to be several different screens depending on the state it was in, which is exactly how a figure ends up with two plausible origins and no obvious one. Now a billing item's fixed fee and the overage it produced are one card and one amount column, each part tickable and editable while you are still proposing. The card opens to the Harvest entries behind the amount, with the included and the overage hours separated, so the answer to what a line is made of is one click away rather than an export.
That is also what makes a line defensible in front of the client. A free-text description travels with it onto the proposal, the invoice and next month's plan, confirming an invoice freezes its wording so an issued invoice never changes afterwards, and a partially billed item keeps only its remainder, so what you invoice next is exactly what is left.
Every past month opens as a full proposal, with the same composer, the same invoice date and the same Confirm action as the current one. The separate retroactive-invoice step and the closed-month notice are gone, and a fee line that was already invoiced shows its detail but can never be proposed twice.
Hours arrive on their own: the Harvest sync runs on a schedule against the shared project number, so a month is already assembled when somebody opens it rather than being reconstructed from an export.
Prepared invoices are not treated as money that does not exist. A month whose invoices are prepared shows the prepared amount rather than zero, the contract bar and the budget pots carry a distinct prepared segment next to invoiced and accrued, and the remaining budget subtracts prepared invoices as well as issued ones, so the figure never overstates what is still available.
Planned revenue is the sum of billing plans on live engagements, adjusted by what has actually been booked - not a number copied into a forecast sheet.
Archiving an engagement preserves its issued invoices in the forecast for the selected year. Archived rows remain read only and add no planned revenue. Once every invoice of the year is paid the archived row steps out of the matrix by default while its amounts stay in the totals; a switch shows it again.
A capped engagement also reports what is still plannable: the order value minus every committed invoice, prepared as well as issued, minus the months that still carry a plan. A month that has been invoiced counts its invoice rather than the plan the invoice replaced, so the same money is never counted twice and the number answers what is still free to distribute.
Recurring and one-time billing items, fixed-price and time-based arrangements and change requests roll up into portfolio liquidity, project margin and account profitability.
During payment reconciliation the forecast narrows as you type: a search over customer and project names, reachable with a single keystroke, finds the engagement an invoice belongs to in seconds.
A project month can be marked as draft invoice created while the final hosting costs are still outstanding; the forecast flags it from the first of the following month until the invoice exists, without locking the month in the cost sync. The Status filter lists the open draft markers of a year in one click.
We will rebuild it from contract, imported hours and attributed asset cost - and show where the reconstruction went wrong.
