🖥️ F&A Process Guide

Accounting Systems — SAP & Oracle Guide

SAP and Oracle are the world’s leading ERP platforms for Finance & Accounting. Understanding their architecture, key modules, and configuration gives you a massive edge — whether you’re an end-user, a Finance analyst, or implementing a new system.

▶ Start: ERP in Finance — Why It Matters

An ERP (Enterprise Resource Planning) system integrates all Finance processes — GL, AR, AP, Fixed Assets, Payroll, Consolidation — into a single database. This eliminates data silos, reduces errors, and enables real-time financial visibility.

• Benefits: Single source of truth, automated reconciliations, real-time reporting, audit trail, compliance enforcement
• Market Leaders: SAP S/4HANA (large enterprises), Oracle Fusion Cloud (mid to large), Microsoft Dynamics 365 (mid-market), Tally (India SMEs)
• Selection Criteria: Company size, industry, geography, integration needs, total cost of ownership, vendor support

🔷 SAP FI Module — Key Concepts

SAP FI (Financial Accounting) is the core module for external financial reporting. Key sub-modules:

• 📋 GL (General Ledger): New GL in S/4HANA — real-time document splitting, parallel ledgers (Ind AS + IFRS simultaneously), profit centre accounting built-in
• 📋 AR (Accounts Receivable): Customer master, billing, dunning (F150), payment allocation (F-28), credit management (FD32)
• 📋 AP (Accounts Payable): Vendor master, invoice posting (FB60), payment run (F110), GR/IR reconciliation
• 📋 AA (Asset Accounting): Asset master, depreciation runs (AFAB), retirement, transfers — linked to GL automatically
• 📋 Bank Accounting: Bank reconciliation (FF67), electronic bank statement import, cash journal (FBCJ)
• Key T-Codes to Know: FB50 (GL posting), F-43 (vendor invoice), VA01 (sales order), ME21N (PO), F.01 (financial statements)

🔷 SAP CO — Controlling Module

SAP CO handles internal/management accounting — cost tracking, profitability analysis, and performance measurement. FI handles external reporting; CO handles internal decision support.

• Cost Centres (CCA): Track costs by department — allocate overhead from shared service centres to business units
• Internal Orders: Track costs for specific projects or events (e.g., a product launch or plant maintenance job)
• Profit Centres (PCA): Measure P&L by business segment — revenue and costs assigned by product line, region, or channel
• Product Costing (CO-PC): Calculate standard cost of manufactured products — material + labour + overhead
• Profitability Analysis (CO-PA): Multi-dimensional P&L analysis — profitability by customer, product, region, sales rep simultaneously

🔷 Oracle Financials Cloud

• Architecture: Cloud-native SaaS — no on-premise hardware, automatic quarterly updates, mobile-first interface
• General Ledger: Multidimensional chart of accounts (POET: Project, Organisation, Expenditure Type) — flexible segment structure
• Accounts Payable: AI-powered invoice processing with automatic 3-way match and exception handling
• Accounts Receivable: AutoInvoice interface, Advanced Collections with AI-prioritised worklist
• Financial Reporting Studio: Drag-and-drop report builder — publish to Excel, PDF, or web
• EPM Integration: Native integration with Oracle Planning Cloud for seamless Budget vs Actual reporting

🔷 Chart of Accounts Design

The Chart of Accounts (CoA) is the numbered list of every GL account in your ERP — the DNA of your financial system. Design it poorly and you’ll fight it for years.

• Structure: 1XXXXX = Assets | 2XXXXX = Liabilities | 3XXXXX = Equity | 4XXXXX = Revenue | 5XXXXX–6XXXXX = Expenses
• Numbering: Leave gaps (10100, 10200, 10500) to add accounts later without breaking sequence
• Global CoA vs Local CoA: Group uses one standard CoA; local entities can have additional local accounts mapped to group CoA
• Account Rationalisation: Aim for fewer, cleaner accounts — 500–800 accounts is sufficient for most companies; avoid creating accounts for every cost sub-type
• Natural Accounts vs Cost Centres: Use CoA for the nature of cost (travel, rent) and cost centres for the who/where — never encode department into the account number

✅ End: ERP Implementation Tips

• 🔷 Data Migration: Clean your master data BEFORE go-live — garbage in, garbage out. Run parallel for at least 2 months
• 🔷 Process Before System: Document your To-Be processes before configuring the ERP — never let the system dictate the process
• 🔷 Change Management: 70% of ERP failures are people problems, not technology. Invest heavily in training and communication
• 🔷 UAT (User Acceptance Testing): Finance team must test all critical scenarios with real data before go-live sign-off
• ✅ Hypercare Period: Keep implementation team on site for 4–6 weeks post go-live to resolve issues immediately
• ✅ Post-Implementation Review: 3 months after go-live — measure benefits realised vs business case promised