The Log

One pay period's entries, grouped by day. Not everything you have ever recorded: 120 days in a single scroll is fine for last week and useless for last March, and stepping by calendar month would put a boundary where payroll does not have one.

Moving between periods

The strip along the top steps through pay periods. The line under it names the period and totals it.

The Log, Summary and Reports share one idea of which period you are looking at. Step back to June here and Summary and Reports show June too. Without that, each screen would quietly describe whichever period you last chose somewhere else: a filter you can neither see nor reach.

Reading a day

Tap a day to fold it open or shut; Collapse all does the lot. Each entry row carries its times, its hours, its job and activity, and small markers for the things that change what it is worth: the country, the onsite tick, an overnight stay, a journey attached to it.

The hours are the ones the timesheet counts: each entry rounded up to the quarter hour. The times stay as they were typed or tapped.

A journey through midnight is a row on each day, each with its own hours: continues Sun on the first, from Sat on the second. That is how the timesheet files it, and the day decides what the hours are worth.

Tap an entry and you get Edit entry and Delete entry. Editing opens the same form as Add entry manually, filled in.

Two things cannot be edited from here:

• A running timer. Clock out first.
• An entry that is no longer loaded. Pull down to refresh and try again.

The ERP tick

If you have switched on the Company ERP reminder in Settings › Features, each row carries a box, On company ERP, to tick once you have also entered that day on your employer's own ERP. Self-employed, it is the Invoice reminder, and the box reads Invoiced. Either way it is a reminder and nothing else: it changes no hours and no pay. An entry that has not reached the server yet cannot be ticked, and says so.

It is off for anybody new. At the end of the period it also lists the days not yet ticked; see Reports.

Correcting several at once

Select turns on selection mode. Tick the entries, and the bar at the bottom reports how many are selected before it offers to do anything with them.

Delete removes them, and leaves Put them back on screen for twelve seconds: long enough to read what happened, short enough that it is gone before you have forgotten what it referred to.

Move opens a small form. Every field is optional and blank means leave it alone:

Export

Export opens on the period you are looking at, with two date boxes for the times you want something else: a single week, or a fortnight lying across a period boundary. It counts the rows before it offers to write them.

The file has one row per entry:

Date, Start, Finish, Break, Hours, Job, Timezone, Activity, Tags

Three things about it are worth knowing before you open it in a spreadsheet:

• Break is a number of hours, not minutes. Half an hour is 0.5 - or write it 0:30 or 30 min, which the import reads the same way.
• Finish has the break added back, so the row adds up on paper: Start + Hours + Break = Finish. The stored finish time is the earlier one, with the break trimmed off.
• Timezone is where the day was worked, not where the phone is when you export. A trip that crossed zones is written the way its Log row says it: the day it left, the start where it set off, the finish where it arrived, and both zones, as America/Mexico_City>Europe/London. Imported back, it is the same entry.

On a phone the file goes to the share sheet, so it lands straight in the mail you were going to attach it to. On a desktop it downloads.

Import

The same sheet, below Export. It takes a Muster export or a TimeSheet Pro export, as .csv or as .xlsx saved from Excel or Google Sheets.

Nothing is written until you have seen what it would create. The report appears first; Create these entries commits it. Re-importing the same file is safe: rows that already exist are skipped, not duplicated.

Where these hours were worked sets the time zone for the file. An entry cannot be stored without one, and a Muster export does not carry one unless it has a Location column, so it is asked rather than guessed. A file that does carry zones overrides this row by row, and the report says which was used before anything is written.

The blank template

Download a blank template gives you the headings and nothing else. There is no example row, because an example left in by mistake imports as a day nobody worked, onto your pay record.

Date, Start, Finish, Break, Hours, Job, Timezone,
Activity, Country, Onsite, Overnight, Bank holiday, Shift pay, On company ERP, Tags

The six columns after Activity are the switches from the entry form, asked as questions: write Yes where one applies and leave the rest blank. (A Google Sheets tick box exports TRUE, which reads as Yes. An older template that says On portal still imports.) They are there because a free-text Tags cell is where an answer goes wrong silently: "Onsite" typed into Tags is not the onsite tick, and quietly does not count.

Fill in one row per shift: dates like 2026-08-03, times like 07:00, Break in hours.

When an import stops

It stops on the first thing it cannot read, names the row and says what to fix rather than importing a best guess. The common ones:

• Dates that could be read two ways. 03/08/2026 is two different days depending on where you are. Format the Date column as yyyy-mm-dd before saving.
• A bare number in the Break column is hours. 30 there is thirty hours, and the row will not add up; 30 min or 0:30 is half an hour.
• A row with no start or no finish. Every row needs both.

Next: Summary · Reports