Give every sale one place in the calendar

Choose a date field before choosing a week

Invoice date, appointment date and payment date describe different events. A service performed on Sunday and invoiced on Monday can belong to different periods under different definitions. Record the selected field on the close checklist and use a source export that actually supplies it.

Trimsum’s import field is invoice date, and its period calculation includes rows whose mapped date is on or after the start and on or before the end. It works with calendar dates. It does not infer a report timezone or convert an appointment timestamp into the agreed commission date for you.

Check a clean weekly boundary

The fictional runs below use invoice dates and inclusive Monday–Sunday periods. A $110.00 service supplies $10.00 tax and a 40% rate, so each included example line contributes $40.00. The boundary determines which run contains it, not the amount of its commission.

Treat month ends as dates, not fixed-length blocks

Monthly periods have different lengths. Use the actual last calendar date rather than adding thirty days. A fortnightly process should similarly use the stated fourteen-day range and record its anchor date, instead of alternating vaguely labelled “first half” and “second half” files.

Store date-only values in an unambiguous form such as 2026-09-21. If the source uses 09/10/2026, confirm whether that means 9 October or 10 September. A parser accepting both possibilities cannot determine the intended date from that value alone.

Find both overlaps and missing days

Make a small register of completed periods with start, end, run label and source export. Check adjacent entries: an identical end and next start means a shared day; a next start more than one day later means a gap. Neither is automatically wrong if explicitly intended, but both need an explanation.

Do not rely only on duplicate warnings. Trimsum compares a defined combination of source fields; a modified name, item or amount can change that comparison. Period coverage is a separate check that catches missing or repeated days even when the individual rows are not exact matches.

1. Sort completed periods by start date.
2. Compare each next start with the preceding end plus one day.
3. Inspect the first and last source rows in each export.
4. Reconcile the boundary-day totals and document any exception.

Handle late records without rewriting their dates

A late export may reveal an invoice dated inside a period you already closed. Keep the original date. Identify the affected run and use a documented follow-up process rather than changing the invoice date to make it fit the current week.

A refund created this week for an older service is a different situation: the refund has its own event date and a link to the original sale. Preserve both dates and confirm the supplied adjustment rule. The original service should not be moved into the new period simply because it helps explain the refund.

Verify the next starting point when you close

After finalising, confirm which draft rows remain outside the closed period. In Trimsum, closing a period removes its rows from the editable draft and retains the completed snapshot; rows outside that range remain for later review. Their presence is a reason to check dates, not proof of a failed close.

Record the next period’s bounds before the next import. Use the date-range checker on a sample or prepared export to inspect inside and outside rows. A repeatable boundary check keeps calendar mistakes from becoming unexplained commission differences.