PYUA

Payroll Ukraine (PY-UA)
HR-CEECUA110_604
Document Version: 2.0 – 16.10.2012

Copyright
© Copyright 2012 SAP AG. All rights reserved.
SAP Library document classification: PUBLIC

No part of this publication may be reproduced or transmitted in any form or for any purpose
without the express permission of SAP AG. The information contained herein may be
changed without prior notice.
No part of this publication may be reproduced or transmitted in any form or for any purpose
without the express permission of SAP AG. The information contained herein may be
changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary
software components of other software vendors.
Microsoft, Windows, Excel, Outlook, PowerPoint, Silverlight, and Visual Studio are registered
trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x,
System z, System z10, z10, z/VM, z/OS, OS/390, zEnterprise, PowerVM, Power Architecture,
Power Systems, POWER7, POWER6+, POWER6, POWER, PowerHA, pureScale, PowerPC,
BladeCenter, System Storage, Storwize, XIV, GPFS, HACMP, RETAIN, DB2 Connect, RACF,
Redbooks, OS/2, AIX, Intelligent Miner, WebSphere, Tivoli, Informix, and Smarter Planet are
trademarks or registered trademarks of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the United States and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registered
trademarks of Adobe Systems Incorporated in the United States and other countries.
Oracle and Java are registered trademarks of Oracle and its affiliates.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are
trademarks or registered trademarks of Citrix Systems Inc.
HTML, XML, XHTML, and W3C are trademarks or registered trademarks of W3C®, World
Wide Web Consortium, Massachusetts Institute of Technology.
Apple, App Store, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi-Touch, Objective-C,
Retina, Safari, Siri, and Xcode are trademarks or registered trademarks of Apple Inc.
IOS is a registered trademark of Cisco Systems Inc.
(C) SAP AG HELPX.PYUA 2

RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry
Torch, BlackBerry Storm, BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry App
World are trademarks or registered trademarks of Research in Motion Limited.
Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps,
Google Mobile Ads, Google Mobile Updater, Google Mobile, Google Store, Google Sync,
Google Updater, Google Voice, Google Mail, Gmail, YouTube, Dalvik and Android are
trademarks or registered trademarks of Google Inc.
INTERMEC is a registered trademark of Intermec Technologies Corporation.
Wi-Fi is a registered trademark of Wi-Fi Alliance.
Bluetooth is a registered trademark of Bluetooth SIG Inc.
Motorola is a registered trademark of Motorola Trademark Holdings LLC.
Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer,
StreamWork, SAP HANA, and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP AG in Germany and
other countries.
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal
Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services
mentioned herein as well as their respective logos are trademarks or registered trademarks of
Business Objects Software Ltd. Business Objects is an SAP company.
Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase
products and services mentioned herein as well as their respective logos are trademarks or
registered trademarks of Sybase Inc. Sybase is an SAP company.
Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are registered trademarks of
Crossgate AG in Germany and other countries. Crossgate is an SAP company.
All other product and service names mentioned are the trademarks of their respective
companies. Data contained in this document serves informational purposes only. National
product specifications may vary.
These materials are subject to change without notice. These materials are provided by SAP
AG and its affiliated companies ("SAP Group") for informational purposes only, without
representation or warranty of any kind, and SAP Group shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP Group products and
services are those that are set forth in the express warranty statements accompanying such
products and services, if any. Nothing herein should be construed as constituting an
additional warranty.

Icons in Body Text
Icon Meaning
Caution
Example
Note
Recommendation
Syntax
Additional icons are used in SAP Library documentation to help you identify different types of
information at a glance. For more information, see Help on Help General Information
Classes and Information Classes for Business Information Warehouse on the first page of any
version of SAP Library.
Typographic Conventions
Type Style Description
Example text Words or characters quoted from the screen. These include field names, screen
titles, pushbuttons labels, menu names, menu paths, and menu options.
Cross-references to other documentation.
Example text Emphasized words or phrases in body text, graphic titles, and table titles.
EXAMPLE TEXT Technical names of system objects. These include report names, program
names, transaction codes, table names, and key concepts of a programming
language when they are surrounded by body text, for example, SELECT and
INCLUDE.
Example text Output on the screen. This includes file and directory names and their paths,
messages, names of variables and parameters, source text, and names of
installation, upgrade and database tools.
Example text Exact user entry. These are words or characters that you enter in the system
exactly as they appear in the documentation.
<Example text> Variable user entry. Angle brackets indicate that you replace these words and
characters with appropriate entries to make entries in the system.
EXAMPLE TEXT Keys on the keyboard, for example, F2 or ENTER.

Table of Contents
Payroll Ukraine (PY-UA) ........................................................................................................ 9
Document Change History ............................................................................................... 10
Payroll in the SAP System ............................................................................................... 11
Payroll Basics (PY-XX-BS) ........................................................................................... 12
The Payroll Process ..................................................................................................... 13
Payroll in a Background Operation................................................................................ 14
Infotypes for Personnel Administration and Payroll ........................................................... 15
Infotypes of Personnel Administration and International Payroll..................................... 16
Infotypes for Payroll Ukraine ......................................................................................... 17
Personnel Actions: Ukraine-Specific Features ........................................................... 18
Documents and Certificates (Infotype 0290): Ukraine-Specific Features .................... 20
Tax and Social Insurance Payments (Infotype 0291): Ukraine-Specific Features ....... 21
Additional Social Insurance Data (Infotype 0292): Ukraine-Specific Features............. 22
Garnishment Orders (Infotype 0295): Ukraine-Specific Features ............................... 23
Garnishment Documents (Infotype 0296): Ukraine-Specific Features ........................ 24
Personnel Orders (Infotype 0298): Ukraine-Specific Features ................................... 26
Archiving of Personnel Orders ............................................................................... 28
Tax Privileges (Infotype 0299): Ukraine-Specific Features ......................................... 29
Absences (Infotype 2001): Ukraine-Specific Features ............................................... 30
Legal Properties (Infotype 1656) ............................................................................... 32
Relationship of Legal Entities in Organizational Management ................................ 34
Example: Structures of Company ....................................................................... 36
Payroll Basics for Payroll Ukraine .................................................................................... 38
Internal Tables for Payroll Ukraine ................................................................................ 39
Main Customizing Settings for Payroll Ukraine .............................................................. 40
Employee Status .......................................................................................................... 41
Determination of Employee Status ............................................................................ 42
Example: Recording Employee Status Changes .................................................... 44
Grouping of Personnel Assignments in Ukraine......................................................... 46
Evaluation of Payroll Data Using Employee Statuses ................................................ 49
Determination of Payroll Data After Rehiring Process ................................................... 51
Future Period Processing ............................................................................................. 53
Gross............................................................................................................................... 55
Wage Types ................................................................................................................. 57
Payments ..................................................................................................................... 58
Time Management Aspects in Payroll ........................................................................... 59
Wage Type Valuation ................................................................................................... 60
Technical Process of Average Processing (New) .......................................................... 61

Incentive Wages: Overview .......................................................................................... 64
Partial Period Remuneration (Factoring) ....................................................................... 65
Making of Indexation Payments .................................................................................... 66
Calculation of Indexation Amounts ............................................................................ 67
Personal Reduction in Indexation Amounts ............................................................... 69
Valuation of Employee Salary ................................................................................... 71
Calculation of Employee's Average Income .................................................................. 73
Continuation of Average Salary Following Transfer ................................................... 75
Absence Processing ........................................................................................................ 76
Calculation of Sick Pay ................................................................................................. 77
Calculation of Sick Pay for New Employees .............................................................. 79
Example: Linking Periods of Absence ....................................................................... 80
Calculation of Maternity Pay ......................................................................................... 82
Calculation of Vacation Pay .......................................................................................... 84
Limitation of Absence Pay ............................................................................................ 85
Example: Limitation of Sick Pay ................................................................................ 87
Net .................................................................................................................................. 88
Tax Classes ................................................................................................................. 89
Determination of Tax Classes ....................................................................................... 90
Income Tax .................................................................................................................. 91
Income Tax Calculation............................................................................................. 92
Example: Income Tax Calculation.......................................................................... 94
Privilege Processing for Income Tax ......................................................................... 96
Processing of Income Tax Discrepancies .................................................................. 97
Example: Processing of Income Tax Discrepancies ............................................... 99
Social Insurance ......................................................................................................... 101
Social Insurance Calculation ................................................................................... 102
Example: Social Insurance Contribution (ESV) .................................................... 104
Seniority Calculation ............................................................................................... 106
Garnishment Processing ............................................................................................ 108
Balances & Totals ...................................................................................................... 110
Loans ......................................................................................................................... 112
Off-Cycle Activities......................................................................................................... 113
Making Advance Off-Cycle Payments ......................................................................... 114
Additional Off-Cycle Payment (Infotype 0267) ............................................................. 115
Advance Payment Methods ........................................................................................ 117
Making Advance Payments Based on Monthly Salary ............................................. 118
Deduction Processing for Payments Based on Monthly Salary............................. 120
Making Off-Cycle Vacation Payments ..................................................................... 121
Making Off-Cycle Bonus Payments ......................................................................... 123

Off-Cycle Workbench ................................................................................................. 125
Payroll History......................................................................................................... 126
Off-Cycle Payroll ..................................................................................................... 127
Running Off-Cycle Payroll ................................................................................... 128
Reasons, Types and Categories for Off-Cycle Payroll .......................................... 129
Reversing Payroll Results.................................................................................... 131
Reversing the Payroll Result ............................................................................ 133
Effects of an Out-of-Sequence Reversal........................................................... 135
Making Mass Advance Off-Cycle Payments................................................................ 137
Preselecting Employees Requiring Master Data Records ........................................ 138
Employee Selection for Fast Data Entry .................................................................. 139
Creating Master Data Records ............................................................................ 140
Mass Generation of Records for Advance Off-Cycle Payments (HRUU0267) .......... 141
Completeness Check (HUAC0267)............................................................................. 143
Deductions and Calculation of the Bank Transfer Amount .............................................. 144
Example: Deductions Processing ............................................................................... 145
Example: Deductions Processing ............................................................................... 146
Subsequent Activities..................................................................................................... 147
Preliminary Program DME .......................................................................................... 148
Repeating a Payment Run ...................................................................................... 152
Wage and Salary Payments ....................................................................................... 153
Tools for the Salary / Remuneration Statement ........................................................... 154
Payroll Account (Report RPCKTOx0; HxxCKTO0) ...................................................... 155
Payroll Journal (RPCLJNx0; HxxCLJN0) .................................................................... 156
Posting to Accounting (PY-XX-DT) ............................................................................. 157
Reporting ....................................................................................................................... 158
Wage Type Reporter .................................................................................................. 159
Evaluating the Payroll Results Using ITs or the Logical Database ............................... 160
Personnel Administration Reports............................................................................... 161
Personnel Order Management Forms ..................................................................... 162
Form P-1 (HUAAORDP1) .................................................................................... 164
Form P-3 (HUAAORDP3) .................................................................................... 165
Form P-4 (HUAAORDP4) .................................................................................... 166
Payroll Reports........................................................................................................... 167
HR Process Workbench ................................................................................................. 168
Interface Toolbox for Human Resources (PX-XX-TL) ..................................................... 169
Glossary ........................................................................................................................ 170

Payroll Ukraine (PY-UA)
You use this component to run payroll for employees in Ukraine. In addition to the
international processes that apply to all countries, this component covers the specific
functions related to Ukraine and its legal environment.
This documentation contains some references to Russia and to Payroll Russia (PY-RU).
Unless stated otherwise, the corresponding functions are relevant for Ukraine too.
Integration
Components in Human Capital Management
The Payroll Ukraine (PY-UA) component is integrated with the Personnel Management (PA)
and Personnel Time Management (PT) components.
Other SAP Components

The Payroll Ukraine (PY-UA) component is integrated with the Financial Accounting (FI) and
Controlling (CO) components, which enable you to pay your employees and evaluate payroll
results respectively.
Features
This component allows you to carry out the following functions:
Generate and evaluate an employee’s net pay
Calculate contributions and taxes
Process garnishments
Create remuneration statements
Create reports for the State Tax Administration of Ukraine
Create reports for the Ukrainian pension fund
Prepare data for the Ministry of Statistics of Ukraine
Constraints
Multiple payroll calculations based on the Reference Personnel Number Priority infotype
(0121) are not supported, because the shipment does not contain a schema to process the
calculations.

Document Change History
Versio
Date Comment
n
21/08/201 The document has been updated in accordance with the latest legal
2.0
2 requirements.
10/08/201
1.0 First version released.
1

Payroll in the SAP System
For general information, see SAP Help Portal at http://help.sap.com SAP Business Suite
SAP ERP SAP ERP Central Component SAP ERP Central Component SAP ERP
Central Component 6.0 SAP Library English SAP ERP Central Component Human
Resources Payroll (PY) Payroll Other Countries (PY-XX) Payroll in the SAP System .

Payroll Basics (PY-XX-BS)
Resources Payroll (PY) Payroll Other Countries (PY-XX) Payroll in the SAP System
Payroll Basics (PY-XX-BS) .

The Payroll Process
The Payroll Process .

Payroll in a Background Operation
Payroll in a Background Operation .

Infotypes for Personnel Administration and Payroll
This section contains international infotypes that apply to all country versions and country-
specific infotypes.

Infotypes of Personnel Administration and
International Payroll
For general information about the Personnel Administration infotypes and the Payroll
infotypes that are valid internationally, see SAP Help Portal at http://help.sap.com SAP
Business Suite SAP ERP SAP ERP Central Component SAP ERP Central Component
SAP ERP Central Component 6.0 SAP Library English SAP ERP Central Component
Human Resources Payroll (PY) Payroll Other Countries (PY-XX) Infotypes for
Personnel Administration and International Payroll Infotypes of Personnel Administration
and International Payroll .

Infotypes for Payroll Ukraine
This section contains documentation about infotypes that you need to meet business and
legal requirements in Ukraine.

Personnel Actions: Ukraine-Specific Features
A personnel action is a series of infotypes that are added, changed, completely or partially
deleted, or delimited in the Human Resources (HR) System for the reason specified, for
example, hiring, change of cost center, and leaving.
You use the following Ukraine-specific personnel actions to meet requirements for storing
employee data in Ukraine.
Since Ukrainian legislation stipulates that you store and print a special document to record
personnel actions, you must add the Personnel Orders (0298) infotype to all personnel
actions.
The following table shows Ukraine-specific personnel actions and the info groups that contain
the required infotypes for the personnel actions.
To enable the system to correctly process personnel actions for hiring, leaving, and
rehiring, you must specify the reason behind a particular personnel action type. You make
the setting in Customizing for Personnel Management under Personnel Administration
Personal Data Russia-Specific Settings Assign Action Types for Hiring and Leaving
.
Personnel
Personnel Info
Action Description
Action Group
Type
The international info group contains a user

Hiring 01 10
group for Ukraine-specific infotypes.
Organizational The international info group contains a user

02 82
Reassignment group for Ukraine-specific infotypes.
The international info group contains a user

group for Ukraine-specific infotypes.
To ensure that the leaving date is entered

correctly in the Time Quota Compensation
Leaving 10 84 (0416) infotype, you use a dynamic action to
create it from the Personnel Orders (0298)
infotype. For more information, see Personnel
Orders (Infotype 0298): Ukraine-Specific
Features [Page 26].
Shows an example of a personnel action that

Vacation contains the infotype for storing and printing
UV UV
registration personnel orders, the Personnel Orders
infotype (0298).
A dynamic action that contains the necessary

Recall from
UF - Ukraine-specific infotypes to store data when
vacation
you call back employees from vacation.

For a list of the infotypes that an info group contains, see Customizing for Personnel
Management Personnel Administration Customizing Procedures Actions Define
infogroups .

Documents and Certificates (Infotype 0290):
Ukraine-Specific Features
Contains data related to an employee's personal documents and certificates, such as his or
her passport.
You use this infotype to enter the data stored in each of the following documents, which are
represented as subtypes of this infotype:
Passport of Ukrainian citizens (subtype UAIC)
Taypayer’s identification card (subtype UAIN)
Social insurance certificate (subtype UASC)
If you need to store data for documents that are not listed above, you can create your
own subtypes to represent the additional document types. You create new subtypes in
Customizing for Personnel Management under Personnel Administration Personal
Data Russia-Specific Settings Documents and Certificates Define Document Types
The system uses the data that you enter in the Documents and Certificates (0290) infotype to
enter an employee’s data on official forms, for example, on form 1DF. To determine in which
order reports read the subtypes for an employee, you specify the priority of the subtypes for a
given report in Customizing. You make this setting in Customizing for Payroll Ukraine under
Reporting General Tools Determine Priorities of Documents for Reporting .

Tax and Social Insurance Payments (Infotype
0291): Ukraine-Specific Features
Contains data related to the tax and social insurance deductions for an employee.
If an employee is subject to taxes that are not part of the standard tax schema, you use this
infotype to determine which taxes the system deducts from an employee during the payroll
run. As part of this process, you can add taxes to the common tax schema or remove taxes
from the common tax schema.
You determine which tax types you can select in this infotype in Customizing for
Personnel Management under Personnel Administration Payroll Data Tax and
Social Insurance Payments (Russia) Define Subtypes for Tax and SI Payments
Infotype .
Integration
The data stored in the Residence Status (0048) infotype also influences the level and kind of
social insurance payments that you deduct for an employee.

Additional Social Insurance Data (Infotype 0292):
Ukraine-Specific Features
Contains data about the social insurance group and social insurance group modifier (see
Glossary [Page 170]). You can also view an employee’s seniority in this infotype.
The system uses the data stored in this infotype to calculate how much an employee is paid
when he or she is sick. The percentage of a month’s salary that an employee receives as sick
pay depends on the social insurance group, and if applicable, the social insurance group
modifier.
You determine which social groups and social insurance group modifiers you want to select in
this infotype in Customizing for Personnel Management under Personnel Administration
Personal Data Ukraine-Specific Settings Additional Social Insurance Data .
If you do not enter social insurance data in this infotype, the system uses an employee’s
seniority to determine the social insurance group and corresponding level of payment in
accordance with the sickness certificate.
Example
Your employee, Andriy Buday, has worked for seven years without interruption. Andriy
becomes sick and is unable to work for 10 days.
In the system, you assign Andriy to social insurance group >5<8 (between five and eight
years of uninterrupted work). For the period of sickness, you use absence type 0159. The
system calculates the amount of pay that Andriy receives during the period of sickness using
the employee’s average pay during the previous year. The social insurance group >5<8
determines that the payment is reduced to 80%.
If Andriy had been in continuous employment for more than eight years, that is, in social
insurance group >8, Vladimir would receive 100% of his regular pay during a period of
absence (absence type 0159).

Garnishment Orders (Infotype 0295): Ukraine-
Specific Features
A set of master data relating to a garnishment order, which is based on a garnishment
document.
You use garnishment orders to store the processing data for a garnishment request. For
example, you store the following data:
The initial balance of a claim
The details of periodic deductions
You make settings about the garnishment order types, such as alimony, and the
calculation rules that you want to use for garnishment orders in Customizing for
Personnel Management under Personnel Administration Personal Data Ukraine-
Specific Settings Garnishment Orders .
You can display details of garnishments that your employees have paid by using the
Garnishment History (HUACGARI) report. For more information, see the report documentation
in the system.
Integration
Before you create a garnishment order, you create a garnishment document. For more
information, see Garnishment Documents (Infotype 0296) [Page 24].

Garnishment Documents (Infotype 0296): Ukraine-
Specific Features
A set of master data relating to garnishment documents, for example, as follows:
General information, such as the status, important dates, priority, and category of
garnishment documents
Vendor information
Information about the originator of the garnishment document
Details about the garnishment release date
You use a garnishment document as the basis for a garnishment order. When you save a
garnishment document, the system opens the maintenance transaction for garnishment
orders.
If you have not already created the payees that are required for garnishments, you can create
payees directly from the maintenance screen for this infotype. As part of this process, you can
use payees that you create in Human Resources (HR) or payees that you create in Financial
Accounting (FI). You determine whether the system uses payees from HR or FI based on the
employee's organizational assignment and the settings in Customizing for Personnel
Management under Personnel Administration Personal Data Ukraine-Specific Settings
Garnishment Documents Payee Data Determine Default Payee Data .
You make settings related to the payee and other general settings for garnishment
documents in Customizing for Personnel Management under Personnel Administration
Personal Data Ukraine-Specific Settings Garnishment Documents .
Multiple Garnishment Documents

If the courts issue multiple garnishments related to the same executive document, for
example, the courts issue an additional garnishment as a penalty, you create more than one
record in this infotype. Since they are related to the same executive document from the
courts, the system links them together using the ExDoc.No. (Executive Document Number)
field.
The system processes payments for multiple garnishment documents based on the status
and priority of the garnishment documents, as specified by the courts. For more information,
see the following system documentation:
Processing of the Priorities and Deduction Group Tables (UAPRI) function
Summarize Deductions in Table AIT (UADL) personnel calculation rule
Process Garnishments According to Priorities (UADE) personnel calculation rule
Calculate Balance of Deductions (UADR) personnel calculation rule
You make settings to link together garnishment documents in Customizing for Personnel
Management under Personnel Administration Personal Data Ukraine-Specific
Settings Garnishment Documents Determine Special Parameters for Garnishments
.

Garnishment History
You can display details of garnishments that your employees have paid by using the
Garnishment History (HUACGARI) report. For more information, see the report documentation
in the system.
More Information
Garnishment Processing [Page 108]

Personnel Orders (Infotype 0298): Ukraine-Specific
Features
Contains data related to the documents you create when one of your employees is involved in
a personnel action.
Ukrainian legislation stipulates that when an employee is involved in a personnel action, you
must record this event in a document. For example, you create a personnel action when you
hire someone, when you fire an employee, or when you assign an employee to a different
organizational unit.
When you execute a personnel action, you store general data, such as the start date, action
type, and reason for a personnel action, in the Actions (0000) infotype. After you enter the
general data, you create a personnel order for each personnel action.
When you execute a personnel action, you store general data, such as the start date, action
type, and reason for a personnel action, in the Actions (0000) infotype. After you enter the
general data, you create a personnel order for each personnel action. The Personnel Orders
(0298) infotype allows you to record the number of the personnel order, when the employee
signs the personnel order, and if the employee’s manager has signed the personnel order.
Details About Personnel Actions

In addition to the reason for a particular personnel action that you enter in the Actions (0000)
infotype, the Personnel Orders (0298) infotype allows you to enter details for each reason
behind a personnel action.
You enter the possible details about reasons for personnel actions in Customizing for
Personnel Management under Personnel Administration Personal Data Russia-
Specific Settings Personnel Orders Specify Details About Reasons for Personnel
Actions . You select these reasons when you create a personnel order.
If necessary, you can enter more than one set of details about a given reason for a personnel
action.
You make the setting that allows you to enter multiple sets of details in Customizing for
Personnel Management under Personnel Administration Personal Data Russia-
Specific Settings Personnel Orders Set Parameters About Reasons for Personnel
Actions .
Numbering of Personnel Orders

If you want the system to assign a number to a personnel order automatically by using the
next available number in the designated number range, choose the AutoNumber pushbutton.
You set up this function in Customizing for Personnel Management under Personnel
Administration Personal Data Russia-Specific Settings Personnel Orders Determine
Defaults for Personnel Order Number Ranges and Determine Number Range Intervals for
Personnel Orders .
Printing of Personnel Orders

To meet legal requirements, you can print forms for both individual personnel orders and
group personnel orders. To print the forms, you can use the following options:

Use the print function in the maintenance transaction for the infotype
Use a dynamic action to print the forms automatically when you create a new record,
for example, in this infotype.
For more information about dynamic actions, see Customizing for Personnel
Management under Personnel Administration Customizing Procedures
Dynamic Actions .
Additional Documents
This infotype allows you to store information about various documents, which are represented
by the Personnel Order (Ukraine) (UAOR) subtype.
To store additional data about the subtypes in this infotype, you can create standard texts and
assign them to each subtype. You can include these texts in the output forms that you
generate on the basis of personnel orders. To assign standard texts to subtypes, in
Customizing for Payroll Russia under Reporting Personnel Administration Personnel
Order Management Assign Standard Texts to Infotypes .
Time Quota Compensation during Leaving Action

By default, during the leaving action, the system enters the day after leaving as default
starting date in all infotypes included in the action. To ensure that the starting date is entered
as the actual day of leaving in the Time Quota Compensation (0416) infotype, you use a
dynamic action to create the Time Quota Compensation (0416) infotype from the Personnel
Orders (0298) infotype. For more information, see SAP Note 1678669.
Integration
You use the data stored in this infotype in forms that you are obliged to keep for a given
period of time, as defined by Ukrainian legislation. For example, you store data about when
employees start work in form P-1.
For more information about the reports you can run to generate forms that contain data about
personnel orders, see Personnel Order Management Forms [Page 162].
More Information
Archiving of Personnel Orders [External]

Archiving of Personnel Orders
This function enables you to archive personnel orders in the system.
You archive personnel orders by selecting Archive as the storage mode in the print dialog box
when you print personnel orders.
For more information about printing personnel orders, see Printing of Personnel Orders in
Personnel Orders (Infotype 0298): Ukraine—Specific Features [Page 26].
After you archive a personnel order, the ArchDocument pushbutton appears on the
maintenance screen for the Personnel Orders infotype. You use this function to view or print
personnel orders that you have archived.
If you change personnel orders and want to retain copies of all versions, you can archive
each version of the personnel order. If you archive multiple versions of a personnel order,
when you choose ArchDocument, you can select the versions as follows:
Using a dialog box
To enable this option, you must enter parameter ID ARCHIVELINKHITLIST and

parameter value BDN in your user profile (see Maintaining User Defaults and
Options).
Directly in the Adobe-based form viewer
Prerequisites
You have made the following settings in Customizing for SAP NetWeaver under Application
Server Basis Services ArchiveLink Basic Customizing :
1. You have checked the settings for the content repository that you want to use to
archive personnel orders in the Customizing activity Define Content Repositories.
2. You have created an active link to the content repository in which you want to archive
personnel orders.
To do this, in the Customizing activity Edit Links, enter the following data and specify
the required content repository:
Object Type Document Type Status of Link Entry Relationship
PREL HRORUORDER X TOAHR
To archive multiple versions of a personnel order, you must have selected Archive Versions
for the corresponding print output program. You make this setting in Customizing for Payroll
Ukraine under Reporting Personnel Administration Personnel Order Management
Determine Print Output Programs for Personnel Orders .

Tax Privileges (Infotype 0299): Ukraine-Specific
Features
Contains data about the personal income tax privileges to which employees are entitled.
You use the data stored in this infotype to determine the personal privilege that an employee
receives and the tax class to which the privilege applies.
The tax classes to which privileges apply are stored as subtypes in this infotype. You
determine which tax classes you want to be available in this infotype in Customizing for
Personnel Management under Personnel Administration Payroll Data Tax and Social
Insurance Payments (Russia) Define Subtypes for Tax Privileges Infotype .
You use this infotype to store data related only to personal tax privileges, for example, the
tax privilege to which employees are entitled when they have children. These tax
privileges require confirmation from the relevant authorities, which the employee must
give to the employer. You can only use tax privileges for which the Personal Priv.
(Personal Privilege) checkbox is selected in Customizing for Payroll Russia under Tax
and Social Insurance Payments Maintain Tax Privileges .

Absences (Infotype 2001): Ukraine-Specific
Features
Contains data about paid and unpaid absences that your employees take.
The international infotype has been enhanced to enable you to meet legal requirements in
Ukraine. For more information about the international infotype, see SAP Library for ERP
Central Component on SAP Help Portal at http://help.sap.com SAP ERP Central
Component SAP ERP Central Component Human Resources Personnel Time
Management (PT) Time Data Recording and Administration Time Management Infotypes
Time Recording Absences Infotype (2001) .
The sections below describe the functions that are specific to Ukraine.
Linking Absences
To meet legal requirements in Ukraine, the infotype enables you to link previous absences
with a current absence.
To use this function, make the settings in Customizing for Payroll Ukraine under
Absences Absence Link .
The table below describes the scenarios in which you can link absences:
Requirement Entry in Absence Link Group Box
For some absence types, Ukrainian legislation

stipulates that you must use the same rate for
absences that lie in different payroll periods. To In the Abs. Link – Average
use the same rate, you link together two
(Absence Link for Average) field,
absences, which means that the rate from a select the start date of the previous
previous absence applies to the current absence. absence.
For more information, see Absence Processing
[Page 76].
In the Subs. Sickness (Subsequent

Sickness) field, select the absence
record with which you want to link
According to Ukrainian legislation, you must the current absence record.
process some adjacent periods of sickness as if
they were one continuous period of sickness.
For example, you link together periods of When you select a record in the
sickness if they are related and you must process Subs. Sickness field, the
them as one for the purposes of continued sick system enters the start date of
pay or sick pay supplements. the corresponding absence
record in the Abs. Link –
Average (Absence Link for
Average) field automatically..
In some legally defined scenarios, you have to In the Ev. Date – Avg. (Evaluation
calculate an employee’s average pay in a certain Date for Average Calculation) field,
period in the past. enter the date that falls after the end
of the legally defined period in

Requirement Entry in Absence Link Group Box
which the system calculates an
For example, according to Ukrainian legislation,
when an employee is absent immediately before employee’s average pay.
the current absence, you must not calculate the
employee’s average pay in the legally defined
period immediately before the current absence.
Instead, you must calculate the average pay in
the legally defined period before the absence that
precedes the current absence.
Processing Absences to Care for Family Members

To meet legal requirements in Ukraine, you record periods of absence when your employees
take leave to care for members of their family who are sick. The subtype that you select for an
absence determines whether you can enter the family member that your employees take
leave to care for. For example, assume that one of your employees has to stay home to care
for his or her sick child. You process the absence in the system by recording the data on the
sickness certificate that your employees submit to you in the Additional Information group box
in the Absences (2001) infotype.
Integration
To record the family members that your employees take leave to care for, you can only select
family members who you store in the employee's master data in the Family
Member/Dependents (0021) infotype. For more information, see SAP Library for ERP Central
Component on SAP Help Portal at http://help.sap.com SAP ERP Central Component
SAP ERP Central Component Human Resources Payroll Payroll Russia Infotypes
for Russian Payroll Family Members/Dependents (Infotype 0021): Russia-Specific Features
.
To determine which subtypes you can use to store absences for employees who take leave to
care for sick family members, you use the Screen (2033) Control for Infotype 2001 - Russia
(33ABS) feature. For more information, see the online documentation for the Screen (2033)
Control for Infotype 2001 - Russia (33ABS) feature.
Note that these Russia-specific features are relevant for Ukraine as well.
More Information
Absence Processing [Page 76]
SAP Library for ERP Central Component on SAP Help Portal at http://help.sap.com
SAP ERP Central Component SAP ERP Central Component Human
Resources Personnel Time Management (PT) Time Data Recording and
Administration Time Management Infotypes Time Recording Absences Infotype
(2001)

Legal Properties (Infotype 1656)
This organizational management infotype contains organizational data that is specific to the
legal entities of companies registered in Ukraine.
You use this infotype to store information about a company's legal entities that are relevant
for legal reporting. This information is necessary for submitting legal forms in one or more of
the following reporting areas:
Income tax
Pension fund
Social insurance
Statistics Committee
The system uses information that is stored in this infotype to group personnel assignments for
different payroll and reporting purposes. This information includes a unique four-character
identifier for the legal entity. The system uses this identifier as a grouping value for grouping
the personnel assignments.
You enter organizational information for legal entities as follows:
Information Specific to Legal Entity Reporting
General Data
Contact Data
Information Specific to Income Tax, Pension Fund, Social Insurance, and Statistical
Reporting
Information Specific to Legal Entity Reporting

Legal entities are responsible for submitting legal reports to the authorities. The types of
reports that a legal entity submits to the authorities depend on the type of the legal entity. You
specify the reporting responsibilities of your legal entity as one of the following:
Head unit
Head units are responsible for submitting legal forms to the authorities in all of the
reporting areas specified above. Therefore, if you have specified that your legal entity
is a head unit, the system selects all reporting areas, and you cannot change this
setting.
Detached subdivision
You must also specify for which reporting areas the subdivision is responsible. You
can select the corresponding checkboxes to specify one or more of the following
areas:
o Income tax
o Pension fund
o Social insurance
o Statistics Committee

General Data
You enter the official data that is relevant for all the legal reporting types for which this legal
entity is responsible. This data is printed on all legal forms that the legal entity submits to the
authorities. You also specify the tax authority to which the legal entity submits its tax reports.
Contact Data
You enter the company's contact details such as address, telephone number, fax number,
and e-mail address. You also enter the communication details of the contact persons for the
legal entity.
Information Specific to Income Tax, Pension Fund, Social Insurance,

and Statistical Reporting
You enter official information that is specific to these reporting areas. You also specify the
communication details for the contact persons who are responsible for the corresponding
reporting area.
If the legal entity is a detached subdivision, you can enter official data and contact
information just for the reporting areas that you have specified for this legal entity.

Relationship of Legal Entities in Organizational
Management
To fulfill requirements for legal reporting and payroll calculation in Ukraine, you must
represent your company structure from both an internal, organizational perspective and a
legal perspective. To reflect both perspectives, you must represent your company as a matrix
organization. Matrix organizations have two dimensional structures: the vertical dimension
represents the internal, organizational perspective, whilst the horizontal dimension represents
the legal perspective. The horizontal dimension comprises legally autonomous units called
legal entities. For information about the international payroll tables, see SAP Help Portal at
http://help.sap.com SAP ERP SAP ERP Central Component Human Resources
Personnel Management (PA) Organizational Management Organizational Plan Mode
Matrix Organization .
To set up the matrix organizational structure as described, you use standard objects and
relationships in Organizational Management together with the Legal Properties (1656)
infotype.
In Ukraine, the relationship of legal entities in a company determines the following:
The reporting areas for which the legal entity submits legal reports
The organizational units for which the legal entity submits its reports
The grouping of personnel assignments for payroll and reporting purposes
Legal entities are responsible for submitting legal reports in one or more of the following
reporting areas:
Income tax
Pension fund
Social insurance
Statistic Committee
The reporting areas for which legal entities are responsible are determined by the type of
legal entity. The types of legal entities are as follows:
Head unit of organization
A company can have only one head unit. Head units are responsible for submitting
legal reports in all the reporting areas listed above. Head units submit legal reports for
the head unit as well as for the whole company (including detached subdivisions).
Detached subdivision
A company can have one or more detached subdivisions. Detached subdivisions,

however, cannot have any subordinate detached subdivisions. Detached subdivisions
are responsible for submitting legal reports in one or more of the reporting areas
listed above. Detached subdivisions submit reports only in the reporting areas
specified for them in the Legal Properties (1656) infotype.
Note that head units retain responsibility for submitting reports for the whole company
(including detached subdivisions).

More Information
Example: Structures of Company [Page 36]

Example: Structures of Company
To fulfill requirements for legal reporting and payroll calculation in Ukraine, you are required to
represent your company structure from both an internal, organizational perspective and a
legal perspective. To reflect both perspectives, you define your company as a matrix
organization using standard objects and relationships in Organizational Management together
with the Legal Properties (1656) infotype. The following examples illustrate typical company
structures from both the legal and the internal, organizational perspectives.
Company Without Detached Subdivisions

The figure below illustrates the legal and organizational aspects of a Ukrainian company
without detached subdivisions and is followed by an explanation:
Legal Structure Organizational Structure
Company A Company A
(OR 33000001) (O 3301)
Production Sales
Department Department
(O 3302) (O 3303)
Relationship type B, Legend for Object Types

relationship 401 in Org.
O = Organizational unit
Management
OR = Legal entity
Company Without Detached Subdivisions
Company A has two organizational subunits; a production department and a sales

department. From an internal, organizational perspective, Company A is represented by the
Company A (O 3301) organizational unit; both the Production Department (O 3302) and the
Sales Department (O 3303) organizational subunits report to this organizational unit.
However, from a legal perspective, Company A and all its organizational units (the Company
A (O 3301) head unit, and both its production and sales departments) are represented by the
Company A (OR 33000001) legal entity.
Company With Detached Subdivisions

The figure below illustrates the legal and organizational aspects of a Ukraine company with
detached subdivisions and is followed by an explanation:

Organizational Structure
Company A
(O 50000200)
Production Sales
Headquarters
Department Department
(O 50000201)
(O 50000202) (O 50000203)
Lvov
Donetsk (O 50000207)
(O 50000206)
Donetsk Lvov
Kiev
(O 50000204) (O 50000205)
(O 50000208)
Legal Structure
Company A Relationship type B,
(OR 33000001) relationship 401 in Org.
Management
Det. Subdivision Det. Subdivision

Donetsk Lvov
(OR 33000002) (OR 33000003)
(Legal entity for income tax
and pension fund reporting)
k
(Legal entity for income tax
reporting)
Legend for Object Types
O = Organizational unit
OR = Legal entity
Company With Detached Subdivisions
Company A has a number of organizational units. For example, from an internal,

organizational perspective, the sales department has subunits in Donetsk (O 50000206), Kiev
(O 50000208) and Lvov (O 50000207). Similarly, the production department has subunits in
Donetsk (O 50000204) and Lvov (O 50000205).
Note that the same relationships exist between the Donetsk detached subdivision (OR
33000002) and its sales and production department subunits (OR 33000004 and OR
33000004) respectively as those between the Lvov subdivision and its sales and production
department subunits.
From a legal perspective, the Company A (OR 33000001) legal entity has two detached
subdivisions; one in Lvov (OR 33000003) and one in Donetsk (OR 33000002). These legal
entities are responsible for submitting statutory reports to the authorities.
For tax reporting purposes, for example, this means that the Lvov subdivision submits income
tax reports to the local tax office for employees who have personnel assignments in the sales
and production department subunits in Lvov.
Note that depending on the setup of your organization, an organizational unit can report to
different companies; one for the internal, organizational perspective and the other for the legal
perspective.

Payroll Basics for Payroll Ukraine
To run payroll correctly for employees in Ukraine, the system uses extensions to international
payroll functions and concepts that are specific to Payroll Ukraine.
The functions and concepts are as follows:
Internal Tables for Payroll Ukraine [Page 39]
Main Customizing Settings for Payroll Ukraine [Page 40]
Employee Status [Page 41]
Determination of Payroll Data After Rehiring Process [Page 51]
Future Period Processing [Page 53]

Internal Tables for Payroll Ukraine
The Ukraine-specific payroll cluster, UA, contains the international payroll structure and the
following tables that are specific to Ukraine:
Technical Name of
Contents
Table
UAAV Cumulation of average amounts
FUP Data for processing future periods
Ukrainian salary indexation details according to the consumer price

UAIND
index (see Glossary [Page 170])
UAILL Data to calculate sick pay based on sickness certificates
UAGRP Data about employee groupings based on organizational assignment

and data about employee statuses
TAX Ukrainian tax calculation details
For information about the international payroll tables, see SAP Help Portal at
Payroll (PY) Payroll Other Countries (PY-XX) Payroll in the SAP System Payroll
Basics (PY-XX-BS) Internal Tables for Payroll .

Main Customizing Settings for Payroll Ukraine
To be able to run payroll correctly for employees in Ukraine, you make settings in
Customizing for Payroll Ukraine under Basic Settings Basic Settings – Ukraine . The
Customizing settings comprise the following fundamental parts of Payroll Ukraine:
Technical switches
o You configure the payroll functions and operations that are required for
Ukraine.
o You specify additional parameters, for example, the payroll schema ID,
seniority processes for defining an employee’s default social group, and
vacation selection processes for processing off-cycle payroll runs.
Legally defined settings
o You enter amounts that are defined by law, for example, the living wage and
minimum wage, and the validity periods of these amounts.
o You determine how the system classifies employees when you hire them,
when you terminate their employment contracts, and when you rehire
employees.
o You enter the details of global salary increases, which apply to all employees
in your company.

Employee Status
The definition of an employee based on criteria that affect the way in which the system
evaluates payroll data for employees.
An employee’s status is determined by the contents of the following infotypes:
An employee’s assignment to a legal entity in the Legal Properties (1656) infotype
An employee’s challenge group in the Challenge (0004) infotype
An employee’s contract type in the Contract Elements (0016) infotype
The system uses the employee’s status to evaluate payroll data in line with legal
requirements and to determine which tax schema (see Glossary [Page 170]) the system
uses for an employee.
More Information
Determination of Employee Status [Page 42]
Grouping of Personnel Assignments in Ukraine [Page 46]
Evaluation of Payroll Data Using Employee Statuses [Page 49]

Determination of Employee Status
The system determines an employee’s status based on an employee's attributes in the
following infotypes:
The Legal Properties (1656) infotype
The Challenge (0004) infotype
The Contract Elements (0016) infotype
For more information about an employee’s status, see Employee Status [Page 41].
Prerequisites
You have portrayed your organizational structure in the system and created the required
relationships between the organizational units. For more information, see SAP Help Portal at
Personnel Management (PA) Organizational Management Organizational Plan Mode
Organizational Management .
For each head unit and detached subdivision in your company, you have created a record in
the Legal Properties (1656) infotype. For more information, see Legal Properties (Infotype
1656) [Page 32].
Features
Data Stored in Legal Properties (1656) Infotype
To determine the attributes of an employee’s status that are based on his or her
organizational assignment, the system uses the legal entity to which an employee is assigned
in the Legal Properties (1656) infotype. In the Legal Properties (1656) infotype, the system
uses grouping reasons to assign a grouping value to each category of data, for example,
social insurance contributions, for which a legal entity is responsible. Depending on an
employee’s organizational assignment, his or her status comprises one or more grouping
values at any given point in time.
Assume that the head unit in your organization is responsible for filing all legal reports
with the authorities, whereas one of the detached subdivisions is responsible for filing
income tax reports only. If an employee is assigned to the detached subdivision, his or
her employee status comprises two different grouping values: one grouping value for
income tax reporting (for the detached subdivision) and a different grouping value (for the
head unit) for all other reporting purposes.
The system uses the following grouping reasons to assign grouping values in the Legal
Properties (1656) infotype:
Category of Data Grouping Reason
Assignment to head unit in organization UAER
Pension fund contributions UAPF

Category of Data Grouping Reason
Social insurance contributions UASI
Income tax deductions UATX
Reporting to State Statistics Committee of Ukraine (see Glossary

UACS
[Page 170])
For more information about how the system groups personnel assignments, see
Grouping of Personnel Assignments in Ukraine [Page 46].
Data Stored in Challenge and Contract Elements Infotypes

To determine an employee's attributes based on the data stored in the Challenge (0004) and
Contract Elements (0016) infotypes, the system reads an employee’s challenge group and
contract type that are valid at a given point in time.
Further Processing
To use an employee’s status for further processing in payroll, the system stores the grouping
values for the legal entity to which an employee is assigned in the Legal Properties (1656)
infotype as well as the challenge group and contract type in a special payroll table. For more
information about how the system processes employee statuses, see Evaluation of Payroll
Data Using Employee Statuses [Page 49].
More Information
Legal Properties (Infotype 1656) [Page 32]
Example: Recording Employee Status Changes [Page 44]

Example: Recording Employee Status Changes
The following sample scenarios show how the system records changes to an employee’s
status.
Change in Challenge Status

Assume that one of your employees, Olena Petrova, is injured in an accident and is
registered disabled starting on March 20. You record the employee’s challenge status in the
Challenge (0004) infotype.
After you update Olena’s master data in the system, the system records Olena’s new
challenge status starting on March 20 in the Ukraine-specific payroll table, UAGRP, as follows:
Social
Head Pensio Incom Statisti
Star Insuran
Unit n Fund e Tax cs Contr Challen
t End ce
Groupi Groupi Groupi Groupi act ge
Dat Date Groupi
ng ng ng ng Type Group
e ng
Value Value Value Value
Value
Mar
ch March
1, 19, 0001 0001 0001 0001 0001 01 –
201 2010
0
Mar
ch Decem
20, ber 31, 0001 0001 0001 0001 0001 01 01
201 9999
0
Change in Organizational Assignment

Assume that one of your employees, Anton Ivanchuk, works as an HR clerk in your
company’s head office in Kiev. To cover for a colleague who is on maternity leave, you
transfer Anton to your detached subdivision in Lviv on April 5. Two weeks later, a new
position for an HR specialist in Lviv opens up, and Anton gets the job. He starts his new job
on April 19.
You update Anton’s organizational assignment in the Organizational Assignment (0001)

infotype. Since the Lviv office is responsible for filing its own income tax and social insurance
reports with the local authorities, Oleg’s new organizational assignment corresponds to
different records for income tax and social insurance data in the Legal Properties (1656)
infotype. The system assigns grouping value 0002 to the detached subdivision for income tax
and social insurance data.
Furthermore, Anton’s new job as an HR specialist requires a new type of employment

contract, which you enter in the Contract Elements (0016) infotype.
After you update Anton’s master data in the system, the system records Anton’s status
changes in the Ukraine-specific payroll table, UAGRP, as follows:

Social
Head Pensio Incom Statisti
Insura
Unit n Fund e Tax cs Contr Challe
Start End nce
Groupi Groupi Groupi Groupi act nge
Date Date Groupi
ng ng ng ng Type Group
ng
Value
Janu
April 4,
ary 1, 0001 0001 0001 0001 0001 01 –
2010
2010
April April
5, 18, 0001 0001 0002 0002 0001 01 –
2010 2010
April Decem
19, ber 31, 0001 0001 0002 0002 0002 02 –
2010 9999

Grouping of Personnel Assignments in Ukraine
The system groups personnel assignments for different payroll and reporting purposes in
Ukraine using the following grouping features:
Grouping reason
Grouping reasons represent the business purpose for which personnel assignments
are grouped. They determine how the personnel assignments and the corresponding
data are processed. Each type of processing corresponds to a grouping reason as
described in the table below.
Grouping value
Grouping values are used to group personnel assignments. Each personnel

assignment is assigned a grouping value for each grouping reason. The system
groups personnel assignments that have the same grouping value for a specific
payroll or reporting purpose.
In Ukraine, grouping values are unique four-character identifiers. The system

attaches these identifiers to legal entities, such as company head units or detached
subdivisions, for a specific validity period. The system generates grouping values
when you create a record of the Legal Properties (1656) infotype for the legal entity,
and stores them in the infotype.
The following table lists the grouping reasons:
Descriptive Name
Grouping
of Grouping Type of Processing/Use
Reason
Reason
Payroll processing and the Sickness Certificate

Printing (HUAASIL0) report, used for processing
UAER Employer
assignments of head units and those of their detached
subdivisions together.
Legal Entity for

Payroll processing and the Form 1DF (HUAL1DF0)
UATX Income Tax
legal form for income tax reporting.
Reporting
Legal Entity for Payroll processing and the Pension Fund Declaration
UAPF Pension Fund
(HUALPFD0) report.
Reporting
Legal Entity for

UASI Social Insurance Payroll processing
Reporting
Legal Entity for

UACS Statistic Committee Payroll processing
Reporting
Features
Assignment of Grouping Values to Personnel Assignments
To group an employee's personnel assignments for any type of processing, the system
assigns grouping values to the personnel assignments according to the following:

The grouping reason for the type of processing in question
The legal perspective of the company structure
The system assigns a grouping value to a personnel assignment as follows:
1. For each personnel assignment that matches the selection criteria for the type of
processing that you use, the system determines to which organizational unit (object
type O in Organizational Management) it is assigned.
2. Starting from the organizational unit to which the personnel assignment is assigned,
the system finds the nearest legal entity in the organizational hierarchy (relationships
of type 002). For information about the international payroll tables, see SAP Help
Portal at http://help.sap.com SAP ERP SAP ERP Central Component Human
Resources Personnel Management (PA) Organizational Management Expert
Mode Organizational Management Organizational Plan Relationships (Infotype
1001) .
3. The system checks if the type of processing for which the system is grouping the
assignments is specified for this legal entity in the Legal Properties (1656) infotype.
For example, if the system groups assignments for an income tax report, it checks if
income tax is specified for this legal entity as a reporting area.
o If the system finds a match, it reads the grouping value of this legal entity
from the Legal Properties (1656) infotype, and assigns the value to the
personnel assignment.
o If the system does not find a match, it retrieves the company head unit using
the hierarchy of legal entities (relationships of type 400). Since company
head units are subject to all types of processing, the system finds a match
here. Therefore, the system assigns its grouping value to the personnel
assignment.
The system assigns grouping values based on their validity periods. The validity periods
of the values are the same as the validity periods of the records in the Legal Properties
(1656) infotype in which the grouping values are stored. Therefore, the system may
assign a grouping value or a set of grouping values with the corresponding validity
periods to a personnel assignment.
Use of Grouping Values for Payroll and Reporting

Grouping values are used to group personnel assignments for the following purposes:
Payroll
Reporting
Certain payroll and pension fund reports use these values to group personnel
assignments by legal entity as follows:
o Head unit (see Glossary [Page 170])
o Detached subdivision (see Glossary [Page 170])
o Head unit and all detached subdivisions (for the whole company)

Example
You run an income tax report for your company. Your company has a head unit (with
grouping value 0001) and two subdivisions, one of which is responsible for tax reporting.
The grouping process for this report is as follows:
The system uses the grouping reason UATX to group personnel assignments for tax
reporting purposes.
In the selection screen for the income tax report, you enter grouping value 0001 for
the head unit of the company. Note, the system allows you to enter only a grouping
value that corresponds to the grouping reason for tax reporting.
You also specify that you want to run the report for all employees of the head unit and
all its detached subdivisions. Since the company has a detached subdivision that is
responsible for tax reporting, the system uses its grouping value (0002) for grouping
in addition to that of the head unit.
For personnel assignment 1001, the nearest legal entity is a detached subdivision,
and its grouping value is 0002. This subdivision is responsible for submitting income
tax reports to the authorities, so the system assigns this grouping value to the
personnel assignment.
For personnel assignment 1002, the nearest legal entity is the head unit. Since the
head unit is also responsible for tax reporting, the system assigns this grouping value
to the personnel assignment.
Since the grouping values attached to the personnel assignments match the values that the
system uses for grouping, the system groups both personnel assignments for this tax report.
More Information
Legal Properties (Infotype 1656) [Page 32]
Relationship of Legal Entities in Organizational Management [Page 34]

Evaluation of Payroll Data Using Employee
Statuses
To meet legal reporting requirements in Ukraine, you must show the payroll data that applies
to an employee when he or she has a particular status. If an employee’s status changes in
the reporting period, Ukrainian legislation requires you to show the amounts and the rates of
income tax and social insurance contributions that apply at a given point in time.
The system also uses an employee’s status when it determines which rates for income
tax deductions and social insurance contributions apply to an employee. The system uses
the employee’s status to select the tax schema (see Glossary [Page 170]) that
comprises the required tax classes for an employee’s status.
Prerequisites
You have made the settings described in Determination of Employee Status [Page 42].
You have determined the work place/basic pay (WPBP) splits that you want to use in
Customizing for Payroll Ukraine under Basic Settings Basic Settings – Ukraine Set Up
WPBP Split and Create Starting Points .
Features
The system uses the validity period of an employee’s status to split the payroll results
according to the period of time when an employee’s status applies. To store an employee’s
payroll-related data based on an employee’s status, the system uses functions described
below.
International Functions Based on Work Place/Basic Pay (WPBP) Split

For more information about the international functions for wage type splits, see SAP Help
Portal at http://help.sap.com SAP ERP SAP ERP Central Component Human
Resources Payroll (PY) Payroll Other Countries (PY-XX) Gross Part of Payroll Wage
Types Wage Type Splits .
Ukraine-Specific Functions Related to an Employee’s Status

To assign the payroll data that applies to an employee at a given point in time, the system
splits the payroll data in line with any changes to an employee’s status. The Initialization of
Ukrainian Payroll (UAINI) payroll function reads the attributes of an employee’s status and
stores the data in the Ukraine-specific payroll table, UAGRP. The table contains the grouping
values, challenge group, contract type, and the validity period for a given combination of this
data. The table below shows an example of an employee’s status, as stored in the Ukraine-
specific payroll table, UAGRP:
Social
Head Pensio Income Statisti
Insuran
Star Unit n Fund Tax cs Contra Challen
End ce
t Groupi Groupi Groupi Groupi ct ge
Date Groupi
Date ng ng ng ng Type Group
ng
Value
Mar Mar
ch 1, ch 0001 0001 0001 0001 0001 01 01
201 20,

Social
Head Pensio Income Statisti
Insuran
Star Unit n Fund Tax cs Contra Challen
End ce
t Groupi Groupi Groupi Groupi ct ge
Date Groupi
Date ng ng ng ng Type Group
ng
Value
0 201
0
If any of the attributes that make up an employee’s status change, the system creates a new
record in the Ukraine-specific payroll table, UAGRP. The individual records in the table enable
the system to assign the correct payroll data to an employee at a given point in time.
If an employee changes to a different organizational unit during a payroll period, you can
determine how much income tax you deducted when the employee was assigned to each
organizational unit.
Activities
To split the payroll results when an employee’s status changes, the WPBP and IT Separation
in Special Situations (Ukraine) (UASPL) function uses the work place/basic pay (WPBP) splits
that the international functions create as the basis for further processing. The Ukraine-specific
function generates additional splits in the Work Place/Basic Pay (WPBP) and Internal (IT)
tables to match the changes to an employee’s status.
The Additional Master Data Processing Because of Off-Cycle (UASP) subschema determines
which wage types in the Results (RT) table apply to an employee’s status at a given point in
time by using the WPBP split that the WPBP and IT Separation in Special Situations
(Ukraine) (UASPL) function prepares. The system determines the actual amounts that apply to
an employee’s status by reading the amounts stored in the wage types that have the
corresponding WPBP splits.
More Information
System documentation for the Additional Master Data Processing Because of Off-Cycle
(UASP) subschema
System documentation for the WPBP and IT Separation in Special Situations (Ukraine)
(UASPL) function

Determination of Payroll Data After Rehiring
Process
You use this function to determine the payroll results for your employees' periods of
employment in your company, that is, in cases when employees leave your company and you
rehire the employees.
To meet legal reporting requirements in Ukraine and general payroll calculation requirements,
when you rehire employees, you must record an employee’s remuneration specific to an
employee's particular period of employment in your company. To match the remuneration in a
given payroll period to an employee’s specific period of employment, the system splits the
payroll period on the day when you rehire an employee.
The system uses the payroll period split as follows:
Purpose Description
In Ukraine, income tax is processed on a monthly basis. To ensure that

you deduct the correct amount of income tax and apply the correct limits
on income tax deductions when you run payroll each month, the system
Tax must know when an employee leaves and rejoins your company.
calculation
To enable the system to differentiate between an employee’s current
period of employment and a previous period of employment in your
company, the system uses the payroll period split.
If an employee is absent after you rehire the employee, according to

Absence Ukrainian legislation, you must take into consideration an employee’s
processing remuneration during the period of working time after you last rehire an
employee.
The legally defined reports containing payroll-related data that you file with
the authorities must show payments specific to an employee’s particular
period of employment.
Reporting Assume that an employee worked in one position until March 13, and
then left the company. You then rehired the employee on March 16.
The reports that you file with the authorities must show an employee’s
income tax and social insurance contributions separately for both
periods of employment.
For more information, see Reporting [Page 158].
Prerequisites
You have checked, and if required, adapted the Ukraine-specific personnel action for rehiring
employees, Reentry into Company (UR). You check the personnel action in Customizing for
Payroll Ukraine under Basic Settings Basic Settings – Ukraine Configure Personnel
Actions for Hiring and Leaving Events .
Activities
To split the payroll period on the day when you rehire employees, you use the Reentry into
Company (UR) personnel action.

To enable the system to process payroll period splits when you rehire employees, the
Initialization of Ukrainian Payroll (UAINI) payroll function analyzes instances when you use a
personnel action to hire employees or to terminate employees’ contracts. The function stores
the data about the leaving and hiring events in the internal table, GT_HIFI. The system uses
the data in the internal table for further processing related to an employee’s period of
employment. For more information, see the system documentation for the Initialization of
Ukrainian Payroll (UAINI) payroll function.

Future Period Processing
This function enables you to process future periods as follows:
Vacation pay or maternity leave
You can process an employee’s vacation pay or maternity leave when an employee’s
vacation/leave spans at least two payroll periods, that is, part of the vacation/leave
lies in the future.
Company-wide salary increases
You can take into consideration company-wide salary increases that apply as of a
payroll period in the future and should lead to an adjustment of the average rate value
(vacation payment adjustment) for days of vacation that fall after the date of the
salary rise. For more details, see the example below.
Prerequisites
You have made the settings in Customizing for Payroll Ukraine under Future Periods.
Features
The function for processing future periods supports the following features:
Generation of several AB records, Split by Months
This feature enables the system to divide the payroll period into subperiods according
to changes in an employee’s status.
Generation of Amounts with an Assignment to the Corresponding AB Split
This feature enables the system to assign a payment or deduction to a given month.
Calculation of Taxes for Each Deduction
This feature enables the system to have separate tax amounts for future periods; this
feature enables you to process any changes to the tax amounts that apply in the
future.
Processing of Payments that Relate to a Different Payroll Period
This feature enables you to use the new Process Amounts of Future Periods (UAFUP)
function to process payments (accruals and deductions) that relate to a different
payroll period, and generate records in the payroll cluster table for future periods,
FUP. The function determines the corresponding payroll period based on AB splits.
The Wage Type Substitution During Advance Off-Cycle Payments (UAO1) payroll
schema processes the substitution of wage types that relate to future periods to
support the correct posting to FI accounting.
Processing a Future Period that Becomes the Current Period
When a period that was calculated as a future period becomes the current period, the
system supports the following functions:
o A localized version of the Process Previous Cumulations (SETCU) function

initializes the internal Cumulated Results (CRT) table with monthly
cumulations based on the data in table FUP.

o Generates wage types that can be used for FI accounting of future period
expenses.
Example
Assume that one of your employees, Anna Petrenko, takes vacation from November 20 to
December 10. In the November payroll run, the system calculates the average amount for
vacation pay in the standard way.
Since part of the vacation falls in the following payroll period, December, the system stores
the amount for December in a separate wage type in the table for future periods, FUP.
Nevertheless, Anna receives the entire vacation pay as part of the November payroll run.
Salary Increase
Since Anna’s company increases its turnover by 15%, the Executive Board decides to
increase everyone’s salary by 1.5%, starting on December 1. This means that the vacation
pay to which Anna is entitled is higher in December than it is in November.
To determine how much additional vacation pay Anna receives for the part of her vacation
that falls in December, the system uses the amount that it saved in the table for future
periods, FUP, during the initial vacation pay calculation.
Once the system processes the additional amount of vacation pay, it transfers the additional
amount to the regular FI account.
More Information
System documentation for the Process Amounts of Future Periods (UAFUP) and the
Additional Splitting of WPBP and IT (UASPL) functions

Gross
You use this component to calculate an employee’s gross pay in line with current legislation.
Below are some examples of the payments that are included in the calculation of gross
remuneration:
Basic pay
Bonuses
Vacation allowance
Sick pay based on sickness certificates
Additional payments to make up 100% of an employee’s basic pay in previous

position
If an employer moves an employee to a different position in the company, and the

basic pay for the new position is lower than the basic pay of the previous position, the
employer must pay the employee the same amount of basic pay. This function
calculates the additional amount that must be added to the basic pay of the new
position.
Indexation payments related to the living wage (see Glossary [Page 170])
For more information, see Making of Indexation Payments [Page 66].
Features
Factors such as statutory regulations for a given profession determine whether such
payments and deductions increase or reduce the taxable income.
The system groups together individual gross values to form bases for tax or social insurance
(SI) contributions. Below are some examples of gross cumulations:
Gross tax amount
Gross social insurance amount
Assessment base for holiday bonuses, vacation allowances, or other employee

bonuses
When the system calculates an employee’s gross remuneration, it takes into consideration
the following aspects:
Area Description More Information
System documentation for

the following subschemas:
The system takes into consideration any Master Data and

payments that are specific to an employee Basic Payments
Payments
based on his or her master data and the (UAB0) subschema
basic pay that an employee receives.
Import Additional
Payments and
Deductions (UAP9)

Area Description More Information
subschema
System documentation for

The system bases an employee’s gross the Time Wage Types
Time
remuneration on the time that an employee
Management Processing (UAT1)
works in a given month.
subschema
The system evaluates the wage types that System documentation for
Wage Type the Factoring and Storage
contain any salary factoring algorithms that
Valuation
are required for a given employee. (UAF0) subschema
If an employee is sick and receives a

sickness certificate from his or her doctor, System documentation for
Absences the employee is entitled to a certain amount the Processing Absences -
of sick pay, which the system adds to the Ukraine (UAA0) subschema
employee’s gross remuneration.

Wage Types
Types .

Payments
Resources Payroll (PY) Payroll Other Countries (PY-XX) Gross Part of Payroll
Payments .

Time Management Aspects in Payroll
Resources Payroll (PY) Payroll Other Countries (PY-XX) Gross Part of Payroll Time
Management Aspects in Payroll .

Wage Type Valuation
Type Valuation .

Technical Process of Average Processing (New)
Purpose
The procedure for processing averages described in this and the following
sections refers to releases from Release 4.6B. The processing of averages has
fundamentally changed since this release.
For more information, see the Implementation Guide (IMG) for Payroll under Time
Wage Type Valuation Averages New Bases for Valuation of Averages
[External].
If you have been using the old version for processing averages up until now,
you can still continue to use this version. You do not have to convert your
system to the new version. However, the old version for processing averages
will no longer be developed. If you reconfigure, you should only use the new
version for processing averages.
Prerequisites
When setting up the new average valuation of wage types in your system, you
must perform the following activities:
Forming the Basis for Calculating Average Values
The average calculation bases are used as a basis for calculating averages. The wage
types assigned to the average calculation bases are stored in the secondary wage
types /201 to /232.
Definition of calculation rules for averages
The calculation rules are made up of the following rules and values:
Relevancy rules
Cumulation rules
Final processing rules
Comparison rules
Adjustment rules
Number of relevant previous periods
Specify if the calculated average value should be frozen
Manual values (employee- and period-specific)
Off-cycle rules
Assignment of calculation rules to wage types
This assignment defines which primary wage type should be calculated according to
which calculation rule.
For information on setting up average valuation, see the Implementation
Guide (IMG) for Payroll under Time Wage Type Valuation Averages New.

Process Flow
In the following, certain personnel calculation schemas and rules that start with
the letter X serve as an example. The X represents the international personnel
calculation schemas and rules and can be replaced with a country-specific letter.
For example, there is a German personnel calculation schema D000 for the
international personnel calculation schema X000.
The subschema XT00 (Processing of Time Data for Payroll) is accessed by
personnel calculation schema X000. The function AVERA (Average Calculation)
is called within this schema and performs the whole average calculation.
Averages are calculated in the following sequence:
...
1. Wage type selection and specification of calculation rules

You can specify which wage types you want to valuate with an average value in Payroll
Customizing under Time Wage Type Valuation Averages New Basis for Valuation
of Averages. The function AVERA selects the wage types marked in such a way and
establishes which calculation rules are assigned to these wage types.
2. The system checks the calculation rules for manual values
The system checks if a manually assigned value already exists for a wage type in the
internal table IT for every calculation rule. The system uses this value from the AMT
field as an average value. In this case, the system skips averages calculation and
continues processing with step 7.
3. The system checks the calculation rules for frozen averages
For each calculation rule, the system checks the start and finish date specified in the
internal table AVERAGE: If a frozen average already exists for the relevant wage type
and is valid for the current period, the system skips the calculation of averages and
continues processing with step 7.
4. Selection of all potentially relevant payroll results and creation of average calculation
bases
You have specified under which conditions a period should be relevant for the
calculation of averages in the IMG for Payroll using the calculation rule in the relevancy
rule. The system selects all payroll results that are, according to the relevancy rule,
relevant and checks these according to the Relevancy Test for Valuation According to
the New Principle of Averages [External].
You can also flag the current period as being relevant for the calculation of averages.
The system then accesses a preliminary value from the data previously determined for
the current period and uses this value for average calculation. The system finally
calculates the final value for the current period that is written to the results table RT at
the end of averages calculation in step 9.
5. Cumulating average calculation bases
The system cumulates the individual average calculation bases from the selected
payroll results (from the relevant periods) for each calculation rule in the internal table
MV.
In Customizing for Payroll under Time Wage Type Valuation Averages New
Create Calculation Rules for Averages [External], you can specify which of the values
from the fields NUM, RTE or AMT of the wage type are cumulated. Here, you can also
specify which sign (+/-) should be used to cumulate each value.
Create Calculation Rules for Averages, you can make the following settings in the view

Adjustment Rules for Bases for Calculating Average Values (V_T51AV_C) using
adjustment rules:
You can decide whether the system reads payroll results that are only partially in
the averages period completely, partially or not at all for averages calculation.
You can take a pay increase or an individual wage increase and, in this way,
adjust the average calculation bases to the increased payments.
You can make both positive and negative adjustments.
6. Calculation of the average value
The average value is calculated in the personnel calculation rule X018. In the standard
system, the system divides the cumulated amount calculated in step 5 for all AMT fields
by the cumulated amount from all NUM fields of the average calculation bases. You
can also specify your own formulas or constants in the personnel calculation rule X018.
The result of the calculation is the average value in the RTE field (rate).
Create Calculation Rules for Averages, you can create your own final processing rules
in the view Final Processing Rules for Averages (V_T51AV_E), which you can then
assign to a calculation rule.
Create Calculation Rules for Averages, you can create your own final comparison rules
in the view Comparison Rules for Averages (V_T51AV_W), which you can then assign
to a calculation rule. For example, you can compare the calculated value with a
specified value (for example, standard pay) and specify under which conditions which
value should be used as an average value.
7. Multiplying the average value with the number
The system writes the average value calculated in step 6 in the RTE field for every
calculation rule to the RTE field for all wage types that are assigned to this calculation
rule. The amount of the average value in the field AMT of the wage types is the result
of multiplying the contents of the fields RTE and NUM for each wage type.
8. Freezing the average
You may want to freeze the value obtained by calculating averages. To do so, you can
save the average value from the RTE field in the payroll results in the internal table
AVERAGE for every calculation rule. In Customizing for Payroll under Time Wage Type
Valuation Averages New Create Calculation Rules for Averages, you can specify
the period for which the average should be frozen in the view Calculation Rules for
Averages (V_T51AV_A).
9. Creating the average calculation bases for subsequent periods
The function ADDCU (Update Cumulations) checks which wage types from the results
table RT should be included in an average calculation basis. These wage types are
collected in the relevant average calculation bases and the average calculation bases
are finally written to the results table RT. This means that they are available in the
payroll results for future calculations according to the principle of averages.

Incentive Wages: Overview
Resources Payroll (PY) Payroll Other Countries (PY-XX) Gross Part of Payroll
Incentive Wages: Overview .

Partial Period Remuneration (Factoring)
Resources Payroll (PY) Payroll Other Countries (PY-XX) Gross Part of Payroll Partial
Period Remuneration (Factoring) .

Making of Indexation Payments
You use this process to adjust an employee’s basic salary in line with inflation. To ensure that
an employee’s purchasing power remains the same after inflation, you make additional
payments to employees based on the consumer price index (CPI) (see Glossary [Page
170]) that the government publishes.
To calculate the amount of the indexation payment to which an employee is entitled each
month, you base the indexation calculation on an employee’s actual earnings each month, but
only up to the amount of the living wage.
Assume that an employee earns UAH 1,000 per month and the living wage is UAH 650.
In this case, you calculate indexation payments based on the living wage of UAH 650.
Prerequisites
You have made the settings in Customizing for Payroll Ukraine under Indexation.
Process
1. The system calculates the indexation amount for an employee’s salary by multiplying
the indexation percentage (see Glossary [Page 170]) by an employee’s income.
For more information about how the system calculates the indexation amount, see
Calculation of Indexation Amounts [Page 67].
2. The system compares the indexation amount that it calculates for a given month with
an employee’s salary increase in that month.
To determine whether an employee received a salary increase, and to determine the

size of the salary increase, the Indexation - Ukraine (UAIDX) function compares an
employee’s salary in the previous month with the employee’s salary in the current
month.
For more information about how the system valuates an employee’s salary, see
Valuation of Employee Salary [Page 71].
3. Based on the result of the salary comparison, the system determines whether an
employee is entitled to an indexation payment as follows:
o If the salary increase is greater than the indexation amount, the employee is
not entitled to an indexation payment
o If the salary increase is less than the indexation amount, the employee is
entitled to an indexation payment
4. Before the system adds the calculated indexation amount to an employee's salary,
the Indexation - Ukraine (UAIDX) function limits the base for indexation payments to
the living wage.
5. The system adds the calculated indexation amount to an employee's salary.
More Information
System documentation for the Indexation - Ukraine (UAIDX) function
Personal Reduction in Indexation Amounts [Page 69]

Calculation of Indexation Amounts
You use this process to calculate the indexation amount that you pay employees in a given
payroll period. To calculate the indexation amount, the system uses the consumer price
index (CPI) (see Glossary [Page 170]) that the government publishes each month and the
employee’s actual earnings up to the amount of the living wage.
Prerequisites
You have entered the following data in Customizing for Payroll Ukraine under Indexation:
The legally defined consumer price index per month
The legally defined threshold for calculating indexation amounts
Process
1. The Indexation - Ukraine (UAIDX) function determines the base period (see Glossary
[Page 170]) for calculating indexation payments.
2. In the base period, the Indexation - Ukraine (UAIDX) function sets the cumulated CPI
(see Glossary [Page 170]) to zero.
3. Starting in the base period, the Indexation - Ukraine (UAIDX) function cumulates the
part of the CPI that exceeds 100%. For more information, see the example below.
4. When the cumulated CPI exceeds the legally defined percentage that you enter in the
Customizing activity Enter Threshold for Indexation, the Indexation - Ukraine (UAIDX)
function calculates indexation payments as follows:
1. Increases the indexation percentage by the value by which the cumulated

CPI exceeds 100%
2. Starting in the month after the cumulated CPI exceeds the legally defined
threshold, cumulates the value of the CPI that exceeds 100%
3. Multiplies the part of an employee’s salary on which indexation can be

calculated (up to a maximum of the living wage) by the indexation percentage
Example
Assume the following points:
An employee earns UAH 500 each month and the living wage is UAH 550.
Since the employee earns less than the living wage, you calculate indexation
payments for the employee based on his or her salary of UAH 500.
The legally defined threshold for calculating indexation amounts that you enter in the
Customizing activity Enter Threshold for Indexation is 101%.
The indexation percentage is zero and the cumulation of the CPI starts in May.
The table below contains the monthly CPI that the government publishes from May through
August and the indexation calculations that the system carries out:

CPI
Month Cumulated CPI (%) Indexation Percentage Indexation Amount
(%)
May 101.6 101.6 n/a n/a
June 100.3 100.9 n/a n/a
July 100.0 100.9 n/a n/a
August 100.5 101.4 1.4 UAH 500 x 1.4%
As the table above shows, the cumulated CPI exceeds the legally defined limit of 101% in
August. In line with legal requirements, the Indexation - Ukraine (UAIDX) function calculates
indexation payments starting in August. The amount by which the cumulated CPI exceeds
100% becomes the indexation percentage (1.4%) in August. To calculate the indexation
amount that the employee receives in August, the Indexation - Ukraine (UAIDX) function
multiples the employee’s salary (UAH 500) by the indexation percentage (1.4).
The system resets the cumulated CPI in September and starts to cumulate the CPI again.
The indexation percentage that the Indexation - Ukraine (UAIDX) function calculated in
August applies to all indexation payments until the cumulated CPI next exceeds the legally
defined limit of 101%, as shown in the table below:
CPI Cumulated CPI Indexation Indexation

Month
(%) (%) Percentage Amount
September 100.3 100.3 1.4 UAH 500 x 1.4%
October 100.2 100.5 1.4 UAH 500 x 1.4%
November 100.8 101.3 2.7 (1.4 + 1.3) UAH 500 x 2.7%
As the table above shows, the cumulated CPI next exceeds the legally defined limit of 101%
in November. The Indexation - Ukraine (UAIDX) function calculates the indexation percentage
that applies from November by adding the percentage (1.3%) by which the cumulated CPI
exceeds 100% to the indexation percentage (1.4%) that applied from September.

Personal Reduction in Indexation Amounts
You use this function to reduce the indexation amounts that individual employees receive by
reducing the base amount for calculating indexation amounts. You can use this function in the
following cases:
An employee has more than one job
If an employee receives an indexation payment for his or her main job, legislation
stipulates that when an employee’s other employers calculate indexation amounts for
the employee, they must deduct the employee's indexed income (see Glossary
[Page 170]) from the living wage (see Glossary [Page 170]). For more information,
see the example below.
An employee is absent or resigns
For example, in your company, you reduce the base amount for calculating
indexation amounts when employees hand in their notice.
Prerequisites
You have set up the model wage type that you use to reduce the base amount for calculating
indexation amounts by making the following settings:
You have specified the Salary Indexation (/113) wage type as the wage type in
which the system cumulates the part of an employee’s income for which indexation
amounts have already been calculated.
You make this setting in Customizing for Payroll Ukraine under Indexation Set
Up Wage Types to Reduce Base for Indexation Payments .
You have entered the model wage type that contains an employee’s income on which
indexation amounts have already been calculated in the Additional Payments (0015)
infotype.
The model wage type is the source for the Salary Indexation (/113) wage type.
Activities
If you want to reduce the base amount for calculating indexation amounts, you enter a special
model wage type, which you set up in Customizing (see Prerequisites), in the Additional
Payments (0015) infotype.
The special model wage type stores the employee’s indexed income (see Glossary [Page
170]) or another amount by which you want to reduce the base amount for calculating the
indexation amount. The system cumulates the amount from the special wage type in the
Salary Indexation (/113) wage type and processes this wage type during the indexation
calculation.
During the payroll run, the Indexation - Ukraine (UAIDX) function reduces the amount on
which it is possible to calculate indexation payments by the amount stored in the Salary
Indexation (/113) wage type.
Example
Assume that one of your employees, Andrij Barnik, has two employment contracts. During the
week, Andrij works as an office clerk in your company’s headquarters in Kiev, and on the
weekend, he works as a waiter for a large restaurant chain. Andrij earns UAH 400 as an office

clerk and UAH 150 as a waiter. As such, you are Andrij’s main employer. Assume that the
current living wage is UAH 453.
According to legislation, since you are Andrij’s main employer, you calculate the indexation
amount to which Andrij is entitled on the basis of the salary that you pay him (UAH 400).
Andrij informs his other employer, the restaurant chain, that you made an indexation payment
to him on the basis of UAH 400.
The restaurant chain saves the amount of Andrij’s earnings on which you calculated the
indexation amount in a special wage type in the Additional Payments (0015) infotype. When
the restaurant chain calculates the indexation amount for Andrij, it uses the difference
between the indexed income (see Glossary [Page 170]) (UAH 400) and the living wage
(UAH 453) as the basis. As such, in Andrij’s job as a waiter, he is entitled to an indexation
payment based on UAH 53.
More Information
System documentation for the Indexation - Ukraine (UAIDX) function

Valuation of Employee Salary
To valuate an employee's salary in the current payroll period, you can use one of the
following methods:
Indirect valuation
You can set up evaluation models to calculate the employee's salary based on the
model wage types in the Basic Payments (0008) infotype.
A constant
You can use any amount, for example, the living wage, as the basis for calculating an
employee's salary increase. The system regards the amount as the employee's
salary in the current payroll period when it calculates an employee's salary increase.
You determine how the system valuates an employee’s salary in the current month in
Customizing for Payroll Ukraine under Indexation Configure Wage Types to Evaluate
Salary Increase .
If an hourly wage earner gets a monthly benefit, you also have to define the relevant wage
type in this Customizing activity to ensure that the system considers this sum as a monthly
wage instead of an hourly rate.
Example
Salary Increase of an Hourly Wage Earner
Your employee, Vasyl Petrenko, has been working as an hourly wage earner as of January 1,
2011. On June 15, 2011, Vasyl Petrenko’s hourly rate is raised and at the same time, his
average monthly working hours are increased as well:
Period Hourly Rate Average Monthly Working Hours
1 January, 2011 – 14 June, 2011 UAH 10 163
15 June, 2011 – 30 June, 2011 UAH 12 167
When the indexation amounts are calculated in June, the base salary calculated for June is
compared with the base salary calculated in June for May:
The base salary evaluated for May in June, 2011 is 10 * 167 = UAH 1,670.
The base salary evaluated for June, 2011 is 12 * 167 = UAH 2,004.
In this case, the salary increase calculated in June is UAH 2,004 – UAH 1,670 = UAH 334.
Hourly Wage Earner Changing to Salaried Employee

Your employee, Oksana Shevchenko, worked as an hourly wage earner between 1 January,
2011 and 14 June, 2011, but on 15 June, she became a salaried employee. In addition, she
got a monthly benefit of UAH 100 every month when she worked as an hourly wage earner.
Average Monthly Monthly

Period Hourly Rate/Salary
Working Hours Benefit
1 January, 2011 – 14
UAH 10 (hourly rate) 163 UAH 100
June, 2011

Average Monthly Monthly
Period Hourly Rate/Salary
Working Hours Benefit
15 June, 2011 – 30 UAH 2,000 (monthly

167 -
June, 2011 salary)
The base salary is evaluated as follows:
Base salary evaluated for May in June:
o Base salary based on hourly rate: UAH 10 * 167 = UAH 1,670
o Base salary based on monthly benefit: UAH 100
That is, the base salary evaluated for May is UAH 1,670 + UAH 100 = UAH 1,770.
Base salary evaluated for June is UAH 2,000.
In this case, the salary increase calculated for June, 2011 is UAH 2,000 – UAH 1,770 = UAH
230.

Calculation of Employee's Average Income
This function enables you to meet legal requirements in Ukraine by calculating an employee's
average income. You use an employee's average income in a given period of time as the
basis for the following calculations:
Calculation of absence pay
Minimum and maximum amounts for sick pay and maternity pay
Additional payments following an internal transfer
Prerequisites
You have defined the wage types that the system uses to determine the minimum
amount for maternity pay and the maximum amounts for certain types of absence
pay. You enter the wage types in Customizing for Payroll Ukraine under Absences
Absence Processing Sickness Limitation of Sickness Certificate Payments :
o Enter Wage Type to Determine Minimum Maternity Pay
o Enter Wage Type to Determine Maximum Absence Pay
You have defined the base amounts that the system uses to limit social insurance
payments for social tax base amounts in Customizing for Payroll Ukraine under
Absences Absence Processing Sickness Limitation of Sickness Certificate
Payments Enter Base Amount to Limit Social Insurance Payments .
You have defined the wage type that contains an employee’s income in the current
payroll period in Customizing for Payroll Ukraine under Time Wage Type Valuation
Determine Wage Type for Additional Payment in Current Period .
The system uses the wage type to calculate the difference between an employee’s
actual income in the current payroll period and the amount that the employee’s
income in previous payroll periods.
Features
Calculation of Absence Pay
When an employee is absent, for example, due to vacation or sickness, you use the
employee's average salary before the absence to determine the daily (or hourly) absence rate
for the period of absence.
For more information, see Calculation of Sick Pay [Page 77], Calculation of Maternity Pay
[Page 84], and Calculation of Vacation Pay [Page 84].
Minimum and Maximum Limits for Sick Pay and Maternity Pay
In line with legal regulations in Ukraine, employees are not entitled to an unlimited amount of
sick pay or maternity pay. To limit these payment types, the system compares the amount
that the Evaluate Rate for Absence Pay (UAFD) personnel calculation rule calculates with the
amount that the system calculates on the basis of the legally defined base amounts for
calculating social insurance payments.
For more information, see Limitation of Absence Pay [Page 85].
In the case of maternity pay, employees are entitled to a minimum amount. To determine the
minimum amount, the system calculates the minimum daily rate for maternity pay.

For more information, see Calculation of Maternity Pay [Page 84].
Additional Payments Following an Internal Transfer

According to legislation in Ukraine, some internal transfers entitle an employee to the same
level of basic pay, even if the employee’s new job has a lower level of basic pay. In these
situations, you must make additional payments to the employee to ensure that the employee
receives the same basic pay as he or she received before the internal transfer.
For more information about how the system calculates the additional payments, see
Continuation of Average Salary Following Transfer [Page 75].

Continuation of Average Salary Following Transfer
This function enables you to meet legal requirements by making additional payments to
employees who are transferred to a position within your company that pays a lower salary.
According to Ukrainian legislation, some internal transfers, for example, due to health
reasons, entitle an employee to same level of pay after an internal transfer as the pay that
they received before the internal transfer.
Prerequisites
You have defined the wage type that contains an employee’s income in the current payroll
period in Customizing for Payroll Ukraine under Time Wage Type Valuation Define Link
Between Actual Income and Calculated Average .
Features
To make the required additional payment to employees, the End Processing of Averages –
Ukraine (UAAM) personnel calculation rule determines the difference between the calculated
average rate for the employee in the two payroll periods before the transfer and the
employee's income in the current payroll period.
If the employee's income in the current period is less than the employee's average income,
the personnel calculation rule adds the difference between the two amounts to the
employee's salary in the current payroll period.
Example
Assume that your employee, Arina Karmazin, operates heavy machinery in your Kiev plant.
When Arina becomes pregnant, she is no longer able to operate the machinery. You transfer
Arina to your sales office, where she takes orders over the phone. Arina works in this position,
which pays less than her job as a machine operator, until she goes on maternity leave.
According to legislation, in this situation, Arina is entitled to the same salary that she received
as a machine operator.

Absence Processing
This function enables you to handle absences in payroll in line with Ukrainian legislation, such
as absences caused by sickness, maternity leave or vacation. You use the Ukraine-specific
functions in addition to the standard functions for absences. For more information about the
standard functions for absences, see SAP Library for SAP ERP Central Component on SAP
Help Portal at http://help.sap.com SAP ERP SAP ERP Central Component Human
Resources Payroll (PY) Payroll Other Countries (PY-XX) Gross Part of Payroll Time
Management Aspects in Payroll Absences .
The amount that employees receive during periods of absence (both sickness and vacation)
depends on the average amount that they receive during a specific period of time, for
example, during the last 6 months.
In the case of sickness payments, the employee's social insurance group also forms part of
the calculation to determine the level of sick pay.
For more information, see Calculation of Sick Pay [Page 77], Calculation of Maternity Pay
[Page 82], and Calculation of Vacation Pay [Page 84].
Integration
You have made the settings for absence processing in Customizing for Payroll Ukraine under
Absences.

Calculation of Sick Pay
This function enables you to determine the amount of pay an employee receives when he or
she is unable to work because of sickness.
The system takes the following factors into consideration to determine the amount of sick pay
that an employee receives:
Level of seniority
Social insurance group and social insurance group modifier
Absence type
Average income
Prerequisites
You have made the settings in Customizing for Payroll Ukraine under Absences Absence
Processing Sick Leave and Maternity Leave .
Activities
For each paid absence, the Calculation of Social Insurance Allowances for Ukraine (UASI0)
function determines the employee's seniority using a particular calculation process. If you do
not enter a seniority calculation process in the Calculation of Social Insurance Allowances for
Ukraine (UASI0) function, the system uses calculation process specified in Customizing for
Payroll Ukraine under Absences Absence Processing Sick Leave and Maternity Leave
Determine Calculation Method for Social Insurance Seniority .
Using the Social Insurance Group

The system uses the Social Insurance Group (36SI0) feature to determine the employee's
social insurance group. If a record exists for the employee in the Additional Social Insurance
Data (0292) infotype, the function uses the social insurance group and modifier from this
infotype. Based on the settings in Customizing for Payroll Ukraine under Absences
Absence Processing Sick Leave and Maternity Leave Check Conversion of Social
Insurance Groups , the function determines the employee's social insurance group.
Calculating Sick Pay Using an Employee's Average Income

To determine the sick pay that an employee receives, the system takes into account an
employee's average income, including bonuses and any wage increases. The Calculation of
Averages for Ukraine (UAAVE) function determines an employee's average income, which the
Calculation of Social Insurance Allowances for Ukraine (UASI0) function uses to determine
the actual amount that an employee can receive. For more information, see the online
documentation for the Calculation of Averages for Ukraine (UAAVE) function. You can,
however, adjust the final rate of an employee's sick pay based on a combination of the social
insurance group and absence type. You determine this rate in Payroll Ukraine under
Absences Absence Processing Sick Leave and Maternity Leave Determine Level of
Social Insurance Payments During Absence .
An employee who has worked for less than five years becomes sick. You decide that the
employee receives 60% of the rate that the Calculation of Averages for Ukraine (UAAVE)
function) calculates.

Another employee who has worked for more than 8 years becomes sick. You decide that
the employee receives 100% of the rate that the Calculation of Averages for Ukraine
(UAAVE) function) calculates.
Linking Periods of Absence

According to Ukrainian legislation, in the case of some absences, you must use the same sick
pay rate for absences that lie in different payroll periods. To use the same rate, you link
together two absences, which means that the rate from one absence also applies to another
absence.
For more information, see Example: Linking Periods of Absence [Page 80].

Calculation of Sick Pay for New Employees
You use this function to calculate the sick pay that employees receive when they are sick on
the first day of employment in your company. If employees are sick on the first day of
employment, there are no payroll results to determine the average salary for sick pay. In
these cases, Ukrainian legislation stipulates that you use the employee's salary in the Basic
Pay (0008) infotype to determine sick pay.
Prerequisites
You have made the settings in Customizing for Payroll Ukraine under Absences Absence
Processing Sick Leave and Maternity Leave .
Activities
To calculate the daily (or hourly) sick pay rate, the system divides the employee’s salary in
the Basic Pay (0008) infotype by the number of working days (hours) in the month for which
the employee is sick.
If the sick pay rate is greater than the maximum rate of sick pay that employees receive, the
system limits the sick pay rate to the maximum rate of sick pay. The system calculates the
maximum rate using the legally defined social insurance base that you enter in Customizing
for Payroll Ukraine under Absences Absence Processing Sick Leave and Maternity
Leave Enter Base Amounts to Limit Social Insurance Payments .
Example
Assume that one of your employees receives a salary of UAH 15 000 and works 176 hours
per month. The employee goes on sick-leave on the first working day of the month. The
system calculates the sick pay rate as follows: UAH 15 000 / 176 = UAH 85.23 (hourly rate).
The system calculates the maximum rate of sick pay using the legally defined maximum base
amount for social insurance payments that you enter in Customizing for Ukraine Absences
Absence Processing Sick Leave and Maternity Leave Enter Base Amounts to Limit
Social Insurance Payments . As the legally defined base amount is UAH 14 400, the
system calculates the maximum hourly rate for sickness payment as follows: UAH 14 400 /
176 = UAH 81.82.
Because the maximum rate of sick pay is lower than the rate that the system calculates from
the employee's salary and number of working hours, the system limits the sick pay rate to the
maximum rate of UAH 81.82.
As a final step in determining the sick pay limit for the employee, the system calculates 60%
of the defined sick pay. For more information about limiting an employee’s sick pay, see
Limitation of Absence Pay [Page 85].
As a result, the system calculates the employee's sick pay rate finally as follows: UAH 81.82 x
60% = UAH 49.09 (hourly rate).

Example: Linking Periods of Absence
An employee joins the company with a starting salary of UAH 12,000 on January 01, 2011.
His salary is increased to UAH 15,000 on April 1, 2011.
The employee takes sick leave in 2011 as follows: initially he takes sick leave from July 27 to
August 2, but because he cannot return to work on August 3, he extends his sick leave to
August 10.
When the HR clerk enters the extension in the system, she creates a second sick leave
record in the Absences (2001) infotype for the period from August 3 to August 10. Because
this period is an extension of the first sick leave period, the clerk links together the two
absence periods by entering the start date of the first period (July 27, 2011) for the second
record in the Abs. Link – Average field in the Absences (2001) infotype.
The system calculates sick leave for the period from July 27 to August 2 as follows:
1. Calculates the average for sick leave calculation by taking into account the following
data from the 6–month evaluation period before the month in which the employee's
sick leave starts:
o The lesser of the following two amounts: the employee's salary in each month
of the evaluation period and the base amount for limiting social insurance
payments.
In the first 3 months of the evaluation period, the employee's salary is less
than the base amount for limiting social insurance payments; therefore, the
system cumulates the salary amounts for the first free months: UAH 36,000
In the last 3 months of the evaluation period, the base amount is less than
the salary amount; therefore, the system cumulates the base amount of UAH
14,400 for the last three months: UAH 43,200.
The system reads the base amount from the Customizing activity in
Customizing for Payroll Ukraine under Absence Absence Processing
Sick Leave and Maternity Leave Limitation of Sickness Certificate
Payments Enter Base Amounts to Limit Social Insurance Payments
o The number of working days in the evaluation period, that is, 20 + 20 + 22 +

21 + 20 + 21 = 124
The average amount is calculated as follows: (36,000 + 43,200) / 124 = 638.71
2. Calculates the average of the base amount for social insurance payments in the
month before the sick leave starts: UAH 14,000 / 21 = 685.71
3. Uses the lesser of the two amounts, that is UAH 638.71, for further processing
4. Because the employee works for the company for less than 5 years, the system limits
the payment to 60%: UAH 638.71 x 60% = UAH 383.23
5. Because the first 5 days of the sick leave are paid by the employer, whilst the last 2
days are paid by the social insurance fund, according to the settings in Customizing
for Payroll Ukraine under Absence Absence Processing Sick Leave and
Maternity Leave Determine Level of Social Insurance Payments During Absence
, the system splits up the calculated amount as follows:
o 3 x UAH 383.28 = UAH 1,149.69 paid by the employer
o 2 x UAH 383.23 = UAH 766.46 paid by the social insurance fund

Because the sick leave period from August 3 to August 10 is linked to the period from July 27
to August 2, the system calculates sick pay as follows:
Uses the rate from the previous period to calculate sick pay for this period
Because the first 5 days of the previous period are paid by the employer the full
amount of sick pay for this period is paid by the social insurance fund

Calculation of Maternity Pay
This function enables you to determine how much an employee receives when she goes on
maternity leave.
To determine the maternity pay that an employee receives, the system takes into account the
following:
The employee's average income including bonuses and wage increases
The minimum daily rate for maternity pay
The base amount to limit social insurance payments
The average number of calendar days per month
Activities
The system calculates maternity pay as follows:
Calculation of Minimum Amount for Maternity Pay

In Ukraine, employees are entitled to a minimum amount of maternity pay, which is based on
the minimum wage. The system uses the Evaluate Rate for Absence Pay (UAFD) personnel
calculation rule to determine the minimum daily rate for maternity pay by dividing the
minimum wage that you enter in Customizing for Payroll Ukraine under Basic Settings
Basic Settings – Ukraine Enter Minimum Wage by one of the following:
The number of calendar days in the month in which the employee’s maternity leave
starts
The average number of calendar days per month that you enter as the value of the
KALTM constant in Customizing for Payroll Ukraine under Absences Absence
Processing Enter Average Number of Calendar Days per Month .
You determine which number the system uses in Customizing for Payroll Ukraine under
Absences Absence Processing Sickness Limitation of Sickness Certificate Payments
Enter Wage Type to Determine Minimum Maternity Pay .
For more information, see the documentation for the Evaluate Rate for Absence Pay (UAFD)
personnel calculation rule.
Calculation of Average Rate for Maternity Payment

The system uses the Calculation of Averages for Ukraine (UAAVE) function to calculate the
average rate for maternity payment by dividing the salary in the 6 months preceding the
month in which the employee's maternity leave starts by the number of calendar days in the
same period.
For more information, see the system documentation for the Calculation of Averages for
Ukraine (UAAVE) function.
Limitation of Maternity Pay

The system uses the Calculation of Averages – Ukraine (UAAVE) function to determine the
maximum daily rate for an employee's maternity pay based on the last month in the
evaluation period. The function determines maximum daily rate by dividing the maximum
base amount that you enter in Customizing for Payroll Ukraine under Absences Absence
Processing Sick Leave and Maternity Leave Limitation of Sickness Certificate Payments

Enter Base Amounts to Limit Social Insurance Payments by the number of calendar days
as follows:
The number of calendar days in the month in which the employee’s maternity leave
starts
The average number of calendar days per month that you enter as the value of the
KALTM constant in Customizing for Payroll Ukraine under Absences Absence
Processing Enter Average Number of Calendar Days per Month .
You determine which number the system uses in Customizing for Payroll Ukraine under
Absences Absence Processing Sickness Limitation of Sickness Certificate Payments
Enter Wage Type to Determine Maximum Absence Pay .
For more information, see Limitation of Absence Pay [Page 85].
Determination of Daily Rate for Maternity Pay

The system uses the End Processing of Averages – Ukraine (UAAM) personnel calculation
rule to determine the actual daily rate to calculate maternity pay. The system multiplies this
rate by the number of days in the employee's maternity leave.

Calculation of Vacation Pay
This function enables you to determine how much an employee receives when he or she
takes vacation. The function also takes into consideration changes to an employee's pay
during a period of vacation.
The average amount that an employee earns during the evaluation period forms the basis for
vacation pay. The average earnings that the system takes into consideration comprise the
following parts:
Basic pay
Bonuses
Company-wide salary increases
Prerequisites
You have set up wage types for vacation processing in Customizing for Payroll Ukraine under
Absences Absence Processing Vacation Configure Wage Types .
Activities
The system determines the absence period and then calculates the average rate that it uses
to ascertain the employee's vacation pay. To meet legal requirements, if you grant a salary
increase to all employees in your company, the system applies an adjustment factor to an
employee’s pay before the global salary increase. The Calculation of Averages for Ukraine
(UAAVE) function uses the employee’s adjusted salary as the employee’s average income
when it determines the employee’s vacation pay.
You determine which adjustment factor the system uses in Customizing for Payroll Ukraine
under Absences Absence Processing Determine Adjustments for Average Calculation
.
Example
Dmitry Bondarenko joins your company on January 1, 2011 with a starting salary of UAH
10,000. Due to a global salary rise in your company on June 1, 2011, his salary is increased
to UAH 12,000.
Dmitry decides to take vacation August 3–10, 2011.
To calculate an employee's vacation pay, you determine his or her average income for the 12
months preceding the month in which his vacation starts. However, because Dmitry has not
worked for your company for 12 months, you determine his average income based on the
salary that he earned in the 7 months from January to July 2011 as follows:
Cumulated salary amount = 12.000 x 7 = 84,000
Number of calendar days without holidays (from January to July) = 29 + 28 + 30 + 30

+ 28 + 29 + 31 = 205
Average income = UAH 84,000 / 205 = 409.76
Using his average income and the number of vacation days, you calculate Dmitry's vacation
pay as follows:
409.76 x 8.00 (calendar days) = UAH 3,278.08

Limitation of Absence Pay
To meet legal requirements in Ukraine, you limit the absence pay that employees receive
when they are absent for one of the reasons covered by the social insurance fund. For
example, when employees are sick or are on maternity leave.
To limit the amount of absence pay that employees can receive, the system uses the base
amount for calculating social insurance payments (see Glossary [Page 170]) that the
government publishes and the legally defined evaluation period that applies to a particular
kind of absence. For example, in the case of sickness, the system uses the actual number of
working days or hours in a 6-month evaluation period. The system carries out the following
steps:
1. Calculate the average daily or hourly rate that applies to the entire evaluation period
before the period of absence starts.
2. Limit the calculated daily or hourly rate for the entire evaluation period by using the
legally defined base amount for the last month in the evaluation period.
This documentation refers to the daily rate and the number of days in the evaluation
period, but if an employee receives an hourly wage, the system uses the hourly rate and
the number of hours in the evaluation period.
Prerequisites
You have entered the base amounts for calculating social insurance payments that the
government publishes in Customizing for Payroll Ukraine under Absences Absence
Processing Sickness Limitation of Sickness Certificate Payments Enter Limit for Social
Insurance Base Amount .
Activities
Calculation of Average Daily Rate Based on Entire Evaluation Period
To calculate the maximum daily rate for absence pay, the system calculates the average daily
rate based on the entire evaluation period by carrying out the following steps:
1. The Limit Average Bases for Sick Leave (UA4B) personnel calculation schema stores
the base amounts for calculating absence pay and the number of days (calendar
days for maternity leave and actual working days for sick leave) in each month in the
evaluation period in valuation basis wage types.
For example, in the case of absences resulting from sickness, the system stores the
base amount for each month in the evaluation period in the Base for Sickness (/218)
wage type and the number of days (calendar days for maternity leave and actual
working days for sick leave) in each month in the evaluation period in the
AverageBasesForIllness (/202) wage type.
The base amount for calculating absence pay is an employee’s salary, but
legislation stipulates that the base amount that you use must not exceed the
legally defined base amount for a given month. You enter the maximum base
amount in Customizing for Payroll Ukraine under Absences Absence
Processing Sickness Limitation of Sickness Certificate Payments Enter
Limit for Social Insurance Base Amount . If an employee’s salary exceeds the

maximum base amount for calculating absence pay, the Limit Average Bases for
Sick Leave (UA4B) personnel calculation schema stores the legally defined base
amount instead of the employee’s salary.
2. The Calculation of Averages – Ukraine (UAAVE) function determines the average

daily rate for the entire evaluation period as follows:
1. Divides the sum of the base amounts that the system stores for each month
in the evaluation period by the sum of days (calendar days for maternity
leave and working days for sick leave) in the entire evaluation period.
2. Stores the result of the calculation in a model wage type for the type of
absence in question, for example, in the case of sickness, in the Sick Pay (SI
Fund, Days) (M421) wage type.
3. The Calculation of Averages – Ukraine (UAAVE) function determines the maximum

daily rate for an employee’s period of absence by calculating the maximum daily rate
based on the last month in the evaluation period. To do this, the system carries out
the following steps:
1. Divides the maximum base amount (see the Customizing activity Enter Limit
for Social Insurance Base Amount) for calculating absence pay that applies
to the last month in the evaluation period by the number of days (calendar
days for maternity leave and planned working days for sick leave) in that
month.
2. Stores the result in a limits wage type for the type of absence in question, for
example, in the case of sickness, in the Sickness Certificate Limit (Days)
(/0S2) wage type.
The Calculation of Averages – Ukraine (UAAVE) function outputs the following wage types for
further processing in the End Processing of Averages – Ukraine (UAAM) personnel calculation
rule:
A wage type that contains the daily rate for absence pay based on the employee’s
pay or based on the maximum permitted base amounts for the entire evaluation
period. For example, in the case of sickness, in the Sick Pay (SI Fund, Days) (M421)
wage type.
A limits wage type that contains the maximum permitted daily rate, for example, the
Sickness Certificate Limit (Days) (/0S2) wage type
Limitation of Absence Pay Based on Last Month in Evaluation Period

In a final step, the End Processing of Averages – Ukraine (UAAM) personnel calculation rule
limits the daily rate for absence pay by comparing the wage types that the Calculation of
Averages – Ukraine (UAAVE) function prepares. If the daily rate that the Calculation of
Averages – Ukraine (UAAVE) function prepares exceeds the amount in the limits wage type,
the system uses the amount in the limits wage type for the employee’s daily absence pay.
More Information
System documentation for the following objects:
Calculation of Averages – Ukraine (UAAVE) function
Limit Average Bases for Sick Leave (UA4B) personnel calculation schema
End Processing of Averages – Ukraine (UAAM) personnel calculation rule
Example: Limitation of Sick Pay [Page 87]

Example: Limitation of Sick Pay
Assume that one of your employees is sick from December 10 through December 15.
According to legislation, the evaluation period for calculating sick pay is 6 months, that is,
from June through November.
To determine the average daily rate in the evaluation period, the system stores the base
amounts for calculating sick pay and the actual number of working days in each month from
June through November in valuation basis wage types. If the employee’s salary exceeds the
legally defined maximum base amount for calculating social insurance payments in a given
month, the system stores the legally defined maximum base amount in the valuation basis
wage type for the month in question. The table below shows the amounts for June through
November:
Monthly Salary Legally Base Amount Actual

(Base Amount for Defined Stored in Number of
Month
Social Insurance Maximum Valuation Basis Working
Payments) Base Amount Wage Type Days
June UAH 4,500 UAH 4,800 UAH 4,500 22
July UAH 4,500 UAH 4,800 UAH 4,500 22
August UAH 5,000 UAH 4,800 UAH 4,800 15
September UAH 5,500 UAH 4,800 UAH 4,800 17
October UAH 4,500 UAH 4,500 UAH 4,500 21
November UAH 6,500 UAH 4,500 UAH 4,500 21
Totals n/a n/a UAH 27,900 118
The system cumulates the base amounts that apply to the employee from June through
November and divides the result by the total number of working days from June through
November. The result of this calculation (UAH 27,600 / 118 days) is the average daily rate for
the entire evaluation period: The average daily rate is UAH 234 (UAH 233.9).
In a final step, the system determines the maximum daily rate to which the employee is
entitled by comparing the average rate for the evaluation period with the daily rate for the last
month in the evaluation period (November). Since the employee’s November salary (UAH
6,500) is greater than the legally defined maximum base amount (UAH 4,800) in November,
the system divides the legally defined maximum base amount by the actual number of
working days (21) in November. The system stores the resulting maximum daily rate (UAH
214) (UAH 214.29) in the Sickness Certificate Limit (Days) (/0S2) limits wage type.
Since the calculated daily rate (UAH 234) for the entire evaluation period exceeds the
maximum daily rate for November (UAH 214), the daily rate that the employee receives for
the period of sickness is UAH 214.

Net
You use this component to calculate an employee’s net pay in line with contractual
requirements. Net pay is the amount paid to employees after the deduction of tax and social
insurance contributions from gross remuneration.

Tax Classes
To enable the system to calculate an employee’s tax deductions and social insurance
contributions in line with Ukrainian legislation, the system uses tax classes (see Glossary
[Page 170]) that are grouped in tax schemas (see Glossary [Page 170]). The system uses a
tax schema based on an employee’s data, for example, based on his or her tax status in
Ukraine, or the employee group and subgroup to which an employee is assigned.
You determine which tax classes a tax schema comprises in Customizing for Payroll
Ukraine under Tax and Social Insurance Payments Assign Tax Classes to Tax
Schema .
Structure
The standard system contains tax schemas comprising tax classes that the system processes
during the payroll run. The tax schemas in the standard system are listed in the following
table:
Description Tax Schema
Default Tax Schema 36
Employees with Civil Contracts 37
Disabled Employees 38

Determination of Tax Classes
You use this process to establish which tax classes are relevant for calculating income tax
deductions and social insurance contributions for employees. The tax classes that are
relevant for an employee determine the following:
Income tax that is deducted from an employee’s gross salary
Social insurance contributions that an employer makes for its employees
Tax privileges that reduce income tax deductions and social insurance contributions
In the system, the Tax Calculation – Ukraine (UATAX) function determines the tax classes that
apply to an employee.
Prerequisites
You have made settings for tax classes and tax schemas as described in Customizing for
Payroll Ukraine under Tax and Social Insurance Payments Tax Calculation Overview .
Process
1. Determine the basic tax schema (see Glossary [Page 170]) that applies to an
employee by reading the employee’s master data, including personnel area, subarea,
and personal information (for example, whether an employee has signed a civil
contract).
You can find the template basic tax schemas in Tax Classes [Page 89].
2. Determine the additional tax classes, taking an employee's other information into
consideration. For example, employees with different labor contracts are entitled to
different tax classes.
3. Comply a list of all relevant tax classes that apply to a given employee.
More Information
Online documentation for the Tax Calculation — Ukraine (UATAX) function
Income Tax Calculation [Page 92]
Social Insurance Calculation [Page 102]

Income Tax
You use this component to calculate and subsequently deduct the amount of income tax that
your employees pay.
You can also take into account any tax privileges that apply both to individual employees, as
well as to entire tax classes.
Features
This component contains the following sections:
Income tax calculation
Privilege processing for income tax
Income tax discrepancies

Income Tax Calculation
This function enables you to calculate the amount of income tax that an employee pays
during the payroll run. The following factors influence the amount of income tax that is
deducted from an employee's taxable income:
Basic pay
Tax privileges (see Glossary [Page 170]) for a given tax class
Tax privileges for an individual employee
Integration
If an employee is entitled to a non-monetary benefit, the employer compensates the income
tax that is due on the amount of the benefit. When the system calculates the employee's ESV
(see Glossary [Page 170]) contribution, the system increases the ESV base by the amount of
income tax that the employer compensates on the value of the benefit. For more information,
see Example: Income Tax Calculation [Page 94] and Example: Social Insurance Contribution
(ESV) [Page 104].
Prerequisites
You have made the settings described in Determination of Tax Classes [Page 90].
You have made settings specific to tax classes in Customizing for Payroll: Ukraine under
Tax and Social Insurance Payments Maintain Taxes and Social Insurance Payments .
You have defined tax privileges in Customizing for Payroll: Ukraine under Tax and Social
Insurance Payments Tax Privileges Maintain Tax Privileges .
You have set up the wage types in which you want to store income tax amounts in
Customizing for Payroll: Ukraine under Tax and Social Insurance Payments Tax
Privileges Configure Wage Types .
Features
The Tax Calculation - Ukraine (UATAX) function uses personnel calculation rules to determine
the base amount for income tax calculation, and to subsequently store the amount of income
tax in a secondary wage type.
For more information, see the online documentation for the Start Tax Calculation (UAXN)
and Final Processing for Income Tax Calculation (UAXO) personnel calculation rules.
Activities
The function calculates the amount of income tax that the system deducts from an
employee's gross salary as follows:
Stores the base amount for income tax calculation in the base wage type you enter in
the Customizing activities under Tax and Social Insurance Payments Tax
Uses the base amount for income tax calculation that is stored in the base wage type
to process any tax privileges (see Privilege Processing for Income Tax).

After applying any privileges to the base amount for income tax calculation, the
function stores the actual amount of income tax in the formed wage type you enter in
the Customizing activities under Tax and Social Insurance Payments Tax

Example: Income Tax Calculation
This example shows how the total income tax amount for an employee is calculated.
Assume Ivanov Ivan Ivanovich’s income in January 2011 consists of the following wage
types:
Wage type M004 (Monthly salary): UAH 8000
Wage type M174 (Monthly bonus): UAH 8000
The amounts for these wage types have been divided into smaller amounts in the
preprocessing run of the Tax Calculation – Ukraine (UATAX) function.
Example 1: Income Tax Calculation Using Different Priorities for the Tax
Class
Wage type M004 (Monthly salary) has a higher priority than wage type M174 (Monthly
bonus) for tax class U6 (Income Tax Calculation). Wage type M004 (Monthly salary) is
processed in the first place with priority 10 and wage type M174 (Monthly bonus) is
processed in the second place with priority 20. Therefore, the income tax is calculated in a
different way, so the resulting amount differs from one wage type to the other as follows:
Wage ESV Tax on Real Tax Income

Income Tax
Type Amount Base on Tax on Total
Tax Base Rate
Link (/4T3) Amount Amount
1,161.89
R 01 1
7,057.5 254.07 6,803.43 15 1,020.51 (total
(M004)
M004)
R 01 4
942.5 0 942.5 15 141.38
(M004)
1289.63
R 02 2
1,410 50.76 1359.24 15 203.89 (total
(M174)
M174)
R 02 5
942.5 0 942.5 17 160.23
(M174)
R 02 3
5,647.5 203.31 5,444.19 17 925.51
(M174)
Total Income Tax for M004 = UAH 1,161.89
The amounts for the income tax in both wage types are different because the wage types
have different priorities for tax class U6.
The amount 9,410 is the tax base for tax scale 15%. In general, Social Insurance Contribution
(ESV) deductions are calculated with percentage 3,6%.
9,410*3.6% = 338.76 (ESV exemption for income tax calculation).
9,410-338.76 = 9,071.24 (real income tax base). In this example, this amount (9,071.24) is
not met because part of amount 942.50 (of wage type M004 with highest priority) was not
included in the ESV calculation.

Example 2: Income Tax Calculation Using the Same Priority for the Tax
Class
Wage type M004 (Monthly salary) and wage type M174 (Monthly bonus) are calculated with
the same priority, 10, for tax class U6 (Income Tax Calculation).
Wage ESV Tax on Real Tax Income

Income Tax
Type Amount Base on Tax on Total
Tax Base Rate
Link (/4T3) Amount Amount
1,226.09
R 01 1
4,705 169.38 4,535.62 15 680.34 (total
(M004)
M004)
1,226.11
R 02 3
1,410 50.76 1,359.24 15 203.89 (total
(M174)
M174)
R 02 4
3,295 118.62 3,176.38 15 476.46
(M174)
R 01 6
942.5 0 942.5 17 160.23
(M004)
R 01 2
52,352.5 84.69 2,267.81 17 385.52
(M004)
R 02 7
942.5 0 942.5 17 160.23
(M174)
R 02 5
2,352.5 84.69 2,267.81 17 385.53
(M174)
The amounts for the income tax in both wage types are the same because the wage types
have the same priority for tax class U6.
In opposition to the income tax calculation in the first example, in this example the real
income tax base amount 9,071.24 (4,535.62 + 1,359.24 + 3,176.38) is met, because each
income tax base (column 2 in the table) taxed with 15% (column 5 in the table) has the
corresponding ESV tax amount calculated (column 3 in the table).
The income tax calculation of the examples above (examples 1 and 2) has been done
based on the social insurance contribution (ESV) calculated using the same priority for
the tax class (see Example 2: Social Insurance Contribution Deduction Using the Same
Priority for the Tax Class of Example: Social Insurance Contribution (ESV) [Page 104].

Privilege Processing for Income Tax
This function enables you to handle privileges that apply to the base amount for income tax
calculation. When you apply privileges, the system reduces the amount on which the income
tax calculation is based, thereby reducing the amount of income tax that the system deducts
from an employee’s salary. The function processes privileges as follows:
Determines which privileges apply to a given employee
Calculates the amount of a given privilege
Subtracts the amount of the privilege from the employee’s taxable income
Prerequisites
You have entered tax privileges and defined how the system calculates privileges in
Customizing for Payroll: Ukraine under Tax and Social Insurance Payments Tax
Privileges Maintain Tax Privileges .
You have assigned tax privileges to a given tax class in Customizing for Payroll: Ukraine
under Tax and Social Insurance Payments Maintain Taxes and Social Insurance
Payments .
You have assigned personal tax privileges in the Tax Privileges (0299) infotype.
Features
Based on the employee’s taxable income, the Tax Calculation - Ukraine (UATAX) function
uses Ukraine-specific personnel calculation rules to determine which privileges apply to an
employee, before determining the actual amount of the privileges.
Non-Personal Privileges
As part of the privilege calculation, the function takes into consideration the limit on privileges
that you set in the Customizing activity Maintain Tax Privileges (see the Prerequisites section
above).
The personnel calculation rules within the Tax Calculation - Ukraine (UATAX) function store
the amounts of the privileges in wage types for further processing.
Personal Privileges
The personnel calculation rules read the tax privileges you enter in the Tax Privileges (0299)
infotype and as a result, reduce the base amount on which an employee’s income tax is
calculated.
The Tax Calculation - Ukraine (UATAX) function uses personnel calculation rules to reduce
the amount on which the income tax calculation is based by the amount of the privilege. For
example, the Decrease Income Tax Base on Value of Previous Tax (UA74) personnel
calculation rule reduces the value of income tax base by removing the amount of ESV (see
Glossary [Page 170]) deductions that have already been calculated, and the Apply Total of All
Social Privileges to Income Tax (UA76) personnel calculation rule deducts the amount of a
personal privilege from the income tax base.
More Information
Tax Privileges Infotype (0299) [Page 29]

Processing of Income Tax Discrepancies
This function enables you to reconcile income tax discrepancies (see Glossary [Page 170]).
According to Ukrainian legislation, you can reconcile tax discrepancies in the month in which
they occur or you can carry them over to the next month. However, you must reconcile
discrepancies in the following cases:
Employee leaves the company and the current month is his or her last working month
Employee has submitted an application for changing his or her tax privilege (see
Glossary [Page 170]) in the current month
You calculate income tax for the final payroll period of the year
Assume you raise an employee's salary from UAH 1000 to UAH 1500 in February
retroactively from January. If you want to carry over income tax discrepancies from one
month to the next, you can calculate income tax on his salary when you do retroactive
accounting for January, as follows:
By applying tax according to the regulations effective in January and February

respectively, that is, by calculating tax on the increased salary amount of UAH
1500 for both months. This means that you calculate the tax as if the employee
had earned the increased salary in January.
By applying tax in February on the increased salary for February (UAH 1500) plus
the amount of the salary increase from January (UAH 500) in accordance with the
regulations in February. In this case, the tax amount for January does not
change.
Income tax discrepancy is the difference between the tax amount calculated using the
two methods. Because you reconcile discrepancies only if the above mentioned
conditions are met, the discrepancy for January is transferred to February where it is
cumulated with the discrepancy amount for February. This amount is reconciled, for
example, if your employee leaves the company.
Prerequisites
To enable the system to determine income tax discrepancy for a given payroll period, you
have set up the system as follows:
To calculate income tax using both tax classes in one of the following pairs of tax
classes, by making the corresponding settings in Customizing for Payroll Ukraine
under Tax and Social Insurance Payments Maintain Taxes and Social Insurance
Payments :
o Income Tax Calculation (U6) and Recalculation of Income Tax (U7)
o Income Tax Calculation for Miners (U2) and Income Tax Recalculation for
Miners (U3)
o Calculation of Income Tax without Subtraction (U4) and Recalculation of

Income Tax without Subtraction (U5)
To use the income tax recalculation process in Customizing for Payroll Ukraine under
Tax and Social Insurance Payments Income Tax Recalculation Determine
Income Tax Recalculation (With/Without Recalculation)

Activities
To determine income tax discrepancies, the system uses the Recalculation of Income Tax
(UAIT) schema. The schema determines the income tax discrepancy in the month that it
processes by taking into account any discrepancies from the previous month. In January, the
schema also checks for any income tax discrepancy from the previous year.
To reconcile income tax discrepancies, the schema checks the above mentioned conditions,
and proceeds as follows:
If any one of the conditions are met, the schema reconciles the income tax
discrepancies in the given month
If neither of the above conditions is met, the system stores the income tax
discrepancies for use in the next month.
For more information, see the system documentation for the Recalculation of Income Tax
(UAIT) schema.
More Information
Example: Processing of Income Tax Discrepancies [Page 99]

Example: Processing of Income Tax Discrepancies
One of your employees, Mikhail Komarov, earns UAH 1000 monthly and is entitled to a
personal income tax privilege of UAH 470.50. He is entitled to the tax privilege as long as his
salary does not exceed the threshold amount of UAH 1320 that you enter in Customizing for
Payroll Ukraine under Tax and Social Insurance Payments Tax Privileges Define
Constant for Threshold on Income Tax Social Privilege . The income tax rate on his salary
is 15%.
In January 2011, income tax on his salary is calculated as follows:
ESV (see Glossary [Page 170]) = 1000 (ESV base) x 3.6% (ESV rate) = UAH 36
Income tax = {(UAH 1000 (income tax base) – UAH 36 (ESV) – 470.50 (income tax
privilege))} x 15% (income tax rate) = –74.03
The income tax amount is negative because it is deducted from the employee's salary:
UAH 1000 (gross salary) – 74.03 (income tax) = 889.97 (net salary)
In February, Mikhail's salary is raised from UAH 1000 to UAH 1500 retroactively from
January. Because of this retroactive change, a discrepancy occurs between the tax that you
calculate on Mikhail's income using the following two methods:
Method 1: You calculate income tax on the amount of salary increase (UAH 500) in
February. That is, you increase the income tax base for February by the amount of
the salary increase for January, and the income tax amount for January does not
change.
Method 2: You calculate income tax for both months based on the increased salary of
UAH 1500. That is, you calculate income tax as if Mikhail earned the increased salary
in January.
You calculate income tax on Mikhail's salary as follows:
Retroactive tax calculation in February for January
Tax according to method 1
No change to the income tax amount = UAH –74.03
{UAH 1500 (original salary + increase) – UAH 36 (ESV)} x 15% (income tax rate) = –
219.60
Social privilege is not applied because Mikhail's salary exceeds the UAH 1320
threshold amount
Income Tax Discrepancy: –74.03 –(–219.60) = 145.57
The discrepancy amount is positive because it is not reconciled (deducted from the
employee's salary) in the given month, but is transferred to the next month.
Tax calculation for February
Income tax base: UAH 1500 (original salary + increase) + 500 (salary increase from
January) = UAH 2000

ESV = UAH 2000 (ESV base) x 3.6% (ESV rate) = 72
{2000 (income tax base) – UAH 72 (ESV)} x 15 % (income tax rate) = –289.20
Social privilege is not applied because Mikhail's salary exceeds the UAH 1320
privilege limit
ESV = UAH 1500 (ESV base) x 3.6% (ESV rate) = 54
{UAH 1500 (income tax base) – UAH 54 (ESV)} x 15 % (income tax rate) = –216.90
Discrepancy: UAH –289.20 – (–UAH 216.90) = UAH –72.30
Discrepancy from last month taken into account: UAH –72.03 + UAH 145.57 = UAH
73.27
Because Mikhail leaves the company on 28 February 2011, the discrepancy of UAH 73.27 is
deducted from his net pay.

Social Insurance
You use this component to calculate and process the ESV (see Glossary [Page 170]) for the
employees and to calculate the relevant seniority of employees.

Social Insurance Calculation
This function enables you to calculate social insurance (SI) contributions for employees. The
Ukraine SI contribution for an employee, ESV (see Glossary [Page 170]), comprises
contributions by the employee (deducted from gross income) and contributions by the
employer.
The following income types are subject to SI contribution calculation:
Salary or full-pay vacation
Additional benefits
Sickness payment
Salary for civil-contract holders
For each income type, Ukraine legislation defines the contribution percentages for both
employee and employer, along with the respective decision factors. For example, the
contribution percentage for salary or vacation varies according to the employer’s industry and
an employee’s disability status.
Prerequisites
You have made the Customizing settings described in Determination of Tax Classes [Page
90].
You have made settings specific to tax classes and privileges in Customizing for Payroll
Ukraine, under Tax and Social Insurance Payments:
Maintain Taxes and Social Insurance Payments
Maintain Tax Privileges
Privilege processing is relevant to calculation of ESV base amount only for

employees who are entitled to nonmonetary payments. For more information, see
Privilege Processing for Income Tax [Page 96].
Define Priority of Wage Types for Taxation
You have set up the wage types in which you want to store SI contributions in Customizing for
Payroll Ukraine, under Tax and Social Insurance Payments Configure Wage Types .
Features
The system calculates the SI contribution for each applicable income type separately. The
Tax Calculation - Ukraine (UATAX) function first determines the individual base amount for
each contribution. An upper limit is defined to restrict the sum of all the base amounts. If this
upper limit is exceeded, the system reduces the exceeding amount, starting from the SI base
amount with the lowest priority. The priority settings for various contributions are as follows:
Low: SI for sickness payment
Medium: SI for payment to civil-contract holders
High: SI for salary, vacations, or additional benefits

For example, an employee has the following income this month:
Salary: UAH 12000
Additional benefit: UAH 2000
Sickness payment: UAH 2000
The total income is UAH 16000, which is more than the upper limit for SI base amount, UAH
14400. The exceeding difference UAH 1600 will be deducted from income with the lowest
priority, that is sickness payment; and then only UAH 400 from sickness payment is included
as SI base amount.
Activities
In the system, the payroll function UATAX calculates social insurance contributions as follows:
1. Stores the initial base amount for SI calculation in the basis wage types that you enter
in the Customizing activity Maintain Taxes and Social Insurance Payments.
2. Determines the base amounts for calculation according to the priority settings.
3. Calculates the actual tax amounts by calling the finish processing rule that you enter
for a given tax class in the Customizing activity Maintain Taxes and Social Insurance
Payments, and stores the result in the formed wage types.
For tax classes related to SI contribution calculation, the finish processing rule is
Processing Negative and Positive Tax Amounts (UAXL). This rule uses the Additional
Splitting of WPBP and IT (UASPL) operation to store the tax class and align with the
tax scale of the above Customizing activities in the TAX table of the Ukraine-specific
cluster, UA. Data in the TAX table will be extracted for reporting purpose later, and
used as a basis for creating forms about the level and rates of social insurance
contributions.
More Information
Online documentation for payroll function: Tax Calculation – Ukraine (UATAX)
Online documentation for personnel calculation rules
Start Tax Calculation (UAXN)
Processing Negative and Positive Tax Amounts (UAXL)

Example: Social Insurance Contribution (ESV)
This example shows how the total amount for an employee´s social insurance contribution is
calculated.
Assume Ivanov Ivan Ivanovich’s income in January 2011 consists of the following wage
types:
Wage type M004 (Monthly salary): UAH 8000
Wage type M174 (Monthly bonus): UAH 8000
The amounts for these wage types have been divided into smaller amounts in the
preprocessing run of the Tax Calculation – Ukraine (UATAX) function.
Example 1: Social Insurance Contribution Deduction Using a Different

Priority for the Tax Class
Wage types M004 (Monthly salary) and M174 (Monthly bonus) have a different priority for
tax class E3 (ESV Deductions Main). Wage type M004 is calculated with priority 10 and
wage type M174 is calculated with priority 20. Therefore, the ESV (Unified Social
Contribution) deduction calculated on these wage types differs as follows:
ESV
Wage ESV Tax Total ESV ESV Tax on Total
Tax
Type Link Base (/4B3) Tax Base Amount (/4T3) Amount
Rate
R 01 1
7,057.5 7,057.5 3,6 254.07
(M004)
R 01 6 288 (total
942.5 8,000 3,6 33.93
(M004) M004)
R 02 2
1,410 9,410 3,6 50.76
(M174)
R 02 3 220.14 (total
4,705 14,115 3,6 169.38
(M174) M174)
R 02 4
942.5 15,057.5 0
(M174)
R 02 5
942.5 16,000 0
(M174)
Total ESV Amount for M004: UAH 288
Total ESV Amount for M174: UAH 220.14
The total ESV amount for both wage types is different because the wage types have a
different priority for tax class E3.
Example 2: Social Insurance Contribution Deduction Using the Same

Priority for the Tax Class
Wage types M004 (Monthly salary) and M174 (Monthly bonus) have the same priority for
tax class E3 (ESV Deductions Main). Therefore, the ESV (Unified Social Contribution)
deduction calculated on these wage types is the same:

ESV
Wage ESV Tax Total ESV ESV Tax on Total
Tax
Type Link Base (/4B3) Tax Base Amount (/4T3) Amount
Rate
R 01 1 254.07 (total
7,057.5 7,057.5 3,6 254.07
(M004) M004)
R 02 2 254.07 (total
1,410 8,467.5 3,6 50.76
(M174) M174)
R 02 3
5,647.5 14,115 3,6 203.31
(M174)
R 01 4
942.5 15,057.5 0
(M004)
R 02 5
942.5 16,000 0
(M174)
The first three records of the total ESV tax base are below the amount 14,115 (7,057.5 +
1,410 + 5,647.5 = 14,115). Up to this amount (14,115), the tax rate is 3,6%; above this
amount (record 4 (15,057.5) and record 5 (16,000), the tax rate is 0.
ESV for M004 and ESV for M174 is both UAH 254.07, because both wage types have the
same priority for tax class E3 (or the priority has not been customized for tax class E3).

Seniority Calculation
In Ukraine, the seniority of an employee determines how much social insurance payments an
employee gets in case of sicknesses. In accordance with legal requirements, seniority is
determined in months and is calculated in one of the following ways:
If the social insurance contribution (ESV) tax in the given month is equal to or more
than the minimum ESV amount, the month is included in the seniority of the
employee.
If the ESV tax in the given month is less than the minimum ESV amount, the seniority
is calculated using the following formula:
Seniority = Paid ESV Amount / Minimum ESV Amount
The minimum ESV amount is calculated based on the minimum wage amount for the given
months.
The system allows you to calculate the seniority of an employee in case the ESV tax in the
given month is less than the minimum ESV amount.
Prerequisites
You have defined the minimum wages in Customizing for Payroll Ukraine, under
Basic Settings Basic Settings – Ukraine Enter Minimum Wage .
You have defined the wage types for paid ESV bases in Customizing for Payroll
Ukraine, under Basic Settings Basic Settings – Ukraine Define Wage Types for
Paid ESV Bases .
Features
The Time Specification/Employ. Period (0552) infotype contains the percentage of the month
that is included in the seniority of an employee. This information can be added to the infotype
in one of the following ways:
You can manually enter the percentage in the Seniority Calculation (Manual) (UASM)
subtype of the infotype.
If you did not enter any values in the UASM subtype, the system can automatically
calculate the percentage and enter it in the Seniority calculation (Auto) (UAES) of the
infotype.
Activities
The system uses the Generate ESV Seniority (UASEN) function to calculate the seniority and,
if there is no manual entry in the UASM subtype, to update or create a record in the UAES
subtype of the Time Specification/Employ. Period (0552) infotype. To calculate the seniority, it
uses the ESV Seniority Calculation (UASE) personnel calculation rule.
Example
Your employee, Ivanov Ivan Ivanovich, has a monthly salary of UAH 700 and received a sick
leave payment of UAH 400 in the given month. The minimum ESV amount is UAH 1094.
In this case, the paid ESV amounts are:
For salary: UAH 285.46 (using the rate of 40.78%)

For sick leave payment: UAH 140.80 (using the rate of 35.2%)
In this case, the system calculates seniority as follows:
UAH 285.46 + UAH 140.80 / UAH 1094 = 0,389634
That is, the seniority for this period is 0,389634 month.

Garnishment Processing
This function enables you to process garnishment payments that the courts instruct your
employees to pay in line with Ukrainian legislation.
For an overview of the basic garnishment process, see SAP Help Portal at
http://help.sap.com SAP ERP SAP ERP Central Component English SAP ERP
Central Component Human Resources Payroll (PY) Payroll United States (PY-US)
Net Part of Payroll (PY-US-NT) Garnishments The Garnishment Process .
Prerequisites
You have made the Customizing settings described in the documentation for the following
infotypes and you have entered the required master data in both infotypes:
Garnishment Orders (Infotype 0295) [Page 23]
Garnishment Documents (Infotype 0296) [Page 24]
You have set up the required wage types and calculation rules for your garnishment order
types in Customizing for Payroll Ukraine under Garnishment Processing .
Features
You use the function to process the following cases:
Deduct a percentage or fixed amount from one of your employee’s salaries each
month
In the case of alimony, the period is limited. For example, you deduct 10% of your
employee’s salary until the employee’s child turns 18 years of age.
Deduct an amount from your employee’s salary
This case does not have a time limit. You deduct an amount from your employee’s
salary until the balance is zero. For example, your employee is in debt and must pay
back the balance of the debt.
A combination of the above two cases: you first deduct amounts from your
employee’s monthly salary until the balance of the garnishment order is zero. You
then deduct a percentage or amount from the employee’s salary until a particular
event occurs, such as the employee’s child turns 18 years of age.
In the above cases, you use the international Balances & Totals function to create and
process deductions of equal amounts over several periods. For more information, see
Balances & Totals [Page 110].
Overview of Garnishments
To enable accountants and master data specialists in your company to obtain an overview of
the garnishment cases that you have processed, and are still processing, in your company,
you can use the Garnishment History (HUACGARI) report. For more information, see the
report documentation in the system.
Activities
The system can process the following garnishment payments:

Deduct Percentage or Amount from Monthly Salary
To deduct an amount or percentage of the monthly salary, you create a document order with
the required order type for alimony in the Garnishment Orders (0295) infotype.
Deduct Amount from Salary until Zero Balance

The international function has been enhanced to fulfill Ukrainian requirements. Based on the
payment requirements in the garnishment document, you create two records in the
Garnishment Orders (0295) infotype: one record for arrears (order type A0) and one record
for alimony to reduce the balance of arrears (order type A2).
To meet Ukrainian requirements for garnishment, the standard functions have been enhanced
to enable you to process more than one garnishment document for the same employee. For
example, if one of your employees must pay money to two different payees, you create two
different garnishment documents. The system uses the same wage type for the total
garnishment amount in both documents, but splits the balance in the internal table, V0.
Deduct Amount until Zero Balance then Monthly Amount

To enable the system to deduct an amount until the balance reaches zero and then deduct a
percentage from the employee’s salary each month, you create the following order types in
the Garnishment Orders (0295) infotype:
Arrears (order type A0)
Alimony (order type A1)
Alimony to reduce arrears (order type A2)
The system processes the deductions for the above order types, and deducts amounts from
employees’ salaries in line with the start and end dates of the garnishment order.
When you create an order type for arrears (A0), to create only one initial balance, you
limit the record to the first month of garnishment.
Payment
The system processes the payment as part of the regular payroll run. After the payroll run,
you transfer the money to the required payee, as stipulated in the garnishment document.
More Information
Garnishment Orders (Infotype 0295) [Page 23]
Garnishment Documents (Infotype 0296) [Page 24]

Balances & Totals
Use
You use this function when you want to set up deductions so that a specified total amount is
deducted in equal installments over several periods. You can use it, for example, to easily set
up interest-free loans for your employees.
Scope of Function
To set up a deduction in the system that is valid over several payroll periods, you generally
create a record in the infotype Recurring Payments/Deductions (0014). If you want the
individual deductions to add up exactly to a specified total amount you must choose the
validity period for this infotype record so that the sum of the partial amounts corresponds to
the total amount. This procedure can not only require considerable maintenance, but is also
prone to errors if, for example, one of the following occurs:
The employee changes to another payroll area with a different payroll periodicity.
The deduction is factored because the employee has unpaid absences.
The net amount in a period is not sufficient, so the amount is only partially deducted or is
not deducted at all.
In these cases it is not established from the start how long the infotype record must be valid
for in order that the total amount can be completely deducted. You can use the balances &
totals function to ensure that the required total amount is deducted in full.
To do this you link three wage types in Customizing for Payroll under Deductions Wage
Types for Deductions With Balances and Totals.
Deduction:
You create a record for the infotype Recurring Payments/Deductions (0014). This
record contains the partial amount that is to be deducted per payroll period. The end
date of this record can extend far into the future.
Balance:
The balance wage type is the required total amount that is to be reached by the
individual deductions in the infotype Recurring Payments/Deduction (0014). You create
this wage type in the infotype Additional Payment (0015). The validity date for this
record lies in the payroll period in which the payments will start. With each deduction in
the individual periods the amount of this balance wage type is reduced during payroll.
Total:
The system creates the totals wage type during the payroll run. This wage type
contains the total amount that has already been deducted in the previous periods, this
means the total of the individual deductions in the infotype Recurring
Payments/Deductions (0014) up to the current period. You can not enter this wage
type using an infotype.
Deductions are withheld during payroll runs until the total amount has been reached. If
necessary, the deduction is reduced in the last period to the amount that is still outstanding. In
all subsequent periods nothing will be deducted, even if the record in the infotype Recurring
Payments/Deductions (0014) is still valid.
All three wage types (deduction, balance and total) are stored for each period in the RT table.
Example
A total amount of USD 250 should be deducted by USD 50 per period.. The following graphic
describes the interaction of the wage types during several periods:

Deduction (in infotype Recurring Payments/Deductions (0014): USD 50
Balance (in infotype Additional Payment (0015): USD 250
$ 50 $ 50 $ 50 $ 50 $ 50
Deduction
(IT 0014)
$ 200
$ 150
$ 100
$ 50
$0
Balance
(IT 0015)
$ 250
$ 200
$ 150
$ 100
$ 50
Total
01 02 03 04 05 Payroll Period
The record of the infotype Recurring Payments/Deductions (0014) creates a deduction in

each payroll period of USD 50. The balance wage type decreases from the starting amount of
USD 250 by USD 50 for each deduction until it has decreased to zero in period 05. The totals
wage type increases simultaneously per payroll period by USD 50 and adds up, therefore, to
USD 250 in period 05. In the subsequent periods the system does not deduct anything.
See also:
Arrears Processing for Deductions [External]
Limits for Deductions [External]

Loans
Resources Payroll (PY) Payroll Other Countries (PY-XX) Deductions Loans .

Off-Cycle Activities
You use this component to pay employees in between regular payroll runs. In Ukraine,
companies are legally obligated to pay their employees at least once every half month. The
payments are called advance off-cycle payments.
Implementation Considerations
Since the Off-Cycle component is an addition to Payroll, you must have installed the regular
Payroll component and made all the settings in Customizing for Payroll Ukraine.
Features
In addition to the functions provided by the standard Off-Cycle Workbench [External], you can
perform the following functions specific to Ukraine:
Incorporate advance off-cycle payments in regular payroll runs
Unlike the international concept of off-cycle payments, in the country version for
Ukraine, the system takes into consideration taxes and other deductions associated
with the advance off-cycle payments during the next regular payroll run (see Advance
Payment Methods [Page 117]).
Use reports to make advance off-cycle payments to large numbers of employees at

the same time (see Making Mass Advance Off-Cycle Payments [Page 137])
Use a tool to check that employees who have a master data record in the Additional
Off-Cycle Payment [Page 115] (0267) infotype are included in the desired payroll run
for advance off-cycle payments (see Completeness Check (HUAC0267) [Page 143])
Constraints
The following constraints apply to the current off-cycle functions for Ukraine:
It is not possible to calculate loans during off-cycle payroll runs.
You can release payments for future periods during regular payroll runs only.
You cannot process arrears during off-cycle payroll runs. The system imports arrears
from the last regular payroll run only.

Making Advance Off-Cycle Payments
You use this process to make advance payments to your employees in between regular
payroll runs.
Process
1. You create master data records in the Additional Off-Cycle Payment (0267) infotype.
To process the master data records required to pay individual employees, you use
the Off-Cycle Workbench, or to pay large numbers of employees, you use Ukraine-
specific reports (see Making Mass Advance Off-Cycle Payments [Page 137]).
2. You start the off-cycle payroll calculation using the Off-Cycle Workbench, or in the
case of mass payments, you call the payroll driver specific to Ukraine.
3. Based on the reason for the off-cycle payroll run that you enter in the Off-Cycle
Workbench or in the Ukraine-specific reports, the payroll driver determines the
required calculation type for the advance off-cycle payment in question (see Advance
Payment Methods [Page 117]).
4. Depending on the settings that you make with regard to deductions on final
payments, the system uses the Substitution Wage Types in Off-Cycle Payroll Run
(73) processing class to exclude deductions from the final transfer amount (see
Advance Payment Methods [Page 117]).
5. To check whether the system included all employees who are to receive an advance
off-cycle payment in the off-cycle payroll run, you can check the outcome (see
Completeness Check (HUAC0267) [Page 143]).
6. You start the regular payroll run.
o The system reduces the final payment by the advance off-cycle payment(s)
that you made since the last regular payroll run.
o The system calculates taxes and other deductions, and makes any
adjustments in line with the deductions the system calculated during off-cycle
payroll runs.
More Information
Additional Off-Cycle Payment (Infotype 0267) [Page 115]

Additional Off-Cycle Payment (Infotype 0267)
Definition
Infotype in which additional wage elements that are only made once or irregularly can be
stored for off-cycle payroll [External].
Use
The Additional Off-Cycle Payment infotype (0267) is not available in all countries.
To create additional off-cycle payments, you have the following options:
If you only want to create an additional off-cycle payment for one or a few employees,
we recommend that you use the Off-Cycle Workbench [External]. The system thereby
saves you from carrying out several steps that you must otherwise carry out manually
in the Additional Off-Cycle Payment infotype (0267).
If you want to create additional off-cycle payments for many employees, we
recommend that you edit the Additional Off-Cycle Payment infotype (0267) using Batch
Input [External]or Fast Entry [External].
If you create additional off-cycle payments in the Additional Off-Cycle Payment

infotype (0267), you must ensure that the system is using the correct data from
the infotype during the payroll run. You must therefore make sure that you enter
the same data in the selection screen for the process or the payroll driver as you
did when you created the infotype record. This includes the following entries:
Off-Cycle Reason
Payroll Type
Payroll identifier
Payment date of the off-cycle payroll
If you create one-time payments in the Off-Cycle Workbench, the system
ensures that payroll accounting is executed using the correct data.
Structure
The standard system contains various wage types as subtypes
You can only select off-cycle reasons that are assigned to payroll type A in
Customizing. For more information, refer to Reasons, Types and Categories for Off-
Cycle Payroll [Page 129].
You must therefore only give a payroll identifier, if you make two records of the
Additional Off-Cycle Payment infotype (0627) for one employee on the same day. The
system requires the payroll identifier to distinguish between two runs with the same
date and the same payroll type.
You have made a bonus payment of USD 100 for an employee. In doing so, you
have not entered a payroll identifier. The employee is to receive a further bonus
payment on the same day of USD 50. You must therefore enter a payroll
identifier, e.g. the figure 1, to enable the system to differentiate.
Integration
If you create mass off-cycle payments in the Additional Off-Cycle Payment infotype (0267),
you implement the payroll run using a process model [External] that you defined in

Customizing off-cycle activities. In the HR Process Workbench, you create a Process
[External] using this process model. You then run the process model. The process model
ensures that payroll is only run for employees for whom there is a corresponding record
available in the Additional Off-Cycle Payment (0267) infotype.
You can also start the payroll driver without using a process model. In this case, you have the
following options:
You enter each employee that has received an additional off-cycle payment.
You run payroll for the entire payroll area. You run payroll for the entire payroll area.
We recommend making mass off-cycle payments using a process model.

See also:
Creating bonus payment details in infotype 0267 [External] (Payroll Thailand)

Advance Payment Methods
This function enables you to make advance payments to your employees in line with both
legal and common business requirements in Ukraine.
You can run off-cycle payroll to make different types of advance payments. For more
information, see the following links:
Making Advance Payments Based on Monthly Salary [Page 118]
Making Off-Cycle Vacation Payments [Page 121]
Making Off-Cycle Bonus Payments [Page 123]

Making Advance Payments Based on Monthly
Salary
You use this process to make advance off-cycle payments to your employees using the most
common methods in Ukraine. The payments are based on employees' salaries as follows:
Simple advance payment (amount or percentage of basic salary) – off-cycle category

11
Advance payment of percentage of monthly salary – off-cycle category 08
Advance payment of amount earned up to a given date – off-cycle category 09
In Ukraine, off-cycle payments are advance payments that must be incorporated in the
regular payroll run to make sure that the system calculates deductions (for example, social
insurance payments and income tax) on the employees' total earnings correctly. To ensure
that the system makes the correct deductions, the system takes into account the previous
payroll results and any deductions based on advance off-cycle payments.
Prerequisites
To run off-cycle payroll for one of the above advance off-cycle payments, you must have
created the required master data records in the Additional Off-Cycle Payment (0267)
infotype.
You have made the following settings in Customizing for Payroll Ukraine under Off-Cycle
Activities Configure Wage Types :
You have set up the wage types in which you want to store the deductions based on
the type of advance off-cycle payments that you make.
To enable the system to incorporate off-cycle payments in the regular payroll run, you
must have assigned the wage types that store off-cycle payments and associated
deductions to wage types that the system processes during regular payroll runs.
To enable the system to process deductions during off-cycle payroll runs correctly,
you must have determined how the system stores the affected wage types in the
payroll results table.
Process
1. You run off-cycle payroll using the Off-Cycle Workbench.
2. To determine the percentage of an employee’s monthly salary that the system must
pay during the off-cycle payroll run, the system imports the required record in the
Additional Off-Cycle Payment (0267) infotype.
The system processes the payment according to the type of advance payment as
follows:
o Advance payments based on a percentage of a monthly salary (off-cycle

category 08) and based on the amount an employee earns up to a given date
(off-cycle category 09)
The system evaluates all basic payments in the required period in the same
way that the system process payments during the final monthly payroll
calculation. To do this, the system imports payments from the Basic Pay
(0008), Recurring Payments/Deductions (0014), and Additional Payments

(0015) infotypes, evaluates an employee’s working time, and processes
absences.
o Simple advance payments that comprise only an amount or a percentage of

a basic salary (off-cycle category 11)
The system uses the amount or percentage that you enter in the infotype
record and does not process an employee’s different payment types or
working time.
3. Based on your Customizing settings for wage type substitution, the system calculates
only the advance off-cycle payment or also the required deductions, for example,
taxes or garnishment.
For more information about how the system processes deductions, see Deduction
Processing for Payments Based on Monthly Salary [Page 120].
4. During the next regular payroll run, the system recalculates all off-cycle results and
deducts the amounts that employees have already received from the final result.
For more information, see the online documentation for parameter RCOC in the
Beginning a Loop in the Payroll Schema (LPBEG) function.
More Information
Deduction Processing for Payments Based on Monthly Salary [Page 120]

Deduction Processing for Payments Based on
Monthly Salary
When the system processes advance payments based on an employee’s monthly salary, the
system calculates the deductions that apply to the advance off-cycle payments.
Depending on the off-cycle category that you use to make advance off-cycle payments based
on an employee’s salary, the system defers deductions until the next regular payroll run or
makes deductions from the advance off-cycle payment. In both of these cases, the system
does not transfer deductions to Financial Accounting (FI), but rather substitutes the regular
deduction wage types with wage types specific to off-cycle payroll runs.
The personnel calculation rules Substitute Wage Types in RT During Off-Cycle Run
(UAO9) and Substitute Wage Types in IT During Off-Cycle Run (UAOA) control how the
system substitutes wage types.
Features
Making Deductions on Simple Advance Payments
If an advance off-cycle payment is a percentage of an employee's basic salary or is a fixed
amount, the system calculates the applicable deductions and stores them in substitute wage
types specific to off-cycle payments. As a result of the wage type substitution, the system
does not transfer the deductions to FI during the off-cycle payroll run.
To ensure that employees pay the deductions due on the total amount that they earn in a
given month, during regular payroll runs that follow off-cycle payroll runs, the system includes
the advance off-cycle payments when it calculates deductions. The system adds the
substitute wage types to the regular wage types that store the base amount for calculating
deductions, for example, to the wage types that store the base amount for income tax
calculation, /161 and /165.
Making Deductions on Advance Payments of Total Earnings

To ensure that the system deducts income tax and any contributions related to advance off-
cycle payments that are based on an employee’s total earnings only once, the system
decreases the advance off-cycle payment by the total of all deductions that apply to the
employee in question. The system calculates the deductions and stores them in wage types
that are specific to off-cycle payroll runs.
The system subtracts the deductions due on the amount that the employee earns up to the
date of the advance off-cycle payment and takes into consideration the deductions during the
next regular payroll run. During the next regular payroll run, the system transfers the
deductions to FI.
More Information
System documentation for the personnel calculation rules Substitute Wage Types in RT
During Off-Cycle Run (UAO9) and Substitute Wage Types in IT During Off-Cycle Run (UAOA)

Making Off-Cycle Vacation Payments
In Ukraine, employers are legally obligated to pay their employees vacation pay at least three
days before the period of vacation begins. You use this process to meet this requirement and
to enable the reports that evaluate employees' absences to take into consideration both the
period of absence and the average vacation pay.
To make off-cycle vacation payments, you use a special off-cycle category (10) and off-cycle
payroll reason (0103).
Prerequisites
You have substituted wage types for the off-cycle vacation payment so that only the wage
type for the vacation payment is transferred to Financial Accounting, for example. For more
information, see Customizing for Payroll Ukraine under Off-Cycle Activities Configure
Wage Types Assign Wage Types During Off-Cycle Run with Category 10 .
If you want to run off-cycle payroll using the payroll driver to calculate vacation payments, you
have checked the selection process that the system uses to evaluate periods of vacation and
incorporate them in the off-cycle payroll run. By default, the system uses the selection
process VAC1. For more information, see Customizing for Payroll Ukraine under Off-Cycle
Activities Define Process for Employee Selection .
Process
2. The system determines which vacation records lie in the period for which you want to
run off-cycle payroll.
o If you use the Off-Cycle Workbench, when you select the off-cycle payroll
reason for a vacation payment (0103) the system proposes the periods of
vacation that have not yet been paid for the employee in question. The Off-
Cycle Workbench marks these periods of vacation as paid so that the system
cannot calculate them a second time.
o If you run off-cycle payroll using the payroll driver for Ukraine, for example, by
means of a process model, the Ukrainian RAB with Extension for Off-Cycle
Processing (UARAB) payroll function selects absences based on the selection
process VAC1. The selection process selects periods of vacation that are
linked together by means of the Absence Link for Average field in the
Absences (2001) infotype.
For more information, see the online documentation for the Ukrainian RAB with
Extension for Off-Cycle Processing (UARAB) function.
3. Based on your Customizing settings for wage type substitution, the system calculates
only the vacation pay, or also other types of remuneration, for example, taxes or
garnishment.
For more information, see the online documentation for the personnel calculation
rules Substitute Wage Types in RT During Off-Cycle Run (UAO9) and Substitute
Wage Types in IT During Off-Cycle Run (UAOA).
4. During the next regular payroll run, the system recalculates all off-cycle results and
deducts the amounts that employees have already received from the final result.

Example
Your employee, Nataliya Krasovsky, plans to take vacation from June 15 to June 20. In line
with legislation, you are obligated to make the vacation payment three days before the start of
Svetlana's vacation.
On June 12, you schedule an off-cycle payroll run with the payroll reason for vacation
payments (0103). The system reads the corresponding records in the Absences (2001)
infotype and marks the vacation as paid. As a result of the off-cycle payroll run, Nataliya
receives the vacation payment in time for her vacation.
During the next regular payroll run at the start of July, the system recalculates the vacation
and deducts the amounts that you already paid out from the overall payment that you make to
Nataliya.

Making Off-Cycle Bonus Payments
In Ukraine, it is common for employers to pay their employees a kind of bonus for various
reasons, for example, for public holidays. To pay employees bonuses as close as possible to
a public holiday, for example, you require an off-cycle payroll run, which you can set up
according to your individual requirements.
When you run off-cycle payroll to make bonus payments, you use a special off-cycle category
(16) and off-cycle payroll reason (0107).
Prerequisites
You have substituted wage types for off-cycle bonus payments so that the system does not
calculate taxes or other deductions on the payment itself; the system does this only during the
next regular payroll run. For more information, see Customizing for Payroll Ukraine under
Off-Cycle Activities Configure Wage Types Assign Wage Types During Off-Cycle Run
with Category 16 .
If you want to use a process model to calculate bonus payments, you have created a
selection process that the system uses to evaluate bonus payments and incorporate the
bonus payments in the off-cycle payroll run. For more information, see Customizing for
Payroll Ukraine under Off-Cycle Activities Define Process for Employee Selection .
Process
1. You enter the amount of the bonus in the Additional Off-Cycle Payment (0267)
infotype.
3. Based on your Customizing settings for wage type substitution, during the off-cycle
payroll run, the system uses the Substitute Wage Types in RT During Off-Cycle Run
(UAO9) and Substitute Wage Types in IT During Off-Cycle Run (UAOA) personnel
calculation rules to substitute the wage types.
For more information, see the online documentation for the personnel calculation
rules.
4. During the next regular payroll run, the system evaluates all off-cycle results and
based on your Customizing settings for wage type substitution, adds the amount of
the bonus payment to other payments that the employee receives that month. The
system thereby increases the basis for calculating income tax and other taxes.
Example
You decide to pay all of your employees a bonus of UAH 500 for the May 1 public holiday.
There are no legal requirements that stipulate when you must make the payment.
After you create the required master data records in the Additional Off-Cycle Payment (0267)
infotype, you schedule an off-cycle payroll run with the off-cycle payroll reason for bonus
payments (0107) on April 25. Since you do not want to calculate income tax on the bonus
payment during the off-cycle payroll run, the system transfers UAH 500 to your employees, in
line with your Customizing settings for wage type substitution.
During the next regular payroll run at the start of May, the system increases the amount of
each employee's pay by the amount of the off-cycle bonus payment. The system calculates

taxes on the total amount before deducting the UAH 500 bonus payment from the amount
that the system transfers to Financial Accounting.

Off-Cycle Workbench
A user interface that enables you to carry out off-cycle payroll and reversals.
You use the Off-Cycle-Workbench to perform the following tasks for a specific employee:
Display payroll results
Run various types of off-cycle payroll
Reverse an incorrect payroll result
If you want to carry out off-cycle payroll for a large number of employees on the same
day, see Making Mass Advance Off-Cycle Payments [Page 137].
Structure
The Off-Cycle Workbench contains the following tab pages:
History [Page 126]
Payroll [Page 127]
Reverse Payment [Page 131]

Payroll History
Use
This function enables you to display the previous payroll results relating to payment for a
specific employee within the Off-Cycle Workbench. To see the payroll results, you do not
have to leave the Off-Cycle Workbench or run a report.
For example, you want to replace a torn check. You can refer to the check
number that is displayed in the payroll history to find out for which payroll result
the check was issued.
Features
The History tab page in the Off-Cycle Workbench displays an extract from the payroll cluster
containing the most important information on the employee’s payroll results.
Payments that you have replaced with a check and payroll results that you have reversed are
indicated.
To see more detailed information, you can display the remuneration statement for each
payroll result.
For payments, you can display the following information:
Check number, house bank and company account
In the case of replaced payments - which payment was replaced by which check
In the case of reversed payroll results - the reason for reversal and the administrator
who carried out the reversal
Activities
To display the remuneration statement for a particular payroll result, select the result and
choose Remuneration statement.
For detailed information on a payment, choose .

Off-Cycle Payroll
As an addition to regular payroll, which carries out payroll at fixed regular intervals, this
function enables you to carry out specific off-cycle payroll activities for individual employees
on any day. Off-cycle reasons differentiate between various types of off-cycle payroll runs.
You run off-cycle payroll on the Payroll tab page in the Off-Cycle Workbench.
Prerequisites
You have specified which off-cycle reasons you want to use in Customizing for Payroll
Ukraine under Off-Cycle Activities Set-Up Off-Cycle Reasons .
Features
The country version for Ukraine enables you to perform the following functions:
Use different calculation methods to make advance off-cycle payments to your

employees
The methods are based on off-cycle categories that correspond to the most common
business practices in Ukraine.
Make advance off-cycle payments to one or multiple employees on the same day
Make more than one payment each month
Incorporate the results from off-cycle payroll runs in subsequent regular payroll runs

Running Off-Cycle Payroll
Prerequisites
You are in the Off-Cycle Workbench [External].
Procedure
...
1. Enter the personnel number that you want to process and choose the tab page Payroll
2. Select an off-cycle reason [Page 129]
This determines the subsequent processing.
3. If required, enter a date other than the one proposed.
4. Copy the payment method from the Bank Details infotype (0009), or enter a different
payment method.
5. If required, split the payment and assign the main and secondary bank details.
6. Enter additional data according to the off-cycle reason you have entered.
7. Choose Start payroll
8. After the payroll run, save your data.
Result
Following the off-cycle payroll run, the system makes the following changes:
...
1. It saves the data in the relevant infotypes, and saves the payroll results to the
database.
At the same time, the system makes an entry in the indicator table for batch processing
to show that a payroll result exists that requires further processing.
You can display the contents of the indicator table using report H99LT52OCG
(Display Indicator Table for Off-Cycle Batch Processing). The report is located in
the Off-Cycle menu.
2. At the regularly scheduled time, the system runs as a background job the country-
specific batch report for subsequent processing of off-cycle payroll.
The report reads the indicator table. Using the payroll results from the indicator table,
the system starts the process model that you specified in the report variant.
3. The system carries out all subsequent programs that you specified in the process
model. For example, it produces remuneration statements, prints checks or initiates
transfers and posts payroll results to Accounting if you have specified these steps in
the process model.

Reasons, Types and Categories for Off-Cycle
Payroll
Various off-cycle reasons, and assignment to various types and categories are used to
distinguish payroll runs.
Off-Cycle Regular Advance Christmas Vacation Correction Payroll

reason period on payment bonus bonus payment Results
(example) demand (leave) Adjust-
ment
Category for off-

cycle reason On Advance Bonus Absence Correction Payroll
demand payment payment results
adjust-
ment
Off-cycle
reason type On Advance Bonus Absence Other Other
demand payment
' ' A B C
Payroll type
(Regular (Bonus payment) (Correction- (Manual
payroll run) accounting) check)
Off-Cycle Reason
Off-Cycle Reason
The off-cycle reason differentiates between various business reasons. Off-Cycle reasons
enable an administrator to decide conveniently what kind of payroll to run from the Off-Cycle
Workbench.
The standard system already contains off-cycle reasons for all kinds of off-cycle payroll. In
Customizing for Payroll, you can set up your own reasons that are valid for your enterprise.
You assign each off-cycle reason to a specific category. This enables the system to deal with
similar payroll runs in the same way. The subsequent assignment to a type of off-cycle reason
and to a payroll type is done automatically by the system.
In Customizing, you define the off-cycle reason Holiday bonus and assign it to the
category bonus. The system assigns the type of off-cycle reason Bonus and the
payroll type A to the Holiday bonus.
Category for the Off-Cycle Reason

Categories group several off-cycle reasons together so that similar reasons, such as Easter
bonus and Christmas bonus are dealt with in the same way by the system.
Which types of off-cycle reason are set up in the system depends on the
categories that are required by the country-specific components.

Off-Cycle Reason Type
The system uses the off-cycle reason type to decide what information it must display in the
Off-Cycle Workbench. The decision is made in line with the off-cycle reason selected by the
administrator.
On demand
The system proposes the next regular payroll period.
Advance Payment
The system proposes several future regular payroll periods.
Bonus
If you have defined a wage type, the system proposes a wage type for bonus
accounting that you have set up in Customizing for Payroll.
Absence
The system proposes for payroll future absences that you have recorded in the
Absences infotype (2001).
Other
For a correction run carried out in the Off-Cycle Workbench, the system displays the
date of the retroactive payroll run from the Payroll Status infotype (0003). For a payroll
run with the category Payroll Results Adjustment, the system displays payments that
you have created in the Payroll Results Adjustment infotype (0221).
Payroll Type
The payroll type enables the payroll driver to decide which of the following kinds of payroll are
to be run:
Blank = Regular payroll run
The system then runs on demand payroll for one or several periods.
The types of off-cycle reason on demand and advance payment belong to this payroll
type.
A = Bonus payment
The payment date with which you run off-cycle payroll is the start and end date of the
payroll period. The system creates the payroll result for this day.
The types of off-cycle reason bonus and absence belong to this payroll type.
B = Correction run
The system runs retroactive payroll for past periods on account of a change in master
data. Payroll is re-run for all periods that have already been run, back as far as the
retroactive accounting date. In addition to these retroactive accounting results, the
system creates an original result for the payment date that you use for the off-cycle run.
C = Manual check
The system processes payments that you have entered in the Payroll Results
Adjustment infotype (0221). This payroll type exists for USA and Canada only.

Reversing Payroll Results
Use
Depending on the status of the payroll control record, you have various options for making an
incorrect payroll result invalid.
If the control record does not yet have the status End of payroll, you can:
Repeat the payroll run
Delete the incorrect payroll result [External]
If the control record already has the status End of payroll, you must reverse the payroll
result. If the data medium exchange program has already been run, the system also
reverses the relevant checks and transfers.
When reversing, the payroll results are not deleted from the data base. They are
only marked with the “invalid” indicator. Reversal consequently requires a lot of
memory space.
If the payroll control record does not yet have the status End of payroll, we
recommend that you repeat the payroll or delete the incorrect payroll result.
Integration
In the case of a payment by check, the system reverses the check in Accounting.
If the amount was paid by transfer, the system writes the personnel number, sequence
number, amount, and BT split indicator [External] relating to this transfer to the table T52OCL
(Off-Cycle: Transfer by check replaced or reversed).
This table is not actively evaluated by the system. Instead, it only documents
which payments you have replaced or reversed. You must therefore make sure
that a reversed payment was definitely not transferred. To check the table
T52OCL, you can run the report H99LT52OCL (Transfer by check replaced or
reversed).
Prerequisites
You have scheduled the batch for subsequent processing of off-cycle activities as a regular
background job with a suitable variant by choosing System Services Jobs Define
Jobs. We recommend that you run subsequent processing as a background job on a daily
basis.
Features
The tab page Reverse payment in the Off-Cycle Workbench offers you the following options:
You can reverse the payroll results of a regular payroll run or an off-cycle payroll run,
regardless of whether the employee has received a check or transfer.
The system reverses all payments that belong to that payroll result.
The system offers an overview of all the payroll results. You can display detailed
information on the relevant payments.
You can select a reason for the reversal.
If you reverse a check, you must specify a reason.
You can reverse a transfer without specifying a reason.

Reversing the Payroll Result
Prerequisites
You have corrected the relevant master data.
If you reverse a payroll result that was the result of bonus accounting, you must
also delete the relevant infotype record in the Additional Payment Off-Cycle
infotype (0267).
You are in the Off-Cycle Workbench [External].
Procedure
...
1. Enter the personnel number that you want to process and choose the tab page Reverse
payment.
2. Select the payroll result that you want to reverse.
3. If you want to reverse a check, enter the reason for the reversal.
4. Choose Reverse.
5. Confirm the security check.
Result
The system checks under which circumstances the reversal takes place:
Have you reversed the last payroll result?
Have payments already taken place to the third party?
Had the payroll result already been posted to Accounting?
Depending on these circumstances, different subsequent activities are executed. The graphic
below gives an overview of the subsequent activities:
Last payroll yes yes

Payment to third party
result?
taken place?
no no 2 Void
• Set Invalid indicator V
Out-of-Sequence- Payroll result yes in RGDIR
1 Reversal already posted? • Enter data record in
• Change entries in RT indicator table for OC-
and BT batch processing
no
• Set retroactive • Run batch report for
accounting date subsequent
3 Void
in infotype 0003 processing
• Set Invalid indicator R Set Invalid indicator V • Start processing
in RGDIR in RGDIR
Result 1 – Out-of-Sequence-Reversal
...
1. The system makes changes to the tables RT (Results Table) and BT (Bank Transfers).
For more information, see Effects of an Out-of-Sequence-Reversal [Page 135].
2. Depending on how the reversed payroll result came about, the system sets the
following retroactive accounting date in the Payroll Status infotype (0003):

With an off-cycle payroll run, the system uses the payment date of the payroll as
the date for the earliest payroll-relevant master data change for bonus
payments.
With a regular payroll run, the system uses the start date of the period for which
payroll has been run as the date for the earliest change to master data since the
last payroll run.
This ensures that retroactive accounting takes place.
3. The system places the indicator R in the invalid field of the payroll directory (RGDIR) for
the reversed payroll result. It enters the reason, date and time of the reversal in this
data record.
4. Following the reversal, you have the following options:
If the employee is to receive a payment immediately, carry out a correction
payroll run in the Off-Cycle Workbench.
If you do not execute a correction payroll run in the Off-Cycle Workbench, the
system automatically carries out retroactive payroll when the next regular payroll
run takes place.
Result 2 – Void
...
1. The system places the indicator V in the Invalid field of the payroll directory (RGDIR) for
the reversed payroll result.
If the V indicator is set, the payroll result can no longer be used for evaluations.
Instead, it is only available for the payroll history. The system enters the reason,
the date, and the time of the reversal to the data record.
2. The system makes an entry in the indicator table for off-cycle batch processing.
You can display the contents of the indicator table using report H99LT52OCG
(Display Indicator Table for Off-Cycle Batch Processing). The report is located in
the Off-Cycle menu.
3. The system runs the batch report for subsequent processing of off-cycle activities as a
background job at the time that you have scheduled for the regular processing of the
report.
The report reads the indicator table and starts a process based on the process model
that you specified in the report variant. With this process, the system creates reversal
documents for the reversed payroll results and transfers these to Accounting. As a
result, the documents that were originally posted are reversed.
4. Depending on which payroll result you reversed, you have the following options:
If the payroll result arose from an off-cycle payroll run, you can rerun payroll.
If the payroll result arose from a regular payroll run, retroactive payroll takes
place at the next regular payroll run, since the payroll control record already has
the status End of payroll.
Result 3 – Void
The system places the indicator V in the Invalid field of the payroll directory (RGDIR) for the
reversed payroll result.

Effects of an Out-of-Sequence Reversal
If you cancel the last payroll result and payments have already been made to third parties, or
if you reverse a payroll result other than the last, the system makes the following changes:
Table RT (Results Table)

The system produces the technical wage type /568 that contains the payment amount
for the reversed payroll result.
It writes the amount of the wage type /557 cm to the wage type /569.
It writes the amount of the wage type /558 cm to the wage type /570.
It writes the amount of the wage type /559 to the wage type /571.
It stores the former payment method in coded form in the amount per unit field in wage
types /569, /570 and /571.
Payment by check: 1
Transfer: 2
Check with numbers applied manually: 3
The payment of USD 2,500 to an employee was originally split into a check
payment (USD 1,000) and bank transfer (USD 1,500). The following appears in
the RT table:
Wage Rate Number Amount BT
type
/559 1,000 01
/559 1,500 02
After reversal, the following appears in the results table:
Wage Rate Number Amount BT
type
/568 2,500
/571 1 1,000 01
/571 2 1,500 02
The system deletes the wage types /557, /558, and /559.
BT Table
The system deletes the wage types /557, /558, and /559.
The other wage types in the BT table, for example, wage types from the External Transfers
infotype (0011) are not deleted.
Posting to Accounting
If the posting transfer has already evaluated the reversed payroll result, the system also
adjusts the posting index after an out-of-sequence reversal. In doing so, it converts the
references to the wage types /557, /558 and, /559, which are contained in the posting index
for the reversed payroll result, to the newly-created wage types /569, /570, and /571. In this
way, the split indicators in the Business Add-In (BAdI) Posting Control for Payroll Results are
still available.

Making Mass Advance Off-Cycle Payments
In Ukraine, companies are required by law to make advance off-cycle payments to their
employees on the same day. Depending on the number of employees eligible for the
payments, this could mean paying a large number of employees at the same time.
Unlike the process for paying individual employees by means of the Off-Cycle Workbench, to
pay multiple employees at the same time, you use a selection report along with the regular
payroll driver for Ukraine.
You can exclude employees from the off-cycle payment who are absent within a given
number of days of the advance off-cycle payment date, or who are absent for a particular
reason. For example, you can exclude employees who are on maternity leave.
Prerequisites
You have determined which absence types you want to exclude from advance off-cycle
payments. You make this setting in Customizing for Payroll Ukraine under Off-Cycle
Activities Define Process for Employee Selection Define Content of Employee Selection
Process .
Process
1. You generate a list of employees who are to receive an advance off-cycle payment,
and who therefore require a master data record in the Additional Off-Cycle Payment
(0267) infotype.
For more information, see Preselecting Employees Requiring Master Data Records
[Page 138].
2. You prepare and create the required master data records in the Advance Off-Cycle
Payment (0267) infotype (see Employee Selection for Fast Data Entry [Page 139]).
Alternatively, if you want to automate the payment process, you can combine the
above two steps by using a different report. You use the report to create the required
master data records on a regular basis, for example, in the middle of each month
(see Mass Generation of Records for Advance Off-Cycle Payments (HRUU0267)
[Page 141]).
3. You call the regular payroll driver for Ukraine. You access the payroll driver on the
SAP Easy Access screen under Human Resources Payroll Europe Ukraine
Payroll Start Payroll .
You enter the required payroll area, and the same payroll reason and payment date
that you enter in the records for the Advance Off-Cycle Payment (0267) infotype.
4. You start the payroll calculation.
Result
The system makes advance off-cycle payments to all employees who are in the selected
payroll area and have a record in the Additional Off-Cycle Payment (0267) infotype for the
payment date.

Preselecting Employees Requiring Master Data
Records
To make advance off-cycle payments to large numbers of employees, you use the Fast Entry
(PA70) transaction to prepare a list of employees who require the necessary master data
records in the Additional Off-Cycle Payment (0267) infotype.
Procedure
1. Call the Fast Entry transaction. To access this transaction, on the SAP Easy Access
screen, choose Human Resources Personnel Management Administration
HR Master Data Fast Entry .
2. In the Fast Entry of Master Data section of the screen, select Additional Off-Cycle
Payments.
3. In the Direct Selection group box, enter the Additional Off-Cycle Payments (0267)
infotype and the subtype that corresponds to the required type of advance off-cycle
payment.
4. In the Enter Personnel Numbers group box, select Preselection Using Report and
enter the report name HUAUFST0.
5. Choose Edit Create .
The Employee Selection report appears (see Employee Selection for Fast Data Entry
[Page 139]).

Employee Selection for Fast Data Entry
You use this report to select large numbers of employees for advance off-cycle payments.
Based on the employees that you select, you create the required master data records in the
Additional Off-Cycle Payment (0267) infotype.
The payroll driver processes the master data records that the report creates and makes
advance off-cycle payments accordingly.
Prerequisites
You have selected employees who are to receive an advance off-cycle payment (see
Preselecting Employees Requiring Master Data Records [Page 138]).
To more accurately restrict the number of employees that you want to include in, or exclude
from the off-cycle payroll run using a selection process. You make this setting in Customizing
for Payroll Ukraine under Off-Cycle Activities Define Process for Employee Selection .
Features
Selection
Use the standard selection criteria to select the required employees.
In the Additional Selection Parameters group box, enter the following data:
If required, further restrict the employees who are to receive an advance off-cycle
payment by entering a selection process.
Enter the date of the advance off-cycle payment. Note that the date you enter must
be the same as the date in the Additional Off-Cycle Payment (0267) infotype.
Output
The report lists all employees who meet your selection criteria. To create records in the
Additional Off-Cycle Payment (0267) infotype for the selected employees, see Creating
Master Data Records [Page 140].
Activities
To access this report, on the SAP Easy Access screen, choose Human Resources
Personnel Management Administration HR Master Data Fast Entry .
More Information
Fast Entry of HR Master Data [External]

Creating Master Data Records
To enable the payroll driver to make advance off-cycle payments, you create records in the
Additional Off-Cycle Payment (0267) infotype for all employees who are to receive advance
off-cycle payments.
Prerequisites
You have selected the employees who are to receive advance off-cycle payments by running
the Employee Selection for Fast Data Entry (HUAUFST0) [Page 139] report and you are on
the output screen of the report.
Procedure
1. Select all employees for whom you want to create infotype records and choose Save.
A list of the selected employees appears.
2. Check that your selection is complete, select the required employees, and choose
Edit Create with proposal .
3. Enter the same off-cycle reason that you selected on the Fast Data Entry screen (see
Preselecting Employees Requiring Master Data Records [Page 138]), as well as the
wage types in which you want to store the advance off-cycle payment.
4. Save your entries.
Result
The system creates the master data records that the payroll driver needs to process advance
off-cycle payments.

Mass Generation of Records for Advance Off-
Cycle Payments (HRUU0267)
You use this report to automate the process of making advance off-cycle payments to large
numbers of employees on the same day. This report enables you to make advance off-cycle
payments regularly without needing to first select employees and then perform manual steps
to create the required master data records separately.
Integration
To select the employees who are to receive an advance off-cycle payment, this report calls
the Employee Selection for Fast Data Entry (HUAUFST0) report in the background.
Prerequisites
To more accurately restrict the number of employees that you want to include in, or exclude
from an off-cycle payroll run, you can use a selection process. If you want to restrict
employees in this way, you must create a selection process in Customizing for Payroll
Ukraine under Off-Cycle Activities Define Process for Employee Selection .
Features
Based on the employees that you select, the report creates records in the Additional Off-
Cycle Payment (0267) infotype for the payment date that you enter on the selection screen.
To make the actual payments, you start the payroll calculation using the payroll driver for
Ukraine.
To fully automate the payment process, you can set up the payroll driver to run in the
background after this report generates master data records.
Selection
To restrict the report to a predefined group of employees, in the Additional Selection
Parameters group box, enter the required selection process. Enter the reason for the advance
off-cycle payment and the wage type in which you want to store the payment. Depending on
whether the wage type stores an amount or a percentage, fill in the Amount or Amount and
Number/Unit fields respectively.
You can schedule the report to run in batch mode for a large number of employees, but you
might want to pay only selected employees a different amount. In this case, you can change
the master data on the selection screen (see Example below) by selecting the Overwrite
Master Data checkbox.
In the Generation Type group box, select the way in which you want to run the report:
To fully automate the creation of master data records, choose Batch Input and enter
the batch input session data as required.
To go through the master data records that the system creates individually, choose
Direct and select the Display Screens radio button.
If you want to check the list of employees that the report selects before the report
creates master data records, choose By Record.

Output
The report generates records in the Additional Off-Cycle Payment (0267) infotype and lists
the processing status of the employees that you selected. Depending on the generation type
that you select, the report creates records as follows:
Batch input
The report generates master data records and displays a list of the employees who
the report processes, along with the processing status.
Direct
The report creates master data records and displays the screens of the infotype
records that the report creates.
By record
The report lists all employees who meet the selection criteria. To create master data
records, select the required employees and choose Save.
Activities
Payroll Europe Ukraine Off-Cycle Mass Generation of IT 0267 Records .
Example
Since the heads of department in your company achieve their targets in May, you decide to
pay them 30% of their regular salaries as the advance off-cycle payment in the middle of the
month. All other employees receive 20% of their regular salary in the middle of the month.
Select all employees and enter 20% as the payment amount. Do not select the Overwrite
Master Data checkbox and run the report to create master data records for all selected
employees.
To pay the heads of department 30% of their regular salaries, run the report again. This time,
enter a selection process that contains only the heads of department, enter 30% as the
payment amount, and select the Overwrite Master Data checkbox.
The report overwrites the master data records that you created for the heads of department
during the first report run with the records that contain 30% as the payment amount.

Completeness Check (HUAC0267)
You use this report to check that the employees you select for an advance off-cycle payment
do actually receive the advance off-cycle payment.
The report checks whether off-cycle payroll results exist for employees who have a record in
the Additional Off-Cycle Payment (0267) infotype on the payment date of the off-cycle payroll
run.
Prerequisites
You have created master data records in the Additional Off-Cycle Payment (0267) infotype
for employees who are to receive an advance off-cycle payment:
If you pay individual employees, see Off-Cycle Workbench [Page 125].
If you pay large numbers of employees, see Making Mass Advance Off-Cycle
Payments [Page 137].
You have performed an off-cycle payroll run for the employees who are to receive an advance
off-cycle payment.
Features
Selection
Enter the time frame, payroll area, and any other criteria to select the set of employees whose
advance off-cycle payments you want to check.
Furthermore, enter the off-cycle reason and wage types that you used for the advance off-
cycle payment that you want to check.
Output
The report shows the status of each employee who was supposed to receive an advance off-
cycle payment on the date you enter on the selection screen. The report shows one of the
following errors:
Error Action Required
There are no payroll

Run payroll.
results.
Run the Preprogram DME program.

The system does not
carry out a bank On the SAP Easy Access screen, choose Human Resources
transfer. Payroll Europe Ukraine Payroll Bank Transfer
Preprogram DME .
Activities
Payroll Europe Ukraine Off-Cycle Completeness Check for Payment Results .

Deductions and Calculation of the Bank Transfer
Amount
You use this component to process deductions and subsequently transfer the employee’s net
income to his or her bank.
The component contains Ukraine-specific features that enable you to perform the following
functions:
Combine multiple deductions and limit the total amount of deductions based on
legally-defined percentages
Process the fee for postal transfers of garnishment payments
Make garnishment payments by including the wage types that store garnishment
payments in the Bank Transfer table, BT
More Information
Deduction Processing [External]

Example: Deductions Processing
The gross salary of your employee, Boris Kasparov, is UAH 10,000. Boris has two
garnishment documents. One garnishment document stipulates that he must pay his ex-wife
UAH 4,000 to support their children. You transfer the garnishment amount directly to Boris’s
ex-wife’s checking account. The second document stipulates that Boris must pay UAH 2,000
compensation to the driver of a vehicle with which Boris collided, and for which Boris was at
fault. One of the garnishment payments is to support Boris’s children. Ukrainian legislation
stipulates that the maximum deduction in child support cases is 70% of the gross salary.
Process
The system calculates the base amount for deductions as follows:
Determine ESV deduction (3,6 %) = UAH 10000 * 3.6% = UAH 360.
Determine income tax = 1360,69 (taxed by 15%) + 96,69 (taxed by 17%) = 1457,38
Determine payment without taxes = UAH 10000 – UAH 360 - UAH 1457,38 = 8182,62
Determine maximum deduction at 70% of salary: UAH 8182,62 x 70% = UAH 5727,83
The system cannot deduct the total amount of both garnishment documents (UAH 6,000),
since this exceeds the maximum deduction limit of UAH 5727,83. The system calculates the
deductions proportionally as follows:
Garnishment for children: UAH 4,000 / (UAH 4,000 + UAH 2,000) x UAH 5727,83 = UAH
3.818,56
Garnishment for injury compensation: UAH 2,000 / (UAH 4,000 + UAH 2,000) x UAH 5727,83
= UAH 1909,28
The result of the above calculation equals the limit for deductions, UAH 5727,83.
To process the remaining amounts for both garnishment documents in the following payroll
period, the system stores the remaining amounts in the arrears table (UAH 181,44 and UAH
90,72 correspondingly).

Example: Deductions Processing
The gross salary of your employee, Boris Kasparov, is UAH 10,000. Boris has two
garnishment documents. One garnishment document stipulates that he must pay his ex-wife
UAH 4,000 to support their children. You transfer the garnishment amount directly to Boris’s
ex-wife’s checking account. The second document stipulates that Boris must pay UAH 2,000
compensation to the driver of a vehicle with which Boris collided, and for which Boris was at
fault. One of the garnishment payments is to support Boris’s children. Ukrainian legislation
stipulates that the maximum deduction in child support cases is 70% of the gross salary.
Process
The system calculates the base amount for deductions as follows:
Determine ESV deduction (3,6 %) = UAH 10000 * 3.6% = UAH 360.
Determine income tax = 1360,69 (taxed by 15%) + 96,69 (taxed by 17%) = 1457,38
Determine payment without taxes = UAH 10000 – UAH 360 - UAH 1457,38 = 8182,62
Determine maximum deduction at 70% of salary: UAH 8182,62 x 70% = UAH 5727,83
The system cannot deduct the total amount of both garnishment documents (UAH 6,000),
since this exceeds the maximum deduction limit of UAH 5727,83. The system calculates the
deductions proportionally as follows:
Garnishment for children: UAH 4,000 / (UAH 4,000 + UAH 2,000) x UAH 5727,83 = UAH
3.818,56
Garnishment for injury compensation: UAH 2,000 / (UAH 4,000 + UAH 2,000) x UAH 5727,83
= UAH 1909,28
The result of the above calculation equals the limit for deductions, UAH 5727,83.
To process the remaining amounts for both garnishment documents in the following payroll
period, the system stores the remaining amounts in the arrears table (UAH 181,44 and UAH
90,72 correspondingly).

Subsequent Activities
This component contains activities that you perform after the payroll run.

Preliminary Program DME
You use the preliminary program DME to evaluate the payroll results to create payment data.
The creation of payment data is the first step in the wage and salary payments process.
You can also use the preliminary program DME if you want to make several partial payments
on different dates within a payroll period (see Qualified Advance Payments [External]).
The preliminary program DME can evaluate payments using different payment methods in a
payment run. The payment medium programs, which further process the data created by the
preliminary program DME, select the relevant data records using the payment method.
The preliminary program DME processes both information from the master data [External]
and information from the payroll results [External] for an employee.
Integration
The payment data created by the preliminary program DME is processed by the country-
specific payment medium programs in Accounting to create payment mediums (for example,
DME files for the bank, checks). You must start these subsequent programs after the
preliminary program DME has evaluated the payroll results for the employee and has created
the payment data.
Prerequisites
You have exited payroll for the payroll periods for which you want to make wage and salary
payments. (Exception: You make a qualified advance payment [External] before exiting
payroll.)
You have checked or made the following settings in agreement with Accounting.
Set up the payment methods in Customizing for Personnel Management, by choosing

Personnel Administration Personal Data Bank Details Define Payment
Method
Set up the house banks and house bank accounts in Customizing for Payroll Ukraine,
by choosing Data Medium Exchange and Payments to Employees Preliminary
Programs for Data Medium Exchange Set Up House Banks
Defined the sending banks using the Sender Account Number for Data Medium
Exchange feature (DTAKT) in Customizing for Payroll Ukraine, by choosing Data
Medium Exchange and Payments to Employees Preliminary Programs for Data
Medium Exchange Define Sending Banks
If you do not want to use the company code stored in the Organizational Assignment
infotype (0001), you have defined the paying company code using the Sender
Account Number for Data Medium Exchange feature (DTAKT). To do this, in
Customizing for Payroll Ukraine, choose Data Medium Exchange and Payments to
Employees Preliminary Programs for Data Medium Exchange Define Sending
Banks
Assigned the text key for the payment transaction to transfer wage types in
Customizing for Payroll Ukraine, by choosing Data Medium Exchange and
Payments to Employees Preliminary Programs for Data Medium Exchange
Check Text Keys for Payment Transactions

If you import Support Packages that contain new file formats based on legal changes, to
ensure that the Cyrillic characters appear on the forms correctly, see SAP Note 895804.
Features
For every current original result for employees processed in a payment run, the preliminary
program DME reads the Bank Transfer table (BT) in the payroll results. The system performs
the following steps for every entry in the Bank Transfer table (BT):
The system determines the information on the payment recipient from the following
locations:
o Entry in the Bank Transfer table (BT)
o If the entry in the Bank Transfer table (BT) contains a recipient key, from the
Payee Keys table (T521B)
o If the entry in the Bank Transfer table (BT) does not contain a recipient key
and does not contain any recipient data, from the Personal Data (0002) and
Addresses (0006) infotypes
The system determines the payee information for garnishments from the following
locations:
o Vendor master data in Financial Accounting (FI)
o Payee key in the Ukraine-specific payee table (see Customizing for

Personnel Management, by choosing Personnel Administration Personal
Data Ukraine-Specific Settings Garnishment Documents Determine
Payees (Ukraine) )
The system evaluates the Sender Account Number for Data Medium Exchange
feature (DTAKT) to determine the following information:
o Paying company code
o House bank
o House bank account
The system reads the Purpose field in the Bank Transfer table (BT):
o If the Purpose field is filled, the program transfers the contents of the field to
the payment data.
o If the Purpose field is empty, the system uses the following text:
"Wage/Salary", <Personnel Number>, <Payroll Period> or “Pension”,
<Personnel Number>, <Payroll Period>.
If the entry in the Bank Transfer table (BT) relates to garnishment and the payment
method is blank, the program reads the payment method specified in the payee data.
The system determines the payment currency as follows:
o If the Currency field in the Bank Transfer table (BT) contains a currency, the
system uses this currency for the payment.

o If the Currency field in the Bank Transfer table (BT) does not contain a
currency, the system uses the currency from the Currency field in the Payroll
Status Information table (VERSC) for the payment.
The system reads the bank codes of the house bank and the recipient bank from the
Bank Master Record table (BNKA).
The system checks the payment data for consistency. If a payment with inconsistent
data exists for an employee, the system does not perform a payment for this
employee.
For every entry in the Bank Transfer table (BT), the system creates an entry in the
payment data.
Selection
Enter data as required.
Set Flag for Transfers
We recommend that you set the indicator. It causes the system to mark every processed
entry in the Bank Transfer table (BT) with the date and time, which indicates to payment runs
carried out later that the entries have been processed. This prevents entries in the Bank
Transfer table (BT) being accidentally processed more than once. If the payroll run is
repeated after you have executed the preliminary program DME, the system does not
overwrite the entries marked with date and time but performs a difference calculation. That is
why you must select Set Flag for Transfers if you want to perform a qualified advance
payment.
Wage Type
You can restrict a payment run to certain wage types, for example, to pay the wage types
created for the External Bank Transfers infotype (0011) separately from the employee's
salary.
Test
If you set the indicator, the system only displays the payments to be made as a result of a
payment run. The preliminary program DME does not create any payment data and does not
change any data in the payroll results.
Output
The preliminary program DME creates a payment run that contains payment data. You can
identify every payment run using a combination of the program run date and identification
feature. The identification feature originates from the six-digit system time when you execute
the preliminary program DME. The system replaces the last digit of the six-digit system time
in the identification feature with the letter P.
You start the preliminary program DME at 09:25:12 on 04.14.2000. You can identify the
payment run that the program creates using a combination of the program run date
(04.14.2000) and identification feature (09251P).
The preliminary program DME saves payment data contained in a payment run in the
following tables:
Control Records for the Payment Program (REGUV)
Settlement Data from Payment Program (REGUH)

Processed Items from Payment Program (REGUP)
The payment medium programs in Financial Accounting further process the data in the above
tables. For more information, see Payments (FI-BL) [External].
Activities
To start the preliminary program DME, on the SAP Easy Access screen, choose Human
Resources Payroll Europe Russia Payroll Bank Transfer Preprogram DME .
More Information
Repeating a Payment Run [Page 152]

Repeating a Payment Run
Use
If a payment run was not carried out correctly (for example, because of a
program termination), you have to repeat this payment run.
Prerequisites
When you created the payment run that you now want to repeat, you marked
the Set Flag for Transfers indicator.
Procedure
...
1. Make the same settings on the Preliminary Program DME [External] selection screen
that you made when you created the original payment run.
2. In the Repeat Run: Date and Time fields, enter the date and time for the payment run to
be repeated.
The system uses this entry to evaluate the entries in the Payment Information table
(BT) which the preliminary program DME marked with data and time, but for which the
date and time correspond to your entries in the Repeat Run: Date and Time fields.
3. If you only want to evaluate entries in the Payment Information table (BT) which have
already been marked, select the Flagged Records Only indicator.
If you do not set this indicator, the system also evaluates the entries in the Payment
Information table (BT) which are still not marked with date and time.
4. Choose .
If you do not know the date and time for the payment run to be repeated, proceed
as follows:
...
1. Use the Display Payroll Results [External] program (Report

H99_DISPLAY_PAYRESULT) to display a payroll result (for any employee) that was
evaluated during the original payment run.
2. Display the Payment Information table (BT).
3. Select an entry from the Payment Information table (BT) which the preliminary program
DME marked with date and time when creating the original payment run.
4. Make a note of the values in the Date and Time fields so that you can enter them in the
Repeat Run: Date and Time fields on the Preliminary Program DME selection screen.

Wage and Salary Payments
Resources Payroll (PY) Payroll Other Countries (PY-XX) Subsequent Activities Wage
and Salary Payments .

Tools for the Salary / Remuneration Statement
Resources Payroll (PY) Payroll Other Countries (PY-XX) Subsequent Activities Tools
for the Salary / Remuneration Statement .

Payroll Account (Report RPCKTOx0; HxxCKTO0)
Resources Payroll (PY) Payroll Other Countries (PY-XX) Subsequent Activities
Payroll Account (Report RPCKTOx0; HxxCKTO0) .

Payroll Journal (RPCLJNx0; HxxCLJN0)
Payroll Journal (Report RPCLJNx0; HxxCLJN0) .

Posting to Accounting (PY-XX-DT)
Posting to Accounting (PY-XX-DT) .

Reporting
You use this component to prepare regulatory and tax reports required by the authorities.
The reports allow you to evaluate payroll data and ensure legal compliance, for example, by
preparing forms that you submit to the authorities in the required legal format.
The standard system comprises reports in the following areas:
Personnel Administration Reports [Page 161]
Payroll Reports [Page 167]

Wage Type Reporter
Resources Payroll (PY) Payroll Other Countries (PY-XX) Subsequent Activities Wage
Type Reporter .

Evaluating the Payroll Results Using ITs or the
Logical Database
Resources Payroll (PY) Payroll Other Countries (PY-XX) Reports Evaluating the
Payroll Results Using ITs or the Logical Database .

Personnel Administration Reports
This section contains reports that evaluate personnel data in your company.
Features
Report Description
You use the personnel order reports to evaluate personnel-related

Personnel order data, for example, data in personnel orders that document changes to
reports employees’ jobs and the departments in which they work. For more
information, see Personnel Order Management Forms [Page 162].
You use this report to print out the reverse side of the sickness
certificate for employees who were absent due to sickness. For more
Sickness information about this report, see the online documentation in the
Certificate system.
Reporting
(HUAASIL0) To access this report, on the SAP Easy Access screen, choose
Human Resources Payroll Payroll Ukraine Reporting
Administration Print Sickness Certificate .

Personnel Order Management Forms
You use reports to generate forms that contain data stored in personnel orders. The Ministry
of Statistics requires you to prepare and store forms that contain details about the personnel
actions you initiate in your company. Based on the type of personnel action and the form that
you generate one of the reports below is called.
Since the data for each form must be displayed in a different way and each personnel order
contains different data, each form has its own print output program. The standard system
contains reports that allow you to generate the following forms:
Form Number Description Report
P-1 [Page 164] Applicants you hire and reassign HUAAORDP1
P-3 [Page 165] Periods of vacation your employees take HUAAORDP3
P-4 [Page 166] Employees that you dismiss HUAAORDP4
Integration
The system calls the reports automatically when you print a personnel order from the
maintenance transaction for the Personnel Orders infotype (0298).
The reports read organizational data from the Legal Properties infotype (1656) and report
results at personnel assignment level.
Prerequisites
General Settings
You have initiated personnel actions and created corresponding personnel orders in the
Personnel Orders infotype (0298).
In addition, you have made the following settings:
You have assigned action types and reasons to groups as required. You make this
setting in Customizing for Payroll Ukraine, under Reporting Personnel
Administration Personnel Order Management Assign Actions to Groups .
You have defined the print output programs for the given personnel action. You make
this setting in Customizing for Payroll Ukraine, under Reporting Personnel
Administration Personnel Order Management Determine Print Output Programs
for Personnel Orders .
If you want to set fixed values for some fields, for example, the manager’s name and
position, you must have set up additional form parameters accordingly. You make this
setting in Customizing for Payroll Ukraine, under Reporting Personnel
Administration Personnel Order Management Determine Default Additional Form
Parameters .
If you want to modify delivered procedures for filling fields, you must have set up the
corresponding DAQ subapplication in Customizing for Payroll Ukraine, under
Reporting Personnel Administration Personnel Order Management Set Up
DAQ Subapplications .
If you want to change the default position object as a source of position information,
you must have made the corresponding setting in Customizing for Payroll Ukraine,

under Reporting Personnel Administration Personnel Order Management
Determine Source for Text of Position .
Form-Specific Settings
Form P-1 (HUAAORDP1) [Page 164]
Features
Output
The reports output Smart Forms in the required legal format.
More Information
Personnel Orders (Infotype 0298): Ukraine-Specific Features [Page 26]

Form P-1 (HUAAORDP1)
This report enables you to prepare form P-1 as a Smart Form in the required legal format.
The Ministry of Statistics requires all companies to keep records of changes to their
workforce. When you hire or reassign an employee, you create a personnel order and
generate form P-1. Form P-1 contains data about new employees, such as their personal
data, position in your company, and salary.
Prerequisites
You have made the general settings described in Personnel Order Management
Forms [Page 162].
To print the form, you have made the settings in Customizing for Payroll Ukraine,
Form for Hiring Order (P-1) .

The Ministry of Statistics requires all companies to keep records of vacation that their
employees take. This report reads data in the Absences [Page 30] infotype (2001), and in the
case of the quota available to an employee, the Absence Quotas [External] infotype (2006).
Prerequisites
You have made the general settings described in Personnel Order Management
Forms [Page 162].
To print the form, you have made the settings in Customizing for Payroll Ukraine,
Form for Vacation Order (P-3) .

The Ministry of Statistics requires all companies to keep records of changes to their
workforce. When you terminate an employment contract or an employee hands in his or her
notice, you create a personnel order and generate form P-4. Form P-4 contains data about
employees who leave your company, for example, employees’ personal data, their position in
your company, and the reason for the termination of the employment contract.
Prerequisites
You have made the general settings described in Personnel Order Management Forms [Page
162].

Payroll Reports
This section contains reports that you use to evaluate payroll-related data and to file official
reports with the authorities, for example, the State Tax Administration of Ukraine (STAU) and
the Pension Fund of Ukraine (PFU).
Features
Report Description
You use this report to prepare the pension fund declaration that you
submit to the PFU on a monthly basis.
The declaration contains information about every employee for whom the
company paid pension contributions in the given month. It also shows
Pension Fund
the amounts of contribution paid by the employer and the employees as
Declaration
well as the data of employees who were hired or who left the company
(HUALPFD0)
during that month.
To access this report, on the SAP Easy Access screen, choose

Human Resources Payroll Europe Ukraine Reporting
Payroll Pension Fund Declaration .
You use this report to prepare the income tax calculation in the format
that the STAU requires.
The report reads your company’s organizational data that you store in
Form 1DF
the Legal Properties [Page 32] (1656) infotype.
(HUAL1DF0)
To access this report, on the SAP Easy Access screen, choose
Human Resources Payroll Europe Ukraine Reporting
Payroll Form 1DF .
For more information about the reports, see the report documentation in the system.

HR Process Workbench
Payroll in a Background Operation HR Process Workbench .

Interface Toolbox for Human Resources (PX-XX-
TL)
Resources Payroll (PY) Payroll Other Countries (PY-XX) Interface Toolbox for Human
Resources (PX-XX-TL) .

Glossary
The table below contains a list of the terms and corresponding glossary definitions that are
specific to Ukraine.
Term Definition
The starting point for calculating indexation payments.
The base period is one of the following payroll periods:

base period The payroll period in which an employee is hired
The payroll period when an employee’s salary increase exceeds

the indexation amount
A type of employment contract that is concluded for ad-hoc work. Civil

contracts are regulated by civil law, and in contrast to employment
civil contract contracts, civil contracts cannot be used for regular employees of a
company. Civil contracts are often used for workers in the construction or
service industry.
A statistical estimate of the amount by which prices for certain products

and services rise month on month.
Employers use the consumer price index as the basis for making
consumer price additional payments to their employees. The additional payments, known
index as indexation payments, ensure that an employee’s purchasing power
remains the same following inflation.
The State Statistics Committee of Ukraine publishes the CPI each month,
with a delay of two months.
The result of cumulating the consumer price index (CPI) each month.
The government publishes a threshold percentage for the cumulated CPI.

When the cumulated CPI exceeds the threshold, you determine the
indexation percentage by deducting 100% from the cumulated CPI. You
cumulated CPI
use the indexation percentage to calculate the indexation amount that you
pay an employee.
When the cumulated CPI exceeds the threshold percentage, you reset the
cumulated CPI and start to cumulate the CPI again.
A subordinate unit in an organization.
Subordinate units can have their own official data and in many instances
are classed as separate organizations since they have their own activity
codes, registration data, and so on. The units are always assigned to a
head organization.
detached
subdivision When you prepare legal forms, the authorities require some forms to be
prepared in a consolidated view, in other words, for the head organization
but containing all assigned detached subdivisions.
You prepare other reports, however, at the level of each detached

subdivision and only enter the name of the head organization to which the
subordinate unit is assigned.

Term Definition
In most cases, detached subdivisions are not liable for social insurance
contributions, but instead, another special tax system, for example, the
uniform tax for imputed income (ENVD).
A code used in Ukraine to classify the products and services that the
DKPP code organization sells to its customers. This code is approved by the order of
the State Committee of Standards of Ukraine.
The unified social contribution in Ukraine that employers and employees

make.
ESV Employers calculate contributions using the required base amount – as

defined by legislation - and transfer the contributions to the social
insurance fund. Employers pay the largest percentage of the contributions
and employees pay only a small percentage of the contributions.
Describes the entity at the top of a company's organizational structure.

head unit of The head unit is usually a company's head office or headquarters. Some
organization companies also comprise detached subdivisions, which are responsible
for their own reporting activities.
A tax number in Ukraine issued to legal persons and natural persons

alike.
IIN
The authorities use the tax number to administer taxes, which means that
the tax number must be entered on all tax-related documents that you file
with the authorities.
A difference in income tax amounts calculated by the following calculation

methods:
In accordance with regulations effective in the payroll period to

which the tax liability applies
income tax
discrepancy In accordance with regulations effective in the payroll period in
which the tax liability arises
Income tax discrepancies can arise if you do retroactive accounting for a

payroll period past, and calculate income tax using both of the above
methods.
The payment that you make to employees to ensure that an employee’s

purchasing power remains the same following inflation.
indexation
amount You calculate the indexation amount by multiplying an employee’s actual
earnings by the indexation percentage that you derive from the consumer
price index (CPI).
The percentage that you apply to an employee’s salary to calculate the

indexation amount that applies to an employee’ salary.
indexation According to legislation, you calculate the indexation percentage when the
percentage cumulated consumer price index (CPI) exceeds a legally defined
threshold. For example, assume that the threshold is 101%, the CPI in
March is 100.5%, and the CPI in April is 100.8%. The cumulated CPI in
April is 101.3%. The increase in the indexation percentage in April is 1.3%

Term Definition
(cumulated CPI (101.3%) less 100%).
You cumulate the indexation percentage that applies to an employee’s

salary each time the cumulative CPI exceeds the threshold for calculating
indexation.
The part of an employee’s income for which you have calculated an

indexation amount to counteract inflation.
Example
indexed income Assume that an employee has jobs with two different employers: a main
employer and a secondary employer.
The main employer calculates the required indexation amount for the
employee first.
A code used in Ukraine to classify the types of properties.
Example
KFV code 10: Private Property
31: State Property
32: Community Property
A code used in Ukraine to classify Ukrainian regions, districts, and cities,

for statistical and statutory reporting purposes.
The first two digits denote the region, the next three digits the district, and
the last three digits the town or city.
KOATUU code Example
80: Kiev
80 300: Kiev's administrative districts
80 361: Holosijivsky district
A code used in Ukraine to identify the legal and organizational form of the
business that the organization pursues.
Example
KOPFG code
231: Open Joint Stock Corporation
845: Charitable Organization
KPZED code A code used in Ukraine to classify services of foreign trade activities.
A code used in Ukraine to classify what business activities a company is

engaged in, according to the Classification of Economic Activities.
KVED code The codes cover different types of business activities from all areas,
where enterprises are classified as mining and quarrying (1),
manufacturing (2), and services (3).

Term Definition
The State Statistics Committee introduced the KVED classification in

2001, which is a more up-to-date system than the previous ZKGNG
classification.
The minimum amount that each person must receive per month to ensure
the normal functioning of a person’s body.
The living wage covers food products, non-food products, and a set of
services that are required to meet the basic social and cultural needs of a
person. The government uses a set of official criteria to determine the
living wage
living wage for the main social and demographic groups in society, and
revises the living wage in accordance with increases in the consumer
price index.
In contrast to a minimum wage, the living wage considers the actual cost
of items that a person requires each month.
The minimum amount that an employer is allowed to pay an employee.

The government determines the amount, which is usually expressed as a
monthly amount. There are different kinds of minimum amounts:
The minimum amount that employers are allowed to pay

employees
MROT
The base amount that is used to calculate taxes, privileges, and
garnishments
The base amount that is used to calculate grants and other social
payments
A description of the standard duration and composition of an employee’s

working time, as defined by legislation.
In Ukraine, the most common normative work schedule comprises 8 hours

per day, 5 days per week. On days before official public holidays, the
normative work
normative work schedule comprises a 7-hour workday.
schedule
Normative work schedules represent the standard work schedules on
which personal work schedules and subsequent processes are based. For
example, the system uses normative work schedules to calculate some
absences, payments, and other compensation.
A means of fine tuning the benefits to which employees in a given social

insurance group are entitled.
Example
You use the social insurance group to determine the amount of pay an
social insurance employee receives when he or she is sick. The social insurance group is
group modifier based on the length of time an employee has worked, that is on their
seniority.
If the employee is a single mother, she is entitled to a higher level of sick

pay for a given level of seniority than a parent who is married.
You use the social insurance group modifier to grant the single mother the
same percentage of sick pay as someone in a higher social insurance

Term Definition
group.
The payments that employees receive when they are unable to work due
social insurance to one of the reasons covered by social insurance. For example, when
payments employees are sick or are on maternity leave, they are entitled to a certain
amount of sick pay and maternity pay respectively.
The number of years for which employers have made contributions to the
social insurance fund for an employee.
social insurance
seniority An employee’s social insurance seniority is not bound to a particular
employer, and determines the level of pay that an employee receives
when he or she is sick, for example.
A code used in Ukraine to identify the Ministry, or other central authorities

SPODU code that the organization is subordinated to, according to the system of
notation of state administrative bodies.
The official body that is responsible for collecting statistical data about the
State Statistics population.
Committee of
Ukraine Companies are required by law to provide the State Statistics Committee
with certain data about their employees for statistical purposes.
The classification of a tax or social insurance contribution that employers

calculate. For example, there are tax classes for different rates of income
tax and social insurance contributions.
Depending on the type of tax or social insurance contribution that a tax

tax class class represents, you use tax classes to calculate and transfer amounts to
the required body or to deduct amounts (for example, income tax) from an
employee’s salary.
The system groups together the tax classes that apply to a given set of
employees in tax schemas.
A benefit that entitles employees to a reduction in tax, for example, in

income tax.
tax privilege If employees are entitled to tax privileges, for example, when they
purchase real estate, the system reduces the amount on which the
income tax calculation is based, thereby reducing the amount of income
tax that the system deducts from an employee’s salary.
A range of tax rates that relate to different amounts. For example, the
tax scale applicable tax rate increases in line with the level of an employee’s
income.
A group of tax classes that you use for different types of employees. For
example, there are different tax schemas for citizens of the country and
for foreign citizens.
tax schema You use tax schemas to assign different sets of tax classes to different
employees based on the requirements of legislation. For example, the
rates for income tax deductions and social insurance contributions that
you use for citizens of the country differ from the rates that you use for
foreign citizens. To enable the system to use the different rates correctly,

Term Definition
you assign different tax schemas to the various types of employees in
your organization.
A code used in Ukraine to classify what business activities a company is

engaged in, according to the Classifier of Branches of the National
Economy. The codes cover different types of business activities from all
areas, where the economic activities are divided into production and non-
ZKGNG code
production spheres.
The ZKGNG classification has been replaced by the KVED classification,

which was introduced by the State Statistics Committee in 2001.

PYUA

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

PYUA

Transféré par

Droits d'auteur :

Formats disponibles

Payroll Ukraine (PY-UA)

Document Version: 2.0 – 16.10.2012

SAP Library document classification: PUBLIC

IOS is a registered trademark of Cisco Systems Inc.

(C) SAP AG HELPX.PYUA 2

INTERMEC is a registered trademark of Intermec Technologies Corporation.

Wi-Fi is a registered trademark of Wi-Fi Alliance.

Bluetooth is a registered trademark of Bluetooth SIG Inc.

Motorola is a registered trademark of Motorola Trademark Holdings LLC.

Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH.

(C) SAP AG HELPX.PYUA 3

(C) SAP AG HELPX.PYUA 5

(C) SAP AG HELPX.PYUA 6

(C) SAP AG HELPX.PYUA 7

(C) SAP AG HELPX.PYUA 8

Other SAP Components

Generate and evaluate an employee’s net pay

Calculate contributions and taxes

Create remuneration statements

Create reports for the State Tax Administration of Ukraine

Create reports for the Ukrainian pension fund

Prepare data for the Ministry of Statistics of Ukraine

(C) SAP AG HELPX.PYUA 9

(C) SAP AG HELPX.PYUA 10

(C) SAP AG HELPX.PYUA 11

(C) SAP AG HELPX.PYUA 12

(C) SAP AG HELPX.PYUA 13

(C) SAP AG HELPX.PYUA 14

(C) SAP AG HELPX.PYUA 15

(C) SAP AG HELPX.PYUA 16

(C) SAP AG HELPX.PYUA 17

The international info group contains a user

Organizational The international info group contains a user

The international info group contains a user

To ensure that the leaving date is entered

Shows an example of a personnel action that

A dynamic action that contains the necessary

(C) SAP AG HELPX.PYUA 18

(C) SAP AG HELPX.PYUA 19

Passport of Ukrainian citizens (subtype UAIC)

Taypayer’s identification card (subtype UAIN)

Social insurance certificate (subtype UASC)

(C) SAP AG HELPX.PYUA 20

(C) SAP AG HELPX.PYUA 21

(C) SAP AG HELPX.PYUA 22

The initial balance of a claim

The details of periodic deductions

(C) SAP AG HELPX.PYUA 23

Information about the originator of the garnishment document

Details about the garnishment release date

Multiple Garnishment Documents

Processing of the Priorities and Deduction Group Tables (UAPRI) function

Summarize Deductions in Table AIT (UADL) personnel calculation rule

Process Garnishments According to Priorities (UADE) personnel calculation rule

Calculate Balance of Deductions (UADR) personnel calculation rule

(C) SAP AG HELPX.PYUA 24

(C) SAP AG HELPX.PYUA 25

Details About Personnel Actions

Numbering of Personnel Orders

Printing of Personnel Orders

(C) SAP AG HELPX.PYUA 26

Time Quota Compensation during Leaving Action

(C) SAP AG HELPX.PYUA 27

Using a dialog box