C_TS410_2022 Core Finance: Financial Accounting (FI)

Core Finance: Financial Accounting (FI) Detailed Explanation

SAP Financial Accounting (FI) is a central component of SAP ERP that focuses on recording, managing, and reporting all financial transactions within an organization. It ensures compliance with legal and business reporting requirements.

2.1 Overview of Financial Accounting (FI)

What is Financial Accounting?

SAP Financial Accounting (FI) is responsible for recording, storing, and reporting financial transactions. It is integrated with other SAP modules (e.g., MM - Materials Management, SD - Sales and Distribution) to ensure seamless financial processes across the organization.

Purpose of Financial Accounting

The main goals of SAP FI are:

1. Record Financial Transactions: Every business activity (e.g., sales, purchases, payments) is recorded in real time.
2. Ensure Legal Compliance: Generate financial statements that comply with local and international regulations (e.g., IFRS, GAAP).
3. Provide Insights: Generate accurate and timely financial reports for decision-making.

Key Processes in SAP FI

SAP FI covers the following key processes:

1. General Ledger Accounting (G/L): The central repository for all financial transactions.
2. Accounts Payable (AP): Manages payments to vendors.
3. Accounts Receivable (AR): Tracks customer invoices and payments.
4. Asset Accounting (AA): Manages fixed assets, such as machinery and buildings.
5. Bank Accounting: Manages bank transactions, cash balances, and reconciliations.

2.2 General Ledger Accounting (G/L)

What is General Ledger Accounting?

• The General Ledger (G/L) is the central component of SAP Financial Accounting.
• It is used to record all financial transactions (e.g., revenue, expenses, assets, liabilities) for the entire organization.
• All transactions are stored in real-time, providing up-to-date financial data for reporting.

Key Features of G/L Accounting

1. Real-Time Financial Data:

   • Every financial transaction (e.g., sales, purchases) is automatically updated in the General Ledger.
   • Example: If you create an invoice in Accounts Receivable, it automatically updates the G/L.

2. Integration with Other Modules:

   • The General Ledger integrates with other SAP modules (e.g., MM, SD, CO) so that data flows seamlessly across the system.
   • Example: When goods are received in Materials Management (MM), the financial impact (inventory value) is recorded in G/L.

Key Elements of General Ledger

1. Ledger Types
   SAP allows businesses to use multiple ledgers for different reporting requirements:

   • Leading Ledger: The main ledger for recording accounting data. It follows the organization’s main accounting standard (e.g., IFRS).
   • Non-Leading Ledger: Secondary ledgers that can be used for parallel accounting.
     • Example: You can maintain one ledger for IFRS and another for local GAAP.

2. Chart of Accounts

   • The Chart of Accounts is a list of G/L accounts used by an organization to record transactions.
   • Each G/L account represents a specific type of financial activity (e.g., revenue, expenses, assets).
   • Types of Chart of Accounts:
     • Operating Chart of Accounts: Used for day-to-day accounting.
     • Group Chart of Accounts: Used for group-level reporting in multinational companies.
     • Country Chart of Accounts: Meets country-specific legal requirements.

   Example of G/L accounts:

   • Assets: Cash, Inventory, Buildings (1000-1999).
   • Liabilities: Accounts Payable, Loans (2000-2999).
   • Expenses: Rent, Salaries (4000-4999).
   • Revenue: Sales, Service Income (3000-3999).

3. Account Groups

   • Account Groups are used to organize G/L accounts based on their characteristics.
   • Example:
     • Cash Accounts (1010-1019).
     • Expense Accounts (4000-4999).
   • Account groups also control the fields available when creating a G/L account (e.g., profit center, cost center).

G/L Transactions in SAP

In SAP, you perform G/L accounting transactions using specific tools and transaction codes:

1. Post a G/L Document:

   • Transaction Code: FB50
   • Purpose: Manually enter a financial document into the G/L (e.g., rent payment).

2. Display G/L Balances:

   • Transaction Code: FS10N
   • Purpose: View the balance for a specific G/L account.

3. Display G/L Line Items:

   • Transaction Code: FBL3N
   • Purpose: Display detailed line items (individual transactions) in a G/L account.

Example of a General Ledger Process

1. A company pays $5,000 for office rent.

   • The accounting entry would be:
     • Debit: Rent Expense (G/L Account 4100) → Increases expenses.
     • Credit: Cash/Bank Account (G/L Account 1010) → Reduces cash.

2. The transaction is posted in real-time, and the G/L balance for both accounts is updated.

3. Reports such as the Trial Balance and Profit and Loss (P&L) Statement are generated based on this updated G/L data.

2.3 Accounts Payable (AP)

What is Accounts Payable?

Accounts Payable (AP) in SAP FI is used to manage and monitor vendor liabilities. It ensures accurate processing of vendor invoices, timely payments, and reconciliation of vendor accounts.

Key Processes in Accounts Payable

1. Invoice Processing

   • Enter and validate vendor invoices received for goods or services.
   • Invoice data includes:
     • Vendor Name
     • Invoice Date
     • Amount
     • Purchase Order Reference
   • Transaction Code: FB60 (Enter Vendor Invoice).

2. Payment Processing

   • Schedule and execute payments to vendors. Payments can be:
     • Manual (e.g., issuing a check).
     • Automatic (e.g., bank transfers).
   • Transaction Code: F110 (Automatic Payment Program - APP).

3. Vendor Reconciliation

   • Ensures that all vendor account balances match with actual invoices and payments.
   • Helps identify discrepancies, such as missing invoices or overpayments.

Key Master Data in Accounts Payable

1. Vendor Master Record

   • Contains vendor-specific data, such as:
     • General Data: Name, Address, Contact Information.
     • Accounting Data: Payment terms, tax details.
     • Purchasing Data: Default purchasing organization, currency.

2. Bank Master Data

   • Stores bank account details for processing vendor payments.

Example of Accounts Payable Process

1. A company receives an invoice from a vendor for supplying office supplies worth $2,000.
2. The Accounts Payable clerk enters the invoice using FB60.
3. The invoice is recorded in the Accounts Payable account (Vendor Liability).
4. When the payment is due, the company uses F110 to process the payment.
   • Debit: Vendor Liability Account → Reduces liability.
   • Credit: Bank Account → Reduces cash.

2.4 Accounts Receivable (AR)

Accounts Receivable (AR) is the component of SAP Financial Accounting (FI) used to manage and monitor customer receivables. It focuses on tracking invoices, payments, and overdue balances from customers, ensuring timely collection and proper recording of revenue.

Purpose of Accounts Receivable

1. Manage customer invoices generated from sales of goods or services.
2. Record incoming payments and reconcile them with outstanding invoices.
3. Track overdue payments and send dunning notices (reminders) to customers.
4. Integrate with Sales and Distribution (SD) to streamline sales order-to-cash processes.

Key Processes in Accounts Receivable

1. Sales Invoices

• When goods are delivered or services are provided, a sales invoice is generated.
• The sales invoice is created automatically via the Sales and Distribution (SD) module when a billing document is posted.
• The corresponding customer account in Accounts Receivable is updated with the invoice amount.

Example:

• A company sells goods worth $10,000 to a customer.

• The transaction would be posted as:

  • Debit: Customer Account (Receivable) → $10,000 (amount owed by the customer).
  • Credit: Revenue Account → $10,000 (sales income).

• Transaction Code for Manual Invoices: FB70 (Enter Customer Invoice).

2. Cash Receipts

• When the customer pays the invoice, the payment is recorded in Accounts Receivable and matched with the open invoice.
• Payments can be made via:
  • Bank transfers
  • Checks
  • Cash

Steps to Record Payments:

1. Post the incoming payment against the corresponding customer invoice.
2. The payment reduces the open balance in the customer’s account.

Transaction Code:

• F-28: Post Incoming Payments.

Example:

• The customer pays $10,000 for the earlier invoice.
• The accounting entry would be:
  • Debit: Bank Account → $10,000 (cash inflow).
  • Credit: Customer Account → $10,000 (reducing the customer’s receivable balance).

3. Dunning (Reminders for Overdue Payments)

• Dunning is the process of sending reminders to customers who have overdue payments. SAP automates the dunning process, ensuring timely follow-ups.
• Dunning Levels: SAP allows setting up multiple dunning levels with increasing urgency:
  • Level 1: Friendly reminder (e.g., 7 days overdue).
  • Level 2: Formal notice (e.g., 14 days overdue).
  • Level 3: Final demand before legal action (e.g., 30 days overdue).

Steps in the Dunning Process:

1. Identify overdue customer balances.
2. Generate dunning notices based on predefined levels.
3. Send notices to customers automatically.

Transaction Code:

• F150: Run Dunning Program.

Key Master Data in Accounts Receivable

1. Customer Master Record
   The Customer Master stores all relevant information about a customer. It is shared across SAP modules (e.g., SD and FI).

   Structure of Customer Master Data:

   • General Data: Name, address, contact details.
   • Company Code Data: Reconciliation account, payment terms, dunning settings.
   • Sales Area Data: Sales organization, pricing conditions, shipping details.

Example of Customer Master Setup:

• Customer Name: ABC Company

• Reconciliation Account: 140000 (Accounts Receivable Control Account)

• Payment Terms: 30 days net (payment due in 30 days).

2. Bank Master Data
   • Stores the bank details of customers for processing incoming payments.

Example of Accounts Receivable Process

1. Sales Invoice:

   • A customer purchases products worth $5,000.
   • The system generates the following accounting entry:
     • Debit: Customer Account → $5,000
     • Credit: Revenue Account → $5,000

2. Payment:

   • The customer pays the invoice via bank transfer.
   • The payment entry would be:
     • Debit: Bank Account → $5,000
     • Credit: Customer Account → $5,000

3. Dunning:

   • If the customer does not pay within the due date, the Dunning Program automatically generates a reminder notice.

2.5 Asset Accounting (AA)

Asset Accounting (AA) in SAP FI focuses on managing a company’s fixed assets throughout their lifecycle. Fixed assets include tangible assets (e.g., buildings, machinery) and intangible assets (e.g., patents, software licenses).

Purpose of Asset Accounting

1. Track the acquisition, depreciation, and retirement of fixed assets.
2. Ensure compliance with accounting standards (e.g., IFRS, GAAP).
3. Integrate asset data with General Ledger for financial reporting.

Key Processes in Asset Accounting

1. Asset Acquisition

• Asset acquisition refers to adding new assets to the system.
• Methods of acquisition:
  • Purchase: Buying assets from vendors.
  • Internal Production: Assets created internally (e.g., self-built machinery).
  • Donations or Transfers: Assets received without cost or transferred from other locations.

Transaction Code:

• F-90: Post Acquisition with Vendor.

Example:

• A company purchases machinery for $50,000.
  • Debit: Asset Account → $50,000
  • Credit: Accounts Payable → $50,000

2. Depreciation Calculation

• Depreciation refers to the reduction in an asset’s value over time due to wear and tear.
• SAP automatically calculates depreciation based on predefined rules and posts the depreciation entries to the General Ledger.

Depreciation Methods:

1. Straight-Line Method: Depreciation = Cost / Useful Life.
2. Declining Balance Method: Depreciation = Net Book Value × Rate of Depreciation.

Example:

• If a machine costs $10,000 and has a useful life of 5 years, annual depreciation using the straight-line method is:
  • $10,000 / 5 = $2,000 per year.

3. Asset Retirement

• Asset retirement occurs when an asset is sold, scrapped, or transferred out of the company.
• SAP posts the financial impact of asset retirement in the G/L.

Transaction Code:

• ABAVN: Retire an Asset.

Example:

• A machine with a net book value of $2,000 is scrapped.
  • Debit: Asset Retirement Loss → $2,000
  • Credit: Asset Account → $2,000

Master Data in Asset Accounting

1. Asset Master Record

   • Stores asset-specific details, such as:
     • Asset Class: Defines asset type (e.g., machinery, vehicles).
     • Useful Life: Number of years the asset will be used.
     • Depreciation Key: Method of calculating depreciation.

2. Asset Classes

   • Group similar assets together for reporting and control purposes.
   • Example:
     • 1000: Buildings
     • 2000: Machinery
     • 3000: Vehicles

2.6 Bank Accounting

Bank Accounting in SAP Financial Accounting (FI) focuses on managing and tracking bank transactions, cash flows, and balances. It ensures that all cash and bank-related activities are recorded accurately and reconciled with bank statements.

Purpose of Bank Accounting

1. Manage all bank accounts and cash balances within an organization.
2. Record and track incoming and outgoing bank transactions.
3. Perform bank reconciliation to ensure the company’s records match the bank statements.
4. Support electronic bank statements for automated bank transaction processing.

Key Functions in Bank Accounting

1. Bank Master Data

Bank Master Data includes all relevant information about the company’s banks, such as:

• Bank Name and Address
• Bank Key (unique identifier for the bank)
• Bank Account Numbers
• SWIFT Code (for international payments)
• IBAN (International Bank Account Number for European payments)

2. Bank Transactions

Bank Accounting in SAP FI captures two main types of transactions:

1. Incoming Payments: Cash inflow from customers, loans, or other sources.
2. Outgoing Payments: Cash outflow for vendor payments, salaries, and expenses.

Key Transaction Codes:

• F-28: Post Incoming Payments (customer payments).
• F-53: Post Outgoing Payments (manual vendor payments).

Example of Bank Transactions:

• A customer pays $5,000 via bank transfer.

  • Debit: Bank Account (cash inflow).
  • Credit: Customer Account (reduces receivable).

• A company pays $3,000 to a vendor:

  • Debit: Vendor Liability Account (reduces payable).
  • Credit: Bank Account (cash outflow).

3. Bank Reconciliation

What is Bank Reconciliation?
Bank reconciliation is the process of matching the company’s internal bank records with the bank statement received from the bank. The goal is to identify and correct any differences.

Steps in Bank Reconciliation

1. Upload the Bank Statement

   • Bank statements can be uploaded into SAP manually or automatically using the Electronic Bank Statement (EBS) process.

2. Compare Transactions

   • Match the transactions in the bank statement with the internal bank ledger.

3. Identify Differences

   • Differences may occur due to:
     • Outstanding Payments: Payments issued but not yet cleared by the bank.
     • Bank Fees: Charges or fees deducted by the bank.
     • Unrecorded Transactions: Bank credits or debits not yet recorded internally.

4. Post Adjustments

   • Post any missing or unrecorded transactions in SAP.

Transaction Code for Bank Reconciliation:

• FF67: Manual Bank Statement Processing.
• FEBA: Reconcile Bank Statement Transactions.

4. Electronic Bank Statements (EBS)

What is an Electronic Bank Statement?
The Electronic Bank Statement (EBS) allows businesses to upload bank statements electronically into SAP instead of processing them manually. This automates the bank reconciliation process.

Steps in the EBS Process

1. Bank Statement Import

   • The bank provides a file (e.g., MT940, BAI2 format) containing all bank transactions.
   • This file is uploaded into SAP using Transaction Code FF_5.

2. Automatic Transaction Matching

   • SAP automatically matches the transactions from the bank statement with internal records based on:
     • Amounts
     • Dates
     • Document Numbers

3. Post Clearing Entries

   • Transactions are automatically posted to clear open items (e.g., customer payments, vendor payments).

4. Handle Exceptions

   • Unmatched transactions are flagged for manual review and correction.

Advantages of EBS

• Reduces manual effort and errors.
• Speeds up bank reconciliation.
• Provides real-time visibility into cash balances.

Example of Bank Reconciliation Process

1. The company uploads a bank statement file for the previous month.

   • The bank statement shows:
     • Incoming Payment: $10,000 (customer payment).
     • Outgoing Payment: $7,000 (vendor payment).
     • Bank Charges: $50.

2. SAP matches the incoming and outgoing transactions:

   • Incoming Payment: Clears the open customer invoice.
   • Outgoing Payment: Clears the open vendor liability.

3. The bank charges ($50) are posted manually:

   • Debit: Bank Charges Expense Account → $50
   • Credit: Bank Account → $50

Key Reports in Bank Accounting

1. Cash Position Report: Displays current cash balances in all bank accounts.
2. Bank Reconciliation Report: Shows reconciled and unreconciled items.
3. Statement of Cash Flows: Tracks cash inflow and outflow over a period.

Transaction Codes for Reporting:

• S_ALR_87012301: Cash Flow Statement.
• FF7B: Cash Position Report.

Summary of Bank Accounting

1. Purpose: Manage bank accounts, record transactions, and reconcile with bank statements.
2. Key Processes:
   • Recording incoming and outgoing payments.
   • Automating bank reconciliation through EBS.
3. Master Data: Bank details, account numbers, and transaction formats.
4. Tools:
   • F-28: Post incoming payments.
   • F110: Automatic payments.
   • FF67: Manual bank reconciliation.
   • FF_5: Upload electronic bank statements.

Core Finance: Financial Accounting (FI) (Additional Content)

1. Reconciliation Accounts in Customer and Vendor Master Data

What Is a Reconciliation Account?

A Reconciliation Account is a type of General Ledger (G/L) account used to automatically link subledger accounts (such as customers in Accounts Receivable and vendors in Accounts Payable) to the General Ledger.

In SAP, customer and vendor master records each contain a field for the Reconciliation Account. This configuration ensures that:

• Every transaction posted to a customer or vendor is also automatically posted to the corresponding G/L account.
• Manual entries into reconciliation accounts are not allowed, preserving data consistency between subledgers and the general ledger.

Why It Matters

This mechanism is essential for maintaining real-time integration between FI and its submodules (AR/AP). Without reconciliation accounts, financial reporting and balance integrity between subledgers and the general ledger would be compromised.

Suggested Placement

When covering Accounts Receivable (AR) and Accounts Payable (AP), it’s useful to include a sentence such as:

"Each customer/vendor master must be assigned a Reconciliation Account, which ensures that all transactions in AR/AP are automatically reflected in the General Ledger, maintaining real-time synchronization and accurate financial statements."

2. Introduction to Document Splitting

What Is Document Splitting?

Document Splitting is an advanced feature in SAP Financial Accounting (FI) that allows automatic splitting of accounting entries based on dimensions such as profit center, segment, or business area.

Purpose and Benefits

• Enables detailed segment-based or profit center-based reporting for Profit & Loss and Balance Sheet accounts.
• Helps meet legal or management reporting requirements in organizations with multiple divisions or entities.

How It Works

When document splitting is active:

• SAP automatically assigns financial line items to relevant dimensions, even if they are not explicitly entered.
• For example, if an expense is posted to a cost center linked to Profit Center A, the system will split and assign all relevant lines (e.g., tax, vendor, clearing accounts) to the same profit center.

Example Scenario

If an invoice is posted for office supplies linked to Cost Center 1000 (Profit Center A), document splitting will ensure:

• Expense line is posted to Profit Center A.
• Vendor payable line is also assigned to Profit Center A, even if not entered manually.

Suggested Positioning

You can briefly introduce document splitting in the General Ledger (G/L) reporting section with a note such as:

"To enable detailed financial reporting by dimensions like profit center or segment, SAP FI provides a feature called Document Splitting. It ensures all line items within a document are automatically assigned to the appropriate reporting dimension."