Skip to main content

Basic Settings – Travel Expense Management

Configure the calculation of subsistence costs, the output of the expense report, and the number ranges for credit notes.

Written by Christian Schad

Under Administration > Travel, you find the central master settings for travel expense management — divided into Subsistence costs (calculation logic), Cost accounting (output format and level of detail), and the master data Vehicles and Locations.

Subsistence costs

Here you configure how ZEP calculates the daily flat rates for subsistence costs (also known as per diem or daily allowance). The settings apply company-wide for all employees.

How to record trips and travel times is described in the article Recording Travel Times and Travel Expenses.

Calculation method

The calculation method determines which method is used to calculate subsistence costs — according to German or Austrian tax rules, calendar-day or 24-hour rule, or without an automatic subsistence cost calculation. The choice controls which additional fields become visible in the form.

Under the "Germany" method, the statutory flat-rate rules apply: for an absence of more than 8 hours, ZEP applies the lower daily allowance, and from 24 hours onward, the full daily allowance.

If employees received a complimentary breakfast, lunch, or dinner on a travel day, ZEP deducts a fixed percentage from the daily allowance for each meal. Employees indicate which meals were provided directly in time recording for that travel day.

Time-limit check for tax-free reimbursement

When the German procedure is active, two time-limit options can be enabled: the three-month rule for prolonged work at the same project or at the same customer. When the limit is exceeded, ZEP automatically switches to taxable reimbursement.

ZEP determines the date from which you have booked more than two days per week to the same work location and the same project or the same customer. An interruption of more than four weeks resets this deadline. If the three-month deadline is likely to be exceeded, ZEP displays a corresponding notice in the employee's Cost Accounting.

Detect overnight stay

When this option is active, ZEP detects an overnight stay based on the travel duration spanning evening and morning. Three detail values control the detection:

  • Minimum – hours that must lie between the end of one trip and the start of the next

  • Evening start – from when ZEP considers an overnight stay possible

  • Morning end – until when overnight detection applies

Trips > Subsistence costs settings with calculation method Germany, deadline check, highlighted overnight time detection Yes at least 2 h with start evening 22:00 and end morning 06:00

If you deactivate "Detect overnight stay", ZEP generally does not take an overnight stay into account when calculating the meal allowance. This particularly affects arrival and departure days on which the minimum absence time is undercut: for these days, ZEP then never calculates a meal allowance.

If you enter "0" for "Minimum", ZEP instead always recognizes an overnight stay as soon as a trip exists - even without a break between the time entries. In this case, ZEP always calculates a meal allowance for arrival and departure days on which the minimum absence time is undercut.

Proportional distribution of subsistence costs

When an employee has booked time on multiple projects on the same day, this setting controls how the calculated subsistence costs are distributed across the projects:

  • Proportional across all projects – the subsistence costs are distributed equally across all booked projects of the day

  • Only for the same customer – proportional distribution applies only when all booked projects belong to the same customer

  • Treat booking as break – determines whether the daily-allowance calculation treats booking gaps as actual breaks (affects the hour calculation for the subsistence costs)

Subsistence costs edit settings dialog with calculation method, deadline check, overnight time options plus highlighted VMA distribution options for all projects or only same customer

The calculation is based on a two-step logic: first, ZEP determines the subsistence allowance for the day from the employee's perspective, based on all time bookings for that day across all projects. The amount depends on the rates per absence duration stored in the locations master data. Only in the second step does ZEP distribute this daily allowance across the projects involved that day.

For internal cost accounting, the proportional distribution across all involved projects always applies, regardless of the setting selected here. Only with the option "Proportional across all projects" does the externally billed subsistence amount match this internal total exactly. With the option "Only for the same customer", the externally billed amount can differ depending on the projects and customers involved.

This setting is only available if you previously selected "Subsistence costs for projects from different customers are separated" for the proportional distribution. It determines how bookings for other customers' projects affect a project's absence time:

Please note: the daily subsistence allowance paid out to an employee does not equal the sum of all project invoices. Projects of different customers can each be invoiced separately for the same daily subsistence allowance, without bookings on other projects affecting one another.

  • "Treat all times booked for projects of other customers like a break": these times do not interrupt the absence time.

  • "Treat only times booked with 'Location not relevant to project' for projects of other customers like a break": this applies only to bookings with the location "not relevant to project". Times booked with "relevant to project" interrupt the absence time, including the surrounding breaks.

  • Third option: all times booked for projects of other customers and the surrounding breaks do not count toward the absence time, but interrupt it as well.

Show all start/destination locations

Controls whether all start and destination locations from the location lists are selectable in the trip recording forms or only a reduced list of typical locations. For very large location lists, the reduced list improves clarity.

The setting also affects the employee's expense statement:

With several entries on the same day, the consolidated view can be clearer, while the individual view makes each leg of a trip traceable.

  • When the checkbox is enabled, the expense statement shows the individual start and destination location for each time entry with a travel activity, even when several entries follow directly after one another.

  • When the checkbox is not enabled, the expense statement consolidates the locations and shows only the start location of the first entry and the destination location of the last entry, provided it differs from the start location.

Location display in reports

Specifies how locations are displayed in the expense report, project time record, and project sales volume — either as a short form with a legend at the end of the report, or directly as the full label.

Cost accounting

Here you configure the output format of the printed expense report that employees receive for approval and payment.

Level of detail per report table

For the three report tables Subsistence costs, Mileage, and Receipts, you control which reference levels appear in the columns:

  • Show project – the table is grouped by project (available for all three areas)

  • Show project and operation – additionally grouped by operation within the project (only for mileage and receipts)

File format

The approved expense report is output in one of the supported formats — PDF is suitable for archiving and handover to accounting, HTML for quick display in the browser.

Approved expense report in landscape format

With the checkbox Approved expense report in landscape format, the PDF output is switched to landscape orientation. Recommended for detailed trips with many receipts and columns that become too narrow in portrait format.

Did this answer your question?