Hierarchy
SAP_HRCUS (Software Component) Sub component SAP_HRCUS of SAP_HR⤷
PY-US (Application Component) USA⤷
P10C (Package) HR customizing: USA
IMG Activity
| ID | OHAUR0007 | Posting relevant information |
| Transaction Code | S_AHR_61000333 | IMG-Aktivität: OHAUR0007 |
| Created on | 19981218 | |
| Customizing Attributes | OHAUR0007 | Posting relevant information |
| Customizing Activity |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | OHAUR0007 |
Description
The goal of this Implementation Guide chapter is to give a basic understanding of how Third Party Remittance (3PR) can be used to setup payroll payments to third parties. You will learn about the different settings and options of this functionality versus SAP's Payroll Posting to Accounting functionality. The latter allows posting of liabilties and expenses to the general ledger. It evaluates the symbolic account for the debit posting to real G/L accounts in your FI/CO. Payroll payments to third parties are generally posted to vendor respectively payment or banking accounts in FI. In addition to this the payment should clear the general ledger associated with the liability/expense.
Remittance handling can be divided into the following areas:
- Configuration
The configuration of 3PR contains to major steps that are set up within this chapter of the IMG. The crucial elements from the HR perspective are the HR payee and the symbolic accounts.
In the chapter Payroll Posting to Accounting of the IMG you have to first make relevant symbolic account assignments for Third Party Remittance, including:
- Define symbolic accounts
- Define wage type posting attributes
- Assign financial accounts
- Assign expense accounts
- Assign technical accounts
- Assign customer accounts
- Assign vendor accounts
- Assign loan accounts
Maintenance steps
- Maintain payroll evaluation schema
- HR Payee maintenance
- Remittance rule and accumulator maintenance
- Wage type maintenance
- Number Ranges
- Evaluation run (payroll driver with schema U500)
You will need to add specific functions to the payroll evaluation schema. These functions control the remittance flow and determine the due date for each payment to an HR payee. The evaluation run creates 2 TemSe files for cummulated and detailed (per employee) remittance data. - Store evaluation run (run now)
The Store evaluation run updates the remittance tables according to the content of the evaluation run's TemSe files. It assigns a final evaluation run number to the remittance postings as well as a remittance origin link. For these numbers a designated number range has to be configured. - Create Third-Party Remittance Posting Run (run now)
The posting process produces posting documents that can be viewed with the posting run transaction under evaluation type 'TP'. The documents belonging to this posting run will be posted to AP/FI using the payroll accounting interface.
Once the data is posted to AP, the specified amount is paid on the specified due date using the specified payment method.
This process assigns a posting run number and creates a cummulated entry for the payee in the posting table. - Acknowledgement run (run now)
When the AP payment program has been run, all remittance items paid are marked. In the posting table on the HR side get updated with a stamp for the payment or acknowledgement run number. - Remittance reconciliation (run now)
During the remittance process the reconciliation run can be used at all times to verify the current status of the overall remittance process.
Further notes
Other remittance
The current data model of remittance allows to maintain only one wage type per HR payee. Therefore if you want to post to multiple other remittance payees in different coampany codes you need to create duplicate wage types. A solution for this restriction might be found using Payees with special dependencies.
Company codes and business areas
According to the origin of the payment all payments in the SAP HR sytem are currently linked to the organizational company code of the person. Therefore all payments are usually linked to the accounting company code whereas payments in general could also be posted to a different company code, the paying company code. Paying company codes are currently not supported within Third Party Remittance.
Another most often asked feature is regarding the settings for business areas. Some companies have the need to subdivide or group their company codes to business areas and have their payments be treated according to these settings. If there are more than one business area linked to a compay code as it is allowed by SAP's FI configuration the payroll payments to third parties can not support such a constellation. In otherwords business areas crossing company codes are not supported at this time. Configurations that are set this way cause problems in the clearing process.
Please refer to note 0203276 regarding the change in the posting to FI interface.
Garnishment and Child Support Remittance
Please refer to the garnishments IMG step and its documentation as well as note
0154021 Printing garnishment info on vendor chk./adv.
General Help
For general help on remittance please refer to note
0121138 Q&A for Third-Party Remittance
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | I | Valid for countries specified |
| Customizing Attributes | Country Key | Country Name |
|---|---|---|
| OHAUR0007 | US | USA |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | OHAUR0007 | 0 | HLA0009697 | Third Party Remittance |
Maintenance Objects
| Maintenance object type |
History
| Last changed by/on | SAP | 20010926 |
| SAP Release Created in |
