# Travel Charge Variance Report Source: https://docs.astalty.com.au/guide/reports/travel-charge-variance-report > Find supports where the travel approved for billing doesn't match the travel the Participant was charged for. Scheduling add-on - This feature requires the Scheduling add-on, which is available on Astalty Premium. See How to enable Scheduling. The [Travel Charge Variance report](https://app.astalty.com.au/reports/scheduling/travel-charge-variance) lists supports where the travel approved for billing doesn't match the travel the Participant was charged for. ## Overview Astalty compares the kilometres and travel hours approved on a support's [Travel](https://docs.astalty.com.au/guide/scheduling/travel-to-during-and-from) against the transport charges raised for that support, and lists every support where the two differ. A positive variance is labelled **not charged** - travel was approved but the Participant wasn't billed for it. A negative variance is labelled **over charged** - the Participant was billed for more travel than was approved. The report opens on supports that haven't been invoiced yet, because those are the ones still worth correcting. ![The Travel Charge Variance report for Support Date 1 - 31 Oct 2026 with Variance Any, Billing All, Invoiced Not yet invoiced and Participant All, cards for Supports, Kilometres not charged, Kilometres over charged and Travel hours not charged, and rows showing approved against charged kilometres and hours with not charged and over charged variances.](https://docs.astalty.com.au/assets/travel-charge-variance-report-guide.png) ## Before You Start By default, only Admins can open this report. A Manager can open it once **Can access Scheduling** is turned on for them. See [Roles & Permissions](https://docs.astalty.com.au/guide/users/roles-permissions#scheduling). ## Where To Find It 1. From the left-hand menu, select **Reports**. 2. Under **Scheduling**, select **Travel Charge Variance**. ## What Gets Compared **Approved** figures come from the Travel recorded on the support: - Kilometres - the approved distance on each trip whose **Charge Behaviour** is **Kilometres only**, **Time & km** or **None**. - Travel hours - the approved duration on each trip whose **Charge Behaviour** is **Time only**, **Time & km** or **None**. A trip set to **None** counts towards both comparisons, so approved travel that was set not to charge shows as **not charged**. A trip set to **Time only** is left out of the kilometre comparison, and **Kilometres only** is left out of the hours comparison. On a support billed manually, every trip counts towards both comparisons regardless of its Charge Behaviour, since a person decides what to charge rather than the behaviour. Trips marked as not travelled are excluded, as are supports cancelled with a charge behaviour of no charge. **Charged** figures come from the support's billable transport charges: kilometre charges for the kilometre comparison, hourly travel charges for the hours comparison. Voided and non-billable charges are ignored. A variance is only calculated once **every** trip in that comparison has been approved. Until then that comparison shows a dash rather than a variance that isn't settled yet. A support is listed only when at least one of its two comparisons is fully approved and the approved and charged figures differ, rounded to two decimal places. ## Filters | Filter | What it does | | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Support Date** | The date range of the supports included, matched against each support's scheduled start and including the whole of the end date. Defaults to the current month and can't span more than 366 days. | | **Variance** | **Any** (the default), **Not charged**, or **Over charged**. | | **Billing** | **All** (the default), **Automatic**, or **Manual**. | | **Invoiced** | **Not yet invoiced** (the default) excludes any support that already has an invoiced charge. **Include invoiced** shows them all. | | **Participant** | One or more Participants. | ## Summary Statistics Above the table, each of these appears when it is greater than zero: - **Supports** - how many supports match the filters. - **Kilometres not charged** / **Kilometres over charged** - the totals across those supports. - **Travel hours not charged** / **Travel hours over charged** - the same for travel time. ## Understanding The Results | Column | What it shows | | --------------------------- | -------------------------------------------------------------------------------------------- | | **Support Date** | The date of the support. Sortable. | | **Participant** | The Participant on the support. | | **Billing** | **Automatic** or **Manual**. | | **Invoiced** | **Invoiced** when the support already has an invoiced charge. | | **Approved / Charged km** | Approved kilometres against kilometres charged. | | **Kilometre Variance** | Approved minus charged, labelled **not charged** or **over charged**. Sortable. | | **Approved / Charged hrs** | Approved travel hours against travel hours charged. | | **Hours Variance** | Approved minus charged, labelled **not charged** or **over charged**. Sortable. | | **Travel Charge Behaviour** | Each trip's **Charge Behaviour**, listed by leg: **To**, **During** or **From** the support. | | **Travel Pay Behaviour** | Each trip's **Pay Behaviour**, listed the same way. | | **Charge Item Set** | The Charge Item Set applied to the support. | Rows are sorted by the largest variance first until you sort by a column. Select a row to open the support on its **Finance** tab. ## Things To Keep In Mind > **No km Charge Item means the kilometres could never be billed** > > On a support billed automatically, a **No km charge item** chip against the kilometre variance means the approved kilometres had no Charge Item to bill against, so no charge was ever raised. Travel during a support needs either a [Travel During KM Charge Item Override](https://docs.astalty.com.au/guide/scheduling/travel-to-during-and-from#travel-during-km-charge-item-override) or a kilometres-during Charge Item on the Charge Item Set; travel to and from a support needs a kilometres-not-during Charge Item on the set. See [Charging Kilometres Requires a Travel Charge Item](https://docs.astalty.com.au/guide/scheduling/travel-to-during-and-from#charging-kilometres-requires-a-travel-charge-item). - A dash in place of the approved figure in an **Approved / Charged** column means the support has no trip counted in that comparison, or not every such trip has been approved. The charged figure always shows, even when it is 0. - Trips marked as not travelled are left out of the figures and of the **Travel Charge Behaviour** and **Travel Pay Behaviour** lists. - Kilometres and hours are compared separately. A support can be over charged on kilometres and not charged on hours at the same time. - There is no export of this report.