Ansicht
Dokumentation

HIECEOY0 - IE Year End Report : Production of Legislative Forms

Vendor Master (General Section) BAL_S_LOG - Application Log: Log header data
This documentation is copyright by SAP AG.

Title

Year-End reporting for Ireland

Use

This program produces the following year-end reports for Ireland:

P60 - End of year Summary for the Employee

P35L - Employee's Annual Return to Revenue Commissioner (with PPS Number)

P35LT - Employee's Annual Return to Revenue Commissioner (without PPS Number)

E-Filing - XML file that can be sent to the Revenue Commissioner electronically

PRD35 - Employer's Annual Return for Pension Related Deduction (PRD) for submission to Department of Finance (only relevant for Public Sector)

PRD60M/S - End of Year Pension Related Deduction (PRD) summary certificate for the employee (only relevant for Public Sector)

PRD60R - Revised EOY PRD certificate for the employee (only relevant for Public Sector)

End of year Summary for the Employee (P60)

A P60 form is only generated if the employee is working with the company on December 31st of an appropriate tax year.

Employee's Annual Return to Revenue Commissioner (P35L/P35LT)

A P35L(LT) is always generated, even if the employee has left the company during this particular tax year. Once an employee has an organisational assignment change within the year, that implies a tax reference change, the reports will be produced one record per particular tax reference. (That is, if an employee changes the tax reference from July 1st of a specific tax year, then two P35L records are generated, one with the values for the period 01.01 to 30.06 and one for the period 01.07 to 31.12. If they should change back to their original tax reference within the same tax year, then these earnings are added to the earlierone with the same tax reference, thus still two P35L/LTs records would be issued).

According to legislation, a P35L/LT entry should not be produced for any employee not having any reportable situation, that is Tax, USC, Local Property Tax (LPT), PRSI, Tax credits equal to zero.

Employer's Annual Return to Revenue Commissioner (P35)

The P35 form is no longer required as annual returns are made by means of an XML file uploaded to Revenue Online Services (ROS).

The report can be run both in online and batch mode. In order to make printing more convenient, the printing of each form is sent to a different spool request.

If you start the report in online, you will come - upon execution- to a screen which allows you to choose which form you wish to display, also you will be presented with the report statistics. You can switch between all different forms as often as you like. If you start with output option SAPScript, you first have the chance to check the forms.

Under menu option Extras', you will be able to switch to the ALV output and check the appropriate information via the ALV tool. If you start with output option ALV, you can not switch to a SAPScript display.

Also under menu option Extras, you will find the display of the error lists, either with Information messages (I/W/E) or only warnings and errors (W/E).

You also find there the opportunity to display the timeframes in ALV. This ALV output is supposed to be an analysis tool and is only meaningful if you run the report for a single employee. (Note: If you run the report for a set of employees the list only shows the timeframes for the last processed employee)

End-of-Year (EOY) returns - P35L and P35LT forms

You can generate an E-file in XML format for the End-of-Year (EOY) returns - P35 form. You can submit this file to the Revenue Online Service (ROS) electronically through the internet. E-filing is applicable from tax year 2005 (01/01/2005 - 12/31/2005) onwards.

To generate an E-file select the Generate XML option on the selection screen of this report.

After you run the report, you have the following options:

Display XML - Select this option on the Application Tool Bar to display the generated XML file that you can submit to the ROS.

Save XML (PC) - From the menu bar, choose Extras->Save XML (PC), to download the generated XML file on to the presentation server.

XML Errors - From the Menu options, choose Extras-> XML Errors,to view the errors pertaining to the XML file generated.

End-of-Year PRD certificate

A PRD60 form is only generated if the employee is working with the company on December 31st of an appropriate tax year. There are two types of PRD60 form: PRD60M for main employment and PRD60S for subsidiary employment. Both forms contain the summary of total PRD amounts that the employee has paid till date. If you have activated the PRD solution in the system, an additional field PRD60will be displayed on the selection screen under SAP Scriptsection and the ALV output section.

PRD60R

You generate PRD60R certificate where you have revised the PRD values for an individual. It contains the summary of revised total PRD amounts for the employee. If you have activated the PRD solution in the system, an additional checkbox PRD60Rwill be displayed on the selection screen under Tax Criteriasection.

End of Year Return PRD35

You generate the PRD35 for submission to the authorities. It contains the summary of total PRD amounts that the employee have paid to date. If you have activated the PRD solution in the system, an additional field PRD35 will be displayed on the selection screen under the ALV output section.

Parameters

Tax year Determine timeframe for selection of personnel numbers

Please refer to detailed documentation

Tax reference Derives payroll areas for given tax reference

Please refer to detailed documentation

Test

Once this indicator is set, the SAPScripts that are generated contain the indicator Test. You can also run the report for any selection criteria combination you desire. In particular, this testsetting can be used to check during the run for a year how the reports are looking at a given point in time.

For example: How would the EOY look if done now?

If this indicator is not set, the EOY output are produced in a productive mode. As mentioned above, the productive mode forces a tax reference to be entered.

Output Options

The following output options exist for this report:

SAPScript Print or print preview the EOY reports via SAPScript forms.

ALV Output Shows the data for EOY reports via ALV

Create TemSe files for formsStore data for EOY reports to TemSe files

EP60E-mail output options

Submission Media

Generate XML

External data source (via TemSe) Reading TemSe files as data source.

Prerequisites

The following customizing activities should be performed/checked before you run this report:

Tables

Wage type assignment for EOY ,,(in the view cluster Non-statutory subapplications (VC_596A_B))

Features

ADDRS ,,Source of employee address (subtype of the infotype Addresses (0006)) RCLAS CEOY

ENTRY,,Definition of aspects to determine entry date (FB HR_STARTING_DATE)

LEAVE,,Definition of aspects to determine leave date (FB HR_LEAVING_DATE)

Constants

EOYER ,,Determines whether the Information messages should be printed in batch processing. (If the ,,,,,,constant does not exist or has value 0, then the information messages are printed)

Performance Information

A performance analysis on a midsized computer showed that 10.000 EOY reports take approximately 20 minutes under the option Create TemSe files for forms and Create TemSe file for MagMedia. The most time consuming part is the mass SAPScript production. For checking the results from the TemSe creation we recommend to use specific ALV display variants as this can reduce the run time substantially. You may define yourself various ALV display lists for the various checking aspects and switch between them when looking at the various aspects to check.

Information about Statistics

After the report is run it displays statistical information on the processing.

Selected persons : The number of employees selected for this run. Only those employees are considered who either had at least one active day in the tax year or got a payment in the tax year.

P35L forms generated : The number of produced P35L entries.

P35LT forms generated : The number of produced P35LT entries.

P60 forms generated : The number of produced P60 forms. Also this number typically is lower than the P35L(T) number as a P60 is only to be produced for employees active on 31st of December of the tax year.

P35 forms generated : The number of produced P35 forms. For production runs this number should never exceed 1.

Timeframes rejected :The report examines the timeframes of interest individually. (The following criteria must be identical within a timeframes: activity indicator and tax reference.) If such an timeframe can not be analysed due to a problem situation, it is rejected. It still could happen that other timeframes for an employee are correctly analysed. Please refer to the Error messages issued for those situations.

In principle the number of P35Ls generated plus those not needed plus the rejected timeframes should at least match (or exceed) the number of selected persons. The number of P60 forms generated should equate to your active headcount on 31st of December of an appropriate tax year.

Additional Technical Hints

For the SAPScript forms it might be useful to know what information is contained in each field, in case you wish to amend a SAPScript or even produce another view for the year end data. For the P60 form (HR_IE_P60_xxxx), the data is available in an internal table called P60 and the fields of structure P11_P60_C. So P60-BUKRS contains the company code. For the P35L form the internal table name is P35L.

For a comprehensive list of general fields available, please refer to the DDIC structure.

Section 1

Field,,Data Source

BUKRS,,Infotype Organizational Assignment (0001) field Company Code

BUTXT,,Text of appropriate company code from table T001

WERKS,,Infotype Organizational Assignment (0001) field Personnel Area

NAME1,,Text of appropriate personnel area from table T500P

BTRTL,,Infotype Organizational Assignment (0001) field Personnel Subarea

BTEXT,,Text of appropriate personnel subarea from table T001P

PERSG,,Infotype Organizational Assignment (0001) field Employee Group

PGTXT,,Text of appropriate employee group from table T501T

PERSK,,Infotype Organizational Assignment (0001) field Employee Subgroup

PKTXT,,Text of appropriate employee subgroup from table T503T

ORGEH,,Infotype Organizational Assignment (0001) field Organizatinal Unit

ORGTX,,Text of appropriate organizational unit from table T527X

KOSTL,,Infotype Organizational Assignment (0001) field Cost Center

KOSTT,,Text of appropriate cost center from Financial module

ABKRS,,Infotype Organizational Assignment (0001) field Payroll Area

ABKTX,,Text of appropriate payroll area from table T549T

ER_NAME,,Employer name from table T7IE6 (V_T5IE6)

ER_ADR1,,Employer address line 1 from table T7IE6 (V_T5IE6)

ER_ADR2,,Employer address line 2 from table T7IE6 (V_T5IE6)

ER_ADR3,,Employer address line 3 from table T7IE6 (V_T5IE6)

ERNIE,,Derived from Infotype 0359 (Tax data IE)

EUNIE,,Derived from ERNIE via T7IE6

WTEXT,,The personnel number of the employee

PERID,,Infotype Personal Data (0002) field PPS number

ACTVE,,Infotype Actions (0000) field Employment

ENAME,,Infotype Personal Data (0002) field Name

NACHN,,Infotype Personal Data (0002) field Last name

VORNA,,Infotype Personal Data (0002) field First name

NAME2,,Infotype Personal Data (0002) field Birth name

GBDAT,,Infotype Personal Data (0002) field Birth date

GESCH,,Derived from the infotype Personal Data (0002). The system reads the domain text of the gender
,,,,(Male/Female) and takes the first digit of this string.

LINE0,,,,Depending on the customizing of feature ADDRS, the data can be
,,,,read from different subtypes of infotype Addresses (0006)
,,,,The appropriate infotype is processed by the function module HR_MAKE_ADDRESS.
,,,,Field LINE0 is filled with the returned LINE1 (Skipping Form-of-Address)

LINE1,,as LINE0 but filled by LINE2

LINE2,,as LINE0 but filled by LINE3

LINE3,,as LINE0 but filled by LINE4.

PSTLZ,,Infotype Addresses (0006) field Postal code

LAND1,,Infotype Addresses (0006) field Country code

TXTBL,,Read from last payroll result in period. (Payroll structure IETAX field TXBAS, converting

,,,,N (Normal) to 0, W (Week1/Month1) to 1, E (Emergency) to 2 and X (Excluded) to 3

STARTD,,Represents the start date of an employee, delivered from function module
,,,,HR_ENTRY_DATE. If there are various timeframes, which would need
,,,,to be looked at separately and both have a start date, then
,,,,the earlier date is taken.

LEAVED,,Represents the leave date of an employee, delivered from function module
,,,,HR_LEAVING_DATE. If there are various timeframes, which would
,,,,need to be looked at separately and both have a start date,
,,,,then the earlier date is taken.

BEGDA,,ONLY technical meaning - the begin date of a particular timeframe.

ENDDA,,ONLY technical meaning - the end date of a particular timeframe.

TAXYR,,The appropriate tax year, which is derived from the report selection screen.

P_EARN,,Derived from the payroll results. Those wage types maintained
,,,,in the viewcluster VC_596A_B under cumulation wage type PAY1 will be taken.

C_EARN,,Derived from the payroll results. Those wage types maintained
,,,,in the viewcluster VC_596A_B under cumulation wage type PAY2 will be taken.

T_EARN,,Derived from the payroll results - addition of P_EARN and C_EARN.

P_TAX,,Derived from the payroll results. Those wage types maintained
,,,,in the viewcluster VC_596A_B under cumulation wage type TAX1 will be taken.

C_TAX,,Derived from the payroll results. Those wage types maintained
,,,,in the viewcluster VC_596A_B under cumulation wage type TAX2 will be taken.

T_TAX,,Derived from the payroll results - addition of P_TAX and C_TAX.

TFATO,,Derived from the payroll results (table RT) . Those wage types maintained
,,,,in the viewcluster VC_596A_B under cumulation wage type TCRE will be taken.

CUTOF,,Derived from the payroll results (table RT). Those wage types maintained
,,,,in the viewcluster VC_596A_B under cumulation wage type CUTO will be taken.

TOGRP,,Derived from the payroll results. Those wage types maintained
,,,,in the viewcluster VC_596A_B under cumulation wage type TOGR will be taken
,,,,Only used for the magnetic media.

,,,,in the viewcluster VC_596A_B under cumulation wage type TAX1 will be taken.