Ansicht
Dokumentation

ISPSCA_TFMCA_INCORR - Define Inbound Correspondence Category

ISPSCA_TFMCA_INCORR - Define Inbound Correspondence Category

rdisp/max_wprun_time - Maximum work process run time   General Data in Customer Master  
This documentation is copyright by SAP AG.
SAP E-Book

You define inbound correspondence categories in this IMG activity. You can then use them to generate different inbound correspondence for different contract objects. For example, you can define that you expect a different inbound correspondence for trade tax than for income tax. 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”).

You can also use the inbound correspondence categories to map inbound correspondence requests with different time periods (for example, quarterly or annually).

For each inbound correspondence category you define the specifications that control the generation of inbound correspondence requests:

  • Period (defined by specifying the first and last period)
  • Revenue type (for example, trade tax or income tax)
  • Status: the program includes only those inbound correspondence categories that show a status with active generation for inbound correspondence for the automatic generation of inbound correspondence requests.
  • Reminder days: this determines how many days before the due date of an inbound correspondence the correspondence dunning run creates a reminder.

When maintaining master data for the contract object, you activate specific inbound correspondence categories for this contract object and thereby define which return you expect for the 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. The inbound correspondence request can therefore be created manually in this case during maintenance of the master data for the contract object.

You are working with the enhanced functions for inbound correspondence. See step Activate Inbound Correspondence.

You have created the status for generating inbound correspondence in step Define Status for Generating Inbound Correspondence.

You have created billing periods in step Define Specifications for Tax Periods; this means you have defined the time frame in which the period should be valid and specified a preceding period.

To be able to use reminder mail, you must activate this in step Define Settings for Enhanced Inbound Correspondence and define a corresponding dunning activity.






BAL_S_LOG - Application Log: Log header data   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Length: 3106 Date: 20240523 Time: 153550     sap01-206 ( 71 ms )