Ryan Duguid

Payday Super timing evidence evaluation

Result: the 4 fictional fixtures return AT_RISK for a timely remittance with no fund receipt, LATE for a late remittance or a late receipt, and ON_TIME only for a receipt on the due date. Reproduce them below, then inspect what remittance evidence cannot establish.

Published 26 August 2026. Last reviewed 30 September 2026. This review puts the recorded result first. The recorded evaluation and its release pins are unchanged. Newer releases exist; the Payday Super page names the current one.

Accounting problem

For Payday Super, the operational record can show when money was remitted, but the statutory timing question depends on when an eligible fund received and allocated the contribution.

Intended reviewer

This pack is for an accountant, payroll reviewer or technical evaluator who wants to reproduce the evidence classifications without handling a client payroll export.

Fictional inputs

The 4 CSV fixtures contain fictional dates and amounts for a supported due date of 17 August 2026 and an as-at date of 20 August 2026. No client, employee or live payroll data is included.

Reproduce

This historical run remains pinned to 0.1.3. Checker 0.1.6 treats a receipt date without an amount as full receipt, with a caveat. Published 0.1.7 corrects that assumption. Check the version-specific receipt rules; these historical outputs do not establish a fix.

Needs Git, and uv with Python 3.12; the commands are the same on Windows, macOS and Linux. Clone the australian-accounting monorepo at tag payday-super-checker/v0.1.3 (commit 8e9bd7235030b2c42bc8f2e7d2e8a60dce627182) and run these commands from packages/payday-super-checker. The first 4 commands write the 4 reports; the final command runs the evaluation contract test. 

git clone --branch payday-super-checker/v0.1.3 --depth 1 https://github.com/ryanduguid/australian-accounting.git
cd australian-accounting/packages/payday-super-checker
uv run --locked --extra dev --python 3.12 payday-super-check evaluation/payday_super_evidence/fixtures/timely_remittance_no_receipt.csv --as-at 2026-08-20 -o timely-report.csv
uv run --locked --extra dev --python 3.12 payday-super-check evaluation/payday_super_evidence/fixtures/late_remittance_no_receipt.csv --as-at 2026-08-20 -o late-remittance-report.csv
uv run --locked --extra dev --python 3.12 payday-super-check evaluation/payday_super_evidence/fixtures/receipt_on_due_date.csv --as-at 2026-08-20 -o on-time-report.csv
uv run --locked --extra dev --python 3.12 payday-super-check evaluation/payday_super_evidence/fixtures/receipt_after_due_date.csv --as-at 2026-08-20 -o late-receipt-report.csv
uv run --locked --extra dev --python 3.12 pytest tests/test_evaluation_pack.py -q

Recorded development evidence pack

The tool page describes the workflow introduced in checker 0.1.4 and MCP 0.2.2. These commands preserve the original development snapshot for comparison. From the monorepo root, fetch CLI PR 147 and select the exact development revision below before entering the checker directory. The published v0.1.3 checkout used above does not contain this command.

git fetch origin pull/147/head
git switch --detach d91bef569e01c8b9e4f15bbe0978f33bf4567a8b
cd packages/payday-super-checker
uv run --locked payday-super-check evidence-pack evaluation/payday_super_evidence/fixtures/timely_remittance_no_receipt.csv --as-at 2026-08-20 -o evidence-pack
uv run --locked --extra dev pytest tests/test_evidence_pack.py -q

The evidence pack command exits 2 and writes 4 files into a new directory. exceptions.json must contain AT_RISK; decision-log.md has blank evidence, decision and sign-off sections. Tests verify deterministic output, identifier omission, SHA-256 binding, existing-directory refusal and the 4 pinned timing outcomes. They do not establish model performance or renew the legal review date.

The new command follows review-pack exit meanings: 0 only for all ON_TIME, 2 for any exception and 1 on input or write failure. The existing checker command retains its remittance-confirmation behaviour. Missing fund receipt evidence is never inferred.

Expected result

Fictional fixture Expected result
timely_remittance_no_receipt.csv timely_remittance_no_receipt.csv exits 2 with AT_RISK.
late_remittance_no_receipt.csv late_remittance_no_receipt.csv exits 2 with LATE.
receipt_on_due_date.csv receipt_on_due_date.csv exits 0 with ON_TIME.
receipt_after_due_date.csv receipt_after_due_date.csv exits 2 with LATE.

A missing receipt cannot prove on-time, remittance timing can prove late and timely remittance without receipt remains at-risk. The outcome identifiers are AT_RISK, ON_TIME and LATE.

Controls triggered

The production check keeps a missing receipt at AT_RISK, records an on-time receipt as ON_TIME and classifies a remittance after the deadline or a late receipt as LATE.

Primary sources

Versions

Product release v0.1.3; fixture version 1; source reviewed 15 August 2026.

payday-super-checker/v0.1.3 is the first release from the australian-accounting monorepo and the first to contain the evaluation directory. Its calculation behaviour is unchanged from v0.1.2, and the evaluation artefacts are fixed to that release’s commit.

Human decision

Remittance evidence can show operational timing but cannot prove on-time; a human must establish eligible fund receipt, allocation and the other assessment facts before relying on a statutory conclusion.

Limitations

Experimental review aid. Not a compliance determination. This evaluation does not provide advice or make an ATO assessment. It tests fictional evidence classifications only. See Evidence and Assurance for the common assurance record and boundaries.

Written by Ryan Duguid in his own time and on his own equipment.