> 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. Review the costing and choose what to bill, then check the draft before issuing it.

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

{% hint style="info" %}
Inside a Job, the Financial tab is visible to people with **Manager access or higher**. The agency-wide [Finance](/admin/finance.md) page requires Finance access or higher. See [Users](/company-settings/users.md) for the role hierarchy.
{% endhint %}

## The Financial dashboard

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

* **Total Billed** — the value of issued, non-void Invoices, with each Invoice’s tax included, and its percentage of Job Value. Drafts and voided Invoices are excluded. This is invoiced value, not payment received.
* **Job Value** — the current Job Costing total for all billable Tasks and Costs, including Draft items and the Client’s tax. A Draft item can therefore contribute to Job Value before it is approved to proceed.
* **Balance** — Job Value less Total Billed. It shows the remaining value to invoice against the current costing, not unpaid client debt.
* **Work done** — previously labelled Billable. It shows the Job’s reported work value and a progress percentage against its Budget or estimate, excluding VAT. This card does not create or issue an Invoice.

{% hint style="info" %}
**Read the tax basis before comparing cards.** Total Billed and Job Value use tax-inclusive totals; Work done uses an excluding-VAT reference. Subtracting the two displayed amounts does not give a reliable “delivered but unbilled” figure. Check the Tasks, Job Costing and issued Invoices before deciding what to bill.
{% endhint %}

{% hint style="info" %}
A positive **Budget** changes the reference amount for Work done. Without one, the card uses the Job Costing sub-total. It does not replace the Job Costing-based Job Value. See [Setting a Budget](/jobs/managing-jobs.md#setting-a-budget).
{% endhint %}

### Checking the cards

{% stepper %}
{% step %}
Open the Job’s **Financial** tab and wait for the figures to finish loading.
{% endstep %}

{% step %}
Check **Job Value** against the billable costing, including any Draft Tasks or Costs.
{% endstep %}

{% step %}
Check the **issued Invoices** behind Total Billed. Use their payment indicators separately when checking what the Client owes.
{% endstep %}

{% step %}
Review **Work done** with its Budget or estimate reference, then choose the items for the next Invoice.
{% endstep %}
{% endstepper %}

The Job Value and Balance captions read **Including VAT** when the agency’s Tax rate % in Finance settings is above zero, otherwise **Excluding VAT**. The captions follow the agency setting; they do not change the Client’s tax or the amounts.

{% hint style="info" %}
A website Job has a tax-inclusive Job Value of R23,000 and issued Invoices totalling R5,750. Its Balance is R17,250 even if the deposit is still unpaid. Payment collection and the next progress Invoice are separate decisions.
{% 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>

## Opening Activity

{% stepper %}
{% step %}
Below the Invoice or Purchase Order list, click **Activity** when it is available.
{% endstep %}

{% step %}
Read the matching document entries: type and date above the person or System and the action, with an amount where recorded.
{% endstep %}

{% step %}
Click Activity again to close it. Keyboard users can focus the heading and use Enter or Space.
{% endstep %}
{% endstepper %}

Activity starts closed when you open another Job or switch between Invoices and Purchase Orders. These lists show their own document types. Use [Central](/jobs/central.md#activity) for the wider Job timeline and its Search; the Financial Activity disclosure has no separate search field. A missing entry does not prove an action never happened.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.agencydesk.io/jobs/financial.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.