Period End Closing Financial Accounting. SAP Best Practices

Transcription

1 Period End Closing Financial Accounting SAP Best Practices

2 Purpose, Benefits, and Key Process Steps Purpose The closing operations component helps you prepare and carry out the activities required for day-end, month-end and year-end closing. For this purpose, the system provides a series of standard reports that can be used to generate evaluations and analyses of the posted account balances directly. Benefits The system helps you to carry out the following: create the balance sheets and P&L statements document the posting data Key Process Steps Day-end Closing Month-end Closing Year-end Closing 2014 SAP SE or an SAP affiliate company. All rights reserved. 2

3 Required SAP Applications and Company Roles Required Enhancement package 7 for SAP ERP 6.0 Company Roles Finance Manager General Ledger Accountant Accounts Payable Accountant Accounts Receivable Accountant Finance Manager (Germany) Accounts Payable Manager 2014 SAP SE or an SAP affiliate company. All rights reserved. 3

4 Detailed Process Description Day-end Closing in Financial Accounting Update Exchange Rates Gaps in Document Number Assignment Invoice Numbers Allocated Twice Display Compact Document Journal 2014 SAP SE or an SAP affiliate company. All rights reserved. 4

5 Detailed Process Description Month-end Closing in Financial Accounting (I) Update Exchange Rates Gaps in Document Number Assignment Invoice Numbers Allocated Twice Open and Close Posting Periods Enter Recurring Entries Post Recurring Entries Run Batch Input Session Automatic Clearing of GR/ IR Account special process Analyze GR/ IR Clearing Accounts Automatic Clearing of GR/ IR Account Post Adjustment Entries 2014 SAP SE or an SAP affiliate company. All rights reserved. 5

6 Detailed Process Description Month-end Closing in Financial Accounting (II) Foreign Currency Revaluation Post Tax Payable Advance Return for Tax on Sales/ Purchases EC Sales List Foreign Trade Regulation Reports Z4 Foreign Trade Regulation Reports Z5A Comparison Documents/ Transaction Figures Close Previous Accounting Period Balance Interest Calculation Display Document Journal Financial Statement 2014 SAP SE or an SAP affiliate company. All rights reserved. 6

7 Detailed Process Description Year-end Closing in Financial Accounting Create Factory Calendar for New Year Carry Forward AP/ AR Balances Carry Forward GL Balances Re-grouping Receivables/ Payables Balance Confirmation Receivable Balance Confirmation Payable Final Close and Release Financial Reporting Close Previous Accounting Period Display Document Journal 2014 SAP SE or an SAP affiliate company. All rights reserved. 7

8 General Ledger Accountant Finance Manager Event Process Flow Diagram Process 1, Day-End Closing Day-End Closing Update Exchange Rates Display the Compact Document Journal Process Decision Create List of Gaps in Document Number Assignment Create List of Invoice Number Allocated Twice 2014 SAP SE or an SAP affiliate company. All rights reserved. 8

9 Finance Manager (Germany) General Ledger Accountant Accounts Payable Manager Finance Manager Event Process Flow Diagram Process 2, Month-End-Closing Month-End Closing - Posting Month-End Closing Updating Gaps in Document Number Assignment Invoice Number Allocated Twice Enter Recurring Entries Process Decision Run Batch Input Session Execute Recurring Entries Financial Statement Actual/Acutal Comparsion Valuation of Provisions Define Interest Rates Financial Statement Actual/ Acutal Comparsion Actual/ Actual Comparsion Financial Statement Manual Clearing Account - Automatic Clearing Assign Provisions Open and Close Posting Periods Update Exchange Rate Analyse GRIR Clearing Account - Automatic Clearing Post G/L Account Document Interest Calculation Balances Open and Close Posting Periods Post Provisions Display Document Journal Foreign Currency Revaluation Reconciliation New Post Tax Payable Advance Return for Tax on Sales/Pur chases EC Sales List Foreign Trade Regulation Reports Z4 Foreign Trade Regulation Reports Z5A 2014 SAP SE or an SAP affiliate company. All rights reserved. 9

10 Accounts Receivable Accountant Accounts Payable Accountant General Ledger Accountant Finance Manager Event Process Flow Diagram Process 3, Year-End-Closing Year-End Closing -Updating Create Factory Calendar for New Year Carry Forward AP/AR Balances Display Document Journal Carry Forward GL Balances Open and Close Posting Periods Regroup Receivables / Payables Create Balance Sheet and P&L Statement Create Balance Confirmation Payable Create Balance Confirmation Receivable 2014 SAP SE or an SAP affiliate company. All rights reserved. 10

11 External to SAP <Function> Legend Symbol Description Usage Comments Symbol Description Usage Comments Band: Identifies a user role, such as Accounts Payable Clerk or Sales Representative. This band can also identify an organization unit or group, rather than a specific role. The other process flow symbols in this table go into these rows. You have as many rows as required to cover all of the roles in the scenario. External Events: Contains events that start or end the scenario, or influence the course of events in the scenario. Role band contains tasks common to that role. Diagram Connection Hardcopy / Document To next / From last Diagram: Leads to the next / previous page of the Diagram Hardcopy / Document: Identifies a printed document, report, or form Flow chart continues on the next / previous page Does not correspond to a task step in a document; instead, it is used to reflect a document generated by a task step; this shape does not have any outgoing flow lines Flow line (solid): Line indicates the normal sequence of steps and direction of flow in the scenario. Flow line (dashed): Line indicates flow to infrequently-used or conditional tasks in a scenario. Line can also lead to documents involved in the process flow. Connects two tasks in a scenario process or a non-step event Financial Actuals Financial Actuals: Indicates a financial posting document Does not correspond to a task step in a document; instead, it is used to reflect a document generated by a task step; this shape does not have any outgoing flow lines Business Activity / Event Business Activity / Event: Identifies an action that either leads into or out of the scenario, or an outside Process that happens during the scenario Does not correspond to a task step in the document Budget Planning Budget Planning: Indicates a budget planning document Does not correspond to a task step in a document; instead, it is used to reflect a document generated by a task step; this shape does not have any outgoing flow lines Unit Process Process Reference Unit Process: Identifies a task that is covered in a step-by-step manner in the scenario Process Reference: If the scenario references another scenario in total, put the scenario number and name here. Corresponds to a task step in the document Corresponds to a task step in the document Manual Process Manual Process: Covers a task that is manually done Does not generally correspond to a task step in a document; instead, it is used to reflect a task that is manually performed, such as unloading a truck in the warehouse, which affects the process flow. Sub- Process Reference Sub-Process Reference: If the scenario references another scenario in part, put the scenario number, name, and the step numbers from that scenario here Corresponds to a task step in the document Existing Version / Data Existing Version / Data: This block covers data that feeds in from an external process Does not generally correspond to a task step in a document; instead, this shape reflects data coming from an external source; this step does not have any incoming flow lines Process Decision Process Decision: Identifies a decision / branching point, signifying a choice to be made by the end user. Lines represent different choices emerging from different parts of the diamond. Does not usually correspond to a task step in the document; Reflects a choice to be made after step execution System Pass/Fail Decision System Pass / Fail Decision: This block covers an automatic decision made by the software Does not generally correspond to a task step in the document; instead it is used to reflect an automatic decision by the system that is made after a step has been executed SAP SE or an SAP affiliate company. All rights reserved. 11

12 2014 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. Please see for additional trademark information and notices. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE s or its affiliated companies strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions SAP SE or an SAP affiliate company. All rights reserved. 12