Amending Tax Returns

PDF download from SAP Help Portal:

http://help.sap.com/erp2005_ehp_05/helpdata/en/04/9ca0150349406b95438794e8549736/content.htm
Created on June 19, 2014
The documentation may have changed since you downloaded the PDF. You can always find the latest information on SAP Help Portal.
Note
This PDF document contains the selected topic and its subtopics (max. 150) in the selected structure. Subtopics from other structures are not included.
2014 SAP AG or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose
without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG
and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by
SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be
liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express
warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. SAP and other
SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other
countries. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.
Table of content
PUBLIC
2014 SAP AG or an SAP affiliate company. All rights reserved.
Page 1 of 6
Table of content
1 Amending Tax Returns
1.1 Configuring the Amendment Framework
1.2 Duplicate Tax Returns Merging
1.3 Automatic Merging of Duplicate Tax Returns
PUBLIC
2014 SAP AG or an SAP affiliate company. All rights reserved.
Page 2 of 6
1 Amending Tax Returns

If you have to change a tax return that has already been billed, you can amend it in the Web Dynpro application for Tax Processing. This might happen because
a taxpayer files an additional return for the same tax type and tax period. The amendment features available in the Web Dynpro application for Tax Processing
are configurable using amendment action groups.
Note
If the program finds two duplicate tax returns in the system with different receipt dates, it automatically merges the two returns. For more information, see
Automatic Merging of Duplicate Tax Returns.
Prerequisites
An amended tax return is a duplicate return in the sense that there is already a filed tax return with the same business partner, contract account, contract
object, period key, and revenue type (tax type) in the system. In the Web Dynpro application for Tax Processing, the system automatically detects
duplicate tax returns in FICA event P333 and determines the amended tax return in FICA event P281. Finally, it sets the working mode to amendment
mode based on the logic implemented in FICA event P285.
We deliver default implementation FMCA_EVENT_P285_2 for this event. As default, when an invoice document has been created for a form bundle, the
system automatically switches to amendment mode when the tax officer opens an amended tax return.
The pushbuttons available in amendment mode are derived from the Customizing settings in the system. For more information, see Configuring the
Amendment Framework.
Features
To amend tax returns, we deliver the key features listed in the table below. Technically each feature corresponds to an action group that was defined in
Customizing. Each feature is displayed as a pushbutton (for example, Change Taxpayer) in the upper area of the Web Dynpro application for tax return
processing.
Feature Remarks
Change Taxpayer
Change Period
Change Postmark Date
Change Receipt Date
Merge Return When duplicate returns exist in the system, you can use this function to merge them
manually.
For more information, see Duplicate Tax Returns Merging
Amend Form We deliver a variety of functions through this action group. For example, add, remove,
supersede, transfer, retrieve forms or activate/obsolete forms. Additional information on
some features is given below.
Supersede
If you want one form to supersede another one, you select the source form (the
one to be superseded), press and hold the Control pushbutton, select the second
form (this is the one to supersede the first one. In the following explanation this
form is called superseding form), then choose Supersede .
Data of the As Amended view of the source form is moved to the As Filed view
of the superseding form. The original data of the As Filed view of the
superseding form is moved to its As Amended view. If there is no data in the As
Amended view of the source form, the program moves data of the As Filed view
to the As Filed view of the superseding form.
Note
You can enhance this logic in FICA event P282.
Retrieve
This function triggers a dialog box with version information. You can select and
restore one version. The selected version overwrites the current version.
Change Form Data
Transfer Forms If you have selected a form and chosen the Transfer Forms function, the system
displays a dialog box containing the target tax return. Once you confirm, the system
transfers the selected tax form to the target tax return and sets the status of the form in
the source tax return to obsolete.
Toggle Long / Short Form Long/short form refers to different layouts for a given form template. It is defined in
Customizing for Contract Accounts Receivable and Payable through the definition of a
related scenario for one form.
Example
The tax agency defines a short version of a form to simplify the filing of tax returns
for a special target group.
PUBLIC
2014 SAP AG or an SAP affiliate company. All rights reserved.
Page 3 of 6
By default, all scenarios are treated as long versions.
Create Note
Change Documents If you choose this function, the system navigates to the Document tab where the
Document Management Service is in change mode. For more information, see
Document Management Service.
Straight to Zero If this function is chosen, the system creates billing documents with zero amounts and
adjusts existing FICA documents to zero. The status of the tax return is set to
Processed .
Example
A tax officer expecting more accurate data from the taxpayer can choose this function.
Void Return This function is used to deal with tax returns filed erroneously. Technically, void means
straight to zero but sets the status of the tax return to obsolete .
After the functionality of an amendment action group has been executed and changes are saved, the system logs notes for each action group as well as the
processing reason.
Only authorized action groups are available in amendment mode for tax return processing (authorization object F_PSFH_AMD).
Amendment processing history is recorded as part of tax return change history.
1.1 Configuring the Amendment Framework

The amendment framework is a powerful and flexible tool that allows you to correct tax returns that have already been billed. This may be necessary because a
taxpayer files an additional return for the same tax type and tax period, or because a tax officer needs to change a tax return.
The purpose of having the framework is to allow customers to map different kinds of amendments and at the same time to uniformly handle changes to tax returns.
Furthermore, the amendment framework provides authorization checks, and it also logs all changes to a tax return thereby making the process safe against
manipulations, transparent, and traceable.
Prerequisites
In Customizing for Contract Accounts Receivable and Payable , you have maintained the form processing settings.
Business Package BP ERP TAX OFFICER 1.51 is applied to your system.
You have checked that the following events cover your requirements:
P280 for form supersede proposal
P281 for duplicate and amendment check
P282 for data merge
P285 to determine whether a tax return has to be processed in amendment mode
P286 for the overall amendment process
For more information about events, see SAP Library for SAP ERP on SAP Help Portal at http://help.sap.com/erp SAP ERP Enhancement Packages
ERP Central Component Enhancement Package 5 Industries in SAP ERP SAP Public Sector Collections and Disbursement Event Concept .
Procedure
The description is intended as a comprehensive list of activities that are required for the configuration of the amendment framework. For detailed information on
individual Customizing activities, select the relevant IMG object on the Configuration tab and display its documentation.
Note
SAP provides content for the amendment framework. Before creating your own entries, check the content delivered in your Customizing system.
1. Define which activities in the Form Processing Framework are relevant for amendments. To do so, choose Customizing activity Define Activity that Calls the
BRF for Form Processing .
Whenever one of these activities is triggered, the system initiates the level of amendment checks you defined in this activity.
2. Define processing options for amendments
This Customizing activity contains the essential parts for amendment customizing. The following table lists the various folders that are accessible from within
this Customizing activity and explains their usage
Customizing of Processing Options for Amendments
Folder Use
Define Actions You only have to define your own actions if the ones delivered by SAP do not meet
your requirements. Each action can be defined for a set of fields or pushbuttons on
the user interface, that is you can trigger multiple steps with one action. They are
individual units that have to be grouped in action groups to make them visible on
your Web Dynpro application.
Define Processing Reason(s) for Action Group(s) Here you can define multiple reason codes and their long texts that you can later
reuse across the actions belonging to the relevant action groups.
Define Action Groups Actions can be assigned to action groups. Action groups are only visible in the Web
Dynpro application if you have assigned this action group to an action group list and
the tax officer user is authorized to execute this action group. The action group is
PUBLIC
2014 SAP AG or an SAP affiliate company. All rights reserved.
Page 4 of 6
shown as a toggle button (for example, Change Taxpayer ) in the upper area of the
Web Dynpro application for tax return processing. An action group consists of at least
one action. To define a new action group, you create a name for it and then assign the
desired actions. Furthermore, you can assign one of the reason codes you have
defined in the previous folder.
Note
Actions Void Return , Merge Return and Straight to Zero are predefined as
action groups by SAP and you can also use them in your own list of action
groups.
Define List of Action Groups The action group list consists of at least one action group and allows you to
differentiate the pushbuttons displayed according to system status. For more
information, see the next table entry.
Note
Each action group has a two-digit number that serves as a key to determine the
order in which the pushbuttons are displayed. Action group number 99 is the
default action group, in other words, actions belonging to this action group are
automatically displayed, if the relevant action group list is activated. Activated
means that the action group list is assigned to the status the current form bundle
is processed with.
Assign Action Group List to Status To have different action group lists according to the status of the tax return, you can
assign your action group list to a system or user status. SAP provides a sample
delivery.
Define Reason for Amendment To categorize amendment requests, you can provide different reasons that are
displayed as radio buttons in the Tax Processing Web Dynpro application. Thus the
tax officer can select one of these reasons to document why an amendment had to be
made.
3. If you want to limit the amendment period, you can define a maximum period for late amendments.
1.2 Duplicate Tax Returns Merging

You can use this function to merge duplicate tax returns. In the system, tax returns are referred to as form bundles. A form bundle is a collection of forms that are
to be processed together. In the following explanation, tax return and form bundle are used as synonyms.
Integration
An amended tax return is a duplicate return in the sense that a filed tax return with the same business partner, contract account, contract object, period key, and
revenue type (tax type) is already stored in the system. The system automatically detects duplicate tax returns in FICA event P333 and determines the amended
tax return in FICA event P281. It sets the working mode to amendment mode based on the logic implemented in FICA event P285. We deliver default
implementation FMCA_EVENT_P285_2 for this event. By default, the system switches to amendment mode when a form bundle is edited again after an invoice
document has already been created.
Prerequisites
Whether the system checks a tax return for duplicates is determined by the Customizing settings and cannot be influenced by the user. The determining
parameter is the activity. For more information, see Configuring the Amendment Framework. In the standard delivery, activity Create Assessment - Print out
Separately triggers a duplicate check and if the system finds duplicates it issues a message. The tax officer can then select this tax return in the Web Dynpro
application for Tax Processing and choose the Merge Return feature.
Features
The forms in the form bundle are displayed under the Source Form Bundle list. The tax returns with identical header data that are already stored in the system are
regarded as duplicates and appear in the List of Duplicate Form Bundles. After you have selected the duplicate tax return you want to merge, it is displayed in
the Target From Bundle list. You can use various features for merging duplicate tax returns. In all cases you select the duplicate tax return that you want to merge
and then choose the appropriate pushbutton.
Pushbutton System Response
Move to Source and Void
Forms, documents and notes of the duplicate tax return are merged into the
source tax return.
The header data of the source tax return overrides the header data of the duplicate
tax return.
The form bundle number of the duplicate return is not changed to allow the
tracking of the filing obligation.
The status of the duplicate tax return is changed to Void .
Move to Target and Void In this case the merge direction is different. The duplicate return is the leading (target)
return to which the content is moved
Forms, documents and notes of the source tax return are merged into the
PUBLIC
2014 SAP AG or an SAP affiliate company. All rights reserved.
Page 5 of 6
duplicate tax return.
The header data of the duplicate tax return overrides the header data of the source
tax return.
The form bundle number of the source return is not changed to allow the tracking
of the filing obligation.
The status of the source tax return is changed to Void .
Move to Source with Correction and Void Same as for Move to Source and Void . Additionally, the system also merges the form
data of the As Corrected view to the source tax return.
Move to Target with Correction and Void Same as for Move to Target and Void . Additionally, the system also merges the form
data of the As Corrected view to the target (duplicate) tax return.
More Information
Amending Tax Returns
1.3 Automatic Merging of Duplicate Tax Returns

You use this function to automate the merging of duplicate tax returns. If the system finds two duplicate tax returns with different receipt dates during the billing run,
it automatically merges these returns.
Prerequisites
You have defined an activity that processes the form bundle using the Business Rule Framework (BRF). For this activity you have defined that the system
is performing the Amendment Check and Merge function.
Note
In the standard delivery, activity Create Assessment - Print out Separately performs the Amendment Check and Merge function
You define this activity in Customizing for Contract Accounts Receivable and Payable under Define Activity that Calls the BRF for Form Processing .
You have selected a form bundle (using either the mass activity or individual processing) with an activity for which the amendment check function was
configured.
Features
FICA events P333 and P286 control the merge logic. P333 performs the check for duplicates and P286 is used to process amended tax returns. Default
implementation of event P286 automatically merges duplicate tax returns.
PUBLIC
2014 SAP AG or an SAP affiliate company. All rights reserved.
Page 6 of 6