> For the complete documentation index, see [llms.txt](https://help.agencydesk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.agencydesk.io/jobs/financial.md).

# Financial

The Financial tab of a Job: invoice for work done and raise Purchase Orders for Supplier costs, all drawn straight from the Job Costing.

The **Financial** tab of a Job is where tracked work becomes billing. Because Agencydesk is built exclusively for agencies, everything here draws directly from the [Job Costing](/jobs/job-costing.md): the [Tasks](/jobs/tasks.md), Costs, rates, and [Billing Tier](/company-settings/general/billing-tiers.md) already set up on the Job. You do not rebuild figures or re-check rates. You choose what to bill, and the numbers are already right.

The tab has two sub-tabs, each covered in its own guide:

{% hint style="info" %}
Inside a Job, the Financial tab is visible to users with **Manager** access or higher. The agency-wide [Finance](/admin/finance.md) page is separate and visible only to the Finance role. Access levels are set per user under [Users](/company-settings/users.md).
{% endhint %}

## The Financial dashboard

At the top of the Financial tab, four cards summarise the Job's billing health:

* **Total Billed** — the percentage and value of the Job that has actually been **billed on issued** [**Invoices**](/jobs/financial/invoices.md). Draft Invoices don't count, so this figure reflects real, issued billing only. (Void an issued Invoice and this drops accordingly.)
* **Job Value** — the total value of the Job, including VAT.
* **Balance** — what remains to be billed, including VAT.
* **Billable** — the value of work actually **done** so far, shown as a percentage of the estimated Job value. This is made up of tracked time (capped at each item's estimated amount, so an overrun doesn't inflate it) plus any [Tasks marked complete](/jobs/tasks.md#completing-a-task), which count in full even if no time was tracked on them.

{% hint style="info" %}
**Total Billed vs Billable** answer two different questions. **Total Billed** is what you've invoiced. **Billable** is what you've earned the right to invoice based on work done. The gap between them is work delivered but not yet billed, which is exactly what an Account Executive wants to see before raising the next progress Invoice.
{% endhint %}

{% hint style="info" %}
Setting a **Budget** on a Job changes what the Billable card measures against. See [Setting a Budget](/jobs/managing-jobs.md#setting-a-budget) on Managing Jobs.
{% endhint %}

## In this section

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h3>Invoices</h3></td><td>Create, build, edit, issue, download, and void Invoices, with guardrails that keep billing accurate and audit-ready.</td><td><a href="/jobs/financial/invoices.md">Invoices</a></td></tr><tr><td><h3>Purchase Orders</h3></td><td>Raise Supplier POs from Job Costs, with buy-and-resell views and correct dual tax-rate handling.</td><td><a href="/jobs/financial/purchase-orders.md">Purchase Orders</a></td></tr></tbody></table>


---

# 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://help.agencydesk.io/jobs/financial.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.