Introducing the Registration Process

No matter which channels are used, every registration activity reflects in the primary data.

Below are the primary data objects and levels used in SAP Tax And Revenue Management:

1. SAP Business Partner (taxpayer/citizen): This object could be an individual, anorganization, or or event a group of business entity or even a group.
2. Contract Account: This object holds the tax agency's internal accounting details, similar to your account with a credit card firm or service provider. It is used as a dimension to record revenue in SAP PSCD.
3. Contract Object: This tracks tangible items like properties, specific locations, vehicles, and so on. It isn't an individual or a legal establishment.

Depending on the client's requirements, various SAP applications can be chosen, such as online registration, in-house registration, or integration with external data sources.

Through SAP's Taxpayer Online Services, taxpayers or their tax advisors can directly manage online registrations.

For in-house registration, there are several available supporting tools, such as registration via Web Dynpro or a form-based application.

Before initiating any tax-related processes like handling tax returns, it's essential to establish the taxpayer's profile and their associated tax details, which include tax and filing obligations.

Taxpayers can be registered in two ways:

1. Automatically, by uploading their tax registration forms
2. Manually, by a tax officer

Manual registration might be required in exceptional scenarios or for specific tax categories, such as import/export or alcohol retailers. In such instances, various measures like asking for supplementary details or introducing extra approval stages might be initiated.

For the form-based approach, the XML file generated from the form is subjected to Business Rule Framework (BRFplus) validation upon uploading. If any existing validations don't pass, a task is generated in the tax official's work center. This task generation procedure also applies when prior approval is needed before creating the master data.

1. Create master data objects manually
2. Create master data objects with the standard Web Dynpro Application
3. Create master data objects with the registration form (from Tax Officer's Workcenter)
4. Create master data objects with the registration from (from online services)

The subsequent slides will delve deeper into these four techniques.

Before initiating the form-based registration, it is imperative to consider the pertinent configuration. Initially, one must establish a registration form within the Configuration framework. The successive slides describe the systematic steps required to form the Configuration.

A form-based process should be defined in the IMG under the path: Financial Accounting (New) → Contract Accounts Receivable and Payable → Business Transactions → Public Sector Tax Assessment → Form Processing → Form-Based Processes → Create New Processes.

This specific process is recognized as an attribute in the DFMCA_RETURN table and can be assessed through BRFplus. Notably, the form-based process termed TRM_REGISTRATION is incorporated within the default configuration.

For further adjustments, one can tailor a form-based process in the IMG via: Financial Accounting (New) → Contract Accounts Receivable and Payable → Business Transactions → Public Sector Tax Assessment → Form Processing → Form-Based Processes → Define Configuration of Processes.

Should the pre-configured form-based processes by SAP be misaligned with your specific needs, adjustments are possible.

Ensure that the configurations for your unique processes, as specified earlier, are retained. If there's a customization in the status profile or the FPM configuration variant concerning form bundle processing in the tax officer's dashboard, the system will dynamically fetch this configuration. In its absence, the canonical configurations provided by SAP will be operative. It is pertinent to highlight that the TRM_REGISTRATION process is encapsulated within this standard delivery configuration as well.

For the formulation of an entirely novel procedure, the expertise of a seasoned developer is indispensable. Customer processes have to be defined in the customer namespace.

In this IMG activity you can:

• Change the settings of the form-based processes delivered by SAP if they do not meet your requirements.
• Maintain the settings for the customer-specific processes that you have defined in the previous step.

If you maintain your own status profile or the Form Processing Framework (FPM) configuration variant for processing form bundles in the tax officer work center, then the system will read this at runtime. Otherwise, the standard settings delivered by SAP will be used.