Skip to main content

Error: 'No Expense found on GL matrix for Pay code [PAY CODE]'

On the View Gross to Nett Observation report for a pay group, the following error appears: 'No Expense found on GL matrix for Pay code [PAY CODE]'

O
Written by Onyema Onyejekwe
Updated this week

If you encounter an error on the View Gross to Nett Observation report for a pay group, it may stem from one of two causes.

We’ve compiled a list of potential reasons for the error message and how to resolve them.


Pay code not set up

The specified pay code is not configured in the Profit and Loss or Balance Sheet matrix.

To resolve this, follow the steps below in Portal.

  1. Click Settings then under General Ledger Costing, click General Rules & Settings.

  2. From the dropdown menu, select Profit & Loss matrix type.

  3. Add a new row with:

    • Pay code

    • Department

    • Expense

  4. Click Save.

  5. From the dropdown menu, select Balance Sheet matrix type.

  6. Add a new row with:

    • Pay code

    • Department

    • Expense

  7. Click Save then re-run the GL.

πŸ“ŒNote: We recommend completing all changes in the UAT environment before applying them in the LIVE environment.



Pay code mapped at company level

The pay code is mapped in the company-level matrix, but the cost center has not been entered in the allowance screen for this pay code. To do this, follow the steps below.

Portal

  1. Click Employee then in the search field, search for employee.

  2. Beside the relevant employee, click VIEW then click Employee Allowances.

  3. Click Amend an Existing Allowance then locate the allowance record that uses this pay code.

  4. In the Amend Cost Centre field, adjust the cost centre as needed for this record.

  5. Click Save.

Back Office

  1. Click CorePay then click Employee.

  2. Click Employee Allowances then click Amend an Existing Allowance.

  3. Locate the allowance record that uses this allowance pay code.

  4. Amend the cost centre for the allowance record, then click the save

    icon.

Did this answer your question?