SAP Financials: The Core of SAP#
The SAP Finance (FI) module is the foundation of SAP ERP. Even organisations that implement SAP primarily for operational reasons need robust financial capabilities. Understanding SAP FI's capabilities and configuration options is essential for any SAP implementation.
If you're implementing SAP, the FI module will likely be one of the first modules configured. The decisions made during FI configuration will affect every other module that integrates with finance—which is essentially all of them.
---
General Ledger (FI-GL)#
Chart of Accounts#
The chart of accounts is the foundation of financial reporting.
Key considerations: - Operational chart of accounts: Used for daily postings - Group chart of accounts: Used for consolidation - Country-specific chart of accounts: Used for local statutory reporting
For ANZ organisations: - Typically one operational chart of accounts - May need country-specific charts for multi-country operations - GST/Tax reporting requirements drive account structure
Company Code Configuration#
The company code is the legal entity for financial reporting.
Key configuration: - Company code definition - Fiscal year variant (July-June for AU, April-March or calendar for NZ) - Currency (AUD, NZD) - Posting periods
Posting Logic#
Document principle: Every financial transaction creates a document with: - Document number - Posting date - Document date - Reference - Header text - Line items with debits and credits
Validation and substitution: Rules that validate or modify postings based on defined criteria.
Period-End Closing#
SAP provides structured period-end closing: - Recurring entries: Regular journal entries (rent, insurance) - Accruals: Deferral of expenses/revenue - Foreign currency valuation: Revaluing foreign currency balances - Intercompany elimination: For multi-entity organisations
---
Accounts Payable (FI-AP)#
Vendor Master Data#
Vendor record structure: - General data (address, communication) - Company code data (payment terms, reconciliation account) - Purchasing data (ordering address, currency)
Payment terms: Define when payment is due. - Net 30, Net 60 - 2/10 Net 30 (2% discount if paid in 10 days) - Installment payments
Invoice Processing#
Invoice entry: - Direct invoice entry - Invoice reference to purchase order (PO) - Invoice verification against goods receipt (3-way match)
Down payments: Track and manage supplier advances.
Payment Processing#
Payment program: Automatic payment selection and generation.
Payment methods for ANZ: - Direct credit (EFT) - standard for NZ/AU - Cheques (still used for some vendors) - Cards (for specific vendor types)
Bank file formats: - ABA format for Australian banks - Direct credit files for NZ banks
NZ/AU-Specific AP Considerations#
GST handling: - Tax codes for GST on purchases (15% NZ, 10% AU) - Input tax credits - GST on imports
Withholding tax: - Not common in NZ - May apply for specific vendor types
---
Accounts Receivable (FI-AR)#
Customer Master Data#
Customer record structure: - General data (name, address) - Company code data (payment terms, credit limit) - Sales area data (shipping, billing)
Invoice Processing#
Invoice creation: - Direct invoice entry - Invoice from sales order - Invoice from delivery
Billing plan: Milestone billing, periodic billing.
Payment Processing#
Payment receipts: - Manual entry - Lockbox (AU) - Bank statement processing (electronic bank statement)
Dunning: Automated collection letters for overdue accounts.
Credit Management#
Credit control: - Credit limits by customer - Credit checks on sales orders - Credit blocks for review
NZ/AU-Specific AR Considerations#
GST handling: - Tax codes for GST on sales - Tax invoices - Export GST (zero-rated)
Bank integration: - Bank statement import in standard formats - Direct credit for customer refunds
---
Fixed Assets (FI-AA)#
Asset Classes#
Different asset types have different treatment: - Buildings - Plant and equipment - Vehicles - Office equipment - Leasehold improvements
Depreciation#
Depreciation methods: - Straight-line - Diminishing value - Units of production
Depreciation areas: - Book depreciation (for financial statements) - Tax depreciation (for tax returns) - Group depreciation (for consolidation)
Asset Lifecycle#
Acquisition: - External acquisition (purchase) - Internal construction (AUCAV) - Asset transfer
Depreciation: - Ordinary depreciation - Unplanned depreciation - Revaluation
Retirement: - Sale - Scrapping - Transfer
NZ/AU-Specific Asset Considerations#
Tax depreciation: - Diminishing value method common - Different rates for different asset types - Immediate expensing for low-value assets
Revaluation: - Fair value revaluation permitted - Historical cost also acceptable
---
Bank Accounting#
Bank Master Data#
Bank key: Identifies the bank. - BSB format for Australia - Bank number format for New Zealand
Bank accounts: Company bank accounts.
Bank Reconciliation#
Manual reconciliation: - Compare bank statement to SAP records - Post differences
Electronic bank statement (EBS): - Import bank statement file - Auto-match transactions - Post unmatched items
formats supported: - MT940 (SWIFT) - BAI2 - Bank-specific formats
Cash Management#
Cash position: Current cash status. Liquidity forecast: Projected cash flows.
---
Integration with Other Modules#
Integration with MM (Materials Management)#
Invoice verification: MIRO posts to FI-AP.
Goods receipt: Posts to FI through account determination.
Integration accounts: - GR/IR clearing account - Inventory accounts - Price difference accounts
Integration with SD (Sales and Distribution)#
Billing: VF01 posts to FI-AR.
Revenue accounts: Determined by account key.
Integration accounts: - Revenue accounts - Cost of goods sold - Rebate accruals
Integration with CO (Controlling)#
Primary costs: Flow from FI to CO.
Secondary costs: Allocations within CO.
Real-time integration: Every FI posting can create CO posting.
---
NZ/AU-Specific Reporting#
GST Reporting#
NZ GST Return: - GST on supplies (sales) - GST on acquisitions (purchases) - Net GST payable/refundable
AU BAS (Business Activity Statement): - GST on sales (G1) - GST on purchases (G2) - GST summary
Financial Statements#
Statement of Financial Position (Balance Sheet): - Assets, liabilities, equity
Statement of Financial Performance (Income Statement): - Revenue, expenses, profit
Statement of Cash Flows: - Operating, investing, financing activities
Statement of Changes in Equity: - Movements in equity accounts
---
Implementation Best Practices#
Chart of Accounts Design#
Start with reporting requirements: - What reports do you need? - What level of detail is required? - What dimensions matter (cost centre, profit centre)?
Keep it simple: - Fewer accounts is better - Group similar items - Use account groups for organisation
Master Data Governance#
Vendor/customer master: - Define ownership - Create request/approval workflow - Regular review and cleanup
Consistent naming conventions: - Standard abbreviations - Search term population - Address standardisation
Period-End Process#
Document the close process: - What needs to be done - Who does it - When it must be completed
Use SAP's closing cockpit: - Task lists - Dependencies - Monitoring
---
Monday Morning Action Plan#
- Review Your Chart of Accounts: Before implementing SAP FI, document your current chart of accounts. Identify what works and what needs improvement.
- Map Your Reporting Requirements: List all financial reports you need. Include regulatory (GST, tax), management (monthly reports), and external (audit, bank) requirements.
- Document Your Banking Integration: What banks do you use? What file formats? Test that SAP supports your bank's formats.
- Assess GST Requirements: NZ GST or AU BAS—ensure you understand the SAP configuration needed for compliant reporting.
- Plan Your Master Data Migration: Vendor and customer master data migration is often underestimated. Start early.
---
Conclusion: SAP FI Is the Foundation#
SAP Financials is mature, comprehensive, and well-tested. For ANZ organisations, it handles local requirements well—GST, banking integration, and financial reporting. Success requires careful chart of accounts design, robust master data governance, and clear period-end processes.