BUSINESS PROCESS BLUEPRINT FINANCE

Project:

Project:

166531223.doc

8/23/2013

Page 1 of62

Business Blueprint Process signoff document................................................................................3 FI01 General Ledger Accounting................................................................................................4 FI0101 Creation of GL Master Account..................................................................................4 FI02 Basic Setting........................................................................................................................6 FI0201 Fiscal Year and Posting Periods..................................................................................6 FI0202 Document....................................................................................................................9 FI0203 Tax on Sales/Purchases in SAP System....................................................................11 FI0204 Posting Help..............................................................................................................14 FI0205 Withholding Tax........................................................................................................16 FI03 General Ledger Processing................................................................................................18 FI0301 Postings in GL...........................................................................................................18 FI0302 General Ledger Account Analysis.............................................................................21 FI0303 Account Clearing [GL]..............................................................................................24 FI0304 Recurring Entries.......................................................................................................26 FI0305 Closing Operations....................................................................................................28 FI04 Accounts Payable Processing............................................................................................31 FI0401 Vendor Down Payments............................................................................................31 FI0402 Invoices and Credit Memos.......................................................................................33 FI0403 Vendor Account Analysis..........................................................................................35 FI0404 Vendor Payments.......................................................................................................37 FI0405 Bill of Exchange Payable .........................................................................................40 FI0406 Account Clearing [AP]..............................................................................................42 FI0407 Correspondence with Vendors..................................................................................44 FI05 Accounts Receivables Processing.....................................................................................46 FI0501 Customer Down Payments........................................................................................46 FI0502 Invoices & Credit Notes............................................................................................48 FI0503 Account Analysis.......................................................................................................50 FI0504 Customer Payments...................................................................................................53 FI0505 Account Clearing.......................................................................................................56 FI0506 Dunning.....................................................................................................................58 FI0507 Interest Calculations..................................................................................................60

166531223.doc

8/23/2013

Page 2 of62

Business Blueprint Process signoff document

Name Core Team Member 1 Core Team Member 2 Process Owner Consultant (HEROSOFT) Project Manager (HEROSOFT) Project Manager (<CLIENT ABBREVIATION>) DHARMENDER GOEL SUBODH AGGARWAL Sign Date

Version Management This Document is subject to change control. Every change of the document has to undergo change control procedure and has to be registered in the following table Version 1.0 Change Initial document Prepared By DHARMENDER Date

166531223.doc

8/23/2013

Page 3 of62

FI01 General Ledger Accounting

FI0101 Creation of GL Master Account
Module Process Sub Process Sr No 1.1 Financial Accounting General Ledger Accounting Creation of GL Master Account

Topics Requirements & Expectations 1. G/L Account Master creation to be done centrally, other than Customer & Vendor accounts.

Sr No 2.1

Topics Existing Process General Explanation a) Requirement for new GL account is identified by functional users and created by the respective user, in the existing system. b) The new GL account is opened up either as a Balance Sheet or as a Profit & Loss a/c item. c) GL account master is common for both, MIS and Statutory ledger.

2.2 2.3

Explanation of Existing Functions & Events Flow Sheet Not Applicable Special Organizational Considerations Not Applicable Topics Proposed Process General Explanation GL master will be maintained by a single user, which comes under <ROCKMAN CYCLE INDUSTRIES LIMITED >. The account code structure is proposed to be of maximum 6 digits. The need for the new GL account should be intimated to the GL account administrator by SAP mail, giving complete details about the GL account, its nature (Balance sheet or Profit & Loss). Explanation of Proposed Functions & Events Flow Sheet Not Applicable Special Organizational Considerations
Page 4 of62

Sr No 3.1

3.2 3.3
166531223.doc

8/23/2013

 Sr No 4.1 4.2

Authorization for creation of G/L Master should be given to a single user.

Topics Changes Management Issues None Description of Improvements Centralized GL Master Creation Description of Functional Deficits None Approaches for covering Functional Deficit Not Applicable Topics Notes on Further Improvement Not Applicable Topics System configuration considerations Account groups and number ranges to be created based on the nature of account GL Account numbers shall be externally assigned. Field status groups shall be created for controlling transaction processing. Reconciliation accounts shall be identified. Open items accounts shall be identified. Accounts where line items display is required shall be identified. Cost elements for P&L accounts shall be created in controlling module. File conversion considerations (Master data maintenance). GL account master data to be uploaded into SAP using an ABAP program from Excel worksheet. Interface considerations None Reporting considerations None Authorization considerations Single authorized administrator (user) will control and maintain

4.3

4.4

Sr No 5.1

Sr No 6.1

6.2

6.3 6.4 6.5

166531223.doc

8/23/2013

Page 5 of62

GL account master.

FI02 Basic Setting

FI0201 Fiscal Year and Posting Periods
Module Process Sub Process Sr No 1.1 Financial Accounting Basic Setting Fiscal Year and Posting Period

Topics Requirements & Expectations 1 Accounting Year to be maintained for 12 month starting from 1 st April to 31st March each year as per the current system. .

Sr No 2.1

Topics Existing Process General Explanation a) Posting periods are maintained month-wise, Month wise accounts closing are done for MIS purpose. b) In the Financial / Accounting period / year setting is made only once at the time of creation of a Company, once it is fixed the same is continued automatically in the subsequent years. c) Accounts closing at the end of the year i.e. on 31st March is automatically done, this effects the transfer of balances in Income & Expenditure GL accounts to P& L A/c thus arriving at a Profit or Loss. Balances in Assets & Liabilities GL accounts are automatically carried forward to the subsequent year as Opening balances. Explanation of Existing Functions & Events Flow Sheet Not Applicable Special Organizational Considerations Not Applicable

2.2 2.3

166531223.doc

8/23/2013

Page 6 of62

Sr No 3.1

3.2 3.3

Topics Proposed Process General Explanation Periods in SAP are controlled in Financial Accounting & Logistics module. Financial Accounting: The financial accounting period is a calendar month. The Open and closed period will be controlled at a GL Account level. A period in Logistic represents a calendar month. In respect of Logistic module, at any point of time maximum two periods can be kept open. Posting to Inventory related transaction will not be made unless the Logistic Periods are open. Period Opening & Closing should be done by an authorized Person. This is to be defined in the authorization Once the period is closed editing of records is not possible. At the year end Balances in Assets & Liabilities accounts are to be carried forward by running a program. Balance in P&L accounts will automatically become Zero at the year-end. Explanation of Proposed Functions & Events Flow Sheet Not Applicable Special Organizational Considerations Authorization for Opening & Closing periods should be given to a single user. Topics Changes Management Issues Once the Period is closed backdated postings will not be possible. Description of Improvements Backdated Postings is ruled out by which consistency in the information is maintained. Description of Functional Deficits None Approaches for covering Functional Deficit Not Applicable Topics Notes on Further Improvement Not Applicable Topics

Sr No 4.1 4.2

4.3 4.4

Sr No 5.1

Sr No
166531223.doc

8/23/2013

Page 7 of62

6.1

6.2 6.3 6.4 6.5

System configuration considerations Fiscal Year variant & Posting Period Variant should be defined & assigned to the Co. Code File conversion considerations (Master data maintenance). None Interface considerations None Reporting considerations None Authorization considerations Authorization for Opening & Closing periods should be given to a single user.

166531223.doc

8/23/2013

Page 8 of62

FI0202 Document
Module Process Sub Process Sr No 1.1 Financial Accounting Basic Setting Document

Topics Requirements & Expectations 1. It is required that all document types be uniquely defined in SAP. 2. It is desired that voucher numbers should be identified with numeric numbering sequence clearly identifying the Voucher Type, date, Year & Month. Topics Existing Process General Explanation a. RCIL follows document numbering for different voucher types of documents. Different frames are there for different kinds of vouchers i.e. Cash, Bank, Journal & Purchase. By default the system gives next number to every voucher. If two different users save same kind of voucher at the same time, then again the system takes care of numbering. Different numbers are assigned to different vouchers.

Sr No 2.1

2.2 2.3 Special Organizational Considerations: None

Sr No 3.1

Topics Proposed Process General Explanation It is proposed to use the Standard SAP Document types will be used for recording different business transactions. Voucher Numbers will be internally (automatically) assigned by the system. Audit Trail (specific detailed report describing the activity and completion of a process) is maintained in SAP.

166531223.doc

8/23/2013

Page 9 of62

3.2 3.3 Sr No 4.1 4.2

Explanation of Proposed Functions & Events Flow Sheet Not Applicable Special Organizational Considerations None Topics Changes Management Issues None Description of Improvements Automatic Assignment of Voucher numbers by the system gives complete control in terms of recording the transactions sequentially rather than manual assignment of vouchers. Pulling out Reports by Document type. Description of Functional Deficits None Approaches for covering Functional Deficit Not Applicable Topics Notes on Further Improvement Not Applicable Topics System configuration considerations Various Document Types should be defined. Availability of these document types to various account types should be defined. File conversion considerations (Master data maintenance). None Reporting considerations None Authorization considerations None

4.3 4.4

Sr No 5.1

Sr No 6.1

6.2

6.3 6.4

166531223.doc

8/23/2013

Page 10 of62

FI0203 Tax on Sales/Purchases in SAP System

Module Process Sub Process Sr No 1.1 Financial Accounting Basic Setting Tax on Sales/Purchasing in SAP Systems

Topics Requirements & Expectations Provisions for the following Tax on Purchase & Sales are required. 1. Sales Tax 2. Sales Tax on Purchase (URD purchases) 3. Excise duty 4. Custom Duty

Sr No 2.1

Topics Existing Process General Explanation Excise Duty 1. Excise duty is charged on sales of all products at applicable rates. Excise duty is paid on purchases(Except Cycle Division ), wherever applicable. Modvat is claimed equivalent to the amount of duty paid except in case of capital goods / goods which are not input items, where 50 % of Modvat is taken at the time of purchase & balance 50 % is taken in the next Financial Year. Sales Tax 1. Sales Tax is charged on Sales of all products at applicable rates (except in the case of job work, where we do not charge sales tax) after taking into consideration. a. Type of Product b. Place of Sale c. Type of Customer, (i.e. providing ST forms or not ) d. Etc. .

2.2

Explanation of Existing Functions & Events Flow Sheet Not Applicable

166531223.doc

8/23/2013

Page 11 of62

2.3

Special Organizational Considerations Not Applicable

Sr No 3.1

Topics Proposed Process General Explanation Tax Codes for Sale of goods as per respective categories (as per requirement) along with the rates will be defined in SAP. Explanation of Proposed Functions & Events Flow Sheet Not Applicable Special Organizational Considerations None Topics Changes Management Issues None Description of Improvements Description of Functional Deficits None Approaches for covering Functional Deficit Not Applicable Topics Notes on Further Improvement Not Applicable Topics System configuration considerations Relevant Tax codes along with rates to be created. File conversion considerations (Master data maintenance). None Interface considerations None Reporting considerations None

3.2 3.3

Sr No 4.1 4.2 4.3 4.4

Sr No 5.1

Sr No 6.1 6.2 6.3 6.4

166531223.doc

8/23/2013

Page 12 of62

6.5

Authorization considerations None

166531223.doc

8/23/2013

Page 13 of62

FI0204 Posting Help

Module Process Sub Process Sr No 1.1 Financial Accounting Basic Setting Posting Help

Topics Requirements & Expectations 1. In SAP we require certain Templates for regular entries such as Rent, Payment of Statutory dues such as Income Tax TDS, Sales Tax, Provident Fund, ESIC, etc., Topics Existing Process General Explanation Amount of TDS, Sales Tax, ESIC, PF etc are calculated manually through system. However, before payment the respective GL accounts are reconciled.

Sr No 2.1

2.2 2.3

Explanation of Existing Functions & Events Flow Sheet Not Applicable Special Organizational Considerations Not Applicable

Sr No 3.1

Topics Proposed Process General Explanation Accounting of Transactions which are very regular in business can be easily accounted through Account Assignment Model, Fast Entry tool & Post with Reference Options. Explanation of Proposed Functions & Events Flow Sheet Not Applicable Special Organizational Considerations Topics Changes Management Issues None Description of Improvements

3.2 3.3 Sr No 4.1 4.2

166531223.doc

8/23/2013

Page 14 of62

4.3 4.4

Manual entering of regularly occurring transactions can be accounted much faster. Accuracy in using the GL accounts and other details can be maintained. Description of Functional Deficits None Approaches for covering Functional Deficit Not Applicable Topics Notes on Further Improvement Not Applicable Topics System configuration considerations Account Assignment Models, Fast entry tools should be created. File conversion considerations (Master data maintenance). None Interface considerations None Reporting considerations None Authorization considerations None

Sr No 5.1

Sr No 6.1 6.2 6.3 6.4 6.5

166531223.doc

8/23/2013

Page 15 of62

FI0205 Withholding Tax

Module Process Sub Process Sr No 1.1 Financial Accounting Basic Setting Withholding Tax

Topics Requirements & Expectations 1. Tax Deduction At Source (TDS) are to be booked every month & paid before 7th of subsequent month. 2. TDS amounts are expected to be generated automatically in SAP. A proper Year wise breakup bifurcation into each category of TDS rates & further reclassification into Corporate & Non Corporate required. 3. Also TDS Certificates Form 16A & Form 16 to be generated from SAP, along with Annual Return Form 26, 27 etc Topics Existing Process General Explanation 1. TDS GL A/c Rate wise & entity wise (Corporate/Non Corporate) is created under the sub group Duties & Taxes under group Current Liabilities. At the time of booking the expenses & crediting to vendor account, the user identifies a. Whether TDS is applicable. b. What rate of TDS applicable. c. Whether the Vendor is a Corporate or non Corporate & books the entry in Tally accordingly. Payment for the same is made before the 7th of the subsequent month. . Explanation of Existing Functions & Events Flow Sheet Not Applicable Special Organizational Considerations Not Applicable Topics Proposed Process General Explanation Withholding Tax Types & Withholding Tax codes along for the above said combinations will be created and the same should be assigned to the vendor master records. Rounding of Tax will be done to nearest rupee.

Sr No 2.1

2.2 2.3

Sr No 3.1

166531223.doc

8/23/2013

Page 16 of62

 3.2 3.3 Sr No 4.1 4.2 4.3 4.4

TDS on salary would be taken care in HR module.

Explanation of Proposed Functions & Events Flow Sheet Not Applicable Special Organizational Considerations None Topics Changes Management Issues Description of Improvements Withholding Tax calculation & Printing would be done online by the system. Description of Functional Deficits None Approaches for covering Functional Deficit Not Applicable Topics Notes on Further Improvement Not Applicable Topics System configuration considerations Various WT Codes & Types for various combinations to be created in SAP. File conversion considerations (Master data maintenance). None Interface considerations None Reporting considerations Withholding Tax reports showing the amount of tax deducted will be generated. Authorization considerations None

Sr No 5.1

Sr No 6.1 6.2 6.3 6.4 6.5

166531223.doc

8/23/2013

Page 17 of62

FI03 General Ledger Processing

FI0301 Postings in GL
Module Process Sub Process Sr No 1.1 Financial Accounting General Ledger Processing Postings in GL

Topics Requirements & Expectations 1. Vouchers are posted into the GL accounts directly after the concerned Manager approves them. 2. A proper validation check is required whereby the person entering the document should not have the right to post the document into GL. This will be vested in the hands of the Managers. Topics Existing Process General Explanation 1. Journal Vouchers: b) The Executive receives the supporting documents i.e. bills / invoices. c) On this basis he makes an entry into GL. d) He prints the voucher and attaches the supporting along with it and sends it to the Manager Accounts for approval. e) The Manager approves the vouchers and the signed document is then filed. 2. Cash Vouchers : a) In the case of Cash Vouchers, payment is made against bills duly authorized by the concerned HOD. b) A petty cash book is maintained by the cashier manually, Cashier after entering into this petty cash book makes the necessary payments. c) At the end of the day all the bills against which payment is made are punched into the system i.e. Cash Voucher is prepared and the cash balance as per system is tallied with the physical cash. d) In case cash is received from someone, CASH RECEIPT VOUCHER is prepared. e) After the voucher is punched into the system, Voucher & Annexure are printed through system, attached with the bills paid and given to HOD for approval.

Sr No 2.1

166531223.doc

8/23/2013

Page 18 of62

3. Allocation of Materials Issued : a. Raw Material, BOC, Direct consumables etc which are in BOM are issued when Final Production entry is punched into the system, prior to the issue of finished products to Despatch Department for Despatch. (i.e. during transfer of final product to the Despatch Department). All the items other than those mentioned above are treated as issued / consumed as soon as MIN is prepared. b. Capital Work in Progress : Details below 4. Capital Work in Progress : All expenses & issue of materials for projects which are not expected to get completed in a particular financial year are capitalized as Capital Work In Progress (CWIP). E.g. etc. On completion of the project the total project cost is transferred to Fixed Assets under Plant & Machinery. 5. Cash Imprest, Loans & Advances: As decided by the management, a certain amount of cash is given to some employees for day-to-day expenses by debiting their imprest account. This kind of imprest is called running imprest. It has to be cleared by the employee at the financial year end and can be taken again, in the next financial year. If required, any employee can take advance / loan in his / her imprest account for certain purposes like for tour, urgent cash purchases etc. Imprest has to be settled before the month end. Moreover, if the amount of loan / advance exceeds Rupees 20000.00 in a Financial Year, it attracts interest as per Income Tax Act. Such interest is calculated through system on monthly reducing balances and added to the taxable income of the employee as a perquisite. (It is calculated only for the purpose of calculation of income Tax without making any entry in the Books) For taking loan / advance, the employee has to submit an application duly approved by competent authority, with the Finance Department. If the payment is to be made through cheque, the Finance Department prepares cheque by debiting the Loan / advance account of respective employee. At the time of preparation of cheque the following informations are punched into the system while preparing BANK VOUCHER/Cash Voucher: Type (loan or advance) Employee name (Employee code, department, shop code etc are automatically picked by the system through his / her name) Amount of loan / advance Nature of loan / advance Number of installments Approving authority Before disbursement of Salary / Wages the Finance Department makes sure that the installments are deducted from Salary / Wages of respective employees. For this there are various frames in the Finance Menu through which Loan Balance, employee wise loan details of last five years etc can be viewed. 2.2
166531223.doc

Explanation of Existing Functions & Events Flow Sheet

Page 19 of62

8/23/2013

2.3

Not Applicable Special Organizational Considerations Not Applicable Topics Proposed Process General Explanation The entered JVs will be parked by the executive and will be posted into the books only after the authorized person approves the same. In case of cash transactions Cash Journal will be used which will act as a sub ledger. Depending on the needs several cash journals will be used. The system automatically calculates Opening & closing balances and the receipts & payments totals. The entries entered in the cash journal will be saved before posting into Books. After proper authorization these transactions will be booked into FI books. Material issues for Consumption, Fixed assets will flow from MM module into FI. Details pertaining to Capital WIP can be captured by creating an Internal Order until Asset Management is implemented wherein the functionality of Assets Under Construction can be used to capture the Capital WIP. For Cash Imprest & Advances given to employees, separate vendor accounts will be created for each employee. Explanation of Proposed Functions & Events Flow Sheet Not Applicable Special Organizational Considerations None Topics Changes Management Issues None Description of Improvements Description of Functional Deficits None Approaches for covering Functional Deficit Not Applicable Topics Notes on Further Improvement Not Applicable Topics

Sr No 3.1

3.2 3.3 Sr No 4.1 4.2 4.3 4.4

Sr No 5.1

Sr No
166531223.doc

8/23/2013

Page 20 of62

6.1 6.2 6.3 6.4 6.5

System configuration considerations File conversion considerations (Master data maintenance). None Interface considerations None Reporting considerations None Authorization considerations None

FI0302 General Ledger Account Analysis

166531223.doc

8/23/2013

Page 21 of62

Module Process Sub Process Sr No 1.1

Financial Accounting General Ledger Processing General Ledger Account Analysis

Topics Requirements & Expectations 1. A detail report of all line items date wise to be made available. 2. Analysis of line items into cost centers & profit centers desired. 3. Group wise ledger accounts desired. 4. Printing option to be made available at Main group level or sub-level or Cost Center level depending on the requirement of the person. 5. Link of Ledger accounts up to Balance Sheet & Profit & Loss Account level to be obtained. All the above reports to be made available for any desired periods. Topics Existing Process General Explanation a) The Executive executes the GL printing by selecting the Account he wants to scrutinize. b) He can scrutinize the account on screen or he can print the output onto a printer. c) Detail analysis of Cost Centre wise breakup is available for Balance Sheet as well as P& L Items. d) A Group wise scrutiny is also possible. e) Analysis of Cash Flow transactions. Explanation of Existing Functions & Events Flow Sheet Not Applicable Special Organizational Considerations Not Applicable Topics Proposed Process General Explanation Some of the Generally available reports in SAP are Balance Sheet / Profit and Loss Statement Cash Flow Actual/Actual Comparison for Year Periodic Plan/Actual Comparison G/L Account Balances G/L Line Items, List for Printing G/L Account Statements Explanation of Proposed Functions & Events Flow Sheet
Page 22 of62

Sr No 2.1

2.2 2.3

Sr No 3.1

3.2
166531223.doc

8/23/2013

Not Applicable 3.3 Sr No 4.1 4.2 4.3 4.4 Special Organizational Considerations None Topics Changes Management Issues None Description of Improvements Above said reports can be made available at any point of time. Description of Functional Deficits None Approaches for covering Functional Deficit Not Applicable Topics Notes on Further Improvement Not Applicable Topics System configuration considerations None File conversion considerations (Master data maintenance). None Interface considerations None Reporting considerations Any other reports apart from the above would be considered for development. Authorization considerations None

Sr No 5.1

Sr No 6.1 6.2 6.3 6.4

6.5

166531223.doc

8/23/2013

Page 23 of62

FI0303 Account Clearing [GL]

Module Process Sub Process Sr No 1.1 Financial Accounting General Ledger Processing Account Clearing [GL]

Topics Requirements & Expectations 1. Open item options to be maintained for Balance sheet items so that it can be squared off. 2. Accounts should always show Open Items. Topics Existing Process General Explanation a) The Entry is posted in accounts and GL will give reference of the document on which it is cleared. b) Clearing can be part or in full. Explanation of Existing Functions & Events Flow Sheet Not Applicable Special Organizational Considerations Not Applicable

Sr No 2.1

2.2 2.3

Sr No 3.1

Topics Proposed Process General Explanation SAP offers the following procedures for clearing the accounts with Open Item Management. 1. Account Clearing: In this transactions belonging to only one account can be cleared and no clearing document will be generated. 2. Post with Clearing: In this Posting as well as Clearing is done simultaneously and a clearing document will be generated. In one clearing transaction we can process several accounts and different account types (G/L account, Customer, Vendor).

3.2
166531223.doc

Explanation of Proposed Functions & Events Flow Sheet

8/23/2013

Page 24 of62

Not Applicable 3.3 Sr No 4.1 4.2 Special Organizational Considerations None Topics Changes Management Issues None Description of Improvements Clearing documents keep a track of which accounting documents were cleared and by which user. Sub ledger & GL are updated online keeping the Information system updated. Analysis on cleared items can be drawn at any point of time. Description of Functional Deficits None Approaches for covering Functional Deficit Not Applicable Topics Notes on Further Improvement Not Applicable Topics System configuration considerations Clearing Rules to be defined. File conversion considerations (Master data maintenance). None Interface considerations None Reporting considerations None Authorization considerations None

4.3 4.4

Sr No 5.1

Sr No 6.1 6.2 6.3 6.4 6.5

166531223.doc

8/23/2013

Page 25 of62

FI0304 Recurring Entries

Module Process Sub Process Sr No 1.1 Financial Accounting General Ledger Processing Recurring Entries

Topics Requirements & Expectations 1. Recurring entries like Rent, Loan instalments, Hire purchase instalments etc to be automatically posted at the appropriate due dates. 2. Subsequently payments to be made automatically on due dates subject to funds availability. 3. Recurring entries to be posted automatically at one go for all accounts on a particular run date. Topics Existing Process General Explanation a) Recurring entries are posted manually for certain payments to be made on a monthly or quarterly basis. b) A normal payment entry is passed in GL when the payment is made and the document is printed for approval and sent for filing. Explanation of Existing Functions & Events Flow Sheet Not Applicable Special Organizational Considerations Not Applicable

Sr No 2.1

2.2 2.3

Sr No 3.1

Topics Proposed Process General Explanation Recurring entries are business transactions that are repeated regularly, such as rent or insurance. The recurring data is entered in a recurring entry original document, which does not update the transaction figures. The recurring entry program uses it as a basis for creating Accounting Documents. The following data never changes in recurring entries : posting Key, Account & Amount.

3.2
166531223.doc

Explanation of Proposed Functions & Events Flow Sheet

Page 26 of62

8/23/2013

Not Applicable 3.3 Sr No 4.1 4.2 4.3 4.4 Special Organizational Considerations None Topics Changes Management Issues None Description of Improvements Automatic Creation of Accounting Documents at one go. Description of Functional Deficits None Approaches for covering Functional Deficit Not Applicable Topics Notes on Further Improvement Not Applicable Topics System configuration considerations Recurring Document Models to be created. File conversion considerations (Master data maintenance). None Interface considerations None Reporting considerations None Authorization considerations None

Sr No 5.1

Sr No 6.1 6.2 6.3 6.4 6.5

166531223.doc

8/23/2013

Page 27 of62

FI0305 Closing Operations

Module Process Sub Process Sr No 1.1 Financial Accounting General Ledger Processing Closing Operations

Topics Requirements & Expectations 1. Monthly & Yearly closing should be maintained. 2. Monthly, Quarterly, Yearly Trial Balance, P&L, Cash Flow and Balance sheet required. Topics Existing Process General Explanation a) Accounts are closed on a monthly basis for the purpose of MIS. Provision entries are passed at the end of the month b) During year end all entries for provisions and adjustments are passed into books of accounts. A trial balance is obtained from system. Balance sheet & Profit & Loss accounts are prepared & compiled in Excel in a schedule VI Format. c) Trial Balance run and scrutinized. d) Necessary rectification entries passed to rectify discrepancies. e) Final Adjustment entries passed. f) Profit & Loss and Balance Sheet printed. g) Cash Flow is also generated in Excel. Explanation of Existing Functions & Events Flow Sheet Not Applicable Special Organizational Considerations Not Applicable

Sr No 2.1

2.2 2.3

166531223.doc

8/23/2013

Page 28 of62

Sr No 3.1

Topics Proposed Process General Explanation Closing Operations to be performed Month wise, Quarter wise & Year wise . To carry out closing operations in GL, closing operations have to be performed in the following sub ledgers: Accounts Receivable & Accounts Payable, Materials Management, and Asset Accounting & Payroll. Data from other Branches has to flown into SAP through a proper interface program. Once data is consolidated from all the relevant resources reports like Trial Balance, P& L account, Balance sheet can be pulled out from SAP.

3.2 3.3 Sr No 4.1 4.2

Explanation of Proposed Functions & Events Flow Sheet Not Applicable Special Organizational Considerations None Topics Changes Management Issues None Description of Improvements As the Data is maintained Online, Reports like Balance Sheet, P&L account, Cash flow statements can be pulled out at any point of time. Description of Functional Deficits None Approaches for covering Functional Deficit Not Applicable Topics Notes on Further Improvement Not Applicable Topics System configuration considerations Posting Periods in all other sub ledgers need to be closed before performing closing operations in GL.
Page 29 of62

4.3 4.4

Sr No 5.1

Sr No 6.1

166531223.doc

8/23/2013

6.2 6.3 6.4 6.5

File conversion considerations (Master data maintenance). None Interface considerations None Reporting considerations None Authorization considerations None

166531223.doc

8/23/2013

Page 30 of62

FI04 Accounts Payable Processing

FI0401 Vendor Down Payments
Module Process Sub Process Sr No 1.1 Financial Accounting Accounts Payable Processing Vendor Down Payments

Topics Requirements & Expectations 1. A proper system to be implemented for down payments taking into consideration the As Is procedure as mentioned below. Topics Existing Process General Explanation a) A request for making a down payment is received from Purchase Department through a Purchase document (or concerned department). b) Normally down payments are made as advance against a Purchase Order or as On-Account payment against existing balance. c) All down payments are approved as per fund allocation and are passed into vendor account. d) They are reflected on the credit side under the head Current liabilities as Advances. Explanation of Existing Functions & Events Flow Sheet Not Applicable Special Organizational Considerations Not Applicable

Sr No 2.1

2.2 2.3

Sr No 3.1

Topics Proposed Process General Explanation Special G/L transactions are special transactions in accounts receivable and accounts payable that are displayed separately in the general ledger and the subledger. This is achieved by posting to alternative reconciliation accounts, instead of posting to the reconciliation accounts for receivables and payables . This may be necessary for reporting or for internal reasons. For example, down payments, guarantees, Security deposits, Bills of Exchange etc. Down Payment Requests in SAP is recorded as a Noted item which functions as a reminder to make the down payment . The

166531223.doc

8/23/2013

Page 31 of62

document so generated on posting will not update any debits & credits. Down Payment made with reference to Request clears the request and is posted to Special GL account, gets reflected in GL through Alternative Reconciliation account and is shown under Current Assets in the Balance Sheet.

3.2 3.3 Sr No 4.1 4.2

Explanation of Proposed Functions & Events Flow Sheet Not Applicable Special Organizational Considerations None Topics Changes Management Issues None Description of Improvements Transactions like Advance, Bills of Exchange, Security deposits, Guarantee are separately tracked through Special GLs, hence not mixed up with receivables & payables for goods & services thereby keeping controlled track of these transactions. Description of Functional Deficits None Approaches for covering Functional Deficit Not Applicable Topics Notes on Further Improvement Not Applicable Topics System configuration considerations Special GL Indicators should be defined for each type and the Alternative Reconciliation Accounts for each type. File conversion considerations (Master data maintenance). None Interface considerations None Reporting considerations Desired reports like Advance received, Advance made etc can be pulled out for desired periods, customers/vendors etc.

4.3 4.4

Sr No 5.1

Sr No 6.1

6.2 6.3 6.4

166531223.doc

8/23/2013

Page 32 of62

6.5

Authorization considerations

FI0402 Invoices and Credit Memos

Module Process Sub Process Sr No 1.1 Financial Accounting Accounts Payable Processing Invoices and Credit Memos

Topics Requirements & Expectations 1. A valid system of authorization of invoice & Credit memos to be incorporated. Topics Existing Process General Explanation a) Invoices are received by accounts after preparation of Purchase order and SRN from the Material Department (MD). b) The vendor invoices are verified with reference to SRR and purchase order. The quantities are matched with SRR quantities, in case there are any shortages the separate debit notes for shortages are raised for short quantity to the vendor. Similarly, prices are matched with PO prices, in case of rate difference the separate debit notes for rate difference are raised to the vendors. b) The annexure is printed and all supporting documents are attached. c) The document is signed by the Accounts Executive and authorized by the Manager & then sent for filing.

Sr No 2.1

2.2 2.3

Explanation of Existing Functions & Events Flow Sheet Not Applicable Special Organizational Considerations Not Applicable

Sr No 3.1
166531223.doc

Topics Proposed Process General Explanation Invoice verification with PO, GRN & DC is done in FI module.
Page 33 of62

8/23/2013

Once it is done the accounting entries flow automatically into FI books. Authorization Groups for the Invoices are to be defined in FI module. Only after the authorized person posts the Invoice the purchase transaction values flow into FI books.

3.2 3.3 Sr No 4.1 4.2 4.3 4.4

Explanation of Proposed Functions & Events Flow Sheet Not Applicable Special Organizational Considerations None Topics Changes Management Issues None Description of Improvements Description of Functional Deficits None Approaches for covering Functional Deficit Not Applicable Topics Notes on Further Improvement Not Applicable Topics System configuration considerations Authorization Groups should be defined accordingly. File conversion considerations (Master data maintenance). None Interface considerations None Reporting considerations None Authorization considerations None

Sr No 5.1

Sr No 6.1 6.2 6.3 6.4 6.5

166531223.doc

8/23/2013

Page 34 of62

FI0403 Vendor Account Analysis

Module Process Sub Process Sr No 1.1 Financial Accounting Accounts Payable Processing Vendor Account Analysis

Topics Requirements & Expectations 1. A detail Vendor wise Accounts Analysis Vendor wise to be made available at any time on a month wise fashion. 2. Detail bifurcation into clear & open items to be made available. 3. Age Wise outstanding report required. 4. Group wise analysis of Vendor required. 5. A report of Advance to Vendors required. 6. Purchase Order balances (Qty wise & Value wise) Topics Existing Process General Explanation a) Vendor outstanding (Bill wise & amount wise detail) is generated on weekly basis for making vendor payment. All the bills due upto that day are shown in that statement. The said bills are paid vide cheques. b) Whenever a vendor account has to be scrutinized, the account is run on screen or the output is generated on print. c) Rectification entries are passed whenever the vendor account is scrutinized. d) Month end provisions are passed for MIS closing. e) The final scrutiny is carried out at the year-end when the rectification entries and provision entries are passed into the vendor accounts. Explanation of Existing Functions & Events Flow Sheet Not Applicable Special Organizational Considerations Not Applicable

Sr No 2.1

2.2 2.3

Sr No
166531223.doc

Topics

8/23/2013

Page 35 of62

3.1

Proposed Process General Explanation Apart from Regular SAP reports like Vendor Account Balances Due Date Analysis for Open Items List of Vendor Line Items List of Vendor Open Items for Printing Open Items - Vendor Due Date Forecast Vendor Payment History with OI Sorted List List of Cleared Vendor Items for Printing List of Down Payments Open On Key Date Vendors Payment List Check Register Many more customized reports can be formulated depending upon the business needs.

3.2 3.3 Sr No 4.1 4.2 4.3 4.4

Explanation of Proposed Functions & Events Flow Sheet Not Applicable Special Organizational Considerations None Topics Changes Management Issues None Description of Improvements All the above desired reports are available at any point of time. Description of Functional Deficits None Approaches for covering Functional Deficit Not Applicable Topics Notes on Further Improvement Not Applicable Topics System configuration considerations Apart from SAP standard reports any others need to be developed. File conversion considerations (Master data maintenance). None Interface considerations None

Sr No 5.1

Sr No 6.1 6.2 6.3

166531223.doc

8/23/2013

Page 36 of62

6.4 6.5

Reporting considerations On need basis customized reports will be generated Authorization considerations None

FI0404 Vendor Payments

166531223.doc

8/23/2013

Page 37 of62

Module Process Sub Process Sr No 1.1

Financial Accounting Accounts Payable Processing Vendor Payments

Topics Requirements & Expectations 1. Payments are required to be made on a bill-to-bill basis, either fully or partly. Topics Existing Process General Explanation a) Vendor payments are done on the basis of account balances of the particular vendor. Payments are made based on Due dates . However due dates are maintained as the basis for all payment entry. b) Payment request is received from the Vendor/Department (either in case of advance payment or before the due date) c) Accounts Executive checks the vendor account for balance & due date to release payment. d) Payment voucher is created and vendor account is given effect. e) Cheques are printed automatically from the system. f) Payment voucher, Cheques along with the supporting documents are sent to the manager for approval. g) The same is then forward to the designated signatories for their signatures. h) The signed Cheques are couriered to parties. i) Voucher along with the supporting documents are filed. Explanation of Existing Functions & Events Flow Sheet Not Applicable Special Organizational Considerations Not Applicable

Sr No 2.1

2.2 2.3

Sr No 3.1

Topics Proposed Process General Explanation Payments to Vendors can be done manually wherein individual vendor accounts are pulled out and choosing the bills which are to be paid out. Cheque on the name of the vendor would be automatically printed out on posting the transaction.

166531223.doc

8/23/2013

Page 38 of62

Using the Option Post with Clearing + Print forms option not only clears the open item but also generates a cheque. Payments to group of vendors will be proposed & put in choose list through Automatic Payment Program wherein a range of vendors to be paid out are selected in the program and the vendors whose due date falls on the Payment Program Run will be paid out through Cheque .

3.2 3.3 Sr No 4.1 4.2

Explanation of Proposed Functions & Events Flow Sheet Not Applicable Special Organizational Considerations None Topics Changes Management Issues None Description of Improvements Vendor Sub ledger account & GL are updated simultaneously on clearing the Open item transactions Description of Functional Deficits None Approaches for covering Functional Deficit Not Applicable Topics Notes on Further Improvement Not Applicable Topics System configuration considerations Automatic payment program to be configured. File conversion considerations (Master data maintenance). None Interface considerations None Reporting considerations None Authorization considerations

4.3 4.4

Sr No 5.1

Sr No 6.1 6.2 6.3 6.4 6.5

166531223.doc

8/23/2013

Page 39 of62

FI0405 Bill of Exchange Payable

Module Process Sub Process Sr No 1.1 Financial Accounting Accounts Payable Processing Bill of Exchange payable

Topics Requirements & Expectations 1. An option for Bill of Exchange & Hundi required. 2. Due Date Wise Report to be generated as & when required. Topics 1. RCIL deal in a Local form of bill of exchange which is known as HUNDI. The process is similar to that of Vendor Payments, which is as under. a The Bill of Exchange is received from the vendor. After checking it with our records, the same is accepted and sent back to the vendor. b. A record of such transactions is maintained in an Excel file. c. On due date the said Bill of Exchange is paid by the Bank.

Sr No 2.1

Sr No 3.1

Topics Proposed Process General Explanation Bills of Exchange in SAP are separately tracked through Special GL indicators which are linked to GL through Alternative Reconciliation account. On Acceptance of Hundi vendor account gets knocked off with the Hundi amount and the liability to bank is showed through Bills Payable account. Report showing due dates for Bills Payable can be pulled out at any point of time. Explanation of Proposed Functions & Events Flow Sheet Not Applicable Special Organizational Considerations None Topics Changes Management Issues None Description of Improvements Description of Functional Deficits
Page 40 of62

3.2 3.3 Sr No 4.1 4.2 4.3

166531223.doc

8/23/2013

None 4.4 Approaches for covering Functional Deficit Not Applicable Topics Notes on Further Improvement Not Applicable Topics System configuration considerations Special GL indicators for Bills of Exchange need to be created. File conversion considerations (Master data maintenance). None Interface considerations None Reporting considerations Need based reports can be formulated. Authorization considerations None

Sr No 5.1

Sr No 6.1 6.2 6.3 6.4 6.5

166531223.doc

8/23/2013

Page 41 of62

FI0406 Account Clearing [AP]

Module Process Sub Process Sr No 1.1 Financial Accounting Accounts Payable Processing Account Clearing [AP]

Topics Requirements & Expectations 1. A proper system in SAP to be implemented taking into consideration the AS IS scenario. Topics Existing Process General Explanation 1. In present system, at the time of booking the purchase / expenses we have following methods of adjustments. a. Against Reference: To add on to an already existing Bill Reference. b Advance : To Book as Advance (Advance can be given more than once against the same purchase order like 20 % after completion of one stage, 20 % against next stage & so on) c New Reference : To Create new Bill Reference d On Account : Not to book against as a specific Bill Reference Explanation of Existing Functions & Events Flow Sheet Not Applicable Special Organizational Considerations Not Applicable

Sr No 2.1

2.2 2.3

Sr No 3.1

Topics Proposed Process General Explanation SAP offers the following procedures for clearing the accounts with Open Item Management. 1. Account Clearing: In this transactions belonging to only one account can be cleared and no clearing document will be generated. 2. Post with Clearing: In this Posting as well as Clearing is done simultaneously and a clearing document will be generated. In one clearing transaction we can process several accounts and different account types (G/L account,

166531223.doc

8/23/2013

Page 42 of62

Customer, Vendor).

3.2 3.3 Sr No 4.1 4.2

Explanation of Proposed Functions & Events Flow Sheet Not Applicable Special Organizational Considerations None Topics Changes Management Issues None Description of Improvements Clearing documents keep a track of which accounting documents were cleared and by which user. Sub ledger & GL are updated online keeping the Information system updated. Analysis on cleared items can be drawn at any point of time. Description of Functional Deficits None Approaches for covering Functional Deficit Not Applicable Topics Notes on Further Improvement Not Applicable Topics System configuration considerations Clearing rules to be defined. File conversion considerations (Master data maintenance). Interface considerations None Reporting considerations None Authorization considerations None

4.3 4.4

Sr No 5.1

Sr No 6.1 6.2 6.3 6.4 6.5

166531223.doc

8/23/2013

Page 43 of62

FI0407 Correspondence with Vendors

Module Process Sub Process Sr No 1.1 Financial Accounting Accounts Payable Processing Correspondence with Vendors

Topics Requirements & Expectations 1. Correspondence with Vendors is expected while generating Yearly Balance Confirmation / Outstanding. 2. Confirmation for PO raised but Goods Not received. 3. Defective Goods / Replacements. Topics Existing Process General Explanation Annual Balance Confirmation is sent to vendors / customers Necessary letter is generated through system and sent to vendors / customers for confirmation of balances. Explanation of Existing Functions & Events Flow Sheet Not Applicable Special Organizational Considerations Not Applicable

Sr No 2.1

2.2 2.3

Sr No 3.1

Topics Proposed Process General Explanation All evaluations and reports that we send to business partners by mail are considered correspondence. Correspondence for both customers and vendors includes: Account statements and open items lists in letter form Individual letters and standard letters Balance confirmations Document extracts

166531223.doc

8/23/2013

Page 44 of62

3.2 3.3 Sr No 4.1 4.2

Explanation of Proposed Functions & Events Flow Sheet Not Applicable Special Organizational Considerations None Topics Changes Management Issues None Description of Improvements By using various types of correspondence types available in SAP, Communication between business partners is standardized. Description of Functional Deficits None Approaches for covering Functional Deficit Not Applicable Topics Notes on Further Improvement Not Applicable Topics System configuration considerations Standard SAP correspondence types to be used. If any changes to be made to the existing ones will be considered. File conversion considerations (Master data maintenance). None Interface considerations None Reporting considerations None Authorization considerations None

4.3 4.4

Sr No 5.1

Sr No 6.1

6.2 6.3 6.4 6.5

166531223.doc

8/23/2013

Page 45 of62

FI05 Accounts Receivables Processing

FI0501 Customer Down Payments
Module Process Sub Process Sr No 1.1 Financial Accounting Accounts Receivables Processing Customer Down Payments

Topics Requirements & Expectations 1. Down payments made by customer should be adjusted with his future bills, any unadjusted amount should appear as an advance in books of accounts (Advance received for special purposes like development of tooling etc should be shown separately and detailed report should be available at any time which covers all the information relating to that advance) 2. A report should be made available for all such advance received as and When required. Topics Existing Process General Explanation 1. Whenever a down payment is received from a customer the same is credited to his account (opened under the GL Account Advance from customers) & shown as advance received. 2. This advance is then adjusted against the future Sales (or as agreed with the customer). Explanation of Existing Functions & Events Flow Sheet Not Applicable Special Organizational Considerations Not Applicable Topics Proposed Process General Explanation Advance received from Customers is accounted into GL through Alternative Reconciliation Account via Special GL Indicators. The above advance gets adjusted against future bills or as per agreed terms with the customers. Desired reports relating to Customer Advances can be pulled out from SAP. Explanation of Proposed Functions & Events Flow Sheet
Page 46 of62

Sr No 2.1

2.2 2.3

Sr No 3.1

3.2
166531223.doc

8/23/2013

Not Applicable 3.3 Sr No 4.1 4.2 4.3 4.4 Special Organizational Considerations None Topics Changes Management Issues None Description of Improvements None Description of Functional Deficits None Approaches for covering Functional Deficit Not Applicable Topics Notes on Further Improvement Not Applicable Topics System configuration considerations Special GL Indicators & Alternative Reconciliation Accounts should be defined File conversion considerations (Master data maintenance). None Interface considerations None Reporting considerations None Authorization considerations None

Sr No 5.1

Sr No 6.1 6.2 6.3 6.4 6.5

166531223.doc

8/23/2013

Page 47 of62

FI0502 Invoices & Credit Notes

Module Process Sub Process Sr No 1.1 Financial Accounting Accounts Receivables Processing Invoices & Credit Notes

Topics Requirements & Expectations a. Invoices against sale of finished goods or job work. b. Only MD should be authorized to issue any Credit Notes or Discounts.

Sr No 2.1

Topics Existing Process General Explanation Only MD authorized to issue any Credit Notes or Discounts.

2.2 2.3

Explanation of Existing Functions & Events Flow Sheet Not Applicable Special Organizational Considerations Not Applicable

Sr No 3.1

Topics Proposed Process General Explanation For Customers which are maintained in SAP , Billing information flows from Sales & Distribution module which get accounted in FI module. Credit Notes, Discounts against each Invoice get accounted only after proper authorization from VP Finance & CFO. Accordingly Authorization Groups will be defined in SAP which controls the above transactions. Explanation of Proposed Functions & Events Flow Sheet Not Applicable Special Organizational Considerations None Topics
Page 48 of62

3.2 3.3 Sr No
166531223.doc

8/23/2013

4.1 4.2 4.3 4.4

Changes Management Issues None Description of Improvements None Description of Functional Deficits None Approaches for covering Functional Deficit Not Applicable Topics Notes on Further Improvement Not Applicable Topics System configuration considerations Authorization groups should be defined & assigned to Customer Master Records. File conversion considerations (Master data maintenance). None Interface considerations None Reporting considerations None Authorization considerations None

Sr No 5.1

Sr No 6.1

6.2 6.3 6.4 6.5

166531223.doc

8/23/2013

Page 49 of62

FI0503 Account Analysis

Module Process Sub Process Sr No 1.1 Financial Accounting Accounts Receivables Processing Account Analysis

Topics Requirements & Expectations 1. Following reports are required. a. Amount Billed Subscriber wise but no collections received. b. O/s greater the certain specific amounts. c. O/s of Disconnected Subscribers/Operators. d. Statement showing Operators / Subscribers paying different rates then actually billed. e. Amount Collected but no bills generated. f. Collection Officer wise O/s Statements. g. Collection Targets & incentives based on Targets. h. Headend wise / Subscribers wise / Operator wise Discount Report. 2. Age wise outstanding of Debtors into desirable periods, is expected. Topics Existing Process General Explanation

Sr No 2.1

2.2 2.3

Explanation of Existing Functions & Events Flow Sheet Not Applicable Special Organizational Considerations Not Applicable

Sr No 3.1

Topics Proposed Process General Explanation For the Customers maintained in SAP the following reports are available. Customer Balances Customer Sales

166531223.doc

8/23/2013

Page 50 of62

 3.2 3.3 Sr No 4.1 4.2 4.3 4.4

Due Date Analysis for Open Items List of Customer Line Items List of Customer Open Items Open Items - Customer Due Date Forecast Customer Payment History Customer Open Item Analysis by Balance of Overdue Items List of Cleared Customer Items for Printing List Of Down Payments Open On Key Date Customers

Explanation of Proposed Functions & Events Flow Sheet Not Applicable Special Organizational Considerations None Topics Changes Management Issues None Description of Improvements All the above desired reports are made available at any point of time. Description of Functional Deficits None Approaches for covering Functional Deficit Not Applicable

Sr No 5.1

Topics Notes on Further Improvement Not Applicable Topics System configuration considerations None File conversion considerations (Master data maintenance). None Interface considerations None Reporting considerations On need basis customized reports will be generated. Authorization considerations

Sr No 6.1 6.2 6.3 6.4 6.5

166531223.doc

8/23/2013

Page 51 of62

None

166531223.doc

8/23/2013

Page 52 of62

FI0504 Customer Payments

Module Process Sub Process Sr No 1.1 Financial Accounting Accounts Receivables Processing Receipts from Payments to Customer

Topics Requirements & Expectations

Sr No 2.1

Topics Existing Process General Explanation

2.2 2.3

Explanation of Existing Functions & Events Flow Sheet Not Applicable Special Organizational Considerations Not Applicable

Sr No 3.1

Topics Proposed Process General Explanation

3.2 3.3
166531223.doc

Explanation of Proposed Functions & Events Flow Sheet Not Applicable Special Organizational Considerations

8/23/2013

Page 53 of62

None Sr No 4.1 4.2 Topics Changes Management Issues None Description of Improvements As and when Customer payments are posted the account gets cleared & simultaneously the sub ledger & GL are updated online, thus keeping the books updated. Description of Functional Deficits None Approaches for covering Functional Deficit Not Applicable Topics Notes on Further Improvement Not Applicable Topics System configuration considerations Required fields in the Incoming Payment function to be configured. File conversion considerations (Master data maintenance). None Interface considerations None Reporting considerations None Authorization considerations None

4.3 4.4

Sr No 5.1

Sr No 6.1 6.2 6.3 6.4 6.5

166531223.doc

8/23/2013

Page 54 of62

166531223.doc

8/23/2013

Page 55 of62

FI0505 Account Clearing

Module Process Sub Process Sr No 1.1 Financial Accounting Accounts Receivables Processing Account Clearing

Topics Requirements & Expectations 1. Revenues FROM Sales captured through SAP , these needs to be squared off bill to bill. 2. Open & Cleared items to be displayed as & when required. Topics Existing Process General Explanation

Sr No 2.1

2.2 2.3

Explanation of Existing Functions & Events Flow Sheet Not Applicable Special Organizational Considerations Not Applicable

Sr No 3.1

Topics Proposed Process General Explanation Customer Accounts which are maintained on Open Item basis can be cleared against the corresponding payment from customer through Post with clearing function. A clearing document is created showing which transactions are cleared. Open item & Cleared item reports can be generated as and when desired. Explanation of Proposed Functions & Events Flow Sheet Not Applicable Special Organizational Considerations None
Page 56 of62

3.2 3.3
166531223.doc

8/23/2013

Sr No 4.1 4.2

Topics Changes Management Issues None Description of Improvements Sub ledger & GL are updated online. No need for any manual reconciliation. Description of Functional Deficits None Approaches for covering Functional Deficit Not Applicable Topics Notes on Further Improvement Not Applicable Topics System configuration considerations Customer Masters should be with Open item management & Line item Display. Clearing rules to be defined. File conversion considerations (Master data maintenance). None Interface considerations None Reporting considerations None Authorization considerations None

4.3 4.4

Sr No 5.1

Sr No 6.1

6.2 6.3 6.4 6.5

166531223.doc

8/23/2013

Page 57 of62

FI0506 Dunning
Module Process Sub Process Sr No 1.1 Financial Accounting Accounts Receivables Processing Dunning

Topics Requirements & Expectations 1. Generation or Reminder Letters of o/s dues. 2. Generation of Reminder Letters to send the necessary TDS Certificates. Topics Existing Process General Explanation a) A balance confirmation is obtained at the end of each quarter. b) This is an audit requirement. c) Also a reminder letter for recovery of TDS Certificates is sent to parties. Explanation of Existing Functions & Events Flow Sheet Not Applicable Special Organizational Considerations Not Applicable

Sr No 2.1

2.2 2.3

Sr No 3.1

Topics Proposed Process General Explanation The SAP System allows you to dun business partners automatically. The system duns the open items from business partner accounts in which the overdue items create a debit balance. The dunning program selects the overdue open items, determines the dunning level of the account in question, and creates a dunning notice. It then saves the dunning data determined for the items and accounts affected.

166531223.doc

8/23/2013

Page 58 of62

Accordingly various correspondence types can be used for communication purposes.

3.2 3.3 Sr No 4.1 4.2 4.3 4.4

Explanation of Proposed Functions & Events Flow Sheet Not Applicable Special Organizational Considerations None Topics Changes Management Issues None Description of Improvements None Description of Functional Deficits None Approaches for covering Functional Deficit Not Applicable Topics Notes on Further Improvement Not Applicable Topics System configuration considerations None File conversion considerations (Master data maintenance). None Interface considerations None Reporting considerations None Authorization considerations None

Sr No 5.1

Sr No 6.1 6.2 6.3 6.4 6.5

166531223.doc

8/23/2013

Page 59 of62

FI0507 Interest Calculations

Module Process Sub Process Sr No 1.1 Financial Accounting Accounts Receivables Processing Interest Calculations

Topics Requirements & Expectations 1. Interest charged on outstanding balance on customers account. Topics Existing Process General Explanation Interest charged on outstanding balance on customers account

Sr No 2.1

2.2 2.3

Explanation of Existing Functions & Events Flow Sheet Not Applicable Special Organizational Considerations Not Applicable

Sr No 3.1

Topics Proposed Process General Explanation IN SAP interest can be calculated on the balance of those G/L accounts which are managed with open item display by using the balance interest calculation function in the FI system. This function can be used in accounts receivable, accounts payable & to double-check the interest calculated on your accounts by the bank. Interest Calculation is controlled by Interest indicators which are to assigned to the Master Records of the accounts on which interest is to be calculated for.

On executing the Interest calculation run the relevant reports get updated. Accordingly a report can be generated containing the information like Interest Overview, Interest rate overview, Line items etc.
3.2
166531223.doc

Explanation of Proposed Functions & Events Flow Sheet Not Applicable

Page 60 of62

8/23/2013

3.3 Sr No 4.1 4.2

Special Organizational Considerations None Topics Changes Management Issues None Description of Improvements Interest calculation is taken care by the system wherein before posting one can view the interest calculation & then go ahead for posting. Description of Functional Deficits None Approaches for covering Functional Deficit Not Applicable Topics Notes on Further Improvement Not Applicable Topics System configuration considerations Interest Indicators should be defined for each category. Specifications like Interest Calculation frequency, key date of last int. calc etc should be mentioned in the Master Record. File conversion considerations (Master data maintenance). None Interface considerations None Reporting considerations Desired reports can be pulled from SAP. Authorization considerations None

4.3 4.4

Sr No 5.1

Sr No 6.1

6.2 6.3 6.4 6.5

166531223.doc

8/23/2013

Page 61 of62

166531223.doc

8/23/2013

Page 62 of62