Skip to navigation Skip to content

Raising Public Governance, Performance and Accountability Act 2013 (PGPA) debts 107-04130000

Expand/Collapse all sectionsExpand all



For Debt Staff.

This document outlines how to raise PGPA debts arising from payments made to customers and organisations on behalf of customers.

Raising PGPA overpayments

Expand table

Step

Action

1

Raising a PGPA overpayment

The process below is for raising a PGPA overpayment for an organisation. If needed, also see other procedures on PGPA debts:

Use the Debt Action script to raise a PGPA debt for a customer.

Note: use the guided procedure in Customer First to raise TAP debts.

To raise a debt for an organisation, search for the organisation record. In these fields:

  • CRN, key organisation CRN, or
  • on the Organisation Name Search (ON) screen, in:
    • Org, key the name of the organisation, or
    • Keyword, key words appropriate to organisation
  • press [Enter]

Matches display on the Organisation List (OL) screen

Create a new organisation debt record if not on Debt Management and Information System (DMIS).

2

Manually create an overpayment

For a new overpayment record for an organisation, go to the Add Debt (OPAD) screen in DMIS.

3

Add Debt (OPAD) screen

On the OPAD screen, in these fields:

  • Benefit Type, key payment type at the time the overpayment occurred
  • Reason, key reason for the overpayment
  • Section of the Act, key Rule 11, PGPA Rule 2014
  • Date of Event, key the date of event that caused the overpayment. The date coded cannot be in the future
  • Start Date, key date of commencement of overpayment
  • End Date, key end date of overpayment
  • Calculated Amount, key correct amount of the overpayment

Once completed, the Overpayment Component Adjustment (OPCA) screen displays.

The Account Payable (OPAOD) screen is skipped as an Account payable does not get issued for PGPA debts:

4

Other fields on the OPAD screen

Other fields on this screen may need coding. This depends on the details of the overpayment:

  • Authority, PGPA. This defaults automatically and comes from the benefit type
  • Estimated Amount, can be keyed manually, if it was an overpayment created manually via the OPAD screen. It may be the same or different from the calculated amount

5

Component Amount (OPCA) screen

The screen flow goes to the OPCA screen.

Key the component amounts. The sum of component amounts must be equal to the overpayment total amount.

The OPCA screen shows the breakdown of an overpayment by financial years and payment components, mainly for tax adjustment.

For manually added overpayments, manually change the OPCA screen to raise an overpayment. The dates used in the financial year breakdown are based on the whole entitlement period. This is what customers would have been paid in the given financial year.

6

Key Dates (OPKD) screen

As automatic advice does not issue. Go to the Key Dates (OPKD) screen and in these fields:

  • Date Sent, key the date the manual advice sent
  • Comments, key the reason for the issue of the manual advice
  • By Logon Id, automatically defaults

7

DOC screen

Record details on a DOC, including a summary.

These notes help in the recovery process.