Você está na página 1de 75

0

A Comprehensive Guide
to SAP HR Payroll
Integration with SAP
ERP Financials and SAP
General Ledger
Mike Timm
Integrated Consulting Group
© 2009 Wellesley Information Services. All rights reserved.
What We’ll Cover …
• Understanding FI data objects used by HR/Payroll
• Utilizing the SAP General Ledger functionality
• How payroll updates FI and AP
• Using the Payment Program
• Mapping components for the Posting to Accounting process
• Automating Month-End Accruals
• Identifying objects for the Posting Third-Party Remittance process
• Wrap-up

2
Understanding FI Data Objects Used by HR/Payroll
• External modules have defined objects that are used in Human
Resources and assigned to employees
ΠCompany code

f Personnel areas are assigned to a company code

ΠCost center

f Organizational units or Positions may be assigned to a cost


center
f Assignment performed at the individual employee level or
even within an specific infotype record
ΠBusiness area

ΠWBS element

• These objects are then processed through to payroll and used


during the Posting to Accounting process
3
FI Data Objects Found in Organizational Management
• Transaction Code PP01
• Infotype 1001 Relationships
• Position 20001398 cost
center assignment record
in Organizational
Management

4
FI Data Objects Found in Infotype 0001 Org Assignment
• Transaction Code PA30
• Infotype 0001 Organizational Assignment
• Company code is
inherited from the
Personnel Area
assignment set in
configuration

• Cost center is inherited


from Position assignment
in Organizational
Management
• The cost center could
have been assigned at the
Organizational Unit and
inherited by the position
and employee
• Or, the cost center could
be assigned in the field if
it were not set to locked
FI Data Objects Found in Infotype 0027 Cost Distribution
• Transaction Code PA30
• Infotype 0027 Cost Distribution
• The home cost center in
Infotype 0001 Organizational
Assignment is 100800
• This employee will have 50%
of the cost distribution
posted to cost center 100820

6
FI Data Objects Found in Infotype 0015 Additional Payments
• Transaction Code PA30
• Infotype 0015 Additional Payments
• Position 20001398 cost center
assignment record in
Organizational Management

• Cost Assignment allows the


override of home cost objects
• The $1,000 entry will post to
cost center 100810

7
Understanding FI Data Objects Used by HR/Payroll
• The FI objects used in Human Resources processed and
integrated with the payroll process
• These objects will dictate how postings to accounting and
third-party remittance are completed
• Cost centers may be assigned at many different levels allowing
for a great deal of flexibility for cost distribution
ΠOrganizational Unit or Position РOrg Management assignment
inherited by the employee
ΠInfotype 0001 Organizational Assignment Рhome/master cost
center for employee
ΠInfotype 0027 Cost Distribution Рallows for multiple cost
centers to be allocated a percentage
ΠInfotype 0015, 0014, 2001, 2002, 2010, etc. Рindividual entries
may be posted to different cost centers
8
What We’ll Cover …
• Understanding FI data objects used by HR/Payroll
• Utilizing the SAP General Ledger functionality
• How payroll updates FI and AP
• Using the Payment Program
• Mapping components for the Posting to Accounting process
• Automating Month-End Accruals
• Identifying objects for the Posting Third-Party Remittance process
• Wrap-up

9
Utilizing the SAP General Ledger Functionality
• SAP ERP 6.0 has an optional general ledger that posts liabilities
according to expenses based on the following elements:
ΠOrder

ΠCompany Code

ΠBusiness Area

ΠCost Center

ΠCost Object

ΠNetwork

ΠWBS Element

ΠOper./Act.

ΠSales Order

ΠSales Ord. Item

10
Utilizing the SAP General Ledger Functionality (cont.)
• You have the option of posting the liabilities in the following
manner:
ΠDo not want to distribute liabilities

ΠDistribute the liabilities according to expenses

ΠDistribute the liabilities solely according to the assignment in


the Infotype 0001 Organizational Assignment
• Table V_T52SWCODIST is updated to identify which of the three
options is to be used
ΠThe default provided from SAP is no distribution of liabilities

• SAP has provided a set-by-step setup procedure in the IMG and


makes implementation

11
Utilizing the SAP General Ledger Functionality (cont.)
• IMG Payroll Œ Payroll:USA Œ Posting to Financial Accounting Œ
New General Ledger: Distribution of liabilities according to
expense
ΠNo configuration required if not distributing liabilities

ΠAll nodes need to be configured if distributing liabilities


according to expenses
ΠMaster data, Posting of payments, Posting transfer to Financial
Accounting nodes need to be configured if liabilities are to be
distributed by Organizational Assignment

12
What We’ll Cover …
• Understanding FI data objects used by HR/Payroll
• Utilizing the SAP General Ledger functionality
• How payroll updates FI and AP
• Using the Payment Program
• Mapping components for the Posting to Accounting process
• Automating Month-End Accruals
• Identifying objects for the Posting Third-Party Remittance process
• Wrap-up

13
How Payroll Updates FI and AP
• Posting to accounting
ΠPayroll and FI have defined integration points through which
data is passed, just like Materials Management/Sales and
Distribution (MM/SD)
ΠUnlike MM/SD, though, some integration points require human
intervention
ΠThis may cause confusion between the payroll and FI teams
both on the implementation and after go-live
• Third-party remittance
ΠCreates payables to different vendors as a result of HR/Payroll

14
Payroll Integration Points with FI
• The integration points between Payroll and FI are:
Œ Creating the Data Medium Exchange (DME) for payments —
update check register only
ΠPosting to financial accounting

ΠPosting third-party remittance

• I will demonstrate each of the Payroll-FI integration points by:


ΠRunning the Payroll (prepares the net results)

ΠCreating the DME (generates the payments)

ΠPosting to accounting (updates FI with data from the


payroll run)
ΠPosting third-party remittance (generates payment
information for vendors)

15
Running the Payroll
• First, select “Release payroll”
ΠIn this step, the payroll area and payroll period to be processed
are selected
ΠThe payroll control record is set to allow payroll processing

ΠEmployee master data records are locked

• Next, select “Start payroll,” enter screen parameters, and launch


the payroll process
ΠPayroll processes generating wage types for earnings,
deductions, and taxes
ΠAssignment to company and cost center are done based on the
Employee Infotypes
ΠCheck the results by viewing the Remuneration statement

16
Running the Payroll (cont.)
• Finally, select “Exit payroll”
ΠThe payroll control record is set to finalized, allowing for
additional processing such as posting to accounting and
third-party remittance
ΠEmployee master data records are unlocked for current and
past changes

17
Running the Payroll (cont.)
• How to run payroll:
ΠRelease payroll

ΠStart payroll

ΠExit payroll

• Menu Path
ΠHR ΠPayroll ΠAmericas
ΠUSA ΠPayroll

None of these steps updates FI


18
Creating the DME
• Next, we’ll create the DME
ΠThis step prepares the payroll Remuneration data for ACH and
check printing
ΠYou specify one of the following DME types:

f Payroll Check

f ACH Transfer (Direct Deposit)

• Payroll uses the AP Payment Program for the ACH and check
printing processes
ΠThe check register will be updated

ΠFI/CO will not be updated

After doing this, your check register will be out of balance with your outgoing payments’
general ledger account in FI/CO. FI/CO will also be out of balance with Payroll because no
expense or liability postings will have been transferred yet.
19
Creating the DME (cont.)
• How to generate the DME:
ΠPre-program DME

ΠCreate DME

ΠDME management

ΠPrint check

• Menu path
ΠHR ΠPayroll ΠAmericas
ΠUSA ΠPayroll ΠBank
transfer

• Check register is updated when these steps


are processed

20
Creating the DME (cont.)
• The results
ΠPayroll checks and ACH files for the direct deposit were
generated
ΠThe check register has been updated and reflects the newly
printed payroll checks, but FI has no payroll information
• Conclusions
ΠChecks and direct deposits may be generated without
transferring to FI
ΠIn other words: The payroll may be run successfully, with check
and direct deposits for payroll cut and distributed, without
updating FI

21
Posting to Accounting
• The discrepancy caused while creating the DME is solved by
executing transaction PCP0
ΠThis is an important, separate step after generating payroll
and cutting checks (DME)
• PCP0 updates FI — expenses, liabilities, and assets — using any
of these
Œ The employee’s home cost center

ΠInfotype 27 cost distribution

ΠIndividual infotype overrides

• The process also uses the mapping of wage types to symbolic


accounts to G/L accounts to determine the correct G/L
account/cost element to use

22
Posting to Accounting (cont.)
• Execute posting run (RPCIPE00)
• Execute posting run for
payments
(H99_POST_PAYMENT)
• Process posting run (PCP0)
• Menu Path
Œ HR Œ Payroll Œ Americas Œ
USA ΠSubsequent activities
Œ Per payroll period Œ
Evaluation ΠPosting to
accounting

When viewing the FI/CO update document, use menu path Extras > Original
Document to jump to the payroll remuneration statement (which lists the wage
types/employees that make up the FI posting)
23
Posting to Accounting (cont.)
• Posting to accounting and Posting of payment processes
generated the following two documents

24
Retroactive Calculation Posting
• Retroactive postings with amount change
ΠIf only the amount changes, the difference is posted

f In the original period starting 11/01, the employee was paid


$1,000 in salary
f A retroactive change is made effective 11/01 to make the
salary $1,500
f The period starting 11/01 will generate a difference posting of
$500, and the 12/01 period will generate a posting of $1,500,
for a total of $2,000 to the salary account

Period 11/01 Period 12/01


Payable 1,000 Payable 2,000
Salary 11/01 1,000 Salary 11/01 500
Salary 12/01 1,500

25
Retroactive Calculation Posting (cont.)
• Retroactive postings with accounting object change
ΠIf an account assignment object changes, the amount in the
old account assignment object is reversed and posted to the
new one
f In the original period starting 11/01, the company code 0010
employee was paid $1,000 in salary
f A retroactive change is made effective 11/01 moving the
employee to company code 0020
f The period starting 11/01 will generate a reversal posting of
$1,000 in company code 0010 and $1,000 posting in company
code 0020 along with the 12/01 period generating a posting of
$1,000 for company code 0020
Period 11/01 Period 12/01
Payable 1,000 Payable 0010 1,000
Salary 11/01 0010 1,000 Salary 11/01 0010 1,000
Payable 0020 2,000
Salary 11/01 0020 1,000
Salary 12/01 0020 1,000
26
Reverse Payroll Postings
• Reverse postings
ΠReversal documents are created with identical information as
the original posting with the exception of the sign (+/-)
ΠReversal documents transfer and post to accounting, canceling
the incorrect original posting
ΠPayroll results are reset

ΠLinks to the reversed posting documents are found and


available for viewing
ΠPlease keep in mind that you will need to run the process
to post the payroll results
• Program RPCIPR00
Check Posting to Accounting Completeness
• Program RPCIPC00 is the check completeness report for FI
posting
Œ Human Resources Œ Payroll Œ Americas Œ USA Œ
Subsequent activities Œ Per payroll period Œ Evaluation Œ
Posting to accounting ΠCheck completeness
ΠEnter the date you want to search from and then enter the
Run Type
ΠExecute, and you will receive all the non-posted payroll results
with enough detail to complete the posting

28
Posting Third-Party Remittance
• Payables may be generated for vendors as a result of HR/Payroll.
Examples include:
ΠGarnishment processors
ΠTaxing authorities
ΠBenefit providers
• This is an additional step done after payroll and the update of
payroll results to FI
Œ Posting third-party remittances isn’t required to run the next
payroll
ΠEmployee withholdings such as garnishments can NOT be
passed to the AP vendor if the third-party remittance posting
run is not executed
ΠOnce you post your third-party remittances, the proper AP
vendors’ accounts are updated so that you can process them
like any other liability through the AP payment program 29
Posting Third-Party Remittance (cont.)
• How to post third-party remittance:
ΠEvaluation remittance (New)
(PC00_M99_URME)
ΠCreate posting run
(PC00_M99_URMP)
ΠProcess posting run (PCP0)

• Menu path:
Œ HR Œ Payroll Œ Americas Œ
USA Œ Subsequent activities Œ
Per payroll period ΠEvaluation
ΠThird-party remittance

30
Check Third-Party Remittance Completeness
• Program RPURMC00 is the check completeness for third-party
remittance
Œ Human Resources Œ Payroll Œ Americas Œ USA Œ
Subsequent activities Œ Per payroll period Œ Evaluation Œ
Third-party remittance ΠRun remittance completeness check
• Execute and you will receive output of third-party remittance
processing that needs to be completed

31
Third-Party Remittance Reconciliation
• Program RPURMR00 is the third-
party reconciliation report
Œ Human Resources Œ Payroll Œ
Americas ΠUSA ΠSubsequent
activities Œ Per payroll period Œ
Evaluation ΠThird-party
remittance ΠReconcile postings
• Unless you know you have few
entries, narrow down the HR payee
item selection to keep a controllable
amount of output
• ALV Layout determines how the
data will be displayed

32
Third-Party Remittance Reconciliation (cont.)

• The output is changeable with ALV Layout


• Pertinent information is displayed along with the status so we know
where the remittance stands

33
What We’ll Cover …
• Understanding FI data objects used by HR/Payroll
• Utilizing the SAP General Ledger functionality
• How payroll updates FI and AP
• Using the Payment Program
• Mapping components for the Posting to Accounting process
• Automating Month-End Accruals
• Identifying objects for the Posting Third-Party Remittance process
• Wrap-up

34
Using the Payment Program
• As was shown in the previous section, Payroll uses the AP
payment program to generate checks and ACH payments (DME)
• Configuration is essentially the same as is done for AP
ΠCreate house banks and accounts (tcode FBZP)

ΠCreate payment methods (tcode FBZP)

ΠAssign to accounts (tcode FBZP)

ΠCreate RFFOUS_C and RFFOUS_T variants

• Whether the same bank accounts are used for AP payments and
payroll payments, new payment methods for payroll check and
ACH transfers should be configured
ΠEnables easier reconciliation of checks, accounts, and check
register to SAP General
ΠAllows for a greater degree of authorization to
view/create/change payroll checks 35
House Bank Account and Payment Method

• Transaction code FBZP


ΠHouse bank and account(s) are created

ΠBank account information and the G/L account are assigned

ΠC is the AP check
ΠK is the Payroll check

36
Employee Infotype 0009 Bank Details

• Transaction code PA30


• Infotype 0009 Bank Details

37
Using the Payment Program
• As shown earlier, there is no “automatic” integration link between
Payroll and FI/CO
ΠThis is an issue, especially when corporations use one
company code to make payments for other company codes
ΠManual processing allows more room for error
ΠThere is no financial link between the G/L line items in the bank
clearing account and the check register
• You can automate clearing journal entries and link the G/L line
items to the check register with program H99_POST_PAYMENT
ΠThe program requires that the payroll results be posted to a
clearing account
ΠAutomatically journals out of the clearing account and into the
proper bank clearing account and company code
f Based off the DME run in the payment program
f This program is a must-have in a cross-company scenario 38
What We’ll Cover …
• Understanding FI data objects used by HR/Payroll
• Utilizing the SAP General Ledger functionality
• How payroll updates FI and AP
• Using the Payment Program
• Mapping components for the Posting to Accounting process
• Automating Month-End Accruals
• Identifying objects for the Posting Third-Party Remittance process
• Wrap-up

39
Mapping Components for the Posting to Accounting
Process
• In this section, I will show the configuration behind the Payroll
integration points with FI/CO:
1 – Defining Symbolic Accounts
2 – Defining Wage Types (Gross to Net)
3 – Mapping Wage Types to Symbolic Accounts
4 – Mapping Symbolic Accounts to the SAP General Ledger

40
1: Defining Symbolic Accounts
• Symbolic accounts are names used in HR/Payroll instead of G/L
account numbers
Œ They’re similar to account keys in SD

ΠYou can think of symbolic accounts as an intermediate step to


determining the proper G/L account
• The types of symbolic accounts are:
ΠFinancial РBalance sheet

ΠExpense РIncome statement

ΠTechnical РClearing account

ΠVendor РVendors

ΠCustomer РCustomers

ΠLoans РEmployee loans

41
1: Defining Symbolic Accounts (cont.)
• Symbolic accounts have an employee grouping key, which allows
the symbolic account to be associated with different G/L accounts
ΠEmployee groupings are done with the feature PPMOD
ΠPPMOD allows many employee organizational fields to be used
for decisions, with the following being most common:
f Company code, cost center
f Personnel area, subarea
f Employee group, subgroup (hourly, salaried, etc.)

• How to add/maintain symbolic accounts


ΠUse IMG Payroll ΠPayroll:USA ΠPosting to Financial
Accounting ΠActivities in the HR System ΠEmployee
Grouping and Symbolic Accounts ΠDefine Symbolic Accounts42
1: Defining Symbolic Accounts (cont.)
• Selecting the MOMAG field will determine whether the feature
PPMOD impacts the posting to accounting
• Selecting the Fixed MOMAG triggers the liability distribution by
expenses

43
2: Defining Wage Types (Gross to Net)
• Wage types are elements used in the payroll schema
to represent different types of payroll activities
(e.g., wages, deductions, taxes)
ΠWage types for gross wages, net wages, and taxes are
delivered standard and ready to use
ΠEmployee deductions and earning codes are delivered as
examples
• The payroll schema uses wage types in the calculation of net
payroll from gross payroll
ΠThe wage types used in payroll are what will ultimately drive
SAP General Ledger postings and accounts that are used in FI

44
3: Mapping Wage Types to Symbolic Accounts
• Next, wage types need to be mapped to symbolic accounts so
SAP R/3 can determine which G/L accounts to update
ΠIMG Payroll ΠPayroll:USA ΠPosting to Financial Accounting
Œ Activities in the HR-System Œ Wage Type Maintenance Œ
Define Wage Type posting attributes

Enter symbolic account

Normal processing signifies this posting attributed


will be used during regular payroll processing

Specifies how the positive number will post to


accounting. This option allows us to determine
how a wage type positive or negative amount will
post to the SAP General Ledger

45
3: Mapping Wage Types to Symbolic Accounts (cont.)
• Tax wage type posting attributes are slightly different
• Use the Posting US Tax node on the left side of the Dialog
Structure

Normal
processing
signifies this
posting
Specifies how the attributed will
positive number will be used
post to accounting. during
This option allows regular
us to determine how payroll
a wage type positive processing
or negative amount
will post to the SAP
General Ledger

Enter symbolic account

Tax Authority – may be multiple per tax wage type


46
3: Tips for Mapping Wage Types to Symbolic Accounts
• Know what each wage type is used for before maintaining them
• Know how each wage type relates to financial transactions
• Make sure your payroll and FI teams communicate
• When in doubt, create a new symbolic account
ΠSometimes the intended use of the wage type is not completely
understood or may change over time
ΠOften, when it is time to change how the wage type is posting in
the SAP General Ledger, people take a shortcut and change the
mapping of the symbolic account that is assigned to that wage
type
ΠIf that symbolic account is assigned to other wage types that
are posting correctly, you can break more than you are fixing

47
4: Mapping Symbolic Accounts to the SAP General Ledger
• Next, you need to map symbolic accounts to G/L accounts
ΠTechnically, the task typically resides in the FI module based on
the updated table
Œ The mapping is an Automatic Account Assignment T030 — just
like any other FI automatic account assignment
ΠVery straightforward

48
4: Mapping Symbolic Accounts to the SAP General
Ledger (cont.)
• How to map symbolic accounts to G/L accounts:
ΠEnter symbolic account

ΠEnter employee group

ΠEnter the debit account

ΠEnter the credit account

• IMG Payroll Œ Payroll:USA Œ Posting to Financial Accounting Œ


Activities in the AC-System ΠAccount Assignment

49
4: Mapping Symbolic Accounts to the SAP General
Ledger (cont.)
• How to create a clearing account:
ΠEnter the account key
ΠEnter the G/L account

• Use clearing accounts (key 1001) when:


ΠThere are multiple company code or business area
assignments within a payroll period
ΠRetroactive accounting changes occur prior to an employee
changing company codes or business areas
ΠEmployee company code or business area changes
retroactively or within a period
ΠUtilizing third-party remittance
• Key 1002 is used when there are > 999 posting lines in a
document 50
4: Mapping Symbolic Accounts to the SAP General
Ledger (cont.)
• Once you have your mappings completed, use the wage type to
G/L mapping report RPDKON00
Œ Human Resources Œ Payroll Œ Americas Œ USA Œ Tools Œ
Customizing Tools Wage Type Assignment - Display G/L
Accounts

51
4: Tips for Mapping Symbolic Accounts to the SAP General
Ledger
• Work closely with the finance team to coordinate how the
symbolic accounts are being used
• Be careful about changing the mapping.
Make sure that the symbolic account
needing change is not assigned to
another wage type that needs to post
where the symbolic account is currently
set to post!

52
What We’ll Cover …
• Understanding FI data objects used by HR/Payroll
• Utilizing the SAP General Ledger functionality
• How payroll updates FI and AP
• Using the Payment Program
• Mapping components for the Posting to Accounting process
• Automating Month-End Accruals
• Identifying objects for the Posting Third-Party Remittance process
• Wrap-up

53
Automating Month-End Accruals
• Additional configuration is required to trigger and perform the
month-end accruals
ΠRule UAC0 will trigger the month-end processing

ΠPosting and closing dates need to be configured

• Wage type posting attributes need to be configured for accrual in


a similar method as was done for Posting to Accounting
ΠCommonly, period wages (salary) accrued will contain all
wages, absences, holidays, etc., and will not differentiate the
type of wage

54
Automating Month-End Accruals (cont.)
• Accrual postings are automatically reversed in the next month
ΠAssuming one company code, three payroll posting documents
will be created in the accrual period
f Current period payroll results

f Month-end accrual in the current month

f Month-end accrual reversal in the following month

55
Triggering Month-End Accrual in Payroll
• Transaction code PE02
• Update rule UAC0
• Change the value of UAC0 line 10 from ACCMO=0 to ACCM0=1

• Rule UMOD operation MODIF C= determines the factoring


mechanism
ΠA = work days

ΠK = calendar days

ΠS = work hours

56
Triggering Month-End Accrual in Payroll (cont.)
• Maintain posting dates
Œ IMG Payroll Œ Payroll:USA Œ Month End Accruals Œ
Triggering Month-End Accrual Computations ΠMaintain
posting dates
• Defines the posting date of individual payroll periods
ΠTypically, this is the same as the check date

ΠIn the example below, period 01.2009 has a posting date of


01/07/2009

57
Triggering Month-End Accrual in Payroll (cont.)
• Define closing dates
Œ IMG Payroll Œ Payroll:USA Œ Month End Accruals Œ
Triggering Month-End Accrual Computations ΠDefine closing
date
• Defines the last possible payroll posting date for payroll in the
previous month
ΠDictated by accounting irrespective of when accounting actual
closes the month
ΠIn the example below, payroll must post to accounting no later
than 01/08/2009 for December 2008 payrolls

58
Triggering Month-End Accrual in Payroll (cont.)
• Set latest document creation date
Œ IMG Payroll Œ Payroll:USA Œ Month End Accruals Œ
Triggering Month-End Accrual Computations ΠSet latest
document creation date
• Defines the posting date of individual payroll periods
ΠTypically, this is the same as the check date

ΠIn the example below, period 01.2009 has a last document


creation date of 01/07/2009

59
Triggering Month-End Accrual in Payroll (cont.)
• Using the table entries from the previous three slides, we know
that period 01.2009 will generate three posting to accounting
documents
ΠCurrent period 01.2009 with a posting date of 01/07/2009

ΠMonth-end accrual for the three work days in December 2008


dated 12/01/2008
ΠMonth-end accrual reversal for the three work days in
December 2008 dated 01/01/2009
• If the closing date had been prior to 01/08/2009, then, period
53.2008 would have generated three posting documents
ΠThe month-end accrual computations would have for the three
remaining work days in December would be based on estimates
instead of actuals

60
Mapping Wage Types to Symbolic Accounts
• Wage types need to be mapped to symbolic accounts so SAP R/3
can determine which G/L accounts to update
• IMG Payroll Œ Payroll:USA Œ Month End Accruals Œ Line item
Creation for Month-End Accruals ΠAssign symbolic accounts to
wage types

Enter symbolic account

Month-end accrual signifies this posting attributed


will be used during the month end accrual process

Specifies how the positive number will post to


accounting. This option allows us to determine
how a wage type positive or negative amount will
post to the SAP General Ledger

61
Reviewing Wage Type Posting Attributes
• Once you have your mappings completed, use the wage type to
G/L mapping report RPDKON00
Œ Human Resources Œ Payroll Œ Americas Œ USA Œ Tools Œ
Customizing Tools Wage Type Assignment - Display G/L
Accounts

62
Considerations for Month-End Accruals
• Future actions or changes to employee master data are not taken
into account during the accrual calculation
ΠKeep this in mind if the next period has significant pay raises
since those increases are in the future and not automatically
accrued
• The accruals are based on results from the current payroll period
• Also be aware of the accruals for taxes in a month when employee
bonuses are paid, as the accrual will not be accurate

63
What We’ll Cover …
• Understanding FI data objects used by HR/Payroll
• Utilizing the SAP General Ledger functionality
• How payroll updates FI and AP
• Using the Payment Program
• Mapping components for the Posting to Accounting process
• Automating Month-End Accruals
• Identifying objects for the Posting Third-Party Remittance process
• Wrap-up

64
Identifying Objects for Posting Third-Party Remittance
• The third-party remittance process was described earlier
ΠDuring payroll, liabilities may be accrued for:

f Benefit providers

f Tax authorities

f Garnishment vendor processors

f Other deduction vendors

ΠGarnishment processors and the other types of vendors are


posted to AP during the third-party remittance process
• The key integration point is linking an HR payee to an AP Vendor
account

65
Identifying Objects for Posting Third-Party
Remittance (cont.)
• Garnishment processors are directly connected to an
AP vendor
ΠWhen creating a garnishment document for an employee, the
user selects an AP Vendor directly
ΠAll other types of vendors go through the third-party mapping
process

66
Defining Third-Party Tax Remittance Components
• Assign wage types to HR payee and HR payee to AP Vendor
ΠHuman Resources ΠPayroll ΠPayroll:USA ΠThird-party
remittance ΠHR payee maintenance ΠSetup HR payees for
tax remittance

67
Defining Third-Party Regular Remittance Components
• Assign wage types to HR payee and HR payee to AP Vendor
ΠHuman Resources ΠPayroll ΠPayroll:USA ΠThird-party
remittance ΠHR payee maintenance ΠSetup HR payees for
regular remittance

68
Identifying Objects for Posting Third-Party Remittance

• Utilizing third-party remittance allows for tight integration between


the withholdings made in payroll and Accounts Payable (AP)
• Setup is relatively straightforward and relies only on table entries
• Communications between payroll and Accounts Payable are
crucial for wage types to pass to the correct AP vendor
• AP vendors need to be created in the lower system environments
(DEV, QA) so they are available for payroll to configure during
assignment of HR payee to AP vendor

69
What We’ll Cover …
• Understanding FI data objects used by HR/Payroll
• Utilizing the SAP General Ledger functionality
• How payroll updates FI and AP
• Using the Payment Program
• Mapping components for the Posting to Accounting process
• Automating Month-End Accruals
• Identifying objects for the Posting Third-Party Remittance process
• Wrap-up

70
Resources
• SAP Note 119865
ΠProvides additional information about payroll postings that may
not be found in documentation
• SAP Note 532744
ΠThe master Note for third-party remittance that will redirect to
other Notes or resources
• Clay Molinari, “Accurately Manage Changes in Your HR to FI
Posting Configuration” (HR Expert, May 2006).
• Ilene Schuss, “Create an Error-Free Connection Between Your HR
and FI Modules” (HR Expert, April 2003).
• Phil Taylor, “An expert guide to leveraging SAP General Ledger to
allocate liabilities by expense category during payroll accounting”
(Financials 2009, March 2009).

71
7 Key Points to Take Home
• SAP General Ledger will impact many facets of design
• Accounting elements may be assigned in numerous places
throughout HR and passed to accounting after payroll processing
• Transferring payroll results must be manually posted to FI/CO
• The Payroll Payment Program does not update FI/CO like it does
in AP; it only updates the check register
• SAP delivers easy-to-use reconciliation and completeness reports
for posting to accounting and third-party remittance
• Create new payment types in the AP payment program for payroll
payments
• Mapping payroll creditors to AP vendors is the key integration
step for third-party remittances

72
Your Turn!

How to contact me:


Mike Timm
(866) 415-0072
mtimm@integratedcg.com
73
Disclaimer
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver®, Duet™, PartnerEdge, 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 in several other countries all over the world. All
other product and service names mentioned are the trademarks of their respective companies. Wellesley Information Services is neither owned nor
controlled by SAP.

74

Você também pode gostar