Help · Running this period

Running this period

Written for TableDI 2.0.0 on macOS · updated 2026-09-11

A period is one pass of a job over new files: September's statement and ledger in, September's result out. On Jobs, click the job's Do this period, or Process this period on the job's own page. The preflight reads the new files and shows what matches, what changed since last period and what will be held back; click Run this period. The result appears on the job's Overview, the rows that need a person wait on Exceptions under To confirm, and when you're done, Generate this period's delivery on the Delivery tab hands the file over. In a month with nothing unusual, that's a handful of clicks.

Each period has a label — 2026-09 for a monthly job, 2026-W36 for a weekly one, 2026-09-06 for one you run when you say so — and each label runs once, so the preflight is the place to catch a wrong file.

Where to start

Jobs: the card's button. It reads Do this period when files are due, and Run one now for a job that isn't due yet.
The job's page: Process this period, top right.
This period in the sidebar: every job with a due date, soonest first, under Overdue, Due this week and Due this month, each with its one button.

All three open the same screen: the preflight.

1 · Preflight

The files are on the left, the decisions on the right.

Files for this period — one card per source. If the job has a folder and a file-name pattern, TableDI 2 fills in the file it expects for this period. Otherwise drop the file onto the card, or click it to choose one. Use a different file swaps it.
This period — the label. The small print says where it came from: Following 2026-08, Read from the file names or From the schedule. Change it if it's wrong.
How this period goes in — Add to history, This period only or Update on …. The job's usual choice is marked · the job’s default.
Run this period — stays disabled until every source has a file and nothing is listed in red.

What each part means is in Reading the preflight.

2 · Run, then read the Overview

Run this period runs the job's rules on the files, with no AI involved, and opens the job's Overview:

Flow · how … came out — one card per step, with what went in, what was kept and what was held back. Every number opens the rows behind it.
Result — the first rows of this period's result. Where from names the source rows each result row came from, and Open the full result shows all of it.
This period panel — In, Kept (matched), Held back, Difference, vs last period and Exceptions, with a button for what to do next.

Under the job's name, a strip follows the period through Prepare files, Review results and Generate delivery.

A job's Overview after a run: the steps with their counts, the first rows of the result, and the This period panel.

3 · Exceptions

If rows are waiting for you, the panel says … to confirm and offers Handle exceptions. That opens the Exceptions tab with the rows still to confirm. Each one gets a decision: add a rule, waive it with a reason, carry it to next period, mark it to do, or note that the source file was wrong. The options are in The five ways out of an exception.

You don't have to settle all of them before delivering.

4 · Delivery

On the Delivery tab, pick what to deliver and who gets it, then click Generate this period's delivery. If exceptions are still to confirm, TableDI 2 asks once: Deliver anyway or Go back and handle them. After that the period shows as delivered on Jobs. The details are in Handing the result over.

Stopping in the middle

A period you've run stays as you left it: the result, the exceptions you've decided and the ones still to confirm are all kept. You can close TableDI 2 and pick up later from the job's card, which shows where the period stands — Done · ready to deliver, for example.

Each period runs once

TableDI 2 won't run a period label that isn't later than the last one run: the preflight refuses and says that period has already been run. In 2.0.0 there's no button to run the same period again.

So look at the preflight before you click Run this period. If a file for a period you've already run turns out to be wrong, settle the affected rows on Exceptions — waive them with a reason, or mark them to do — so the delivery says what happened, and get the source corrected for next period.

When not to run a period

Something is listed in red under Has to be fixed before this can run. The run button stays disabled until it's fixed, and each problem says what to do.
The row count is far off last period's, under Against last period. It's usually the wrong file or the wrong month; swap the file before running.
A column you rely on is missing. The preflight says that column comes out empty. If that makes the delivery useless, get a fresh export first.

Still stuck? Email us — one inbox, read by the people who build TableDI.