How Do I Correct Incorrectly Reported JobKeeper Eligibility Dates?

If you have incorrectly reported an employee's JobKeeper eligibility period you may need to correct the STP JobKeeper Fortnight codes as described on the last page of this ATO document, and shown below.

Regarding corrections of these JobKeeper flag codes, the ATO advises:

"This design does not support multiple corrections, so extreme
caution should be taken to ensure accuracy of originally reported
JobKeeper data."

These manual adjustment fortnights can be added into Lightning Payroll under Employees >> Tax Rates >> JobKeeper Settings.

Correct a JobKeeper Start Fortnight

There are several scenarios that may need correction with respect
to the JobKeeper Start Fortnight:

• Wrong employee – if the wrong employee was reported as
  eligible via the use of the JOBKEEPER-START-FNXX, then
  cancel this employee from eligibility via the use of matching
  JOBKEEPER-FINISH-FNXX where the “XX” fortnights are the
  same (cancellation via matching start/finish fortnights)
• Incorrect start FN (later) – if a later start fortnight is
  incorrectly reported, report an additional earlier start fortnight.
  ATO will assume the earliest start fortnight is relevant where
  no unmatched finish fortnight is reported. For example:
  reported JOBKEEPER-START-FN02 but should have been
  JOBKEEPER-START-FN01
• Incorrect start FN (earlier) – if an earlier start fortnight is
  incorrectly reported, cancel this entry via a matching finish
  fortnight (cancellation via matching start/finish fortnights) and
  report an additional later start fortnight
• Future-dated start FN – if the JobKeeper start fortnight is
  greater than the STP Pay Event Pay/Update Date field, then it
  will be ignored, as if not reported. It will only become valid in
  the matching JobKeeper fixed fortnight that applies. Do not
  cancel or otherwise attempt to correct this invalid entry.
  This design does not support multiple corrections, so extreme
  caution should be taken to ensure accuracy of originally reported
  JobKeeper data. This critical detail is used to determine
  reimbursement to the employer.

Correct a JobKeeper Finish Fortnight

There are several scenarios that may need correction with respect
to the JobKeeper Finish Fortnight:

• Wrong employee – if the wrong employee was reported as
  becoming ineligible via the use of the JOBKEEPER-FINISHFNXX, then cancel this ineligibility via the use of matching
  JOBKEEPER-START-FNXX where the “XX” fortnights are the
  same (cancellation via matching start/finish fortnights)
• Incorrect finish FN (later) – if a later finish fortnight is
  incorrectly reported, report an additional earlier finish fortnight.
  ATO will assume the earliest finish fortnight is relevant where
  no unmatched start fortnight is reported. For example:
  reported JOBKEEPER-FINISH-FN06 but should have been
  JOBKEEPER-START-FN05
• Incorrect finish FN (earlier) – if an earlier finish fortnight is
  incorrectly reported, cancel this entry via a matching start
  fortnight (cancellation via matching start/finish fortnights) and
  report an additional later finish fortnight
• Future-dated finish FN – if the JobKeeper finish fortnight is
  greater than the STP Pay Event Pay/Update Date field, then
  this will assist to inform the ATO that the period reported is the
  final pay to be claimed, as the employee becomes ineligible in
  the following fortnight. This is the required timing to report
  cessation of the JobKeeper payment – in the preceding
  fortnight, during the final JobKeeper eligible fortnight. Finish
  fortnights greater than the next JobKeeper fortnight are
  ignored. For example, an employee who becomes ineligible
  on 30/06/2020 will be reported in the pay period covering that
  JobKeeper fortnight (FN07) with JOBKEEPER-FINISH-FN08,
  as the employee may be terminated and not be included in
  future STP reports.

The correction options for the JobKeeper payment are limited,
given the use of the only STP Pay Event field that can be used for
this purpose: Other Allowance Type description field.
No other existing PAYEVNT.2018 field allows for the capture of
this data without delay. Extreme caution should be taken by
employers to ensure that validation and reconciliation processes
are strong enough to warrant confidence in the initially reported
data.