- Insights
- Travel Charge Variance Report
Travel Charge Variance Report
The Travel Charge Variance report 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 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.
Before You Start
- The report is part of Scheduling. Without Scheduling it does not appear in Reports at all.
- By default it is available to the Admin and Manager roles. See Roles & Permissions.
Where To Find It
- From the left-hand menu, select Reports.
- 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 includes kilometres.
- Travel hours — the approved duration on each trip whose Charge Behaviour includes time.
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. A support with one approved trip and one still awaiting approval shows a dash rather than a variance that isn't settled yet, and the support drops off the report entirely until at least one trip is approved.
Filters
| Filter | What it does |
|---|---|
| Support Date | The date range of the supports included. Defaults to the current month and can't span more than 366 days. |
| Variance | Any, Not charged, or Over charged. |
| Billing | All, 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. |
| 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
- A dash in an Approved / Charged column means the support has no trip charging that way, or not every such trip has been approved.
- 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.