> For the complete documentation index, see [llms.txt](https://docs.allshore.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.allshore.ai/time-and-money.md).

# Time & money

The operational core: **Team time**, **Invoicing**, **Expenses**, **Payroll**, **Margin**, and **Reports**.

## Time

Consultants log time in a weekly grid or day view, with live timers and copy-week. Submitted weeks flow to the client for sign-off (or auto-approve after your per-client policy window); you can override or reopen with the full activity timeline preserved. **Team time** shows the whole roster's week; missing timesheets are chased automatically by an agent. Logging past a contract budget warns at entry time.

## Expenses

Consultants capture their own expenses with receipts; billable ones (with optional markup) land on your **Expenses** worklist to be added to the next invoice.

## Invoicing

**Generate** prices approved time against the contract's effective-dated rates, applies tax rates, expenses, and retainer credits, and numbers the invoice from your firm's sequence. Add manual lines, then **Send** — the client's contacts get a branded email with the PDF attached, and the PDF is persisted so downloads are stable forever. Past-due invoices flip to overdue automatically, with dunning reminders and a collections agent escalating older debt. **Recurring schedules** and **retainers** (prepaid balance with draw-down) automate steady billing. Payments reconcile from your Stripe webhook or manual records; admins can void with a reason.

## Payroll

**Compute** turns approved time into a run of payout instructions per consultant (gross/withheld/net) by classification. **Approve** and **execute** are admin-only, and the platform **never moves money** — it produces provider-shaped export files (Mercury ACH/wire, Gusto hours, internal, EOR, or your own configured format) from your **provider registry**, with preflight validation that names anyone whose payout details are missing before a single row is written. Exports are persisted and re-downloadable; reconcile instructions once your bank or provider confirms. Year-end exports cover tax season.

## Margin & reports

**Margin** shows realized margin by placement and client with trends. **Reports** adds four forward/health views with deliberately precise definitions:

* **Revenue projection** — *confirmed placements only* (active placements × effective bill rate × remaining term, 40-hour weeks; no pipeline weighting). Open-ended rows are surfaced as unprojectable, never silently dropped.
* **AR aging** — buckets net of payments, plus **DSO** (trailing-90-day simple).
* **Billing lifecycle** — billed-to-date vs cap and projection per engagement.
* **Utilization** — billed hours ÷ contracted hours (from the agreement), with internal time shown separately, not consuming capacity.

*Detailed pages per area are being added — tracked in Linear milestone **M30**.*


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.allshore.ai/time-and-money.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
