Company X

Risk Control Matrix - Project for Lines

Completeness
Process Sub-process Risk Description Control Control Description

Valuation and Allocation

Anti-Fraud Operational/ Test Type: Testing Steps: Walkthrough Testing Key/ Control Preparer: Reviewer: Preventive / Automated / Source Information Management IPE Activities

Existence or Occurrence

Rights and Obligation

Presentation and Disclosure

Reference (Yes/No) Financial (Inquiry/ Period: Period: Non-Key Frequency: Detective Manual System Provide by
Inspection/ Entity (IPE)
Observation/ (Yes/No)
Re-performance)

Fixed Assets & Project for Survey report may not be On the basis of new customer application, a a No Financial Inquiry and 1) Perform an inquiry with Name, DGM, Commercial on 16/03/2016 to gain an understanding of the process. date date Key As needed Field Engineer Sr. Divisional Preventive Manual Manual Yes The Management currently relies on the ITGC
Project Lines approved Business Development Team requests the Inspection Engineer procedures for the accuracy and completeness of
Engineering Team to conduct a survey. Post 2) Obtain the list of survey conducted during FY 2016-17 the controls
conducting a survey a report is submitted to
Sr. Divisional engineer approves the survey 3) Randomly select a sample
report
4) Obtain the copy of mail sent by engineering Department to commercial Department

5) Verify whether the mail sent contains the details of the materials required for the project
Test of Design Test of Operating Effectiveness
Walkthrough Details: Test of Design Issue Recommendation Test of O/E Issue Recommendation
Conclusion Summary Conclusion Summary

1) Inquired with Name, DGM, Commercial and gained an understanding of the process. Pass NA NA Pass NA NA

2) Obtained the list of survey conducted during FY 2016-17

3) Randomly selected a sample

4) Obtained the copy of mail sent by engineering Department to commercial Department

5) Verified that mail sent contains the details of the materials required for the project
Design Effectiveness Testing Procedures
Location: Plant
Process: Fixed Assets & Project
Control Reference: 0
Control Owner: Name

Tester:
Reviewer:

Risk Description Survey report may not be approved

On the basis of new customer application, Business Development Team requests the Engineering Team to
Control Description: conduct a survey. Post conducting a survey a report is submitted to Sr. Divisional engineer approves the
survey report

Key/Non-Key Key
Control Frequency: As needed
Automated / Manual Manual
Preventive / Detective Preventive
Preparer Field Engineer
Reviewer Sr. Divisional Engineer
As per the sampling methodology, we have considered one sample for testing the design of the above
Sampling Approach: mentioned control

If IPE, document the testing procedures below:

IPE Type (i.e., canned report, IT customized report, query
report, spreadsheet)?
If IPE is relied upon, reference the corresponding report or
spreadsheet testing.
If IPE is validated, discuss the procedures performed in this
control to validate the completeness and accuracy of data
inputs, data processing, and data outputs.
System generated report
1) Noted that list of survey conducted during FY 2015-16 was generated using T-code ''ZCUST_DETAILS' from
the SAP. The parameters used to pull the report are as follow.
Generated the 'consumer master' by executing.
Since it is generic SAP report, the logic of the report need not be tested.

1) Inquired with Name, DGM, Commercial and gained an understanding of the process.
2) Obtained the list of survey conducted during FY 2016-17

Walkthrough Details 3) Randomly selected a sample

4) Obtained the copy of mail sent by engineering Department to commercial Department

5) Verified that mail sent contains the details of the materials required for the project

Conclusion: Pass

Testing Attribute A: Evidence of approval of survey report by Sr. divisional Manager

Attribute

Sample Approver A Exceptions Noted? Notes Work paper Reference

Population and mail

contained material Shekhar Pal Y NA NA PFL 1.1 & 1.2
required for the
project

Work papers References:

PFL 1.1 Approval of servey report
PFL 1.2 Population of survey conducted

Legend:
Y Control attribute achieved (pass)
X Control attribute not achieved (exception)
N1, N2, N3…. Testing Note
N/A Not Applicable
Operating Effectiveness Testing Procedures
Location: Plant
Process: Fixed Assets & Project
Control Reference: 0
Control Owner: Name

Tester:
Reviewer:

Risk Description Survey report may not be approved

On the basis of new customer application, Business Development Team requests the Engineering Team to
Control Description: conduct a survey. Post conducting a survey a report is submitted to Sr. Divisional engineer approves the
survey report

Key/Non-Key Key
Control Frequency: As needed
Automated / Manual Manual
Preventive / Detective Preventive
Preparer Field Engineer
Reviewer Sr. Divisional Engineer
As per the sampling methodology, as this control operates on an as needed frequency, hence have made 25
Sampling Approach: sample selections for the test of operating effectiveness of the above mentioned control.

If IPE, document the testing procedures below:

IPE Type (i.e., canned report, IT customized report, query report, System generated report
spreadsheet)?

If IPE is relied upon, reference the corresponding report or 1) Noted that list of survey conducted during FY 2015-16 was generated using T-code ''ZCUST_DETAILS' from
spreadsheet testing. the SAP. The parameters used to pull the report are as follow.
If IPE is validated, discuss the procedures performed in this control to Generated the 'consumer master' by executing.
validate the completeness and accuracy of data inputs, data Since it is generic SAP report, the logic of the report need not be tested.
processing, and data outputs.

1) Inquired with Name, DGM, Commercial and gained an understanding of the process.

Testing Details 2) Randomly selected 25 sample

3) Verified that there is survey report is reviewed by the Sr Divisional Engineer

Conclusion: Pass

Testing Attribute A: Evidence of approval of survey report by Sr. divisional Manager

Attribute

Sample Approver A Exceptions Noted? Notes Work paper Reference

Population and mail

contained material required Y NA NA PFL 1.3 & 1.4
for the project

Population and mail

contained material required Y NA NA PFL 1.3 & 1.4
for the project

Population and mail

contained material required Y NA NA PFL 1.3 & 1.4
for the project

Population and mail

contained material required Y NA NA PFL 1.3 & 1.4
for the project

Population and mail

contained material required Y NA NA PFL 1.3 & 1.4
for the project

Population and mail

contained material required Y NA NA PFL 1.3 & 1.4
for the project

Population and mail

contained material required Y NA NA PFL 1.3 & 1.4
for the project

Population and mail

contained material required Y NA NA PFL 1.3 & 1.4
for the project

Population and mail

contained material required Y NA NA PFL 1.3 & 1.4
for the project

Population and mail

contained material required Y NA NA PFL 1.3 & 1.4
for the project

Population and mail

contained material required Y NA NA PFL 1.3 & 1.4
for the project

Population and mail

contained material required Y NA NA PFL 1.3 & 1.4
for the project

Population and mail

contained material required Y NA NA PFL 1.3 & 1.4
for the project

Population and mail

contained material required Y NA NA PFL 1.3 & 1.4
for the project

Population and mail

contained material required Y NA NA PFL 1.3 & 1.4
for the project

Population and mail

contained material required Y NA NA PFL 1.3 & 1.4
for the project

Population and mail

contained material required Y NA NA PFL 1.3 & 1.4
for the project

Population and mail

contained material required Y NA NA PFL 1.3 & 1.4
for the project

Population and mail

contained material required Y NA NA PFL 1.3 & 1.4
for the project

Population and mail

contained material required Y NA NA PFL 1.3 & 1.4
for the project

Population and mail

contained material required Y NA NA PFL 1.3 & 1.4
for the project

Population and mail

contained material required Y NA NA PFL 1.3 & 1.4
for the project

Population and mail

contained material required Y NA NA PFL 1.3 & 1.4
for the project

Population and mail

contained material required Y NA NA PFL 1.3 & 1.4
for the project

Population and mail

contained material required Y NA NA PFL 1.3 & 1.4
for the project

Population and mail

contained material required Y NA NA PFL 1.3 & 1.4
for the project

Work papers References:

PFL 1.3 Approval of servey report
PFL 1.4 Population of survey conducted

Legend:
Y Control attribute achieved (pass)
X Control attribute not achieved (exception)
N1, N2, N3…. Testing Note
N/A Not Applicable
Design Effectiveness Testing Procedures
Location: Plant
Process: Fixed Assets & Project
Control Reference: 0
Control Owner: Name

Tester:
Reviewer:

Risk Description Possibility of misses in updating the critical deta

Project created in SAP may not be approved by
Control Description: The new projects created in SAP is reviewed an

Key/Non-Key Key
Control Frequency: As needed
Automated / Manual Manual
Preventive / Detective Preventive
Preparer Business Development Team (BD Team)
Reviewer As per Approval Matrix

As per the sampling methodology, we have cons

Sampling Approach: mentioned control

If IPE, document the testing procedures below:

IPE Type (i.e., canned report, IT customized report, query
System generated report
report, spreadsheet)?

1) Noted that list of list of new project created in

the SAP. The parameters used to pull the report
If IPE is relied upon, reference the corresponding report or Plant code
spreadsheet testing.
If IPE is validated, discuss the procedures performed in this Document No.
Generated the 'all the documents from docume
control to validate the completeness and accuracy of data Since it is generic SAP report, the logic of the rep
inputs, data processing, and data outputs.
Refer PFL 2.1
 1) Inquired with Name, DGM, Commercial and g

2) Obtained the list of new project created in SA

Walkthrough Details 3) Randomly selected a sample

4) Obtain the screen shot of the approvals made

5) Verified that the approval is as per approval m

Conclusion: Pass

Testing Attribute A: Evidence of approval by the authorized matrix fo

Attribute
Sample Approver A
As per
Screen shot of approval Y
approval made
matrix

Work papers References:

PFL 2.1 Population of new project created
PFL 2.2 Screenshort of approval made for a project

Legend:
Y Control attribute achieved (pass)
X Control attribute not achieved (exception)
N1, N2, N3…. Testing Note
N/A Not Applicable
roject

ses in updating the critical details of the project in SAP

n SAP may not be approved by authorized approver
ts created in SAP is reviewed and approved by the authorized approver

pment Team (BD Team)

Matrix

ling methodology, we have considered one sample for testing the design of the above
rol

ed report

t of list of new project created in SAP was generated using T-code ''ZBUDGET_DISPLAY' from
ameters used to pull the report are as follows

all the documents from document no.

c SAP report, the logic of the report need not be tested.
Name, DGM, Commercial and gained an understanding of the process.

list of new project created in SAP during FY 2016-17

ected a sample

een shot of the approvals made by approving authority

he approval is as per approval matrix

roval by the authorized matrix for the projects created in SAP

Exceptions Noted? Notes Work paper Reference

NA NA PFL 2.1 & PFL 2.2

ew project created
pproval made for a project
Operating Effectiveness Testing Procedures
Location: Plant
Process: Fixed Assets & Project
Control Reference: 0
Control Owner: Name

Tester:
Reviewer:

Risk Description Possibility of misses in updating the critical details o

Project created in SAP may not be approved by aut

Control Description: The new projects created in SAP is reviewed and a

Key/Non-Key Key
Control Frequency: As needed
Automated / Manual
Preventive / Detective
Preparer Business Development Team (BD Team)
Reviewer As per Approval Matrix
As per the sampling methodology, as this control o
sample selections for the test of operating effectiv
Sampling Approach:

If IPE, document the testing procedures below:

IPE Type (i.e., canned report, IT customized report, query System generated report
report, spreadsheet)?
If IPE is relied upon, reference the corresponding report or 1) Noted that list of list of new project created in SA
the SAP. The parameters used to pull the report are
spreadsheet testing. Plant code
If IPE is validated, discuss the procedures performed in this
control to validate the completeness and accuracy of data Document No.
Generated the 'all the documents from document n
inputs, data processing, and data outputs. Since it is generic SAP report, the logic of the repor

1) Inquired with Name, DGM, Commercial and gain

2) Randomly selected 15 samples

Testing Details
3) Obtain the screen shot of the approvals made by

4) Verified that the approval is as per approval mat

Conclusion: Pass

Testing Attribute A: Evidence of approval by the authorized matrix for t

Attribute
Document No. Approver A Exceptions Noted?
As per
Screen shot of
approval made approval Y NA
matrix

Screen shot of As per

approval Y NA
approval made matrix

Screen shot of As per

approval Y NA
approval made matrix

Screen shot of As per

approval made approval Y NA
matrix
 As per
Screen shot of approval Y NA
approval made
matrix
As per
Screen shot of
approval Y NA
approval made matrix
As per
Screen shot of
approval Y NA
approval made matrix
As per
Screen shot of approval Y NA
approval made
matrix
As per
Screen shot of approval Y NA
approval made
matrix
As per
Screen shot of approval Y NA
approval made matrix
As per
Screen shot of
approval Y NA
approval made matrix
As per
Screen shot of approval Y NA
approval made
matrix
As per
Screen shot of approval Y NA
approval made
matrix
As per
Screen shot of approval Y NA
approval made matrix

Screen shot of As per

approval Y NA
approval made matrix

Work papers References:

PFL 2.3 Population of new project created
PFL 2.4 Screenshot of approval made for a project

Legend:
Y Control attribute achieved (pass)
X Control attribute not achieved (exception)
N1, N2, N3…. Testing Note
N/A Not Applicable
& Project

misses in updating the critical details of the project in SAP

ed in SAP may not be approved by authorized approver

jects created in SAP is reviewed and approved by the authorized approver

elopment Team (BD Team)

val Matrix
mpling methodology, as this control operates on an as needed frequency, hence have made 15
tions for the test of operating effectiveness of the above mentioned control.

ated report
 list of list of new project created in SAP was generated using T-code ''ZBUDGET_DISPLAY' from
parameters used to pull the report are as follows

o.
e 'all the documents from document no.
eric SAP report, the logic of the report need not be tested

ith Name, DGM, Commercial and gained an understanding of the process.

selected 15 samples
screen shot of the approvals made by approving authority

at the approval is as per approval matrix

pproval by the authorized matrix for the projects created in SAP

Notes Work paper Reference

NA PFL 2.3 & 2.4

NA PFL 2.3 & 2.4

NA PFL 2.3 & 2.4

NA PFL 2.3 & 2.4

 NA PFL 2.3 & 2.4

NA PFL 2.3 & 2.4

NA PFL 2.3 & 2.4

NA PFL 2.3 & 2.4

NA PFL 2.3 & 2.4

NA PFL 2.3 & 2.4

NA PFL 2.3 & 2.4

NA PFL 2.3 & 2.4

NA PFL 2.3 & 2.4

NA PFL 2.3 & 2.4

NA PFL 2.3 & 2.4

f new project created

f approval made for a project
Design Effectiveness Testing Procedures
Location:
Process:
Control Reference:
Control Owner:

Tester:
Reviewer:

Risk Description

Control Description:

Key/Non-Key
Control Frequency:
Automated / Manual
Preventive / Detective
Preparer
Reviewer

Sampling Approach:

If IPE, document the testing procedures below:

IPE Type (i.e., canned report, IT customized report, query report, spreadsheet)?

If IPE is relied upon, reference the corresponding report or spreadsheet testing.

If IPE is validated, discuss the procedures performed in this control to validate the
completeness and accuracy of data inputs, data processing, and data outputs.
Walkthrough Details

Conclusion:

Testing Attribute A:

Attribute
Sample Approver A

Offer Letter given to

consumer & cost DGM, (Commercial and Billing) Y
approved in SAP

Work papers References:

PFL 3.1
PFL 3.2

Legend:
Y Control attribute achieved (pass)
X Control attribute not achieved (exception)
N1, N2, N3…. Testing Note
N/A Not Applicable
Plant
Fixed Assets & Project
0
Name

The final quotation amount in offer letter may not tie out with the cost approved in SAP
VP, Technical/DGM, Commercial & Billing/AGM, Technical reviews and signs off the offer letter before
sending it to the consumer

Key
As needed
Manual
Preventive
BD Team
VP, Technical/DGM, Commercial & Billing/AGM, Technical
As per the sampling methodology, we have considered one sample for testing the design of the above
mentioned control

System generated report

1) Noted that list of offer letter given to consumer during FY 2015-16 was generated using T-code
''ZCUST_DETAILS' from the SAP. The parameters used to pull the report are as follow.
Generated the 'consumer master' by executing.
Since it is generic SAP report, the logic of the report need not be tested.
 1) Inquired with Name, DGM, Commercial and gained an understanding of the process.
2) Obtained the list of offer letter given to consumer during FY 2016-17

3) Randomly selected a sample

4) Obtained the copy of offer letter given to prospective consumer

5) Obtained the screen shot of cost approved in SAP

6) Verified that the offer letter is signed by DGM, Commercial & Billing

Pass

Evidence of offer letter given to consumer is signed by VP, Technical/AGM, Technical/DGM, Commercial &
Billing

Exceptions Noted? Notes Work paper Reference

NA NA PFL 3.1 & 3.2

Screen shot of approval made for a project

Offer letter given to consumer

e achieved (pass)
e not achieved (exception)
 e cost approved in SAP
ws and signs off the offer letter before

ple for testing the design of the above

5-16 was generated using T-code

report are as follow.

tested.
anding of the process.
016-17

er

Billing

ical/AGM, Technical/DGM, Commercial &

Operating Effectiveness Testing Procedures
Location: Plant
Process: Fixed Assets & Project
Control Reference: 0
Control Owner: Name

Tester:
Reviewer:

Risk Description The final quotation amount in offer letter may n

Control Description: VP, Technical/DGM, Commercial & Billing/AGM,

sending it to the consumer

Key/Non-Key Key
Control Frequency: As needed
Automated / Manual Manual
Preventive / Detective Preventive
Preparer BD Team
Reviewer VP, Technical/DGM, Commercial & Billing/AGM,
As per the sampling methodology, as this contro
Sampling Approach: sample selections for the test of operating effec

If IPE, document the testing procedures below:

IPE Type (i.e., canned report, IT customized report, query

System generated report
report, spreadsheet)?

1) Noted that list of offer letter given to consum

If IPE is relied upon, reference the corresponding report or
spreadsheet testing. ''ZCUST_DETAILS' from the SAP. The parameter
Generated the 'consumer master' by executing.
If IPE is validated, discuss the procedures performed in this Since it is generic SAP report, the logic of the rep
control to validate the completeness and accuracy of data
inputs, data processing, and data outputs.
 1) Inquired with Name, DGM, Commercial and g

2) Randomly selected 15 sample

Testing Details 3) Obtained the copy of offer letter given to pro

4) Obtained the screen shot of cost approved in

5) Verified that the offer letters is signed by VP,

Conclusion: Pass

Evidence of offer letter given to consumer is sign

Testing Attribute A: Billing

Attribute

Sample Approver A Exceptions Noted?

Offer Letter given to DGM,

consumer & cost (Commercial Y NA
approved in SAP and Billing)

Offer Letter given to

consumer & cost VP, Technical Y NA
approved in SAP

Offer Letter given to

consumer & cost VP, Technical Y NA
approved in SAP

Offer Letter given to

consumer & cost VP, Technical Y NA
approved in SAP

Offer Letter given to

consumer & cost VP, Technical Y NA
approved in SAP
Offer Letter given to
consumer & cost VP, Technical Y NA
approved in SAP

Offer Letter given to

consumer & cost VP, Technical Y NA
approved in SAP

Offer Letter given to

consumer & cost VP, Technical Y NA
approved in SAP

Offer Letter given to

consumer & cost VP, Technical Y NA
approved in SAP

Offer Letter given to

consumer & cost VP, Technical Y NA
approved in SAP

Offer Letter given to

consumer & cost VP, Technical Y NA
approved in SAP

Offer Letter given to

consumer & cost VP, Technical Y NA
approved in SAP

Offer Letter given to

consumer & cost VP, Technical Y NA
approved in SAP

Offer Letter given to

consumer & cost VP, Technical Y NA
approved in SAP

Offer Letter given to DGM,

consumer & cost (Commercial Y NA
approved in SAP and Billing)

Work papers References:

 PFL 3.3 Screen shot of approval made for a project
PFL 3.4 Offer letter given to consumer
PFL 3.5 Population of new project created

Legend:
Y Control attribute achieved (pass)
X Control attribute not achieved (exception)
N1, N2, N3…. Testing Note
N/A Not Applicable
roject

on amount in offer letter may not tie out with the cost approved in SAP
GM, Commercial & Billing/AGM, Technical reviews and signs off the offer letter before
consumer

GM, Commercial & Billing/AGM, Technical

ling methodology, as this control operates on an as needed frequency, hence have made 15
ns for the test of operating effectiveness of the above mentioned control.

ed report

t of offer letter given to consumer during FY 2015-16 was generated using T-code
S' from the SAP. The parameters used to pull the report are as follow.
consumer master' by executing.
c SAP report, the logic of the report need not be tested.
Name, DGM, Commercial and gained an understanding of the process.

ected 15 sample
copy of offer letter given to prospective consumer

screen shot of cost approved in SAP

he offer letters is signed by VP, Technical and DGM, Commercial & Billing

r letter given to consumer is signed by VP, Technical/AGM, Technical/DGM, Commercial &

Notes Work paper Reference

NA PFL 3.3 & 3.4

NA PFL 3.3 & 3.4

NA PFL 3.3 & 3.4

NA PFL 3.3 & 3.4

NA PFL 3.3 & 3.4

NA PFL 3.3 & 3.4

NA PFL 3.3 & 3.4

NA PFL 3.3 & 3.4

NA PFL 3.3 & 3.4

NA PFL 3.3 & 3.4

NA PFL 3.3 & 3.4

NA PFL 3.3 & 3.4

NA PFL 3.3 & 3.4

NA PFL 3.3 & 3.4

NA PFL 3.3 & 3.4

 pproval made for a project
n to consumer
ew project created
Design Effectiveness Testing Procedures
Location: Plant
Process: Fixed Assets & Project
Control Reference: 0
Control Owner: Name

Tester:
Reviewer:

Risk Description The capitalization entry posted may not be com

Control Description: DGM, F&A reviews the capitalization entry poste

Key/Non-Key Key
Control Frequency: As needed
Automated / Manual Manual
Preventive / Detective Preventive
Preparer Accounts Department
Reviewer DGM, F&A
As per the sampling methodology, we have cons
Sampling Approach: mentioned control

If IPE, document the testing procedures below:

IPE Type (i.e., canned report, IT customized report, query

System generated report
report, spreadsheet)?

If IPE is relied upon, reference the corresponding report or
spreadsheet testing.
If IPE is validated, discuss the procedures performed in this
control to validate the completeness and accuracy of data
inputs, data processing, and data outputs.
1) Noted that list of list of new project created in
parameters used to pull the report are as follow
Plant code
Asset No.
Generated list of all assets and filtered to custom
Since it is generic SAP report, the logic of the rep

1) Inquired with Name, DGM, Commercial and g

2) Obtained the list of consumer job capitalised

Walkthrough Details 3) Randomly selected a sample

4) Obtained the screen shot of capitalisation ent

5) Verified that the entry posted in SAP is appro

Conclusion: Pass

Testing Attribute A: Evidence of capitalisation entry made

Testing Attribute B: Evidence of capitalisation entry made is approve

Attribute
Sample Approver A B

Capitalisation entry
made and approval Anil Prasad Y Y
thereof

Work papers References:

PFL 4.1 Capitalisation entry made and approval thereo
PFL 4.2 Population for consumer job capitalised during
PFL 4.3 Parameter used to pull the Report
Legend:
Y Control attribute achieved (pass)
X Control attribute not achieved (exception)
N1, N2, N3…. Testing Note
N/A Not Applicable
roject

n entry posted may not be complete and accurate

ws the capitalization entry posted in SAP

ment

ling methodology, we have considered one sample for testing the design of the above
rol

ed report
t of list of new project created in SAP was generated using T-code 'AR02' from the SAP. The
d to pull the report are as follows

f all assets and filtered to customise the report

c SAP report, the logic of the report need not be tested.

Name, DGM, Commercial and gained an understanding of the process.

list of consumer job capitalised during FY 2016-17

ected a sample

screen shot of capitalisation entry made

he entry posted in SAP is approved by DGM, F&A

talisation entry made

talisation entry made is approved by DGM, F&A

Exceptions Noted? Notes Work paper Reference

NA NA PFL 4.1 & 4.2

ntry made and approval thereof

consumer job capitalised during FY 2016-17
to pull the Report
Operating Effectiveness Testing Procedures
Location: Plant
Process: Fixed Assets & Project
Control Reference: 0
Control Owner: Name

Tester:
Reviewer:

Risk Description The capitalization entry posted may not be com

Control Description: DGM, F&A reviews the capitalization entry poste

Key/Non-Key Key
Control Frequency: As needed
Automated / Manual Manual
Preventive / Detective Preventive
Preparer Accounts Department
Reviewer DGM, F&A
As per the sampling methodology, as this contro
Sampling Approach: sample selections for the test of operating effec

If IPE, document the testing procedures below:

IPE Type (i.e., canned report, IT customized report, query
report, spreadsheet)? System generated report

1) Noted that list of list of new project created in

If IPE is relied upon, reference the corresponding report or
spreadsheet testing.
If IPE is validated, discuss the procedures performed in this
control to validate the completeness and accuracy of data
inputs, data processing, and data outputs.
parameters used to pull the report are as follow
Plant code
Asset No.
Generated list of all assets and filtered to custom
Since it is generic SAP report, the logic of the rep
 1) Inquired with Name, DGM, Commercial and g
2) Randomly selected 3 sample
Testing Details
3) Obtained the copy of capitalization entry mad
4) Verified that the entry posted in SAP is appro

Conclusion: Pass

Testing Attribute A: Evidence of capitalization entry made

Testing Attribute B: Evidence of capitalization entry made is approve

Attribute
Sample
Approver A B
(Voucher)
Y Y
Y Y
Y Y

Work papers References:

PFL 4.4 Capitalisation entry made and approval thereo
PFL 4.5 Population for consumer job capitalised during
PFL 4.6 Parameter used to pull the Report

Legend:
Y Control attribute achieved (pass)
X Control attribute not achieved (exception)
N1, N2, N3…. Testing Note
N/A Not Applicable
roject

n entry posted may not be complete and accurate

ws the capitalization entry posted in SAP

ment

ling methodology, as this control operates on an as needed frequency, hence have made 3
ns for the test of operating effectiveness of the above mentioned control.

ed report

t of list of new project created in SAP was generated using T-code 'AR02' from the SAP. The
d to pull the report are as follows

f all assets and filtered to customize the report

c SAP report, the logic of the report need not be tested.
Name, DGM, Commercial and gained an understanding of the process.
ected 3 sample

copy of capitalization entry made

he entry posted in SAP is approved by DGM, F&A

talization entry made

talization entry made is approved by DGM, F&A

Exceptions Noted? Notes Work paper Reference

NA NA PFL 4.4 to 4.6

NA NA PFL 4.4 to 4.6
NA NA PFL 4.4 to 4.6

ntry made and approval thereof

consumer job capitalised during FY 2016-17
to pull the Report