Pension journal configuration

You can set a global nominal for all pension schemes. However, this may not be detailed enough. If you enter {pension.override} as the global nominal A nominal account is a general ledger account that you close at the end of each accounting year., pension overrides can be used.

Pension overrides are used when operating more than one pension scheme and want to apply separate nominal mappings for each scheme.

1. Open the required company.

2. Go to Pension.

3. Select the required pension scheme.

4. Select Journal Configuration.

   

5. Enter the required:

   • Nominal Code Nominal codes are the codes that are used in the chart of accounts to record income and expenditure.

   • Nominal Name

   • Journal Narrative

6. Select Update Pension Scheme.

Check you have set {pension.override}.

1. Open the required company.

2. Select the company name and select Settings.

   

3. Go to Pay Codes.

4. Select Nominal Codes.

   

5. Go to Output CSV Format and select:

   • Default.

   • SAP SAP or Statutory Adoption Pay. If an employee is adopting a child with a partner, one of them may be entitled to SAP and the other may be entitled to Ordinary Statutory Paternity Pay (OSPP). SAP usually follows the same basis as SMP in terms of amounts of length of time. S/4HANA.

   • Mapped Output - only available when a mapped output file is used.

6. Select Enable Nominal Mappings - When selected, the fields can be split for use in mapped output files. This can be used with journal tokens.

7. Select Merge matching nominals if required.

8. Select Control Codes.

9. Go to EMPLOYEEPENCONTROL, EMPLOYERPENCONTROL & enter {pension.override} as the Nominal Code.

   

10. Select Employer Codes.

11. Go to PENSIONCONTRIB and enter {pension.override} as the Nominal Code.

    

12. Select Update Mappings.

Good to know...

• If either of the name or narrative fields are left blank at the pension level configuration, the output will default return the information for that field at nominal code level.

• There is a token called {Nominal.Code} that allows the user to reference what has been returned in the nominal code field using a single token. This will be utilised primarily in mapped output files.

• When the nominal journal is run it will be returning data from numerous locations into this field.

  In effect it will allow the user to draw the returned value from the resulting fixed mappings and look ups and return the results into a single mapped field.