SAP ERP Implementation Business Blue Print Finance

Record of Release
Version No. 1.0 2.0 2.1 Modified By Reviewed By Authorized By Release Date Modifications Done

IT CO LOGO

Business Blue Print- Finance

CLIENT LOGO

TABLE OF CONTENTS......................................................................................................................... 1 ORGANIZATION STRUCTURE...................................................................................................................7 Chart of Account...................................................................................................................................................9 Company Code......................................................................................................................................................9 Ledger 10 Fiscal year variant...............................................................................................................................................10 Posting period Variant........................................................................................................................................10 Document number range for Company Code.................................................................................................10 Document type & number range.......................................................................................................................10 Field status Group ..............................................................................................................................................10 Tolerance group for users..................................................................................................................................10 Currency...............................................................................................................................................................10 Posting Keys.........................................................................................................................................................10 2 MASTER DATA..............................................................................................................................................10 a) General Ledger Accounting ........................................................................................................................10 General Ledger master .....................................................................................................................................10 Account Group....................................................................................................................................................10 Reconciliation account .......................................................................................................................................10 Retained earning account ..................................................................................................................................10 Number Range.....................................................................................................................................................10 b) Accounts Receivable Accounting................................................................................................................10 Customer Master data .......................................................................................................................................10 Terms of payment...............................................................................................................................................10 c) Accounts payable accounting........................................................................................................................10 Maximum exchange rate difference..................................................................................................................10 Vendor Master data............................................................................................................................................10 Tax calculation procedure .................................................................................................................................10 Tax codes..............................................................................................................................................................10 Terms of payment...............................................................................................................................................10
2 of 194

Business Blue Print- Finance CLIENT LOGO d) Asset Accounting............................................................................................................................................10
IT CO LOGO

Chart of Depreciation .......................................................................................................................................10 Asset Class............................................................................................................................................................10 Asset Master........................................................................................................................................................10 Asset sub number...............................................................................................................................................10 Depreciation Key.................................................................................................................................................10 e) Bank Accounting............................................................................................................................................10 3 BUSINESS PROCESS.....................................................................................................................................12 GENERAL LEDGER ACCOUNTING...........................................................................................................12 3.1.1 Cash Transactions......................................................................................................................................12 3.1.2 Bank Receipt...............................................................................................................................................14 3.1.3 Funds Transfer...........................................................................................................................................19 3.1.4 Dishonor of Instruments...........................................................................................................................21 3.1.5 Bank payment ............................................................................................................................................23 3.1.6 Electronic Payments..................................................................................................................................25 3.1.7 Demand Draft/ Pay order.........................................................................................................................27 3.1.8 Reversal Entries.........................................................................................................................................29 3.1.9 Bank Reconciliation Statements...............................................................................................................31 3.1.10 Bank Deposits...........................................................................................................................................34 3.1.11 Term Loans / Cash Credit......................................................................................................................36 3.1.12 Journal Entries – Intra Branch..............................................................................................................38 3.1.13 Journal Entries-Inter Branch.................................................................................................................40 3.1.14 Taxes-Excise............................................................................................................................................42 3.1.15 Taxes-Sales Tax........................................................................................................................................47 3.1.18 Taxes-TDS.................................................................................................................................................51 3.1.19 Tax Deducted at Source (Asset).............................................................................................................55 3.1.22 Job Work Accounting..............................................................................................................................57 3.1.24 Stock Transfer-Raw Material................................................................................................................59 3.1.25 Stock Transfer-Finished Good...............................................................................................................61 3.1.26 Accruals.....................................................................................................................................................63
3 of 194

..........41 Cash Flow Statement............................................................................................................................................................2...........1..................2.................44 RBI Return for Foreign Investments.................................Finance CLIENT LOGO 3............1..............................................................................79 3.......87 3.........................117 3................47 Sample documents.............121 3.104 3......97 3.............................45 Transactions with Associated Concerns........................................Obsolete / Damaged Stock..111 3...............................................................2..........................................2 Receipts against Credit Supplies...1......................................................81 3.....................................42 Payroll...........35 Stock Valuation ...........................1..........67 3.................38 Stock Valuation .............108 3..............................................4 Bill Discounting (BOE).............................................................................115 3............................1.........Business Blue Print..................................................................................................75 3................................1.....83 3.......................................................77 3.................37 Stock Valuation ...................................36 Stock Valuation ......................95 3.........85 3.................................................................48 GL document parking & posting...............................99 3.............1 Advance Receipts.................................................89 3..................... 000.......1...............29 Technical Fee...............2..................................Raw Material/Packing Material/Fuels & Lubricants...................................................................................................................1...................................................................2..............................................................................................................................1.............................40 Excise Differential (RTP) XYZ LIMITED.............................................................................................91 3........69 3.............................................................................................................1..............1.....51 Clear GL accounts ......1.......................................20......34 Valuation ....46 Security Deposits Received or Paid in excess of Rs..............................................................................33 Proof Sheets............................................................119 3.....................................108 3...............................................................................................1........................................................................................................................50 Valuation of Foreign Currency item.........................6 Interest on Delayed Payments.................2.......................101 3........................................................2..................124 3....................................................................................................3 Bank Guarantee / Letter of Credit for Credit Supplies..........1...................73 3................1......................................1....2..............................................................Finished Goods........................................................................................93 3.................49 Document Split functionality....................................................................................................................................71 3.............................................31 Marketing Compensation.......Stock in Transit.........................................65 IT CO LOGO 3....................1........1................1..........32 Prepaid expenses........................................43 Issue of Bank Guarantee.................................................................................1............................................8 Sales Returns......126 4 of 194 ...1..Depot Stocks........106 ACCOUNTS RECEIVABLE:-........5 Inter Branch Receipt Accounting......7 Debit & Credit Notes............

............184 3.................................2 Depreciation Accounting...............................................3........................................................................................8 Purchase Bill Processing – Imports....................................................................................................189 3.........................................3...............................................................139 3......................141 3...............................................4 Disposal of Assets...........................3............................180 3......16 GR/IR account maintenance..9 Bad Debts & Provisions.........169 3........132 3.....3...............................................................................................173 3...........................15 Credit Memo/Note with Purchase Order......3.........................3......................................................................................10 Exchange Fluctuations ......................................................3........................................................171 ASSET ACCOUNTING..130 ACCOUNTS PAYABLE.................................2...............4 Letter of Credit..............................3..........13 Customer Invoice document holding & posting....................14 Invoice processing without Purchase order.........................................................3......................Business Blue Print..................................................................................2....................161 3.......12 Service Vendor Payments:-.....................3 Transfer of Assets..........3............2 Year End Process – CY...................................................182 3.......5 Physical Verification of Assets.....3.................................192 5 of 194 ................5 Month End Process....................................................................3..............................................................................................158 3..................................................189 3....................................................................................1 Year End Process – FY........132 3...5 Payment against Document...13 Capital Vendor Payments.......................................18 Vendor Invoice document holding & posting......................Capital / Revenue..........................................................................................................................................................................................................143 3...................................Finance CLIENT LOGO 3............................................................................................3.........................4........................................................................4..........................................17 Bill of Exchange..........11 Payment of Duty on Imports........................................3..................................................186 YEAR END PROCESS..............................................................................7 Inter Office Payments................................1 Purchase of Material Bill Processing.......................4.....................................................................173 3.....................................3..............................150 3..................................6............................................................................................................................135 3......................................................................128 IT CO LOGO 3..............9 Payment processing– Imports after credit period...............................................................................146 3............................................177 3...............................155 3.............2 Payment Process.................6..167 3.....1 Acquisition Process...................................................................................................................163 3.....................165 3...........3 Bank Guarantee from Vendors................................................................................................3............4....................148 3..........................................................................................................................................4.........3.......................152 3...............................................................................

IT CO LOGO Business Blue Print.Finance CLIENT LOGO 6 of 194 .

The company code created in Finance will be assigned to controlling area. That means all the transactions taking place in the plants are posted to the attached company code in FI. The sales organization created in SD module will be attached to company code.IT CO LOGO Blue Print Document –Finance CLIENT LOGO 1 Organization structure Attached below is the Organization structure:- System Configuration Considerations The controlling area created in controlling module will be assigned to operating concern. The purchasing organization created in MM module will be attached to company code. 5. 2. 3. 7 of 194 . 1. 4. The plants created in material management module will be assigned to company code.

IT CO LOGO Blue Print Document –Finance CLIENT LOGO 8 of 194 .

IT CO LOGO

Blue Print Document –Finance

CLIENT LOGO

Chart of Account
Chart of account serves the following two purposes:1. Permits recording of transactions to the level of detail required by business. 2. Preparation of Balance sheet & Profit and loss statement in compliance with the statutory regulations. One Chart of Account will be created for BPE. Below values will be defined while configuring Chart of Account: Field Chart of Account Description Maint. Language Length of GL account Controlling integration Name BPE BPE Chart of Account English 6 (Numeric) Manual creation of Cost element

Cost element can be created in SAP in two ways:1. Automatic creation of cost element:-Whenever a GL account is created, cost element will be created automatically in the background. 2. Manual creation of Cost element:-Once GL account is created, cost element will be created manually through a separate process. For BPE, Cost element will be created manually, to have control over creation of cost element.

Company Code
Company code is the basic organizational unit in SAP FI for which the balance sheet and profit & loss can be drawn from the legal requirement point of view. One Company code will be created for BPE.

9 of 194

IT CO LOGO

Blue Print Document –Finance

CLIENT LOGO

Below values will be defined while configuring Company code: Field Company Code Company Name City Country Currency Language Address Value BPE Bull Power Electronics Limited Mumbai India INR English

Company code created will be assigned to the Chart of Account created in above step.

Ledger
Ledger Concept: 1. Possible to perform parallel accounting for different accounting principles 2. Separate ledgers can be defined for the different accounting principles 3. Documents can be posted in these ledgers or group of ledgers to fulfill the accounting requirement 4. All company codes are assigned to a leading ledger ‘0L’ for each client. Only one leading ledger for each client. 5. Only values from leading ledger are posted to CO New GL accounting will be implemented for BPE. Below mentioned Ledger will be created for BPE:Ledger 0L H1 L1 U1 I1 Description Leading Ledger Colas reporting ledger Local GAP Ledger US GAP Ledger IFRS Ledger

Accounting for the BPE financial year April to March will be done through Leading ledger 0L and non leading ledger H1 will be used for reporting as per the Colas, France financial year January to December. Fiscal year variant V3 (April to March) will be assigned to leading ledger 0L, and non leading ledgers except H1. Fiscal year variant K4 (Jan to Dec) will be assigned to the non leading ledger H1. Above Ledgers are created to report according to different accounting principle requirements. Ledger 0L is the leading ledger. Ledger L1 is the non leading Ledger which represents the Local GAP reporting requirements. All the Finance postings in the Leading ledger 0L will flow automatically to all the other non leading ledgers. Posting specifically made to any of the non leading ledger to adhere to the respective accounting principle requirements will not flow to any of the other ledger.
10 of 194

IT CO LOGO

Blue Print Document –Finance

CLIENT LOGO

11 of 194

.1 Flow Chart of Business Process : Submodule GL. identification of payments in excess of Rs. of AS-IS document 3.1 Ref. ………. No of To-BE document 3.1.Dr Bank A/c.1.15000/. 15000/-. Process Step FB01 / FB50 Explanation. variations and exceptions Enter G/L account document Potential Gaps: None Potential Gap Resolution: None 12 of 194 . Detailed Process Description. Also at the month end the expenses will be booked in to the system.…. 20000/. Controlling of cheque isuue more then Rs. No.Cash Transactions Date : General Requirements/Expectations Description Cash withdrawal from bank for the day to day utilization purposes is not accounted directly in to the books of accounts. Through identified voucher series. the filter “>20000” will be put in the amount field of respective GL line item report. Process Variations and Exceptions Once the expense voucher accumulates to Rs. As a year end activity imprest will be grouped to cash in Hand.1 Cash Transactions Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr. the expenditure will be booked in to the system.1. Following Journal entry (Document type SA) will be passed for booking of such expenses:Expense A/c ………… .IT CO LOGO Blue Print Document –Finance CLIENT LOGO 3 Business Process General Ledger Accounting 3. The cash withdrawal is treated as Cash imprest in the hand of Assistant commercial Plant.…Cr If the Cheque is to be printed from SAP.1 Cash transactions Name of Business Process : General Ledger Accounting Module Finance Version no of document: 2.……. then this transaction will be routed through Vendor account.can be done through setting the tolerance limit for the user. Sr.

IT CO LOGO Blue Print Document –Finance CLIENT LOGO System Configuration Considerations None Reports required related to business process Report for all such expenses can be withdrawn using the transaction code FBL3N or FS10N.Conversion Requirements None Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements None Business Benefits Even without maintaining the cash register separately. Outputs required for this business process Expenses Vouchers can be printed through SAP Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No User Roles and Authorizations Cash expenses transaction booking authorisation will be given to only limited set of users. Unit Signature 13 of 194 . Sign-off (Approval) for this document : Name of Team member Organisation/Bus. Reports None Technical Considerations . the cash expenses will be accounted in a proper way. Technical Considerations – Forms.

.…Cr In case the detail is not available along with the receipt. DD etc.2.2 Ref. Following entries will be passed on receipt of payment from Customer using the transaction code F-28 (post incoming payments):Bank clearing (receipt) account ………… …. ……………………… ….1 & 3. Receipt from customer against credit supplies will be cleared against the customer open invoices.Dr Bank Clearing (receipt) Account.1.…….Bank Receipt Date : General Requirements/Expectations Description All the bank transactions (Incoming & Outgoing) should be accounted in SAP. that payment is received against which Invoice. Process Variations and Exceptions Advance receipt from customer will be entered in to SAP using special GL indicator. Bank Clearing (receipt) Account……………………… ………Dr Customer A/c (with special G/L)………………. The Customer ledger will show the detail of the receipt document along with the reference of the Invoice against which the payment is received. the below mentioned entry will be passed:Bank A/c………………. No. If the bank upload functionality explained below is not used then on receipt of the bank statement. then open item of the customer will be cleared on FIFO basis.2. It will also show the mode of payment like Cheque. The detailed procedure for accounting of incoming payment has been explained in detailed in section 3.……… ………Cr Advance received from customer will be entered in SAP along with the special GL indicator with a separate reconciliation account.2.1.2 Bank Receipt Name of Business Process : General Ledger Accounting Module Finance Version no of document: 2.Dr Customer A/c………………… ……….1. No of To-BE document 3. ………… ….1 Flow Chart of Business Process : Submodule GL.IT CO LOGO Blue Print Document –Finance CLIENT LOGO 3.2 Bank Receipt Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr. Sr.Cr 14 of 194 . of AS-IS document 3.. Detailed Process Description.

The cheques in transit from depots will be considered as cheques in hand and will be accounted into the system. actual posting will be done manually for the payment received.………………. Following entry will be passed:Bank.Cheques will be posted into the system immediately on the receipt of the cheque.IT CO LOGO Blue Print Document –Finance CLIENT LOGO Receipt like EMD for tenders will be handled in SAP with the help of special GL indicator. credit will be given to customer through below mentioned entry:Bank Clearing (receipt) Account……………………… ………Dr Customer A/c …………………. below mentioned entry will be passed:Bank A/c………………. On due date. During BDS generation. below mentioned entry will be passed:- 15 of 194 . upon receipt of credit for the same.… …. Post date cheques can be eneterd in the below mentioned two ways in to the system: 1. ………… ….. A/c………. receipt accounting will be done as follows:Bank Clearing (receipt) Account……………………… ………Dr Customer A/c …………………. a statistical entry will be passed. upon receipt of credit for the same. This will ensure factual credit position of the customer as well as MIS reporting.………………. ………… …..Cr Once the cheque is deposited in to the bank on the due date.. the cheques in hand which are not deposited in to the bank. During period closures.…………..Dr Customer A/c…………… ………Cr If the post dated cheque is received from the customer. 2.Actual credit to the customer immediately after receipt of the cheque:If the post dated cheque is received from the customer. The document date will be entered as cheque date with the posting date as the current date. On the due date bank deposit slip will be generated by the system automatically (through development). will be accounted and the credit will be given to the Customer. An option will be provided in the bank deposit slip report to display the exclusion list..Cr Once the cheque is deposited in to the bank on the due date..……… ………Cr If the payment receipt entry is passed wrongly. If the customer deposit the amount in to bank directly. ………… …. in that case the amount deposited will be credited to customer account on receipt of the bank statement.Dr Bank Clearing (receipt) Account. those cheques will be excluded from the Bank deposit slip by selecting the same.Posting as statistical entry:. that entry will be reversed through transaction code FB08.

. For this a format will be provided to the bank. For depositing the cheques received from customer.. Bank statement will be uploaded in to SAP using the transaction code FF_5.……………. Bank clearing account is maintained as open item managed account. if previous period is open. At the month end. variations and exceptions Import Bank Statement Enter G/L account document Post Incoming payments Reverse document Reset items Cheque register Manual bank statement entry Manual check deposit Potential Gaps: 1. Below mentioned entry will be passed by the system automatically on upload of the Bank statement :Bank A/c………………. 3. ……………………. those Invoices & Cheques can be entered in the previous period. 2. The above mentioned entry will automatically clear the respective open entry passed at the time of accounting the receipt of the cheque from the Bank (Entry is mentioned below again for ready reference):Bank Clearing (receipt) Account……………………… ………Dr Customer A/c ………………….….Cr All the Cheques and Invoices received from the depot will be accounted at the respective parent locations. Bank will send the bank statement through the agreed media like through E-mail. If the item is already cleared then it will be reset using FBRA. ………… …. Bank statement upload functionality:For uploading the bank statement in to SAP.Dr Bank Clearing (receipt) Account..Dr Bank Clearing (receipt) Account.……… ………Cr The original entry and the reversal entry will be knocked off through open item clearing functionality..……… ………Cr The above entry will have the reference of the Cheque number.IT CO LOGO Blue Print Document –Finance CLIENT LOGO Bank A/c………………. ………… …. on the due date the bank deposit slip is not printed automatically 16 of 194 . Process Step FF_5 FB01 F-28 FB08 FBRA FCHN FF67 FF68 Explanation. System does not provide a report for the number of days for delayed credit by considering the difference of date of deposit and actual clearing date... the bank has to provide the bank statement in the SAP acceptable format. In case of Post dates cheques. …. there is no standard advice slip available in the SAP.

2. System Configuration Considerations 1. Bank deposit slip report will be created in SAP. Technical Considerations – Forms. Configuration for uploading the bank statement in to SAP. 3. 2. A new report will be developed to provide a report for the number of days for delayed credit by considering the difference of Date of Deposit and actual clearing date. FBL1N-Vendor line item report 5. 2. Reports None Technical Considerations . Cheque register. Reports required related to business process 1. FS10N-GL balance summary 4. Functionality will be developed to generate the bank deposit slip automatically on the due date for the post dated cheques along with the option of exclusions for in transit receipts accounted. ( if any ) : User Roles and Authorizations Bank transaction posting authorisation will be given to limited set of users only.Conversion Requirements None Technical Considerations – Interface Requirements None 17 of 194 . Describe in details and attach the format in which data would be stored in the other system : Output from this business process sent to other functions. Reason code configuration for reversing the documents. FBL5N-Customer line item report Outputs required for this business process None Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No If Yes. FBL3N-GL line item report 3.It can be generated using the transaction code FCHN.IT CO LOGO Blue Print Document –Finance CLIENT LOGO Potential Gap Resolution: 1.

Once all the clearing items are cleared. balance as per SAP matches with the bank statement.IT CO LOGO Blue Print Document –Finance CLIENT LOGO Technical Considerations – Enhancements None Technical Considerations – Workflow requirements None Business Benefits Bank transactions will be posted in SAP regularly. Sign-off (Approval) for this document : Name of Team member Organisation/Bus. Unit Signature 18 of 194 . This way there will be better control over the funds.

. Sr.Dr Bank Clearing A/c……………. reconciliation will be done by the Chennai Plant and below mentioned entry will be passed manually:SBI Bank Mumbai Chennai A c..………. below entry will be passed by the system automatically:SBI Bank Mumbai (HO) A/c. No of To-BE document 3.3 Funds Transfer Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr. variations and exceptions Bank Statement upload Enter GL account document 19 of 194 ..……….1. Once the bank statement is uploaded by the Chennai Plant.1.1.. Process Variations and Exceptions For example. No.…. of AS-IS document 3.Cr On receipt of the bank statement.5 FB01/FB50 Explanation. Detailed Process Description.Dr SBI Bank Chennai A/c.Dr Bank Clearing A/c……………. SBI bank account of Chennai is having surplus fund. reconciliation will be done by the Mumbai HO and below mentioned entry will be passed manually:Bank Clearing A/c……………...….Dr SBI Bank Mumbai (HO) A/c.Cr On receipt of the bank statement. Bank will transfer the surplus fund from Chennai branch to HO branch Mumbai.1 Flow Chart of Business Process : Submodule GL.IT CO LOGO Blue Print Document –Finance CLIENT LOGO 3.Cr Once the bank statement is uploaded by the Mumbai HO .Cr Process Step FF.3 Ref. below entry will be passed by the system automatically:Bank Clearing A/c…………….3 Funds Transfer Name of Business Process : General Ledger Accounting Module: Finance Version no of document: 2...Funds Transfer Date : General Requirements/Expectations Description On the basis of arrangement with the bank surplus balances are transferred at the end of the day to the main accounts at Mumbai (Pooling accounts) and vice versa for effective utilisation of funds.

Technical Considerations – Forms. Reports None Technical Considerations .IT CO LOGO Blue Print Document –Finance CLIENT LOGO Potential Gaps: None Potential Gap Resolution: None System Configuration Considerations None Reports required related to business process Using the SAP standard transaction code the account balance can be viewed at any point of time. Sign-off (Approval) for this document : Name of Team member Organisation/Bus.Conversion Requirements None Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements None Business Benefits We will have better control & utilisation on Inter branch fund transfer. Unit Signature 20 of 194 . FBL3N-GL line item report FS10N-GL balance summary FBL1N-Vendor line item report FBL5N-Customer line item report Outputs required for this business process None Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No User Roles and Authorizations Document posting authorisation will be given to limited set of users only.

Dishonor of Instruments Version no of document: 2. first those items will be reset using transaction code FBRA and incoming payment entry will be reversed:Customer A/c……………………………………. the appropriate accounting entries should be passed for the reversal.. Customer A/c…………………. Process Step FB08 FBRA FB01 / FB50 Explanation. Sr.IT CO LOGO Blue Print Document –Finance CLIENT LOGO 3.1..1 Date : Flow Chart of Business Process : General Requirements/Expectations Description The bank gives credit for the DD/Cheques deposited into the bank on the Day 1 as per the CMS arrangement irrespective of the instrument being cleared.………..Dr Bank Clearing A/c……………… ……………….….1.1. No.4 Dishonor of Instruments Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr.………….Cr Reversal reason codes are to be assigned for reversal of the incoming payment entry.Cr A report on dishonur of Instruments can be derived from the SAP system through transaction code FBL5N by putting the reversal reason code in the selection criteria.4 Dishonor of Instruments Name of Business Process : General Ledger Accounting Module Finance Submodule GL. In SAP first those bank charges will be booked as expenses after receipt of the bank statement by passing the below mentioned Journal voucher:Bank charges A/c…………………. Detailed Process Description. No of To-BE document 3..Dr Bank charges A/c.Cr A separate debit note will be raised manually to customer for the bank charges debited by bank for dishonor of the instrument using the transaction code FB70. of AS-IS document 3.Dr Bank A/c……………… ……………….4 Ref. Customer blocking and change of payment terms from Cheque to DD will be done at the sales area level manually. Process Variations and Exceptions If the open invoices has already been cleared and the cheque is dishonoured.…… …………………. If the instrument is dishonored. variations and exceptions Reverse Document Reset cleared item Enter GL account document 21 of 194 .

Reports required related to business process Using the SAP standard transaction code the account balance can be viewed at any point of time. Reports None Technical Considerations . System Configuration Considerations Reversal reason codes will be configured in SAP. FBL3N-GL line item report FS10N-GL balance summary FBL5N-Customer line item report Outputs required for this business process None Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No User Roles and Authorizations Document reversal authorisation will be provided to limited set of users only. Potential Gap Resolution: Through enhancement dishonored cheques will be attached to the document as part of correspondence. Technical Considerations – Forms.IT CO LOGO Blue Print Document –Finance Customer Line item report CLIENT LOGO FBL5N Potential Gaps: Dishonored cheques are not attached to the document as part of correspondence in standard SAP. Sign-off (Approval) for this document : Name of Team member M Harikrishna Organisation/Bus.Conversion Requirements None Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements None Business Benefits Dishonoured instrument can be accounted for and tracked in SAP. Unit Bull Power Limited Electronics Signature 22 of 194 .

Sr. Tel & Fax. Detailed Process Description. Detail of the cheque lot received from the bank will be updated in to the system. Rent. code FCH3) 2. Telephone Deposits.5 Bank payment Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr.1. Page overflow 2. Cheques issued along with the list of the Void cheques leaving the balance cheques list as stock in hand. Printing & Stationery. Balance cheques in hand information would be available through T. Appropriate accounting entry is to be passed for such payments (non vendor). Below mentioned are the some of the SAP standard Void reason code:1.5 Bank payment (Non Vendor) Name of Business Process : General Ledger Accounting Module : Finance Version no of document: 2. Customs. No of To-BE document 3. code FCH9) 3. Travel Expenses. Ripped during printing 3.3.Bank payment (Non Vendor) Date : General Requirements/Expectations Description The bank payments for non vendor based (Expenses like Electricity. Cheque Void functionality is also provided by SAP. Statutory dues.Code FCHI. Salaries etc) are processed from HO & plant locations respectively. Payment for such type of payment can be done either through automatic payment run or through manual payment. Cancel Payment (T.5 Ref. Trainings.IT CO LOGO Blue Print Document –Finance CLIENT LOGO 3. Issued cheques can be void at the below mentioned three stages:1. Issued Cheque (T.code FCH8) Void reason codes have to be given at the time of voiding the Cheque.2 for Vendor Payment process. If payment is done manually then cheque series has to be manually updated in SAP. Cheque register shows the list of all the cheques received from Bank. Printed incorrectly 23 of 194 . Unused Cheque (T. Cheque register can be generated using the T. Subscriptions. Please refer section 3.1.code FCHN. Other Deposits. Process Variations and Exceptions Separate vendor code will be created for the above mentioned transactions. Electricity Deposits. No. Staff welfare. of AS-IS document 3.1 Flow Chart of Business Process : Submodule GL.1.

Reports required related to business process FBL3N-GL line item report FS10N-GL balance summary Outputs required for this business process None Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No User Roles and Authorizations Bank related transaction posting authorisation will be given to limited set of users only.IT CO LOGO Blue Print Document –Finance CLIENT LOGO 4. Reports None Technical Considerations . Technical Considerations – Forms. Sign-off (Approval) for this document : Name of Team member Organisation/Bus. variations and exceptions Post outgoing payments Manual check creation Display cheque information Automatic Payment Run Potential Gaps: None Potential Gap Resolution: None System Configuration Considerations Appropriate G/L accounts to be defined for booking such expenses (non vendor) to appropriate heads. Unit Signature 24 of 194 . Destroyed/Unusable 5.Conversion Requirements None Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements None Business Benefits Non vendor expenses can be booked separately than the vendor transactions. Stolen Process Step F-07 FCH5 FCH1 F110 Explanation.

....1. Process Variations and Exceptions A new document type will be created for such type of payments.IT CO LOGO Blue Print Document –Finance Bull Power Limited Electronics CLIENT LOGO M Harikrishna 3......Cr...6 Electronic Payments Name of Business Process : General Ledger Accounting Module Finance Version no of document: 2............ Following entry will be passed on the TDS payment :TDS payable A/c……………………...... No of To-BE document 3. Cr..1..........6 Electronic Payments Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr. Bank A/c. Sr.1.5 and then through Internet the payment will be done. No.. the below mentioned entry will be passed by the system automatically:Bank clearing A/c………………………………….. For example below mentioned payment document will be generated on deposit in to PLA account:PLA on Hold A/c…………………….. First the payment document will be created in SAP as per the process explained in the section 3............ Bank clearing A/c…………………………………... Dr.. 25 of 194 ...... If bank upload functionality is used....1.. the below mentioned entry will be passed by the system automatically:Bank clearing A/c……………………….Dr.......... Cr..……………Dr. If bank upload functionality is used..... Bank clearing A/c…………………………………....... Such payments are made by the personnel who are authorized to logon to the Internet Banking facility and make the payment as per the due dates.. of AS-IS document 3....……………Dr.... Bank A/c..... Detailed Process Description....................... TDS liabilities of the individual manufacturing locations is paid to the credit of tax department by E-payment......…………. If the bank statement upload functionality is not used... then the above entry will be passed manually. Cr...6 Ref.....1 Flow Chart of Business Process : Submodule GL........Electronic Payments Date : General Requirements/Expectations Description The Excise liability.

all the E payments can be identified in the system separately.IT CO LOGO Blue Print Document –Finance CLIENT LOGO If the bank statement upload functionality is not used. Process Step FB01/FB50 F-07 Explanation. variations and exceptions Enter G/L account document Post outgoing payments Potential Gaps: None Potential Gap Resolution: None System Configuration Considerations A new document type will be created in SAP for Electronic payments. Technical Considerations – Forms. Sign-off (Approval) for this document : Name of Team member Organisation/Bus. then the above entry will be passed manually. Reports None Technical Considerations . Reports required related to business process FBL3N-GL line item report FS10N-GL balance summary Outputs required for this business process None Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No User Roles and Authorizations Bank transaction posting authorisation will be given to limited set of users. Unit Signature 26 of 194 .Conversion Requirements None Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements None Business Benefits Through separate document type.

.1..........7 Demand Draft/ Pay order Name of Business Process : General Ledger Accounting Module Finance Version no of document: 2. Cr If bank upload functionality is used.. 27 of 194 .. Bank A/c. variations and exceptions Post outgoing payment Enter G/L account document Potential Gaps: Generation of Bank wise serially numbered DD/Pay order requests through system is required....... Expenses/Vendor A/c…………………. Process Variations and Exceptions The expenses will be accounted for in the system as explained in section 3. No of To-BE document 3......1...…Dr Bank clearing A/c…………………. of AS-IS document 3.. Sr. then the above entry will be passed manually. No.IT CO LOGO Blue Print Document –Finance Bull Power Limited Electronics CLIENT LOGO M Harikrishna 3.1.... The DD/pay order number can be updated into the system on receipt of the details through document change option.. the below mentioned entry will be passed by the system automatically:Bank clearing A/c…………………………………............ If the bank statement upload functionality is not used....……..5.....1......7 Demand Draft/ Pay order Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr.Dr..Demand Draft/ Pay order Date : General Requirements/Expectations Description Certain payments of statutory nature are to be paid by way of DD/Pay Order...7 Ref. Standard SAP does not provide this request form.. Bank charges for issuance of Demand Draft/Pay order will be accounted in the system on the basis of the Bank statement....1 Flow Chart of Business Process : Submodule GL. Process Step F-07 FB01/FB50 Explanation. An advice in writing is provided to the bank signed by the authorized signatories requesting for the preparation of DD/Pay Order... The Bank is also authorized to debit the bank charges applicable directly to the current account. Detailed Process Description.. Cr....

System Configuration Considerations None Reports required related to business process FBL3N-GL line item report FS10N-GL balance summary Outputs required for this business process None User Roles and Authorizations Transaction posting authorisation will be given to limited set of users. Sign-off (Approval) for this document : Name of Team member M Harikrishna Organisation/Bus.IT CO LOGO Blue Print Document –Finance CLIENT LOGO Potential Gap Resolution: Bankwise serially numbered DD/Pay order request form will be created in SAP. Reports None Technical Considerations . Unit Bull Power Limited Electronics Signature 28 of 194 .Conversion Requirements None Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements None Business Benefits Accounting will be done in SAP in proper way. Technical Considerations – Forms.

The reversal document will have the original document number in the reference field.1.8 Ref. a reversal entry should be passed in SAP. variations and exceptions Transaction code for Reversing documents 29 of 194 .……Dr Travel Expenses A/c……………. the below mentioned will be the reversal document (document number 100328):Expenses accrued A/c………………. The reversal reason is to be mentioned in the reversal document.. No.1. No of To-BE document 3. Both such entries are cleared by the SAP if the accounts are open item managed account.. Detailed Process Description. if the payment voucher is wrongly prepared for the wrong amount or any other reason.1 Flow Chart of Business Process : Submodule GL.. Process Variations and Exceptions If the document to be reversed is already cleared against any other document.8 Reversal Entries Name of Business Process : General Ledger Accounting Module Finance Version no of document: 2. then first that clearing document is reset using the transaction code FBRA. For example. below mentioned is the original document (document number 100020):Travel Expenses A/c………………. Process Step FB08 Explanation.. Similarly the reversal document number 100328 will be stored automatically in the original document number 100020. Sr. Cr Once the above document is reversed using the transaction code FB08.1. ……. Cr The original document number 100020 will be stored automatically in the reversal document number 100328 in the reference field. of AS-IS document 3.IT CO LOGO Blue Print Document –Finance CLIENT LOGO 3. Also the original will also be updated automatically with the reversal document in the reference field.8 Reversal Entries Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr. Debit and credit entry in original document will be reversed by passing the credit and debit entry in the reversal document.Reversal Entries Date : General Requirements/Expectations Description Due to any reason.………Dr Expensed accrued A/c…………………….

Reports required related to business process FBL3N-GL line item report FS10N-GL balance summary Outputs required for this business process None Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No If Yes.Conversion Requirements None 30 of 194 . Describe in details and attach the format in which data would be stored in the other system : Inputs/ data received from other function for this process. ( if any ) : User Roles and Authorizations Reversal transaction posting authorisation will be given to limited set of users.IT CO LOGO Blue Print Document –Finance Reset cleared items CLIENT LOGO FBRA Potential Gaps: None Potential Gap Resolution: None System Configuration Considerations Reversal reasons are to be configured in SAP which defines the reason for the reversal of the document. Technical Considerations – Forms. Reports None Technical Considerations . ( if any ) : Output from this business process sent to other functions.

Sr. Sign-off (Approval) for this document : Name of Team member M Harikrishna Organisation/Bus. No.IT CO LOGO Blue Print Document –Finance CLIENT LOGO Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements None Business Benefits Reversal transaction will always have the track of the original transaction and vice versa. The process is done by obtaining a Bank Statement (soft copies as well as hard copies) on regular intervals from the respective Banks.1.9 Bank Reconciliation Statements Name of Business Process : General Ledger Accounting Module Finance Version no of document: 2. Unit Bull Power Limited Electronics Signature 3.1.9 Ref. No of To-BE document 3.1 Flow Chart of Business Process : Submodule Statements GL- Bank Reconciliation Date : General Requirements/Expectations Description The bank reconciliation is done by the Commercial Officer for all the banks that are attached to their respective HO & Plant locations. 31 of 194 .9 Bank Reconciliation Statements Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr.1. of AS-IS document 3.

Process Variations and Exceptions Bank account in SAP will be reconciled with the bank statement received from bank. ………… ….………………. The above mentioned entry will automatically clear the respective open entry.Dr Unclaimed cheques A/c…. variations and exceptions Post incoming payments Post outgoing payments Enter G/L account document Potential Gaps: 1. than those cheque payment entries are reversed manually. Bank clearing account is maintained as open item managed account. the bank has to provide the bank statement in the SAP acceptable format.……… ………Cr The above entry will have the reference of the Cheque number. For uploading the bank statement in to SAP. Below mentioned entry will be passed by the system automatically on upload of the Bank statement :Bank A/c………………. Potential Gap Resolution: 1. passed at the time of accounting the receipt of the cheque from the Bank (Entry is mentioned below for ready reference):Bank Clearing (receipt) Account……………………… ………Dr Customer A/c ………………….IT CO LOGO Blue Print Document –Finance CLIENT LOGO Detailed Process Description. The accounting document generated is:Bank clearing A/c………………………….. Incoming payment clearing & Outgoing payment clearing account will be cleared manually with main account on the basis of the bank statement. For this a format will be provided to the bank.In SAP three bank GL accounts will be configured :32 of 194 . ………… ………………Dr Bank Clearing (receipt) Account. Bank charges not accounted in the SAP as per the bank statement will be accounted for in SAP. .…. ………………. Bank will send the statement on the daily basis in the required format through the media agreed with the Bank for example through E-mail.Cr If some of the cheque issued to Vendor are not presented for clearing by Vendor for a very long period of time. No functionality is available in SAP for preparing the bank reconciliation statement directly from the system in the traditional format. No SAP standard report is available to provide a list of instruments of stale nature pending clearance over 6 months for deposits both for payment & deposits. 2.. Bank statement can be uploaded in to SAP using the transaction code FF_5... Cr Process Step F-32 F-53 FB01/FB50 Explanation.. An interface will be developed with the bank for receiving the bank statement.

Reports required related to business process FBL3N-GL line item report FS10N-GL balance summary Outputs required for this business process None Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No If Yes. 33 of 194 . Incoming payment clearing account 3. Outgoing payment clearing account. Main Bank Account 2. Technical Considerations – Forms.IT CO LOGO Blue Print Document –Finance CLIENT LOGO 1. a new report can be developed to provide the bank reconciliation in the traditional (Legacy) format. Also. Reports None Technical Considerations . System Configuration Considerations Configuration of three accounts mentioned above. A new report will be developed to provide a list of instruments of stale nature pending clearance over 6 months for deposits both for payment & deposits. ( if any ) : User Roles and Authorizations Transaction posting authorisation will be given to limited set of users.Conversion Requirements None Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements None Business Benefits Bank reconciliation statement can be prepared through SAP using the three accounts mentioned above. Describe in details and attach the format in which data would be stored in the other system : Inputs/ data received from other function for this process. Bank reconciliation statement can be prepared by combining the above mentioned three accounts. 2. ( if any ) : Output from this business process sent to other functions.

of AS-IS document 3.10 Bank Deposits Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr.1.1.Bank Deposits Date : General Requirements/Expectations Description The surplus fund lying in the bank would be converted to Fixed deposit for specific period after approval from authorities.10 Bank Deposits Name of Business Process : General Ledger Accounting Module: Finance Version no of document: 2. Unit Bull Power Limited Electronics Signature 3. No of To-BE document 3. 34 of 194 .10 Ref.1 Flow Chart of Business Process : Submodule GL.IT CO LOGO Blue Print Document –Finance CLIENT LOGO Sign-off (Approval) for this document : Name of Team member M Harikrishna Organisation/Bus. No. Sr.1.

( if any ) : User Roles and Authorizations Bank related transaction posting authorisation will be given to limited set of users. The interest calculation will be done through the system only for the statistical purposes. 35 of 194 . Describe in details and attach the format in which data would be stored in the other system : Inputs/ data received from other function for this process.IT CO LOGO Blue Print Document –Finance CLIENT LOGO Detailed Process Description. Process Step FB01/FB50 FF_1 Explanation.Dr Interest Received A/c ………………….. Custodian. then separate term deposit accounts needs to be created for each of the term deposit.Dr Bank A/c …………………Cr The detail entered in to the system (like Bank name. Validity) at the time of passing the entry can be get from the system using the line item report (Transaction code FBL5N). ( if any ) : Output from this business process sent to other functions. Rate of interest will be defined for the each of the term deposit..Cr If the interest calculation is to be done through system.. Actual interest received will be accounted as Income in SAP as follows:Bank A/c …………………………………Dr TDS receivable A/c……………………. The Fixed Deposit will be accounted as follows:Term Deposit A/c ………. variations and exceptions Enter GL account document Interest Calculation on GL account Potential Gaps: None Potential Gap Resolution: None System Configuration Considerations None Reports required related to business process None Outputs required for this business process None Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No If Yes. Process Variations and Exceptions Separate term deposit GL accounts (Balance sheet type) will be created in SAP for each of the Bank.

1.IT CO LOGO Blue Print Document –Finance CLIENT LOGO Technical Considerations – Forms.1 Date : Flow Chart of Business Process : General Requirements/Expectations Description Term Loans are taken from Banks for funding Capital and Other commitments against security of Stocks and Plant. No.1. Sr. No of To-BE document 3.11 Term Loans / Cash Credit Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr. Reports None Technical Considerations . Proper accounting is to be done in SAP for the Term loan & interest thereon.11 Term Loans / Cash Credit Name of Business Process : General Ledger Accounting Module : Finance Submodule GL. of AS-IS document 3.Term Loans / Cash Credit Version no of document: 2.11 Ref. Unit Bull Power Electronics Limited Signature 3. 36 of 194 .Conversion Requirements None Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements None Business Benefits A better control on Term deposit accounts will be possible through SAP.1. Sign-off (Approval) for this document : Name of Team member M Harikrishna Organisation/Bus.

All those details can be generated from the system later on using the GL line item report.IT CO LOGO Blue Print Document –Finance CLIENT LOGO Detailed Process Description. Describe in details and attach the format in which data would be stored in the other system : Inputs/ data received from other function for this process. Interest on term loan will be booked to Interest on Term Loan account (P&L account)... ( if any ) : Output from this business process sent to other functions. Following accounting entry will be passed into the system for the actual interest on Term Loan availed:Interest on Term Loan A/c …………..………………………Dr Term Loan A/c ……………………………………………….Dr Term Loan A/c …………………Cr Interest calculation on term loan will be done only for the statistical purpose through the system.Cr While doing the entry for the Term loan. Process Step FB01/FB50 FF_1 Explanation. all the details like Interest rate. Process Variations and Exceptions Separate term loan GL accounts (Balance sheet type) for Term loan will be created in SAP for each of the Bank. variations and exceptions Enter GL account document Interest Calculation on GL account Potential Gaps: None Potential Gap Resolution: None System Configuration Considerations Required configuration has already been covered in the above processes. The following accounting entry will be passed into the system for Term Loan availed:Bank A/c ………………………. Reports required related to business process FBL3N-GL line item report FS10N-GL balance summary Outputs required for this business process None Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No If Yes. repayment period. ( if any ) : 37 of 194 . Installments detail etc will be filled in.

1. No of To-BE document 3. Sign-off (Approval) for this document : Name of Team member M Harikrishna Organisation/Bus.1 Flow Chart of Business Process : Submodule GL. 38 of 194 .12 Journal Entries – Intra Branch Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr.1. Unit Bull Power Electronics Limited Signature 3. of AS-IS document 3.12 Journal Entries – Intra Branch Name of Business Process : General Ledger Accounting Module Finance Version no of document: 2.Journal Entries – Intra Branch Date : General Requirements/Expectations Description Transactions within the branch should be recorded separately.Conversion Requirements None Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements None Business Benefits Accounting for Term loan and & interest there on will done in SAP in proper way. Sr.IT CO LOGO Blue Print Document –Finance CLIENT LOGO User Roles and Authorizations Transaction posting authorisation will be given to limited set of users. No. Reports None Technical Considerations .1.12 Ref. Technical Considerations – Forms.

.Cr Process Step FB01 / FB50 Explanation.Conversion Requirements None 39 of 194 .Dr Electricity A/c ……. Describe in details and attach the format in which data would be stored in the other system : Inputs/ data received from other function for this process. Process Variations and Exception These transactions are posted to transfer the expenses/balances from one GL account to another GL account within the branch.IT CO LOGO Blue Print Document –Finance CLIENT LOGO Detailed Process Description. Document type SA can be used for posting such transactions in to SAP. ( if any ) : Output from this business process sent to other functions. ( if any ) : User Roles and Authorizations Transaction posting authorisation will be given to limited set of users. Reports None Technical Considerations . variations and exceptions Enter GL account document Potential Gaps: None Potential Gap Resolution: None System Configuration Considerations None Reports required related to business process FBL3N-GL line item report FS10N-GL balance summary Outputs required for this business process None Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No If Yes. Technical Considerations – Forms. For Eg: If the Telephone Expense is wrongly debited to Electricity Expense a/c. In SAP these transactions are posted through Journal entry. then the Journal Voucher for rectification of the same will be passed as follows: Tel & Fax A/c …….

No.Journal Entries-Inter Branch Version no of document: 2.1 Date : Flow Chart of Business Process : General Requirements/Expectations Description Inter branch transactions are required to be posted in to the system to effect adjustment entries among inter location GL accounts.13 Ref. Sign-off (Approval) for this document : Name of Team member M Harikrishna Organisation/Bus. No of To-BE document 3.1.1.1. Unit Bull Power Electronics Limited Signature 3. of AS-IS document 3.13 Journal Entries-Inter Branch Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr. 40 of 194 .13 Journal Entries-Inter Branch Name of Business Process : General Ledger Accounting Module Finance Submodule GL. Sr.IT CO LOGO Blue Print Document –Finance CLIENT LOGO Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements None Business Benefits Wrongly booked transactions will be corrected using the Journal entry feature of SAP.

Describe in details and attach the format in which data would be stored in the other system : Inputs/ data received from other function for this process... Chennai Cost center will be entered in the line item. The following accounting entry will be entered at the Vashi Plant:Cost center Office Exp A/c ……. Process Step FB01 / FB50 Explanation. Those expenses will be reported in the Chennai Plant Profit & Loss account. Process Variations and Exceptions In the line of the document. Profit Center is assigned in the Cost center master data. ( if any ) : 41 of 194 .Cr Chennai Profit Center Chennai Chennai There will be no need of the inter office adjustment account. the Cost center of the branch/plant for which the expenses has been incurred will be entered. For example. Reports required related to business process FBL3N-GL line item report FS10N-GL balance summary Outputs required for this business process None Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No If Yes. while entering the Journal entry at the Vashi branch.IT CO LOGO Blue Print Document –Finance CLIENT LOGO Detailed Process Description.. if the Vashi plant has incurred expenses on behalf of Chennai plant. variations and exceptions Enter GL account document Potential Gaps: None Potential Gap Resolution: None System Configuration Considerations Required configuration has already been covered in the above processes. The second line item will automatically derive the profit center from the expense line item profit center.Dr Vendor A/c ………. The profit center in the Expense line item will be derived through the cost center mentioned in the Expense line item.

Sr.Taxes-Excise Date : General Requirements/Expectations Description For individual Manufacturing Location total Excise liability for the individual month should be 42 of 194 .14 Ref. Sign-off (Approval) for this document : Name of Team member M Harikrishna Organisation/Bus. Technical Considerations – Forms.Conversion Requirements None Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements None Business Benefits Inter branch transactions can be recorded and controlled through Profit center functionality in a better way. No.IT CO LOGO Blue Print Document –Finance CLIENT LOGO Output from this business process sent to other functions.14 Taxes-Excise Name of Business Process : General Ledger Accounting Module Finance Version no of document: 2.14 Taxes-Excise Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr.1 Flow Chart of Business Process : Submodule GL. No of To-BE document 3.1. Unit Bull Power Electronics Limited Signature 3. ( if any ) : User Roles and Authorizations Transaction posting authorisation will be given to limited set of users. of AS-IS document 3.1. Reports None Technical Considerations .1.

In SAP any service tax credit available will be adjusted to the excise liability.IT CO LOGO Blue Print Document –Finance CLIENT LOGO calculated at the month end. RG23D-For Depot item 3. Three different excise registers will be maintained in SAP:1. PLA RG 23A & RG23C Part I shows the quantities of the materials. Cenvat credit receivable-Revenue (RG23AII) a/c. In SAP. SHE cess on service tax . For financial disclosure it will be treated as contingent liability. the excise duty will be calculated on the quantity consumed at the applicable excise rate on the cost of production + 10%. In the next financial year credit can be taken for that 50% carried forward from the previous year against the excise liability for the year. PLA a/c etc. SHE Cess. Advances paid to Excise/Custom dept for any demands raised by them will be accounted in to separate GL account. GR/IR clearing………………Cr. the excise liability will be arrived through the below mentioned formula:Output tax liability of Excise. 2. Below mentioned accounting entries are passed at the time of domestic procurement of Raw material:During GR:Material Stock ……………Dr. Detailed Process Description. Edu Cess. Cenvat credit receivable-Capital (RG23CII) a/c. In SAP. Edu cess and SHE cess as applicable. while arriving at the Excise duty liability at the time of month end. During Excise Invoice Credit:43 of 194 . RG1 register 4. and how much you have transferred to the CENVAT accounts. Process Variations and Exceptions Excise duty related posting will automatically flow in to FI module through MM & SD module after doing the required CIN configuration in all the three modules. The above mentioned registers are updated on real time basis through MM & SD module. In this case the balance in the service tax credit will be transferred to the Cenvat. Separate GL accounts will be defined and configured in SAP for each of the excise element for example excise payable. Edu Cess on service tax. In the case of captive consumption (excisable goods used for own consumption). RG23A & RG23C-For Raw materials & capital items respectively. In SAP 50% excise credit on capital items will be transferred to the next year by the system automatically. Any excise liability after taking the credit of available excise credit will be paid through PLA a/c in SAP.Opening Credit balance of Excise-Current months credit = Liability or Nil Liability. credit will be taken for the excise paid at the time of purchase which is setoff against the excise duty liability at the time of sale. The excise duty on storage loss or on the material used for testing will be accounted as duty loss. RG 23A & RG23C Part II shows the amounts of excise duty on the materials.

Custom Payable……….Dr. Cr. During Invoice Verification:Cenvat Clearing………. During Excise Invoice Credit:Cenvat Account ………. 44 of 194 . Cr In the next year. GR/IR Clearing………. During Invoice Verification:Cenvat Clearing……………. Cenvat Account…………….Dr. Vendor Payable ……………Cr. Cenvat On-hold……….Cr.. Dr.Dr. below mentioned entry will be passed by the system for transfer of Cenvat on Hold to Cenvat account:Cenvat Account……….IT CO LOGO Blue Print Document –Finance CLIENT LOGO Cenvat Account……………. (50%) (50%) (50%) (50%) Below mentioned accounting entries are passed for Import Procurement of Raw Material:During Customs Duty Clearing invoice Custom Clearing……….. During GR Material Stock………… Dr.Cr. Dr. GR/IR clearing…………Cr.Dr. GR/IR Clearing……………. Cr.Dr. Vendor Payable ………. Below mentioned accounting entries are passed at the time of domestic procurement of Capital Goods:During GR:Material Stock …………Dr. Cenvat Clearing………. Cenvat Clearing……………Cr. Dr. For Excise Duty Reversal through Excise JV Cenvat Clearing…………….Dr..Dr. Cenvat On-hold………...

During monthly Utilization Cenvat payable………………. Cr. Custom Clearing……… Cr. Dr. Cenvat payable………………. Dr. Dr..Dr. For GAR-7 Challan PLA Account………………………. Cenvat payable……………………. PLA on hold Account……………. Cr.Cr.. Vendor Payable……… Cr. Sales Account………………………. During Excise Invoice Credit Cenvat Account………. During Invoice Verification GR/IR Clearing……….Cr. Cenvat Suspense Account…………Cr. PLA Account…………………… Cr.Cr.IT CO LOGO Blue Print Document –Finance CLIENT LOGO GR/IR clearing………. PLA on hold Account………… Cr.Cr..Cr. Sales Tax Payable account……….. For GAR-7 Challan PLA Account…………………. Cenvat Account………………. Dr. During Excise Invoice Creation Cenvat Suspense Account…………Dr. Below mentioned accounting entries are passed at the time of Stock Transfer through SD:No Accounting entry is passed for Performa Billing Document During Excise Invoice Creation Cenvat Suspense Account…… Dr.. 45 of 194 . Below mentioned accounting entries are passed at the time of Sale of Finished Goods from Plant:During Billing Document Customer Account……………………Dr.

The tax movement summary with details such as Opening Balance. a report consisting of the Vendor Name. Manufacturer or Dealer category. return will be prepared manually. Product Name.IT CO LOGO Blue Print Document –Finance CLIENT LOGO During monthly Utilization Cenvat payable……………….. Credits debits during the period and Closing Balance will be provided for individual locations for the individual months through the Excise GL accounts. Cenvat Account………………. ( if any ) : 46 of 194 . On the basis of the Vendor Masters. The excise liability would be set off against service tax credit available in the service tax receivable account through excise JV. All the required detail for filling up the ER-1 return will be provided. 1. More detailed explanation will be provided during the User testing & User training phase of the Project. Describe in details and attach the format in which data would be stored in the other system : Inputs/ data received from other function for this process. Cr. Qty etc needs to be generated through the SAP system. Reports required related to business process FBL3N-GL line item report FS10N-GL balance summary Outputs required for this business process Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No If Yes. ( if any ) : Output from this business process sent to other functions. Various Excise related Tax codes will be configured. Cr. CETH number. ECC number. Dr. Potential Gaps: None Potential Gap Resolution: None System Configuration Considerations Excise related GL accounts will be assigned through MM & SD account determination. PLA Account………………….. 2.

Technical Considerations – Forms. 47 of 194 .Taxes.1. of AS-IS document 3.1.1 Flow Chart of Business Process : Submodule GL.15 Taxes-Sales Tax Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr. Sign-off (Approval) for this document : Name of Team member M Harikrishna Organisation/Bus. Reports None Technical Considerations .15 Ref.1.15 Taxes. No of To-BE document 3. The tax liability should be calculated for the month and paid to the credit of the tax dept as per the due dates.Sales Tax Name of Business Process : General Ledger Accounting Module Finance Version no of document: 2.Sales Tax Date : General Requirements/Expectations Description All Manufacturing plants are registered with the Sales Tax dept and are under the regime of Value Added Tax. Sr.IT CO LOGO Blue Print Document –Finance CLIENT LOGO User Roles and Authorizations Transaction posting authorisation will be given to limited set of users. Unit Bull Power Limited Electronics Signature 3. SD & FI module. No.Conversion Requirements None Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements None Business Benefits Through CIN all the excise accounting will be done in close integration of MM.

The amount which is not eligible for set off will be included in the Inventory cost. The sales tax will be calculated at the rate defined in the Tax codes in SAP. state acts which is ineligible. returns will be prepared manually. Credits and Debits during the period and Closing Balance will be provided by SAP for individual locations for the individual months. A certain percentage of vat credit will be reversed on purchase of fuels and added to the cost as per the resp.. This can be generated any time from the system using transaction code J1I2. 48 of 194 . Various applicable Sales Tax codes will be created in SAP to calculate the sales tax at different state rate and for the concessional tax. Sales tax register showing all the credits availed during the period with details such as Vendor Name. Separate GL accounts will be defined and configured in SAP. Sales tax code for both the input & output tax will be created. Sales Account………………………. Below mentioned accounting entries are passed at the time of Sale of Finished Goods from Plant:During Billing Document Customer Account……………………Dr. In the case of Deferment of Sales tax (IFST) liability for a specified period and specified amount will be accounted in a separate GL account “IFST Deferral A/c. Sales tax eligible for set off will be accounted in separate GL account.Opening Credit balance of Sales Tax-Current months credit = Liability or Nil Liability.” It will be paid as per the due dates. Assessable Value. for example in case of C form. TIN Number. Tax Invoice No.Cr. Input tax credit will be derived from the purchasing module and output tax credit will be derived from Sales and distribution module. Tax Rate. however it will be only the output tax liability at depot.IT CO LOGO Blue Print Document –Finance CLIENT LOGO Detailed Process Description. Sales Tax liability will be calculated in SAP as per the below mentioned formula:-Output tax liability of Sales tax. Sales Tax registers will be maintained as depot in similar way as maintained at the plant. All the required detail for filling up the Sales tax return will be provided. Separate GL accounts will be created for Local Sales tax & Central Sales Tax. SAP has provided standard Sales Tax register. The Sales tax movement summary with details such as Opening Balance. Tax Amount and percentage will be generated from SAP. Process Variations and Exceptions Output Tax:Sales Tax related posting will automatically flow in to FI module through SD module after doing the required configuration in SD & FI module. Tracking of the due date will be manual.

If the entire input tax is nondeductible. Sales Tax liability will be paid as per the due date. example A) or distribute it to the G/L account (see the following figure. example B). There will be no automatic prompt for payment of liability on the due date. The receivable amount will be transferred to Sales Tax Receivable A/c and shown in the BS. you can post the tax amount to a separate expense account or distribute it to the G/L account. example C) or be distributed between the G/L account and assets line items. You enter the tax percentage rates for the input tax portion and the nondeductible portion to a shared tax code.200. Potential Gaps: None Potential Gap Resolution: None System Configuration Considerations Sales tax related tax codes will be configured. Sales tax receivable (excess credit) at the end of the FY will not be carried forward to the subsequent FY. Sales Tax Payable account………. Input Tax:Input tax is calculated as per the tax code mentioned in the purchase order. If the entire input VAT amount is non-deductible. If a part or the entire input tax is nondeductible. you must specify for the tax code that zero percentage input tax is to be calculated.. You can now post the nondeductible portion to a separate account (see the following figure. no input VAT posting is made. Reports required related to business process Sales Tax register 49 of 194 . You have to post an incoming invoice amounting to INR 1. More detailed explanation will be provided during the User testing & User training phase of the Project.IT CO LOGO Blue Print Document –Finance CLIENT LOGO Cenvat Suspense Account…………Cr. the non-deductible input tax can be posted to a separate account (see the following figure. The tax amount of INR 200 (20 percent) comprises 12 percent input taxes (INR 120) and a nondeductible portion of eight percent (INR 80).Cr.

Unit Bull Power Limited Electronics Signature 50 of 194 . Technical Considerations – Forms. Reports None Technical Considerations . ( if any ) : User Roles and Authorizations Transaction posting authorisation will be given to limited set of users.Conversion Requirements None Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements None Business Benefits Sales tax related accounting will be done in SAP in proper way. Describe in details and attach the format in which data would be stored in the other system : Inputs/ data received from other function for this process. Sign-off (Approval) for this document : Name of Team member M Harikrishna Organisation/Bus.IT CO LOGO Blue Print Document –Finance CLIENT LOGO Outputs required for this business process None Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No If Yes. ( if any ) : Output from this business process sent to other functions.

At the year end closing. professionals or on payment of Rent. This can be handled by specifying the base amount on which withholding tax is to be calculated.1 Flow Chart of Business Process : Submodule GL. Detailed Process Description. It can. of AS-IS document 3. If you first make a down payment (and withhold tax on it) and then enter the vendor invoice later on.1. you have to clear the invoice against the down payment so that you do not withhold tax on the same item twice. Sr. Brokers. No of To-BE document 3. Such TDS are to be accounted for in SAP under the appropriate heads. only one withholding tax code can be used for a down payment or invoice. depending on the section of the Income Tax Act. Salaries etc at predefined rate. but issue separate invoices for different tax rates. Various types of TDS accounts will be maintained in SAP for various types of payments. Process Variations and Exceptions Country Version India offers two solutions for handling withholding tax (also known as tax deducted at source or TDS):1. whichever comes first. When you enter a vendor invoice or make a down payment that is liable to withholding tax. That is.IT CO LOGO Blue Print Document –Finance CLIENT LOGO 3. This implies that an invoice cannot contain items with different withholding tax rates. Since different taxes need to be remitted on due dates. Classic Withholding Tax .Taxes-TDS Date : General Requirements/Expectations Description TDS is to be deducted on any payment to contractors. however. All the TDS 51 of 194 .advance). TDS liability as on 31 st March.The withholding tax for an invoice or a down payment is calculated at header level. No. You are required to calculate taxes either when you enter an invoice or when you make any sort of payment (incl.18 Ref.18 Taxes-TDS Name of Business Process : General Ledger Accounting Module Finance Version no of document: 2.1. On account of calculation at header level.Extended Withholding Tax-Multiple tax codes can be used in one Invoice Extended withholding tax will be activated for BPE. the system automatically creates line items for the appropriate taxes. the system also calculates and records each line item's due date. 2. companies have to instruct their suppliers not to include items with different withholding tax rates in a single invoice. will be cleared by 31st May.18 Taxes-TDS Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr. including surcharges. contain one or more items with the same withholding tax rate and one or more items with no withholding tax.1.

. The calculation for the same will be done outside the system.Dr Vendor Account…………………. you have to enter a Journal voucher (JV) to correct the error. Employee whose TDS has to be deducted will be created as Vendor in SAP. TDS amount for NRI payments (Colas) will be grossed up and the liability will be accounted. payable by vendor Debit Loss account Credit Vendor account Tax payable Vendor account account Vendor account Tax payable TDS (Work Contract Tax) for Service Orders will be calculated and deducted.Cr 52 of 194 .IT CO LOGO Blue Print Document –Finance CLIENT LOGO accounts will have the separate limit and separate rates. TDS certificates for the vendor will be generated from the SAP. through configuration. after you have entered and cleared a vendor invoice and you have discovered that you have posted the wrong amount of tax or that you have posted the tax using the wrong official tax key. TDS will be calculated at the rate mentioned in the tax code. Tax code maintained in the master data is defaulted to the document automatically. Type of change Tax refund to vendor (tax already remitted) Tax refund to vendor (tax not yet remitted) Tax increase. The following entry will be passed on booking the Vendor Invoice:Expenses Account………………. Tax code is maintained in the vendor Master data. PAN number detail of the vendor will be defaulted from the Vendor master. two entries will be created as follows:Recipient type CO OT Text Companies Others If. For each withholding tax type. Below mentioned are the few of the examples:Key 194A 194C 194D 194I 194J 195 Description Income other than Securities Payment to Contractors Insurance Rent Professional services Other Payment residents to Non- TDS will be accounted in to the system as TDS payable at the time of booking the vendor invoice or at the time of payment whichever is earlier.

if any.IT CO LOGO Blue Print Document –Finance CLIENT LOGO TDS payable Account………… Cr SAP will provide a report on TDS payable for the deductions made during the month for all locations with a clear segregations under various category of deductions with details such as Voucher reference no. Withholding Tax base amount 7. Define GL accounts 10. Withholding Tax keys 3. Surcharges 9. Country key for withholding Tax 2. Describe in details and attach the format in which data would be stored in the other system : Inputs/ data received from other function for this process. Withholding Tax codes 6. TDS codes will be defaulted in the Invoice from the master data. Appropriate action can be taken for the differences. Potential Gaps: None Potential Gap Resolution: None System Configuration Considerations Below are the configuration to be done for TDS:1. Minimum & Maximum amounts 8. Date of Deduction. Certificate numbering Reports required related to business process FBL3N-GL line item report FS10N-GL balance summary Outputs required for this business process None Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No If Yes. More detailed explanation will be provided during the User testing & User training phase of the Project. TDS will be paid as per the due date. ( if any ) : 53 of 194 . PAN Numbers. TDS Certificates will be generated and printed through SAP for various categories of services at the year end for all the Vendors. Withholding Tax type 5. Vendor Name. TDS defaulted can be compared with the Vendor actual invoice. Reason for Exemption 4.

IT CO LOGO Blue Print Document –Finance CLIENT LOGO Output from this business process sent to other functions. 2. ( if any ) : User Roles and Authorizations Transaction posting authorisation will be given to limited set of users. Technical Considerations – Forms. TDS certificates will be generated from SAP. Sign-off (Approval) for this document : Name of Team member M Harikrishna Organisation/Bus.Conversion Requirements None Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements None Business Benefits 1. Unit Bull Power Limited Electronics Signature 54 of 194 .TDS related transaction and outstanding liability detail can be derived from the SAP quickly. Reports None Technical Considerations .

variations and exceptions Enter GL account document Potential Gaps: None Potential Gap Resolution: None System Configuration Considerations None Reports required related to business process FBL3N-GL line item report 55 of 194 . No of To-BE document 3. Cr A separate GL account will be maintained for the TDS receivable account.Tax Deducted at Source (Asset) Version no of document: 2. This will help in identification of the certificates year wise.19 Tax Deducted at Source (Asset) Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr. Manual reconciliation will be done for the TDS certificate received from the customer against the TDS entries posted in to the system. . Sr. The year to which the TDS certificate pertains to.19 Tax Deducted at Source (Asset) Name of Business Process : General Ledger Accounting Module Finance Submodule GL. Process Step FB01 / FB50 Explanation..IT CO LOGO Blue Print Document –Finance CLIENT LOGO 3. are to accounted in the system on receipt of confirmation from the deductor.1. No. More detailed explanation will be provided during the User testing & User training phase of the Project.1. Process Variations and Exceptions On receipt of confirmation from the tax deductor. Electricity Deposits etc. Following accounting entry will be passed for TDS (Asset):TDS receivable account…………… Dr Customer Account………………. will be entered in the text field of the document.19 Ref.1. Hospitality charges reimbursements and Interest on Bank Deposits. Detailed Process Description. the tax will be accounted for in the system. Such type of TDS will be accounted for in SAP.1 Flow Chart of Business Process : Date : General Requirements/Expectations Description The Tax is Deducted at Source on receivable such as Job Work. of AS-IS document 3.

( if any ) : Output from this business process sent to other functions. ( if any ) : User Roles and Authorizations TDS Transaction posting authorisation will be given to limited set of users. Reports None Technical Considerations .Conversion Requirements None Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements None Business Benefits TDS receivable accounting will be done in SAP in proper way. Technical Considerations – Forms.IT CO LOGO Blue Print Document –Finance CLIENT LOGO FS10N-GL balance summary Outputs required for this business process None Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No If Yes. Describe in details and attach the format in which data would be stored in the other system : Inputs/ data received from other function for this process. Unit Bull Power Electronics Limited Signature 56 of 194 . Sign-off (Approval) for this document : Name of Team member M Harikrishna Organisation/Bus.

1. Detailed Process Description.IT CO LOGO Blue Print Document –Finance CLIENT LOGO 3. 4. The excise differential workings would be provided by MM.Dr Job Work Charges A/c ……….1. The below mentioned accounting entry will be passed in to the system through SD module:XYZ LIMITED – Job work Reimbursible A/c ……………….Cr More detailed explanation will be provided during the User testing & User training phase of the Project. TDS will be deducted by XYZ LIMITED on job work. The differential duty will be recovered by BPE from XYZ LIMITED. Process Variations and Exceptions As per the Job Work arrangement for manufacture of Modified Bitumen between XYZ LIMITED/Customer & BPE.…….. The job work qty. of AS-IS document 3. BPE does Job Work of only Crumb Rubber Modifier Bitumen to XYZ LIMITED and also does other grades of Modified Bitumen to other Customers. No of To-BE document 3. 57 of 194 . The entire flow of excise transaction in Finance will be from MM & SD.1 Date : Flow Chart of Business Process : General Requirements/Expectations Description The Job Work to XYZ LIMITED and other Customers is done by BPE under Sub Contract basis at all BPE manufacturing locations. The Job Work Processing Charges will be calculated and accounted in the system for individual manufacturing location by multiplying the Job work sale quantity in Metric Ton’s for the month with the agreed process charges per MT. BPE avails input tax credit of Excise on the stock transfer made by XYZ LIMITED/Customer for duty paid Bitumen as Job Work input. BPE will avail tax credit of Excise on stock transfer made by XYZ LIMITED for duty paid Bitumen as Job work input.1. On the finished product Modified Bitumen the excise duty will be paid by BPE.Job Work Accounting Version no of document: 2. The following will be the accounting treatment in SAP:1. 2. information will be available from the SD module.22 Ref.22 Job Work Accounting Name of Business Process : General Ledger Accounting Module Finance Submodule GL. Duty paid on excisable modifier will be availed as input credit. No.22 Job Work Accounting Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr. 3. Potential Gaps: Job work differential duty calculation will not be done by the system automatically. Sr.

Technical Considerations – Forms. ( if any ) : Output from this business process sent to other functions. Unit Bull Power Limited Electronics Signature 58 of 194 . Reports required related to business process FBL3N-GL line item report FS10N-GL balance summary Outputs required for this business process None Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No If Yes.Conversion Requirements None Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements None Business Benefits Job work related accounting will be done in SAP in proper way. ( if any ) : User Roles and Authorizations Transaction posting authorisation will be given to limited set of users. Describe in details and attach the format in which data would be stored in the other system : Inputs/ data received from other function for this process. Sign-off (Approval) for this document : Name of Team member M Harikrishna Organisation/Bus. Reports None Technical Considerations . System Configuration Considerations CIN related configuration will be done in MM. SD & FI module.IT CO LOGO Blue Print Document –Finance CLIENT LOGO Potential Gap Resolution: New report will be developed for the Job work differential duty calculation in MM module.

1.IT CO LOGO Blue Print Document –Finance CLIENT LOGO 3. Process Variations and Exceptions The system automatically passes the accounting entry through Inter office adjustment account.24 Stock Transfer-Raw Material Name of Business Process : General Ledger Accounting Module Finance Submodule GL.24 Stock Transfer-Raw Material Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr.1. Please refer MM BBP document.1 Date : Flow Chart of Business Process : General Requirements/Expectations Description The Plant to Plant stock transfer of Raw Material will be handled through the Material Management module. Reports required related to business process Stock report Outputs required for this business process None Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : 59 of 194 . The sending location will pay the duty on the stock transferred and the receiving location will take the Cenvat credit. Cenvat credit receivable GL account will be configured. Potential Gaps: None Potential Gap Resolution: None System Configuration Considerations 1. No of To-BE document 3.24 Ref. Excise duty will be passed on by the sending location to receiving location on FIFO basis. No.1. 2. Detailed Process Description.Stock Transfer-Raw Material Version no of document: 2. More detailed explanation will be provided during the User testing & User training phase of the Project. Sr. of AS-IS document 3. This process is covered under MM module. Excise payable GL account will be configured.

Conversion Requirements None Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements None Business Benefits Proper accounting treatment will be given in SAP of the Stock transfer. ( if any ) : User Roles and Authorizations Transaction posting authorisation will be given to limited set of users.IT CO LOGO Blue Print Document –Finance CLIENT LOGO No If Yes. Unit Bull Power Limited Electronics Signature 60 of 194 . Describe in details and attach the format in which data would be stored in the other system : Inputs/ data received from other function for this process. Sign-off (Approval) for this document : Name of Team member M Harikrishna Organisation/Bus. Reports None Technical Considerations . Technical Considerations – Forms. ( if any ) : Output from this business process sent to other functions.

the system automatically passes the accounting entries.1.25 Ref.25 Stock Transfer-Finished Good Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr. This process is covered under MM module. Excise payable GL account will be configured.1. 2. Please refer MM BBP document.1. Reports required related to business process Stock report 61 of 194 . of AS-IS document 3.25 Stock Transfer-Finished Good Name of Business Process : General Ledger Accounting Module Finance Submodule GL.1 Flow Chart of Business Process : Date : General Requirements/Expectations Description The Plant to Depot stock transfer of Finished Goods will be processed through Material Management module. Process Variations and Exceptions When routed through this Material Management module.Stock Transfer-Finished Good Version no of document: 2. More detailed explanation will be provided during the User testing & User training phase of the Project. Detailed Process Description. Sr.IT CO LOGO Blue Print Document –Finance CLIENT LOGO 3. No of To-BE document 3. Expense on stock transfer GL account will be configured. Potential Gaps: None Potential Gap Resolution: None System Configuration Considerations 1. No.

Unit Bull Power Limited Electronics Signature 62 of 194 . Reports None Technical Considerations .Conversion Requirements None Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements None Business Benefits Proper accounting treatment will be given in SAP of the Stock transfer. Technical Considerations – Forms.IT CO LOGO Blue Print Document –Finance CLIENT LOGO Outputs required for this business process None Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No If Yes. Sign-off (Approval) for this document : Name of Team member M Harikrishna Organisation/Bus. ( if any ) : User Roles and Authorizations Transaction posting authorisation will be given to limited set of users. ( if any ) : Output from this business process sent to other functions. Describe in details and attach the format in which data would be stored in the other system : Inputs/ data received from other function for this process.

the original entry is automatically reversed.1 Flow Chart of Business Process : Submodule GL. Similarly. Transaction type ‘Recurring Journals’ can be used to amortize prepayments if the amount of amortization is the same for each period. the accrual booked will not be reversed in the next period.Accruals Date : General Requirements/Expectations Description Accruals and Prepayments are some of the common period-end processes.1. provided the future period is open. BPE will be booking the Accrual through Journal vouchers. Note that the reversal entry gets generated and Posted into the next period.1. the amortization has to be done manually. 2.26 Accruals Name of Business Process : General Ledger Accounting Module Finance Version no of document: 2.IT CO LOGO Blue Print Document –Finance CLIENT LOGO 3. Process Variations and Exceptions Accrual can be booked in SAP in two ways:1. SAP facilitates automatic reversal of accrual entries. If the amount varies in each period. No of To-BE document 3. In this case. In the next period.1.26 Accruals Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr. Detailed Process Description. Appropriate TDS will be deducted on the accrued expenses.Posting of accrual through Journal voucher:A journal voucher can be posted for the accruing the expenses at the month end. Process Step FBS1 Explanation. of AS-IS document 3. No. Sr. Posting the accrual at the month end and reversal in the next month:Accrual transactions need to be accounted for in the books of accounts so as to portray a true and fair view of the financial status of any organization. This entry may be reversed at the start of the following period.26 Ref. by running a specific program. Expenses incurred during the period under review in respect of which invoices have not been received have to be accrued. a proportionate part of the prepayments has to be expensed during each period. When the accrual entry is posted. variations and exceptions Post accrual document 63 of 194 . the user has to indicate that the entry has to be reversed in a subsequent period. These entries may however be reversed in the subsequent period to nullify the original entry. The difference between the accrual amount and the actual expenses will be booked separately.

Potential Gap Resolution: Accrual upload functionality will be provided through development System Configuration Considerations Authorization to execute a recurring transaction Reports required related to business process FBL3N-GL line item report FS10N-GL balance summary Outputs required for this business process None Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No If Yes. Unit Signature 64 of 194 . ( if any ) : User Roles and Authorizations Transaction posting authorisation will be given to limited set of users.IT CO LOGO Blue Print Document –Finance CLIENT LOGO Potential Gaps: Accrual upload functionality is not available in SAP. Reports None Technical Considerations . Describe in details and attach the format in which data would be stored in the other system : Inputs/ data received from other function for this process. Sign-off (Approval) for this document : Name of Team member Organisation/Bus.Conversion Requirements None Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements None Business Benefits Audit trail of accrual transactions and their Reversal status can be maintained. ( if any ) : Output from this business process sent to other functions. Technical Considerations – Forms.

.. Sr.. variations and exceptions Enter Vendor Invoice 65 of 194 .1. Vendor(Technical Fee Payable) A/c………. If a G/L account is managed in a foreign currency.... The entry in the system would be as follows: Technical Fee A/c …………………………Dr TDS Payable (195) A/c ……….... Detailed Process Description....... that is.Technical Fee Date : General Requirements/Expectations Description A liability for Technical Fee is created and paid to one of the promoters COLAS for specified amount in foreign currency as per agreement. No of To-BE document 3... Process Step FB60 Explanation. An accrual in EUR currency will be made by HQO during the financial closure through transaction code FB60..IT CO LOGO Blue Print Document –Finance Bull Power Limited Electronics CLIENT LOGO M Harikrishna 3.1.1 Flow Chart of Business Process : Submodule GL.. The system will convert EUR to INR based on the exchange rate maintained in the system. Service tax credit will be posted through JV.Cr As per the BPE current practice.1. No.Cr Vendor(Technical Fee Payable) A/c ………………………….51.Cr While the actual payment is made...……. Process Variations and Exceptions Technical Fee document can be posted in any foreign currency for which a currency key is defined in the system..29 Ref. …………………………Dr Foreign Exchange Gain/Loss....29 Technical Fee Name of Business Process : General Ledger Accounting Module Finance Version no of document: 2.Cr/Dr Bank Clearing A/c …………...……………. The Foreign exchange gain/loss method is explained in the section 3.... for example a bank account..1. The R & D Cess on amount to be remitted to the promoter (in INR) is calculated at the specified rate and paid before the remittance of amount to the promoter. of AS-IS document 3. the foreign currency.. the TDS deducted on Technical fee is treated as expenditure. transaction can only be posted to this G/L account in the account currency... The Service Tax is also calculated on the gross of amount at the specified rate (Less R & D Cess amount) and paid before the remittance of amount to the promoter... The TDS on the same @ 10% is grossed up manually and paid to the Tax authorities as per the scheduled due dates.. the exchange gain/loss will be calculated by the system automatically..29 Technical Fee Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr..

IT CO LOGO Blue Print Document –Finance CLIENT LOGO Potential Gaps: None Potential Gap Resolution: None System Configuration Considerations 1.Conversion Requirements None Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements None Business Benefits System will automatically convert the amount in foreign currency in the document to the INR amount. Unit Signature 66 of 194 . For automatic calculation of foreign exchange gain / loss. ( if any ) : User Roles and Authorizations Transaction posting authorisation will be given to limited set of users. Foreign exchange gain/loss account will be configured in the system. Reports required related to business process FBL3N-GL line item report FS10N-GL balance summary Outputs required for this business process None Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No If Yes. Describe in details and attach the format in which data would be stored in the other system : Inputs/ data received from other function for this process. ( if any ) : Output from this business process sent to other functions. Technical Considerations – Forms. Reports None Technical Considerations . Sign-off (Approval) for this document : Name of Team member Organisation/Bus.

No. variations and exceptions Enter Vendor invoice Potential Gaps: None Potential Gap Resolution: None System Configuration Considerations None Reports required related to business process FBL3N-GL line item report FS10N-GL balance summary 67 of 194 .31 Marketing Compensation Name of Business Process : General Ledger Accounting Module Finance Version no of document: 2. Detailed Process Description. The amount arrived on basis the slab will be accrued in to the system through vendor Invoice and a corresponding Tax will be deducted at Source.31 Marketing Compensation Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr. The calculation for marketing compensation will be done outside the system.1 Flow Chart of Business Process : Submodule GL.1. of AS-IS document 3. No of To-BE document 3. Sr.Marketing Compensation Date : General Requirements/Expectations Description During the book closure activity. Process Variations and Exceptions Total qty.IT CO LOGO Blue Print Document –Finance CLIENT LOGO M Harikrishna Bull Power Limited Electronics 3.1. The compensation is derived on the basis of a slab system for the quantities of sale during the year. sold information will be generated through SD module. an accrual is made for the amount payable for marketing support provided by XYZ LIMITED for sale of BPE products.1.31 Ref. Process Step FB60 Explanation.

Sign-off (Approval) for this document : Name of Team member M Harikrishna Organisation/Bus. ( if any ) : User Roles and Authorizations Transaction posting authorisation will be given to limited set of users. Describe in details and attach the format in which data would be stored in the other system : Inputs/ data received from other function for this process.IT CO LOGO Blue Print Document –Finance CLIENT LOGO Outputs required for this business process None Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No If Yes. Technical Considerations – Forms. Reports None Technical Considerations . Unit Bull Power Limited Electronics Signature 68 of 194 .Conversion Requirements None Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements None Business Benefits Accounting will be done in SAP in proper way. ( if any ) : Output from this business process sent to other functions.

.. of AS-IS document 3.. below mentioned entry will be passed by the system automatically:Bank clearing A/c ……………..IT CO LOGO Blue Print Document –Finance CLIENT LOGO 3... Insurance.1..32 Prepaid Expenses Name of Business Process : General Ledger Accounting Module Finance Version no of document: 2..Dr Bank A/c…………………………………….Prepaid Expenses Date : General Requirements/Expectations Description Some of the expenses like Annual Maintenance Charges. No.. No of To-BE document 3. Sr... Prepaid Exp A/c . variations and exceptions Enter GL account document Potential Gaps: None Potential Gap Resolution: None 69 of 194 .1......1 Flow Chart of Business Process : Submodule GL.……………………Dr Bank clearing A/c …………….... and Subscriptions etc are paid in advance for a specific period. The entry would be as follows: Expense A/c ………………Dr Prepaid Expenses A/c ……Cr Process Step FB01/FB50 Explanation...…....1....... Detailed Process Description......Cr A journal entry will passed periodically by the system automatically to transfer the balance in the Prepaid Exp A/c to Respective Expense A/c of respective Cost Centre on completion of the period proportionate to the actual total coverage period..Cr On upload of the bank statement.32 Ref.32 Prepaid expenses Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr. Process Variations and Exceptions Such expenses will be booked in the “Prepaid expenses” account (Balance sheet item).

Reports None Technical Considerations . Sign-off (Approval) for this document : Name of Team member M Harikrishna Organisation/Bus. ( if any ) : User Roles and Authorizations Transaction posting authorisation will be given to limited set of users.Conversion Requirements None Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements None Business Benefits Accounting will be done in SAP in proper way. ( if any ) : Output from this business process sent to other functions. Describe in details and attach the format in which data would be stored in the other system : Inputs/ data received from other function for this process.IT CO LOGO Blue Print Document –Finance CLIENT LOGO System Configuration Considerations None Reports required related to business process FBL3N-GL line item report FS10N-GL balance summary Outputs required for this business process None Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No If Yes. Technical Considerations – Forms. Unit Bull Power Limited Electronics Signature 70 of 194 .

The summary report can be drilled down further to the line item level.Proof Sheets Date : General Requirements/Expectations Description The Proof Sheets are prepared for all the Balance Sheet items at regular intervals to identify the open items by scrutinizing the GL of the Balance Sheet items. Process Variations and Exceptions SAP standard transaction codes are available to check/confirm the balances of General ledger balances.1 Flow Chart of Business Process : Submodule GL.IT CO LOGO Blue Print Document –Finance CLIENT LOGO 3. of AS-IS document 3.33 Ref.1. Process Step FS10N FBL3N Explanation.33 Proof Sheets Name of Business Process : General Ledger Accounting Module Finance Version no of document: 2.33 Proof Sheets Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr. code FS10N) or at the line item level (FBL3N). No. variations and exceptions GL balance period wise GL line item detail Potential Gaps: None Potential Gap Resolution: None System Configuration Considerations None Reports required related to business process FBL3N-GL line item report FS10N-GL balance summary Outputs required for this business process 71 of 194 . Open item balances can be seen at the summary level (T. Sr. This information from SAP will be used for balance confirmation as well as for tracking any incorrect postings.1. Detailed Process Description.1. The above mentioned statement/summary report can be generated at any time/date as well as on the monthly basis. No of To-BE document 3.

Technical Considerations – Forms. Sign-off (Approval) for this document : Name of Team member M Harikrishna Organisation/Bus. ( if any ) : User Roles and Authorizations Transaction posting authorisation will be given to limited set of users. 2. Balance confirmation can be done easily for any accounts. Incorrect entries can be tracked down easily. Describe in details and attach the format in which data would be stored in the other system : Inputs/ data received from other function for this process. ( if any ) : Output from this business process sent to other functions.IT CO LOGO Blue Print Document –Finance CLIENT LOGO None Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No If Yes. Unit Bull Power Limited Electronics Signature 72 of 194 . Reports None Technical Considerations .Conversion Requirements None Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements None Business Benefits 1.

34 Valuation . Reports required related to business process Stock Valuation report Outputs required for this business process 73 of 194 .1. No of To-BE document 3. Detailed Process Description. of AS-IS document 3.34 Valuation .Raw Material/Packing Material/Fuels & Lubricants Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr.IT CO LOGO Blue Print Document –Finance CLIENT LOGO 3.Raw Material/Packing Material/Fuels & Lubricants Name of Business Process : Valuation . Process Variations and Exceptions The Stock of various Raw Material/Packing Material/Fuels & Lubricants will be valued by system automatically at moving average price. Process Step MCBA Explanation.1.34 Ref. No. The detailed process is explained in the MM TO-BE document.1. variations and exceptions Stock valuation report Potential Gaps: None Potential Gap Resolution: None System Configuration Considerations Required configuration has already been covered in the above processes. Sr.1 Flow Chart of Business Process : Date : Raw Material/Packing Material/Fuels & Lubricants General Requirements/Expectations Description Physical Stock valuation will be done on periodical basis for all Raw Material/Packing Material/Fuels & Lubricants obtaining a Physical Verification Stock Statement of the concerned official which is compared with the Book Stocks (Monthly Plant Report) for the individual respective Plants. Report on consumption of raw material will be generated from SAP system.General Ledger Accounting Module Finance Submodule GLValuation Version no of document: 2. More detailed explanation will be provided during the User testing & User training phase of the Project.

Sign-off (Approval) for this document : Name of Team member M Harikrishna Organisation/Bus. Technical Considerations – Forms.Conversion Requirements None Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements None Business Benefits Accounting will be done in SAP in proper manner. Unit Bull Power Limited Electronics Signature 74 of 194 . ( if any ) : User Roles and Authorizations Transaction posting authorisation will be given to limited set of users. ( if any ) : Output from this business process sent to other functions. Describe in details and attach the format in which data would be stored in the other system : Inputs/ data received from other function for this process. Reports None Technical Considerations .IT CO LOGO Blue Print Document –Finance CLIENT LOGO None Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No If Yes.

Finished Goods Name of Business Process : General Ledger Accounting Module Finance Submodule GL.Finished Goods Version no of document: 2.Stock Valuation . Reports required related to business process Stock Valuation report Outputs required for this business process 75 of 194 . Process Step MCBA Explanation.35 Stock Valuation . Finished Goods at Depots by obtaining a Physical Verification Stock Statement of the Plant Manager which will be compared with the Book Stocks (Monthly Plant Report) for the individual respective locations. No. Standard price for the Finished good will calculated at monthly basis.IT CO LOGO Blue Print Document –Finance CLIENT LOGO 3. No of To-BE document 3. Process Variations and Exceptions The Stock of various Finished Goods will be valued at standard price by the system automatically.1.1. A Marketing Personnel is deputed to verify the physical stocks at Depots who confirms the same in a prescribed format with the signature of the Depot In charge.1.35 Ref. The detailed process is explained in the MM TO-BE document.35 Stock Valuation .Finished Goods Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr. More detailed explanation will be provided during the User testing & User training phase of the Project. of AS-IS document 3. Detailed Process Description. Sr. variations and exceptions Stock Valuation report Potential Gaps: None Potential Gap Resolution: None System Configuration Considerations Required configuration has already been covered in the above processes.1 Flow Chart of Business Process : Date : General Requirements/Expectations Description Physical Stock valuation will be done on periodical basis for all Finished Goods at Plants.

( if any ) : Output from this business process sent to other functions. Unit Bull Power Limited Electronics Signature 76 of 194 .IT CO LOGO Blue Print Document –Finance CLIENT LOGO None Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No If Yes. ( if any ) : User Roles and Authorizations Transaction posting authorisation will be given to limited set of users. Reports None Technical Considerations . Technical Considerations – Forms. Describe in details and attach the format in which data would be stored in the other system : Inputs/ data received from other function for this process.Conversion Requirements None Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements None Business Benefits Accounting will be done in SAP in proper way. Sign-off (Approval) for this document : Name of Team member M Harikrishna Organisation/Bus.

Moving average price is the moving average of the standard price of the sending manufacturing plant.IT CO LOGO Blue Print Document –Finance CLIENT LOGO 3. Sr. No of To-BE document 3.Stock Valuation . Process Step MCBA Explanation.36 Ref.Depot Stocks Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr. Moving average price is updated with each receipt of the material.1.Depot Stocks Name of Business Process : General Ledger Accounting Module Finance Submodule GL.36 Stock Valuation .1 Flow Chart of Business Process : Date : General Requirements/Expectations Description Stock valuation will be done on periodical basis for all Finished Goods at Depots by obtaining a Physical Verification Stock Statement from the Marketing Personnel deputed to verify the physical stocks at Depots will confirm the same in a prescribed format with the signature of the Depot In charge.1.36 Stock Valuation . Reports required related to business process Stock Valuation report Outputs required for this business process None 77 of 194 .1.Depot Stocks Version no of document: 2. More detailed explanation will be provided during the User testing & User training phase of the Project. of AS-IS document 3. The detailed process is explained in the MM & CO TO-BE document. Process Variations and Exceptions The Stock of various Depot Goods will be valued at Moving average price. Detailed Process Description. variations and exceptions Stock Valuation report Potential Gaps: None Potential Gap Resolution: None System Configuration Considerations Required configuration has already been covered in the above processes. No.

Sign-off (Approval) for this document : Name of Team member M Harikrishna Organisation/Bus. Describe in details and attach the format in which data would be stored in the other system : Inputs/ data received from other function for this process. ( if any ) : Output from this business process sent to other functions. Unit Bull Power Limited Electronics Signature 78 of 194 . ( if any ) : User Roles and Authorizations Transaction posting authorisation will be given to limited set of users. Technical Considerations – Forms.IT CO LOGO Blue Print Document –Finance CLIENT LOGO Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No If Yes.Conversion Requirements None Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements None Business Benefits Accounting will be done in SAP in proper way. Reports None Technical Considerations .

Moving average price is updated with each receipt of the material.1. More detailed explanation will be provided during the User testing & User training phase of the Project. of AS-IS document 3.1.1 Flow Chart of Business Process : Date : General Requirements/Expectations Description The valuation for Stock in Transit is done for those goods which are sent by one location but not received by the destiny location. Process Variations and Exceptions The Stock of various in transit Goods will be valued at Moving average price.37 Stock Valuation .Stock in Transit Version no of document: 2. Reports required related to business process Stock Valuation report Outputs required for this business process None Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : 79 of 194 .Stock in Transit Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr.1. variations and exceptions Stock Valuation Report Potential Gaps: None Potential Gap Resolution: None System Configuration Considerations Required configuration has already been covered in the above processes. No of To-BE document 3.37 Stock Valuation .Stock Valuation . Process Step MCBA Explanation. The detailed process is explained in the MM & CO TO-BE document.Stock in Transit Name of Business Process : General Ledger Accounting Module Finance Submodule GL. Detailed Process Description. No. Sr.IT CO LOGO Blue Print Document –Finance CLIENT LOGO 3.37 Ref. Moving average price is the moving average of the standard price.

IT CO LOGO Blue Print Document –Finance CLIENT LOGO No If Yes. ( if any ) : User Roles and Authorizations Transaction posting authorisation will be given to limited set of users.Conversion Requirements None Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements None Business Benefits Accounting will be done in SAP in proper way. Sign-off (Approval) for this document : Name of Team member M Harikrishna Organisation/Bus. Describe in details and attach the format in which data would be stored in the other system : Inputs/ data received from other function for this process. Technical Considerations – Forms. Unit Bull Power Limited Electronics Signature 80 of 194 . Reports None Technical Considerations . ( if any ) : Output from this business process sent to other functions.

Sr. No. of AS-IS document 3.1 Flow Chart of Business Process : Date : General Requirements/Expectations Description The obsolete / damaged stock is valued at Zero value or at the net realizable rate that can be fetched from the market.Stock Valuation .1.Obsolete / Damaged Stock Name of Business Process : General Ledger Accounting Module Finance Submodule GL. More detailed explanation will be provided during the User testing & User training phase of the Project. The detailed process is explained in the MM TO-BE document.Obsolete / Damaged Stock Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr.Obsolete / Damaged Stock Version no of document: 2.1.38 Ref. variations and exceptions Good issue Potential Gaps: None Potential Gap Resolution: None System Configuration Considerations Required configuration has already been covered in the above processes. Process Variations and Exceptions The obsolete / damaged stock will be scrapped at net realizable value or nil value as the case may be through Material management module. Process Step MB1A (551 Movement type) Explanation.38 Stock Valuation .1.IT CO LOGO Blue Print Document –Finance CLIENT LOGO 3.38 Stock Valuation . No of To-BE document 3. Detailed Process Description. Reports required related to business process Stock Valuation report Outputs required for this business process None Data Interface 81 of 194 . Separate GL accounts will be defined for the loss/gain on Stock revaluation and Capital items.

( if any ) : Output from this business process sent to other functions. Reports None Technical Considerations . Unit Bull Power Limited Electronics Signature 82 of 194 . Technical Considerations – Forms. Describe in details and attach the format in which data would be stored in the other system : Inputs/ data received from other function for this process. ( if any ) : User Roles and Authorizations Transaction posting authorisation will be given to limited set of users. Sign-off (Approval) for this document : Name of Team member M Harikrishna Organisation/Bus.Conversion Requirements None Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements None Business Benefits Accounting will be done in SAP in proper way.IT CO LOGO Blue Print Document –Finance CLIENT LOGO Whether data records of current business process would be transferred to system other than SAP R/3 : No If Yes.

Excise JV functionality can also be used for posting the Excise differential. of AS-IS document 3. Process Variations and Exceptions Excise duty will be entered as per the excise document. variations and exceptions Excise JV Potential Gaps: None Potential Gap Resolution: None 83 of 194 .1. Sr.1 Flow Chart of Business Process : Submodule GL.40 Excise Differential (RTP) XYZ LIMITED Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr.Dr.1. Process Step J1IH Explanation.Cr. Detailed Process Description. then that proposed amount will be overwritten manually.40 Ref. When Bitumen/SKO is sourced from XYZ LIMITED Terminal other than a refinery location. sometimes the Cenvat benefit may be lesser than amount of excise duty recovered in the price charged by XYZ LIMITED.IT CO LOGO Blue Print Document –Finance CLIENT LOGO 3. No of To-BE document 3. Also. Cenvat Account………………. No.40 Excise Differential (RTP) XYZ LIMITED Name of Business Process : General Ledger Accounting Module Finance Version no of document: 2. More detailed explanation will be provided during the User testing & User training phase of the Project. Accounting entry for Excise Duty Reversal through Excise JV Cenvat Clearing………………. there is a difference in the Excise Duty which is charged in the commercial invoice which is on higher side as compared to actual cenvat document which is for lower amount. The detailed process has been explained in the MM TO-BE document.1.Excise Differential (RTP) XYZ LIMITED Date : General Requirements/Expectations Description Majority of Bitumen/SKO sourcing is made from XYZ LIMITED. Due to pricing difference at Terminal compared to refinery. If the excise amount proposed by the system is higher then the actual excise invoice.

Sign-off (Approval) for this document : Name of Team member M Harikrishna Organisation/Bus. ( if any ) : Output from this business process sent to other functions. Describe in details and attach the format in which data would be stored in the other system : Inputs/ data received from other function for this process. Reports None Technical Considerations .Conversion Requirements None Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements None Business Benefits Correct excise duty will be entered in the SAP. Technical Considerations – Forms. Reports required related to business process FBL3N-GL line item report FS10N-GL balance summary Outputs required for this business process None Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No If Yes. ( if any ) : User Roles and Authorizations Excise invoice posting authorisation will be given to limited set of users. Unit Bull Power Limited Electronics Signature 84 of 194 .IT CO LOGO Blue Print Document –Finance CLIENT LOGO System Configuration Considerations CIN related configuration has already been explained in the above sections.

No of To-BE document 3.41 Ref.1.IT CO LOGO Blue Print Document –Finance CLIENT LOGO 3. of AS-IS document 3. Describe in details and attach the format in which data would be stored in the other system : Inputs/ data received from other function for this process. ( if any ) : Output from this business process sent to other functions.41 Cash Flow Statement Name of Business Process : General Ledger Accounting Module Finance Submodule GL. Potential Gap Resolution: A new report will be developed to get the Cash flow statement. ( if any ) : 85 of 194 .1 Date : Flow Chart of Business Process : General Requirements/Expectations Description Cash Flow statement should be prepared at all the locations reflecting Cash inflow.1.1. Sr. Potential Gaps: Cash Flow statement is not readily available in the SAP systems. Process Variations and Exceptions Cash Flow statement is not readily available in the SAP systems.Cash Flow Statement Version no of document: 2. This is a GAP. outflow and balance. Detailed Process Description. No. System Configuration Considerations Reports required related to business process Cash Flow statement Outputs required for this business process None Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No If Yes.41 Cash Flow Statement Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr.

IT CO LOGO Blue Print Document –Finance CLIENT LOGO User Roles and Authorizations Transaction posting authorisation will be given to limited set of users. Technical Considerations – Forms. Unit Bull Power Limited Electronics Signature 86 of 194 . Sign-off (Approval) for this document : Name of Team member M Harikrishna Organisation/Bus. Reports None Technical Considerations .Conversion Requirements None Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements None Business Benefits Accounting will be done in SAP in proper way.

the liability will be discharged through Bank entry. Dr Bank A/c………………………………. No.1. EPF payable etc.42 Payroll Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr.42 Payroll Name of Business Process : General Ledger Accounting Module Finance Version no of document: 2. of AS-IS document 3.1 Flow Chart of Business Process : Submodule GL.1. Sr. Separate GL account will be created in SAP for each of the salary item like Professional tax payable. then vendor code will be created for those employees. Process Variations and Exceptions The salary will be entered in the SAP system through journal voucher.42 Ref.Payroll Date : General Requirements/Expectations Description The Payroll processing is done through a separate outsourcing agency. No of To-BE document 3. ESIC payable.2.1.IT CO LOGO Blue Print Document –Finance CLIENT LOGO 3. Interest will be calculated for the advances as per the interest indicator mentioned in the master data. First all the expenses will be accounted in SAP through Journal voucher and once salary is paid.2 87 of 194 . TDS will also be accounted for along with the ESIC & EPF. Cr If the payments to some of the employees are to be done through system generated cheques.. Detailed Process Description. The employees portion of EPF & ESIC will also be accounted along with the salary. If the advance to employees is to be shown employee wise. Salary-BPE A/c TDS on Salaries A/c Professional Tax Payable A/c ESIC Payable A/c EPF Payable A/c Advance to Employees A/c Salary BPE Payable A/c Dr Cr Cr Cr Cr Cr Cr The payment entry in SAP will be as mentioned belowSalary BPE Payable A/c……………. then separate vendor code needs to be created in SAP to whom the advance is given and advance will be entered in the system through special GL indicator. Payment will be generated for them as per the process explained in section 3. Basis the inputs provided by the HR dept the outsourced company prepares the salary register.

Potential Gap Resolution: Necessary enhancement will be done to upload the Payroll in SAP. EPF. variations and exceptions Enter GL account document CLIENT LOGO Process Step FB01 / FB50 Potential Gaps: SAP does not provide the functionality of Payroll upload. Sign-off (Approval) for this document : Name of Team member Organisation/Bus. ( if any ) : User Roles and Authorizations Journal voucher transaction posting authorisation will be given to limited set of users.IT CO LOGO Blue Print Document –Finance Explanation.Conversion Requirements None Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements None Business Benefits Salary will be accounted in to the system along with all the components like TDS. Describe in details and attach the format in which data would be stored in the other system : Inputs/ data received from other function for this process. Unit Signature 88 of 194 . Reports None Technical Considerations . Technical Considerations – Forms. ESIC etc. System Configuration Considerations None Reports required related to business process FBL3N-GL line item report FS10N-GL balance summary Outputs required for this business process None Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No If Yes. ( if any ) : Output from this business process sent to other functions.

Interest indicator will be maintained in the vendor master data.1 Date : Flow Chart of Business Process : General Requirements/Expectations Description During the setup of new plants in the process of expansion at various states.1.43 Issue of Bank Guarantee Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr. variations and exceptions Enter GL account document Potential Gaps: None Potential Gap Resolution: None System Configuration Considerations Required configuration has already been covered in the above processes. beneficiary name.43 Issue of Bank Guarantee Name of Business Process : General Ledger Accounting Module Finance Submodule GL. 89 of 194 . amount. Accounting entry will be posted in the SAP for the Fixed deposit.Issue of Bank Guarantee Version no of document: 2. Interest accrued thereon will be accounted separately. The party in whose favour bank guarantee is issued will be created as Vendor. Process Variations and Exceptions The Bank Guarantee is secured by the Fixed deposit in the Bank. during the assessments. Also. expiry period etc. The details like Custodian name.1. Interest calculated by the system on the basis of interest indicator can be compared with the actual bank interest.. Process Step FB01 / FB50 Explanation. Sr. the Bank Guarantee may be required to be submitted for any demand raised by the tax depts. No. in some instances. for obtaining registration with the Tax Depts. Bank name. Detailed Process Description. will be available through GL line item report.1. No of To-BE document 3. The interest calculation will be done in the system only on the statistical basis. as per the respective states VAT Act.IT CO LOGO Blue Print Document –Finance CLIENT LOGO M Harikrishna Bull Power Limited Electronics 3. a Bank Guarantee for the specified amount needs to be provided in favour of the respective Tax Depts.43 Ref. of AS-IS document 3.

IT CO LOGO Blue Print Document –Finance CLIENT LOGO Reports required related to business process FBL3N-GL line item report FS10N-GL balance summary Outputs required for this business process None Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No If Yes. Sign-off (Approval) for this document : Name of Team member M Harikrishna Organisation/Bus. ( if any ) : Output from this business process sent to other functions. Describe in details and attach the format in which data would be stored in the other system : Inputs/ data received from other function for this process. ( if any ) : User Roles and Authorizations Transaction posting authorisation will be given to limited set of users. Technical Considerations – Forms. Unit Bull Power Limited Electronics Signature 90 of 194 .Conversion Requirements None Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements : None Business Benefits Fixed deposit related accounting will be done in SAP in proper way. Reports None Technical Considerations .

Potential Gaps: No option in available in SAP to generate the form of return as required by RBI notification giving information of Foreign Direct Investments & Other Investments like Trade Credit.1 Flow Chart of Business Process : Date : General Requirements/Expectations Description A report should be generated in the form of return (as required by RBI notification) giving information of Foreign Direct Investments & Other Investments like Trade Credit. The return is filed on or before 31st July for the pervious FY.39 RBI Return for Foreign Investments Name of Business Process : General Ledger Accounting Module Finance Submodule GL.1.1. Potential Gap Resolution: All the details required for RBI return will be available in SAP. Return will be filled in manually.. All the details required for RBI return will be available in SAP.44 Ref. No.IT CO LOGO Blue Print Document –Finance CLIENT LOGO 3.1.44 RBI Return for Foreign Investments Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr. System Configuration Considerations None Reports required related to business process None Outputs required for this business process 91 of 194 . Detailed Process Description. Sr. No of To-BE document 3. Process Variations and Exceptions RBI return for Foreign Investment is not available in SAP. of AS-IS document 3.RBI Return for Foreign Investments Version no of document: 2. This is a GAP.

Unit Bull Power Limited Electronics Signature 92 of 194 . ( if any ) : User Roles and Authorizations Report execution authorisation will be given to limited set of users.Conversion Requirements None Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements : None Business Benefits RBI return will be generated through SAP. ( if any ) : Output from this business process sent to other functions. Reports None Technical Considerations . Technical Considerations – Forms.IT CO LOGO Blue Print Document –Finance CLIENT LOGO RBI return in Prescribed format (not available in SAP) Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No Inputs/ data received from other function for this process. Sign-off (Approval) for this document : Name of Team member M Harikrishna Organisation/Bus.

Technical Assistance etc. the detail of all the transactions with the associated concern can be generated. Detailed Process Description.Vendor Line item display or FBL5N-Customer line item display. No. Process Variations and Exceptions Associated concern will be created in SAP as Customer/Vendor.45 Transactions with Associated Concerns Name of Business Process : General Ledger Accounting Module Finance Submodule GL. Spares.45 Transactions with Associated Concerns Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr. Method of Determining the arms length price. No of To-BE document 3. variations and exceptions Vendor line item display Customer line item display Potential Gaps: No report is available in SAP which shows the comparison of the item sold by associated concern to any other concern in India with the Item sold to BPE. The detail for the same is covered in the MM BBP document. the comparables of the other companies or details of the similar items sold by the associated concern to any other concern in India. Detail in the format of gross amount and taxes & duties separately can be derived from the Material Management report.1.1.45 Ref. Process Step FBL1N FBL5N Explanation. It contains information in respect of items Purchased/Nature of services received. Potential Gap Resolution: None System Configuration Considerations 93 of 194 . Custom valuation. Exchange Rate for converting into Indian Currency. Sr.IT CO LOGO Blue Print Document –Finance CLIENT LOGO 3. amount in Foreign Currency. Capital Equipments. of AS-IS document 3. By running the transaction code FBL1N.Transactions with Associated Concerns Version no of document: 2.1.1 Flow Chart of Business Process : Date : General Requirements/Expectations Description A report should be available to generate the information on International Transactions with associated concerns whether in respect of Raw Materials.

Reports None Technical Considerations .Conversion Requirements None Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements None Business Benefits All the Foreign currency transactions & reports can be viewed through SAP. Unit Bull Power Electronics 94 of 194 Signature . ( if any ) : User Roles and Authorizations None Technical Considerations – Forms.IT CO LOGO Blue Print Document –Finance CLIENT LOGO Reports required related to business process FBL3N-GL line item report FS10N-GL balance summary FBL5N-Customer line item report FBL1N-Vendor line item report Outputs required for this business process None Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No Inputs/ data received from other function for this process. Sign-off (Approval) for this document : Name of Team member M Harikrishna Organisation/Bus. ( if any ) : Output from this business process sent to other functions.

46 Security Deposits Received or Paid in excess of Rs. 000/. Sr. Report on the security deposit received or paid in excess of Rs. Max amount outstanding and the mode of payment etc. Detailed Process Description. 000/ Name of Business Process General Ledger Accounting Module Finance Submodule GL. PAN number.IT CO LOGO Blue Print Document –Finance Limited CLIENT LOGO 3. Security Deposits report. 000 Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr. of AS-IS document 3.1.Security Deposits Received or Paid in excess of Rs. Process Variations and Exceptions Security deposit entry will be done in SAP through special GL indicator.Party wise opening balance. receipts.in aggregate.can be generated by putting greater than 20000/.46 Security Deposits Received or Paid in excess of Rs. repayments and closing balance will be provided by the system.20. No of To-BE document 3. 000/ Version no of document: 2.20.20.condition in the amount field of transaction code FBL3N for the reconciliation account mentioned above. amount received or paid against Security Deposit during the FY. The report contains information like name of Vendor. 20000/. No. variations and exceptions Enter GL account document GL line item display Potential Gaps: None Potential Gap Resolution: None 95 of 194 .46 Ref.1. Process Step FB01 / FB50 FBL3N Explanation. Reconciliation account will be created with the option of line item display. Corresponding GL will have a separate reconciliation account.1 Flow Chart of Business Process : Date : General Requirements/Expectations Description A report will be generated giving details of those Vendors from whom Security Deposits are received or to whom Security Deposits are repaid for an amount of more than Rs.1.20.

( if any ) : Output from this business process sent to other functions. Reports None Technical Considerations . Unit Bull Power Limited Electronics Signature 96 of 194 . Technical Considerations – Forms.Conversion Requirements None Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements : None Business Benefits Accounting will be done in SAP in proper way.IT CO LOGO Blue Print Document –Finance CLIENT LOGO System Configuration Considerations None Reports required related to business process FBL3N-GL line item report FS10N-GL balance summary Outputs required for this business process None Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No Inputs/ data received from other function for this process. ( if any ) : User Roles and Authorizations Transaction posting authorisation will be given to limited set of users. Sign-off (Approval) for this document : Name of Team member M Harikrishna Organisation/Bus.

sample document can be used as reference document.1. No of To-BE document 3.47 Sample documents Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr. Their advantage is that you can change or enhance them. Detailed Process Description. They serve merely as data sources for an accounting document. variations and exceptions Enter GL account document 97 of 194 .Sample documents Date : General Requirements/Expectations Description If same natures of documents are used quite frequently without change.47 Ref. of AS-IS document : No Name of Business Process General Ledger Accounting Module Finance Version no of document: 2.1. You therefore use a sample document rather than an accounting document. They serve merely as data sources for an accounting document.1 Flow Chart of Business Process : Submodule GL. Process Variations and Exceptions In contrast to an accounting document.IT CO LOGO Blue Print Document –Finance CLIENT LOGO 3. Below mentioned is the process for posting the document with reference to Sample document:Determine the use of sample document • Determine the type of transaction and accounts for which sample document can be created • Create sample document • Approve/Authorize sample document • Use post with reference function • Enter the sample document number • Change the document if required • Simulate the document to see overview before posting • Post the document Sample document can be treated as template. • Process Step FB01 / FB50 Explanation. sample documents do not update transaction figures. Sr. No.

( if any ) : User Roles and Authorizations Establish Authorization for creating account assignment model.IT CO LOGO Blue Print Document –Finance CLIENT LOGO Potential Gaps: None Potential Gap Resolution: None System Configuration Considerations None Reports required related to business process None Outputs required for this business process None Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No Inputs/ data received from other function for this process.Conversion Requirements None Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements : None Business Benefits Using the sample document functionality repetitive efforts in putting the similar type of data can be avoided. ( if any ) : Output from this business process sent to other functions. Technical Considerations – Forms. Unit Signature 98 of 194 . Sign-off (Approval) for this document : Name of Team member Organisation/Bus. Reports None Technical Considerations .

1.IT CO LOGO Blue Print Document –Finance CLIENT LOGO M Harikrishna Bull Power Limited Electronics 3.1 Flow Chart of Business Process : Submodule GL. On receipt of missing information such as a narration. They will not have the authorization for posting those documents. Postings will be done by the authorized users only. There are two methods for parking a document • • From the GL Document entry Directly entering the document to be parked The data entered in the parked document is available for evaluation. Park document can be deleted using the SAP transaction code FBV0. Bank payments & Bank receipts entries will have authorization for the Parking the documents only. Detailed Process Description. But once park document is posted. checked and then posted at a later Date if necessary by a different data entry clerk. Parked documents can be completed. User preparing the Journal voucher entries.GL document parking & posting Date : General Requirements/Expectations Description Document parking is used to enter and store (park) incomplete documents. cost centre assignment call up the parked documents and do the final posting. of AS-IS document :No Name of Business Process General Ledger Accounting Module Finance Version no of document: 2.48 Ref. it cannot be deleted. 99 of 194 . No of To-BE document 3. without carrying out extensive entry checks. When documents are parked. Process Variations and Exceptions Parked documents can be posted either individually or via a list. business area.1. Sr. data is not updated.48 GL document parking & posting Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr. No.

Reports None Technical Considerations . variations and exceptions Park GL account document CLIENT LOGO Process Step FV50 FBV0 FB01 / FB50 Delete parked document Enter GL account document Potential Gaps: None Potential Gap Resolution: None System Configuration Considerations None Reports required related to business process FBL3N-GL line item report FS10N-GL balance summary Outputs required for this business process None Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No Inputs/ data received from other function for this process.Conversion Requirements 100 of 194 . ( if any ) : Output from this business process sent to other functions. Technical Considerations – Forms. ( if any ) : User Roles and Authorizations Park document functionality will be given to limited set of users.IT CO LOGO Blue Print Document –Finance Explanation.

101 of 194 .49 Document Split functionality Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr.1.IT CO LOGO Blue Print Document –Finance CLIENT LOGO None Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements : None Business Benefits Using the park document functionality. No.49 Ref.1 Flow Chart of Business Process : Submodule functionality Date : GL- Document split General Requirements/Expectations Description In BPE each of the plant will be treated as Profit center. To generate the Plant wise Profit & loss account and the Balance sheet each of the line item of the document should have the profit center. the entered data will be saved and while posting the document. Sign-off (Approval) for this document : Name of Team member M Harikrishna Organisation/Bus. No of To-BE document 3.1. Unit Bull Power Limited Electronics Signature 3. of AS-IS document :No Name of Business Process General Ledger Accounting Module Finance Version no of document: 2. Sr. there is no need to enter all that data again.

Dr Pctr02 Vendor…………………Cr 500 1500 General Ledger View – How a document appears only in GL view. the profit center in the line item will be derived through the cost center mentioned in the Expense line item.Dr Pctr01 1000 Expenses………………. – – Financial accounting document has two views – Entry view – How a document also appears in the subledger Vendor Invoice Expenses……………….Dr Pctr02 500 Vendor…………………Cr Pctr01 1000 Vendor…………………Cr Pctr02 500 Profit Center is assigned in the Cost center master data. Process Variations and Exceptions – – – – New functionality under New General Ledger in SAP Organizes line items in the financial documents according to selected dimensions like profit center For each financial accounting document. Eg during payment Active Split .The System creates clearing lines automatically to achieve a split.IT CO LOGO Blue Print Document –Finance CLIENT LOGO Detailed Process Description. Types of Document Split – Passive Split -During clearing the account assignments of the items to clear are inherited to the clearing line items.Dr Pctr01 1000 Expenses………………. 102 of 194 . line items are split on the basis of predetermined entity such as profit center in real time Financial statements can be created at profit center level. In the above example.System splits the documents on the basis of document Splitting Rules Zero Balance indicator . Vendor Invoice Expenses………………. The Vendor line item will automatically derive the profit center from the expense line item profit center.

IT CO LOGO Blue Print Document –Finance CLIENT LOGO Potential Gaps: None Potential Gap Resolution: None System Configuration Considerations Reports required related to business process None Outputs required for this business process None Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No Inputs/ data received from other function for this process. ( if any ) : Output from this business process sent to other functions. Profit center wise Balance sheet and Profit & loss can be easily derived through this functionality. ( if any ) : User Roles and Authorizations Technical Considerations – Forms.Conversion Requirements None Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements : None Business Benefits Each of the line item of the document will have the profit center. Sign-off (Approval) for this document : 103 of 194 . Reports None Technical Considerations .

Valuation of Foreign Currency items Date : General Requirements/Expectations Description 104 of 194 .IT CO LOGO Blue Print Document –Finance Organisation/Bus.1 Flow Chart of Business Process : Submodule GL.50 Ref. No of To-BE document 3. No. Sr.1.1. Unit Bull Power Electronics Limited Signature CLIENT LOGO Name of Team member M Harikrishna 3. of AS-IS document :No Name of Business Process General Ledger Accounting Module Finance Version no of document: 2.50 Valuation of Foreign Currency item Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr.

( if any ) : Output from this business process sent to other functions. the gain/loss is booked in to the realized gain/loss account maintained in the configuration.Customer balances 3.Balance Sheet items 2. Detailed Process Description. Process Variations and Exceptions Below mentioned three types of accounts maintained in the Foreign currency are to be revaluated at the end of every month:1. variations and exceptions Foreign Currency valuation Potential Gaps: None Potential Gap Resolution: None System Configuration Considerations Reports required related to business process None Outputs required for this business process None Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No Inputs/ data received from other function for this process. All the open items at the month end will be revaluated and the unrealized gain/loss on revaluation will be posted according to the GL account maintained in the customization. The exchange rate is maintained in the exchange rate table on the monthly basis as per the rates published by the RBI.Vendor balances In the customization.IT CO LOGO Blue Print Document –Finance CLIENT LOGO At the end of each month Foreign Currency item has to be revaluated. Whenever the Foreign currency items are paid off. Process Step F.05 Explanation. GL accounts are maintained for realized gain/loss and unrealized gain/loss. ( if any ) : 105 of 194 .

1. Reports None Technical Considerations . Sr. No of To-BE document 3. of AS-IS document :No Name of Business Process General Ledger Accounting Module Finance Version no of document: 2.1.1 Submodule GL.IT CO LOGO Blue Print Document –Finance CLIENT LOGO User Roles and Authorizations Technical Considerations – Forms. No.51 Ref.51 Clear GL accounts Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr.Conversion Requirements None Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements : None Business Benefits Sign-off (Approval) for this document : Name of Team member M Harikrishna Organisation/Bus.Clear GL accounts Date : 106 of 194 . Unit Bull Power Limited Electronics Signature 3.

( if any ) : User Roles and Authorizations Technical Considerations – Forms. ( if any ) : Output from this business process sent to other functions.IT CO LOGO Blue Print Document –Finance CLIENT LOGO Flow Chart of Business Process : General Requirements/Expectations Description GL accounts needs to be cleared on periodic basis. variations and exceptions Clear GL accounts Potential Gaps: None Potential Gap Resolution: None System Configuration Considerations Reports required related to business process None Outputs required for this business process None Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No Inputs/ data received from other function for this process.Posting date 4. Others Process Step FB1S Explanation. Detailed Process Description. Reports 107 of 194 .Document type 6.Reference 5.Amount 2.Tax code 7.Document number 3. Process Variations and Exceptions GL accounts maintained on the open item management account needs to be cleared on periodic basis which is a manual process. GL accounts can be cleared on the basis of the below mentioned criteria:1.

of AS-IS document 3.1 Advance Receipts Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr.1 Advance Receipts Name of Business Process : Accounts Receivable Module Finance Version no of document: 2. No.2. No of To-BE document 3.2.IT CO LOGO Blue Print Document –Finance CLIENT LOGO None Technical Considerations . Sign-off (Approval) for this document : Name of Team member M Harikrishna Organisation/Bus.Conversion Requirements None Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements : None Business Benefits GL accounts can be cleared on periodic basis. Sr.2.Advance Receipts Date : 108 of 194 .1 Submodule AR. Unit Bull Power Limited Electronics Signature Accounts Receivable:3.1 Ref.

Dr Customer A/c …………………Cr The Customer a/c will show a credit balance till the delivery of material is made by BPE by way of an invoice. This allows the user to post the document to an alternative GL account instead of “normal” customer’s reconciliation account. When the supply will be made. both the documents (Payment and Invoice document) will be open. This amount is shown separately under Balance sheet as Liability through that account. They are defined in configuration for Customers reconciliation accounts. This is possible due to SAP functionality of Special GL indicators. Once both the items are cleared. Detailed Process Description. Customer aging report will also be available from the system. Both the open item can be cleared using transaction code F-32.IT CO LOGO Blue Print Document –Finance CLIENT LOGO Flow Chart of Business Process : General Requirements/Expectations Description The customer makes the payment on advance basis (normally by DD. Process Variations and Exceptions In SAP advance receipt is called as down payment. Process Step F-29 VA01 VF01 F-32 Explanation. The customer ledger will show the advance receipt document and the Invoice entered subsequently. Once the Invoice is entered in to the system through SD module. the advance cash receipt punched earlier will be adjusted against the invoice delivered.. Down Payment in SAP allows to post to another GL account which is called as Down payment from Customer. the advance receipt document will be updated with the Invoice document number and the Invoice document will be updated in the advance receipt document in the reference field. occasionally by cheque as per the authorizations in LAM) before the supply is taken. variations and exceptions Down payments Enter Customer Sales Order (Done in SD module) Enter Customer Billing document (Done in SD module) Clear Open Items Potential Gaps: None 109 of 194 .. The down payments are used for • • • Short term or medium term financing Shown separately on the balance-sheet as liability Reminds by the system when entering the invoice An accounting entry will be passed in the system by debiting the Bank a/c and crediting the Customer a/c with special GL indicator as follows: Bank clearing A/c …………………….

FD10N.Customer balance report . FBL5N-Cutomer line item report 2.Conversion Requirements None Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements : None Business Benefits 1. Special GL indicator configuration 2. ( if any ) : User Roles and Authorizations Transaction posting authorisation will be given to limited set of users. System prompts the message while entering the Invoice. Alternative GL account assignment instead of normal reconciliation account. ( if any ) : Output from this business process sent to other functions. that down payment is already received. Outputs required for this business process None Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No Inputs/ data received from other function for this process. Down payments are identified separately from the normal payment.IT CO LOGO Blue Print Document –Finance CLIENT LOGO Potential Gap Resolution: None System Configuration Considerations 1. 2. Sign-off (Approval) for this document : Name of Team member M Harikrishna Organisation/Bus. Reports required related to business process 1. Technical Considerations – Forms. Reports None Technical Considerations . Unit Bull Power Electronics 110 of 194 Signature .

2 Receipts against Credit Supplies Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr.2 Ref.2. No. No of To-BE document 3. Sr.2.2. of AS-IS document 3.1 Date : 111 of 194 .2 Receipts against Credit Supplies Name of Business Process : Accounts Receivable Module Finance Submodule AR.Receipts against Credit Supplies Version no of document: 2.IT CO LOGO Blue Print Document –Finance Limited CLIENT LOGO 3.

the open invoices will be selected and Invoice against which the payment is received will be cleared. The Customer Ledger/Statement showing the details of Invoices raised & payment received will be provided through the SAP system. the accounting entry will be posted automatically in the Finance module. Separate GL accounts needs to be defined for the discount given to the Customers. Customer ageing report will be based on the date of invoice. Detailed Process Description. Once both the items are cleared. Process Variations and Exceptions Once the customer Invoice is entered in to system through SD module. Cheques. both the open items (Invoice & payment document) can be cleared manually using transaction code F-32. against the incoming payment. Amount 2. Discount given will be shown separately in the financial statement. The customer ledger will show the Invoice document and the Payment receipt document. Document type 5.g. Reference The details of Bank Guarantee & Letter of Credit will be maintained in the Customer master data. If the incoming payments are entered without clearing the open item.D. Incoming payment from customer received later as per the credit terms will be accounted for in SAP using the T. variations and exceptions Post Incoming payments 112 of 194 . etc. D. Document number 3. the receipt document will be updated with the Invoice document number and the Invoice document will be updated in the payment receipt document in the reference field. Customer can be cleared separately based on one of the criteria mentioned below:1. Dunning area 6. Process Step F-28 Explanation. Code F-28: At the time of posting the above transaction. Posting date 4.IT CO LOGO Blue Print Document –Finance CLIENT LOGO Flow Chart of Business Process : General Requirements/Expectations Description The receipts from customers against the supplies made on credit basis will be accounted by way of a receipt voucher tagging to the individual outstanding invoice on FIFO basis. The system will provide the detail on the nature of payment received from Customer e.

IT CO LOGO Blue Print Document –Finance Clear customer Clear customer CLIENT LOGO F-32 FB1D Potential Gaps: None Potential Gap Resolution: None System Configuration Considerations Following are to configured in the SAP:1. 113 of 194 . ( if any ) : Output from this business process sent to other functions. Dunning procedure 6. ( if any ) : User Roles and Authorizations Transaction posting authorisation will be given to limited set of users. House Bank 5. Terms of Payment 2. Dunning Clerk Reports required related to business process FBL5N-Customer line item report FD10N-Customer balance report Outputs required for this business process None Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No Inputs/ data received from other function for this process. Tolerance group 4. Payment method 3.

Unit Bull Power Limited Electronics Signature 114 of 194 .IT CO LOGO Blue Print Document –Finance CLIENT LOGO Technical Considerations – Forms. only the Invoices against which the payment is due can be seen in the system by selection the option “open items only” in the customer line item report. After clearing the open item. Sign-off (Approval) for this document : Name of Team member M Harikrishna Organisation/Bus.Conversion Requirements None Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements : None Business Benefits Open Invoice documents can be cleared immediately at the time of posting the incoming payments. Reports None Technical Considerations .

Process Step FD32 FBL3N FBL5N FD10N Explanation.3 Bank Guarantee / Letter of Credit for Credit Supplies Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr.IT CO LOGO Blue Print Document –Finance CLIENT LOGO 3.1 Flow Chart of Business Process : Date : General Requirements/Expectations Description The Credit Supplies to the Customers will be secured either by a Bank Guarantee or a Letter of Credit for a specified amount. Detailed Process Description. of AS-IS document 3. Sr. claim period etc.Bank Guarantee / Letter of Credit for Credit Supplies Version no of document: 2. Process Variations and Exceptions The Bank Guarantee received from the customer will be entered in the SAP with a special GL indicator as a statistical entry.2. Before the due date of the bank guarantee. prompt message is not provided by the SAP.3 Ref.2. Report on the Bank Guarantee or a Letter of Credit can be generated using transaction code FBL3N for the reconciliation account mentioned above. The Bank Guarantee / Letter of Credit are invoked to settle the outstanding dues before the due date by sending a demand to the respective Bank along with the required documents. Interest factor consideration for credit limit check without passing the Interest entry in the system is not possible in the SAP. Potential Gap Resolution: 115 of 194 . No. variations and exceptions Customer credit limit management GL line item display Customer line item report Customer balance report Potential Gaps: 1. and will be posted as statistical entry.3 Bank Guarantee / Letter of Credit for Credit Supplies Name of Business Process : Accounts Receivable Module Finance Submodule AR. No of To-BE document 3. Corresponding reconciliation will have a separate GL account. Interest indicator will be maintained in the customer master data. 2. If the Customer had been provided a credit period. Amount. A report on the Bank Guarantees received from Customers will be provided through the system. then an interest will be posted for the delayed payments and the same will also be considered before releasing the supplies for the Customers inline to the Bank Guarantee limits. due date. The report will have all the details entered at the time of document posting such as Bank name. The supplies will be affected to the Customer to the extent of these specified limits and no supplies would be honored beyond the same. GL account will be created with the option of line item display. Interest will be calculated on the Customer level.2.

Reports required related to business process FBL5N-Customer line item report FD10N-Customer balance report Outputs required for this business process None Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No User Roles and Authorizations Transaction posting authorisation will be given to limited set of users. Sign-off (Approval) for this document : Name of Team member M Harikrishna Organisation/Bus. Reports None Technical Considerations . Unit Bull Power Electronics 116 of 194 Signature . Special GL indicator G & L defined in standard SAP can be used for Bank Guarantee & Letter of Credit respectively. Credit limit has to be checked manually in that case. Alternative GL account is to be configured for Customer. Development needs to be done to provide the early message of the bank guarantee expiry due date. Technical Considerations – Forms.Conversion Requirements None Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements : None Business Benefits SAP will always check the Credit limit of the customer before releasing the delivery.IT CO LOGO Blue Print Document –Finance CLIENT LOGO 1. Define the special GL indicator for Bank Guarantee & Letter of Credit. 2. 2. Interest factor consideration for credit limit check without passing the Interest entry in the system is not possible in the SAP. System Configuration Considerations 1.

2. The master bill of exchange document will be prepared for all the invoices for the respective customer. No of To-BE document 3. the customer open item will be cleared. a letter is addressed by BPE to the Customer along with the details of supplies to release the payment for the same within the due date (Credit Period extended) to the Bank and an acceptance for the same is obtained from the Customer. variations and exceptions Post Incoming payments Clear customer Potential Gaps: None 117 of 194 .2.4 Bill Discounting (BOE) Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr. the bills along with the acceptance letter of Customer to pay to the Bank are submitted to the Bank for discounting the same at an agreed rate. Under this arrangement. No. The bill discounting charges will also be accounted for.2. Customer wise BOE detail can be generated from the system using the Customer GL line item report. The Block has to be put manually in the customer master data. This master BOE will be identified by a separate number.4 Bill Discounting (BOE) Name of Business Process : Accounts Receivable Module Finance Submodule AR. of AS-IS document 3.2.4 Ref. so that no further supply can be made to that customer. Process Variations and Exceptions The payment received from the bank will be accounted into the system through the procedure mentioned in the section 3. Contingent liability can be posted in to the system through statistical posting using special GL indicator. Customer master can be blocked at the sales area level. If the Customer does not pay to the bank as per the due date. Detailed Process Description.IT CO LOGO Blue Print Document –Finance Limited CLIENT LOGO 3. Process Step F-28 F-32 Explanation. Journal entry will be passed for the Bank charges absorbed by BPE and the Bank charges recovered from the customer. Once the customer Invoice is entered in to system through SD module.2.Bill Discounting (BOE) Version no of document: 2. the accounting entry will be posted automatically in the Finance module. After the supply is made. the payments for credit supplies are received by an arrangement between Customer and BPE and mutually agreed Bank.1 Date : Flow Chart of Business Process : General Requirements/Expectations Description In some instances. immediately after the supply is made or within the credit period extended to the Customer. Once the payment is received from the bank on behalf of customer. Sr.

( if any ) : User Roles and Authorizations Transaction posting authorisation will be given to limited set of users. Technical Considerations – Forms. Sign-off (Approval) for this document : Name of Team member M Harikrishna Organisation/Bus. Unit Bull Power Limited Electronics Signature 118 of 194 . Reports None Technical Considerations .Conversion Requirements None Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements : None Business Benefits Customer account will be managed in better way through Bill discounting related postings and clearing of outstanding. ( if any ) : Output from this business process sent to other functions.IT CO LOGO Blue Print Document –Finance CLIENT LOGO Potential Gap Resolution: None System Configuration Considerations None Reports required related to business process FBL5N-Customer line item report FD10N-Customer balance report Outputs required for this business process None Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No Inputs/ data received from other function for this process.

1 Flow Chart of Business Process : Date : General Requirements/Expectations Description The Customer at rare instances. Reports required related to business process FBL3N-GL line item report 119 of 194 . variations and exceptions Post Incoming payments Enter GL account document Potential Gaps: None Potential Gap Resolution: None System Configuration Considerations Required configuration has already been covered in above processes.2.5 Inter Branch Receipt Accounting Name of Business Process : Accounts Receivable Module Finance Submodule ARAccounting Inter Branch Receipt Version no of document: 2. the profit center will be entered of the location from whom the supplies were made. Sr.5 Ref.IT CO LOGO Blue Print Document –Finance CLIENT LOGO 3. No.1. But while accounting for the receipt. Detailed Process Description. Process Step F-28 FB01 / FB50 Explanation. of AS-IS document 3.2. Process Variations and Exceptions Such payments will be deposited into the receiving locations Bank account as normal cheque deposits are done. provides the payments to locations. where actually the supplies were made by some other location.2. Through this the receipt from Customer will be reflected in the location on behalf of which payment is received. Incoming payments will be accounted for in the system as per the procedure mentioned in the section 3.2. Please refer section 3.2.5 Inter Branch Receipt Accounting Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr. No of To-BE document 3.13 for detailed explanation.

Technical Considerations – Forms.Conversion Requirements None Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements : None Business Benefits Customer will receive the credit even if the payment is received at some other location and net balance of the inter branch adjustment account will always be nil. ( if any ) : Output from this business process sent to other functions. Unit Bull Power Limited Electronics Signature 120 of 194 . Sign-off (Approval) for this document : Name of Team member M Harikrishna Organisation/Bus.IT CO LOGO Blue Print Document –Finance CLIENT LOGO FS10N-GL balance summary FBL5N-Customer line item report FBL1N-Vendor line item report Outputs required for this business process None Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No Inputs/ data received from other function for this process. Reports None Technical Considerations . ( if any ) : User Roles and Authorizations Transaction posting authorisation will be given to limited set of users.

In this case. No. No of To-BE document 3. in whose master data Interest indicator is maintained. Data from Account Master Record 2.2. 121 of 194 . Specifications made for interest calculation run Interest Calculation Period: The determination of interest calculation period can be in two ways 1. You can define these rules either per account or per interest indicator. The balance interest calculation program is controlled using the following specifications: 1.1 Date : Flow Chart of Business Process : General Requirements/Expectations Description Interest at specified rate should be calculated on the outstanding amount beyond the credit limit period specified.6 Ref.IT CO LOGO Blue Print Document –Finance CLIENT LOGO 3. of AS-IS document 3.6 Interest on Delayed Payments Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr. Sr. For calculating the interest on the overdue payment Interest indicator and interest cycle will be defined in the customer master data.2. Process Variations and Exceptions Terms of payment will be maintained and assigned in the customer master data. Interest will be calculated by the system only for the customer. the system determines the period according to rules you have specified. Specification stored under interest indicator 3. Manually for every interest calculation run 2.6 Interest on delayed payment Name of Business Process : Accounts Receivable Module Finance Submodule AR.2. Payment terms will have the payment due date.Interest on delayed payment Version no of document: 2. Automatically . Detailed Process Description.

Define interest indicator 3. ( if any ) : User Roles and Authorizations Transaction posting authorisation will be given to limited set of users.Cr Interest calculation can be done for single customer or for all the customer together. Define payment terms 2. Potential Gap Resolution: A new report will be developed to provide the Interest calculation report in the BPE format. Process Step FINT Explanation.IT CO LOGO Blue Print Document –Finance CLIENT LOGO Interest will be entered in to the system only when it is received :Customer A/c ……….e. Define interest calculation cycle Reports required related to business process FBL5N-Customer line item report FD10N-Customer balance report Outputs required for this business process None Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No Inputs/ data received from other function for this process.. Technical Considerations – Forms. Reports None Technical Considerations . Interest rates are defined in the system with respect to the validity date. System Configuration Considerations 1. variations and exceptions Item Interest calculation Potential Gaps: SAP provides the interest calculation output format in the standard format.Dr Interest received A/c …..Conversion Requirements None Technical Considerations – Interface Requirements None 122 of 194 . Interest rates are time bound i. ( if any ) : Output from this business process sent to other functions.

Sign-off (Approval) for this document : Name of Team member M Harikrishna Organisation/Bus. Unit Bull Power Electronics Limited Signature 123 of 194 .IT CO LOGO Blue Print Document –Finance CLIENT LOGO Technical Considerations – Enhancements None Technical Considerations – Workflow requirements : None Business Benefits Accounting will be done in SAP in proper way.

IT CO LOGO Blue Print Document –Finance CLIENT LOGO 3. of AS-IS document 3. Proportionately the service tax is taken care off.1 Flow Chart of Business Process : Submodule AR.Debit & Credit Notes Date : General Requirements/Expectations Description The Debit Notes & Credit Notes are given to the customer a/c’s when the Basis Rates on the invoice are under/over charged.2. if the customer acknowledges a shortage in material supplied. If the Customer doesn’t provide the Form-C the differential tax along with the interest will be recovered from the customer by raising the debit note to the customer .2. a credit note will be given to the customer proportionate to the invoice value & the same will be recovered from the Vendor (Transporter) A/c. The debit note will be raised from the Finance module. No of To-BE document 3. Credit memos can be posted directly through Finance module in case of rate differences.2. Please refer SD BBP document for detailed explanation. variations and exceptions Customer Credit memo Enter GL account document Vendor Credit memo Potential Gaps: None Potential Gap Resolution: 124 of 194 . But in that case it will have only the amount related adjustments and will not have any quantity effects. wrong charge of taxes. In certain cases of delivered supplies.7 Ref. Detailed Process Description.7 Debit & Credit Notes Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr. Process Step FB75 FB01 / FB50 FB65 Explanation. No. Sr.7 Debit & Credit Notes Name of Business Process : Accounts Receivable Module Finance Version no of document: 2. Process Variations and Exceptions In the integrated SAP system the credit memos are created in SD (Sales and Distribution) module in case of sales return and sent to Accounts Receivable component of Financial Accounting (FI-AR). freight etc. Subsequent supply to the Customer will be done at the full rate through change in the Customer master data & Sales order (through SD module). The payment to the transporter for transportation will be made for the net quantity delivered at Customer’s site.

( if any ) : Output from this business process sent to other functions.Conversion Requirements None Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements : None Business Benefits 1. Reports required related to business process FBL5N-Customer line item report FD10N-Customer balance report Outputs required for this business process None Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No Inputs/ data received from other function for this process. Reports None Technical Considerations .IT CO LOGO Blue Print Document –Finance CLIENT LOGO None System Configuration Considerations Required configuration has already been covered in above processes. Unit Bull Power Electronics 125 of 194 Signature . Appropriate accounting treatment will be given to the CST. 2. Sign-off (Approval) for this document : Name of Team member M Harikrishna Organisation/Bus. ( if any ) : User Roles and Authorizations Transaction posting authorization will be given to limited set of users. Technical Considerations – Forms. Appropriate accounting treatment will be given to the customer & vendor account.

Detailed Process Description.2. Please refer SD BBP document for detailed explanation. No of To-BE document 3. the same can be booked as bad debts after getting the required approval. If the Customer does not return the entire quantity and does not pay for the quantity retained by him.IT CO LOGO Blue Print Document –Finance Limited CLIENT LOGO 3. VAT etc. Potential Gaps: None Potential Gap Resolution: None System Configuration Considerations None Reports required related to business process FBL5N-Customer line item report FD10N-Customer balance report 126 of 194 . Sales order (type RE) and Billing document (type G2) will be created for reversal. No.1 Flow Chart of Business Process : Submodule AR. A reversal for the quantity of sales will be made in the system which reverses the entire entry of sales by crediting the customer and debiting the Sales A/c.8 Sales Return Name of Business Process : Accounts Receivable Module Finance Version no of document: 2. Reversal Billing document will have the reversal accounting entries.2. Excise Duty.Sales Return Date : General Requirements/Expectations Description The Sales returns from Customers would effect due to quality complaints or any other issues such as lack of storing capacity at Customer’s site. Process Variations and Exceptions Sales will be reversed through Sales & Distribution module.8 Ref.2.8 Sales Returns Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr. of AS-IS document 3. Sr.

Reports None Technical Considerations . Technical Considerations – Forms.Conversion Requirements None Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements : None Business Benefits Accounting will be done in SAP in proper way. ( if any ) : Output from this business process sent to other functions. Sign-off (Approval) for this document : Name of Team member M Harikrishna Organisation/Bus. ( if any ) : User Roles and Authorizations Transaction posting authorisation will be given to limited set of users. Unit Bull Power Limited Electronics Signature 127 of 194 .IT CO LOGO Blue Print Document –Finance CLIENT LOGO Outputs required for this business process None Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No Inputs/ data received from other function for this process.

Bad Debts & Provisions Version no of document: 2. Noted items can be seen through customer line item report FBL3N by selecting the option Noted item display.. No.9 Bad Debts & Provisions Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr. variations and exceptions Enter GL account document Potential Gaps: None Potential Gap Resolution: None 128 of 194 . of AS-IS document 3... On the basis of the inputs and approvals received. The report is reviewed at the time of Book Closure and the entries are journalized in the system.39 Bad Debts & Provisions Name of Business Process : Accounts Receivable Module Finance Submodule AR.IT CO LOGO Blue Print Document –Finance CLIENT LOGO 3.. the entries for bad debts are accounted in the system inline to the company’s policy. Sr.Cr Bad debts written off will be posted as noted item in Customer account to keep a track on the Customer. Bad Debts A/c …………………….2. The Provision for Doubtful Debts is passed in the system basis the ageing report of the customer accounts through manual Journal voucher. Detailed Process Description. Process Step FB01 / FB50 Explanation.1 Date : Flow Chart of Business Process : General Requirements/Expectations Description The debit balance in the customer accounts are provided by the Finance dept and reviewed by the Marketing Dept.1. Process Variations and Exceptions Bad debts will be accounted in SAP through Journal vouchers.39 Ref.1.Dr Customer A/c ……………………. No of To-BE document 3.

Technical Considerations – Forms.IT CO LOGO Blue Print Document –Finance CLIENT LOGO System Configuration Considerations None Reports required related to business process FBL5N-Customer line item report FD10N-Customer balance report Outputs required for this business process None Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No Inputs/ data received from other function for this process. Unit Bull Power Limited Electronics Signature 129 of 194 .Conversion Requirements None Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements : None Business Benefits Accounting will be done in SAP in proper way. Sign-off (Approval) for this document : Name of Team member M Harikrishna Organisation/Bus. Reports None Technical Considerations . ( if any ) : Output from this business process sent to other functions. ( if any ) : User Roles and Authorizations Transaction posting authorisation will be given to limited set of users.

No of To-BE document 3. you may be interrupted. it does not have to be complete. functionality should be available in SAP to store the entered data in SAP. and then continue with the document entry at a later time. Account balances are not updated and the document data is not available for evaluation.13 Ref. Detailed Process Description. variations and exceptions Enter Customer Invoice 130 of 194 .13 Customer Invoice document holding & posting Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr. Process Variations and Exceptions In this case. Sr. or you may not have all the data you need for entering a document. you can temporarily save the data you have entered.2. Process Step FB70 Explanation. No.IT CO LOGO Blue Print Document –Finance CLIENT LOGO 3. without giving the financial impact. of AS-IS document :No Name of Business Process : Account Receivable Module Finance Submodule AR.2.1 Date Flow Chart of Business Process : General Requirements/Expectations Description While entering the Customer Invoice directly through FI .Customer Invoice document holding & posting Version no of document:2. If you want the system to hold a document. A document number is not assigned.

Technical Considerations – Forms.Conversion Requirements None Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements : None Business Benefits 131 of 194 . ( if any ) : User Roles and Authorizations Hold document functionality will be given to limited set of users. ( if any ) : Output from this business process sent to other functions.IT CO LOGO Blue Print Document –Finance CLIENT LOGO Potential Gaps: None Potential Gap Resolution: None System Configuration Considerations Reports required related to business process Outputs required for this business process Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No Inputs/ data received from other function for this process. Reports None Technical Considerations .

1 Purchase of Material Bill Processing Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr. matching and posting) in the SAP system. No of To-BE document 3.IT CO LOGO Blue Print Document –Finance CLIENT LOGO Using the hold document functionality.1 Ref. of AS-IS document 3. 132 of 194 . The invoice can then alternatively be “Parked” or “Posted” into the system. Unit Bull Power Electronics Limited Signature Accounts Payable 3. No. when the PO number is entered. During invoice entry. The person entering the invoice will then have to confirm or change the value of the individual line items. the entered data will be saved and while posting the document.3.Purchase of Material Bill Processing Version no of document: 2. Sr.3. the system brings up the individual line items of the PO.1 Flow Chart of Business Process : Date : General Requirements/Expectations Description This sub-process covers the processing of vendor invoices (entering.3.1 Purchase of Material Bill Processing Name of Business Process : Accounts Payable Module Finance Submodule AP. Sign-off (Approval) for this document : Name of Team member M Harikrishna Organisation/Bus. there is no need to enter all that data again. Invoices with PO are processed through the ‘Logistics Invoice Verification’ sub-module of Materials Management.

it cannot be paid. An authorized employee has to monitor blocked invoices on a regular basis and take necessary action to resolve the same.……. Once the 133 of 194 . Vendor liability is created in the system by means of booking an Invoice. In the event of discrepancies or non-receipt of goods.Cr Releasing of blocked Invoices Blocking of invoices can be categorized into the following: 1. the system gives a suitable message. A listing of all such blocks can be extracted from the system and the same may be released for payment at one go.. Manual Blocks entered during document entry. can be predefined in the system. Tolerance Limit Tolerances for acceptable level of variances between the actual and invoiced quantity values etc. the system gives a message that the invoice is blocked for payment. payment method. If the discrepancy is within the specified tolerance limit. the purchase account functionality will be activated through valuation class in MM module.e. If the invoice as entered fully matches with the GRN. the system will block the invoice i. Purchase of raw material should also be shown in the P&L statement. Process Variations and Exceptions Logistic Invoice Verification It is a procedure through which Vendor Invoices are booked in the system by performing a match between the PO rates and the Invoice values.Delivery Date An authorized employee will have to scrutinize all blocked invoices on a periodic basis and take corrective action to un-block the invoices...Rate variances 2.IT CO LOGO Blue Print Document –Finance CLIENT LOGO Detailed Process Description. Additional functions like booking “Subsequent Debits/Credits” are also provided for. the system posts the difference to a predefined ledger account and posts the invoice as ready for payment. Facilities like loading any additional costs to a material stock account or to an expense GL code are supported by the standard system. At the time of GR.. following entry will be passed by the system automatically:Raw material purchase A/c ……. Incase. Some instances whereby variances will arise are: 1. As per the schedule VI requirement. if the tolerance limits are exceeded then the Invoice gets blocked by default. For this. Unless there is a complete match between the invoice amount and the GRN(s). The invoices can be either “Parked” or “Posted. discounts etc get defaulted from the Vendor Master. These values are however modifiable at the invoice level. System generated Blocks during Invoice verification 2. The tolerance amount will be posted as discount to the vendor. This could either be accepting the difference or getting a credit note from the vendor.Quantity variances 3.Dr Change in stock A/c ……………………. The system provides a facility for setting up tolerance limits for invoice matching by employee or employee groups. Data pertaining to payment terms.

t Purchase order v/s Invoice qty & value information Please refer MM BBP document for detailed explanation.IT CO LOGO Blue Print Document –Finance CLIENT LOGO discrepancy is resolved. excise duty & VAT Potential Gap Resolution: New report will be developed for requirements of 145A of IT Act for grossing up of CENVAT. which occur during Invoice verification. Process Step F-53 F-48 F. b.13 FB65 Explanation. A new report will be developed in MM module to provide the information w. the system removes the block and the invoice becomes free for payment. Any variances. a list of parked documents will be extracted from the system at the end of each accounting period and the relevant expenses accrued. ( if any ) : 134 of 194 . will result in the following a. Debit/Credit to the Stock accounts Debit/Credit to the Price Difference account in case of inadequacy of Stocks Subsequent Debit note to vendors are adjusted with the original Invoice. ( if any ) : Output from this business process sent to other functions. Since parked documents are not posted in FI. excise duty & VAT. System Configuration Considerations Payment term configuration Tax code configuration Document type configuration Reports required related to business process FBL1N-Vendor line item report FD10N-Vendor balance report Outputs required for this business process None Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No Inputs/ data received from other function for this process. variations and exceptions Post outgoing payment Post Vendor down payment Automatic clearing Credit memo Potential Gaps: Requirements of 145A of IT Act for grossing up of CENVAT.r.

3.IT CO LOGO Blue Print Document –Finance CLIENT LOGO User Roles and Authorizations Transaction posting authorisation will be given to limited set of users.1 Flow Chart of Business Process : Submodule AP. No of To-BE document 3.3.2 Name of Business Process : Accounts Payable Module Finance Version no of document: 2. 135 of 194 . Technical Considerations – Forms.2 Payment Process Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr.Conversion Requirements None Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements : None Business Benefits • Streamlining the process of Invoice booking • Adherence to the Purchase Order rates is maintained through the 3 way matching process. Variances if any. Reports None Technical Considerations . The payment can be done through manual process or through automatic payment process. Unit Bull Power Limited Electronics Signature 3. get routed to the stock or Price Difference accounts Sign-off (Approval) for this document : Name of Team member M Harikrishna Organisation/Bus.Payment Process Date : General Requirements/Expectations Description The Payment to the respective Vendors are released as per the due dates mentioned in the payment terms.

The system proposes Invoices for Payment based on user defined criteria e. which are paid through the Payment Run.e. Editing the payment proposal – This is a control step in the process wherein the proposal generated by the system is scrutinized by a Supervisor.IT CO LOGO Blue Print Document –Finance CLIENT LOGO Detailed Process Description. payment method etc. At the end of the payment run. Vendor range. Subsequently. The transaction is then posted as an FI document. A separate transaction needs to be executed for linking the payment document number with the cheque issued to the Vendor. The term “invoices due for payment” are those matched invoices processed in MM and those approved/unblocked invoices processed under FI-AP Module. A single cheque for multiple vendor invoices can be generated or alternatively. payable amount range etc. Process Variations and Exceptions Manual payment process:.Dr Bank clearing A/c ………. The other option is to use the Payment run and specify the payment method as ‘Manual Cheque’. payment methods and date of the next payment run. The cheque can be written out manually instead of being printed through the system. Editing can take the form of adding or deleting invoices/vendors from the proposal.Cr Automatic payment process:An automatic payment program in SAP is a useful tool and the most effective time saver in settling various vendor invoices due for payment.Manual payment can be done to vendor using transaction code F-53. Further. The payment document clears open Invoices. There are two options within this sub-process. The system also 136 of 194 .g. Open invoices are cleared against the payment entered. vendors etc. the cheque is written out manually. changing the bank. the individual Vendor accounts and the Bank account is up-dated. This also includes the desired posting date. Options for voiding of unused.. The accounting entry would be as follows: Vendor A/c ………………. priorities of House Banks can be configured so that the appropriate bank gets selected during the Payment run. due date. Manual cheques needs to be updated in to the system to keep track of cheque number. but does not print a cheque. Executing the payment run and payment media programs – The system posts the payments in FI i.. damaged or issued cheques are available in the above methods of payment. Each payment has to be entered as a separate transaction. Creating the payment proposal – The system proposes a Listing of invoices for payment which meet the specified parameters. each Invoice can be paidoff through individual cheques. the system posts the transactions in FI. The payment program consists of the following four steps: • • • • Enter parameter specification – this includes inputs for company codes. to include in the payment run.

All transactions including down payments are posted to the individual vendors’ accounts. it can be converted into an actual payment at which point accounting entries are posted. Simultaneously the Cheque register is also updated in the system. variations and exceptions Down payment request Post down payments 137 of 194 . The user has to then decide whether to adjust the down payment against the current invoice or not. Cheque register is automatically updated through every cheque payment entry. Advance/down payment to Vendors is treated as Special G/L transactions in SAP. Void cheque is also automatically updated in the cheque register and is shown separately. depending upon the nature of the transaction. The Vendor Ledger/Statement will be generated through the SAP system showing the details of all the Invoices & payment made. A register for total cheques (lot) received from the respective banks.IT CO LOGO Blue Print Document –Finance CLIENT LOGO prints the cheque and remittance advice. The payment program clears by subtracting the down payment amount from the corresponding invoice amounts and paying the difference. Down Payment:The down payments (advance payment) will be booked in the system through special GL indicator using the transaction code F-48. the net amount of the invoice is included in the subsequent payment run. the system displays a message that a down payment has been made to the vendor. then both the Invoice document & the partial payment document will be open till the further payment is done. The program clears the down payment automatically. The Vendor control account in the General Ledger is split into two – one for the regular transactions and another for down payments. Cheques will be printed automatically on the predefined stationary. utilisations and unused cheques in hand will be generated through the SAP system. Down payments can either be made manually or automatically. No accounting entries are generated in FI whenever a Down payment request is posted in the system. After the proposed payment is authorized. When the invoice received from the Vendor is entered. but these transactions are linked to two GL accounts. The control account for Down Payments can be classified as a ‘Current Asset’ in the Balance Sheet and the normal control account as a ‘Current Liability’. The total of the Vendor sub-ledger balances will agree with the total of the two control accounts in the GL. If the down payment is set-off against the invoice value. Process Step F-47 F-48 Explanation. A down payment request has to be created in the system if they have to be automatically included in the payment run. If the payment to Vendor is only partial. Advance payment clearing:The down payment with the invoice can be cleared directly when payment is made.

Reports None Technical Considerations . ( if any ) : User Roles and Authorizations Transaction posting authorisation will be given to limited set of users.Conversion Requirements None 138 of 194 .IT CO LOGO Blue Print Document –Finance Automatic payment run Vendor Line item report Vendor Balance display Display cheque Register CLIENT LOGO F110 FBL1N FK10N FCHN Potential Gaps: None Potential Gap Resolution: None System Configuration Considerations As explained above Reports required related to business process FBL1N-Vendor line item report FD10N-Vendor balance report Outputs required for this business process None Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No Inputs/ data received from other function for this process. Technical Considerations – Forms. ( if any ) : Output from this business process sent to other functions.

Sign-off (Approval) for this document : Name of Team member M Harikrishna Organisation/Bus. Priorities of banks in the Payment Run can be specified so that the appropriate bank gets selected.3 139 of 194 . Alternative payee is defined in the vendor master data.3. Alternate payees can be used in case if the cheques are to be printed in the name of a vendor other than the main vendor. No of To-BE document 3.IT CO LOGO Blue Print Document –Finance CLIENT LOGO Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements : None Business Benefits • • • • Bulk printing of cheques through the system Automatic selection of Invoices by the system based on user defined criteria like Vendor codes.3. Unit Bull Power Limited Electronics Signature 3. due dates amount or date limits etc.3 Bank Guarantee from Vendors Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr.

the Bank Guarantees are obtained for a specific amount from Transporters through whom the Finished Goods are transported to the Customer’s / Depot site.3.1 Flow Chart of Business Process : Date : General Requirements/Expectations Description The Bank Guarantees from the Vendors are accepted as a precaution for safe guard of their performances. A report on the Bank Guarantees received from Vendors (Service contractors & project contractors) with the details of Custodian. Detailed Process Description. System Configuration Considerations None Reports required related to business process None Outputs required for this business process None Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No Inputs/ data received from other function for this process. of AS-IS document 3. And the Bank Guarantees are obtained from Vendors of Capital Supplies for a specific amount to safe guard the performance of the Items supplied by them. ( if any ) : 140 of 194 . Sr. and Validity will be provided through the system.3 Bank Guarantee from Vendors Name of Business Process : Accounts Payable Module Finance Submodule Vendors AP- Bank Guarantee from Version no of document: 2.IT CO LOGO Blue Print Document –Finance CLIENT LOGO Ref. Process Variations and Exceptions Bank guarantee will be entered in to the system as statistical entry using special GL indicator. Vendor name. ( if any ) : Output from this business process sent to other functions. Normally. No. Potential Gaps: System prompt is not available for the Bank guarantee expiry notification. Amount. Potential Gap Resolution: Prompt message for the the Bank guarantee expiry notification will be provided in advance through development. Bank Name.

Reports None Technical Considerations .Conversion Requirements None Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements : None Business Benefits Vendor bank guarantee information will be available through the system. without any financial impact. Unit Bull Power Limited Electronics Signature 3. Technical Considerations – Forms. Sign-off (Approval) for this document : Name of Team member M Harikrishna Organisation/Bus.3.IT CO LOGO Blue Print Document –Finance CLIENT LOGO User Roles and Authorizations Transaction posting authorisation will be given to limited set of users.4 Letter of Credit Business Blueprint Document For SAP R/3 Implementation at BPE Date : 141 of 194 .

Process Step F-53 Explanation.Letter of Credit Date : General Requirements/Expectations Description Letter of Credit is arranged for foreign vendors who are not ready to accept the credit terms. amount. Reports required related to business process FBL1N-Vendor line item report FD10N-Vendor balance report Outputs required for this business process None Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : 142 of 194 . of AS-IS document 3.1 Flow Chart of Business Process : Submodule AP.39 Letter of Credit Name of Business Process : Accounts Payable Module Finance Version no of document: 2.1.3. No of To-BE document 3.IT CO LOGO Blue Print Document –Finance CLIENT LOGO Sr. Also additional information required will be available through Vendor line item report (FBL1N) More detailed explanation will be provided during the User testing & User training phase of the Project. LC register can be derived through GL line item report will be available through SAP with the details such as Vendor name. No.3. In SAP accounting entry is passed in to the system through the procedure mentioned in the manual payment section of 3.2. variations and exceptions Post outgoing payment Potential Gaps: None Potential Gap Resolution: None System Configuration Considerations Required configuration has already been covered in the above processes. Process Variations and Exceptions The payment is made by the Bank as per terms & conditions agreed in the LC which are debited to Bank A/c along with the Bank Charges after sending an advice to BPE. Bank etc. It is issued by BPE Banker to the Foreign Vendor for guaranteeing payments against consignments sent by them at our request. Sr.4 Ref. Detailed Process Description.Payment process.

Unit Bull Power Limited Electronics Signature 3. ( if any ) : Output from this business process sent to other functions.IT CO LOGO Blue Print Document –Finance CLIENT LOGO No Inputs/ data received from other function for this process.5 Payment against Document Business Blueprint Document For SAP R/3 Implementation at BPE 143 of 194 .3.Conversion Requirements None Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements : None Business Benefits Accounting will be done in SAP in proper way. Sign-off (Approval) for this document : Name of Team member M Harikrishna Organisation/Bus. ( if any ) : User Roles and Authorizations Transaction posting authorisation will be given to limited set of users. Technical Considerations – Forms. Reports None Technical Considerations .

Sr. The Bank in turn sends to BPE an import advice along with invoice copy and other documents to authorize them for debiting BPE account. exchange rate etc for debiting our account along with bank charges.3.1 Date : Flow Chart of Business Process : General Requirements/Expectations Description In certain cases. The purchases will be booked in Foreign currency. as soon as the foreign vendor ships the consignment. More detailed explanation will be provided during the User testing & User training phase of the Project. variations and exceptions Post outgoing payment Clear Vendor open item Automatic payment process Potential Gaps: LC Authorisation letter with the serial number is not available in SAP. Process Variations and Exceptions Purchase from Foreign Vendor will be booked through MM module.2 LC related entries will be done in SAP using special GL indicator.5 Payment against Document Name of Business Process : Accounts Payable Module Finance Submodule AP. No of To-BE document 3.IT CO LOGO Blue Print Document –Finance Date : CLIENT LOGO Sr. BPE there after send an authorization letter stating the account details of the Foreign Vendor. Reports required related to business process FBL1N-Vendor line item report FD10N-Vendor balance report Outputs required for this business process None 144 of 194 .3. In such case.3. Potential Gap Resolution: Development will be done to provide the autorization letter serially numbered. Process Step F-53 F-44 F110 Explanation. of AS-IS document 3. No. Detailed Process Description.5 Ref. Once payment is done by the Bank to the Foreign Vendor. the documents are sent to Banker for payment. the Vendor is agreed for payment against document terms instead of LC. System Configuration Considerations Required configuration has already been covered in the above processes.Payment against Document Version no of document: 2. Vendor account will be debited with credit to Bank clearing account and vendor open item will be cleared as explained in the section 3.

IT CO LOGO Blue Print Document –Finance CLIENT LOGO Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No Inputs/ data received from other function for this process. Unit Bull Power Limited Electronics Signature 145 of 194 . Technical Considerations – Forms. ( if any ) : User Roles and Authorizations Transaction posting authorisation will be given to limited set of users. ( if any ) : Output from this business process sent to other functions. Reports None Technical Considerations . Sign-off (Approval) for this document : Name of Team member M Harikrishna Organisation/Bus.Conversion Requirements None Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements : None Business Benefits Effective Audit trail of the Bills of exchange liability to Bank.

Process Variations and Exceptions In such case.50. This functionality is explained in the section 3.3.7 Inter Office Payments Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr. while posting the vendor payment entry.2-Payment process will be followed for such payments. which are made centrally at HQO Mumbai for which services or material is received at one or the other location.IT CO LOGO Blue Print Document –Finance CLIENT LOGO 3. The payment made by one location on behalf of another location will be tracked through Profit center.Inter Office Payments Date : General Requirements/Expectations Description There are certain payments. of AS-IS document 3.3. There will be no need of Inter office adjustment account.7 Inter Office Payments Name of Business Process : Accounts Payable Module Finance Version no of document: 2.1. profit center will be entered of the plant of which the payment has been done.3. Process Step F-53 F-28 Explanation. Detailed Process Description. The manual payment process as explained in the section 3. No. Sr.3. Reports required related to business process FBL1N-Vendor line item report FD10N-Vendor balance report Outputs required for this business process None 146 of 194 .7 Ref. variations and exceptions Outgoing Payments Incoming payment Potential Gaps: None Potential Gap Resolution: None System Configuration Considerations Required configuration has already been covered in above steps.1 Flow Chart of Business Process : Submodule AP. No of To-BE document 3.

IT CO LOGO Blue Print Document –Finance CLIENT LOGO Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No Inputs/ data received from other function for this process. ( if any ) : Output from this business process sent to other functions. ( if any ) : User Roles and Authorizations Transaction posting authorisation will be given to limited set of users. Technical Considerations – Forms.Conversion Requirements None Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements : None Business Benefits Accounting will be done in SAP in proper way. Sign-off (Approval) for this document : Name of Team member M Harikrishna Organisation/Bus. Unit Bull Power Limited Electronics Signature 147 of 194 . Reports None Technical Considerations .

No.2Payment process. can be overwritten by the user booking the import with reference to IGM date. Although the transaction can be posted in any currency like USD or Euro.8 Purchase Bill Processing – Imports Name of Business Process : Accounts Payable Module Finance Submodule AP. The exchange gain/loss will be calculated on the basis of difference between the document exchange rate & the month end exchange rate.Purchase Bill Processing – Imports Version no of document: 2. That foreign currency transaction needs to be booked in to system in currency INR as well. The system defaults the exchange rate from the exchange rate table based on the document posting date. through exchange rate table (maintained at the company code level) all the foreign currency transactions will be automatically converted in to INR by the system. Process Variations and Exceptions The payment to foreign vendor will be done through the procedure explained in the process 3.3.3. Detailed Process Description.1 Flow Chart of Business Process : Date : General Requirements/Expectations Description The Purchase Order on foreign Vendors is placed in foreign currency of the Country of supply.IT CO LOGO Blue Print Document –Finance CLIENT LOGO 3. Sr. The system will display a warning message at the bottom for the exchange rate difference.3.8 Purchase Bill Processing – Imports Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr.3. Exchange table is maintained on the monthly basis as per the RBI guidelines. Exchange rate can be maintained on daily basis also. 148 of 194 . of AS-IS document 3. More detailed explanation will be provided during the User testing & User training phase of the Project. No of To-BE document 3. Potential Gaps: None Potential Gap Resolution: None System Configuration Considerations Required configuration has already been covered in above steps.8 Ref. based on the Business requirements. Rate defaulted by the system.

Reports None Technical Considerations . ( if any ) : Output from this business process sent to other functions.Conversion Requirements None Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements : None Business Benefits Accounting will be done in SAP in proper way. Unit Bull Power Electronics Limited Signature 149 of 194 . ( if any ) : User Roles and Authorizations Transaction posting authorisation will be given to limited set of users. Technical Considerations – Forms. Sign-off (Approval) for this document : Name of Team member M Harikrishna Organisation/Bus.IT CO LOGO Blue Print Document –Finance CLIENT LOGO Reports required related to business process FBL1N-Vendor line item report FD10N-Vendor balance report Outputs required for this business process None Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No Inputs/ data received from other function for this process.

IT CO LOGO

Blue Print Document –Finance

CLIENT LOGO

3.3.9 Payment processing– Imports after credit period
Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr. No of To-BE document 3.3.9 Ref. Sr. No. of AS-IS document 3.3.9 Payment processing– Imports after credit period Name of Business Process : Accounts Payable Module Finance Submodule AP- Payment processing– Imports
after credit period

Version no of document: 2.1 Flow Chart of Business Process :

Date :

General Requirements/Expectations Description
In some instances, the purchases are made on credit term basis. In such cases, the consignments are received and there after the payment is made after verification of all documents like BOL/ACN, Packing list, certificate of origin, Invoice & MRR. An authorization is given to the Bank specifying the foreign currencies to be paid by debiting the Current Account.

Detailed Process Description, Process Variations and Exceptions
Payment to the Foreign vendor for the Import is done in two ways:1. Advance payment (down payment) 2. Payment after receipt of the goods The process for both the payments has been explained in detail in the section 3.3.2 (Payment Process). Payment to Vendor is done by the bank in the Foreign currency. Foreign currency amount will be the amount as per the purchase order. The exchange rate at the time of booking the Invoice may be different the exchange rate at the time of making payment. The difference payment due to exchange rate variation is booked as Foreign exchange gain/loss. The Foreign exchange gain/loss calculation process has been explained in the section 3.3.10. More detailed explanation will be provided during the User testing & User training phase of the Project.

Process Step
F-53

Explanation, variations and exceptions
Post outgoing payment

Potential Gaps:
None

Potential Gap Resolution:
None
150 of 194

IT CO LOGO

Blue Print Document –Finance

CLIENT LOGO

System Configuration Considerations
Required configuration has already been covered in above steps.

Reports required related to business process
FBL1N-Vendor line item report FD10N-Vendor balance report

Outputs required for this business process
None

Data Interface
Whether data records of current business process would be transferred to system other than SAP R/3 : No Inputs/ data received from other function for this process, ( if any ) : Output from this business process sent to other functions, ( if any ) :

User Roles and Authorizations
Transaction posting authorisation will be given to limited set of users.

Technical Considerations – Forms, Reports
None

Technical Considerations - Conversion Requirements
None

Technical Considerations – Interface Requirements
None

Technical Considerations – Enhancements
None

Technical Considerations – Workflow requirements : None Business Benefits
Accounting will be done in SAP in proper way. Sign-off (Approval) for this document : Name of Team member M Harikrishna Organisation/Bus. Unit Bull Power Limited Electronics Signature

151 of 194

IT CO LOGO

Blue Print Document –Finance

CLIENT LOGO

3.3.10 Exchange Fluctuations - Capital / Revenue
Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr. No of To-BE document 3.3.10 Ref. Sr. No. of AS-IS document 3.3.10 Exchange Fluctuations - Capital / Revenue Name of Business Process : Accounts Payable Module Finance Submodule AP- Exchange Fluctuations Capital / Revenue

Version no of document: 2.1 Flow Chart of Business Process :

Date :

General Requirements/Expectations Description
There could be a difference between the value of goods imported (based on purchase voucher or credit note) and the payment made against the same due to exchange fluctuation between the date of IGM and the date of payment. The difference has to be accounted.

Detailed Process Description, Process Variations and Exceptions
At month end, foreign currency valuation is carried out. This process valuates all transactions posted in foreign currency. To perform the valuation, enter an exchange rate for the end of the month. This valuation covers the following accounts and items:

1. Foreign currency balance sheet accounts
2. Open items posted in foreign currency (Vendors and customers) Below mentioned are the two options for the foreign currency valuation: a) Foreign currency valuation in local currency, (company code currency), b) Foreign currency valuation in parallel currency (for example, group currency). Since BPE will be having only one currency, so Foreign currency valuation will be in local currency INR only. Below mentioned three types of accounts maintained in the Foreign currency are to be revaluated at the end of every month:1.Balance Sheet items 2.Customer balances 3.Vendor balances In the customization, GL accounts are maintained for realized gain/loss and unrealized gain/loss. All the open items at the month end will be revaluated and the unrealized gain/loss on revaluation will be posted
152 of 194

Reports required related to business process FBL1N-Vendor line item report FD10N-Vendor balance report Outputs required for this business process None Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No Inputs/ data received from other function for this process.2-Payment process. Process Step F. The exchange rate is maintained in the exchange rate table on the monthly basis as per the rates published by the RBI. The balance in the customer accounts at the end of each month will be revaluated using SAP standard program and gain/loss on foreign exchange valuation will be accounted accordingly. This process is continued until the balance is cleared.IT CO LOGO Blue Print Document –Finance CLIENT LOGO according to the GL account maintained in the customization. ( if any ) : 153 of 194 . the gain/loss is booked in to the realized gain/loss account maintained in the configuration. The revaluation entry will be reversed at the start of the next month since the revaluation is done just for the month end reporting. On clearance of the balance actual gain/loss will be booked into the system.3. Whenever the Foreign currency items are paid off. System Configuration Considerations Required configuration has already been covered in above steps. ( if any ) : Output from this business process sent to other functions. variations and exceptions Foreign currency valuation Post outgoing payment Potential Gaps: Separate GL accounts for the exchange gain/loss on the capital purchases should be available from the system Potential Gap Resolution: This functionality will be tested during the configuration phase.05 F-53 Explanation. The payment to vendors will be done through the procedure explained in the process 3.

IT CO LOGO

Blue Print Document –Finance

CLIENT LOGO

User Roles and Authorizations
Transaction posting authorisation will be given to limited set of users.

Technical Considerations – Forms, Reports
None

Technical Considerations - Conversion Requirements
None

Technical Considerations – Interface Requirements
None

Technical Considerations – Enhancements
None

Technical Considerations – Workflow requirements : None Business Benefits
Accounting will be done in SAP in proper way. Sign-off (Approval) for this document : Name of Team member M Harikrishna Organisation/Bus. Unit Bull Power Limited Electronics Signature

154 of 194

IT CO LOGO

Blue Print Document –Finance

CLIENT LOGO

3.3.11 Payment of Duty on Imports
Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr. No of To-BE document 3.3.11 Ref. Sr. No. of AS-IS document 3.3.11 Payment of Duty on Imports Name of Business Process : Accounts Payable Module Finance Submodule AP- Payment of Duty on Imports Version no of document: 2.1 Date : Flow Chart of Business Process :

General Requirements/Expectations Description
The payment of duty being independent to payment to supplier. It is to be accounted for separately.

Detailed Process Description, Process Variations and Exceptions
The payment to vendors will be done through the procedure explained in the process 3.3.2-Payment process. Below mentioned accounting entries are passed for Import Procurement of Raw Material:During Customs Duty Clearing invoice Custom Clearing……….Dr. Custom Payable………..Cr. During GR Material Stock………… Dr. GR/IR clearing……….. Cr. During Excise Invoice Credit Cenvat Account………. Dr. Custom Clearing……… Cr. During Invoice Verification GR/IR Clearing………. Dr. Vendor Payable……… Cr. On payment of Custom duty, below mentioned accounting entry is passed:Custom Payable………..Dr.
155 of 194

IT CO LOGO

Blue Print Document –Finance

CLIENT LOGO

Bank clearing A/c……..Cr. On receipt of the bank statement or on the Bank upload, as the case may be following entry is passed:Bank clearing A/c……..Dr. Bank A/c……………...Cr. Basic Custom duty & cess thereon is added to the Inventory cost through condition types in purchase order in the Material Management module. Similarly CHA charges and port expenses are added to the inventory. The detail of CHA charges & port expenses will be available through respective GL accounts. Detailed process is explained in the MM BBP document. More detailed explanation will be provided during the User testing & User training phase of the Project.

Process Step
F-53 F-41

Explanation, variations and exceptions
Post outgoing payment with clearing Post without clearing

Potential Gaps:
None

Potential Gap Resolution:
None

System Configuration Considerations
None

Reports required related to business process
FBL3N-GL line item report

Outputs required for this business process
None

Data Interface
Whether data records of current business process would be transferred to system other than SAP R/3 : No Inputs/ data received from other function for this process, ( if any ) : Output from this business process sent to other functions, ( if any ) :

User Roles and Authorizations
Transaction posting authorisation will be given to limited set of users.

Technical Considerations – Forms, Reports
None

156 of 194

Unit Bull Power Limited Electronics Signature 157 of 194 .Conversion Requirements None Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements : None Business Benefits Import duty booking/payment can be traced easily. Sign-off (Approval) for this document : Name of Team member M Harikrishna Organisation/Bus.IT CO LOGO Blue Print Document –Finance CLIENT LOGO Technical Considerations .

IT CO LOGO Blue Print Document –Finance CLIENT LOGO 3.12 Service Vendor Payments:Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr. • Shipment document will be created after goods receipt against inbound delivery. The service PO will be entered. This would be quantity contract. No of To-BE document 3.3. • Inbound delivery will be created. Security Services.2-Payment process (manual).3.3. of AS-IS document 3. Procurement of material from Domestic Vendor Transport of goods cleared from port locations to plants Stock transport between various plants.14-Invoice processing without purchase order. COD. • Service order will be created against contract • Purchase order will be placed on vendor for material. • Transporter vendor’s payment will be processed against service entry sheet.3. • The shipment cost document will be created.12 Ref. Detailed Process Description. Inward/Outward Transportation :The transportation is used for following : 1. Process Variations and Exceptions Such expenses will be booked in to the system as per the procedure explained in section 3. Service entry sheet will get automatically created against service order as per the price maintained in condition record. The payment to such vendors will be done through the procedure explained in the process 3. & Contract Labour etc are to be accounted for in the system. 3. No. The goods receipt will be automatically posted. C&F Agents. Sr.3.1 Date : Flow Chart of Business Process : General Requirements/Expectations Description The payments to Service Vendors like Transportation.Service Vendor Payments Version no of document: 2. 4.12 Service Vendor Payments Name of Business Process : Accounts Payable Module Finance Submodule AP. 2. Delivery of the material to Customer The process will be as under: • The contract will be created with freight vendor with validity. Material Inventory Valuation: 158 of 194 .

CFA. The procedures of Quantity tracking. contract labour etc would be done as per the process explained in earlier business process. please refer the MM & SD BBP document. variations and exceptions Enter vendor Invoice Post outgoing payment Automatic payment Potential Gaps: None Potential Gap Resolution: None System Configuration Considerations None Reports required related to business process FBL1N-Vendor line item report FD10N-Vendor balance report Outputs required for this business process 159 of 194 . a separate debit/credit memo will be accounted through FI module.IT CO LOGO Blue Print Document –Finance CLIENT LOGO Freight. system will automatically copy the price from the price master and the same price will be transferred to the purchase order for transporter payment. The other service vendor payments like security. In case of loss of material in transit. There will be three types of payment process which need to be maintained for the transporter in the System. Per Metric Tone 3. revision of the prices are covered in MM & SD BBP documents. • Process Step F-43 F-53 F110 Explanation. Per Truck Full Load In case of BPE arranging the transporter for delivering material to their customer. In case of price change. will be defined as condition type and will be part of Pricing procedure to be used for material procurement. The invoice submitted by the Transporter would be matched & knocked off with the system number and then the payment is released. the transporter is debited for the loss of material and at the same time the customer will get credit with the amount which is derived by proportionate the total invoice value. if service order is settled with old rate. Per Kilometer / Per Ton 2. 1. For detailed explanation on the transportation functionality. Applicable TDS would be deducted while releasing the payment. • The price will be copied from the same price condition record used to calculate Freight cost . shortages. More detailed explanation will be provided during the User testing & User training phase of the Project.

Technical Considerations – Forms.Conversion Requirements None Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements None Business Benefits Accounting will be done in SAP in proper way. Sign-off (Approval) for this document : Name of Team member M Harikrishna Organisation/Bus. ( if any ) : Output from this business process sent to other functions. Unit Bull Power Limited Electronics Signature 160 of 194 . Reports None Technical Considerations .IT CO LOGO Blue Print Document –Finance CLIENT LOGO None Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No Inputs/ data received from other function for this process. ( if any ) : User Roles and Authorizations Vendor invoice entry & payment transaction posting authorisation will be given to limited set of users.

IT CO LOGO Blue Print Document –Finance CLIENT LOGO 3. has been covered as the separate business process in this Blue print document. Process Variations and Exceptions The capital purchases are routed booked through material management module as explained in the section 3.2. TDS on WCT.13 Capital Vendor Payments Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr.3.13 Capital Vendor Payments Name of Business Process : Accounts Payable Module Finance Submodule AP. It will have the separate tax rates than the normal tax rates.3. The balance 50% of input tax credit on capital items will be used in the next year. Internal order will be settled once the construction is completed.1 Date : Flow Chart of Business Process : General Requirements/Expectations Description Capital purchases / expenses are to be accounted for differently than the normal purchases. Through AUC settlement in CO. No of To-BE document 3. The purchases will be booked as “Capital Work in Progress A/c” through Internal order. Vendor Bill and the actual bill booked by way of a credit note. Process Step F-53 FB01 / FB50 FB65 Explanation. The payment procedure is explained in the section 3. Separate Tax codes will be defined for the composite tax. No. Sr. While making the payment to the Vendor a/c.3. various assets will be booked in FI as per the rules defined in the AUC settlement rule.3.13 Ref.3. Retention Money as per PO terms are made by way of a Debit Note to the Vendor A/c. The adjustments for Penalties. Detailed Process Description.1 . of AS-IS document 3. TDS. The accounting entries will flow automatically from the Material Management module. More detailed explanation will be provided during the User testing & User training phase of the Project. a three way check will be done with the PO. variations and exceptions Post outgoing payment Enter GL account document Vendor Credit memo 161 of 194 .Capital Vendor Payments Version no of document: 2. service tax.

Unit Bull Power Limited Electronics Signature 162 of 194 . Reports None Technical Considerations . ( if any ) : Output from this business process sent to other functions. ( if any ) : User Roles and Authorizations Transaction posting authorisation will be given to limited set of users. Sign-off (Approval) for this document : Name of Team member M Harikrishna Organisation/Bus.IT CO LOGO Blue Print Document –Finance CLIENT LOGO Potential Gaps: None Potential Gap Resolution: None System Configuration Considerations Reports required related to business process FBL1N-Vendor line item report FD10N-Vendor balance report Outputs required for this business process None Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No Inputs/ data received from other function for this process. Technical Considerations – Forms.Conversion Requirements None Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements : None Business Benefits Capital purchases & payments will be accounted for in SAP properly.

IT CO LOGO

Blue Print Document –Finance

CLIENT LOGO

3.3.14 Invoice processing without Purchase order
Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr. No of To-BE document 3.3.14 Ref. Sr. No. of AS-IS document Name of Business Process : Accounts Payable Module Finance Version no of document: 2.1 Flow Chart of Business Process :

Submodule AP- Purchase of Material Bill
Processing

Date :

General Requirements/Expectations Description
Purchase orders in SAP are created in the MM module. A Goods Received Note (GRN) is generated within the MM module. Hence the relevant invoice should also be posted in the MM module. This enables the system to link the invoice with the GRN and also updates the Purchase Order. There are purchase transactions that do not follow this process (raising of PO and recording of receipt of goods or confirmation of service) e.g. telephone and electricity invoices, invoice for rent, school fees etc. Since these transactions have no link with the MM module, they have to be booked through the Accounts Payable (AP) module of FI. Vendor codes needs to be created for such transactions.

Detailed Process Description, Process Variations and Exceptions
When an invoice is booked through the AP module, the system treats the invoice as approved when posted. It is therefore possible to include these invoices in the payment run, provided they meet the other parameters like due date. There are two ways in which control can be exercised over these invoices. • • Post the invoice, but block it for payment (manually). Park the invoice and block it.

Since blocking is a manual process, there is no control to prevent an inadvertent/deliberate omission. Parking an invoice is the same as logging the invoice in the system. It does not create any accounting entries, however, but all parked documents are visible in the system. It is preferable to block the invoices when parking them, to prevent accidental posting of un-approved invoices. After parking, the invoices can be sent to the relevant managers for approval. When the invoices are received back after approval, an authorized employee can remove the block and post the invoices. At month-end, a listing of Parked invoices needs to be extracted and necessary accruals made for expenses covered by these invoices Please refer MM BBP document for detailed explanation.

Process Step
FB60 F-48 F-53

Explanation, variations and exceptions
Enter Vendor Invoice (FI) Post Vendor down payment Post outgoing payment
163 of 194

IT CO LOGO

Blue Print Document –Finance
Automatic clearing

CLIENT LOGO

F.13

Potential Gaps:
None

Potential Gap Resolution:
None

System Configuration Considerations
Document type configuration

Reports required related to business process
FBL1N-Vendor line item report FD10N-Vendor balance report

Outputs required for this business process
None

Data Interface
Whether data records of current business process would be transferred to system other than SAP R/3 : No Inputs/ data received from other function for this process, ( if any ) : Output from this business process sent to other functions, ( if any ) :

User Roles and Authorizations
Transaction posting authorisation will be given to limited set of users.

Technical Considerations – Forms, Reports
None

Technical Considerations - Conversion Requirements
None

Technical Considerations – Interface Requirements
None

Technical Considerations – Enhancements
None

Technical Considerations – Workflow requirements :
None

Business Benefits
Streamlining the process of Invoice booking Sign-off (Approval) for this document : Name of Team member Organisation/Bus. Unit Signature
164 of 194

IT CO LOGO

Blue Print Document –Finance

CLIENT LOGO

M Harikrishna

Bull Power Limited

Electronics

3.3.15 Credit Memo/Note with Purchase Order
Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr. No of To-BE document 3.3.15 Ref. Sr. No. of AS-IS document Name of Business Process : Accounts Payable Module Finance Version no of document: 2.1 Flow Chart of Business Process :

Submodule AP- Credit Memo/Note with Purchase Order

Date :

General Requirements/Expectations Description
Credit memos represent credits received from the vendor. Credit memos are generally issued to rectify a previously issued invoice. A Credit Memo could be either with or without a PO reference.

Detailed Process Description, Process Variations and Exceptions
A Credit Memo with a PO reference is processed under MM-Logistics - Invoice Verification Module. A Credit Memo can be processed either as a ‘Credit Memo’ transaction or as a ‘Subsequent Credit’ transaction. A Credit Memo transaction is used if the quantity supplied needs correction. If the discrepancy is in the value and not the quantity, ‘Subsequent Credit’ transaction has to be used. Examples of subsequent credits include overpricing in the invoice, correction on freight charges etc. Please refer MM BBP document for detailed explanation.

Potential Gaps:
None

Potential Gap Resolution:
None

System Configuration Considerations
Document type configuration

Reports required related to business process
FBL1N-Vendor line item report
165 of 194

At the time of payment. the net outstanding will be paid-off. ( if any ) : Output from this business process sent to other functions. Technical Considerations – Forms. Reports None Technical Considerations . ( if any ) : User Roles and Authorizations Transaction posting authorisation will be given to limited set of users.IT CO LOGO Blue Print Document –Finance CLIENT LOGO FD10N-Vendor balance report Outputs required for this business process None Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No Inputs/ data received from other function for this process. Unit Bull Power Limited Electronics Signature 166 of 194 .Conversion Requirements None Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements : None Business Benefits Credit memos can be linked to the original vendor invoice. Sign-off (Approval) for this document : Name of Team member M Harikrishna Organisation/Bus.

but there is a discrepancy between the two.16 GR/IR account maintenance Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr. The GR/IR accounts are credited no sooner a Goods receipt is entered by the MM personnel.IT CO LOGO Blue Print Document –Finance CLIENT LOGO 3. It gets nullified when the Vendor Invoice is booked against the Purchase Order. of AS-IS document Name of Business Process : Accounts Payable Module Finance Version no of document: 2. • Invoices paid.3. Potential Gaps: None 167 of 194 .For BPE this is not applicable. as Invoice is entered only after GR. An ‘Automatic Clearing Program’ should be executed periodically to set-off the matching debits and credits in the GR/IR account. but goods not received. No of To-BE document 3. but invoice not posted. At the time of Invoice GR/IR account is debited with the credit to Vendor Account.GR/IR account maintenance Date : General Requirements/Expectations Description The GR/IR account is an accrual account to which entries get posted when a GRN is created in the system. At the year-end. A corresponding debit to the GR/IR account will be generated during Invoice verification. but goods not received.16 Ref.3. Sr. Detailed Process Description. as Invoice is entered only after GR. a program needs to be executed so as to clear the open Debit and Credit balances. A GR/IR account represents a Provision made in the books in respect of goods received pending receipt of Vendor Invoices.1 Flow Chart of Business Process : Submodule AP. GR/IR ……………. No. Process Variations and Exceptions Credit entry in to GR/IR account at the time of GR is not cleared automatically with the debit entry in GR/IR account at the time of Invoice.……… Dr. The liability gets created soon after posting a goods receipt transaction in the MM Module. Cr. • Goods received and invoice posted.For BPE this is not applicable. GR/IR account clearing is done through separate process. Following Entry is passed by the system at the time of Goods issue:Cost of Good Sold A/c………. The open items in the account will then represent either of the following: • Invoice posted. When the invoice received from the vendor is posted in the system. • Goods received. a debit entry is made in the GR/IR account.

Reports None Technical Considerations .IT CO LOGO Blue Print Document –Finance CLIENT LOGO Potential Gap Resolution: None System Configuration Considerations None Reports required related to business process FBL3N-GL line item report Outputs required for this business process None Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No Inputs/ data received from other function for this process. ( if any ) : User Roles and Authorizations Authorization for execution of the Automatic Clearing program for GR/IR accounts Technical Considerations – Forms. This entry is automatically generated by the system. Sign-off (Approval) for this document : Name of Team member M Harikrishna Organisation/Bus. ( if any ) : Output from this business process sent to other functions.Conversion Requirements None Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements : None Business Benefits No need to make any provision at the month-end in respect of goods received pending receipt of invoices. Unit Bull Power Limited Electronics 168 of 194 Signature .

17 Ref.IT CO LOGO Blue Print Document –Finance CLIENT LOGO 3. the banker pays the bill of exchange. Process Variations and Exceptions Bills of exchange are handled as special G/L transactions in the SAP System. The vendor calculates the costs arising from the bill of exchange charges and sends an invoice. “W” denotes the special GL indicator used in respect of Bills of Exchange. The payment of a bill of exchange is posted and simultaneously the bill of exchange payables on the vendor and special G/L accounts is cleared. This facilitates overview of bills of exchange receivable and bills of exchange payable at any stage. Detailed Process Description. No of To-BE document 3.3. When posting a bill of exchange payable.3. After the bill of exchange due date is reached. of AS-IS document Name of Business Process : Accounts Payable Module Finance Version no of document: 2.2. variations and exceptions Bill of Exchange payment Check Bill of Exchange 169 of 194 . Process Step F-40 FBW6 Explanation.3. The detailed payment process is explained in the section 3. All the subsequent postings. These transactions are thus maintained independently of other transactions in the subsidiary ledger and are posted to a special G/L account in the general ledger. such as the payment of a bill of exchange by the bank and the cancellation of the bill of exchange payable and the bill of exchange liability. the payment program clears the open items and posts a bill of exchange payable to the vendor account and to the special G/L account for the bill of exchange payable.17 Bill of Exchange Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr. Normally the Automatic Payment Program is used to post bills of exchange payable. Sr.Bill Of Exchange Date : General Requirements/Expectations Description Bill of Exchange related transactions should be tracked through SAP.1 Flow Chart of Business Process : Submodule AP. It is posted and processed in the same way as any other invoice. More detailed explanation will be provided during the User testing & User training phase of the Project. No. have to be made manually.

( if any ) : User Roles and Authorizations Authorization for execution of the Automatic Clearing program for GR/IR accounts Technical Considerations – Forms.IT CO LOGO Blue Print Document –Finance CLIENT LOGO Potential Gaps: None Potential Gap Resolution: None System Configuration Considerations None Reports required related to business process FBL3N-GL line item report Outputs required for this business process None Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No Inputs/ data received from other function for this process. Reports None Technical Considerations . Unit Signature 170 of 194 .Conversion Requirements None Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements : None Business Benefits Sign-off (Approval) for this document : Name of Team member Organisation/Bus. ( if any ) : Output from this business process sent to other functions.

1 Date Flow Chart of Business Process : General Requirements/Expectations Description While entering the Vendor Invoice directly through FI . Sr. No.Vendor Invoice document holding & posting Version no of document:2.2. No of To-BE document 3. it does not have to be complete. you may be interrupted. functionality should be available in SAP to store the entered data in SAP.3. without giving the financial impact. Process Step FB60 Explanation. A document number is not assigned. If you want the system to hold a document. variations and exceptions Enter Vendor Invoice Potential Gaps: None Potential Gap Resolution: None System Configuration Considerations 171 of 194 . of AS-IS document :No Name of Business Process : Account Payable Module Finance Submodule AP. Process Variations and Exceptions In this case.13 Ref. and then continue with the document entry at a later time. Account balances are not updated and the document data is not available for evaluation. Detailed Process Description.18 Vendor Invoice document holding & posting Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr. or you may not have all the data you need for entering a document. you can temporarily save the data you have entered.IT CO LOGO Blue Print Document –Finance CLIENT LOGO M Harikrishna Bull Power Limited Electronics 3.

Technical Considerations – Forms. there is no need to enter all that data again. Unit Bull Power Electronics Limited Signature 172 of 194 . the entered data will be saved and while posting the document. Sign-off (Approval) for this document : Name of Team member M Harikrishna Organisation/Bus. ( if any ) : User Roles and Authorizations Hold document functionality will be given to limited set of users.Conversion Requirements None Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements : None Business Benefits Using the hold document functionality.IT CO LOGO Blue Print Document –Finance CLIENT LOGO Reports required related to business process Outputs required for this business process Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No Inputs/ data received from other function for this process. ( if any ) : Output from this business process sent to other functions. Reports None Technical Considerations .

Sr. At the year-end.Acquisition process Date : General Requirements/Expectations Description Asset acquisition for example implies the process of procurement of Machinery that is used to carry out the normal production related activities of an organization. the AUC appears as a part of Capital Work in Progress under the Fixed Assets group. The costs are accumulated using an Internal Order and subsequently settled to single or multiple Fixed Assets. of AS-IS document 3. The primary business process in asset accounting is the purchase of assets and/or the capitalization of inhouse produced goods or services. No of To-BE document 3.4.1 Ref.1 Acquisition process Name of Business Process : Asset Accounting Module Finance Version no of document: 2. Detailed Process Description. SAP provides the functionality of Internal orders for tracking the AuC’s. No.1 Acquisition Process Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr. the Transaction type needs to be mandatory input. Process Variations and Exceptions Transaction Type The transaction type identifies the type of business transaction.4. Direct Capitalization 173 of 194 . Assets under Construction As per the generally accepted accounting principles “Assets under construction” (AuC).1 Flow Chart of Business Process : Submodule AA. a. In case of any asset transaction.4. are not permitted to be capitalized and depreciated immediately. The costs are built up over a period of time and are later on capitalized on the day the asset is installed and commissioned.IT CO LOGO Blue Print Document –Finance CLIENT LOGO Asset Accounting 3. Using the transaction type. It will be shown in the Balance sheet as AUC asset. b. the system posts the transaction to the appropriate accounts of the given account determination.

Spares procured to stock can be accounted in two ways:1. If material master is not created for the spares. the exchange gain/loss on sale of asset should be capitalized and the corresponding effect should be given to the Asset block. until block is removed. Low value assets will not be capitalized and will be expensed in the year of purchase.IT CO LOGO Blue Print Document –Finance CLIENT LOGO Direct capitalization refers to asset acquisitions that do not have an asset under construction phase. one can no longer post acquisitions to this asset. If the Internal order is blocked. then no further acquisition can be booked to that order. A new report will be developed to store the exchange gain/loss in the SAP. and transfer from this account to the final asset. The idea behind this. Block can be set at the internal order level also. Low value assets will be defined in the system. Instead. is to prevent future postings to an asset under construction once the project is complete. All the Capital Procurements & Capital Projects will be identified by an AR number. they are capitalized and begin depreciation immediately. 2. This calculation for Income tax purpose will be done outside the system. The blocking indicator can be indicated in the asset master record. Existing Asset Tag number for respective Assets will be captured in the system for easy identification with the legacy system. Fixed asset register is updated automatically on each asset postings. which will be 174 of 194 . variations and exceptions Acquisition of Asset AUC settlement Asset transfer within the company code Potential Gaps: As per the Income tax rule. If material master is created for the spares then spares will be issued from Inventory to Internal order. Hence the series for the same would be external numbering. Subsequent capitalization will be done through separate AUC order. Process Step F-90 AIBU ABUMN Explanation. Once the blocking indicator is set. for example. An external asset acquisition is a business transaction resulting from the acquisition of an asset from a business partner (in contrast to an acquisition from in-house production). For example: -External Asset Acquisitions through FI -Processing Asset Acquisitions in Purchasing (FI-AA/MM) -Account assignment to an Internal Order -Account assignment to a clearing account. then it will be directly debited to the internal order. Potential Gap Resolution: This functionality is not provided in SAP.

Technical Considerations – Forms.Conversion Requirements None Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements : None Business Benefits Asset acquisition will be properly identified and accounted as AUC or direct capitalization. 3. ( if any ) : Output from this business process sent to other functions. 4. Asset classes configuration Depreciation area configuration Depreciation key configuration Account determination Define transaction type for acquisition. Sign-off (Approval) for this document : Name of Team member M Harikrishna Organisation/Bus. 5. System Configuration Considerations 1. ( if any ) : User Roles and Authorizations Asset acquisition transaction posting authorisation will be given to limited set of users. Reports None Technical Considerations .IT CO LOGO Blue Print Document –Finance CLIENT LOGO added to the Asset block in the report so that ready information will be available in SAP for Income tax reporting. Unit Bull Power Electronics 175 of 194 Signature . 2. Outputs required for this business process None Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No Inputs/ data received from other function for this process.

IT CO LOGO Blue Print Document –Finance Limited CLIENT LOGO 176 of 194 .

Detailed Process Description. Normally assets are depreciated based on the useful life and the nature of the asset. subsequently the actual run can be executed.4.Depreciation Accounting Version no of document: 2. Book depreciation areas will be defined for Financial closing and Tax depreciation area will be defined for Income Tax. Process Variations and Exceptions The Straight line method will be considered for the Financial Closings and WDV method will be adopted for Income Tax. No of To-BE document 3. to the sole exception of Capital WIP all assets are to be depreciated. Whether or not an Asset is used or not.Cr (Accumulated Depreciation A/c) Depreciation rate for asset can be changed even after capitalization.IT CO LOGO Blue Print Document –Finance CLIENT LOGO 3. depreciation entry shall be made taking into consideration of capitalizations made during the year.2 Ref. Sr. depreciation will have to be charged on the same. The calculation of depreciation will be done on monthly basis (as part of month end closing activities) by the system at the preconfigured rate. necessary changes has to be done in the depreciation key. Depreciation entry will be posted in to the system using the transaction code AFAB. of AS-IS document 3. No. The system will calculate the depreciation as per the revised rate and will post the difference for the earlier periods in the current month and from the current month onwards the depreciation will be calculated at the revised rate.4. For changing the depreciation rate. Depreciation will be calculated separately for the each of the depreciation area defined in the asset master. Depreciation A/c ……………………………………Dr Provision for Depreciation A/c ……………………. The system automatically determines the planned depreciation for the current fiscal year by means of the depreciation keys entered in the master record.2 Depreciation Accounting Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr.1 Date : Flow Chart of Business Process : General Requirements/Expectations Description Depreciation represents a measure of the wear and tear undergone by an Asset either due to its use in the normal production process or due to it becoming obsolete..2 Depreciation Accounting Name of Business Process : Asset Accounting Module Finance Submodule AA. Options are available for running the Depreciation program in a Test mode. This will generate the requisite Financial postings.4. 177 of 194 . Howsoever. At the time of book closure.

Account determination Reports required related to business process Asset Balance report Outputs required for this business process None Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No Inputs/ data received from other function for this process. Depreciation key configuration 3. System Configuration Considerations 1. variations and exceptions Depreciation calculation Potential Gaps: SAP does not provide the depreciation report as per the Income Tax act Block concept. then depreciation will be calculated as per the depreciation start date mentioned in the asset master data. ( if any ) : User Roles and Authorizations Transaction posting authorisation will be given to limited set of users. On sale/disposal of the asset. the depreciation will be calculated as per the depreciation start date mentioned in the asset master data. Process Step AFAB Explanation.Conversion Requirements None Technical Considerations – Interface Requirements None 178 of 194 . ( if any ) : Output from this business process sent to other functions. Potential Gap Resolution: A new report will be developed to provide the depreciation as per the Block concept of Income Tax. Depreciation area configuration 2. Technical Considerations – Forms. A new report will be developed to provide the depreciation as per the Block concept of Income Tax. appropriate depreciation effect will be given by the system and gain/loss will be booked accordingly.IT CO LOGO Blue Print Document –Finance CLIENT LOGO If the Asset is acquired during the year. Reports None Technical Considerations . On addition to the existing asset also.

Unit Bull Power Electronics Limited Signature 179 of 194 .IT CO LOGO Blue Print Document –Finance CLIENT LOGO Technical Considerations – Enhancements None Technical Considerations – Workflow requirements : None Business Benefits • • Procedure for Calculation of depreciation is automated Simulation of Depreciation into future periods can be made Sign-off (Approval) for this document : Name of Team member M Harikrishna Organisation/Bus.

the Asset register is updated with the adjustment accommodating the movement of the Asset and the transfer of Gross Block of Assets and Accumulated Depreciation at the date of transfer in the books of accounts of the respective Locations.4. The Invoice carries the Excise Duty for the specified Asset which is the reversal of initial credit availed (on transferred Asset) less 2. Excise Invoice for transfer of asset will be prepared through MM module. or an asset component. No.3 Ref. The Excise Duty so paid by the sending location is claimed as Input tax credit by the receiving location. Intracompany transfer may be necessary for one of the following reasons: • • • An asset was created in the wrong asset class.4. Process Step ABUMN Explanation.5 More detailed explanation will be provided during the User testing & User training phase of the Project.1 Flow Chart of Business Process : Submodule AA. No of To-BE document 3.4. to a different asset master record. Cost Center will be updated in the Asset master data. Once the Asset is received by the receiving location. Settle an asset under construction and transfer it to a finished asset.IT CO LOGO Blue Print Document –Finance CLIENT LOGO 3. Split up an asset or move part of an asset (transfer from asset to asset).Transfer of Assets Date : General Requirements/Expectations Description The transfer of Assets (mainly Plant & Machinery) is undertaken from one location to another on requirement/replacement basis. Process Variations and Exceptions Using intracompany asset transfer.3 Transfer of Assets Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr.3 Transfer of Assets Name of Business Process : Asset Accounting Module Finance Version no of document: 2.4. Physical verification of the Asset will be done as per the process explained in the section 3. variations and exceptions Transfer of Asset within Company Code Potential Gaps: None Potential Gap Resolution: 180 of 194 . Sr. of AS-IS document 3. Asset transfer will be done in SAP using the transaction code ABUMN (transfer within company code). Detailed Process Description. a fixed asset is transferred.5% per quarter.

Conversion Requirements None Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements : None Business Benefits Proper treatment in the books of accounts will be given for asset transfer. ( if any ) : Output from this business process sent to other functions. Define transaction type for transfer Reports required related to business process Asset Balance report Outputs required for this business process None Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No Inputs/ data received from other function for this process. Unit Bull Power Limited Electronics Signature 181 of 194 . Technical Considerations – Forms. ( if any ) : User Roles and Authorizations Asset transfer transaction posting authorisation will be given to limited set of users. Reports None Technical Considerations .IT CO LOGO Blue Print Document –Finance CLIENT LOGO None System Configuration Considerations 1. Sign-off (Approval) for this document : Name of Team member M Harikrishna Organisation/Bus.

4 Disposal of Assets Name of Business Process : Asset Accounting Module Finance Version no of document: 2. with no revenue earned. On asset retirement.Disposal of Assets Date : General Requirements/Expectations Description Asset disposal is called as Asset retirement in SAP.4. No of To-BE document 3. resulting in revenue being earned.4.4 Ref. of AS-IS document 3. This asset retirement can be complete or partial on the percentage basis or quantity basis. Gain/Loss on sale of asset will be booked as per the Companies Act only Calculation as per the Income tax will be done separately in the report developed as per the Income tax act rules. resulting in revenue being earned. variations and exceptions Asset retirement from sale with revenue Asset retirement from sale without revenue Potential Gaps: None Potential Gap Resolution: None 182 of 194 . An asset is sold. or the business transaction. Asset will be scraped in case of theft or loss due to natural calamity. An asset has to be scrapped. The sale is posted against a clearing account. Asset retirement is the removal of an asset or part of an asset from the asset portfolio with revenue to a customer or without revenue. one can distinguish the following types of retirement: • • • • An asset is sold.4 Disposal of Assets Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr. No. Detailed Process Description. which leads to the retirement.4. An asset is sold to an affiliated company The Capital Profit or Loss arising due to the retirement of an Asset is automatically calculated and Posted by the system. Code ABAVN).IT CO LOGO Blue Print Document –Finance CLIENT LOGO 3. Process Step F-92 ABAVN Explanation. Process Variations and Exceptions Depending on organizational considerations. appropriate entry will be passed for the depreciation and loss or gain on sale/scrap of asset will be booked. The sale is posted with a customer.1 Flow Chart of Business Process : Submodule AA. Sr. Asset can be retired with revenue (T code F-92) or without revenue (T.

( if any ) : User Roles and Authorizations Asset retirement transaction posting authorisation will be given to limited set of users.IT CO LOGO Blue Print Document –Finance CLIENT LOGO System Configuration Considerations 1. GL accounts for gain / loss from asset sale Reports required related to business process Asset Balance report Outputs required for this business process None Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No Inputs/ data received from other function for this process. ( if any ) : Output from this business process sent to other functions. Reports None Technical Considerations . Technical Considerations – Forms.Conversion Requirements None Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements : None Business Benefits Profit/Loss on retirement of an asset is automatically calculated by the system Flexibility for Complete/Partial Retirement and single/Mass disposals Sign-off (Approval) for this document : Name of Team member M Harikrishna Organisation/Bus. Unit Bull Power Limited Electronics Signature 183 of 194 .

No of To-BE document 3. There is no separate report for tagging the assets as per the books against the physical assets. Tag number of the asset will remain same.Physical Verification of Assets Version no of document: 2. System Configuration Considerations None Reports required related to business process Physical verification report 184 of 194 . of AS-IS document 3. Detailed Process Description.5 Physical Verification of Assets Name of Business Process : Asset Accounting Module Finance Submodule AA.IT CO LOGO Blue Print Document –Finance CLIENT LOGO 3.5 Ref. A new physical verification report will be developed in the required format to provide the year wise information. for example laptop.5 Physical Verification of Assets Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr. Employee detail will be put in the Asset master data for the asset lying with the employees.4.1 Flow Chart of Business Process : Date : General Requirements/Expectations Description The Fixed Asset Register for individual Location is derived from the system and the same is forwarded to them for confirming on the physical verification of Assets. surplus assets and damaged or obsolete assets are reported. Sr. Potential Gaps: Only Fixed asset register is available in the system. will be reported in the report at the location at which the asset is transferred. Process Variations and Exceptions The verification will be done and a physical verification report and any discrepancies in physical and book assets. No. the necessary adjustment entries in the books will be made. which will display the asset detail along with value as per the books. Asset transferred from location to another location.4. Basis the approvals. There is no separate report for tagging the assets as per the books against the physical assets.4. Potential Gap Resolution: A new physical verification report will be developed in the required format.

Reports None Technical Considerations . Technical Considerations – Forms. Unit Bull Power Limited Electronics Signature 185 of 194 .IT CO LOGO Blue Print Document –Finance CLIENT LOGO Outputs required for this business process None Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No Inputs/ data received from other function for this process. ( if any ) : Output from this business process sent to other functions. Sign-off (Approval) for this document : Name of Team member M Harikrishna Organisation/Bus. ( if any ) : User Roles and Authorizations Addition/change authorization in Physical verification report will be given to limited set of users.Conversion Requirements None Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements : None Business Benefits Through new report the assets as per the books can be compared against the physical assets and appropriate action can be taken for the differences.

No of To-BE document 3.IT CO LOGO Blue Print Document –Finance CLIENT LOGO 3.Bank reconciliation statement 2. Maintain Exchange Rates 6. Reclassify Payables and Receivables if necessary 7.5 Month End Process Name of Business Process : Month End Process Module Finance Version no of document: 2. Foreign Currency Open Item Revaluation-Revalue Open Items in GL . No.1 Flow Chart of Business Process : Submodule Month End Process Date : General Requirements/Expectations Description Monthly closure will be done of the books of accounts. Posting Accruals or Provisions entries at month end 3. Detailed Process Description. Posting of Recurring Documents. Statutory returns 6. Run the Depreciation Calculation 8.AR & AP 5. 3. Earnings in Foreign Currency.Customer/Vendor reconciliation 4. Interest from customers. Managing the GR/IR Account-Run the GR/IR Automatic Clearing 4. payments. Job work. stock transfer. Run Financial Statement Version-Balance Sheet and Profit & Loss reports 10.5 Ref. 2.5 Month End Process Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr. Tax movement related reports All the details for Schedule VI requirements like Capex Commitments. of AS-IS document 3. Open Next Accounting Period Below mentioned month end activities/reports will also be done:1. Complete all postings related to expense booking.Cash Flow statement 3. Contingent liability etc. 186 of 194 . Hospitality. Proof sheets 5. Expenditure in Foreign Currency etc will be provided by SAP. Month end activity will be the list of various activities. Contingent Liabilities.Transfer of Prepaid expenses to Expenses 9. Sr. Taxes. Process Variations and Exceptions The Following are the Month End Processes followed at the respective Plants & HQO: 1. inter office adjustments.

( if any ) : User Roles and Authorizations Transaction posting authorisation will be given to limited set of users.IT CO LOGO Blue Print Document –Finance CLIENT LOGO Potential Gaps: None Potential Gap Resolution: None System Configuration Considerations None Reports required related to business process As mentioned above Outputs required for this business process None Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No Inputs/ data received from other function for this process.Conversion Requirements None 187 of 194 . ( if any ) : Output from this business process sent to other functions. Technical Considerations – Forms. Reports None Technical Considerations .

Sign-off (Approval) for this document : Name of Team member M Harikrishna Organisation/Bus.IT CO LOGO Blue Print Document –Finance CLIENT LOGO Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements : None Business Benefits Accounting will be done in SAP in proper way. Unit Bull Power Limited Electronics Signature 188 of 194 .

Posting Accruals or Provisions entries at month end 3. stock transfer. Foreign Currency Open Item Revaluation-Revalue Open Items in GL . Posting of Recurring Documents. Reclassify Payables and Receivables if necessary 7.Cash verification 3. Calculation of XYZ LIMITED marketing compensation 10. Open Next Financial year period 14.Physical verification of report 2.1 Ref. Detailed Process Description. Carry forward the balances to next year of General Ledger (Balance sheet items). Managing the GR/IR Account-Run the GR/IR Automatic Clearing 4. Customers. Fiscal Year Change of Asset Accounting 15. Year end activity will be the list of various activities.6. Job work. payments. Complete all postings related to expense booking. Run Financial Statement Version-Balance Sheet and Profit & Loss reports 13. Contingent liability etc. Run the Depreciation Calculation 8.6. 16. of AS-IS document 3. Taxes. Hospitality. Process Variations and Exceptions 1. Transfer of Prepaid expenses to Expenses 9. No. 3. Sr.Related party transaction disclosures 189 of 194 .1 Year End Process – FY Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr. 2. inter office adjustments. Transfer of P&L balances to retained earning.1 Year End Process – FY Name of Business Process : Year End Process Module Finance Submodule Year End Process – FY Version no of document: 2. No of To-BE document 3.IT CO LOGO Blue Print Document –Finance CLIENT LOGO Year End Process 3.6.Maintenance of number range for the next year Below mentioned month end activities/reports will also be done:1. FBT & Deferred Tax 11.Cash flow statement 4. Interest from customers. Maintain Exchange Rates 6.Calulation of Income tax. Vendors & Assets.1 Date : Flow Chart of Business Process : General Requirements/Expectations Description Yearly closure (FY) will be done of the books of accounts.AR & AP 5. Remittance of Dividends 12.

IT CO LOGO Blue Print Document –Finance CLIENT LOGO 5. Technical Considerations – Forms. ( if any ) : Output from this business process sent to other functions. Potential Gaps: None Potential Gap Resolution: None System Configuration Considerations None Reports required related to business process As mentioned above Outputs required for this business process None Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No Inputs/ data received from other function for this process. Statutory returns 9. Expenditure in Foreign Currency etc will be provided by SAP. Tax movement related reports All the details for Schedule VI requirements like Capex Commitments.Proof sheets 8. Bank Reconciliation 6. Reports None Technical Considerations . Earnings in Foreign Currency. Contingent Liabilities. ( if any ) : User Roles and Authorizations Transaction posting authorisation will be given to limited set of users.Customer/Vendor reconciliation 7.Conversion Requirements None Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None 190 of 194 .

Sign-off (Approval) for this document : Name of Team member M Harikrishna Organisation/Bus. Unit Bull Power Electronics Limited Signature 191 of 194 .IT CO LOGO Blue Print Document –Finance CLIENT LOGO Technical Considerations – Workflow requirements : None Business Benefits Accounting will be done in SAP in proper way.

Customer/Vendor reconciliation 7. No of To-BE document 3.2 Year End Process – CY Name of Business Process : Year End Process Module Finance Submodule Year End Process – CY Version no of document: 2. Tax movement related reports 10.Proof sheets 8. Bank Reconciliation 6. No. Statutory returns 9.6. Foreign Currency Open Item Revaluation-Revalue Open Items in GL . Posting of Recurring Documents.IT CO LOGO Blue Print Document –Finance CLIENT LOGO 3.Physical verification of report 2. Managing the GR/IR Account-Run the GR/IR Automatic Clearing 4. Run the Depreciation Calculation 8. Interest from customers. Open Next posting period Below mentioned month end activities/reports will also be done:1. COLAS investment Budget 14. of AS-IS document 3. Detailed Process Description. Reclassify Payables and Receivables if necessary 7. 3. Complete all postings related to expense booking. payments. Year end activity will be the list of various activities. Sr. Colas Monthly Income Statement 11. Manufacturing Report for COLAS 13. Activity Report All the details for Schedule VI requirements like Capex Commitments. inter office adjustments. 2. Earnings 192 of 194 . transfer of prepaid exp.Cash flow statement 4. Job work.Cash verification 3. Colas B1 & B2 Budgeting 12.6.2 Year End Process – CY Business Blueprint Document For SAP R/3 Implementation at BPE Date : Sr. Maintain Exchange Rates 6. Contingent Liabilities. Posting Accruals or Provisions entries at month end 3. Run the Bank Reconciliation 10 Run Financial Statement Version-Balance Sheet and Profit & Loss reports 11.2 Ref. Contingent liability . Hospitality. stock transfer.1 Date : Flow Chart of Business Process : General Requirements/Expectations Description Yearly closure (CY) will be done of the books of accounts.Related party transaction disclosures 5.6.Transfer of Prepaid expenses to Expenses 9. Taxes.AR & AP 5. Process Variations and Exceptions 1.

( if any ) : User Roles and Authorizations Transaction posting authorisation will be given to limited set of users. Sign-off (Approval) for this document : Name of Team member M Harikrishna Organisation/Bus.IT CO LOGO Blue Print Document –Finance CLIENT LOGO in Foreign Currency. Potential Gaps: None Potential Gap Resolution: None System Configuration Considerations Reports required related to business process As mentioned above Outputs required for this business process None Data Interface Whether data records of current business process would be transferred to system other than SAP R/3 : No Inputs/ data received from other function for this process. Reports None Technical Considerations . ( if any ) : Output from this business process sent to other functions.Conversion Requirements None Technical Considerations – Interface Requirements None Technical Considerations – Enhancements None Technical Considerations – Workflow requirements : None Business Benefits Accounting will be done in SAP in proper way. Expenditure in Foreign Currency etc will be provided by SAP. Unit Bull Power Limited Electronics Signature 193 of 194 . Technical Considerations – Forms.

IT CO LOGO Blue Print Document –Finance CLIENT LOGO 194 of 194 .

Sign up to vote on this title
UsefulNot useful