Help · Running this period
Running this period
Written for TableDI 2.0.0 on macOS · updated 2026-09-15
A period is one pass of a job over new files: September's statement and ledger in, September's result out. Click Process this period on Jobs or on the job's page. The preflight reads the new files; click Run this period. The result lands on the job's Overview, rows that need a person wait on Exceptions under To confirm, and Generate this period's delivery on the Delivery tab hands the file over.
1 · Preflight
It shows each file, what changed since last period and what will be held back. Run this period stays disabled while anything is listed in red. What each part means is in Reading the preflight.
2 · Overview
The run uses the job's rules, no AI. Every number opens its rows; the This period · … panel offers Handle exceptions or Generate delivery.
3 · Exceptions
Each row to confirm gets one of five ways out; you don't have to settle all of them before delivering.
4 · Delivery
Pick the formats and where the file goes, then Generate this period's delivery. If rows are still to confirm, TableDI 2 asks once: Deliver anyway or Go back and handle them. See Handing the result over.
Running a period again
The latest period can run again: pick it in the preflight and the button reads Run … again. Running it with corrected files replaces that period's result; the other periods stay as they are, and waived, carried and to-do rows follow by type · key · difference. From Exceptions, Change the source file leads to the same button once the file is fixed.
Only a job whose periods go in as This period only can take new files for a period it has already run; for the others, run the corrected file as the next period. A period label earlier than the latest one is refused.
When not to run
- Something is listed in red under Has to be fixed before this can run.
- The row count is far off last period's under Against last period — usually the wrong file or month.
- A column you rely on is missing: it comes out empty.
Still stuck? Email us — one inbox, read by the people who build TableDI.