Business Requirement Name: Restriction on cash receive an amount of Rs 2 Lakh or

more in SAP system in respect to Section 269ST of the Income Tax Act
Team: Billing Customer Service SD
Device Management Finance MM
Status:
Last Updated: 28-02-2017 03.04.2017

Sign-off
Please sign and Date. Name Signature Date

Author Gitank Sharma 03-04-2017

Development Team Akhil Garg

Lead:

Process Owner: Mr Surendra

Kumar Das
Checklist
Business Requirement Description
 Are the Business Considerations and “To-Be” event descriptions complete?
 Are the descriptions clearly written? (Free of jargon, logically organized etc.)

Business Process Flow

 Have standard symbols been used?
 Do the flows reference appropriate manual and system points?
 Are the flows at an appropriate level of detail?

Other
 Have all interface and reporting points been identified?
 Have all development items been identified and documented?
 Have differences between current and To-Be processes documented?
 Have all issues been logged in the issues log? Cross Referenced in this document? Attached to
this document? (functional, technical, conversion, development, change management)
 Have all the gaps been documented?
 Has the business process been verified with the business model, RFFP and the proposal?
 Have all high-level conversion considerations been documented?
 Has the application architecture been updated to reflect interfaces?
 Have all referenced items been noted and attached where appropriate? (Spreadsheets,
Functional information papers, etc.)
 Have all exceptions and process variations/ scenarios been documented?
Amendment Record
Revision Date Author Change Summary
0.1 28-02-2017 Gitank Sharma Initial draft
0.2 03-04-2017 Gitank Sharma
Business Requirement Summary
Please list the Sub-Process and Process for which this event is associated. Also provide a few sentences
defining the basic functions supported by this business event.
Process: 1 : Restriction on cash receive an amount of Rs 2 Lakh or
more in SAP system in respect to Section 269ST of the
Income Tax Act
Requirement S. No. Activity
Description: 1. According to Section 269ST of the Income-
tax Act, i.e., no person shall receive an
amount of Rs 2 lakh or more ----

(a) in aggregate from a person in a day;

(b) in respect of a single transaction; or
(c) in respect of transactions relating to one
event or occasion from a person.

otherwise than by an account payee cheque

or account payee bank draft or use of
electronic clearing system through a bank
account.

Applicable from 1st April, 2017.

In SAP system necessary provision needs to

be made to prohibit receiving of cash
transactions of 2 lakh or more :-
a) in aggregate from a consumer in a
day either against single invoice or
multiple invoice.
b) In aggregate in multiple days against
single invoice.

Necessary development must be completed

and implemented before 31st March,2017.

As dicussed with finance team , we will be saving

uncleared invoices with amount equal to Rs 2 Lakh or
above in a Z table . At the time of receiving cash
payment through FPCJ ,if an entry for the BP exists in
the Z Table , the system will give an error message or
warning message depending on the cash desk used.

If cash desk is “04”for Mr Rajkumar Srivastava a

warning message will be displayed – “Payment from
the customer in cash exceeds permitted limit” . Mr
Rajkumar would have to manually check the status of
the invoice in FPL9 in order to process the transaction
or cancel it

If cash desk is other than “04”an error message would

be displayed “Payment from the customer in cash
exceeds permitted limit. Please contact Head
 Cashier”

As and when the invoices get cleared they will be

automatically removed from the Z table

Process Variations
Process Variations
Please provide information of known variations to the standard business process. Specify the variation
description, e.g. the standard process may branch out to two different sub-processes depending on the
satisfaction of a criterion. Ensure that there is a cross reference to the to-be process step(s).
No. Variation Description Ref. To-be
Step(s) Remarks

TO-BE: Development Items

Record development objects. Specify their type (I = Interface, R = Report, E = Enhancement, C = CIC
Integration, W = Workflow) and priority (1 = Mandatory, 2 = Workaround required if not implemented, 3 =
Optional) required. Also cross-reference the number of each task to the number of step in the process flow
diagram.
No. Type Description Priority Ref. To-be
Step(s)
1 I 1 1

2 E 1 1

TO-BE: Conversion /Data Considerations

Document conversion considerations corresponding to the business process. Specify the priority (M =
Mandatory, O = Optional) required.
No. Description Priority
N/A

TO-BE: Identified Business Impacts

Document identified impacts to the business. Specify impact category (OG = Organization, OP = Operation,
CU = Customer, JO = Job, OT = others) the level of impact (H = High, M = Medium, L = Low)
No. Description Impact Category Impact Level

Assumptions
No. Description
Additional Documents Referenced
Enter the location for all other documents, which are referenced here. Enter the full path of the file. Enter a
brief one line description about what the document contains. (e.g. Business Blueprint, Process Flows,
Development Inventory, etc.)