Payroll USA Configuration
Payroll USA Configuration
Payroll USA Configuration
Document
1.0 Introduction……………………………………………………………………………………………..3
2.0 Payroll Organization .................................................................................................................. 3
2.1 Payroll Area ......................................................................................................................... 3
2.2 Default Payroll Area............................................................................................................ 4
2.3 Payroll Periods.................................................................................................................... 4
2.4 Employee Subgroup Groupings for PCR and CAP ......................................................... 5
2.5 Process Models for Payroll................................................................................................ 5
2.6 Hourly Rates with several Decimal Places....................................................................... 5
3.0 Wage Types ................................................................................................................................ 5
3.1 Wage Types from Table T511 or T512T - Report RPDLGA00......................................... 5
3.1 Use of Wage Types in Payroll - Report RPDLGA20 ........................................................ 5
3.2 Wage Types with Processing Class in Payroll - Report RPDLGA40 ............................. 6
4.0 Garnishments ............................................................................................................................. 6
4.1 Garnishment Document Category .................................................................................... 6
4.2 Garnishment Originator ..................................................................................................... 6
4.3 Garnishment Remittance Rule .......................................................................................... 6
4.4 Garnishment Government Rule......................................................................................... 7
4.5 Modifier for Company Rule................................................................................................ 7
4.6 Garnishment Company Rule ............................................................................................. 7
4.7 Garnishment Service Charge ............................................................................................ 8
4.8 Garnishment Service Charge Government Rule ............................................................. 8
4.9 Modifier Service Charge for Company Rule .................................................................... 8
4.10 Garnishment Service Charge Company Rule ................................................................ 8
4.11 Garnishment Number Ranges ......................................................................................... 8
4.12 Garnishment Wage Types................................................................................................ 9
4.13 Garnishment Order Types ............................................................................................... 9
4.14 Garnishment – Adjustable Model for Disposable Net................................................... 10
4.15 Garnishment – Define Levy Form Text ........................................................................... 10
4.16 Garnishment – Special Rules .......................................................................................... 11
4.17 Garnishment – Adjustment Wage Types........................................................................ 12
4.18 Garnishment – Default Values......................................................................................... 13
4.19 Garnishment – Check Priority/Third-Party Remittance for order types...................... 13
4.20 Garnishment – Garnishment Letters .............................................................................. 14
5.0 Off-Cycle ..................................................................................................................................... 14
6.0 Year-End Adjustments Workbench .......................................................................................... 14
7.0 Workers’ Compensation............................................................................................................ 14
9.0 Tax ............................................................................................................................................... 16
9.1 Tax – Tax Company ............................................................................................................ 18
9.2 Tax – Maintain Tax Processing Classes........................................................................... 19
9.3 Tax – Maintain States of Operation................................................................................... 19
9.4 Tax – Tax Authorities ......................................................................................................... 19
10.0 Payroll Posting to FI/CO .......................................................................................................... 27
10.1 Activities In HR System.................................................................................................... 27
10.2 Activities In FI System...................................................................................................... 29
11.0 Electronic Funds Transfer (EFT)/Checks .............................................................................. 29
12.0 Payroll Payments to Third parties .......................................................................................... 30
13.0 Tax Reporter ............................................................................................................................. 30
14.0 Forms, Reports, Interfaces, Conversions, Enhancements (FRICE) ................................... 30
14.1 Forms ................................................................................................................................. 30
14.2 Reports .............................................................................................................................. 30
14.3 Interfaces ........................................................................................................................... 33
14.4 Conversions ...................................................................................................................... 33
14.5 Enhancements .................................................................................................................. 33
15.0 Security and Authorizations ................................................................................................... 33
16.0 Schema and Rule Customization ........................................................................................... 33
Page 2 of 33
ASAP Business Blueprint – Payroll (USA)
1.0 Introduction
The SAP US Payroll component allows you to process payroll for employees in the United States, using data
from SAP Personnel Administration and Benefits under a wide variety of configurations. The SAP Payroll
system also offers a number of standard payroll reports. The Tax Reporter component allows you to generate
all required state and federal tax forms, such as SUI reports and W-2s. US Payroll uses an interface to a
separate BSI Tax Factory database to calculate taxes. There are also interfaces to other SAP modules such as
Financial Accounting and Controlling. This document deals with the design of the SAP US Payroll module for
GMR Infotech Tire Manufacturing Company, USA.
At GMR Infotech, the SAP system will be used to run all payroll processes, including net payroll and Tax
Reporter.
The Payroll Area defines the frequency in which an employee may be paid in an Organization.
Following Payroll Areas would be used:
Table V_T549A
Transaction Code SPRO
Menu Path IMG -> Payroll -> Payroll: USA -> Basic Settings -> Payroll
Organization -> Assign new payroll accounting areas to period modifier
-> Check Payroll Areas
Details of Configuration Here, the date modifier is assigned to payroll Area.
Period Parameter
Table V_T549R
Transaction Code SPRO
Menu Path IMG -> Payroll -> Payroll: USA -> Basic Settings -> Payroll
Organization -> Define period modifiers
Details of Configuration Period parameter is defined for specific payroll periods with start and
end dates. If the payrolls run for all employees are in the same time
interval, then only require one period parameter. Attached sheet has the
Period Modifiers defined for GMR Infotech.
Date Modifier
Table V_T549L
Transaction Code SPRO
Menu Path IMG -> Payroll -> Payroll: USA -> Basic Settings -> Payroll
Organization -> Define Date Modifiers.
Details of Configuration Different date modifiers is required if different payment dates for various
payroll areas with same period parameters is required (for example, the
parameter weekly).
Page 3 of 33
ASAP Business Blueprint – Payroll (USA)
Based on the assignment of the employee to the organization, the following payroll areas will default
on infotype 1 (Organization Assignment):
Feature ABKRS
Transaction Code PE03
Menu Path IMG -> Personnel Management -> Personnel Administration ->
Organizational Assignment -> Check Default Payroll Area
Details of Configuration Here, the table maintenance view of feature ABKRS.
Country Group 10 Employee Group (PERSG) Personnel Area (WERKS) Employee Sub
Group (PERSK) Payroll Area (ABKRS)
Control Records for all the Payroll areas are to be created with an initial pay period of 01.2006 and
earliest retroactive accounting period of 01.2006. The earliest retroactive date will be modified later on
based on the actual go-live date.
Payroll periods for all payroll areas will be generated from 01.2006 to the last period of 2012. These
are to be generated per following pattern:
U1 – pay period 19.2006 is from 09/04/2006 to 09/17/2006, pay date is 09/22/2006. Select payday rule
3 with number of days = 5
U3 – pay period 37.2006 is from 09/04/2006 to 09/10/2006, pay date is 09/14/2006. Select payday rule
3 with number of days = 4
Page 4 of 33
ASAP Business Blueprint – Payroll (USA)
The Employee Subgroup groupings for Personnel Calculation Rule are used in payroll processing.
These values are fixed and should not be changed. A value of ‘1’ signifies hourly wage earners.
The collective agreement provisions are used to group employees with same pay scale requirements.
The value of 1 will be used for Union employees.
Table/View V_503_B
Transaction Code SPRO
Menu Path IMG -> Personnel Management -> Personnel Administration -> Payroll
Data -> Define EE Subgroup Grouping for PCR and Coll.Agrmt.Prov.
Details of Configuration
The Union calculations may require hourly rates with 4 decimal places, if the union configuration
cannot be set up to handle percentage deductions. In that case, a new currency USDN may be needed
that supports this requirement. This also needs to be mapped to the PS Type, PS Area and ESG for
CAP. This will be revisited following finalization of the union configuration for payroll.
Report RPDLGA00 lists the wage types defined in tables T511 or T512T. Permitted infotypes and the
definitions in table T512W can also be displayed for each wage type.
The basic list contains some of the features from table T511 if the wage type is defined in T511. The text from
T512T is also shown.
You can only use this report to evaluate the wage type characteristics that determine the behaviour of a wage
type in Payroll, and not the wage type characteristics which define the behaviour of a wage type in online
processing.
Processing Class:
Evaluation Class:
Cumulation Wage Types:
Page 5 of 33
ASAP Business Blueprint – Payroll (USA)
T512W: Cumulations, Evaluation Classes and Processing Classes. Report RPDLGA40 can be used to set up
and manage wage types. It provides information on
the cumulation wage types and evaluation and processing classes of the individual wage types
the wage types of each cumulation wage type and the processing or evaluation class.
The report can therefore be used to answer the following questions:
Which cumulations and evaluation and processing classes are available for a particular wage type or
group of wage types?
Which wage types use a specific cumulation wage type or specification of an evaluation or
processing class?
Report RPDLGA40 uses table T512W 'Wage Type Valuation'. Wage type texts are read from table T512T.
4.0 Garnishments
The categories that are used to identify various garnishment documents are created in the Document Category.
Table/View V_T5UG1
Transaction Code SPRO
Menu Path IMG -> Payroll -> Payroll: USA -> Garnishments -> Master Data ->
Document -> Create document category
Details of Configuration
The originator describes the legal entity that has issued the garnishment document.
Table/View T5UGM
Transaction Code SPRO
Menu Path IMG -> Payroll -> Payroll: USA -> Garnishments -> Master Data ->
Document -> Create originator
Details of Configuration
To create the rules that will apply during bank transfer of the garnished amounts. A rule contains the features
that HR creditors require to define the due date of remittances and the payment method. One rule can be used
for several HR creditors
Table/View V_T51RK
Transaction Code SPRO
Menu Path IMG -> Payroll -> Payroll: USA -> Garnishments -> Master Data ->
Document -> Remittance Rules for Bank Transfer -> Define remittance rule
Details of Configuration
A rule ID defines:
Page 6 of 33
ASAP Business Blueprint – Payroll (USA)
To define any rules that has been established by government bodies for garnishment remittance. These rules
are applied by default if no company remittance rules exist for the Garnishment.
Table/View V_T5UG7
Transaction Code SPRO
Menu Path IMG -> Payroll -> Payroll: USA -> Garnishments -> Master Data ->
Document -> Remittance Rules for Bank Transfer -> Create government
rule
Details of Configuration
To define you define the modifier that applies to the company remittance rule. Using this modifier, you can
create new company remittance rules as often as required
To create the company remittance rule. This is the remittance rule to which the system will default if no
equivalent rule is specified in the Garnishment Document infotype. We recommend that you use the company
remittance rule only if you want to override the government remittance rule
Table/View V_T5UG8
Transaction Code SPRO
Menu Path IMG -> Payroll -> Payroll: USA -> Garnishments -> Master Data ->
Document -> Remittance Rules for Bank Transfer -> Create company rule
Details of Configuration
Page 7 of 33
ASAP Business Blueprint – Payroll (USA)
For each garnishment, a service charge can be levied through the corresponding field in the Garnishment
Document infotype (Infotype 0194). If you do not make an entry in this field, no service charge will be
calculated.
However, if you do enter a service charge in Infotype 0194, the service charge rule will be derived from the
Company Service Charge view. If no company service charge exists, then the service charge will be derived
from the Government Service Charge view. If a company service charge and a government service charge are
both available, then the smaller of the two amounts will be applied
Table/View V_T5UGC
Transaction Code SPRO
Menu Path IMG -> Payroll -> Payroll: USA -> Garnishments -> Master Data ->
Document -> Service Charges -> Create service charge texts
Details of Configuration
To define create the modifier for the company service charge rule that will apply to garnishments in your
enterprise. Using this modifier, you can create new company service charge rules as often as required
You create the company service charge rule. This rule determines the additional amount that will be levied
upon garnishments and remitted to your enterprise
Table/View V_T5UGG
Transaction Code SPRO
Menu Path IMG -> Payroll -> Payroll: USA -> Garnishments -> Master Data ->
Document -> Service Charges -> Create company rule
Details of Configuration
Page 8 of 33
ASAP Business Blueprint – Payroll (USA)
You create two number ranges that are required to process garnishments. The first number range applies to
the garnishment transfer, and the second number range applies to the vendor subgroup
To create the wage types for the wage type catalog and define which wage types will apply to garnishment
orders in your system
Table/View V_512W_T
Transaction Code SPRO
Menu Path IMG -> Payroll -> Payroll: USA -> Garnishments -> Master Data -> Order
Types -> Wage Types -> Check wage type texts
Details of Configuration
Table/View V_52D7_B
Transaction Code SPRO
Menu Path IMG -> Payroll -> Payroll: USA -> Garnishments -> Master Data -> Order
Types -> Wage Types -> Check Wage Type Catalog -> Check wage type
group 'Order Type'
Details of Configuration
To create the garnishment order types required by your enterprise. Order types are used to describe the
various deductions that exist within a garnishment document
Table/View V_T5UGG
Transaction Code SPRO
Page 9 of 33
ASAP Business Blueprint – Payroll (USA)
Menu Path IMG -> Payroll -> Payroll: USA -> Garnishments -> Master Data -> Order
Types -> Create order types
Details of Configuration
In this section, you will learn how to adjust the disposable net. To do so, you must create an adjustment model
in the two subsequent steps. If you do not need to adjust the disposable net, you may omit this section and
proceed to the Non-Exempt Amount section. The disposable net is formed in conjunction with values 1 and 2 of
processing class 59. For additional information on this topic, refer to the step in which you Check garnish ability
of wage types
Create the model for determining the garnishable amount for Federal or State Levies.
Garnishment – Define text for the filing status from the levy form
Create the model for determining the garnishable amount for Federal or State Levies.
Page 10 of 33
ASAP Business Blueprint – Payroll (USA)
Menu Path IMG -> Payroll -> Payroll: USA -> Garnishments -> Master Data -> Order
Types -> Garnishable Amounts -> Non-Exempt Amount -> Levy -> Create
exempt amount from levy
Details of Configuration
Can store special rules for determining the garnishable amount. You use a special rule in cases where you are
not able to use a model. Here you will define the fields that appear in the infotype Garnishment Order, how
these fields respond to special rules, and how you can use these fields to determine the garnishable amount.
create the special rules with text and define which fields are to appear in the infotype Garnishment Order.
In this step, you determine the garnishable amount for a special rule. A rule can consist of one or more lines.
You can link two fields in one line by using an Operation (e.g. addition, subtraction). These two fields can either
be the fields Operand 1 or the amount of a wage type and the fields Operand 2 or a fixed value (Value).
You can use the fields in the infotype Garnishment Order for operand 1 and operand 2. You defined these
fields in the previous step of the IMG.
You can temporarily store the intermediate results of a line in the field Result. You can use this for operand 1
or operand 2 in any following lines.
The result may not be stored in the Result field in the last line.
In this step, create a model for determining the garnishable amount. You can store your entries in five blocks.
For each of the first four blocks (Limit 1, Limit 2, Federal Minimum Wage and Special Non-exempt), the system
determines an individual garnishable amount each time and uses the lowest amount as the result for the
garnishable amount. A garnishable amount determined in this way is then adjusted by the amount of the fifth
block (Additional Amount).
Page 11 of 33
ASAP Business Blueprint – Payroll (USA)
Menu Path IMG -> Payroll -> Payroll: USA -> Garnishable Amounts -> Non-Exempt
Amount -> Create model for the nonexempt amount
Details of Configuration
In this step, create the Federal Hourly Wage. This amount is used to determine the garnishable amount in
accordance with the Federal Minimum Wage.
In this step, create the rules that will be used within your system to determine the garnishable (non-exempt)
amount. If necessary, you may assign a wage type model to the rule to adjust the disposable net.
In this step, assign the order types Service Charge to the document category. If you have made the entry in
the infotype Garnishment Document that the Service Charge is to be calculated, then you must assign the
document category to the order types. The Service charge in the garnishment results will be stored under this
order type.
Page 12 of 33
ASAP Business Blueprint – Payroll (USA)
You define the defaults that are to be used when you create a garnishment using the infotypes.
Third-Party Remittance
Processing class 73
o All wage types that are transferred must be assigned the value 1.
o Wage types that are not transferred must have no value for this processing class.
Processing class 78
o All wage types that are transferred must be assigned the value 1.
o Wage types that are not transferred must have no value for this processing class.
Priority
Priority
o With the exception of wage types for voluntary garnishments, all wage types must be
assigned the value A, which denotes highest priority.
o Wage types for voluntary garnishments may be assigned a lower priority, such as C.
Arrears
o All wage types must be assigned the value 4.
Execute this step to check the priority value for your adjustment wage types.
Priority
o All wage types must be assigned the value 0
Page 13 of 33
ASAP Business Blueprint – Payroll (USA)
Here configure the processing classes of the wage types in the Order Type and Adjustment wage type
groups. The configurations made in this step determine the release of these wage types into payroll.
Execute this step to check the values assigned to your wage types for the following processing classes.
Processing class 6
o This processing class determines whether the wage type will be transferred from table LRT
in previous payroll periods.
Processing class 30
o This processing class governs the cumulation of the wage type in payroll.
Processing class 32
o This processing class determines whether the wage type will be transferred to application
components FI / CO for further processing.
Third-Party Remittance
5.0 Off-Cycle
Standard SAP
The year end adjustments workbench will be set up in (Phase 2) of the project.
The US Personnel Administration has a standard Workers’ Compensation (WC) report that produces output
as below:
Page 14 of 33
ASAP Business Blueprint – Payroll (USA)
The process for calculating WC wages and premiums in the standard SAP HR system is as follows:
1. When setting up an employee in HR master data, you assign that employee to a Position, Job and
Organizational Unit. WC codes were already assigned to the Job, Position or Organizational Unit during
Configuration.
2. Run payroll. No actual WC calculations are made during the payroll run. The payroll results merely
provide data for the next step.
3. Run RPLWCOU0 (US WC Report). This report uses the payroll results to calculate WC wages and
premiums based on the criteria you specify in the report, and the settings made during Configuration.
The requirements for calculating WC premiums and the WC report output are different from what the
standard system provides. This has been identified as a gap. The actual implementation of the custom solution
will be decided during the implementation phase. The requirements are described below:
WC State: The UI state(s) from the employee master that falls within the report selection period. This can also
be found on the payroll cluster table TAXR.
Page 15 of 33
ASAP Business Blueprint – Payroll (USA)
WC (Classification) Code: This needs to be set up at the Organization Unit level for employees in personnel
area TRU1 (TSI) and TRU2 (TCC). Any overrides will need to be set up at the position or job level. For
employees in personnel areas TRU3 (TFS) and TRU4 (AIS), this needs to be set up at the job level. For this
purpose, the generic jobs for Union employees will be more than each, one for each trade level or
combination.
Gross Wages – ST: For all US states except WA, this is the straight time wages for each employee that falls
within the report selection period. For the state of WA, the earnings field should be left blank, only the hours
field should be populated with the ST hours. These can be obtained from the payroll cluster table RT.
Gross Wages – OT: For all US states except WA, this is the overtime wages for each employee that falls
within the report selection period. For the state of WA, the earnings field should be left blank, only the hours
field should be populated with the OT hours. These can be obtained from the payroll cluster table RT.
Gross Wages – DT: For all US states except WA, this is the double time wages for each employee that falls
within the report selection period. For the state of WA, the earnings field should be left blank, only the hours
field should be populated with the DT hours. These can be obtained from the payroll cluster table RT.
WC Hours – ST/OT/DT: Need to be printed only for the state of WA. Should be left blank for all other states.
Source will be the payroll cluster table RT.
WC Rate: For the purpose of calculating WC premiums, one single WC rate is used by Tracer. This is valid
for all WC classification codes. This is valid for all states, but for WA.
Calculation of WC Premiums: The calculation of WC premiums will be done outside the system, using the
WC rate.
The following report output is needed for employees under OCIP projects (OCIP Report):
The report output should be ALV, to facilitate totals, sub-totals and sorting.
9.0 Tax
SAP uses the BSI TaxFactory 7.0 tax calculation engine for calculating tax. Tracer has to procure and
separately install the BSI executable along with the BSI database for this purpose. Additionally Tracer has to
regularly apply the BSI Tax Update Bulletins (TUBs), both in the SAP and the BSI databases, to keep the tax
tables up-to-date.
Before the SAP Payroll component sends any data to the BSI TaxFactory for tax calculation, the payroll
driver goes through a number of steps to determine exactly which taxes will be applied for each payment or
deduction wage type. These steps depend largely on how you configure wage types, tax types, tax authorities,
and taxability models in the Tax section of the Payroll: USA IMG. This topic illustrates the process by which
the payroll driver determines which tax calculations will be performed by the BSI tax calculation engine.
Page 16 of 33
ASAP Business Blueprint – Payroll (USA)
Tax Authority Tax model R/W/U Tax Class Tax Type Combo
FED 01 R 0 08
4. Based on the tax type combination included in the taxability model, the payroll driver determines which tax
types must be applied to the wage type amount. The payroll driver sends BSI the wage type amount and the
relevant tax types. In this case, the following data would be sent to BSI for tax calculation:
Page 17 of 33
ASAP Business Blueprint – Payroll (USA)
$1000 06 ER Medicare
5. The BSI tax engine calculates the tax on the wage type amount. The tax types passed to BSI determine
which calculation formulas it uses.
6. BSI returns the results of the tax calculations to the SAP Payroll system, including the tax amounts
calculated for each wage type amount and tax type. This information appears in the payroll log.
Result
The tax wage types determined in this process are stored in the payroll results cluster for the employee. These
tax wage types can also be copied to the tax interface tables where they form the basis for various tax reports
generated by the SAP Tax Reporter component.
Need to maintain the same table entries in the BSI database with the BSI client GUI .
Page 18 of 33
ASAP Business Blueprint – Payroll (USA)
Define federal, state and local employer ID numbers within each tax company in this step.
In this step you set the values for the following processing classes for all tax wage types. This allows
controlling the way the wage types are processed by the payroll system.
In this step you enter the states in which you operate. This data will be used to populate the relevant tax
authorities for your firm.
In this step, you check all tax authorities valid for your organization. Tax authorities defined here are used in
infotypes:
Page 19 of 33
ASAP Business Blueprint – Payroll (USA)
In this step, you can also define the following exemption limit criteria:
In this step, you may check or change the assigned sort number for each authority. The sort number is used to
determine the authority's position on a pay statement.
In this step, you define whether each tax authority requires a withholding form, and whether exemption limits
may be imposed by that authority.
Table/View V_5UTZ_C - W4 and IRS exemption limit indicators for tax authority
Transaction Code SPRO
Menu Path IMG -> Payroll -> Payroll: USA -> Tax -> Tax Data Maintenance -> Tax
Authorities -> Check W-4 and exemption limit indicators
Details of Configuration
In this step, you may designate whether an authority is a US territory. This information is used in payroll for
calculation of certain taxes.
In this step, you can display how each SAP tax authority code is mapped to the corresponding BSI tax
authority code.
Page 20 of 33
ASAP Business Blueprint – Payroll (USA)
Table/View V_BTXTAXC - BSI: Grouping BSI Tax Authorities to SAP Tax Authorities
Transaction Code SPRO
Menu Path IMG -> Payroll -> Payroll: USA -> Tax -> Tax Data Maintenance -> Tax
Authorities -> Check tax authority mapping
Details of Configuration
In this step, you define all valid filing statuses for each tax authority. Filing status is used in Infotypes 0161
(IRS Mandates) and 0210 (W-4 Withholding Information).
Example
In this step, you may view all tax types available in the system. Tax types are used in wage types and in
Infotype 0235 (Other Taxes).
Example
01 Withholding tax
05 Employee Medicare tax
10 Employer unemployment
In this step, you may view all tax types for each tax authority.
Example
Page 21 of 33
ASAP Business Blueprint – Payroll (USA)
SAP recommends that the formula and rounding indicators NOT be maintained. The standard SAP R/3
system uses the correct formula and rounding indicators for each tax type.
In this step, you define work tax areas not included in the standard SAP system. Work tax areas are used in
Infotype 0208 (Work tax area).
Example
Since Alabama contains both city and county tax authorities, only the higher level of the two, counties, are
loaded. For example, residence tax area AL0H (Jefferson County, Alabama) is loaded during the load process,
but city tax authorities within Jefferson County are not loaded. Therefore, if you have employees working in
such a city, you would have to create a new tax area here that includes the required city tax authority as well
as the county, state and federal authorities.
In this step, you assign tax authorities to the work tax areas you defined in the previous step.
Example
Standard settings
The SAP standard provides tax areas which include the state tax authority, and the highest level local
authority within the state
Page 22 of 33
ASAP Business Blueprint – Payroll (USA)
In this step, you assign zip code ranges to new work tax areas. You may also maintain zip code ranges for
existing tax areas.
Example
In this step you define residence tax areas not included in the standard SAP R/3 system. Residence tax areas
are used in infotype 207 (Residence tax area).
Example
Standard settings
The SAP standard provides tax areas which include the federal tax authority, state tax authority and the
highest level local authority within the state.
In this step, you assign tax authorities to the residence tax areas you created in the previous step or add tax
authorities to existing areas.
Example
Standard settings
Page 23 of 33
ASAP Business Blueprint – Payroll (USA)
The SAP standard provides tax areas which include the federal tax authority, state tax authority and the
highest level local authority within the state.
In this step, you assign zip code ranges to new residence tax areas. You may also maintain zip code ranges for
existing tax areas.
Example
The taxability model contains information used to calculate the appropriate taxes for the federal government,
and state and local tax authorities.
Two tables are used to keep SAP and customer taxability model data separate. This ensures that customer
changes are never automatically overwritten and that the SAP model is always available for reference.
The report 'Expand Tax Models' enables you to expand tax authorities and display their respective tax types.
This report can be accessed from the US Payroll menu: Info system -> Tax -> Tax Utilities
In this step, you define tax models for each combination of type of payment, type of employee, and residency
or work. Each combination determines a set of tax types to be used for the model.
Example
Page 24 of 33
ASAP Business Blueprint – Payroll (USA)
Example
In this section, you define unemployment tax rates as well as other tax rates and their ceilings.
Unemployment insurance is a self-adjusting tax. If this tax was under withheld in a period, the system will try
to make up for it in the next period. The system uses the tax rates defined here when performing the self-
adjustment. The ceilings and rates defined here ensure continuity when an employee moves to a different state
with a different tax rate for self-adjusting taxes.
This means the system takes the different tax rates and ceilings into account when looking at the year-to-date
unemployment insurance tax withheld to determine if an underpayment was made in a previous period.
Table/View BTXRATE - BSI: Tax Rates per Company Based on Degree of Experience
Transaction Code SPRO
Menu Path IMG -> Payroll -> Payroll: USA -> Tax -> Tax Data Maintenance ->
Unemployment Insurance -> Define BSI tax company experience rates
Details of Configuration
In this step, you set up deduction priorities and rules for tax wage types. For more information about tax
priority functionality, please refer to the documentation of Function UTPRI (Tax priority (USA)).
Recommendation
Only perform this step if you have particular priorities for a tax authority.
Example
Page 25 of 33
ASAP Business Blueprint – Payroll (USA)
Case 2: Puerto Rico taxes are prioritized lower than other state tax authorities.
Page 26 of 33
ASAP Business Blueprint – Payroll (USA)
...
WI Wisconsin /401 Withholding tax 02 2
WV West Virginia /401 Withholding tax 02 2
PR Puerto Rico /441 Disability Tax 02 0001 1
PR Puerto Rico /401 Withholding tax 02 0001 2
C IN01 Adams /401 Withholding tax 03 2
IN02 Allen /401 Withholding tax 03 2
...
D AL01 Attalla /451 Occupation tax 04 1
AL02 Bessemer /451 Occupation tax 04 1
...
Within FI/CO configuration for Tracer, the Business Area field has been made a required field on the FI
document. It is therefore required that the Business Area be made a required field on IT0001 in Personnel
Administration. This will ensure that the posting document from payroll is not rejected in FI/CO.
The cost centers have also been defined. These cost centers need to be mapped to individual Organization
Units and if required, Positions within Organization Management.
In this step, define the employee groupings for account determination. No need to specify employee groupings
unless it needs to post wage types to various accounts in Financial Accounting (FI) in line with employee
attributes.
If you want to post to FI accounts with reference to a specific employee groupings, you must define an
alphanumeric key of up to three characters for each of the required employee groupings. You then define the
conditions for assigning employees to employee groupings that you have defined for posting to accounting.
(You set conditions according to employee attributes, as defined by entries in the Workplace Basic Pay table
(WPBP). Note that an employee can, at any one time, only be assigned to one employee grouping.
Page 27 of 33
ASAP Business Blueprint – Payroll (USA)
Here you specify which wage types are to be posted, how often they are to be posted within the evaluation of
one payroll result, and the symbolic account to be used for each posting.
Plus/minus sign
The system stores wage types with a plus (+) or minus (-) sign in the payroll result. How specific wage types
are stored depends on how the system processes them during the payroll run. In the standard system, the sign
is usually set correctly for secondary wage types. If you enter a plus sign (+) in the V column, positive
amounts are posted as debits, and negative amounts are posted as credits. If you enter a minus sign (-) in the V
column, positive amounts are posted as credits and negative amounts are posted as debits.
Symbolic account
Indicator specifying whether the cost assignment for infotypes Recurring payments/deductions
(0014), Additional payments (0015), and Employee remuneration information (2010) should be
ignored (table C1).
Page 28 of 33
ASAP Business Blueprint – Payroll (USA)
Accounting components use the posting date to determine the posting period
to which postings are to be made.
In this section, you assign accounts in Accounting to symbolic accounts in Human Resources. According to
this assignment, during posting to Accounting, the accounts in Financial Accounting are assigned to line items
for which symbolic accounting has been performed.
With the exception of the technical accounts, the activities for the various account types contain an identical
step, that is, you must define the rules for the corresponding posting transaction. Note the following
information for carrying out this step:
The Debit/Credit indicator must only be set if you want to post debits and credits to different
accounts. It is not advisable to set this indicator, since in posting to Accounting, only summarized
documents are posted.
If you set the EE group indicator, a further column EE group appears in account assignment. You
must only set this indicator if you want to post to any symbolic account for a specific employee
grouping. You make the relevant settings for posting to symbolic accounts in the step Define
Symbolic Accounts.
The Posting to Accounting done on excel with ETV codes mapped to wage types and GL accounts are as
attached:
Page 29 of 33
ASAP Business Blueprint – Payroll (USA)
Wages and salaries are always paid in the US in USD. No FI payments are made in the HR system.
The prenotification function is not needed. New hires usually receive a physical check for their first payroll,
unless the payroll administrator overrides it for a bank transfer.
A sample paycheck has already been provided. The whole company will have the same layout for all
employees. There are no messages that need to print on the paychecks. Checks are to be sorted by last name
for union employees (AIS). For all other employees, checks are to be sorted by department (organization
unit?) and then by last name of the employee. Printing of paystubs and checks will mostly be done at a single
location. However for large projects, it may become needed to print checks on site. In that case, printers
connected to the SAP R/3 systems will be set up at the project location, for check printing. Tracer has already
verified the capability of printing checks from the SAP system. It is yet to be decided if checks are to be
printed using the SAP system or a third-party software (the “Create-A-Check” software).
There is another requirement to print checks selectively for some employees. It is to be explored how this can
be achieved in the standard system.
Retro payments need to be printed separately on the paystub, retro deductions are to be lumped together.
Currently the payments to third parties (e.g. for tax, benefits, garnishments, etc.) are being made manually to
third parties. No electronic funds transfers are being used.
All benefits (both union and non-union) payments are A/P checks.
All garnishments payments are done with A/P checks.
For payment of Federal taxes, the payroll administrator uploads the taxes for each pay period for each
company to a website.
There are some EFTs presently done through the ADP system. These would be brought over to the manual
process (checks) for the Phase 1 go-live.
Thus, the SAP Third-Party Remittance functionality may not be needed for Phase 1. It will be explored later,
and if required and feasible, will be made a Phase 2 functionality.
Tracer uses the following forms: Form 941, SUI forms, Form 940 and W-2. Historically very few W-2Cs or
941Cs were required.
14.1 Forms
14.2 Reports
The standard reconciliation report will be used. The two wage type applications C941 and CCW2 will
be set up to include all required customer wage types for reconciliation.
Page 30 of 33
ASAP Business Blueprint – Payroll (USA)
The standard wage type reporter will be used to replace various reports that are presently used.
3. Remuneration Statement
The standard US Remuneration Statement program (RPCEDTU0) will be used to print paystubs. The
US Off-Cycle Workbench (transaction PUOC_10) can also be used to display paystubs for employees
individually. The layout of the standard form needs to be modified. The custom layout has been
provided separately.
The standard US payroll results report (RPCLSTRU) will be used to display payroll results per
employee per payroll period.
5. Payroll Journal
This standard SAP report, including the form needs to be set up.
The report is used to fill up standard government forms for State Withholding Taxes. The report is to be
printed and sub-totals/totals are to be drawn per state per employee, MTD/QTD/YTD.
Below are the fields that need to be on the report. It should be an ALV output.
Employee No. Employee Name State Gross Wages SWH Exempt SWH Tax
The SAP Wage Type Reporter, or a variant of it, could be possibly used to generate this report.
Below are the fields that need to be on the report. It should be an ALV output.
The SAP Wage Type Reporter, or a variant of it, could be possibly used to generate this report.
The second part of this report (see last page on hard copy) is same as the SAP quarterly 941 Form.
Below are the fields that need to be on the report. It should be an ALV output.
State Employee Employee SSN Credit YTD QTD QTD QTD QTD
No. Name Weeks SUTA SUTA Subject State SUTA
Earnings Earnings to S/W W/H Taxable
Page 31 of 33
ASAP Business Blueprint – Payroll (USA)
Credit Hours: The number of weeks that an employee worked in a quarter. For the state of WA, this is
however the number of hours worked. Such that we can consider a week as “worked”, the employee
needs to earn at least $50 in wages in that week.
The SAP Wage Type Reporter, or a variant of it, could be possibly used to generate this report.
9. Fringe Report
This report shows wage type assignments per project. For US this is not required.
This monthly report is used to display employee earnings and hours for each Union Local and Trade
Level.
Below are the fields that need to be on the report. It should be an ALV output.
Union Local
Trade Level
Employee Number
Employee Name
SSN
Hours worked week 1
Hours worked week 2
Hours worked week 3
Hours worked week 4
Hours worked week 5
Total ST Hours
Total OT Hours
Total DT Hours
Total hours worked
Hours paid
Days worked?
ST earnings
OT earnings
DT earnings
Total earnings
Employee Deduction 1
Employee Deduction 2
Employee Deduction 3
…
…
Employee Deduction n
Employer Benefit 1
Employer Benefit 2
Employer Benefit 3
…
…
Employer Benefit n
Page 32 of 33
ASAP Business Blueprint – Payroll (USA)
14.3 Interfaces
Please refer to the section titled “Employee (non-union) Benefits” for a description of all Benefits
interfaces.
14.4 Conversions
For a targeted go-live date of 2/1/2007, the year-to-date (YTD) payroll results for the period just preceding
the actual go-live on SAP will be uploaded to the payroll cluster, by transferring the actual YTD results
from the legacy system. This will be done using a special payroll run. These final payroll results will only
be the actual payments to and deductions from the employee and the contributions made by the employer to
external agencies. Certain other wage types (example YTD taxable incomes and bases), will also be
uploaded.
14.5 Enhancements
Employees sometimes work outside of their default tax area. The overridden tax area will need to be
captured on the time sheet. However it could become a huge manual effort on part of the user to capture the
tax area (particular at the local authority level) on the time sheet. Presently in the legacy system, the Job
Number for the project (e.g. 81-5659) has a mapping set up, that defaults the correct tax area on the
employees’ time sheet. This mapping is not available in SAP standard and has to be set up, either on any
available User Exit, as a custom report or as a modification to the standard. A new custom table has also to
be created, on which this mapping may be maintained by the user.
Following are the key roles for US Payroll. These roles, and other roles, if needed, will be further defined in
the realization phase. These roles may need to be copied and modified to meet requirements.
Report RPDASC00 lists the entries in tables T52C0 and T52C5 according to the set parameters. Table
T52C0 takes the COPY statements into account and table T52C5 the personnel calculation rule statements.
GMR Infotech has copied U000 as &000 and customized with new rules as per the business requirement.
Page 33 of 33