Ansicht
Dokumentation

PSCD_COLLECTIONS_MANAGEMENT: Enhanced Inbound Correspondence (New) ( RELN603_PSCD_TRM_RETRN_5 )

BAL Application Log Documentation   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Short text

PSCD_COLLECTIONS_MANAGEMENT: Enhanced Inbound Correspondence (New)

Use

As of SAP ECC 6.0, Industry Extension Public Sector, Enhancement Package 03, Business Function TRM: Return Processing (PSCD_TRM_RETURN_PROCESSING), you can use the functions for enhanced inbound correspondence. In order to use the enhanced functions, you must activate the enhanced inbound correspondence in Customizing.

You can continue to display and process the inbound correspondence requests created in the system before this change, but you cannot recreate them. You can also still display the specifications defined for the contract object for inbound correspondence.

Several inbound correspondence categories for each contract object

Until now there was only one inbound correspondence per contract object. As of this release you can generate different inbound correspondence for a contract object. These are then mapped in the system with inbound correspondence categories. You can use inbound correspondence categories to define that you expect a different inbound correspondence for trade tax than for income tax for example. You can also request different inbound correspondence for a revenue type. For example, it is possible to request two different pieces of information from taxpayers for the tax return: one concerning the submission of the tax return (inbound correspondence category "income tax return") and to request that missing information also be submitted (inbound correspondence category "income tax return: additional data"). Inbound correspondence requests can also be mapped using different time periods (for example, quarterly or annually).

Each inbound correspondence category is assigned to a revenue type in the Customizing of Contract Accounts Receivable and Payable. When processing the contract object you activate certain inbound correspondence categories for a contract object and thereby define for which revenue types you expect a tax return for this contract object. The example above assumes that an income tax return is expected from each taxpayer, and as such generates an inbound correspondence request automatically, whereas missing data is only relevant for some taxpayers. Therefore the inbound correspondence request is created manually in this case.

The inbound correspondence categories are time-dependent and are created or processed in the Customizing of Contract Accounts Receivable and Payable. Furthermore, inbound correspondence refers directly to periods. This enables time limit changes to be mapped easily for example. You can overwrite the Customizing setting when processing the contract object. You can define the following when doing this:

• Which inbound correspondence category is active, in other words, is created automatically.

• Exception periods for which you do not expect any inbound correspondence. Exception periods apply to all inbound correspondence categories simultaneously and for each year.

• Alternative periods that subdivide the standard periods.

Process

1. The system generates inbound correspondence requests based on the entries in Customizing or in the contract object. They can either be generated individually when processing the contract object or during a mass activity. Inbound correspondence requests are created for periods. When an inbound correspondence request is generated, the system posts a sample document at the same time.
2. If the inbound correspondence is not submitted by the time limit, you start dunning for it. Dunning is based on the posted sample documents if the dunning by collection strategy is active for this company code, otherwise normal inbound correspondence dunning takes place.
3. The system automatically assigns received inbound correspondence when running program Validation and Billing of Tax Returns and Requests to the open inbound correspondence requests thereby flagging the request as completed. The sample document is thereby cleared automatically. Alternatively you can perform this manually in the inbound correspondence history.

Effects on Existing Data

Effects on Data Transfer

Effects on System Administration

Effects on Customizing

You define the Customizing settings for this function in the Customizing of Contract Accounts Receivable and Payable in section Business Transactions -> Inbound Correspondence -> Inbound Correspondence (enhanced):

To use the enhanced inbound correspondence functions, activate them in IMG activity Activate Enhanced Inbound Correspondence.

Further Information

For more information, see the SAP Library under SAP ERP Central Component → SAP Public Sector Tax and Revenue Management → Collection and Disbursement (PSCD) → Enhanced Inbound Correspondence.

Fill RESBD Structure from EBP Component Structure   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Length: 5440 Date: 20240426 Time: 235529     sap01-206 ( 117 ms )