Skip to main content

Basic settings

In this article you will find basic information about the Administration menu item in ZEP.

Christian Schad avatar
Written by Christian Schad
Updated over 2 weeks ago

Overview

As a rule, you only have the Administration menu item in your ZEP if you have Administrator authorization.

Exception: When using the Invoicing module, a user with Controller authorization also has the Administration menu item with the Billing submenu item.

In this Administration area, you can configure ZEP according to your requirements. You can individually adjust ZEP's behavior, appearance, and the stored data related to your company.

Which menu items are displayed under Administration in ZEP primarily depends on the add-on modules you use. In the following, we will go through the most important points. If you have menu items that are not covered in this article, please refer to the article for the corresponding add-on module.

My Company

General

Company Logo
You can display your company logo on the ZEP login page and in ZEP at the bottom left: Select the corresponding file (maximum size: 1MB) and upload it.

ZEP Color
Either enter the desired hexadecimal color code in the input window or select the desired color by clicking the color symbol. If you want to reset ZEP to the original color, completely delete the entry and click Save.

Access via secure SSL connection
You can specify whether you fundamentally want to enforce an SSL-encrypted connection, offer it as an option, or if it should not be possible. We recommend always accessing ZEP with SSL encryption.

When changing the setting from "automatically redirect" to something else, users must manually delete their ZEP session cookie in the browser. Logging in is otherwise not possible.

Allow saving username and password in the browser
If you want to allow the browser to save the username and password, you can specify this here.

ZEP Language
Here you set the standard language for ZEP. The language setting also includes the language-specific formatting of dates, times, and decimal numbers.

The Employees created in ZEP generally have the language set to "-Standard-." This refers exactly to the language you set here. If a language other than the standard language should permanently apply to an employee, set it for the respective employee. The login page will still be displayed in the standard language, and after logging in, the user will see ZEP in their chosen language.

The same applies to Projects: Every project has its billing language defined under Billing Settings > Format; this is also generally "-Standard-." If the invoices for a project should be created permanently in a language other than the standard language, then change the project's language under Billing Settings > Format.

If you use the ticketing system, every Customer Contact also has a language setting for their ticket access. Here, too, the language is generally "-Standard-" and can be changed if necessary.

Setting Number of Entries per Page

In ZEP, search results are often presented to you in a scrollable table, e.g., Project Management, Employee Administration, etc. By default, 15 entries per page are displayed. Here you can change this number.

The number of entries per page affects usability and speed:

  • A large number is only sensible for large or high-resolution monitors. All entries should always be visible on one screen page, otherwise the interaction between flipping through the table and scrolling in the browser is uncomfortable.

  • With a large number, the display takes longer. Since the first table page is also displayed upon the first call of a page, it creates the impression that the menu change is slower.

This setting has no effect on fully displayed, non-scrollable tables in Reports and no effect on tables in popup windows.

There is also a fixed minimum number of entries: A page break only occurs if the following page will contain at least 4 entries. This means the last page of a table can contain up to three entries more than the set number.

Display company name in Reports (header)
If you do not want your company name to appear in the header of printed Reports, do not check the box.

Retain line breaks in CSV export
If you have longer formatted texts with line breaks in the remarks field of projects/tasks and want to export them formatted that way as CSV, specify Yes here.

E-Mail

Using ZEP Mail-Client

If you click on an email address, the local mail client (e.g., MS Outlook, Lotus Notes) is called up by default. If you do not want this, you can alternatively use the integrated ZEP Mail Client by activating this option.

Advantage of the ZEP Mail Client: The length of the email is not limited.

Separator for email addresses

Set here globally whether a comma or semicolon is used as the separator between email addresses.

Once a user has saved their own email parameter settings under Profile > Email, a change to the global setting will no longer affect that user.

Sender Name for automatically sent emails and for ZEP Mail Client

This sender name is used by ZEP in automatically sent emails:

The recipient sees the following information in their mail program:

  • from: Sender Name <sender-email-address>

  • Reply to: Reply Name <reply-address>

Sender Address

This email address is used by ZEP as the email sender when ZEP sends automatic emails, e.g., for planned hour overruns, overtime notifications, or in connection with the ticket module.

If you have not configured anything specific, the default setting [email protected] applies.

The email address [email protected] is used only for sending; replies are rejected.

Using own E-Mail addresses

If you want to use your own email addresses, you should also use your own mail server that belongs to these addresses (see "Use special outgoing server for mail delivery").

Use ZEP Mailserver

However, if you use the ZEP Mailserver and your email address contains your own domain, you must update your SPF record in the DNS settings to prevent your emails from being marked as spam. This means that you must supplement your SPF record with "a:mail.zep.de". You must insert the entry "a:mail.zep.de" into the SPF record at an appropriate place, with spaces before and after it. Please contact your IT system administrator for this (not the ZEP Support Team); they should know the appropriate location.

An example of the updated entry would be "v=spf1 +a +mx a:mail.zep.de -all" or "v=spf1 +a +mx a:mail.zep.de"

Explanation of SPF Record

The SPF record (Sender Policy Framework Record) is a type of security measure that helps protect email delivery and reduce email fraud. In simple terms, it is a rule set in a domain's DNS settings to confirm which email servers are authorized to send emails on behalf of that domain.

When an email server receives an email, it checks the sender's domain's SPF record to ensure that the email originates from an authorized server. If this is the case, the email is accepted. If not, the email may be classified as spam or forged and rejected or treated accordingly.

Reply Name for automatically sent emails and for ZEP Mail Client

Here you enter the reply name that the recipient of an email automatically sent from ZEP sees.

The recipient sees the following information in their mail program:

  • from: Sender Name <sender-email-address>

  • Reply to: Reply Name <reply-address>

Reply Address for automatically sent emails and for ZEP Mail Client

Here you enter the reply address that the recipient of an email automatically sent from ZEP sees.

The recipient sees the following information in their mail program:

  • from: Sender Name <sender-email-address>

  • Reply to: Reply Name <reply-address>

Since it is usually not desired that the recipient replies to these automatically generated emails, a noreply reply address is often used.

Email Header and Email Footer

Here you can design the header and footer area of the emails sent by ZEP using a simple HTML editor.

Use special outgoing mail server for mail delivery

If you want to use your own email addresses as the sender, you can use your own mail server that belongs to these addresses (same domain).

We recommend using the ZEP Mailserver, as this helps you avoid unnecessary waiting times when using ZEP. The ZEP Mailserver accepts the emails immediately and adds them to a queue—this is then processed in the background. (You only have to supplement the SPF record on all your domains with a:mail.provantis.de so that the emails are not considered spam.) Example: v=spf1 +a +mx a:mail.zep.de -all

If sending via your mail server, ZEP must transmit all emails directly to your server, and you must wait during ZEP usage—depending on the mail provider used, this can take a few seconds. Depending on ZEP's settings, this can also affect employee time recording, as emails are sent immediately upon saving time when overtime is exceeded, the project's planned figure is reached, etc.

Enter your outgoing mail server here if you do not want to use the ZEP mail server. To do this, you define your mail server as a "Special Outgoing Server" with corresponding access data and set:

  • Sender Name for automatically sent emails: ZEP

  • Sender Address for automatically sent emails: [email protected]

In this case, nobody@localhost is not allowed to remain as the sender address, as this will become [email protected], and our SPF record defines that emails with the sender @zep.de may only be sent from our systems.

Mail Delivery via Microsoft OAuth Azure

For ZEP to be able to send emails via Microsoft Azure, access must be configured via OAuth as follows:

Azure Settings:

Then navigate via Azure Active Directory > App registrations > "+ New registration" to App registration:

  • Enter a Name, e.g., "ZEP"

  • Supported account types: Accounts in any organizational directory... and personal Microsoft accounts...

  • Redirect URI:

  • Press Register

When the app is registered, copy the "Application (client) ID" and temporarily save it in a file (e.g., azure.txt).

Now select "Add a certificate or secret" and click "+ New client secret". Here:

  • Enter Description

  • Expires: 24 months (recommended)

  • Press Add.

Now copy the code displayed as Value (Caution: not the Secret ID) and add it as a new line in azure.txt. Important: This code will not be displayed again later.

Afterwards:

  • Select the menu option API permissions, then Add a permission > Microsoft Graph

  • Delegated permissions:

    • under OpenId permissions: select offline_access

    • under SMTP: select SMTP.Send

    • under User: select User.Read (this is usually created automatically; if not, select it as well)

  • Press the Add permissions button

Microsoft 365 Admin Center:

Users > Active users > select the user > Mail > Manage email apps > "Authenticated SMTP".

ZEP Settings:

Administration > My Company > Settings > E-Mail > Change settings => Select Use special outgoing mail server for mail delivery

Fields relevant for Azure:

  • Sender Address: same domain as the username

  • Server: smtp.office365.com

  • Port: 587 (submission)

  • OAuth Id: first saved line in (e.g., azure.txt)

  • OAuth Secret: second saved line in (e.g., azure.txt)

  • Connection Security: STARTTLS

  • All others remain as before (no password needed for OAuth)

Save Then click the External Link icon. This leads to the Office 365 login page. Please complete the login. After successful login, you will be redirected back to the mailbox page. => Done!

Mail Delivery via Google Mail

Google Settings: A guide on how to create an app in Google can be found here:

You must register mail delivery from ZEP as an app (https://cloud.google.com/console). There you will receive the OAuth ID and the OAuth Secret which you must enter in ZEP.

You can find the Redirect URL in the ZEP email settings when you switch to Google OAuth. Normally, it is the following URL; here you must replace your ZEP name:

ZEP Settings:

Administration > My Company > Settings > E-Mail > Change settings

  • Use own Mailserver

  • OAuth = Google

  • OAuth ID = received after creating credentials in Google

  • OAuth Secret = received after creating credentials in Google

  • Server = smtp.gmail.com

  • Username = Your Google username

  • Save

Afterwards, an arrow symbol in a box will appear. There you must log in and grant the necessary permissions via a pop-up, if you have not already done so.

After logging in, you can send a test email using the envelope symbol.

Company Data

Please enter your company data at this point. This data is required as the Invoice Sender for creating ZUGFeRD invoices, XRechnungen, and for the Swiss QR Code. This data is also used as a placeholder variable for the Letterhead. This means that if your company data changes (e.g., change of legal form, change of address, etc.), you can make the change here, and the updated information will automatically be adopted into all your letterhead templates where you have inserted a placeholder for this data.

  • Name, Address, Postal Code, and City

  • Country Code (for ZUGFeRD, not for a mailing address)

  • Phone, Fax, E-mail, and Website/URL

  • Paypal.Me Name

  • Shareholders/Management/Board

  • VAT ID and Tax Number

  • Commercial Register Number and competent Registry Court

  • Global Identification Number Type and Global Identification Number

You must at least fully specify the Name and the Bank details (see next point "Bank details"), otherwise ZEP cannot generate pdf/a-ZUGFeRD invoices. Additionally, the "ZUGFeRD" checkbox must be activated for the customer under Addresses, and the ZUGFeRD country code must be entered.

Invoices with GiroCode/Payment Code (only with Invoicing module) Simplify invoice payment for your customers with a QR code on the invoice. This code contains the recipient, account number/IBAN, amount, currency, payment purpose, or reference, and can be read by numerous banking apps, simplifying the transfer of the data mentioned above into the transfer form.

You can specify this data under Administration > My Company > Company Data. The QR code can be output using the placeholder Payment QR Code (%R_BEZAHLCODE%) in the upper or lower invoice text (project or customer additional fields). To ensure it is output right-aligned, it can be written into a table with right-aligned column alignment.

If you use the Departments module, you can also enter this Company Data separately for various departments that act as independent companies.

Bank Details

Please enter your bank details here. This data is required for the creation of pdf/a-ZUGFeRD invoices. This data is also used as a placeholder variable for the Letterhead. This means that if your bank details change, you can make the change here under New Bank Details, and the updated information will automatically be adopted into all your letterhead templates where you have inserted a placeholder for this data. The fields Bank Name, IBAN, and BIC are also available as document variables for the letterhead.

Every bank detail record has the following fields:

  • Short Form (for identification when selecting later)

  • Currency

  • Language

For ZUGFeRD and as a placeholder for the Letterhead:

  • Bank

  • IBAN

  • BIC

Only for the Letterhead:

  • Multi-line text field (Complete text for document variable in the Letterhead)

You must at least fully specify the Company Name and the Bank Details, otherwise ZEP cannot generate pdf/a-ZUGFeRD invoices.

Additionally, the ZUGFeRD checkbox must be activated for the customer under Addresses, and the ZUGFeRD country code must be entered.

Letter Paper

Here you can upload your own letter paper with logo and company data. All Reports in pdf, doc, docx, or odt format are displayed on this letterhead.

The letterhead is used in the following Reports:

  • Cover Sheet (Project, Customer, Employee)

  • Project Status (Plan / Overall Status Plan, Time / Overall Status Time, Margin / Overall Status Margin)

  • Project Time Matrix / Employee Time Matrix

  • Expense Report (if no custom letterhead is stored)

  • Break Overview

  • Payouts

  • Working Time Overview

  • Annual Absence Summary

  • Open Items

  • Payment Receipts

  • Revenue Forecast

  • Work in Progress

Letterhead Creation

Please note our Instructions for creating the letterhead, which are available for download at this point.

If you do not store your own custom letterhead, the Standard Letterhead is always used. You can see this by the display: Standard Letterhead (Language) Portrait/Landscape format is used. This letterhead merely contains a footerwith your Company Name and the Page Number.

If you want ZEP to create your Reports ( in PDF, Word, or LibreOffice) completely including the letterhead, for example, with your Logo and further information in the header and footer, then you must create your own letterhead and upload it to ZEP.

You can upload different letterheads for these various areas:

  • General

  • Project Revenue/Project Time Verification,

  • Expense Report (available from ZEP Compact with Revenues & Costs module),

  • Employee Time Verification,

  • Offer (Quotation Module), and

  • Invoice/Credit (also used for reminders. Invoicing Module).

Login

Optionally, you can specify whether ZEP may only be accessed from certain IP addresses: Activate the checkbox Use IP Address Authentication and enter the corresponding IP addresses separated by spaces and save.

Optionally, ZEP provides you with the possibility of Login via OAuth: Under Administration > My Company > Settings > Login, specify whether you want to "Enable Login via OAuth." Select whether you want to enable this via Google or Microsoft (Azure), Keycloak, or General. Select the method first, and then the links will become visible. For secure communication of ZEP via OAuth, "CLIENT ID" and "CLIENT SECRET" must be stored in the ZEP settings.

Optionally, you can specify whether the normal ZEP Login should be locked and who is authorized to unlock the ZEP login via email if necessary.

Google:

For this, your ZEP must be registered as an app via the "Google Cloud Console" https://cloud.google.com/console. "CLIENT ID" (Google: "Client ID") and "CLIENT SECRET" (Google: "Client Secret") are generated by Google upon registration.

When registering, ensure that the address to "glogin.php" below the view directory of ZEP is stored with Google as the "REDIRECT URI" (Google: "Authorized redirect URIs").

After configuration, any employee with a valid Google account can log in with their Google access data if the email addresses of the Google account and ZEP match. The employee has another field in their data (next to the email field): Google ID: the email address of the Google account must be stored here.

The login via Google can be initiated by calling the page "glogin.php" below the view directory of ZEP. Google login can also be accessed via the link "Sign in with Google" on the ZEP login page, provided the normal ZEP login is not locked by the Administrator.

Microsoft OAuth:

For Microsoft OAuth, your ZEP must be registered as an app via the App Registration portal: https://aka.ms/appregistrations.

  • Select "New registration" and enter the "Name" and "Redirect URL" and register.

  • Select "Authentication" and enter the Logout URL and save.

  • In the registration, select "Certificates & secrets" and choose "Add new client secret." Please enter this value in ZEP under CLIENT SECRET.

  • Select "API permissions." Note that the user must have read permission on the API permissions.

  • Select "Overview": copy the "Application (Client) ID" and enter it in the Client ID field.

If you have the setting "Supported account types: My organization only" in Azure, you must copy the Tenant ID (also known as Tenant or Directory ID) from Azure and enter it in ZEP under Administration > My Company > Settings > Login > OAuth > Tenant ID.

When logging in via OAuth using Microsoft, you must mandatorily set https as the connection security (under Administration > My Company > Settings > General: Access via secure SSL connection: automatically redirect).

Password

Here you can set quality criteria for the passwords used in ZEP.

  • Password Minimum Length: Enter a minimum length for the password (minimum 4, maximum 30 characters).

  • Password Character Set: Optionally specify which character sets (Lower case letters (a-z), Upper case letters (A-Z), Numbers (0-9), Special characters) must contain elements.

  • Password Expiration Days: Optionally, you can enter the number of days a password is valid.

  • Password Allowed Attempts: You can specify how many attempts the employee has when entering the password before they are prompted to request a new password.

What happens if you have forgotten your password or exceeded the allowed number of input attempts?
ZEP then offers you: "Use this form if you have forgotten your password for ZEP. Enter your username or your email address. ZEP will send you an email with information on how to define a new password."

Sending information for setting a new password only works if an email address is stored for your user in ZEP.

Projects

Settings

Notification upon Percentage Achievement of Planned Hours

Specify here globally the percentage of planned hours at which an email should be generated to the Project Manager(s) with budget responsibility. You can optionally set whether only billably booked hours are considered.

No Email: No email will be sent.

Send Email at: You can enter up to three percentage values here (if only one value is entered, only one email is sent). As soon as a time entry exceeds one of these thresholds, the Project Manager(s) will receive an email notification from ZEP that the actual hours for the corresponding project or task (if you have stored planned figures for tasks) have exceeded the specified value. Of course, only if an email address is specified for the employee in Employee Administration. If there should be no Project Manager with budget responsibility, this email will be sent to the Department Manager (with the Departments module) or to the Administrator.

You can override these values project-specifically for any project under Data & Plan: in these projects, the project-specifically entered values will apply. Depending on the setting, all hours or only billably booked hours are considered. A prerequisite for a warning is the specification of planned hours for the project or the task.

If no Project Manager with budget responsibility and an email address can be determined, all Project Managers without budget responsibility are informed. If there are no Project Managers, all Department Managers of the project's department are informed if applicable; if they also cannot be determined (or if the Departments module is not licensed), all Administrators are informed. With every time booking, ZEP checks whether a percentage of the planned hours has been reached at the task level or project level, meaning up to two emails can be sent for each entered percentage value:

1) An email regarding the booked task or one of its superior tasks (depending on the level at which you entered the planned figures).

2) An email regarding the project.

Display in the I-Point of the task list during time recording

Display planned and actual hours in the I-Point of the task list during time recording If you activate this option, the task I-Point during time recording is supplemented with the planned figures stored in the project or the tasks.

The table of tasks displayed on the help page is expanded to include the following columns:

  • Plan: the "Planned Hours" specified for the task

  • Actual: all hours booked to this task so far

  • Plan-Actual: difference between these two figures

  • Actual (billable): the billable hours booked to this task so far

  • Plan-Actual (billable): difference between these two figures

Display actual hours in the I-Point of the task list during time recording
If you activate this option, the task I-Point during time recording is supplemented with the actual hours recorded for the project or the tasks.

The table of tasks displayed on the help page is expanded to include the following columns:

  • Actual: all hours booked to this task so far

Only display bookable tasks in the I-Point of the task list during time recording
If you activate this option, the employees will no longer see all tasks of the project in the task I-Point, but only the tasks that have a bookable status and whose duration lies within the recording period.

Only display own tasks in the I-Point of the task list during time recording
If you activate this option, the employees will no longer see all tasks of the project in the task I-Point, but only the tasks to which they are assigned as employees.

Remarks of the tasks visible in the I-Point of the task list during time recording Under Administration > Project > Settings, you set whether the remarks of the tasks should be displayed in the task I-Point during project time recording.

Every employee has an I-Point next to the list of tasks during project time recording. When they call up this I-Point, they see a list of the tasks of the configured project.

If this list should also contain the remarks of all tasks, activate the setting Remarks of the tasks visible.

Display task employees including email in the I-Point of the task list during time recording

If you activate this option, all task employees and their email addresses stored in ZEP are displayed in the task I-Point.

Display remark of the selected project in the I-Point of the project list during time recording.
Here you set whether the remark of the selected project should be displayed in the project I-Point during project time recording.

Display billing type of the selected project in the I-Point of the project list during time recording.

Here you set whether the billing type of the selected project should be displayed in the project I-Point during project time recording.

Display all project employees of the selected project including email in the I-Point of the project list during time recording

If you activate this option, all project employees with their function in the project (Project Manager) and their email addresses stored in ZEP are displayed in the project I-Point.

User with Additional Rights/Controller may create projects: If you activate this checkbox, employees with the role "User with Additional Rights" or "Controller" can create new projects (otherwise, only the Administrator is allowed to do this). Such an employee has the Projects menu item.

Internal projects are fundamentally non-billable
Projects without customer assignment are Internal Projects:

Since you cannot bill internal projects to a customer, it makes sense to only book non-billable time to these projects. It is therefore recommended to switch on the setting Internal projects are fundamentally non-billable.

When the setting Internal projects are fundamentally non-billable is switched on (yes):

  • If you create new internal projects, the default setting for Billability is set to non-billable, not changeable by employee. You can no longer change this project setting.

  • The Project Revenue and Project Time Verification reports are not offered for internal projects, as they are based on billable times, which usually do not exist in internal projects with this setting.

  • If an internal project should still contain billable times (e.g., because a customer was previously assigned), you will see this in the Project Time Report, as well as in the Project Status Plan, Project Status Time, Project Status Margin reports, and in the Overall Status reports. If necessary, you must rebook the relevant times to non-billable in the Project Time Report.

A change to the setting Internal projects are fundamentally non-billable does not automatically affect already existing projects. Even if you subsequently change a customer project into an internal project, billably booked times do not automatically become non-billable times. If necessary, you must rebook the relevant times in the Project Time Report.

Display Names

Display name for projects in table columns of reports
Set the designation with which projects should be displayed in table columns of reports:

  • Short form

  • Designation

  • Short form (Designation)

External display name for projects and tasks
Set globally the form in which projects should be displayed in external reports:

  • Short form

  • Designation

  • Short form (Designation)

External display name for tasks
Set globally the form in which tasks should be displayed in external reports:

  • Short form

  • Designation

  • Short form (Designation)

Further Settings

'with signature block in the print version' pre-fill in Project Time Verification:
Set whether the Project Time Verification report should have the default setting with signature block in the print version.

Display Project Category in Project Tables
Set whether the respective assigned project category should be displayed in the project tables.

Keywords
If you specify here "Project Manager may add keywords (Yes)," the Project Managers can also create their own keywords within a project and assign them to the project.

You can classify and search for your projects using Keywords.

You can enter new Keywords under Administration > Projects > Keywords.

Link "Send email to project employees" sends email in project language In a project, in the Project Employees menu item, you can send an email to all project employees via the link Send email to project employees.

With the Yes setting, the email is sent in the project's language (set in the project under Format > Billing Settings).

With the No setting, the email is sent in the ZEP language (set globally under Administration > My Company > General).

Link "Send email to project employees" sends email via "Undisclosed Recipients" (recipients hidden in BCC)
In a project, in the Project Employees menu item, you can send an email to all project employees via the link Send email to project employees.

With the Yes setting, the sender's email address is listed in the To field, and all other recipients are listed in the BCC field.

With the No setting, all recipients of the email are listed in the To field.

All project employees may see the "Project Plan" menu item If you set Yes here, you can additionally specify:

  • Display Planned Hours

  • Display Planned Amounts

  • Display Actual Hours

If you set this, all employees in ZEP have the Projects tab, but only the respectively assigned projects are displayed, and only the Project Plan is displayed in the selected project.

Use Project Number Number Range

Project No. Prefix
The entered text appears as the prefix in the project number. The following placeholders can be used:

  • %YYYY% - Year of the current date

  • %YY% - The last two year digits of the current date

  • %MM% - Month of the current date

  • %DD% - Day of the current date

Project No. Length
This is the length of the number that is inserted between the prefix and suffix. The number is filled with leading zeros, if necessary.

Project No. Suffix
The entered text appears as the suffix in the customer number. The following placeholders can be used:

  • %YYYY% - Year of the current date

  • %YY% - The last two year digits of the current date

  • %MM% - Month of the current date

  • %DD% - Day of the current date

Activities

Activities are designations for different work processes, independent of the project. An Activity is specified for every project time recording. These activities can be billed differently. Special hourly rates per Activity can be specified in the Price Lists (available from ZEP Compact with the Prices & Receipts module).

The distinction of Activities in project time recording is useful for later reports.

Do not define too many different Activities, as this confuses the user. It is not sensible to distinguish Activities that never need to be considered separately in a report. Better than a long list of Activities that would rarely be relevant individually is an Activity called Miscellaneous (Sonstiges).

You can store Activities in multiple languages. The entry is made in the Designation field: Click on German/English/French/Spanish, enter the designation for the short form. Depending on the language set for the employee or the project, the designation will be displayed in the language selection.

Checkboxes

is not relevant to working time, e.g., on-call duty
You can assign this property to any Activity (except travel activity), meaning that for this Activity:

  • It is not relevant to working time, i.e., it is not included in the overtime calculation. (Absences & Overtime module)

  • It causes no internal costs.

  • It is allowed to overlap with one other Activity.

  • It counts as a break according to the break regulation.

  • It does not generate subsistence costs, not even for project billing!

  • It can be billed to the customer, i.e., it can be booked as "billable" or "non-billable." It is billed even if it overlaps with another time. If it is booked as "billable" with a duration of "0," it is listed in the Project Revenue or Invoice Attachment.

Once you have applied these properties to an Activity and recorded project times for it, you cannot reverse these properties. You must first delete the recorded times.

non-billable project times are also visible on Project Time Verification, Project Revenue, and Invoice Attachment, e.g., Goodwill
If an Activity marked this way is booked as non-billable to a project, the time is still listed in the Project Time Verification and is reported in the Project Revenue and on the Invoice Attachment with the price 0.00.

Properties:

  • Can be booked as billable and non-billable.

  • Appears on the Project Time Verification, Project Revenue, and the Invoice Attachment, even if it was booked as non-billable.

  • A billably booked Goodwill Activity can be assigned a special hourly rate.

You can select this option for any Activity and also combine it with other options (travel activity, "on-call duty").

Activities marked as Goodwill are only used to determine the daily rate share in Daily Rate Projects if they have been booked as billable.

If they are booked as non-billable, a daily rate share is also calculated from these non-billablebooked times, which is listed in the Project Time Verification and reported in the Project Revenue and Invoice Attachment with the price 0.00.

Travel Activity

available from ZEP Compact Travel Expense Report.

A further special case is the Travel Activity (usually "re"). Among other things, it defines the start and end of business trips. In conjunction with the work location, ZEP automatically calculates the subsistence costs for the Travel Expense Report (unless you have switched off this function in the settings under the point "Calculation procedure for subsistence costs" by entering "no calculation").

Using Change Travel Activity, you set which of your activities should be the Travel Activity. With the checkbox may overlap with other activities, is not relevant to working time, you can specify whether travel time counts as working time for you or not.

For a Travel Activity with these properties, the following applies:

  • It is not relevant to working time, i.e., it is not included in the overtime calculation - Absences & Overtime module.

  • It causes no internal costs.

  • It is allowed to overlap with one other activity.

  • It counts as a break according to the break regulation.

  • It generates subsistence costs.

  • It can be billed to the customer, i.e., it can be booked as billable or non-billable. It is billed even if it overlaps with another time.

Once you have applied these properties to a Travel Activity and recorded project times for it, you cannot reverse these properties. You must first delete the recorded times.

Activities and Tasks

For the assignment of working hours, there is also the structuring of projects into Tasks. The following notes may be helpful in deciding between an Activity and a Task.

A work process is an Activity if some of the following points apply:

  • The process is very general and not tied to a specific project or project type.

  • A later report would be interesting that tells you how much time was booked for this work process across all projects, for example, because:

    • You pay the employee a special hourly rate for it.

    • You receive a special hourly rate from the client for it.

    • The time is not paid for by the client (e.g., travel time, overhead).

  • This Activity is relevant in the vast majority of projects.

  • After this Activity was included in the ZEP database for a while, employees booked time to it frequently and correctly. (Acceptance)

A Task, on the other hand:

  • Is rather special, tied to a specific project or project type.

  • Is a project phase or a manageable work package of the project.

  • Enables a detailed effort estimation (planned times, planned costs).

Project Status

To define a new status, enter a short form and a designation.

You can store the Project Status in multiple languages. The entry is made in the Designation field: Click on German/English/French/Spanish, enter the designation for the short form. Depending on the language set for the employee or the project, the designation will be displayed in the language selection.

You can select a color for each status; this will be displayed in the project table.

Status Order

You can move a status up or down with the arrow symbols. The sorting determines the sequence in which the statuses are displayed in the selection lists. A newly created status is always appended to the end of the list. You can move it to the correct position with the corresponding arrow symbol.
A newly created or copied project is always placed in the first status in the list.

Bookability

Specify whether this status is bookable. Only projects assigned to a bookable status appear in the selection lists during project time and receipt recording. If a status is bookable, it is displayed in bold in the table.

Filter

The Project Status can be filtered in the project reports and project planning.

Task Status

To define a new status, enter a short form and a designation.
You can store a Task Status in multiple languages. You can select a color for each status; this will be displayed in the task table.

Status Order

Order and moving function analogously to the Project Status via the arrow symbols.

Bookability

The bookability of a task is analogous to the description you can find for bookability in the Project Status.

Mail Templates

ZEP offers you the possibility to send emails at various points. For these emails, there are standardized texts included in the emails. Here you can customize the standardized text for the project mail templates To all project employees or To a single project employee. Additionally, you can optionally add files (max 5 x 20MB / max. 50MB total).

You have the option to send specific information regarding the project and employee through general Placeholders.

Please note: the placeholder Actual Hours (%ISTSTUNDEN%) always delivers only the current billably booked actual hours of the project.

You can send all Mail Templates as a test email (Preview) to your own email address. Click on German/English/Frenchin the column Test Send (to own email address), and you will receive the email in the corresponding language sent to your address.

Categories

Here you define Categories to which you can assign your Projects, respectively. This categorization serves as a search and selection criterion.

You can store Categories in multiple languages.

Keywords

The input of Keywords can help you when using the search function to find and call up Projects faster, for example.

Additional attributes

You can define Additional Attributes for customers, projects, tasks, and employees. An Additional Attribute is a field that is then present for every customer/project/employee and can be maintained via the frontend.

The following information must be provided when creating an Additional Attribute:

  • Name - This is the technical name of the attribute under which it can then also be read or set in the SOAP interface.

  • Designation - Multi-language designation that is displayed in the user interface.

  • Remark - An (internal) remark, e.g., to describe the attribute.

  • Type - The data type of the attribute. Options are: Text, Yes/No, Number, Decimal Number, Percentage, Date, URL, E-mail, Selection List, Employee Selection.

    • Details on the data types:

      • Selection List: Here you can specify one or more options that can then be provided as a single or multiple selection.

      • Employee Selection: An existing employee can be selected and assigned via this.

Additional Attributes are displayed on the Data page of the respective object and can be entered in the edit mode.

Currently, Additional Attributes can be used as follows:

  • In the administration views via configurable columns.

  • As a placeholder on invoices - The value can be inserted via the popup.

  • Via document variable in the Letterhead. An Additional Attribute is available as a document variable under its name.

  • Via SOAP in the <attribute> area.

Customers

Settings

Customer sorting in the selection lists by Name

Customer sorting in the selection lists by Name instead of Customer No.: If you activate this checkbox, customers in the selection lists (e.g., during project planning and project status reports) are sorted by customer name.

User with Additional Rights/Controller may create customers
Only an Administrator is allowed to create customers. Optionally, you can allow employees with the role User with Additional Rights or Controller to create new customers (Yes setting). Such an employee is automatically entered as the Customer Manager (with the permission to change customer data) for this newly created customer. If you subsequently remove this customer responsibility from such an employee (at the customer level), they can no longer edit this customer.

Default VAT for new customers
available from ZEP Compact Revenues & Costs

When creating a new customer, the value entered here is pre-filled.

Only with Invoicing module:

  • Default Discount Period for new customers

  • Default Payment Term for new customers

Default 'Flat travel rate for a continuous trip involving multiple projects' for new customers: available from ZEP Compact Travel Expense Report

As a default setting for new customers, you can set:

For Flat travel rate per day, you have these two options:

  • The flat travel rate is fully charged to every project of this customer involved in the trip.

  • The flat travel rate is distributed among the projects of this customer involved in the trip according to their proportion of hours. This setting is usually only sensible if the same flat travel rate per day applies to all involved projects of this customer.

For Flat travel rate per trip, you have these two options:

  • The flat travel rate is fully charged to every project of this customer involved in the trip. (as previously in ZEP 4.5)

  • The flat travel rate is fully charged to the first project of the trip; no flat travel rate per trip is charged for other projects involved in the trip.

In the menu item Customers > Billing Settings > Travel Settings, you then have the option to individually define for each customer how the flat travel rates should be calculated for that customer.

Industries

In Customer Administration, you can assign your customers to an Industry and filter the list by Industry. You define these Industries here.

You can store Industries in multiple languages. The entry is made in the Designation field: Click on German/English/French/Spanish, enter the designation for the short form. Depending on the language set for the employee or the project, the designation will be displayed in the language selection.

Categories

Here you define Categories to which you assign your customers, respectively. For example: prospect for one of your products, sales partner, or cooperation partner, etc. In Customer Administration, you assign each customer to a category. This categorization serves as a search and selection criterion.

You can store Categories in multiple languages. The entry is made in the Designation field and can also be done in different languages. Depending on the language selected by the employee or the project, the designation will be displayed in the respective language.

Contact Person Categories

At this point, you define Categories to which you assign your Customer Contacts, respectively. For example: Christmas Card, Info, etc. In the contact person's menu, you can then assign one or more categories. This categorization serves as a search and selection criterion under Reports > Customers > Customer Contacts.

Additional Attributes

You can define Additional Attributes for customers, projects, tasks, and employees. An Additional Attribute is a field that is then present for every customer/project/employee and can be maintained.

When creating an Additional Attribute, the following information must be provided:

  • Name: This is the technical name of the attribute, under which it can then also be read or set in the SOAP interface.

When using Personio: The Personio attributes are adopted if the name is the same.

  • Designation: Multi-language designation that is displayed in the user interface.

  • Remark: An (internal) remark, e.g., to describe the attribute.

  • Type: The data type of the attribute. Options are: Text, Yes/No, Number, Decimal Number, Percentage, Date, URL, E-mail, Selection List, Employee Selection.

Details on the data types:

  • Selection List: Here you can specify one or more options that can be provided as a single or multiple selection.

  • Employee Selection: An existing employee can be selected and assigned via this.

Additional Attributes are displayed on the employee's Data page and can be entered in the edit mode.

Current uses of Additional Attributes:

  • In the administration views via configurable columns.

  • Via document variable in the Letterhead: an Additional Attribute is available as a document variable under its name.

  • Via SOAP in the <attribute> area.

Employees

General

Record attendancees in addition to Project Times
If you want employees to clock in/out in addition to recording project time, check the box here. You will then see the clock events of the clock-in and clock-out occurrences of the employees under Reports > Employees > Clock In / Clock Out.

Activate Freelanceers & Credits
If you have Freelance Employees whom you want to bill using Credits, check the box here.

Freelance Employees (excluding Administrators and Department Managers) are not permitted to see other employees in reports, e.g., in the Absence Overview Sometimes it is desired that Freelance Employees do not receive information about other employees in ZEP. If this is the case for you, check the box here.

Employee sorting in the selection lists
Here you can set how employees should be sorted in the selection lists in ZEP. Choose between Username, First Name, and Last Name.

Employee formatting in Customer Reports Here you can specify how an employee's name should be displayed in Reports for customers. You have the choice between:

  • Username

  • Last Name, First Name

  • Username (First Name Last Name)

Employee initials Reports for customers are Reports > Employees > Time Verifications, Reports > Projects > Project Revenue/Customer Revenue, and Project Time Verification.

Employee formatting in internal Reports
Here you can specify how an employee's name should be displayed in internal Reports. You have the choice between:

  • Username

  • Last Name, First Name

  • Username (First Name Last Name)

Employee initials Internal Reports are, for example, Reports > Projects > Project Status, or Overall Status.

Project Time Report Total Sum: Person-Days (PT) correspond to In the Project Time Reports, the total number of hours in the report period is always displayed at the top left. Additionally, the total hours are displayed in Person-Days (PT). Here you specify the number of hours that corresponds to one Person-Day, e.g., 8 hours.

PT display with up to x significant decimal places
Enter a value between 0 and 10.

Notify before expiration of an employment period
Here you can specify whether and who is notified by email before the end of an employee's employment period. If you select one of these options, a (System) Task under Administration > System > Tasks "Employment Periods" is automatically scheduled, which is executed daily. The mail template for the notification emails is located in the master data: Notification before end of employment.

Every employee can specify the date up to which they have finished recording their project times (receipts, absences, if applicable) and thus release them.
Here you set whether ZEP users can release their recorded data (project times, receipts, absences, if applicable). This means every employee can indicate that all project times (receipts and absences, if applicable) are correctly and completely recorded.

In the project time table under My ZEP > Project Times, the symbol with the last entered "Released until Date" can be found.

When employees release their project times, ZEP checks whether there are days in that period where less than half of the target time was booked. ZEP asks whether the data should still be released.

  • Which period is checked? - Since the previous release date, but a maximum of one year since the last month-end closing.

  • Which message appears? - If more than 10 days are underbooked in this period, the number of days is shown; if up to 10 days are underbooked, a list of the dates appears.

Subsequently, employees can no longer edit their project times, receipts, or absences for the time up to and including the release date.

All changes are still possible in Administration. A Project Manager can still rebook project times and receipts within their projects

If an employee has entered a Release Date, they can no longer undo it.

If the Release Date must be changed, a ZEP Administrator can correct the Release Date at any time in the employee's Data submenu item.

Additionally, you can specify whether and to whom a notification should be sent.

Send notification when an employee has granted the release of their project times, receipts, and absences
Optionally to Administrators, Project Managers, Department Managers, Department Managers of superior departments, and additional recipients.

A Project Manager sees a symbol for the Release Date in their project under Project Employees in the table. This symbol is blue if the release is later than the start of the report period (i.e., if the project employee assignment is displayed for October, the symbols are blue if the release is October 1st or later), otherwise gray. The exact Release Date is visible via mouseover.

An Administrator can see this Release Date under Employees and view and change it under Employees > [Employee Name] > General > Data. If you also use the Absences & Overtime module, you see the gray-blue release symbol next to the gray-yellow lock symbol under Administration > System > Month-end Closing.

A Department Manager (only with the Locations & Departments module) views or edits the Release Date under Departments > Employees. If the Absences & Overtime module is also used, the Department Manager can see the Release Dates (gray-blue release symbol next to the gray-yellow lock symbol) of the employees under Department > Employee Locks.

Display Release Date instead of lock in Employee Administration
Specify whether a "released until" column with the corresponding date should be displayed in the employee table under Employees instead of the "release lock."

Optionally specify whether the employee should be notified when they are locked or unlocked for a month.

Pre-fill 'with signature block in the print version' in Time Verification Detail and Employee Project Time Verification
If you want a signature block to be displayed in the print version of the Reports for Employee > Time Verification Detail, you can pre-set this option here.

Pre-fill 'with signature block in the print version' in the Expense Report
If you want a signature block to be displayed in the print version of the Reports for Employee > Expense Report, you can pre-set this option here.

Dashboard-Settings

Display Current Employee Birthdays Widget: Various widgets can be added to the Dashboard in ZEP for viewing. This includes a widget that displays the birthdays of employees (provided they have been maintained for the employees).

This setting controls whether the widget is available for display.

Defaults for new employees

Default working days and regular working hours for new employees

Here you specify which days are working days and the Regular Working hours in hours for each working day. This default setting is automatically adopted when creating new employees. Of course, you can override this default setting for the individual employee.

Default vacation entitlement per year for new employees

Please enter a value for the annual Vacation Entitlement. The setting made here is pre-set as the default value in the Employee Administration and can be overridden for the individual employee.

Default Vacation Days and Absence Days

This setting is primarily relevant for part-time employees:

  • Set correspond to calendar days if the employment contract of a part-time employee stipulates the same number of working days as for a full-time employee, and you therefore enter an average value per day as the Regular Working Time. Absence Days correspond to calendar days. Every whole Absence Day has the same value. Every whole vacation day means one day deducted from the vacation quota.

  • Set convert according to regular working time if the employment contract is such that the number of vacation days was calculated depending on part-time employment. Absence Days correspond to full-time working days. Every whole Absence Day is only worth as many hours as the Regular Working Time of the relevant weekday. If the employee takes a whole day of vacation, this corresponds to the Regular Working Time of the relevant weekday in hours, converted into full-time working days. Example with 8 hours per full-time working day: If the employee only has 4 hours of Regular Working Time on Friday and wants to take the entire Friday off, only half a day of vacation is deducted from their vacation quota.

For full-time employees who have the same Regular Working Time every day, this setting makes no difference.
Exception: If full-time employees have different amounts of Regular Working Time on different weekdays, and if less vacation should be used for the shorter days than for the longer working days, you can also consider the setting "convert according to regular working time" for full-time employees.

If this setting changes for an employee (i.e., if a vacation day is suddenly worth more or less because the employment contract has changed), ZEP will NOT automatically convert the vacation entitlements / remaining vacation. You must agree on the change with the employee, enter the new vacation entitlements, and manually enter an adjustment if necessary.

For (freelance) employees with Regular Working Time 0, only the setting "correspond to calendar days" is suitable. Conversely: With the setting "convert according to regular working time," it no longer makes sense to define working days with Regular Working Time 0.

Overtime hours compensated by salary per month

If you have employees in your company whose employment contract includes a regulation on overtime hours compensated by salary and you have activated the setting deduct inclusive overtime from monthly hour balance under Administration > Overtime & Absences > Settings, you can specify a value and a calculation type for the overtime hours compensated by salary per month here. These values are then automatically adopted for a new employee.

In the menu item Regular Working Time of a selected employee, you can individually adjust the default setting.

Default break regulation for new employees

Here you can specify which break regulation should be used as the default setting for new employees. This setting is pre-set as the default value in the Employee Administration and can be overridden for the individual employee.

Attendance

An employee requires at least the authorization level "User with Additional Rights" to view the current Attendance of all employees under My ZEP > Reports. If you do not check the box here, then all employees, including "Users," will see the current Attendance of all employees.

Employee may only see current attendances in their own department (and downwards in sub-departments) under My ZEP > Reports.
Check the box here if you want an employee to only be able to see the Attendance of employees in the same department (and sub-departments).

For employees with the "Consideration of Attendance Times" setting.
Set whether employees for whom Attendance times are considered can view their own Clock In/Out Report under Reports > My Reports. Additionally, you can set whether an info notification with the clocked attendances appears during project time recording.

Recipient of the info email if an error occurred during clocking in/out.
Specify to whom ZEP should send an info email if an error occurred during an employee's clocking in/out.

Location Transmission
Decide whether the device's location should be transmitted when using the app. This setting can be individually adjusted for each employee.

Text modules

Here you can define so-called Text Modules with standard phrasing and placeholders. You can then easily insert these Text Modules when writing an email (Insert Placeholder/Text Module).

Click New Text Module and enter the Name for the Text Module in the dialog window (select the corresponding language). Enter the desired text in the Content field. You can also embed certain Placeholders here, e.g., %I_VORNAME% %I_NACHNAME%; these Placeholders will then be replaced in the email with the first and last name of the email's author, respectively.

Mail Templates

ZEP offers you the possibility to send emails at various points. For these emails, there are standardized texts included in the emails. Here you can customize the standardized text for the Employee Mail Template. You have the option to send specific information regarding employees through general Placeholders. The Placeholders will be displayed to you when you click into the content text field. Additionally, you can optionally add files (max 5 x 20MB / max. 50MB total).

You can send all Mail Templates as a test email (Preview) to your own email address. Click Test Send (to own email address) and make the desired language selection (currently German, English, French, Spanish, and Polish); you will then receive the email in the corresponding language sent to your address.

Categories

You can define any number of Categories with a short form and designation for employees, for example, internal, external, part-time, full-time.

You can store Categories in multiple languages. The entry is made in the Designation field: Click on German/English/French/Spanish, enter the designation for the short form. Depending on the language set for the employee or the project, the German, English, French, or Spanish designation will be displayed.

In Employee Administration, you can assign any number of Categories to each employee. You can filter the Project Time Report by these Categories: Under Reports > Employees > Project Time Report, you can display all project times for employees of a specific category. The same applies under Project > Reports > Project Time Report.

Additional attributes

You can define Additional Attributes for employees. An Additional Attribute is a field that is then present for every employee and can be maintained.

When creating an Additional Attribute, the following information must be provided:

  • Name: This is the technical name of the attribute, under which it can then also be read or set in the SOAP interface.

When using Personio: The Personio attributes are adopted if the name is the same.

  • Designation: Multi-language designation that is displayed in the user interface.

  • Remark: An (internal) remark, e.g., to describe the attribute.

  • Type: The data type of the attribute. Options are: Text, Yes/No, Number, Decimal Number, Percentage, Date, URL, E-mail, Selection List, Employee Selection.

Details on the data types:

  • Selection List: Here you can specify one or more options that can be provided as a single or multiple selection

  • Employee Selection: An existing employee can be selected and assigned via this.

Additional Attributes are displayed on the employee's Data page and can be entered in the edit mode.

Current uses of Additional Attributes:

  • In the administration views via configurable columns.

  • Via document variable in the Letterhead: an Additional Attribute is available as a document variable under its name.

  • Via SOAP in the <attribute> area.

Prices & Receipts

Basic Price Tables

Define a Base Price List for your company.v

It will apply to the billings and reports for projects for which there is neither a specific Project Price List nor a Customer Price List for the associated customer.

The Base Price List also serves as a copy template for Customer Price Lists.

You specify the date from which the Price List is valid. Whenever you define a new Base Price List for your company starting from a certain date, you also enter it in ZEP as a new Price List with a new start date of validity.

Every Price List consists of four parts:

  • Daily Rates per Price Group: For billing by daily rates, these prices are charged according to the price group of the project-employee assignment. (If a project is billed by hourly rates, the daily rate table can be left empty.)

  • Base Hourly Rates per Price Group: The base hourly rates are calculated for all Activities for which no special hourly rate is defined.

  • Special Hourly Rates per Activity and Price Group: You could, for example, determine that a different hourly rate is paid for a certain Activity.

  • Price Factors: Here you can additionally specify time-dependent factors for billing.

    Price Factors are time-dependent factors that can be coupled to a Price List. If, for example, a special hourly rate is to be defined for night and weekend work, call up the corresponding Price List(s) (Base Price List, Project and/or Customer Price List) and click on the Add Price Factors link and enter the corresponding factors. Additionally, you can also add special Price Factors for other Activities.

You can also explicitly enter no entries available for prices in Price Groups in Price Lists. Every price (hourly and daily rate) for a Price Group in a Price List can be set to no entries available if you remove the checkmark in the respective checkbox. This then leads to an error message in various reports (e.g., in Project Revenue, etc.) that the price is not defined, which is intended in this case.

Price Groups

You can store Price Groups in multiple languages.
The entry is made in the Designation field: Click on German, enter the German designation for the short form; click on English, enter the English designation, and so on. Depending on the language set for the employee or the project, the respective designation will be displayed.

With the help of Price Groups, the employees of a project are divided into differently paid categories.

In Employee Administration, you specify a Price Group for every employee when creating them. This is pre-set later in project planning when you (or the respective Project Manager) assign an employee to a project, but it can also be changed individually.

In the Price Lists, you will always define Hourly Rates and Daily Rates based on the different Price Groups. This applies to the Base Price List(s), as well as to customer-specific Price Lists or project-specific Price Lists.

Here in the Master Data Administration, you manage the list of Price Groups that should be available for selection in Employee Administration, employee-project assignment, and Price List entry. At least one Price Group is mandatory.

Inactivate Price Groups

Price Groups cannot be deleted because this would affect old reports and current planned/actual comparisons or cause them to deviate from earlier reports. To remove no longer needed Price Groups from the display, you can inactivatethem:

Call up the corresponding Price Group for modification and place a checkmark in the inactive checkbox.

In existing Price Lists (Base, Customer, Project Price Lists), the inactive Price Group is displayed with the note inactiveif values for daily or hourly rates are still assigned to this Price Group. As soon as all values are set to 0, the inactive Price Group is hidden. When copying Price Lists, the old Price Lists are copied identically, meaning inactive Price Groups may become visible again during this process.

Daily rate portions

Here it is specified for which number of hours you calculate which share of the daily rate. This is the basis of billing for all projects with the billing type effort based on daily rate.

The definition of Daily Rate Shares established here in the master data applies to all projects that have not defined their own definition of Daily Rate Shares.

When defining Daily Rate Shares, you can use up to 4 decimal places for both the from hours and the to hours(depending on the minute grid set in ZEP; if you have set a 15-minute grid, specifying 2 decimal places is sufficient).

For the Daily Rate Shares, you can enter up to 8 decimal places. ZEP displays the Daily Rate Shares in the reportswith at least 2 and with up to 8 decimal places (depending on the definition). When an individual project is evaluated, exactly the Daily Rate Shares that apply to this project are considered, and a maximum of as many decimal places as specified are displayed.

Please note the following when defining Daily Rate Shares:

  • They must be created contiguously from 0 - 24.00 hours.

  • If you incorrectly create the following Daily Rate Shares, for example:

    • 0.25 - 4.00 hours 0.5 Daily Rates

    • 5.25 - 12.00 hours 1.0 Daily Rates

    • 12.25 - 14.00 hours 2.0 Daily Rates

    • ZEP calculates no Daily Rate at all for 4.5 hours and for more than 14 hours of work.

Methods of Payment

When recording Receipts, the employee must specify whether they paid privately (generally Payment Method private) or whether the invoice was settled by the company (generally Payment Method company). You can define additional Payment Methods for your company here, e.g., one for each of the different company credit cards.

You can store Payment Methods in multiple languages. The entry is made in the Designation field: Click on German/English/French and enter the German/English/French designation for the short form. Depending on the language set for the employee or the project, the German, English, or French designation will be displayed.

Reimbursement of Receipts

If the employee specifies the reimbursement payment method when "Recording Receipts," the amount appears in their Expense Report. If you want to change which Payment Method should result in a reimbursement in the Expense Report, click the link Change Reimbursement. You can specify your desired Payment Method for reimbursement (provided it is not already in use).

Tax Rates

When recording Receipts, the employee specifies the amount and the tax rate. Enter here the VAT Rates that should be available for selection for receipt recording. You can set obsolete VAT Rates to inactive; they will then no longer be offered for selection, but are still available for changes.

Exchange Rates

Currencies and Exchange Rates are recorded here. One of these currencies is used as the Base Currency in ZEP. All Exchange Rates are specified in relation to the Base Currency. Accordingly, the rate of the Base Currency is 1.0.

Example:

  • One Euro has the value 1.00000

  • For one US Dollar, you must pay 0.79530 Euro, i.e., 1 USD has a rate in EUR of: 0.79530 You enter this amount in the "Rate (in EUR)" field.

You can manage your Exchange Rates here manually or you can update the respective entered Exchange Ratesautomatically via the ZEP Scheduler under Administration > System > Tasks > Update Exchange Rates.

Every currency defined here in the master data under Exchange Rates is updated with the current rate. The rate is pulled by ZEP from the website Fixer.io. Please pay attention to the correct currency code!

In some reports (e.g., Travel Expense Report for the employee, Overall Status), all monetary amounts are converted into the Base Currency. The flat rates for vehicle types and work locations are also specified in the Base Currency. A currency can have different Exchange Rates over time. The period of validity for each Exchange Rate can be limited in the "valid until" column. In reports, the current Exchange Rate is used to convert a receipt into the project currency (conversion rate at the receipt date) or to convert an invoice amount from the project currency into the Base Currency(conversion rate at the invoice date).

Conversion Rate Date

  • For Receipts: the Service Date

  • For Times, Mileage Allowance, Subsistence Costs, Flat Travel Rates (internal costs or billing): the Date of the Project Time

  • For Invoice Attachment, Project Revenue, the table of all used rates appears at the end.

  • For Planned Amounts (in Project Status and Overall Status, even if the planned amount is taken as a lump sum amount to be billed): the Start Date of the project.

  • When entire invoices need to be converted into another currency (e.g., Open Items, Revenue Forecast): Invoice Date of the respective invoice.

In the reports, monetary amounts are rounded to two decimal places.

Exception: Monetary amounts in Swiss Francs (currency designation "CHF") are rounded to 5 cents if you specify this option with Yes under Administration > Project Time & Receipts > Settings.

If you want to change the Base Currency, click the link Change Base Currency: Mark the currency that should be your new Base Currency in the Base Currency column. Please note: If you change the Base Currency, all Exchange Ratesmust be adjusted accordingly! The same applies to the flat rates for vehicle types and work locations!

Base Currency

What role does the Base Currency play in ZEP?

  • ZEP creates cross-project and cross-departmental reports in the Base Currency.

  • You specify the prices in the Base Price Lists in the Base Currency.

  • You specify the employees' internal hourly rates in the department currency if the departments module is used, otherwise in the Base Currency.

  • The Base Currency applies to customers, projects, and departments as long as you do not specify a different currency.

  • You also specify the flat rates for locations (subsistence costs) and vehicles (mileage allowance) in the Base Currency by default, but you can also explicitly choose a different currency.

  • You can define a different currency as the Base Currency using the link Change Base Currency.

Caution: When changing the Base Currency, amounts are NOT automatically converted!

Types of receipt

The employee can assign each Receipt to a Receipt Type when recording Receipts. Some typical Receipt Types are already included in ZEP.

You can store Receipt Types in multiple languages. The entry is made in the Designation field: Click on German/English/French and enter the German/English/French designation for the short form. Depending on the language set for the employee or the project, the German, English, or French designation will be displayed.

Default Setting by Receipt Type

You have the option to define specific Default Settings for each Receipt Type. These quasi-Standard Receipts simplify receipt recording for employees and help avoid errors. The Administrator can define the default setting for the following fields for each Receipt Type in the master data:

  • Payment Method

  • Tax Rate

  • Amount and billable amount

  • Currency

  • Service Date may deviate

If a Default Setting is defined, these values are used when recording new Receipts. If no Default Setting is defined, the input fields are pre-filled with the details of the last booked receipt.

Change Short Form of the Receipt Type

You can rename the Short Form of the Receipt Type by clicking the pen symbol, entering the new short form, and saving.

Deviating Service Date

If the Default Setting Service Date may deviate has been set for a Receipt Type, an additional checkbox is displayed during receipt recording. If you check this box, you can specify a second date that deviates from the Booking Date. This date is the so-called Service Date, meaning the receipt is calculated further to the project at this time. For determining the internal costs of the project, the Booking Date is used, as usual. If the payment method is private, this receipt is also listed on the employee's Expense Report at the Booking Date.

Mail templates

ZEP offers you the possibility to send emails at various points. For these emails, there are standardized texts included in the emails. Here you can customize the standardized text for the Receipt Mail Template. You have the option to send specific information regarding the receipt and employee through general Placeholders.

You can send all Mail Templates as a test email (Preview) to your own email address. Click on the column "Test Send (to own email address)" on German"/"English"/"French"; you will then receive the email in the corresponding language sent to your address. Additionally, you can optionally add files (max 5 x 20MB / max. 50MB total).

The Mail Template Receipt Details is sent when an email link (envelope symbol behind an employee's name) is clicked in a receipt table (e.g., Reports > Employees > Receipt Report, Reports > Project > Receipt Report).

Project Times & Receipts

Settings

Retrospective Recording for Project Times

  • Only for today and additional days back If you do not specify additional days back, time recording is only permissible for the respective current day. If you specify that you want to record X days back, these days are added to the setting.

  • Only for current week and additional days back If you set "... additional days back: 0," recording is allowed for the current week (Monday to Sunday). Optionally, you can additionally specify with this definition:

Allow recording for the previous week on Mondays

  • Meaning, retrospective recording for the previous week is allowed on Mondays. If you specify that you want to record X days back, these days are added to this setting. (With the setting "5 days," this means that on Mondays, you are allowed to record retrospectively for the last week up to Monday plus 5 days, i.e., up to Wednesday of the week before last. On Tuesdays, you are allowed to record retrospectively up to Wednesdayof the previous week.)

You can define a separate, independent Retrospective Recording period for receipt recording.

Allow Forward Booking for Time Recording and Receipt Recording

Specify how many days into the future Project Time Recording and Receipt Recording should be possible. You can choose whether the forward booking should be restricted to a number of minutes, or whether your employees are allowed to book several days in advance.

Allow Double Bookings
Specify whether times can be booked parallel to each other.

Multi-line remark field in Project Time and Receipt Recording
If you want your employees to add longer remark texts to the booked times, you can set here that the remark field in the Project Time Recording mask is several lines large.

Enforce Remark Text
If you want a remark to be entered for every time entry and every recorded receipt, specify this here.

Pre-fill Remark Text from the last recorded Project Time / Receipt
Here you can determine whether the remark text should be pre-filled with the remark text of the last recorded project time during time recording or not. This setting also relates to the recording of receipts, i.e., whether the remark text of the last recorded receipt should be pre-filled or not.

Allow Time Recording on holidays and days that are not working days (i.e., weekends)
If your employees also work on days that are not set as working days in the Regular Working Time, you should check the box here.

Display days that are not working days
You can decide whether the non-working days (i.e., weekends) should also be displayed in the Project Time Recording table. Even if non-working days are generally switched off: As soon as a booking has been made on a non-working day, that day becomes visible in the table.

Display of gaps in Project Time Recording
Here you can specify whether breaks (times for which no time entries were recorded) should be marked as a gap.

If you activate this option, the gaps in the daily schedule are indicated by a larger spacing in the project time entry table on the "Record Project Time" page.

These gaps are seen as breaks by ZEP. However, if you have simply forgotten to record time here, ZEP now makes it easier for you to fill this gap as follows: When you click on the corresponding gap, the end time of the previous entry is copied as the from-time and the start time of the following entry as the to-time into the upper recording field. Then specify the project/task/activity and remark accordingly, and you can easily fill this gap.

If you use time recording without from/to times (i.e., the ZEP Compact product variant without travel times, and "Recording by duration" checked in the settings), then there are no gaps and this setting is meaningless.

Pre-filling 'from-time' for a new day

Specify whether users should find a predefined time when ZEP starts, or whether the project time recording should be pre-set with the current time (standard) for a new day.

Minute Grid

Here you can choose whether the project time should be recorded in a 1, 2, 5, 6, 10, 15, 20, or 30 minute grid.

If you choose the decimal representation of times, we recommend a 3 or 6 or 15 or 30 minute grid. With 1, 2, 5, 10, and 20 minute grids, you accept rounding differences in the display, as this grid can result in periodic numbers when converting into the respective hourly share, which are displayed rounded in various tables and reports (hours to 4 decimal places, monetary amounts to 2 decimal places). The correct numbers with 10 decimal places are used for calculations.

However, if you recalculate with the displayed rounded numbers, you may arrive at a different final result. Although the final result displayed by ZEP is the correct one, this can lead to confusion regarding project billing. We therefore recommend a 3-minute, 6-minute, 15-minute, or 30-minute grid as the Minute Grid. If the Minute Grid is changed, editing project times that were recorded in a different grid is only possible to a limited extent.

Example: You work with a 1-minute grid and record a time from 11:04 to 11:17. You then switch to a 15-minute grid. You then call up the recorded time booking, e.g., to correct a typo in the remark field. In the change page, the "old" time is "forced" into the "new" grid by rounding, resulting in 11:00 to 11:15. This is saved or attempted to be saved when changing the booking. The change may then no longer be possible due to overlap, because another project time is already booked until 11:04 (according to the old Minute Grid).

Default Meals

In ZEP, meals (breakfast, lunch, or dinner) that an employee received during their trip must be specified for the relevant day. This results in the meal flat rate being deducted from the subsistence costs for that day, e.g., if breakfast was included with the overnight stay or the employee was invited to dinner/lunch by the customer.

Here you can make a Default Setting for the pre-filling of these meals (the employee can override this default setting individually):

  • No Default Setting

    • i.e., the employee specifies themselves whether and which meal they had on that day.

  • Fixed Default Setting optionally for breakfast, lunch, and/or dinner

    • the specified meals are already pre-filled for a day with a work location that is not the Primary Place of Work; the employee only has to remove the pre-filled setting if they did not have a meal.

This is a first-time and one-time default setting for a new day with a work location that is not the Primary Place of Work; i.e., if the employee has made a different setting for this day, ZEP will no longer automatically change that setting.

This only takes effect if the employee has the setting for subsistence costs.

Working Hours, Target Time, as well as Planned, Overtime, and Deficit Hours in Hours:Minutes Format

Set whether the times recorded in ZEP should be displayed in decimal format or in hours:minutes format.

  • Setting No

    • Decimal representation: 15 minutes are displayed as 0.25 hours, 30 minutes as 0.50 hours. If you have set a ZEP-recommended minute grid (3, 6, 15, or 30), only 2 decimal places are needed. However, if you have a 1-minute grid, for example, the hours are displayed rounded to 4 decimal places (5 minutes correspond to 1/12 hour, or 0.0833333333...).

  • Setting Yes

    • Representation in Hours:Minutes: 5 minutes are displayed as 00:05 hours, 1 hour and 30 minutes as 1:30.

This explanation also applies to the setting option "Display Project Time Verification, Project Revenue, and Invoice Attachment in Hours:Minutes format.

Expense Report, Project Time Verification, Project Revenue, and Invoice Attachment: Activities and Receipt Types with Designation or Short Form and Legend

Specify here globally how Receipt Types and Activities should be displayed in the mentioned Reports:

Expense Report, Project Time Verification, Project Revenue, and Invoice Attachment: Activities and Receipt Types

  • with the respective designation in the table (here "Activity" is also specified as the column header) or

  • Short Form and Legend. This setting uses the short form (in the table) and the legend below the table.

Recording a billable time that falls into a surcharge period according to the price list: Employee is asked and can specify whether this surcharge should actually be applied.

It can happen that employees voluntarily work in the evening, at night, or on weekends for a project, even though it would not be necessary, and consequently, no Price Factors should be calculated. Here you set how to proceed in this case:

  • Yes: If the price list used has Price Factors for specific times, the employee will be asked during their time booking whether the Price Factors should apply to this project time. (Please note, in case of overlaps with already recorded times, the question regarding the Price Factors comes first, followed by the question of whether the time should be overwritten.) The selection of whether the time is subject to a surcharge can also be changed retrospectively: Call up the relevant time for modification and save; the question will then be displayed again and can be changed as desired. A time entry with the specification that the Price Factor should not be applied is marked with a blue money symbol.

  • No: Any existing Price Factors are calculated by default without inquiry.

Project Time Recording: Display Tasks including superior Tasks

If you want to display not only the Task but the Task hierarchy—i.e., all possibly superior Tasks—under My ZEP > Record Project Times, you can set this here.

Work Break regulation

If you want to observe or even enforce the legal requirements for Break Regulation in your company, you can store this here in ZEP. Additionally, you can also define Core Working Hours within a Break Regulation. If you do not want a Break Regulation in ZEP (i.e., employees are responsible for correctly recording their breaks themselves), disregard this point.

What are breaks?

In ZEP, unbooked periods between two time entries are considered breaks. Additionally, Travel Times that are notbooked to a vehicle (e.g., travel by plane or train or as a passenger), so-called passive travel times, count as Break Times in the sense of the Break Regulation, meaning such passive travel times are not counted as Working Time (in certain Reports)! These travel times are deducted from the Working Time in the corresponding Reports and listed as a break in the sense of the Break Regulation.

These travel times are not deducted from your working hours (they count as working time in terms of overtime relevance).

Travel Times in a vehicle (e.g., car), so-called active travel times, are not considered breaks in the sense of the Break Regulation, as ZEP assumes that you were driving yourself and thus cannot take a break.

In Austria, the regulation applies: "For active travel time, the extension of the daily maximum working time is a maximum of 12 hours if the work is performed by ordered driving of a vehicle, provided this does not constitute the employee's main activity." This means here an employee is allowed to work additional hours.

Create Break Regulation

Here you create a Break Regulation for your company (or multiple ones). The Standard Break Regulation is already created, in which the minimum breaks according to § 4 ArbZG (German Working Hours Act) are entered.

If you want to create a new Break Regulation, click Create New Break Regulation, enter a name, and save.

Specify the date from which the Break Regulation is valid.

You can choose whether you want to have a Minimum Rest Time. This refers to the time span between two working days.

If you specify no Minimum Rest Time, you only need to specify the maximum working time per day in hours in the sense of the Break Regulation; if applicable, also enter the additional hours for active travel times.

If you specify a Minimum Rest Time, enter it in hours in the sense of the Break Regulation. This is the time span that must be maintained at least between two working days or shifts. Also specify the maximum working time per day in hours in the sense of the Break Regulation. Enter the additional hours for active travel times, if applicable.

You can enforce compliance with the defined break rule:

  • If you do not activate the checkbox Enforce Compliance, employees will only be warned during the recording of their project times that they are violating the Break Regulation regarding Minimum Rest Time / Maximum Working Time / Minimum Break Length if they do not adhere to the defined requirements. But a correction is not enforced.

Exception: If a "Fixed Break" is defined, compliance with it is always enforced (the break is automatically cut out when recording project time).

  • If you activate the checkbox Enforce Compliance, employees are blocked from Time Recording for the following days when they fail to comply with the defined rules, until the violation is corrected. Additionally, other actions (e.g., time Release, invoicing) are also blocked.

  • You can switch the warning for violation of the Break Regulation on or off at any time via the checkbox If the Break Regulation (Maximum Working Time, Minimum Breaks, Core Working Hours) is not complied with, the user receives a warning already during recording (My ZEP > Project Times, App, Terminal): Yes / No.

The Month-end Report, the Working Time Overview, the Break Overview, and the Month-end Closing continue to show non-compliance.

If you use the Absences & Overtime module, you can optionally specify whether exceeded Maximum Working Time and non-complied Minimum Breaks should be deducted from the employee's Overtime Account. (Non-complied Minimum Rest Times are not deducted.)

Calculation Procedure for Missing Breaks

Specify how the deduction for missing breaks should be calculated.

  • Gross: The total time is considered, and the corresponding minimum break is deducted from it.

  • Net: All minimum breaks are considered sequentially: The time up to the first intended minimum break is considered, and the minimum break applicable to that time is deducted. The resulting net time is considered, and, if applicable, another minimum break is deducted from it.

  • Employee-Friendly: Like the Net variant, but with the following difference: In some cases, it is sufficient to deduct less than the minimum break, so that the Working Time falls under the scope of the relevant minimum break rule and the break rule is thus already fulfilled.

These three variants calculate a number based on the sum of the working hours and the sum of the breaks taken. This number is independent of the times of the working and break periods.

  • Employee-Friendly, but also apply to contiguous segments of the day: Relevant when breaks are too early or too late in the day, resulting in Working Time blocks with a duration greater than 6 hours. The Break Regulation is then applied to these blocks again, and, if applicable, further breaks are cut into them.

Specify the minimum length of a break in the sense of the Break Regulation.

Work interruptions of less than 15 minutes do not count as statutory rest breaks according to §4ArbZG. They therefore count as Working Time. (Exception: companies with corresponding collective agreements or works agreements.) - However, ZEP does not prohibit you from entering minimum lengths shorter than 15 minutes here.

In which reports is the Break Regulation considered/displayed?

  • Every employee sees, under Reports > My Reports > Break Overview, a table for the selected report period showing the observed Rest Periods, start and end of Working Time, the required Minimum Break, and the observed break for each day. Additionally, for days with non-compliance with the Break Regulation, information about insufficient Rest Period, insufficient break, or excessive Working Time is displayed.

  • With Absences & Overtime module: Under Reports > My Reports > Month-end Report, all data regarding observed Rest Periods, start and end of Working Time, required Minimum Break, and observed break are displayed for the selected report period in addition to the existing information. Furthermore, for days with non-compliance with the Break Regulation, information about insufficient Rest Period, insufficient break, or excessive Working Time is displayed.

  • Administrators (and Department Managers, if applicable) can also run these reports for all employees (all employees in the department).

If you use the Absences & Overtime module, you can save the overtime and vacation balances at the end of the month in ZEP with a Month-end Closing. Once a month has been closed, the Break Regulation can no longer be changed for that period, and you must create a new Break Regulation with a suitable start date.

Calculation Procedure - Examples

Here you will find explanations, using examples, of the variants for the Calculation Procedure for missing Minimum Breaks and thus—if set—for the deduction of missing breaks:

Assume the Minimum Breaks are set as follows:

  • From 6:01 to 9:00 hours: Minimum Break 0:30

  • From 9:01 to 24:00 hours: Minimum Break 0:45

And assume an employee has the following bookings:

  • Day A: 7:03 to 16:45 (without break) = Working Time 9:42

  • Day B: 7:15 to 16:21 (without break) = Working Time 9:06

Variant Gross:

  • Day A: Working Time is more than 9 hours => Minimum Break according to table 00:45

  • Day B: Working Time is more than 9 hours => Minimum Break according to table 00:45

    The total time is considered, and the corresponding Minimum Break is deducted from it.

Variant Net:

  • Day A: Working Time is already more than 6:01 hours => Minimum Break according to table 00:30.

  • Remaining Working Time 9:12. This is more than 9:01 hours.

Minimum Break total 00:45 (so in this case, no difference to gross).

  • Day B: Working Time is already more than 6:01 hours => Minimum Break according to table 00:30.

  • Remaining Working Time 8:36. This fulfills all rules for Minimum Break. Total Minimum Break 0:30.

All Minimum Breaks are considered sequentially: The time up to the first intended Minimum Break is considered, and the applicable Minimum Break is deducted. The resulting net time is considered, and, if applicable, a further Minimum Break is deducted from it.

Variant Employee-Friendly:

  • Day A: Working Time is already more than 6:01 hours => Minimum Break according to table 00:30.

  • Remaining Working Time 9:12. This is more than 9:01 hours.

However: With a further break of only 12 minutes, the remaining Working Time is 9:00 hours and thus below the limit of 9:01, therefore the total Minimum Break is only 00:42 hours.

  • Day B: Like the Net variant, but with the following difference: In some cases, it is sufficient to deduct less than the Minimum Break, so that the Working Time falls under the scope of the relevant minimum break rule and the break rule is thus already fulfilled.

These three variants calculate a number based on the sum of the working hours and the sum of the breaks taken. This number is independent of the times of the working and break periods.

  • Employee-Friendly, but also apply to contiguous segments of the day
    Relevant when breaks are too early or too late in the day, leaving Working Time blocks with a duration greater than 6 hours. The Break Regulation is then applied to these blocks again, and, if applicable, further breaks are cut into them.

Minimum Breaks

Within the framework of a Break Regulation, you specify the applicable Minimum Breaks for working hours here:

According to § 4 ArbZG (German Working Hours Act), the minimum duration of breaks is staggered according to the duration of the employees' daily working hours. The minimum duration of breaks for working hours of more than 6 up to 9 hours is at least 30 minutes, and for working hours of more than 9 hours, it is 45 minutes. If you want to map these legal requirements in your ZEP in this way, please specify it as follows:

Create New Minimum Break:

  • from Hours 6:01 and to Hours 9:00:

    • Specify the corresponding Minimum Break in hours in the sense of the Break Regulation: 0:30 and press save.

  • from Hours 9:01 and to Hours 24:00:

    • Specify the corresponding Minimum Break in hours in the sense of the Break Regulation: 0:45 and press save.

Fixed Break

You can create a Fixed Break:

Click on Create New Fixed Break, specify from when to when this break should apply, and Save.

Fixed Breaks are always cut out for all employees to whom the Break Regulation is assigned, except during Travel Activity.

Even Administrators cannot subsequently record times within the time window of the Fixed Break. The specification of a Fixed Break is accordingly only recommended if employees cannot work during that time. For example, during shop closing hours over lunch.

Core Working Hours

Within the Break Regulation, you can define Core Working Hours in ZEP. Core Working Hours are a time span during which employees should record time. An employee can be assigned the Core Working Hours defined there (or multiple Core Working Hours) via the assignment of a Break Regulation.

Compliance with the Core Working Hours is not enforced. In the Project Times table, ZEP displays a blue notification if the Core Working Hours were not complied with on a particular day. In the Month-end Report, a column "insufficient Core Working Hours" is displayed (only with the Absences & Overtime module).

How to create Core Working Hours:

Click Create New Core Working Hours, specify from when to when these Core Working Hours should apply and Save. Specify the maximum permissible break in hours.

Example:

Core Working Hours from 9:00 to 16:00 maximum permissible break of 1 hour. This means the employee must have worked at least 5 hours between 9:00 and 16:00. Please note: the "break" can also be at the beginning or at the end of the Core Working Hours.

If you have employees who work part-time, you should assign them their own Break Regulation with a corresponding core time.

Mail Templates

ZEP offers you the possibility to send emails at various points. For these emails, there are standardized texts included in the emails.

Here you can customize the standardized text for the Project Times Mail Template. You have the option to send specific information regarding employees through general Placeholders. The Placeholders will be displayed to you when you click into the content text field.

Additionally, you can optionally add files (max. 5 x 20MB / max. 50MB total).

You can send all Mail Templates as a test email (Preview) to your own email address.

Click Test Send (to own email address) and make the desired language selection (currently German, English, French, Spanish, and Polish); you will then receive the email in the corresponding language sent to your address.

Travel

Subsistance Costs

Available from ZEP Compact with the Travel Expense Report module

Calculation Procedure for Subsistence Costs

You have the choice:

No Calculation

No subsistence costs are calculated.

Germany

Specify a flat rate for an absence of more than 8 or at least 24 hours, respectively. If you also received breakfast or lunch/dinner paid for on a day, the tax regulation provides for a deduction from the subsistence costs. This is specified as a percentage depending on the location. The indication of whether a meal was paid for is done under My ZEP > Project Times for the relevant day using the cutlery symbol.

Further information on legal provisions:

Details on the calculation of subsistence costs can be found in the documents of the Federal Ministry of Finance (Bundesfinanzministerium):

Austria

Calendar Day Rule

A calendar day is used as the basis for calculating the daily allowance.

24-Hour Rule

The calculation of the daily allowance is based on 24-hour intervals starting from "start of trip."

Under Travel Expense Daily Allowance, you specify the flat-rate daily allowance valid for the location. Furthermore, for each location, you have the choice between the Twelfths Rule and the Thirds Rule:

Twelfths rule:

Travel duration

Daily Allowance

up to 3 hours

no daily allowance

3 to 11 hours

1/12 daily allowance for every commenced hour of travel

11 to 24 hours

full daily allowance (corresponds to the regulation for the tax treatment of domestic business trips in Austria)

The meal deduction relates to the whole daily allowance.

Thirds rule:

Travel duration

Daily allowance

up to 5 hours

no daily allowance

5 to 8 hours

1/3 of the daily allowance

8 to 12 hours

2/3 of the daily allowance

over 12 hours

full daily allowance

The meal deduction relates to the whole daily allowance.

  • Regulation according to collective agreement for iron and metal industry:

Travel duration

Daily allowance

up to 3 hours

no daily allowance

3 to 6 hours

1/4 of the daily allowance

6 to 9 hours

1/2 of the daily allowance

9 to 12 hours

3/4 of the daily allowance

over 12 hours

full daily allowance

The meal deduction relates to the aliquot daily allowance, i.e., to the portion of the daily allowance calculated based on the time of absence.

The calculation procedure set here applies initially to all (new) employees. However, you can switch off the calculation of subsistence costs for each individual employee in their Data, or, for Austria, set the respective other calculation procedure (Calendar Day/24-Hour).

If you also received breakfast or lunch/dinner paid for on a day, you can make a deduction from the subsistence costs. This is specified as a percentage depending on the location. The indication of whether a meal was paid for is done under My ZEP > Project Times for the relevant day using the cutlery symbol.

More Info on Subsistence Costs in ZEP

Where do I see the calculated subsistence costs?

Subsistence costs are reported in the employee's Expense Report and are considered as internal project costs in the Margin reports.

You also have the option to charge subsistence costs further within a project. You can set this per project.

The determined amount is then considered in the project billing and in the Margin reports.

When are subsistence costs incurred?

Subsistence costs are incurred when an employee books project times at a work location that is not the "Primary Place of Work" location. ZEP determines the time the employee was traveling, including breaks.

The best way to do this is for the employee to start every trip with an "outward" (hin) booking and end it with a "return" (rück) booking. (If you have the instruction that the actual travel time is not working time, the outward and return journey can also be booked only at a point in time, i.e., with a duration of "0," so that only the start and end of the trip are clearly set).

Where do the numbers for calculating subsistence costs come from?

The country-specific parameters per location are specified in Administration > Travel > Locations.

For an employee's absence per calendar day, the subsistence costs are determined from the duration of the absence and the parameters of the work location.

Weekend

Under the following conditions, subsistence costs are calculated for unbooked days in between (e.g., Saturday and Sunday):

  • The last booking of a day (e.g., Friday) is external activity (location is not standard) and is not a return journey.

  • No more than three days without a time booking follow (e.g., Saturday, Sunday, and public holiday).

  • The first booking (e.g., on Monday) is at the same location as the last booking (on Friday) and is not an outward journey.

    The intermediate days are counted with 24 hours of absence.

If you have set the Austria 24-Hour Rule, you must record a further travel time with a duration of "0" for Saturday and Sunday, otherwise the weekends will not be included in the calculation.

Case

Example

Booking Process

Billed weekend without subsistence costs

An employee could travel back over the weekend but wishes to stay privately at the external work location. They should not receive any subsistence costs for this time.

For this, the employee books a return journey on Friday with time 0 and then an outward journey again on Monday with time 0.

Billed subsistence costs for weekend

An employee stays at their external work location over the weekend and receives tax-free subsistence costs, even if they did not work on the weekend.

If the Friday and Monday work is booked to a project that passes the subsistence costs on to the customer according to the project plan, then these weekend subsistence costs are also considered in the project billing.

Travel across multiple locations

  1. Travel across multiple domestic locations on one calendar day

  2. Travel domestic and foreign on one calendar day

ZEP recognizes domestic locations because the location designation contains the word Inland (Domestic).

  1. For the subsistence costs calculation in ZEP, the last visited domestic location is decisive.

  2. For the subsistence costs calculation, the last visited foreign location is decisive.

Two separate trips on one calendar day

The employee performs two separate trips on one day.

The sum of the absence times for the day is considered. Here, too, the last visited location, or the last visited foreign location if applicable, serves as the basis for calculating the subsistence costs.

Travel across midnight

An employee is traveling across midnight.

Ensure that the trip begins with exactly one outward journey and ends with exactly one return journey. The Travel Times in between must be onward journeys.

Record the trip in 2 parts

  1. part: up to 24:00 with specification of the location reached at that time.

  2. Part: following day from 0:00, here the destination location is specified.

Midnight Rule

The Midnight Rule means that absences from 2 calendar days may be added together to receive subsistence costs, if applicable. However, this may only happen if there was no overnight stay.

The Midnight Rule is applied when

  • the trip started after 4 PM and ended before 8 AM

and

  • there was no overnight stay (overnight stay according to your settings in "Recognize Overnight Stay Time")

Period Check for Tax-Free Reimbursement of Subsistence Costs

Set here whether the Period Check for the tax-free reimbursement of subsistence costs should refer to the same Projector the same Customer.

  • ZEP determines the date from which the employee has booked to the same Project at the same work location for more than two days per week.

  • ZEP determines the date since which the employee has booked to projects of the same Customer at the same work location for more than two days per week.

If this, minus absence days, is more than 3 months and there has been no interruption of 4 weeks, a corresponding note is issued in the employee's Expense Report.

Recognize Overnight Stay Time

This setting influences the calculation of subsistence costs in the event that an employee travels overnight.

If you specify No here, ZEP will not recognize Overnight Stay Time, meaning an overnight stay will never be considered for the calculation of subsistence costs, as, according to the definition, there is none. This affects arrival and departure days that fall short of the minimum absence time: ZEP will consequently never calculate subsistence costshere.

If you specify Yes here, ZEP applies your definition for overnight stays. Specify the time frame within which an unbooked time span must lie for ZEP to recognize an overnight stay.

Specify the Minimum Overnight Stay Time in hours. For the time frame, enter the Overnight Stay Time Start in the evening (must be greater than 12:00) and the Overnight Stay Time End in the morning (must be less than 12:00).

The Minimum Overnight Stay Time in hours must not be greater than Start until End. (You can also enter 0, in which case an overnight stay is always recognized, even if there was no break. This means for arrival and departure days that fall short of the minimum absence time: ZEP always calculates subsistence costs.)

This means an overnight stay is always assumed if a trip is present, i.e., the location of the time bookings is, for example, not the "Primary Place of Work"

and

between your specified Overnight Stay Time Start in the evening (must be greater than 12:00) and the Overnight Stay Time End in the morning (must be less than 12:00), the Minimum Overnight Stay Time in hours amounts to the specified number of hours.

Midnight Rule

The Midnight Rule means that absences from 2 calendar days may be added together to receive subsistence costs, if applicable. However, this may only happen if there was no overnight stay.

The Midnight Rule is applied when

  • the trip started after 4 PM and ended before 8 AM

and

  • there was no overnight stay (overnight stay according to your settings in "Recognize Overnight Stay Time")

Period Check for Tax-Free Reimbursement of Subsistence Costs

Set here whether the Period Check for the tax-free reimbursement of subsistence costs should refer to the same Projector the same Customer.

  • It determines the date from which the employee has booked to the same Project at the same work location for more than two days per week.

  • It determines the date since which the employee has booked to projects of the same Customer at the same work location for more than two days per week.

If this, minus absence days, is more than 3 months and there has been no interruption of 4 weeks, a corresponding note is issued in the employee's Expense Report.

Recognize Overnight Stay Time

This setting influences the calculation of subsistence costs in the event that an employee travels overnight.

If you specify No here, ZEP will not recognize Overnight Stay Time, meaning an overnight stay will never be considered for the calculation of subsistence costs, as, according to the definition, there is none. This affects arrival and departure days that fall short of the minimum absence time: ZEP will consequently never calculate subsistence costs here.

If you specify Yes here, ZEP applies your definition for overnight stays. Specify the time frame within which an unbooked time span must lie for ZEP to recognize an overnight stay.

Specify the Minimum Overnight Stay Time in hours. For the time frame, enter the Overnight Stay Time Start in the evening (must be greater than 12:00) and the Overnight Stay Time End in the morning (must be less than 12:00).

The Minimum Overnight Stay Time in hours must not be greater than Start until End. (You can also enter 0, in which case an overnight stay is always recognized, even if there was no break. This means for arrival and departure days that fall short of the minimum absence time: ZEP always calculates subsistence costs.)

This means an overnight stay is always assumed if a trip is present, i.e., the location of the time bookings is, for example, not the "Primary Place of Work"

and

between your specified Overnight Stay Time Start in the evening (must be greater than 12:00) and the Overnight Stay Time End in the morning (must be less than 12:00), the Minimum Overnight Stay Time in hours amounts to the specified number of hours.

If an employee books a day on different projects

When an employee incurs subsistence costs (VMA) as part of an external activity, you can specify in a project's Travel Settings whether subsistence costs should be billed.

Here in the settings, you specify how these subsistence costs should be charged further to the relevant project or projects. You can choose the following two options when an employee has booked one day to various projects:

  • distribute the subsistence costs of the day proportionally across all projects or

  • distribute the subsistence costs of the day only to projects of the same customer proportionally according to the number of hours; treat projects of different customers separately.

Distribute subsistence costs of the day proportionally across all projects (i.e., distribute the subsistence costs of the day proportionally across all relevant projects according to the number of hours)

The starting point is the calculation of the subsistence costs from the employee's perspective, i.e., all time bookings across all projects. This determines the flat rate applicable for that day, e.g., more than 8 hours or at least 24 hours (Administration > Travel > Locations).

In a next step, ZEP distributes this result across the involved projects of that day, i.e., across the projects that were booked as "location project-relevant."

This means:

From an internal perspective: The external subsistence costs to be charged are determined using the same key as the internal subsistence costs. In the simplest example: If all involved projects are set up to generally charge subsistence costs (for all times, not just for billable) with the "normal" location flat rates, then the sum of the project billings will be exactly the same amount as the employee receives in their Expense Report.

This implicitly also distributes breaks, transition days (weekends), and the meal deduction proportionally across the projects.

From the customers' perspective (i.e., the invoice recipients): The calculation of the subsistence costs for a project is always dependent on whether the employee also booked time to other projects "out of house" on that day (and it is not avoidable that times, start/destination location, and work location of an "other" project become visible on the invoice attachment for the subsistence costs table).

Please note: This is not always comprehensible to the recipient of the invoice, as the project times of the other projects are naturally not listed on the invoice.

Example:

If 4 hours are booked to the project, there can be a case where:

  • no subsistence costs are charged because no other projects were booked, or

  • half the flat rate is charged because 4 more hours were booked to another project, or

  • one-third of the flat rate is charged because 8 more hours were booked to another project.

or you specify the Treat subsistence costs of projects from different customers separately

i.e., distribute the subsistence costs of the day only to projects of the same customer proportionally according to the number of hours; treat projects of different customers separately.

If you have chosen this option, you can further specify how the subsistence costs should be billed to the project.

If a project has multiple customers:

  • With the setting "Distribute subsistence costs of the day proportionally across all projects," all customers of the project have equal rights. The same full subsistence costs amount is always shown on every customer's invoice.

  • With the setting "only distribute proportionally to projects of the same customer according to the number of hours; treat projects of different customers separately," only projects where the customer is PRIMARY are considered. This results in the subsistence costs being not considered on an invoice to a Secondary Customer, but only on the Primary Customer's invoice

For billing the subsistence costs of a project

if the employee has booked one day to various projects

If you have chosen the option "only distribute proportionally to projects of the same customer according to the number of hours; treat projects of different customers separately," you can select the following options for billing the subsistence costs of a project:

  • treat all times booked to projects of other customers as a break; they do not interrupt the absence time of the one project.

or

  • only treat times booked as "location not project-relevant" to projects of other customers as a break. Times booked as "location project-relevant" to projects of other customers and the breaks around them do not count as part of the absence time of the one project, but interrupt the absence time of the one project.

or

  • all times booked to projects of other customers and the breaks around them do not count as part of the absence time of the one project, but interrupt the absence time of the one project.

The subsistence costs paid out to the employee are not the sum of all project billings. Projects of different customers may receive the same subsistence costs billed (multiple times). Nevertheless, the invoice recipient will be able to correctly understand this, as there are no side effects from bookings to other projects.

Examples for the Further Billing of Subsistence Costs to Projects/Customers

Setting: "distribute proportionally across all projects"

  • Travel setting for both Project A and B: Subsistence costs: "bill for all working hours":

    A Staff Member records 4.5 hours each on one day on two different Project A and B.

    Employee Expense Report: The employee receives the "more than 8 hours flat rate."

    Travel Costs Project A: 50% of the "more than 8 hours flat rate"

    Travel Costs Project B: 50% of the "more than 8 hours flat rate"

  • Staff Member records 7 hours on one day on Project A and 3 hours on Project B.

    Employee Expense Report: The employee receives the "more than 8 hours flat rate."

    Travel Costs Project A: 70% of the "more than 8 hours flat rate"

    Travel Costs Project B: 30% of the "more than 8 hours flat rate"

  • Travel setting for Project A: Subsistence costs: "bill for all working hours" and

    Travel setting for Project B: Subsistence costs: "bill for billable working hours only":

    Employee books 4.5 hours on Project A and 1 hour billable and 3.5 hours non-billable on Project B.

    The employee receives the "more than 8 hours flat rate."

    Travel Costs Project A: 50 % of the "more than 8 hours flat rate"

    Travel Costs Project B: 50% of the "more than 8 hours flat rate,"

  • Employee books 8 hours billable on Project A and 8 hours non-billable on Project B:

    Employee Expense Report: The employee receives the "more than 8 hours flat rate."

    Travel Costs Project A: 50 % of the "more than 8 hours flat rate"

    Travel Costs Project B: 50% of the "more than 8 hours flat rate"

    but since only non-billable time was booked here, 50% of 0.00 = 0 is calculated!

Setting: "treat projects of different customers separately"

— and treat times booked to projects of other customers as a break, meaning no interruption of absence time.

i.e., all times booked to projects of other customers are treated as a break; they do not interrupt the absence time of the one project.

Example: Time is booked alternately for 1 hour each on Project A and Project B:

  • 08:00 - 09:00 Project A

  • 09:00 - 10:00 Project B

  • 10:00 - 11:00 Project A

  • 11:00 - 12:00 Project B

  • 12:00 - 13:00 Project A

  • 13:00 - 14:00 Project B

  • 14:00 - 15:00 Project A

  • 15:00 - 16:00 Project B

  • 16:00 - 17:00 Project A

  • 17:00 - 18:00 Project B

Subsistence costs Project A: 8:00 - 18:00 hours = "more than 8 hours flat rate"; Working Time 5 hours

Subsistence costs Project B: 8:00 - 18:00 hours = "more than 8 hours flat rate"; Working Time 5 hours

— and treat times booked to projects of other customers as "location not project-relevant" as a break, meaning no interruption of the absence time; times booked as "location project-relevant" to projects of other customers interrupt the absence time of a project.

only treat times booked as "location not project-relevant" to projects of other customers as a break. Times booked as "location project-relevant" to projects of other customers and the breaks around them do not count as part of the absence time of the one project, but interrupt the absence time of the one project.

Example 1:

Time is booked alternately for 1 hour each on Project A and Project B, every time booking was "location project-relevant":

08:00 - 09:00 Project A

09:00 - 10:00 Project B

10:00 - 11:00 Project A

11:00 - 12:00 Project B

12:00 - 13:00 Project A

13:00 - 14:00 Project B

14:00 - 15:00 Project A

15:00 - 16:00 Project B

16:00 - 17:00 Project A

17:00 - 18:00 Project B

Subsistence costs Project A: 8:00 - 9:00 hours + 10:00 - 11:00 hours + 12:00 - 13:00 hours + 14:00 - 15:00 hours + 16:00 - 17:00 hours

= 5 hours absence time = no subsistence costs

Subsistence costs Project B: same as Project A, just "time-shifted"

= 5 hours absence time = no subsistence costs

Example 2:

Time is booked alternately for 1 hour each on Project A and Project B, every time booking on Project A was "location project-relevant" (*), on Project B "location not project-relevant":

08:00 - 09:00 Project A*

09:00 - 10:00 Project B

10:00 - 11:00 Project A*

11:00 - 12:00 Project B

12:00 - 13:00 Project A*

13:00 - 14:00 Project B

14:00 - 15:00 Project A*

15:00 - 16:00 Project B

16:00 - 17:00 Project A*

17:00 - 18:00 Project B

Subsistence costs Project A: 8:00 - 18:00 hours = "more than 8 hours flat rate"; Working Time 5 hours

Subsistence costs Project B: no subsistence costs, since location not project-relevant

— and times booked to projects of other customers interrupt the absence of a project

i.e., all times booked to projects of other customers and the breaks around them do not count as part of the absence time of the one project, but interrupt the absence time of the one project.

If an employee books time on two different projects of different customers on one day, each project is considered individually; the times booked to the respective other project are always considered a break.

Example: Time is booked alternately for 1 hour each on Project A and Project B:

08:00 - 09:00 Project A

09:00 - 10:00 Project B

10:00 - 11:00 Project A

11:00 - 12:00 Project B

12:00 - 13:00 Project A

13:00 - 14:00 Project B

14:00 - 15:00 Project A

15:00 - 16:00 Project B

16:00 - 17:00 Project A

17:00 - 18:00 Project B

Subsistence costs Project A: 8:00 - 9:00 hours + 10:00 - 11:00 hours + 12:00 - 13:00 hours + 14:00 - 15:00 hours + 16:00 - 17:00 hours

= 5 hours absence time = no subsistence costs

Subsistence costs Project B: same as Project A, just "time-shifted"

= 5 hours absence time = no subsistence costs

Display all Start/Destination Locations

You can optionally set here whether all start and destination locations should be displayed in the employee's Expense Report.

Example:

8:00 AM - 9:00 AM: Outward Journey from Home to Customer

9:00 AM - 4:00 PM: working at the customer's location

4:00 PM - 5:00 PM: Return Journey from Customer to Office

If you activate this setting (Yes), then the start and destination location of every time booking with the Travel Activity are displayed:

Home, Customer, Customer, Office

If you do not activate this setting (No), then only the first booked start and the last booked destination location that is not identical to the start location are displayed:

Home, Office

This setting might lead to misunderstandings (as in this example).

Examples and Tips for Travel Time Recording and Calculation of Subsistence Costs

Subsistence costs are automatically calculated in ZEP if the work location is not the Primary Place of Work.

One-day Trip

The easiest way to record the data for your travel and project time is in the correct chronological order:

  • Outward Journey

  • Project Time

  • Return Journey

Select the appropriate Non-Primary Place of Work location as the work location so that the subsistence costs are calculated correctly. The calculation period begins with the outward journey, or the first project time at the Non-Primary Place of Work location, and ends with the return journey or at 12:00 AM of the same day if no return journey was recorded. If project time is recorded at the Primary Place of Work location on the next day, ZEP calculates the subsistence costs until the end of the last recorded activity at the Non-Standard work location.

Example:

  • 8:00 AM - 9:00 AM Travel Time (outward), Work Location: D (Domestic outside house)

  • 9:00 AM - 12:00 PM Project Time Work Location: D (Domestic outside house)

  • 1:00 PM - 5:00 PM Project Time Work Location: D (Domestic outside house)

  • 5:00 PM - 6:00 PM Travel Time (return), Work Location: D (Domestic outside house)

You were 9 hours away from home (including the break between 12 and 1 PM) and receive the statutory flat rate of €12 as subsistence costs for this. From 24.00 hours, €24.

Overnight Stay Definition
For the calculation of subsistence costs, it is crucial whether or not an Overnight Stay took place. Therefore, ZEP attempts to recognize whether an Overnight Stay exists based on the time bookings:

An Overnight Stay is assumed if

  • a trip is present, i.e., the location of the time bookings is, for example, not the "Primary Place of Work"

  • between 10:00 PM and 6:00 AM, a contiguous period of at least 2 hours was not booked (i.e., Break)

    or

  • You have stored your own definition under Administration > Travel > Subsistence Costs > Recognize Overnight Stay Time.

Travel Across Midnight

You always record based on the calendar day, meaning a trip across midnight is entered in two parts. In the first part "up to 12:00 AM," the location reached by that time must be specified (regardless of whether by plane, train, or car). In the second part (following day from 12:00 AM), the destination location is specified.

Ensure that the trip begins with exactly one Outward Journey and ends with exactly one Return Journey. The Travel Times in between must be onward journeys.

Midnight Rule

The Midnight Rule means that absences from 2 calendar days may be added together to receive subsistence costs, if applicable. However, this may only happen if there was no Overnight Stay.

The Midnight Rule is applied when

  • the trip started after 4 PM and ended before 8 AM

    and

  • there was no Overnight Stay, i.e., if there was less than 2 hours of contiguous break in the period between 10 PM and 6 AM.

Arrival/Departure Rule without Minimum Absence Time

If a trip begins with an outward journey and is not concluded on the same calendar day, it is considered an arrival day. If an overnight stay took place afterwards (according to the definition above), the daily flat rate for more than 8 hours is credited, even with less than 8 hours of absence.

If a trip continues on a new calendar day and is concluded with a return journey on that day, it is considered a departure day. If an overnight stay took place before that (according to the definition above), the daily flat rate for more than 8 hours is credited, even with less than 8 hours of absence.

In total, no more than the 24-hour flat rate is calculated on any one day, even if multiple arrival and departure days took place.

Multi-day Trip

Trips lasting several days should begin with an outward journey and end with a return journey, just like one-day trips. All Travel Times in between should be recorded as an onward journey.

If you have not recorded a return journey on the same day, ZEP assumes it is a multi-day trip. The subsistence costs are calculated as follows: from the outward journey until 12:00 AM of the same day and from 12:00 AM of the following day until the return journey.

Weekend

ZEP considers that an employee may receive tax-free subsistence costs if they remain at their external work location over the weekend, even if they did not work on the weekend days.

Under the following conditions, subsistence costs are calculated for unbooked days in between (e.g., Saturday and Sunday):

  • The last booking of a day (e.g., Friday) is external activity (location is not "Primary Place of Work") and is not a return journey.

  • No more than three days without a time booking follow (e.g., Saturday, Sunday, and public holiday).

  • The first booking (e.g., on Monday) is at the same location as the last booking (on Friday) and is not an outward journey.

  • The intermediate days are counted with 24 hours of absence.

To prevent subsistence costs from being counted for the weekend, book a return journey on Friday.

Example:

An employee could travel back over the weekend but wishes to stay privately at the external work location, and accordingly should not receive any subsistence costs for this time; in this case, they book a return journey with time 0 on Friday and then an outward journey with time 0 on Monday. No subsistence costs are calculated for the employee for this weekend.

If the Friday and Monday work is booked to a project that passes the subsistence costs on to the customer according to the project plan, then these weekend subsistence costs are naturally also considered in the project revenue (in the invoice, if the Invoicing module is used).

Three-Month Period

Since 2014, the Three-Month Period for the tax-free status of subsistence costs is measured purely chronologically for the interruption regulation. An interruption of professional activity at the same work location leads to a new beginning of the Three-Month Period if it lasts for at least four weeks. The reason for the interruption is irrelevant; only the duration of the interruption counts.

Travels Longer than 3 Months

You have the option to define special locations ("Other Travel") for which the calculation of subsistence costs does not consider overnight stays, meaning the basis for calculating subsistence costs is merely the time from the first time booking of the day until the last time booking of the day.

A possible application for this ZEP functionality is external activities that exceed the duration of 3 months.

The background to this lies in the tax regulations in Germany: Subsistence costs for business trips are generally tax-free only if the employee is not employed at the same location for longer than 3 months. For an external activity lasting longer than this, there are no mandatory regulations for the remuneration of subsistence costs.

With ZEP, you have the choice:

  • Option 1: The employee books their working time back to the standard location after three months have elapsed and receives no subsistence costs.

  • Option 2: You pay subsistence costs even after three months have elapsed, but without considering overnight stays and generally not tax-free. For this, you define a location in the ZEP master data that you flag as "Other Travel" and specify the desired flat rates. The employee books their working time (after three months have elapsed) to this special location and receives the corresponding subsistence costs.

The rule for the further charging of subsistence costs to the customer also applies: For locations flagged as Other Travel, overnight stays are not considered.

Employee Share of Travel Time

A Travel Activity ("re") can also be booked with identical from- and to-times, i.e., with duration 0. Employees whose commute to the customer is not billed as working or project time, but who still receive subsistence costs (VMA) and potentially travel cost reimbursement, book such 0-times as outward and return journey to mark the start and end of the period decisive for subsistence costs.

  • Enter the same time for 'from' and 'to'.

  • Select the Travel Activity "re".

  • Enter the travel data.

  • If travel costs (calculated from the Vehicle, Private, Kilometer, and Passenger fields) are also not reimbursed, enter "-" or "0" for Vehicle, Kilometers, and Passenger.

We recommend starting every trip with an "outward journey" and ending it with a "return journey," with all project times within this period being booked at a Non-Standard Work Location.

Even if you omit the outward and return journey and simply book your working time at the Non-Standard Work Location, ZEP will calculate the subsistence costs for this time. The trip then ends with the next project time booking at the Standard Work Location. Note, however, that bookings at the Non-Standard Work Location on two consecutive days are interpreted as a multi-day trip, and subsistence costs are considered until 12:00 AM / from 12:00 AM.

Cost Accounting & Travel Note

Subsistence Costs Table

If you specify "Display Project" here, the respective project for which the subsistence costs (VMA) were incurred will be listed in an extra column in the Expense Report for the individual employee in the table with the subsistence costs (VMA table).

Mileage Allowance Table

If you specify "Display Project" or "Display Project and Task" here, the respective project or project and task for which the kilometers were specified will be listed in an extra column in the Expense Report for the individual employee in the mileage allowance table.

Receipts Table

If you specify "Display Project" or "Display Project and Task" here, the respective project or project and task of the recorded receipts will be listed in an extra column in the Expense Report for the individual employee in the receiptstable.

File Format

Set the file format in which you want to create Expense Reports with ZEP.

Without the ZEP module "Document Generator," the file format for the Expense Report is "html."

Checked Expense Report in Landscape Format

Specify whether the checked Expense Report should be created in landscape format. Please note: an Expense Report saved as checked is saved in the specified format; if you change the format subsequently in the settings, you must first delete the Expense Report already saved as checked and then save it again in the desired format.

Vehicles

When recording travel times, the employee specifies which vehicle they used. The tax-relevant vehicles are already included in ZEP.

You can store Vehicles in multiple languages.

The entry is made in the Designation field: Click on German/English/French/Spanish, enter the designation for the short form. Depending on the language set for the employee or the project, the designation will be displayed in the language selection.

For each Vehicle, you define here the mileage flat rate (tax-free, or optionally taxable) and possibly the passenger flat rate that is reimbursed in the Travel Expense Report for the employee for trips with the private vehicle. This flat rate can also be invoiced in the project billing.

For Germany and Austria

The flat rates already entered in ZEP are the amounts specified by the tax authorities as tax-free to be reimbursed. You can also store higher flat rates for your employees; these must then be taxed and reported separately on the Expense Report. Enter the amount here that you wish to pay in addition to the tax-free amount. ZEP reports these amounts separately on the employee's Expense Report.

You can also create several identical Vehicle types in ZEP; for example, if multiple vehicles are available in the fleet, you can create each individual one in ZEP with the respective license plate. The employees then select the used vehicle when recording their travel.

Vehicle Currency

Each Vehicle can have its own currency.

Application Example:

There are cases where vehicle flat rates should be billed in a currency other than the Base Currency (e.g., for an employee in another country, or for a project in another country, where you want to pass on exactly the vehicle flat rates valid in that country to the employees). In this case, you can create a new Vehicle where this different currency applies to the flat rates. The rate is retrieved from the website Fixer.io.

When you prepare the employee's Expense Report, the flat rates are converted if necessary. The date of the booked trip applies to the exchange rate used for this conversion.

Work Locations

Create Locations

When booking project times, an employee specifies the Location where the work took place. If the work was not at the usual Standard Work Location, this time may qualify for subsistence costs reimbursement. Here you define which Locations are available for selection. In general, the work Locations are intended to map the different subsistence costs flat rates (VMA flat rates); therefore, only Germany or other countries should be selectable.

In a few countries, there are also, as an exception, cities with higher flat rates. Please inform yourself in advance and create these if required.

You can store Locations in multiple languages.

The entry is made in the Designation field: Click on German/English/French/Spanish, enter the designation for the short form. Depending on the language set for the employee or the project, the designation will be displayed in the language selection.

Home Work Location

Create a Home Work Location if you later want to track when employees worked from home.

You can create one or more Home Work Locations. A Home Work Location is a Location for which (just like for the Primary Place of Work) no VMA and no flat travel rates are incurred, and which consequently appears neither in the employee's Expense Report nor in the project billing.

Therefore, all flat rates are automatically set to 0 as soon as you activate the Home Work Location option.

Conversely, a Location for which you manually set all flat rates to 0 is not necessarily a Home Work Location, but merely a Location for which the employee receives no VMA (flat rate 0), but for which flat travel rates or special daily flat rates can still be charged to the customer project if you set this accordingly in Project > [Project Name] > Billing Settings > Travel Settings.

Taxable

You can also store higher flat rates for your employees; these must then be taxed and reported separately on the Expense Report. Enter the amount here that you wish to pay in addition to the tax-free amount. ZEP reports these amounts separately on the employee's Expense Report.

Domestic or Foreign

Please specify whether the Location is a domestic or a foreign Location.

Background: ZEP requires this information for the correct calculation of VMA.

Generally: For a trip across multiple Locations on one day, the last Location booked on that calendar day is used for calculating the flat rates.

Exception: If a foreign Location is also booked on a calendar day, the flat rates of that Location are calculated, even if it is not the last booked Location of the calendar day.

Location Currency

Each Location can have its own currency. When calculating subsistence costs in an employee's Expense Report and in the project billing, if applicable, the currency is considered. This means:

  • If the reporting currency is identical to the Location currency, the flat rates are adopted directly into the calculation (without rounding errors due to back-and-forth conversion).

  • If the reporting currency is not identical to the Location currency, the Location flat rate is converted. The date of the booked trip applies to the exchange rate used for this conversion.

Business Trip or Other Travel

Example:

The employee always works at a customer location from Monday to Friday. They book an outward journey on Monday, a return journey on Friday, and all working times in between always to the appropriate work Location.

If this work Location is defined as Business Trip:

The basis for calculation is the absence time including overnight stay. This means in the example for Tuesday to Thursday that the absence time begins at 12:00 AM and lasts until 12:00 AM, so the flat rate for 24 hours applies.

If this work Location is defined as Other Travel:

The basis for calculation is the start and end of working time per day; overnight stays are not considered. For example, if the first working time on Tuesday begins at 8:00 AM and the last working time ends at 5:00 PM, these 9 hours apply to the flat rate, consequently, the flat rate for more than 8 hours is credited.

Implementation of Legal Changes

The tax authority determines the amounts for tax-free reimbursement of subsistence costs. In the event of a change in the law, it is sufficient for you yourself to update the figures.

The Primary Place of Work (before 2014: Standard Work Location) is not managed in the list of work locations, as it is not relevant for the Travel Expense Report. It automatically appears in the "Work Location" selection list during project time recording (exception: if special "Project Locations" have been chosen for a project, the selection list may not contain the Primary Place of Work location).

Do not use these work locations to map the different sites of your company. For this, we recommend the Locations & Departments module.

Use of ZEP for Calculation of VMA or Travel Expense Daily Allowance

If you do not use ZEP for calculating subsistence costs or Travel Expense Daily Allowance, then every location only consists of a short form and a designation and has no effect on the Travel Expense Report.

If you use ZEP for calculating subsistence costs or Travel Expense Daily Allowance, check under the menu item Administration > Travel > Subsistence Costs > Calculation Procedure whether you have specified the appropriate country setting. Depending on this, the Locations have further parameters that are used for calculating subsistence costsor Travel Expense Daily Allowance.

Country Regulations Germany & Austria

Deutschland (Germany)

Tax-Free

Specify the tax-free flat rate for an absence of more than 8 or at least 24 hours, respectively. If you also received a meal (breakfast or lunch/dinner) paid for on a day, the tax regulation provides for a deduction from the subsistence costs. This is specified as a percentage depending on the location.

The percentage deduction always refers to the flat rate for 24 hours, even if the employee was absent for less than 24 hours. The indication of whether a meal was paid for is done on the Project Times page for the relevant day using the cutlery symbol.

Taxable

You can also store higher flat rates for your employees; these must then be taxed and reported separately on the Expense Report. Enter the amount here that you wish to pay in addition to the tax-free amount. ZEP reports these amounts separately on the employee's Expense Report. Optionally, you can also specify a percentage deduction for meals.

Österreich (Austria)

ZEP supports the Calendar Day Rule and the 24-Hour Rule. Under Travel Expense Daily Allowance, you specify the flat-rate daily allowance valid for the location. Furthermore, for each location, you have the choice between the Twelfths Rule and the Thirds Rule as well as the collective agreement rule.

Twelfths rule:

Travel duration

Daily Allowance

up to 3 hours

no daily allowance

3 to 11 hours

1/12 daily allowance for every commenced hour of travel

11 to 24 hours

full daily allowance (corresponds to the regulation for the tax treatment of domestic business trips in Austria)

The meal deduction relates to the whole daily allowance.

Thirds rule:

Travel duration

Daily allowance

up to 5 hours

no daily allowance

5 to 8 hours

1/3 of the daily allowance

8 to 12 hours

2/3 of the daily allowance

over 12 hours

full daily allowance

The meal deduction relates to the whole daily allowance.

  • Regulation according to collective agreement for iron and metal industry:

Travel duration

Daily allowance

up to 3 hours

no daily allowance

3 to 6 hours

1/4 of the daily allowance

6 to 9 hours

1/2 of the daily allowance

9 to 12 hours

3/4 of the daily allowance

over 12 hours

full daily allowance

This corresponds to the regulation for the tax treatment of foreign business trips in Austria.

The meal deduction relates to the entire daily allowance.

If you also received breakfast or lunch or dinner paid for on a day, you can make a deduction from the subsistence costs. This is specified as a percentage depending on the location. The indication of whether or not a meal was paid for is done under Project Times for the relevant day using the symbol.

Specify the percentage deduction for the received meal for each location. If you enter a value in the field Percentage deduction for lunch AND dinner (required for foreign locations), you must accordingly enter a deduction of 0 in the field Percentage deduction for lunch or dinner.

Departments

Here you make settings regarding the Locations & Departments module.

Resource Planning

Here you find the configuration options and mail templates for the Resource Planning module.

Overtime & Absences

You receive this tile if you use the Absences & Overtime module.

Ticketing System

Here you can make settings and store data that relate to the Ticketing System module.

Quotations

If you use the Quotation module, you will find the Quotations tile in Administration. There you can make settings and store data that are necessary for the module.

Billing

This tile is displayed to you if you use the Invoicing module for ZEP.

Export for Accounting

If you use the Export for Accounting module, you receive the tile of the same name in Administration with the corresponding configuration options.

Documents

If you use the Document Management module, you receive this additional tile in ZEP.

Interfaces

You have the option to link ZEP with various Interfaces.

Below you will find the links to the help texts for the individual Interfaces:

  • Salesforce

  • HubSpot

  • Personio

  • HR WORKS

  • SOAP Interface

  • REST Interface

System

Information on the menu items contained in this tile can be found in the following places:

  • Month-end Closing

  • Device Management & RFID Chips

  • Tasks

Other

Text Modules for E-Mails

Here, Text Modules suitable for you can be created, which you have not already created elsewhere because they may not be clearly assigned to a single thematic area.

Change History

  • Record changes to project data: Activate the checkbox "Record changes to project data" if you want to log who made what changes to projects and when.

  • Record changes to employee data: Activate the checkbox "Record changes to employee data" if you want to log who made what changes to employee data and when.

  • Record changes to customer data: Activate the checkbox "Record changes to customer data" if you want to log who made what changes to customer data and when.

Scheduler

Enter one or more email addresses here (separate multiple addresses with a "comma" as a separator), to which an email should be sent if errors have occurred during the execution of Tasks. Such an email will then be sent to the ZEP Administrators and to the email addresses specified here. The mail mechanism is intended for when a Task detects logic or configuration errors, e.g., an invalid mailbox was specified.

Event Mail Templates

At this point, you can create, edit, or delete Appointment Mail Templates.

Did this answer your question?