Ansicht
Dokumentation

OHAKR0007 - Configure third-party remittance

OHAKR0007 - Configure third-party remittance

Vendor Master (General Section)   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.
SAP E-Book

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:

  1. 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:

Maintenance Activities

  1. 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.
  2. 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.
  3. 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.
  4. Acknowledgement run
    (Select to execute)
    When the AP payment program has been run, all remittance items paid are marked.
  5. 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.

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.

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.

Refer to the corresponding activity for garnishments configuration.

For general information on Third-Party remittance, you may also wish to consult SAP Note 121138.






Addresses (Business Address Services)   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.

Length: 6858 Date: 20240523 Time: 220425     sap01-206 ( 90 ms )