In this guide, we explain:

An additional table is a custom table created by your company for collecting information that Wemply does not include as standard fields.

For example, an additional table can be used to collect:

Depending on its configuration, each additional table entry is linked to either an employee or an object.

An entry can also have:

The entry's date or period determines the report periods in which the entry is included.

For employee-based additional tables where an employee is required, you can also configure entries to require approval before they are considered valid. For example, this allows bonuses to be entered for review first and included in reports only after they have been approved.

You can add as many additional fields to an additional table as needed. The fields determine what information is entered for each record.

For example, an additional table called “Bonuses” could contain the following fields:

An additional field can, for example, have one of the following types:

Only a decimal number field can be configured as an automatically calculated field. An integer field cannot be used as the target field of an automatic calculation, but it can be used as an input in the calculation.

The value of a decimal number field can be calculated automatically based on other fields in the same entry. You can:

An automatically calculated field cannot be edited manually by the user — Wemply calculates its value automatically every time the entry is saved.

An automatically calculated field is useful, for example, for:

Once data has been entered into an additional table, it can be used in a report in two different ways.

Simple rule: if you want to see a detailed list, use the additional table as a row. If you want to see aggregated totals, use a numeric field from the additional table as report data.

When you select an additional table as the basis for a report row, each additional table entry is displayed as a separate row in the report.

You can add fields from the additional table as columns, for example: date, amount, description, and type.

This is useful when you want to see all individual entries together with their details.

Example: You want to check which bonuses have been entered for employees. The report displays each bonus entry on a separate row together with the employee, date, type, and amount.

If an additional table contains a numeric field, such as “Amount”, you can select it as a report data type.

In this case, each entry is not displayed separately. Instead, Wemply adds together the values of all additional table entries that match the report criteria.

Example: additional table “Bonuses”

If the “Bonus Amount” field is used as report data and the rows are grouped by employee, the values are added together accordingly.

When creating a report, you can determine how the data is organized.

Rows determine what gets a separate row in the report — for example, employee, object, date, or an additional table entry.

Columns determine how the data is divided into different columns within the rows. For example, you can select month as the columns, which displays each employee's totals separately by month.

Grouping Fields allow you to divide the report into larger separate sections based on the selected value. For example, you can create a report where a separate table is displayed for each object.

Example:

If rows = employee, columns = month, and data = the additional table field “Amount”,

the result shows bonus totals by employee and month.

The numeric value from the additional table is added together according to the selected rows, columns, grouping, and filters.

In addition to the report configuration, whether an additional table entry is included in a report depends on the entry's dates, period, filters, and approval status.

If an additional table entry has a date or period, the report includes entries whose date or period overlaps with the selected report period.

If an entry has a start and end date, it is sufficient for the entry's period to overlap with the report period even partially.

Example: If an additional table entry covers the period 15.01–15.02 and the report is created for February, the entry is included because the entry period overlaps with the report period.

If an additional table entry has neither a date nor a period, its inclusion is not restricted to a specific date range.

As a result, the same undated entry may be included in reports created for different periods.

If an additional table is employee- or object-based, report filters affect which entries are included.

For example, if the report is filtered to include only one employee, only additional table entries associated with that employee are included.

If approval is enabled for an additional table, only approved entries are included in reports by default.

If necessary, the report settings allow you to include entries that are awaiting approval and have not yet been reviewed.

Suppose a company wants to see how much in bonuses has been assigned to each employee in different months.

The additional table is employee-based because each bonus belongs to a specific employee.

For example: Bonus Type, Quantity, Unit Price, Amount.

The “Amount” field can be configured to calculate automatically:

Quantity × Unit Price = Amount

If approval is enabled for the additional table, approve the verified entries before using them in the final report.

In the report, select:

Rows — Employee
​Columns — Month
​Data — additional table field “Amount”

You can also create different reports based on the same additional table. For example, you can use the additional table as the basis for report rows to display each individual bonus entry together with all its details.

The basic principle for using additional tables in reports is as follows:

This allows you to create different reports from a single additional table — from detailed lists of individual entries to totals calculated by employee, object, or month.