> For the complete documentation index, see [llms.txt](https://learn.withessential.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.withessential.com/customers-and-work/jobs/add-manual-revenue-or-labor-to-a-job.md).

# Add manual revenue or a manual labor entry to a job

Use manual revenue and manual labor entries to fold work that didn't go through an Essential invoice, or labor that wasn't clocked, into a job's cost rollup — so the Job Costing card and reports reflect the full picture.

**Before you start:** Job Costing must be turned on for your business and your role needs the job-costing manage permission. See [Turn on Job Costing and set cost rates](/administration/settings/turn-on-job-costing-and-set-cost-rates.md).

## Add or edit manual revenue

Manual revenue is for work invoiced outside Essential — billed by email or paper, for example — that you still want counted toward the job's margin. It's added on top of any linked invoices, not a replacement for them.

1. Open the job and expand the Revenue column on the Job Costing card.
2. Click **+ Add revenue** (or **Edit manual revenue** if an amount is already set).
3. Enter the amount and save. Leaving the field empty clears it back to zero; an invalid amount is rejected with an inline error instead.

## Add a manual labor entry

Manual labor entries cover work a clocked timecard entry won't capture. Find the **Labor** section below the totals, click **Add Labor**, and choose one of three entry types:

* **Hours × rate** — pick a technician and enter hours and a dollar rate; costed the same way as clocked time.
* **Flat total** — a label and a single dollar amount, with no hours or rate.
* **Amount + note** — a dollar amount with a free-text note explaining it (for example, "Helper – unexpected").

Save to add the entry. Any manual entry can be edited or removed from the Labor list with its delete icon.

## What happens after

Manual revenue and manual labor entries feed directly into the job's margin on the Job Costing card and into the job costing reports. Labor entries with a technician attached also roll up into that technician's numbers on the Technician profitability report.

> **Where to find it:** Open a job from Scheduling > Jobs; use Revenue and the Labor section on the Job Costing card.

## Related guides

* [Job Costing on a job: revenue, costs, and margin](/customers-and-work/jobs/job-costing-on-a-job.md)
* [Turn on Job Costing and set cost rates](/administration/settings/turn-on-job-costing-and-set-cost-rates.md)
* [Job costing reports: profitability, cost breakdown, and more](/reporting-and-integrations/reporting/job-costing-reports.md)


---

# 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://learn.withessential.com/customers-and-work/jobs/add-manual-revenue-or-labor-to-a-job.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.