Client timesheet

A client timesheet is the numbered, immutable document a billing run produces for one client and period, as HTML, PDF, and CSV, delivered by email to the client's billing recipients.

Written for
user, admin, integration-developer
Roles
owner, admin, project-manager, billing-contact
Requires
Feature
documents

A client timesheet is the document a billing run produces: the list of what one client is charged for in one period, line by line, with the time bank movements underneath. It is what the client receives, and it is what your invoice refers to. The app calls the produced files artifacts and lists them under Documents.

How it relates to other concepts

  • The client's timesheet layout decides the scope: Combined gives one document per run with a section per project; Per project gives one document per project.
  • Delivery goes by email from the workspace mailbox to the client's billing recipients (contacts designated for the client, or for one of its projects). Each delivery shows as in flight, sent, failed, or skipped when no mailbox is connected.
  • A billing contact downloads their own client's documents in the app.

Rules

  • Formats: HTML, PDF, and CSV, each with a checksum. The language is the client's language.
  • Numbering: the workspace prefix, TS, the year and month the period starts in, and a sequence number, for example ACME-TS-2026-09-1. Every document of a run gets its own number.
  • Content per line: date, consultant category, ticket id, billing description (never the ticket title or the entry notes), hours as a decimal, rate, amount, and the outcome: Charged, Covered by time bank, or Free of charge. Corrections are marked. Then a time bank section (opening, credit, carried in, borrowed, consumed, overage, closing). Amounts exclude VAT.
  • Documents are immutable. Voiding the run marks them voided; redacting a ticket supersedes the documents that quoted it with new ones.
  • Who may download: Owners and Admins, everything; a workspace user with a client-wide document grant, every document of that client; a workspace-user Project manager, the project documents of their own projects; a billing contact with a full login, their own client's documents. A project document carries only that project's figures.
  • Through the API and the MCP tool for timesheets, the same access rules apply; a token needs the read scope.

Example

Nordic Retail is set to Per project. The September run produces ACME-TS-2026-09-1 for retail-shop and ACME-TS-2026-09-2 for retail-data. Both go to invoices@nordic-retail.example; Ola, the billing contact, downloads the PDFs from Documents.

  • Client timesheets (documents) What the timesheet documents a billing run produces contain, who can download them, how they are delivered to billing recipients, and how to fetch them through the API or MCP.
  • Run billing for a client Price a client's time for one closed period with the five-step run wizard, fix blockers, review billing descriptions and bank totals, commit, and void a run when needed.
  • Contacts and billing recipients Register email identities without a login, designate the addresses that receive timesheet documents, and grant workspace users client-wide document access.
  • Download client timesheets How to list the client timesheet documents a token may see and download them as HTML, PDF, or CSV through the API or the MCP get_timesheet tool.
  • Billing contact What the Billing contact flag on a client user gives, how it differs from a billing recipient, and how timesheets and bank balances reach the client.