Professional Documents
Culture Documents
Investigative Case
Management
Case
Submitted to
Maldives Inland Revenue Authority
Male City, Maldives
By
Techwave Consulting
1
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
TEAM MEMBERS
Role
Name
Business
Contact
Business
Contact
Business
Contact
Business
Contact
IT
Team
Member
Fathimath
Rasha
Ahmed
Shareef
Hassan
Zareer
Aiman
Ibrahim
Mohamed
Najiz
Consultant
Rajendrra
Pula
Location
Designation
Email
&
Number
Male
CC Manager
rasha.f@mira.gov.mv
Male
Director
Male
Deputy
Commissioner
Male
Director
Male
Director
Male
shareef.a@MIRA.GOV
.MV
Zareer@MIRA.GOV.M
V
aiman.i@MIRA.GOV.M
V
najiz.m@MIRA.GOV.M
V
Siva.pula@techwave.
net
+9609637595
Document Reference
Date
As-IS document
30-3-2016
30-3-2016
Version History
Versio
Date
n
0.1
23-052016
0.2
07-062016
0.3
16-062016
0.4
23-062016
0.5
14-072016
0.6
22-08072016
0.7
29-082016
Phone
Comments
Modified by
Phani Velagaleti
Rajendrra Pula
Rajendrra Pula
Rajendrra Pula
Rajendrra Pula
Rajendrra Pula
Rajendrra Pula
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
Contents
1 Introduction
2 Business Scenario and Process Description
2.1 MIRA enterprise structure for Audit Process
6
2.2 Business Scenario 6
2.3 Lead Creation1213
2.3.1 Intelligence Section:
1213
2.3.2 Assessment Section
1314
2.3.3 Audit CBD, IBD 1314
2.3.4 LBD Yearly Audit Plan 14
2.3.5 Audit Batches convert leads from observations by risk& other teams
14
2.3.6 Special Request/ Desk review by Enforcement or all dept.
1415
2.4 Audit case registration and Taxpayer Factsheet and activities.
15
2.4.1 Activities 1516
2.5 Investigation Committee 2021
Criminal Investigation 2122
2.5.1 2122
Evidence gathering 2223
2.6 2223
Summon Interview
2223
2.6.1 2223
2.6.2 Search and seizure
2224
2.7 Investigation Report writing
2324
2.8 Objection Process 2325
2.9 Linked Processes
2526
2.10 2527
2.10.1 Process specific User Roles & Requirements for the Authorization
Concept 2527
2.10.2 Improvements to the Process Compared to As-Is Status
2527
3 Solution Approach
3.1 Mapping of MIRA process in SAP 2729
3.1.1 Investigation & Audit Process 2729
3.2 Master Data Concept
5056
3.3 High-Level Migration Concept
5056
4
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
Introduction
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.1
Registration
Compliance
Assessment
Investigation
Enforced Collection
Legal Service
As a result, Audit & Investigation process is easy to filter the cases according to
process department wise and forward the cases based on process wise to their
the respective departments.
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.2
Business Scenario
In Audit process, MIRA Audit & Investigation tax authoritiesMIRA verify verifies
(taxpayers) books of accounts / documents related to transactions liable to tax
and also of the deductions claimed from the total turnover effected byof the
Taxpayertaxpayer. The audit is usually carried out at Taxpayers taxpayers place
of business premises by prior appointment, where as in an Audit &
Investigations, no prior appointment is not mandatorymade.through an Audit &
Investigation notice, taxpayer is called to MIRA with his Books of Accounts to
assess taxpayers business activities according to law. In case of reviews, MIRA
will carry out desk work.
Taxpayers file and pay periodically paythe taxes liveable for each taxable period
on a self-assessment basis.under the Act on their own. For this periodic payment
taxpayer works out (self-assess) the amount of tax payable by him. Taxpayer will
file a tax return, while making the payment to MIRA which shows the While
paying this tax by Taxpayer files tax return which gives details of tax
payable.Audit & Investigation done by him or Auditor.
MIRA differentiate the reviews, audit & Investigation process based on Taxpayer
types like,
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
If as per thisDuring the audit, if any tax, interest or penalty is found payable
then notice is issued to Taxpayer taxpayer demanding payment of Taxtax,
interest and penalty. Review, Audit & Investigation (check all records of Taxpayer
if any doubt) is generally done in following cases.
1. Taxpayer liable to pay tax fails to apply for registration.
2. Registered Taxpayer taxpayer fails to file a tax return.
3. Tax authority wants to confirm whether tax returns filed or are correct and
complete.
11
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
At present the audit & Investigation activities are carried out manually and then
the auditing authorities record their observations and other findings in the MIRA
Case Manager system and this process provide results in issuance of report and
release to respective Committee. In SAP environment all these processes are a
going to be automated. The authorities will be able to issue notices, to schedule
hearings, receive submissions, to calculate the tax liability due, and to see the
entire master data as well as transactions data related to particular Taxpayer
taxpayer in the SAP CRM ICM system.
12
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
13
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
14
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
Intel identified by
intelligence
section
Receive
special
request
from
other
departments
or
within
departments.
Annual
Audit
Batch prepared by
LTS ( Large Tax
Service )
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
Initial
10
Field
Procedure
11
Post
Procedures
12
12.1
13
14
16
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
15
16
17
18
19
20
21
Criminal
Once the investigative procedures are completed
Investigation case result is criminal case is closed. Team will resumes the
closed
audit case again.
If criminal case is to be prosecuted, it is forwarded to
legal department. Legal Department will start their
Send
to
Legal
process according to legal issue and closed the report
Dept.
and send it back to Investigation Department for
further audit process.
After completion of audit works, the case is forwarded
Report
send
to
to audit committee for approval. If they reject, which
Audit Committee
will go back to post audit procedures.
Audit
concluded
Once audit report is approved by audit committee, it
and
relevant
will be communicated to taxpayer and relevant
departments
departments via Post / EMAIL
notified.
If taxpayer objects, team will receive objection notice.
Objection notice Here a separate objection case will start (New
received
investigation case).
Review
Process
dispute resolution
Send to Objection
/dispute
resolution
committee
22
ORR
finalized
communicated
23
Assessment
Procedure
Activi
ty No.
Activity
17
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
Intel identified by
intelligence section
Receive
special
request from other
departments
or
within
departments.
Audit
prepared
Profiling.
Leads assign
by
Batch
Risk
18
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
Lead Analysis
Lead Approval
Audit
Creation
cases
Rejected/Suspende
d cases
10
Field
Procedure
Audit
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
writing
11
Post
Procedures
12
Case
sent
investigation
committee
Audit
to
12.1
Investigative
Committee
13
Criminal
case
assigned, audit on
hold
14
Evidence gathering
(Summons,
Raids..etc)
Investigation evidence
summons, raids etcetc.
15
Criminal
Investigation
closed
case
16
17
gathering
which
include
20
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
18
19
20
21
Audit
concluded
and
relevant
departments
notified.
Objection
received
notice
Review
Process
dispute resolution
Send to Objection
/dispute resolution
committee
22
ORR finalized
Communicated
&
21
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.3
Lead Creation
22
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.3.1
Intelligence Section:
All the observations which are sent to Intelligence and Forensic Section (including
whistleblowing observations) will be created as leads in the system.
Supervisor receive all leads in his inbox in SAP CRM system along with
issues.
Every lead has a unique Id number
Once lead opened in SAP ICM, system will automatically identify taxpayer
and factsheet is available to responsible employee for further analysis. For
non-registered parties, supervisor will have to feed the required data.
Once the lead has identified, supervisor will assign the case to an analyst
and the case will be available in analysts inbox.
Analysts will get a note in their worklist regarding new lead has been
assigned. Analyst will do a detail profiling of the lead and shall prepare an
analysis report.
Report shall be sent back to supervisor for approval with an attachment.
Supervisor will review the report and approve the lead.
While approving the lead, supervisor shall make one of the following
decisions.
o Pass the lead to another department
o Close the lead
o Send back the lead for further analysis
Once the lead is send to another department, it will be shown in the
relevant departments supervisors inbox as a lead received for analysis.
Relevant department supervisor has to convert the lead to an audit case
based on their criteria.
If the lead is related to a department that does not use SAP ICM, the lead
shall be sent through an email.
If lead is not required further analysis, supervisor will close the lead with
proper notes.
23
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.3.2
Assessment Section
24
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.3.3
All the observations carried out by audit departments will be created as leads
in SAP ICM. This includes desk reviews, special requests and audit batches
created by risk profiling.
25
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.3.4
26
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.3.5
Audit Batches convert leads from
observations by risk & other teams
All the observations carried out by audit departments will be created as leads
in SAP ICM system. Observation includes desk reviews, special requests and
audit batches created by risk profiling.
Intelligence section create audit batches based on risk profiling and upload
them into SAP system as bulk leads.
Bulk leads shall be forwarded to their respective departments based on
employee responsible and organization.
Respective supervisor will reviewsreview bulk leads in his inbox.
During these reviews, supervisors will set criteria for selection which
needs to be continued as a Lleads in the system and which are should be
closed as a lead.
Based on the criteria set supervisors reviews the leads and convert the
lead into an Audit case.
If the lead is not converted into an Audit, it will be closed by the
supervisor.
27
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.3.6
Special Request/ Desk review by Enforcement
or all dept.
Departments who have access to SAP ICM will create special requests as
leads and will send to relevant Audit department.
Audit department itself can create lead based on the issues they identify
within an existing case.
Once the lead is created, supervisor will assign the lead to an auditors and
the lead will be available in auditors inbox for further action.
Auditors will do review of the lead and will prepare a review report.
Report will be send to manager through SAP system for approval.
Supervisor reviews the report and approves the lead.
While approval supervisor has to decide to make any of the following
actions with a remark
o Convert the lead to an audit case
o Close the lead
o Send the lead to another department
If the lead is related to a department, who does not use SAP system, the
lead shall be sent through email.
28
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.4
29
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.4.1
Activities
30
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
o
o
Document Analysis
Document analysis may occur at any time during the course of audit. It can
occur at taxpayer premises or at MIRA premises.
Responsible employee will maintained a log which contains what are
documents have been assessed by the audit team.
o Responsible employee need to maintain a log which has all analysis
and tests carried out during the audit. This may or may not include
a document obtained during the audit. All audit workings and
analysis need to be update in log, which shall be available in
RECORDS of case.
o During such analysis if the auditor detects any issue, it needs to be
identified via Issue Log
Issue Log
o
Issue log has various issues identified during audit of case based on tax
types. Responsible employee will pick the issue in the case based on their
findings during the audit.
GGST Audit;
o Sales Issue;
o Taxable Sales Issue,
o Zero-rated Sales Issue,
o Exempt Sales Issue,
o Time of Supply,
o Input Related Issues,
Missing Invoices
Non-compliant Invoices
High value Invoices
TGST Audit;
o Sales Issue;
32
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
o
BPT Audit;
o Sales Issue;
o Expenses Issue;
WHT Audit;
o Undeclared Payments
o Declared Payments
GRT Audit;
o GRT not declared
o Tax Calculation Error
BnPT Audit;
o Incorrect provision calculation
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
o
o
o
o
o
After completion of field audit, auditor will prepare the Audit Report,
using report writing action profile in action list and it will be in PDF
format.
This request will be forwarded to the supervisor of the audit to
review.
After reviewing the case, supervisor will approve the request to
prepare the audit report.
Based on the issue logs identified during the case, Audit Report will
be prepared.
This audit report and working paper will be attached to the SAP
system and send for approval to the supervisor.
The supervisor will approve the working paper and the audit report.
o
o
o
After completion of field audit, auditor will prepare the Audit Report,
using report writing action profile in action list and it will be in PDF
format.
This request will be forwarded to the supervisor of the audit to
review.
After reviewing the case, supervisor will approve the request to
prepare the audit report.
Based on the issue logs identified during the case, Audit Report will
be prepared.
35
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
This audit report and working paper will be attached to the SAP
system and send for approval to the supervisor.
The supervisor will approve the working paper and the audit report.
36
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
o
o
o
o
o
o
o
o
38
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.5
Risk Profiling
The investigation committee members or the auditor can easily find the
cases through INVESTIGATION COMMITTEE option in Navigation Bar. Click
on the tab, responsible employees will know the cases existing with
investigation committee.
If an audit team detects any issues which needsissues which need to be
investigated, the auditor shall prepare a case report with the approval of
the supervisor assign them to an auditor to prepare a case report.
The auditor will prepare a case report against case and send it to the
supervisors approval.
Once the supervisor approves the case report, case will automatically be
forwarded to investigation committee team inbox with case report and
investigation division supervisor will be notified by email or notification in
his inbox.
Investigation division supervisor shall review and forward the case to
committee members along with committee meeting request.
The Committee meeting request shall be subject to the availability of CG &
DCG.
In the investigation committee meeting, after discussing the case,
committee will take one of below actions.
o Hold the audit case and intitiateinitiate a criminal investigation
o Continue the audit case.
39
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
40
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.5.1
Criminal Investigation
41
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.5.2
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
Past audit history: Investigators can view past audit history (event log) of
the taxpayer and related party within the system.
Lead reports: All lead reports will be available in SAP ICM
43
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.5.3
Evidence gathering
44
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.5.4
Once the investigation case plan is approved, evidence gathering process starts.
There are various methods of evidence gathering which includes:
SAP ICM system has all features to handle evidence gathering.
o Summon Interview and statements
o Search and seizure
o Third party document requests
o Bank requests (explained in audit process)
45
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
46
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.5.4.2
If an Investigator wants to summon a person regarding a case, he/she
shall create a summon request form in the system and send it for
supervisors approval. (Format of summon request froorm MIRA)
Once a summon request is approved in system by supervisor,. SAP ICM
will create a summon interview (like as an appointment) activity will be
created in the system and send notification to taxpayer regarding
appointment of summons.
Summon interview appointment event includes the details of the parties
involved in meeting, date, time, place of summon etc.
Once a summon request is approved by the supervisor, a Summon
Order form will be created in system automatically. However, it shall be
signed by the Commissioner General and it shall be hand delivered.
After completion of summon meeting with taxpayer, investigation
employee will update the meeting minutes or any documents or audio /
video files in to the case. Investigator will prepare the statement of
interviewof Case.
Once the witness or suspect statement is completed, investigators will
send the statement to supervisor for approval. Once he approvesd,
investigator will get the signature of the suspect/witnesses on statement
and upload to SAP ICM as an attachment. After upload in to the system,
investigator will change the status of action should beto summon closed.
47
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.5.5
48
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.6
Once the Evidence gathering process is completed, the report writing process
begins
In the SAP ICM system investigator has to create an activity for report
writing assignment box.
Since report cannot be incorporated into the system, manually word
document shall be prepared and uploaded to Report writing - block
Also all the annexure (PDF) shall be attached to the Report writing block.
Once investigator attached the report, execute the action for supervisor
approval.
Once the supervisor approves, Report will be sent to legal along with
annexures for legal review.
Once legal review is completed, legal team will send their report as an
attachment to case. Notification will be triggered to investigator for review
report enclosed to case.
Investigator will make the necessary changes to report and send the final
PDF version of the report to supervisors approval.
Once supervisor approves the report it will be sent to Legal division and to
CG and DCG.
Legal department will send the case to prosecution, once prosecution has
reviewed they send acceptance notice to investigator. Investigator shall
upload the notice report writing block in case and all activities belongs to
case will be closed.
When reporting writing activity /event closed, investigator will close the
criminal activity will be closed by investigator. Case will be available to
view the case in all stages.
49
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.7
1
Objection Process
Creating MIRA 903 Notice of Objection form in SAP ICM.
-
Upon receipt of all forms, the supervisor will create the FORM and
update the details and attach the document.
- Form details are TP Name, TIN, Tax Type, NOTA Ref/date, summary of
contention and Date of Notice of Objection.
- Objection process will be available as a separate assignment block.
Any form entered can be ACCEPTED and converted to an objection
activitycase or the form can be rejected in which case the process is
concluded.
- Where the form is accepted, a new objection caseactivity will be
created. The activitycase should appear in supervisors inbox with the
audit unassigned cases number.
- Where the form is accepted the status in the Form tab will show as
accepted
- Where the form is rejected a signed letter needs to be attached to the
decision. The status in the form tab will show as rejected. This
concludes the work flow for such forms.
Assigning Cases from Unassigned TabSupervisors inbox.
- When a case is assigned to an Objection Officer, Case status will be
available.
- The case now should appear in the tab ongoing review and the status
should be review ongoing
Additional Functions through activities in SAP ICM.
a Document Request: If the objection officer requests for a document,
execute email activity for required email. Activity log will be
available in history.
b Meeting: Meeting / appointment activity will be available to
objection officer. Log will be available in history of process.
c Queries: If Objection officer makes a query to the auditor then such
shall be recorded in case. An editable form shall be created by the
officer.
- The Objection Officer will initiate a query or notes, they will write the
query in Notes tab of case.
- Officer will send and the Link it will be Email to the addressed party.
- Officer will add auditor as partner function in the case list and query
notes will be mail to him.Once the form is created, the objection officer
will send the form via email to respective auditor.
- Auditor will complete the form and send back to objection officer.
50
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
6
7
Once officer released to all parties belonging to case, auditor will get
the notification of query notes. Auditor will satisfy with notes he will
close the query notes if not send it back for more notes.
- All queries need to be closed for the Draft Report to be sent for
Approval.
Draft Report
- The Draft Report shall be sent to Supervisor for Review.
After it is sent the status should be read as Report sent for Review.
If rejected, revert to review ongoing status.
- If approved, then the status should be made to Report approved
Approved Report
- Approved Reports by the supervisor shall be sent to Appeal and
Objection Committee (AOC) directly.
AOC tab
- All cases to AOC will be viewed from AOC tab in navigation bar.
- If AOC approves the case then supervisor will select approved from the
AOC tab. sStatus should be updated to AOC approved.
- If rejected it should be reverted to Report send for review status and
should no longer be in the AOC tab.
All approved cases should be in completed status and Objection Review
Report (ORR) should be attached to case.
51
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.8
52
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.9
53
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.10
Upon receipt of all forms, the supervisor will
create the FORM and update the details and attach
the document.
54
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.11
Form details are TP Name, TIN, Tax Type, NOTA
Ref/date, summary of contention and Date of Notice
of Objection.
55
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.12
Objection process will
separate assignment block.
be
available
as
56
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.13
Any form entered can be ACCEPTED and
converted to a objection case or the form can be
rejected in which case the process is concluded.
57
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.14
Where the form is accepted, a new objection
case will be created. The case should appear in
unassigned cases.
58
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.15
Where the form is accepted the status in the
Form tab will show as accepted
59
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.16
Where the form is rejected a signed letter
needs to be attached to the decision. The status in
the form tab will show as rejected. This concludes
the work flow for such forms.
60
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.17
61
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.18
When a case is assigned to an Objection
Officer, Case status will be available.
62
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.19
The case now should appear in the tab ongoing
review and the status should be review ongoing
63
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.20
Additional Functions through activities in SAP
ICM.
64
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.21
Document Request: If the objection officer
requests for a document, execute email activity for
required email. Activity log will be available in
history.
65
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.22
Meeting: Meeting / appointment activity will be
available to objection officer. Log will available in
history of process.
66
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.23
Queries: If Objection officer makes a query to
the auditor then such shall be recorded in case.
67
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.24
The Objection Officer will initiate a query or
notes, they will write the query in Notes tab of case.
68
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.25
Officer will send and the Link it will be Email to
the addressed party.
69
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.26
Officer will added auditor as partner function in
the case list and query notes will be mail to him.
70
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.27
Once officer released to all parties belonging
to case, auditor will get the notification of query
notes. Auditor will satisfy with notes he will close
the query notes if not send it back for more notes.
71
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.28
All queries need to be closed for the Draft
Report to be sent for Approval.
72
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.29
Draft Report
73
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.30
The Draft Report shall be sent to Supervisor
for Review.
74
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.31
After it is sent the status should be read as
Report sent for Review.
75
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.32
76
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.33
If approved, then the status should be made to
Report approved
77
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.34
Approved Report
78
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.35
Approved Reports by the supervisor shall be
sent to AOC directly.
79
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.36
80
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.37
AOC tab
81
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.38
82
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.39
If AOC approves the case then supervisor will
select approved from the AOC tab. status should be
updated to AOC approved.
83
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.40
If rejected it should be reverted to Report
Approved status and should no longer be in the AOC
tab.
84
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.41
All approved cases should be in completed
status and ORR should be attached to case.
85
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.42
SL. NO.
1
2
3
4
5
6
Linked Processes
PROCESS DESCRIPTION
Audit
Investigation
Committee reports
Legal Departments
3rd Party Document service reports
Media Reports
86
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
Pre-Audit Process
MIRA pre- audit process conduct on observations by below departments.
Special Request Investigation Department
Risk Profiling
Other Special Request any Dept.
These units performs a preliminary review of observations to see if it is free of
errors, has been properly completed, and contains all necessary information. If
they found errors or any observed issues / problems in observations then
investigation dept. convert them as a LEAD & SPECIAL REQUEST in the CRM
system. Special Requests are routed to respective departments based an issue
observed, mostly on Registration & Compliance.
87
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.43
88
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.43.1
MIRA Audit team has a functionality on registration of Taxpayers based on recordcompilation function, comprising identification and registration of taxpayers,
constitutes an important task for tax administrations. Although tax authorities
tend to focus on auditing of taxpayers who are already known and registered,
they should also put efforts in including in the tax-return system all persons and
companies that have succeeded in escaping their notice. Management of
taxpayers records consists of three basic functions: creation, updating and
deletion.
MIRA has an effective tax system encourages taxpayer compliance with
registration obligations. There to the tax community should be provided with
clear and comprehensive descriptions of the requirements that lead to
registration and tax administrations should facilitate taxpayers to make the
procedural requirements as easy as possible Online registration by taxpayers
adequately serves the needs of taxpayers thus promotes compliance, reduces
the number of unintentional errors and is cost efficient.
MIRA aims to ensure compliance with registration requirements by collecting and
verifying third party information on the existence of taxable sources of income
and other taxable elements requiring taxpayers to register for the relevant types
of taxes, to file returns when required, and by actively informing potential
taxpayers on their registration and filing obligations and to provide them with the
necessary (electronic) forms and documents. In addition to that, the MIRA
promotes compliance with registration requirements through surveys of potential
taxpayers for instance by physical inspection of business premises and private
residences in selected areas, by visiting starting business, by providing one stop
services for (starting) businesses to inform them on their rights and obligations
in their relations to the MIRA, by on the spot checks at markets and other trade
locations, by inspection of cars and also by searching sources of information on
economic activities such as newspapers and the internet.
To avoid misuse of registrants and false registrants the MIRA also developed
policies and practises to detect and actively deregister those registered
taxpayers who have become inactive and even more falsely registered persons
who register with the intention to misuse their registration with the tax authority.
89
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.43.2
The Tax Identification Number (TIN) is an important tool to easily identify citizens
and businesses for tax purposes. It enables MIRA Tax Administrations to easily
and effectively link the information included in its different data bases with
reference to each taxpayer, and it is a very effective instrument for facilitating
the exchange of information between tax administrations and taxpayers and also
with employers and others who have a withholding obligation or an obligation to
provide third party information to the tax administration and also for the
exchange of information between Tax Administrations and other governmental
bodies and with Tax Administrations from other countries. The use of the Tax
Identification Number helps to improve the efficiency in the information
management and enables and facilitates the realization of matching controls.
Audit team Identified fraud registration of taxpayers is part of audit process and
provide collective information to Registration Department through notifications.
90
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.44
Compliance Process
91
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.45
Assessment Process
Most tax administrations use the self-assessment system for their most
important taxes, such as individual business tax and corporate income tax. In the
Netherlands, this is not the case for the personal income tax, the corporate
income tax and a couple of less-significant taxes in terms of revenue. These
taxes are administered on the basis of administrative assessment, meaning that
the tax administration formally does the assessment of the tax due based on the
information declared by the taxpayers. This system is known as administrative
assessment, which is generally more costly for the tax administration and less
costly for the taxpayers than the self-assessment system that requires taxpayers
to assess their tax obligations, to calculate the tax due and to pay their taxes on
their own initiative within a certain timeframe and that puts most of the
administrative burden on the taxpayers.
92
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
ACTIVITY
Cases
selected
for
assessment after Risk
factor analysis or cases
for
assessment
generated
in
other
module will be assigned
to
the
assessment
officers.
Selects
a
list
of
Documents that will be
required for assessment
from
a
Master
List
available in the system
Prepares
Assessment
Notice
with
Taxpayer
details, Taxable period,
Amount & deadline for
payment.
Sends Assessment Notice
to taxpayer by post and
email attachment
93
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
found
to
be
Document Complete
10
11
Satisfactory to POB
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
12
95
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.46
Investigation Process
96
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.46.1
Process steps
97
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
ACTIVITY
Inbound
Observatio
ns
Create
Leads
Lead
Analysis
Case
Creation
Case
Severity
6
7
Severe
Issues
Start
Investigati
on
Investigati
ve
case
report
98
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
Selects
a
list
of
Documents that will be On the basis of analysis, audit officer selects
required for the audit the list of documents that are required to
from a Master List audit the Taxpayer and find them in FCC.
available in system
Case severity
Sever cases
99
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
5.1
5.2
Investigation
Criminal
case
5.3
Investigation
NOT Criminal
case
5.4
5.5
Prepare
report
5.6
Submit to Investigation
committee
5.8
Criminal
Report
5.9
CIR report will closed Legal Department will start their process
and returned back to according to legal issue and closed the report
respective department. and send it back to Investigation Department.
5.1
5.11
team
will
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
Non-severe cases
6.1
Send
Request
Taxpayer
10
11
12
Document
completed
101
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
13
14
15
16
17
18
19
Send
report
Taxpayer
102
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
20
21
22
Re-start
Audit
again prepare
report
created
and
report
and
103
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.47
Audit Process- Individual Taxpayers/ Corporate
Taxpayers
104
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
105
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
1.1
1.2
1.3
Activity
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
Audit
information
Taxpayer
Taxpayer
approval
Supervisor approval
Audit notice release
Suspend Cases
Initial
Work
10
to
factsheet
Meeting
&
&
Field
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
11
12
13
Taxpayer
replied
comments & required
documents
Updated
Audit
report
send to committee for
approval
14
If Report approved
committee
by
15
108
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.48
ACTIVI
ACTIVITY
TY NO.
Investigatio
Cases will be forwarded to Large tax Audit department
n & other by director / manager to assess the Taxpayers. Manager
Dept.
directly forward to Supervisor to allocate them to team.
1.1
Cases
Allocation
1.2
Case
sheet
review
1.3
Special
Request
Review
Report
Studies the
case
with
the help of
related
books
of
documents,
Taxpayer
Related Info
&
Risk
Parameters.
109
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
Audit
information
to Taxpayer
Taxpayers
factsheet
approval
10
11
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
12
13
14
required
documents
Updated
Audit report Audit Officer updated with taxpayer comments to Audit
send
to Report and send to committee with Manager Approval
committee
workflow.
for approval
Audit report approved by committee with changes or
If
Report
without changes will communicated to Audit officer.
approved by
Audit officer will send committee approved report to
committee
taxpayer through email.
If report not Audit report will revert back to audit officer to track
approved by again case observations and process will start from step
committee
8
111
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.49
SL. NO.
1
2
3
4
5
6
Linked Processes
PROCESS DESCRIPTION
Audit
Investigation
Committee reports
Legal Departments
3rd Party Document service reports
Media Reports
112
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.50
113
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.51
114
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.52
Process specific User Roles & Requirements for
the Authorization Concept
Below is list of business role identified for Audit & Investigation process. Based
on the business role & user master record, authorizations are provided to the
audit officer. Kindly refer to Annexures No. 7 for details about Role &
Responsibilities Matrix.
BUSINESS ROLES
Assistant Commissioner General
Director General
Director
Audit Manager
Team Leader
Audit Leader
Audit Assistant
Audit Member
Investigation Officer
Case Officer
Analyst
115
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
2.52.1
The SAP Tax and Revenue Management & CRM for Public Sector package
provides a single view of the taxpayer, helping MIRA to enhance revenue
collection efficiency and constituent services through consolidated and
coordinated tax processes. MIRA can benefit from:
A complete view of taxpayer and constituent accounts and details
Increased voluntary taxpayer compliance through a one-stop online collection
function that provides a single face of your agency to taxpayers
Decreased outstanding receivables, enhancing overall collection rates and
reducing non-compliance
A single logical master-data framework, with selective views according to the
individual needs of the respective public service
Shorter inquiry response time, where taxpayers can easily obtain quick, ad hoc
information on their account status, including open balances, filing obligations
and deadlines, and anticipated refunds
Improved call center contact rates, because inquiries can be routed and
answered faster
Increased efficiency through mass processing of tax returns
Faster detection of noncompliant taxpayers and nonfilers
More efficient use of resources in Investigation process
116
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
Solution Approach
117
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
3.1
118
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
3.1.1
Investigation Process:-
119
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
PURPOSE
Other Parties
To Capture Parties
Object
To Capture Evidence
Location
Taxpayer
Information
Parties Involves
Relationship
Investigative Record
Notes Types
Taxpayer Overview
Consolidated Return
Audit
&
Investigation
from
120
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
121
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
3.1.1.1.1
Incidents
122
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
3.1.1.1.2
Activities
o
o
o
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
Legal references
If an activity requires legal justification, we can define a legal reference.
Change history
Shows all changes made to the activity data. Change History and Partner History.
Note that change history is only available for activities. The history enables to
see the essential changes an object has undergone up to the present point which
can display information on all changes that have been made to its data, and
former employee that have been involved.
Partner History
Available from the Parties Involved assignment
history displays a list of all the currently valid
business partners with the object concerned. The
example, a taxpayer, service provider, owner, or
validity period for each relationship.
124
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
3.1.1.1.3
Parties Involved
125
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
3.1.1.1.4
Audit / Investigating officer captures the source of information & reliability of the
source in other parties assignment block, Authorized persons or Investigation
officers superior will only have access to Suspect information.
Below is the list of relationship available for Audit/Investigating officer.
NAME
Proprietor
Partner
Director
Employee
of
Taxpayer
Consultant
/
Advisor
Supplier
Customer
Transporter
Creditor / Payer
Debtor / Payee
DESCRIPTION
Taxpayer- Proprietor
Taxpayer -Partner
Director of Company
Employee of Taxpayer
Consultant / Advisor working for Taxpayer
Supplier of Taxpayer
Customers of Taxpayer
Transporter of Taxpayer
Creditor / Payer of Taxpayer
Debtor / Payee of Taxpayer
126
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
3.1.1.1.5
Object / Evidence
Objects are physical items that are of interest for work, such sales documents,
purchase invoices ..etc They are typically secured during an incident or
discovered as part of an investigation.
Audit/Investigating officer will capture details about evidence in Object Assignment Block If during verification, Audit/Investigating officer finds some
documents that will be useful as a direct or in direct evidence; he scans the
documents and uploads them against the case. He assigns the documents with a
unique id & assigns relationship with parties involved or location.
Objects can be created directly from cases, leads, or incidents. The object details
contain basic information about the object, such as ID, name, and category, and
whether the object has been secured
Additional information is used to describe the object in greater detail and provide
an overview of its relationships to other entities:
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
128
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
3.1.1.1.6
Location
LOCATION
Undisclosed
Place
Business
Undisclosed
place
residence
Shared place of business
Shared place of residence
Any Other place used
of
DESCRIPTION
Undisclosed Place of Business of Taxpayer
of
129
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
3.1.1.1.7
Investigation Record
Any documents or emails during Audit & Investigation process will be captured
under respective folder and linked to the case. These documents will be stored in
in DMS with a unique number generated by investigative record automatically.
FOLDER NAME
RECORD
INVESTIGATION
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
3.1.1.1.8
Taxpayer Information
Investigation/Audit/Investigating officer will get a 360 view of Taxpayer data like
return, Audit & Investigation, payment information directly from SAP CRM System
by clicking tax officer overview work centre.
Tax Officer Overview work centre will have below information -
INFORMATION DETAILS
Taxpayer
Basic
Information
Taxpayer Ledger
Taxpayer Return Details
Taxpayer Payment History
Taxpayer
Audit
&
Investigation History
Consolidated Returns
Recovery Status
DESCRIPTION
Taxpayer Information
Ledger Information of Taxpayer
Complete Return Details
Payment Details of History
Audit History of Taxpayer
Return details on Dynamic Date
Recovery history
Taxpayer Overview
From Taxpayer overview work centercentre, Audit/Investigating officer can access
below three functionalities
Taxpayer Overview
Audit/Investigating officer can view the most current information on any
Taxpayer at any given time, like Taxpayer obligation and payments. The system
will also display sub ledger account for each revenue and tax type.
Consolidated Return
131
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
132
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
3.1.1.1.9
Notes Type
NOTES TYPE
Preliminary Notes
Pre Visit Notes
On Visit Notes
Post Visit Notes
Document Notice
Hearing related Notes
Legal Notes
Order Related Notes
133
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
134
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
135
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
Audit/Investigating officer captures the date & time of service of audit notice by
creating new activity.
136
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
If Taxpayer does not submit documents within stipulated time after service of
Audit & Investigation notices, Audit/Investigating officer sends reminders through
email / post for submission of documents.
Audit/Investigating officer can schedule an action for reminder email from
schedule action assignment blocks.
137
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
138
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
Select MAIL FORM in search list before sending email to concerne department.
After selection of Bank statement MAIL FORM, send email to concern department
with Mail form.
139
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
140
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
Audit/Investigating officer saves visit activity & collects signature of the Taxpayer
on print copy of visit activity. Investigation officer attaches it to the case for
future reference in the system.
During the visit Investigation/Audit/Investigating officer decides whether further
documents or hearing is required or not. If it is required, then he provides a time
slot to the Taxpayer to come to MIRA office.
Audit/Investigating officer creates a new appointment from calendar.
141
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
If visit to the Taxpayers POB is not possible, Audit & Investigation cases will be
closed & corresponding Audit & Investigation case will be created & allocated to
the same Audit/Investigating officers worklist.
If Audit/Investigating officer is not satisfied with the visit, he may go for revisit to
the Taxpayers place of business & captures the visit details in visit activity. If the
Investigation officer is not satisfied with the revisit or revisit is not happened,
then Investigation officer cognizance of dis-functional POB taken in hearing.
142
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
143
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
144
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
145
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
Taxpayer will attend the hearing on the appointed date & time. In case further
hearing is required or hearing is adjourned for some reason, audit officer
provides new date to Taxpayer.
In case Taxpayer does not attend the hearing or submit additional document
then Investigation/Audit/Investigating officer will issue a Show-cause notice for
ex parte Audit order.
146
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
147
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
148
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
Upon receipt of all forms, the supervisor will select the FORM and
update the details and attach the document.
Form details are TP Name, TIN, Tax Type, NOTA Ref/date, summary of
contention and Date of Notice of Objection.
Objection process will be available as a separate assignment block.
149
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
If MIRA employee has more than one business role assigned his user id, he has to
select the business role for which he wants access.
Below is the list of business roles identified for MIRA audit process.
BUSINESS ROLES
Director General
Audit Manager /Supervisor
Team Leader
150
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
151
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
152
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
STATUS NAME
In creation
New
In processing
With
Investigative
Department
with Audit Department
with
Assessment
Department
Prepare Fact Sheet &
approval
from
manager
Open
New
In Process
For release
For release
For release
For Approval
153
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
Processing complete
Complete / closed
Closed
Confirmed
154
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
155
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
3.1.1.17.1
Search criteria
Below is the list of Ssearch parameters identified for MIRA are listed below.audit
process.
SEARCH PARAMETER
TIN
Name
Last
Period
Date Type
SAP STANDARD
Contract Object ID
Identification field
of BP
First Name of BP
Last Name of BP
From & TO
Creation Date
DESCRIPTION
TIN Number of Taxpayer
Personal Account Number
First Name of BP
Last Name of BP
From & TO
Date on which case Created
156
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
3.1.1.17.2
The inbox result list, from where the employees select their tasks, contains the
following columns:
RESULT COLUMN
TIN
SAP STANDARD
Contract Object ID
DESCRIPTION
TIN
Number
Taxpayer
PURPOSE
of
157
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
Status Of Case
Case ID
Case Type
Main Emp.
From
To
To
Status Of Case
Case ID
Case Type like IBA, BA
Main Emp of case
Date From selection
Start
Date To selection Start
158
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
3.1.1.17.3
Quick Search
Quick search facility can be used instead of manual search, to search for predefined selection parameters for business role.
Below is the list of quick searches identified for MIRA audit process.
NAME
STATU ASSIGNED
PRIORIT
MAIN
S
Y
Attention
Open
Me
High
Audit Case
Alert
My Immediate Tasks
Open
Me
High
Audit Case
Team Immediate Tasks
Open
My Group
High
Audit Case
Team Tasks
NA
My Group
NA
Audit Case
&
159
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
3.1.1.17.4
Save Search
In addition, all users can define and save their own search variants (Save
Search As). These can be accessed via the pull down menu in Saved
Searches.
160
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
DESCRIPTION
Complete Audit of Taxpayer
Direct Audit & Investigation
161
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
162
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
DESCRIPTION
Very High
High
Medium
Low
163
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
3.2
Master data will be available in CRM system via middleware integration to TRM
system. Master data & Transactional data synchronized and Delta process is
activated in both system for any data changes. So both systems will display
same master data without inconsistency.
NON SAP systems (NEXUS, POLICE, CUSTOMESCUSTOMS & ARREARS) master
data will be display as a POP-UP in CRM systems via RFC functional Modules.
164
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
3.3
165
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
3.4
Gaps
Once the 2nd dunning notice is issued to the taxpayer SAP ICM will create
an automatic lead for the relevant tax type
Once save the case, action email will triggered to all partner functions
about case details as a hyper link of case number.
166
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
167
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
3.4.1
Solution of Gaps
168
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
Core Configuration
169
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
4.1
170
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
4.1.1
The following section describes the master data required for the processes and
functions described in the business requirement.
171
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
172
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
1. Business Partner
a. Taxpayer
b. Relationship (Contacts)
2. Contract Account (Where Taxpayers Financial Transactions are posted)
3. Contract Objects - (Acts, Additional Contract Objects for Taxpayer under
VAT Act are ITC -Input Tax Credit, Goods Return, Debit/Credit notes )
4. Chart of Accounts (List of General Ledger Accounts )
5. Profit Center ( Location of MIRA)
173
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
To assist the police officer in preparation for a later trial for the attorney
general
Locations
Objects
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
Incidents
Activities
Cases
Leads
Introducer
Merger/Amalgamation from
Demerger from
Contract Account:
Each Business Partner (Taxpayer) is assigned to one contract account and all the
financial postings for the Business Partner (Taxpayer) will be posted to this
Contract Account. The Contract Account master record defines the procedures
for posting and processing the line items of a given contract account. For
example, Clearing Category, mode of payment, Dunning Procedure,
Correspondence control etc.
Contract Object (Acts):
MIRA collects taxes under several tax laws. Tax collected under each Act is
separately accounted. In case of MIRA, Contract objects would represent the
various tax laws for which the taxpayer is registered i.e. BPT, GST, Green Tax and
Police fines etc. accordingly in MIRA
contract objects would be created.
Additional contract objects for Taxpayer under VAT Act are ITC, (Input Tax Credit)
Goods Return, Debit/credit notes.
For more detail kindly refer master data BPD.
175
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
4.1.2
Leads
176
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
Registration Lead
Compliance Lead
ICM Leads
177
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
4.1.3
Case Type
178
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
4.1.4
Investigation Case
Audit Case ( Applicable to Large / Micro / Investigation )
Assessment Case
Objection Case
179
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
180
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
4.1.4.1.1
Case ID
Automatic assignment:
This is controlled by configuration and the Case ID must be a numeric value.
SAP Cross-Application Components General Application Functions Records
and Case Management Case Define Number Range Intervals for Case
CASE TYPE
NUMBER
RANGE
INTERNAL
EXTERNAL
Audit
Audit Review
Audit
Rectification
Audit
Cancellation
181
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
4.1.4.1.2
Taxpayer ID
There is standard field for Business Partner ID in details view of ICM Case that will
be used to capture Taxpayer ID.
182
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
4.1.4.1.3
Category
To differentiate between business audit, Issue based audit & refund audit// Audit
& Investigation case.
Customizing Implementation Guide ->Customer Relationship Management
->CRM Cross-Application Components ->Multilevel Categorization ->Define
Application Areas for Categorization.
183
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
4.1.4.1.4
Case Priority
Pre-defined priorities will configure according to MIRA investigation process that
are useful for workload distribution and case searching.
184
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
CASE TYPE
Audit
Audit
Audit
PRIORITY
High
Medium
Low
185
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
4.1.5
Status Management
System Status Locked: Documents with such a status are visible to its author
only
System Status Restricted: With this status, a document's file cannot be
changed anymore. Only the document's attributes can be changed
Released:
The result of authorization type check DOM Standard is that documents with
status IPR Private are only visible to ist creator. Is this authorization type check
not assigned to the RMS_ID documents in status IPR Private will be visible to all
users.
186
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
187
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
188
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
189
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
190
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
4.1.6
Partner Determation Procedure / Partner
Function
SL NO
1
2
CASE TYPE
ZAUD
ZASS
PDP
ZAUDPDP01 (TBD AS PER MIRA)
ZAUDPDP02(TBD AS PER MIRA)
DESCRIPTION
Employee
Employee responsible
Group
Organization
Commissioner General
Commissioner General
191
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
4.1.7
Activities
Activities in ICM have a specific UI which is different from the CRM Activity. The
most obvious difference is the assignment blocks presenting the relationships to
other entities. Incidents have relationships to
1.
2.
3.
4.
5.
6.
7.
8.
Raid Plan
Summons
Outbound Email
Outbound calls
Appointments
Other activities
Incidents
Activity
An Incident is used to put down information about any event which has to be
tracked later for reasons of auditing, e.g. that Audit officer has stopped and
questioned somebody in a routine operation. It has relations to all involved
parties, objects and locations. Furthermore, it can be related to Cases/Leads
when it plays a role within these.
An Activity is a task, appointment or operation in auditing like alike a report,
doing an interview with a suspect or witness, or executing a house search or
observation. An Activity can also have relations to all involved parties, objects
and locations. Furthermore, it can be related to Cases/Leads when it plays a role
within these.
An Activity in ICM is a CRM Activity of particular transaction types. These
transaction types are customizable but must refer to categories of a fixed class.
Activities in ICM have a specific UI which is different from the CRM Activity. The
most obvious difference is the assignment blocks presenting the relationships to
other entities. Incidents have relationships to
Other activities
Incidents
Cases
Leads
Persons and organizations
Objects and locations
192
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
Z002
Z003
Z004
ACTIVITY NAME
Hearing
Final Hearing
Reminder
Error Report
ASSIGNMENT BLOCK
Hearing
Hearing
Email or Action
Email or Action
193
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
Activities have a new assignment block for E-Mails which can be used to create
and send new e-mails as well as relate existing ones.
Vice versa, on the e-mail OVP there is the known assignment blocks for Activities
to display and maintain the relationships of a specific e-mail.
194
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
4.1.7.2 Worklist
Investigation/Audit/Investigating Officer assigned to Activities as employee
responsible can see them in his Worklist.
195
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
4.1.8
Object
196
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
4.1.8.1.1
Object Families: The object family is mandatory and selected by a user during object creation and
cannot be edited once it has been saved. The object family (for example
Voucher) shortens the options of the value for the field Main Category when you
create an object. For example, select the object family voucher, the system will
only display categories with that object family. The attributes displayed for an
object are dependent on categories. This means that objects with different
categories can have different attributes (fields) on the UI
SAP Customer Relationship Industry-Specific Solutions Investigative Case
Management Object
Create the object families listed in the table below:
OBJECT FAMILY
ZF01
ZF02
ZF03
DESCRIPTION
Vouchers / invoices
3rd Party Documents
Miscellaneous
PRODUCT TYPE
Material
Material
Material
DESCRIPTION
Evidence related directly to case & Taxpayer
Evidence related indirectly to case & Taxpayer
Inference
Statement of Confession
Statement of Information
Legal evidence
197
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
4.1.9
Location
198
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
for
Locations,
Persons
and
Maintain a regional structure (enter values for postal codes, cities, streets).
These values are used as input help, when the Investigation/Audit/Investigating
Officer enters an address for locations, persons and organizations on the UI.
199
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
POSTAL CODE
1234
USAGE
Dely post. Code
200
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
4.1.9.3 Cities
SAP NetWeaver Application Server Basis Services Address Management
Regional Structure/City File Cities Create Cities Individually
Enter the data want to have available, for example city of Male and Addoo.
Having done so, Investigation/Audit/Investigating Officer has to assign one of the
postal codes. Select F7 Postal Codes and enter the postal code.
201
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
4.1.9.4 Streets
SAP NetWeaver Application Server Basis Services Address Management
Regional Structure/City File Streets Create Streets Individually
On the selection screen, select the street created above and enter the values
you want to have available, for example Street name, Orchid Magu. (22) and
susun magu. (15).
202
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
203
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
204
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
CATEGORY
3
31
32
33
4
41
42
205
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
Object
Object
Object
Object
Object
Object
Object
Object
Object
Object
43
431
432
433
434
435
44
45
451
452
206
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
207
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
4.1.9.8.1
Partner Determination Procedure for Objects and Locations
In the assignment block Category Data after selecting a category assign
Partner Determination Procedure ICM Object to all categories that have an
object family assigned.
To do so, need to log on to the CRM WebClient UI.
CRM WEB UI Object/Location Hierarchies
Select the hierarchy and select the category and go to the assignment block
Category Data to assign the partner determination procedure ICM Object.
HIERARC
HY
STRUCTU
RE
3
41
42
43
CATEGORY
PRODUCT
TYPE
OBJECT
FAMILY
PARTNER
DE
Locations
Vouchers
3rd party
documents
Miscellaneous
Material
Material
Material
Location
Vouchers
3rd party
documents
Miscellane
ous
ICM Object
ICM Object
ICM Object
Material
ICM Object
208
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
4.1.9.9 Relationship
Relationships are used to link entities, such as a person to a case or an object to
a location. SAP has configured several relationship types and appropriate entity
links.
MIRA can use this object to do the following:
Provide an overview of associations among people, organizations, objects,
locations, incidents, activities, leads, or cases
Document assumptions or facts that arise as a result of investigation as
they pertain to each of the related entities.
SAP Customer Relationship Industry-Specific Solutions Investigative Case
Management General Setting Relationship.
RELATIONSHIP
TYPE
Z001
Z002
Z003
Z004
DESCRIPTION
Has an unspecified
Taxpayer
REVERSE
DESCRIPTION
SECURITY
LEVEL
Non-classified
Non-classified
Non-classified
Non-classified
209
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
MMIE TYPE
KEYWORD
FILE NAME
210
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
4.1.9.10.1
Record Creation Profile which assigns a Record Model to a Case Type. Case Types
which are not assigned to a Record Creation Profile do not have an Investigation
Record at all.
211
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
4.1.9.10.2
Set Record attributes automatically when saving a case for the first time
ICM Standard BAdI has only one method SET_PROPERTIES_CRM2RM which
maps CRM attributes to RM attributes. It is called when saving a case the first
time and can be used to set records attributes automatically. The default
implementation sets the reference number of the record as <case type> : <case
ID>.
Define Reaction to change of status
SAP CRM System documents the current process status of an interaction record
by using status management. The status has combination of individual user &
system statuses.
Status profile which is used to define the status network and is later on assigned
to an element type.
Initial status of a document is defined in the status profile.
SAP provides the new status profile CRM_ICM2 with initial status IPR Private.
Status profile CRM_ICM2 is assigned to element type document
CRM_ICM2_SPS_DOCUMENT_STATUS.
212
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
4.1.9.11 Email
The e-mail function in SAP CRM incorporates the creation and sending of e-mails
and assignment of e-mails to business objects such as accounts, incidents &
Cases and integration with Microsoft Outlook Exchange using server based
Groupware integration. Exchange business partner (contact) data and activities
(appointments and tasks) between the SAP CRM server and a groupware server.
Microsoft Exchange is supported as groupware servers. CRM middleware
provides a groupware adapter that facilitates seamless communication between
servers. The groupware adapter transforms data to the Internet standards for
groupware
objects: vCard for
contacts
and iCalendar for
tasks
and
appointments.
TRANSACTION TYPE
Incoming Transaction
Outgoing Transaction
DESCRIPTION
MIRA Incoming e-mail Transaction
MIRA Outgoing e-mail Transaction
213
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
4.1.9.11.1
214
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
DESCRIPTION
Reminder Mail
Acknowledge Mail
215
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
TEXT PROFILE
ZICM01(To be mapped per MIRA and
updated)
ZICM01(To be mapped per MIRA and
updated)
216
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
PARTNER NAME
Employee
Responsible
Superior Authority
DESCRIPTION
Audit Officer
Refund Officer
Refund Officer
Org Model
217
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
DESCRIPTION
Visit at Taxpayer Place of
Business
Hearing at MIRA Office
Final Hearing at MIRA
Office
SYSTEM
SAP CRM - Task Transaction Type
SAP CRM - Task Transaction Type
SAP CRM - Task Transaction Type
MIRA DESCRIPTION
Appointment
Task
Task
Business Activity
Visit
SAP CRM has standard transaction type for appointment i.e. 000, copy same into
ZVST for appointment creation in audit process.
Hearing & Final Hearing
SAP CRM has standard transaction type for task i.e. 001; copy same into
ZMIRAHE for task creation in audit process.
SAP Customer Relationship Transaction Basic Setting Define Transaction
Type.
218
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
INFORMATION DETAILS
Taxpayer Basic Information
Taxpayer Ledger
Taxpayer Return Details
Taxpayer Payment History
Taxpayer Audit & Investigation
History
Consolidated Returns
Recovery Status
DESCRIPTION
Taxpayer Information
Ledger Information of Taxpayer
Complete Return Details
Payment Details of History
Audit History of Taxpayer
Return details on Dynamic Date
Recovery history
Taxpayer Overview
From Taxpayer overview work centre, audit officer will access below three
functionalities Taxpayer Overview
Audit officer can view the most current information on any Taxpayer at any time
like Taxpayer obligations
& payments, ledger account balance and line items for each revenue & tax type.
Consolidated Return
Investigation/Audit/Investigating officer will be able to access consolidated
information of returns filled by Taxpayer over particular period of time by
219
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
220
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
4.1.10
Records Management
221
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
Document
Document Template
Record Model
Record
222
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
223
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
4.1.11
ICM no specific or new authorization objects are delivered with EhP1. All needed
authorization objects are CRM / RM standard authorization objects. The objects
listed on this slide are those needed for a WebUI User and come with
authorization Role SAP_CRM_UIU_ICM_PROFESSIONAL. Users working in the SAP
GUI need additional authorizations.
How these authorization objects should be maintained depends on the actions a
user is allowed to fulfill. This can differ from customer to customer. SAP does not
deliver any default values for these authorization objects coming with role
SAP_CRM_UIU_ICM_PROFESSIONAL.
These are the authorization objects needed for ICM Records Management
Functionality:
PS_RMPSOEH
PS_RMPSORG
PS_RMPSPGE
PS_RMPSPSP
S_SRMGS_CT
S_SRMGS_DC
S_SRMGS_PR
S_SRMGS_VV
S_SRMRECST
S_SRMSY_CL
S_SRM_STAT
S_SRM_ST_P
S_FRA_AREA
224
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
4.2
Core Enhancement
Once the 2nd dunning notice is issued to the taxpayer SAP ICM will
create an automatic lead for the relevant tax type.
Once save the case, action email will triggered to all partner functions
about case details as a hyper link of case number.
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
Activity log based on Employee and respective their cases issue log /
activity log .
226
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
4.3
Interfaces
SAP CRM System will speak to three other systems .i.e., so we need to integrate
SAP CRM with below systems.
1. SAP TRM
2. SAP BI/BO
3. SAP CRM Integration with DMS
SAP TRM is a component of ECC, so we can integrate it with SAP CRM via
standard Middleware.
SAP BI/BO is individual product of SAP for reporting & analytic purpose, SAP CRM
have BI Adapter in itself in middleware component. So we can integrate it with
SAP CRM with Standard Middleware.
NON SAP systems (NEXUS / POLICE / CUSTOMS / ARREARS) are integrated with
CRM through RFC Functional Module, their Master data will be display as POP-UP
in CRM system with parameters.
MIRA mainly integrated with CUSTOMS for their case investigations.
227
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
4.4
Reports
228
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
4.5
Workflow
Creation & Auto allocation of audit /Audit & Investigation cases to audit
officer.
229
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
4.6
NA
230
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
Open Points
a
b
All the reports to be generated from the work done in this module will
be covered in the BI BO.
The logic on the basis of which any Case allocation (Trigger for creation
of a case of Audit & Audit & Investigation) will happen is to be
elaborated by the audit and investigation team.
Formats of SMS, Emails, error messages and mapping of forms of
notices with those of orders will be freeze at the time of Functional
Specification Stage.
231
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
Annexures
NA
232
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE
Glossary
Term
Explanation
BDOCS
Business Documents
BP
Business Partner
CRM
CG
DCG
DMS
ERP
ERMS
SLA
SSC
SSO
Single Sign On
TRM
233
TW <<BPD-04>>
Project Specific
Page # 1 to 8990
For Use by MIRA & TECHWAVE