Hierarchy
SAP_HRCCA (Software Component) Sub component SAP_HRCCA of SAP_HR⤷
PY-CA (Application Component) Canada⤷
P07C (Package) HR customizing: Canada
IMG Activity
| ID | OHAKR0007 | Configure third-party remittance |
| Transaction Code | S_AHR_61009590 | IMG-Aktivität: OHAKR0007 |
| Created on | 19981221 | |
| Customizing Attributes | OHAKR0007 | Configure third-party remittance |
| Customizing Activity |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | OHAKR0007 |
Description
This chapter provides instructions on configuring Third-Party Remittance (3PR) to set up payroll payments to third parties. (In this chapter, Third-Party Remittance is contrasted with Payroll Posting to Accounting, which allows liabilities and expenses to be posted to the general ledger and evaluates the symbolic account for the debit posting to real G/L accounts in your FI/CO system.)
Third-Party Remittance processing is divided into the following areas:
- Configuration
The configuration of Third-Party Remittance is performed in this chapter. Crucial configuration elements, from an HR perspective, include the HR payee and the symbolic accounts.
In the chapter Payroll Posting to Accounting, you also must perform relevant symbolic account assignments for Third-Party Remittance via the following activities:
- 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 Activities
- 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 two TemSe files for cumulated and detailed remittance data. - Store evaluation run
(Select to execute)
The Store evaluation run transaction updates the remittance tables according to the content of the evaluation run's TemSe files. - Create Third-Party Remittance Posting Run
(Select to execute)
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. - Acknowledgement run
(Select to execute)
When the AP payment program has been run, all remittance items paid are marked. - Remittance reconciliation
(Select to execute)
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
Regular remittance
The data model of remittance allows only one wage type to be maintained per HR payee. Therefore, if you wish to post to multiple regular remittance payees in different company codes, then you must 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 system 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 by Third-Party Remittance.
Another feature of interest concerns the settings for business areas. Some companies have the need to subdivide or group their company codes into business areas, whereby their payments are processed in accordance with these settings. If there is more than one business area linked to a company code, as is allowed in mySAP Financials configuration, then the payroll payments to third parties cannot support such a constellation. In other words, business areas crossing company codes are not supported, because configuration along these lines leads to errors in the clearing process.
Garnishment and Child Support Remittance
Refer to the corresponding activity for garnishments configuration.
General Information
For general information on Third-Party remittance, you may also wish to consult SAP Note 121138.
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 |
|---|---|---|
| OHAKR0007 | CA | Canada |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | OHAKR0007 | 0 | HLA0003918 | Third Party Remittance |
Maintenance Objects
| Maintenance object type |
History
| Last changed by/on | SAP | 20020424 |
| SAP Release Created in |
