Backdated Incapacity Needs Three Ledgers, Not One Payroll Fix

A retrospective incapacity determination can affect claim payments, payroll transactions and leave records at once. Those records do not carry the same legal meaning. AI should reconcile three ledgers and expose variances, while authorised claims and payroll professionals approve and post every correction.

A backdated incapacity determination is not an instruction to reverse every leave entry in the accepted period. It is the start of a controlled reconciliation.

Sending one accepted range to payroll collapses three questions: what compensation was determined and paid, what payroll processed, and what leave was debited or accrued under the governing law or instrument.

Keep three ledgers. Join them by date and source. Let AI identify the mismatches, then require claims and payroll professionals to decide what each mismatch means before a transaction is posted.

Why does one payroll adjustment fail?

The current Safety, Rehabilitation and Compensation Act 1988, Compilation 82 (the SRC Act), effective 1 July 2026, deals with incapacity compensation and leave through different provisions. Section 19 provides for weekly compensation where an employee is incapacitated for work as a result of an injury and the section applies. The relevant authority determines entitlement. Payroll records are evidence, not a substitute determination.

Section 116 addresses post-determination compensation leave. Sick leave and recreation leave entitlements continue to accrue during each of the first 45 weeks of that leave, while long service leave continues to accrue throughout it. The section defines post-determination compensation leave by reference to compensation leave after the pre-determination period.

Section 19(2A)(b) measures cumulative hours prevented from working against 45 times normal weekly hours, and Comcare's FAQ says retrospective incapacity periods count. By contrast, Comcare's October 2024 guidance counts qualifying compensation leave in each seven-day block as a section 116 week. Those weeks need not be consecutive or align with section 19. Copying a claims-system week number into a leave field can therefore be precise and wrong.

The pre-determination period creates another boundary. Comcare's guidance says the SRC Act does not expressly deal with leave accrual during that period. Accrual of National Employment Standards leave is governed by the Fair Work Act 2009 and instruments made under it. Section 130 of that Act generally restricts taking or accruing leave under the National Employment Standards during a workers compensation period, but permits it where a compensation law allows it and separately preserves unpaid parental leave.

Do not turn section 23A into a universal reversal rule. Its current text applies where the Commonwealth made salary, wages or pay and Comcare determined compensation. Section 5(7) reads Commonwealth references as references to a Commonwealth authority for its employees. Section 23A then deals with repayment, set-off and leave-credit restoration. Neither provision makes it a payroll instruction for a licensed bank operating as an eligible corporation.

For a licensed corporation, the treatment of pre-determination leave, payroll corrections and any proposed recovery must be checked against the SRC Act provision actually engaged, the Fair Work Act, the applicable enterprise agreement or contract, and approved employer procedures. Comcare's leave-accrual FAQ tells employers considering remedial action to refer to their own policies and procedures for leave entitlements and debts and seek advice as required.

What belongs in each ledger?

The three ledgers should share an interval ID, not a conclusion. Break the history whenever a determination version, payment status, pay code, leave code or legal period changes.

Ledger one: the claim determination and payment record. Capture the determination date, determined incapacity period, relevant section, weekly or part-week period, authorised amount, payment status, version and source location. Preserve a later variation as a new version. Do not ask the model to recalculate normal weekly earnings, actual earnings or the incapacity amount.

Ledger two: the payroll cash record. Capture each pay cycle, earning or absence code, gross transaction, reversal, adjustment, posting date and payroll source. Distinguish salary paid for work, paid leave, compensation passed through payroll and other adjustments. Never infer the legal character of a transaction from a code label alone.

Ledger three: the leave record. Capture leave type, dates or hours debited, leave payments, accrual entries, correction history, the stated legal or instrument basis and the human owner. Split the pre-determination period from the post-determination period. For the latter, preserve the separate section 116 week count and the evidence that compensation leave occurred in each seven-day interval.

This prompt builds a candidate three-ledger pack from de-identified source material. A claims professional must verify ledger one, and payroll must verify ledgers two and three before the output is used.

Build a de-identified three-ledger reconciliation for [CLAIM_NUMBER].

Ledger 1: copy the human determination and payment periods, amounts, versions and source locations.
Ledger 2: copy payroll pay cycles, pay codes, gross transactions, reversals and source locations.
Ledger 3: copy leave types, debit dates or hours, accrual entries, correction history and source locations.

Split intervals whenever a determination, payment status, pay code, leave code or pre-determination status changes. Give every row an interval ID and source anchor.

Return only source-backed entries, conflicts and missing fields. Do not calculate incapacity, decide leave entitlement, apply section 23A, propose a debt, restore leave, post a correction or make a legal conclusion. Mark each candidate issue with its required human owner: claims, payroll, employee relations or legal.

The output should include a variance register. Useful types are claim period has no payroll match, payroll transaction has no claim source, leave debit overlaps determined period, accrual basis missing, section 116 week count inconsistent and transaction already reversed. These labels identify data conditions, not an underpayment, overpayment or leave entitlement.

How should the three-ledger control work?

Start with immutable source extracts. Use the signed determination and authorised payment record for the claim ledger, payroll transaction detail for the cash ledger, and the leave movement history for the leave ledger. A current balance alone is inadequate because it conceals the sequence of debits, accruals and reversals.

Next, normalise dates to daily or part-day intervals. This is a matching technique, not a legal calculation. If a fortnight contains personal leave, hours worked and an incapacity payment, split it so the source transactions can be compared without pretending the whole pay period has one status.

Then apply a two-owner review. Claims confirms that the accepted periods, amounts and payment statuses have been transcribed correctly. Payroll confirms the pay and leave transactions, the employment instrument and the proposed posting method. Employee relations or legal review is triggered where the proposed action involves a deduction, debt, exited employee, disputed entitlement or uncertain instrument.

Only after those reviews should a human create a posting instruction. That instruction should identify the exact transaction, amount or leave unit, authority, approver and effective date. The AI output stays attached as working material, not as the authority for the correction.

Consider this fictional, de-identified example. [CLAIMANT_NAME] under [CLAIM_NUMBER] was absent between [ABSENCE_START] and [ABSENCE_END]. Payroll debited personal leave during part of that period. On [DETERMINATION_DATE], the relevant authority determined that section 19 compensation was payable for [DETERMINED_START] to [DETERMINED_END].

The model copies the determined period into ledger one. It records the salary and paid-leave transactions in ledger two and the leave debits and accrual movements in ledger three. It splits the timeline at [DETERMINATION_DATE] because Comcare's guidance treats the day of the favourable incapacity determination as part of the pre-determination period, with post-determination compensation leave beginning after that day.

The model flags the personal-leave overlap. It does not order restoration. Because the employer is a fictional licensed corporation, it also flags that section 23A cannot simply be applied as though the salary had been paid by the Commonwealth and the decision made by Comcare. Payroll reviews [APPLICABLE_INSTRUMENT] and the employer's approved procedure. Claims confirms the determined payment and whether any amount has already been passed through payroll.

For later absence after [DETERMINATION_DATE], the model builds a separate section 116 counter from the evidence of compensation leave in each seven-day period. It does not reuse the section 19 week count. Any candidate leave adjustment remains unposted until both owners approve it.

This second prompt stress-tests a proposed reconciliation. A human must inspect every cited record, confirm the governing rule and approve any posting or communication.

Audit the proposed three-ledger reconciliation for [CLAIM_NUMBER].

For each interval, compare the authorised claim record, payroll transactions and leave movements. Report:
1. exact source anchors;
2. matched fields;
3. unmatched or duplicated transactions;
4. whether the interval is pre-determination or post-determination;
5. any asserted section 116 week number and its evidence; and
6. the human decision required before action.

Do not recalculate compensation. Do not assume a pay-code label proves salary, leave or compensation. Do not apply section 23A to a licensed corporation. Do not decide a leave restoration, deduction, recovery, underpayment or overpayment. Do not write to payroll. Return candidate variances only.

Finish with a post-run tie-out. Confirm that approved entries posted once, rejected entries did not post, balances moved as authorised and the employee-facing explanation matches the final transactions. A zero variance is not enough if the audit trail cannot show why each entry changed.

Do this Monday

1. Name the three owners. Assign claims ownership for the determination ledger, payroll ownership for cash and leave transactions, and a clear escalation owner for instrument or debt questions.
2. Export movement histories. Obtain effective-dated claim payments, payroll transactions and leave movements. Do not start from current balances or a manually prepared total.
3. Create interval IDs. Split a fictional test case at every determination, pay-code, leave-code and pre-determination boundary. Confirm each row retains a source anchor.
4. Block automatic posting. Remove any permission that lets an AI reconciliation write a reversal, leave credit, deduction or recovery entry directly to payroll.
5. Test the section 23A boundary. Confirm the workflow does not apply the Commonwealth and Comcare rule to a licensed corporation without a separate legal basis.
6. Run the two-owner tie-out. Require claims and payroll approval before posting, then verify the posting against the approved instruction and employee communication.

Bottom line

A backdated incapacity determination creates a reconciliation problem, not a one-click payroll fix. The claim, cash and leave ledgers answer different questions and can run on different statutory or instrument rules. AI can align their intervals and expose unexplained variance. Humans must calculate compensation, determine leave treatment, approve any recovery or restoration, post every correction and preserve the reasons.

This article is general information and education only. It is not legal advice, and it is not advice about any individual claim. Decisions under the Safety, Rehabilitation and Compensation Act 1988 are made by human decision-makers on the individual merits of each claim, and claimants have reconsideration and review rights in respect of determinations. Seek advice specific to your scheme and circumstances.

References

1. Federal Register of Legislation, Safety, Rehabilitation and Compensation Act 1988, Compilation No. 82, effective 1 July 2026. https://www.legislation.gov.au/C2004A03668/latest/text
2. Federal Register of Legislation, Fair Work Act 2009, Compilation No. 73, effective 7 July 2026. https://www.legislation.gov.au/C2009A00028/latest/text
3. Comcare, Scheme guidance: Accrual of leave, current webpage. https://www.comcare.gov.au/scheme-legislation/src-act/guidance/scheme-guidance-accrual-of-leave
4. Comcare, Accrual of leave, section 116, Safety, Rehabilitation and Compensation Act 1988, SRC332, October 2024. https://www.comcare.gov.au/about/forms-pubs/docs/pubs/scheme-guidance/section-116-leave-accrual.pdf
5. Comcare, Frequently asked questions: Accrual of leave during a period of compensation leave, March 2022. https://www.comcare.gov.au/about/forms-pubs/docs/pubs/scheme-guidance/faq-accrual-of-leave-during-a-period-of-compensation-leave.pdf