belsimple Just right.
EN NL FR

Reports

The reports belsimple generates are designed to support your tax filing or grant progress report. Reports aggregate your team’s time entries by classification, by user, and as raw data.

Generating a time report

  1. Go to the Reports page.
  2. Optionally select a date range using the start and end date pickers. Leave either or both empty to include all logged time.
  3. Choose a format: Excel (.xlsx), Open Document (.ods), or CSV (.zip).
  4. Select which sections to include: Classifications, User and classes, Time entries. Tasks and About are always included.
  5. Click Generate time report.
  6. A confirmation dialog shows a summary of what will be generated. Click Generate time report to proceed.

Generating a project report

You can open the wizard from two places: Generate project report next to any active project in the Project report section of this page, or the Report button on a project row on the Projects page.

The wizard has four steps:

  1. Period. Choose the start and end dates the report should cover. It defaults to the project’s own date range — narrow it for the annual or interim reports that multi-year grants ask for.
  2. Team. The list shows every user who logged time entries during the period that are tagged with one or more of the project’s linked classifications. Tick the users whose data should be in the report. The selection drives both the cover sheet and the time data — entries from de-selected users are not included in any tab.
  3. Documents. Pick which employee and project documents to bundle into the ZIP.
  4. Generate. Confirm and download.

The package contains:

  • summary.txt — the project’s name, reference and dates, with the team roster.
  • time_report.xlsx — per-employee hours broken down by classification. Its About tab carries one row per linked classification, one row per included user, and one row per excluded user, so anyone reading the report can see exactly which inputs went in and reproduce it later.
  • audit_trail.csv — a log of who created, edited, reclassified, or deleted the time entries behind the report, and when. It covers only the entries that make up this report (the included users’ time under the project’s linked classifications, within the period), so an auditor can trace each figure back to the actions that produced it. For the tenant-wide history across all projects, use the Audit log page instead.
  • documents/employees/<name>/ — the documents you selected for each team member.
  • documents/project/ — the project documents you selected.
  • manifest.txt — a listing of everything in the package.

Export formats

Excel (.xlsx)

The default format. Contains multiple tabs in a single spreadsheet file. Subject to a row limit of 1,048,575 rows — use a narrower date range or switch to CSV if you hit this limit.

Open Document (.ods)

The open standard spreadsheet format. Same structure and row limit as Excel. Opens natively in LibreOffice, Google Sheets, and other applications that support ODF. Preferred by EU institutions and Belgian government services.

CSV (.zip)

A ZIP archive containing one standard CSV file per selected section (classifications.csv, user_and_classes.csv, tasks.csv, time_entries.csv, about.csv). The format itself has no row limit, so an export too large for Excel or ODS comes out complete here — but Excel and LibreOffice Calc both cap a sheet at 1,048,576 rows and will load only the first of them, warning that the file was not loaded completely. Above that size the file is still whole; read it with a script or load it into a database rather than a spreadsheet.

What’s in the report

Classifications

Aggregated hours per classification class across all users, grouped by classification. An “Unclassified” row always appears, even if zero — so you can confirm nothing fell through the cracks.

User and classes

Hours per user, broken down by classification and class. Uses equal-split logic when an entry has multiple classes. The “Unclassified” row is always present per user.

Tasks

Time totals per task in the hierarchy, rendered in depth-first tree order with indentation to show nesting. Always included in the report.

Time entries

One row per time entry with full detail:

  • User name
  • Task (full path from root to leaf)
  • Date
  • Duration
  • Description
  • Snapshotted classifications
  • Created and last modified timestamps

This is your audit-ready data — the detailed backup for your tax filing or grant report.

About

Generation metadata for reproducibility: when the report was created, what date range it covers, who generated it, and counts of entries and users included. For project reports, the About tab also lists each linked classification, each included user, each excluded user, and each emitted data tab — one row per item — so a reviewer can see (and reproduce) exactly what went into the report. Always included in the report.

For a worked example of how logged time becomes the figures on the Classifications tab, see A worked example.

Tips

  • Generate reports after reviewing entries (see Reviewing team entries).
  • The equal-split logic applies within a classification: if an entry has two classes from the same classification, each class gets half the duration. Classes from different classifications each get the full duration, since they represent independent dimensions (e.g., an entry can be 100% “Industrial research” under Frascati and 100% “Work package 1” under a grant classification).
  • Keep reports filed by period — they serve as your historical evidence for tax filings.
  • Use ODS format if your organisation prefers open document standards or submits reports to Belgian government agencies.
  • Use CSV format when you need to process data in scripts or when the date range is too large for a spreadsheet.