> For the complete documentation index, see [llms.txt](https://help.allwage.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.allwage.com/guides/job-costing.md).

# Job Costing

Set up teams, activities, sites and pay run templates so you can see what your labour costs per job, site, activity, team or day, and read the Daily Cost Component Report.

Job costing for labour answers one question: what did the work on a job cost in wages? In AllWage, a "job" can be a site, an activity, a team or a combination of these. The answer comes from your pay runs, because payroll already knows what every hour cost, including overtime, Sunday and public holiday rates.

The **Daily Cost Component Report** on each pay run splits every employee's earnings by day, activity and site, and shows the employee's team on every row. You download it as an Excel file and total it the way you need.

For a full worked example, with one employee working across several sites in a week and the overtime split between them, see the case study [Job Costing for Labour: From Clock-In to Cost Per Site](https://www.allwage.com/case-studies/job-costing-from-activities-to-payroll). Its employee, sites and amounts are made up to show how the split works.

## What job costing in AllWage answers

Each row of the Daily Cost Component Report is one employee, one day, one pay run template and one activity-and-site combination. Total the **Total Cost** column by the column that matches your question:

| Question                                            | Column to total by                                            |
| --------------------------------------------------- | ------------------------------------------------------------- |
| What did each job site cost?                        | **Site** (or **Site Code**)                                   |
| What did each region cost?                          | **Region**                                                    |
| What did each activity or task cost?                | **Activity Name**, **Activity Code** or **Activity Category** |
| What did each team cost?                            | **Employee Group** (the employee's team)                      |
| What did each day cost?                             | **Date**                                                      |
| How much was normal time, overtime or an allowance? | **Pay Run Template Name**                                     |

The report covers **earnings only**. Deductions, benefits and company contributions such as employer UIF and SDL are not in it. To see those per employee, use the [Cost report (New)](https://help.allwage.com/modules/payroll/reports/pay-run-reports.md#cost-report-new), which also has a **Team** column.

## What to set up first

Costs can only be split by something the clock or the employee record carries. Set these up before the pay period you want to cost.

1. **Teams.** Each employee belongs to one team, and all of that employee's cost shows against it. Manage teams under [**Manage > Teams**](https://app.allwage.com/#/system/employees/teams). See [Teams](https://help.allwage.com/fundamentals/users-and-employees/teams.md).
2. **Activities and activity categories.** Every clock-in is against an activity, so activities are what split an employee's day by task. Give each activity a **Code** if your accounts use cost codes: it appears in the **Activity Code** column. The activity's category appears in the **Activity Category** column. See [Employee Activities](https://help.allwage.com/modules/time-and-attendance/configuration.md#employee-activities).
3. **Regions and sites**, if a job is a place (a building site, a branch, a client's premises). Each site belongs to a region, and its **Code** appears in the **Site Code** column. See [Regions, Sites and Geofences](https://help.allwage.com/fundamentals/regions-sites-and-geofences.md).
4. **Clocks with an activity and a site.** Employees clock in against an activity. The site comes from the device, a geofence or a manual edit. See [How Sites Are Picked Up Across Clocking Methods](https://help.allwage.com/fundamentals/regions-sites-and-geofences.md#how-sites-are-picked-up-across-clocking-methods). A clock without a site still costs to its activity, but its rows have an empty **Site** column.
5. **Pay run templates linked to working hours.** A template is split by day, activity and site only when it is linked to a metric, for example **Working hours** (normal hours or overtime). A fixed amount with nothing linked can't be split. See [Link a metric or quantity](https://help.allwage.com/modules/payroll/payrun-templates.md#link-a-metric-or-quantity).

{% hint style="warning" %}
Fix missing or wrong sites and activities on clocks before you finalise the pay run. If clocks change after the pay run is finalised, what the employee was paid doesn't change, and the report shows a separate adjustment row (see [Rows called "Pay-run snapshot reconciliation"](#rows-called-pay-run-snapshot-reconciliation)).
{% endhint %}

## How AllWage splits the cost

The report starts from what each employee earned on the pay run and works out where each amount came from. The **Type** column shows which rule produced each row.

| Type       | What it covers                                                                 | How it is split                                                                                                                     |
| ---------- | ------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------- |
| `T_A`      | Pay run templates linked to working hours or other time and attendance metrics | Each day's quantity is split across the activities and sites the employee clocked that day, in proportion to the time spent on each |
| `ACTIVITY` | Piecework templates linked to units captured on an activity                    | The units captured on each day, activity and site, times the rate                                                                   |
| `HARVEST`  | Templates linked to harvested units                                            | The units captured on each day, produce and site, times the rate                                                                    |
| `OTHER`    | Templates with no linked metric, such as fixed amounts, and adjustment rows    | Not split: one row per employee per template, dated the first day of the pay run, with no activity or site                          |

### Overtime and other premiums are shared by time

AllWage doesn't try to decide which hour of a day was the overtime hour. Each template's hours for the day are shared across the day's work in proportion to time.

**Example (made-up figures):** an employee works 6 hours on Masonry at Site A and 4 hours on Concrete at Site B on a weekday. Their clock template makes this 8 normal hours and 2 overtime hours.

| Activity and site | Share of the day | Normal hours | Overtime hours |
| ----------------- | ---------------- | ------------ | -------------- |
| Masonry, Site A   | 6 of 10 hours    | 4.8          | 1.2            |
| Concrete, Site B  | 4 of 10 hours    | 3.2          | 0.8            |
| **Total**         | 10 hours         | **8**        | **2**          |

Each row is then priced at the template's rate, so both sites carry their share of the overtime premium.

Other rules that affect the split:

* **A template linked to the hours of one activity** costs only to that activity. It isn't shared with other activities worked that day.
* **Days with paid hours but no clocks**, such as public holidays, leave or budgeted hours, get a `T_A` row with no activity and no site.
* **Templates with a Min or Max unit constraint** are counted day by day in date order. For example, if a template pays only the hours above 90 in the period, those hours fall on the days after the employee passed 90 hours. See [Unit Constraints](https://help.allwage.com/modules/payroll/payrun-templates.md#unit-constraints).
* **Rounding doesn't change the totals.** Each amount is rounded to the cent, and the last row for each employee and template takes the rounding difference.
* **Finalised pay runs add up to what was paid.** For a finalised pay run, each employee's rows for a template add up to the amount on the payslip. If today's clocks give a different figure, the difference goes on an adjustment row (see [Rows called "Pay-run snapshot reconciliation"](#rows-called-pay-run-snapshot-reconciliation)).

## Download the Daily Cost Component Report

You need the **Cost Report** permission (**Read**). The report only includes the employees in your payroll scope. See [Payroll Permissions](https://help.allwage.com/fundamentals/users-and-employees/user-permissions/payroll-permissions.md#reports-only-show-the-employees-in-your-scope).

1. Navigate to [**Payroll > Pay Runs**](https://app.allwage.com/#/payroll/pay-runs).
2. Open the pay run. For an earlier period, open it from [pay run history](https://help.allwage.com/modules/payroll/recurring-pay-runs/pay-run-history.md).
3. Click the **Reports** tab.
4. Click **Export** next to **Daily Cost Component Report (Beta)**.
5. If the pay run's end date hasn't passed yet, AllWage shows **Pay Run Still in Progress**. Click the confirm button, which shows how many days early you are (for example **Confirm 3 days early**), to download it anyway, or click **Cancel**.

The Excel file is named after the pay run and its dates (for example, for a pay run called Weekly Wages, "Weekly Wages Daily Cost Component Report - …"), and has one sheet called **Costing Data**.

You can download the report before the pay run is finalised, for example to check costs mid-period. Until it is finalised, the figures change whenever clocks, templates or rates change. Use a finalised pay run for job costs you report on.

## What each column means

| Column                                                   | What it shows                                                                                                                               |
| -------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
| **Date**                                                 | The day the cost belongs to (day/month/year). Fixed amounts and adjustment rows use the first day of the pay run.                           |
| **Employee #**                                           | The employee number.                                                                                                                        |
| **First name**, **Surname**                              | The employee's legal names from payroll.                                                                                                    |
| **Employee Group**                                       | The employee's team **today**, not the team they were in during the pay run. Empty if the employee has no team.                             |
| **Current Company Name**, **Current Pay Run**            | The payroll company and pay run the employee is on today.                                                                                   |
| **Clock Template**                                       | The employee's clock template today.                                                                                                        |
| **Label**                                                | The employee's label.                                                                                                                       |
| **Type**                                                 | How the row was calculated: `T_A`, `ACTIVITY`, `HARVEST` or `OTHER`. See [How AllWage splits the cost](#how-allwage-splits-the-cost).       |
| **Activity Name**, **Activity Code**                     | The activity (or harvested produce) and its code. Empty for fixed amounts and for days without clocks.                                      |
| **Activity Category**, **Activity Category Description** | The category the activity belongs to.                                                                                                       |
| **Site**, **Site Code**, **Region**                      | The site the time was clocked at, its code and its region. Empty when the clock had no site, and for fixed amounts and days without clocks. |
| **Pay Run Template Name**                                | The earning, for example normal hours, overtime or an allowance.                                                                            |
| **Units**                                                | The quantity on this row: hours for time-based templates, or units for piecework.                                                           |
| **Factor**                                               | The rate the units are paid at.                                                                                                             |
| **Total Cost**                                           | The rand cost of the row: units times factor, rounded to the cent.                                                                          |

Activity, site, region and category names are today's names. If you rename a site, older pay runs show the new name when you download the report again.

## Use the report for job costing

The quickest way to total the report is a pivot table in Excel:

1. Open the downloaded file and select any cell in the **Costing Data** sheet.
2. Insert a pivot table.
3. Drag the column for your question (for example **Site**) into rows, and **Total Cost** into values as a sum.
4. Add a second column, such as **Activity Name** or **Pay Run Template Name**, to break each job down further.

For a finalised pay run, the grand total of **Total Cost** equals the total earnings of the employees in the report.

To cost a month that has several pay runs, download the report from each pay run and combine the sheets.

## Common problems

### Costs with no site

Rows have an empty **Site** column when:

* the clock had no site. Set the site on the clock: see [Editing a Clock to Set or Change the Site](https://help.allwage.com/fundamentals/regions-sites-and-geofences.md#editing-a-clock-to-set-or-change-the-site).
* the row is a fixed amount (**Type** `OTHER`), which is never split.
* the day had paid hours but no clocks, such as a public holiday or leave.

These costs still count in the totals. Treat them as unallocated, or share them out yourself.

### Costs with no activity

**Activity Name** is empty for fixed amounts (**Type** `OTHER`) and for days with paid hours but no clocks.

### Rows called "Pay-run snapshot reconciliation"

The report works out the daily split from the clocks as they are **now**. For a finalised pay run, if that no longer adds up to what the employee was paid, for example because clocks were changed after finalisation, AllWage adds a row with **Activity Name** "Pay-run snapshot reconciliation" and **Type** `OTHER`, dated the first day of the pay run, holding the difference. The employee's pay doesn't change.

To avoid these rows, correct clocks before you finalise.

### Team totals look wrong

The **Employee Group** column shows each employee's current team. If an employee moved team after the pay run, all of their cost on that pay run shows against the new team. An employee with no team has an empty **Employee Group**. To give them one, see [Teams](https://help.allwage.com/fundamentals/users-and-employees/teams.md#managing-teams).

### A site's costs show under a different site

If a site was set up under another site, its costs are shown under the top-level site and its region.

### Employer contributions and deductions are missing

The report only covers earnings. Use the [Cost report (New)](https://help.allwage.com/modules/payroll/reports/pay-run-reports.md#cost-report-new) for deductions, benefits and company contributions.

### Rates on Manage > Costing aren't used

The Daily Cost Component Report doesn't use any of the prices on [**Manage > Costing**](https://app.allwage.com/#/system/costing), including the hour rates on its **Employee Activities** tab. That page is for purchase, stock and target costs (see [Purchases & Stocktaking](https://help.allwage.com/fundamentals/purchases-and-stocktaking.md)). Labour costs come only from the pay run templates and rates on the pay run.

If a total doesn't match the pay run and none of the above explains it, contact [support](https://help.allwage.com/fundamentals/support-channels.md) with the pay run name and dates, and the employee number of one affected employee.

## Related reports

* **Cost report (New)**, on the pay run's **Reports** tab: each employee's earnings, deductions, benefits and company contributions for the pay run. See [Pay Run Reports](https://help.allwage.com/modules/payroll/reports/pay-run-reports.md#cost-report-new).
* **Accounting Journal Export**, on [**Payroll > Reports**](https://app.allwage.com/#/payroll/reports): a balanced accounting journal for the finalised pay runs in a month. Choose the month and tick the pay runs to include: every finalised pay run of a ticked one is included. Under **Split debit lines by**, you can switch on **Pay run**, **Activity** and **Site**: the journal then uses the same split as the Daily Cost Component Report, and amounts with no activity or site appear as "Unallocated". Click **Preview journal** to check it, or **Download** for the Excel file. You need the **Accounting Journal Export** permission.
* **Activity Site / Block Duration**, under **Reports > Clocks and Activities**: hours by activity and site, without costs. Use it to check that time is landing on the right sites before you run payroll.


---

# 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.allwage.com/guides/job-costing.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.
