SMEStack — Payday Super check: sample pack ========================================== Synthetic data. Fund names are real, but member numbers, USIs, ABNs and every amount are invented. No real person, fund account or bank transaction is in these files. The three files are modelled on what a bookkeeper actually exports, not on how this tool happens to read files: 1-xero-superannuation-payments.csv Xero-style superannuation payment report. Day-first dates (13/11/2026), currency-formatted amounts ("$2,000.00"), a grouped fund column and a trailing Total row. The report columns the payment by its expected pay date. 1myob-pay-super-same-data.csv The same four employees from a MYOB-style export: different headers (Member ID, Pay Date, Contribution) and "13 Nov 2026" dates. Use either; the tool maps both without help. 2-clearinghouse-acknowledgement-*.csv Clearing-house acknowledgement: one row per contribution, keyed by Payment Reference Number, with fund ABN, settlement date, status and the clearing house's own error code. 3-bank-transaction-list.csv Bank transaction list with separate Debit and Credit columns, a running balance and prefixed narratives ("CLICK SUPER PTY LTD SUPERANNUATION PRN-X7F2-0001"). Payday is Friday 13 November 2026, so the seven-business-day deadline is Tuesday 24 November 2026. RUN A — everything reconciles 1-xero-superannuation-payments.csv 2-clearinghouse-acknowledgement-clean.csv 3-bank-transaction-list.csv Expected: 4 employees, 1 payday, $1,140 reported, $1,140 confirmed, 0 exceptions. RUN B — four planted problems 1-xero-superannuation-payments.csv 2-clearinghouse-acknowledgement-exceptions.csv 3-bank-transaction-list.csv What is wrong, and what it looks like in a real month: Alice Nguyen settled 27/11/2026, three days after the deadline. -> late receipt. The fund had the money inside the week; the deadline is on the fund receiving it, not on you paying. Ben Carter Rejected, error MEMBER_ID_INVALID, no settlement date. -> fund rejection. The member number does not exist at that fund. The tool quotes the clearing house's code, and the Error Decoder explains the fix. Chris Wong $100.00 accepted against $216.00 reported. -> partial payment. $116 is still short and starts accruing exposure from 24/11. Dana Patel no acknowledgement row at all. -> not confirmed. Reported in the pay run, never came back from the clearing house. Expected: 4 exceptions, one per problem, $1,140 reported and $340 confirmed, $800 short. Every money-figure in the result is traceable to a row in one of the three files. What the pack deliberately does not pretend ------------------------------------------- - No "Qualifying Earnings" column: Xero and MYOB export OTE, or plain earnings. The tool maps OTE; where an export has no earnings base at all, the 12% check is skipped rather than guessed. - No clean "Status: Accepted/Rejected" only — the rejection carries the clearing house's code, because that is what your inbox carries, and it is what the Error Decoder exists to translate. - No negative-signed Amount column in the bank file. Banks give Debit and Credit columns; this pack uses them. Column names are matched automatically. If your export spells something differently, map it by hand on the page — the mismatch is worth reporting, because it means a real client's file would fail too. Nothing here is uploaded anywhere: each file is parsed inside your browser tab.