SAP FICO Tcodes List: Most Used Transaction Codes for Finance Professionals

SAP FICO Tcodes List: Most Used Transaction Codes for Finance Professionals

SAP FICO is the core of the finances for almost all large corporations, and nearly all actions performed in this module start with Tcodes. The article describes the most used Tcodes for SAP FICO, also known as SAP FICO transaction codes, explaining the purpose, usage and mistakes made in using them. The information will be helpful for accountants, finance executives, SAP novices and people who are going to take the position of SAP FICO specialist or SAP FICO consultant.

What Are SAP FICO Transaction Codes (Tcodes)?

Transaction code or Tcode is a set of letters, numbers and sometimes symbols, which opens a concrete window or functionality in SAP. Instead of opening numerous screens of the SAP Easy Access menu, you enter the code in the field of the command line situated in the upper left corner and press Enter. Thus, entering FB50 opens the window for entering general ledger documents.

There are two modules of SAP FICO : Financial Accounting (FI), which includes external reporting and includes such modules as general ledger, accounts payable, accounts receivable, bank accounting and asset accounting; and Controlling (CO), which is connected with internal reporting, such as cost centers, internal orders, profit centers and profitability analysis. In this article we will speak about the FI side, including the most important SAP FI tcodes.

Tcodes are also connected with security issues: each user is given a certain authorization role, which determines the codes available for the user. The payable clerk sees only Tcodes related to the vendors, while the finance manager sees the period-end and reporting Tcodes. When you enter a code and receive an authorization error, it means that you do not have the rights to use it and the best thing you can do is to contact the SAP security department.

Knowing the list of Tcodes allows to save time, reduces the number of mouse clicks and increases the confidence in the system. There are some useful tips for working with Tcodes: entering /n before the Tcode, such as /nFB60, opens the new transaction in the same session; entering /o before Tcode opens the new transaction in the new session window; entering /next closes SAP.

Most Used SAP FI (Financial Accounting) Transaction Codes

The FI module records all the financial transactions of a company in a structured and auditable manner. The most commonly used codes are in three categories: General Ledger, Accounts Payable and Accounts Receivable. Together they cover postings, master data, payments, reports and changes. The best way to build a solid working knowledge of SAP FI is to learn these groups one by one, which is also how most SAP FICO training programs and SAP FICO interview preparation guides are structured.

General Ledger (GL) Accounting Tcodes

The general ledger is the book of accounts. All postings from payables, receivables, assets and materials management go here. GL Tcodes are used for manual journal entries, balance checks, clearing and period control.

For posting, the most common codes are FB01, which is the general posting transaction, and F-02, which is used for general ledger postings with a standard document entry screen. FB50 is a simplified screen for entering GL account documents and is the one most users prefer for accruals, provisions and adjustments. If you want to park a document for approval before it affects the books, you can use FBV1 to park it and FBV0 to post or change the parked document later.

FB08 reverses a posted document. FB02 changes some fields of an existing document, like the reference text or assignment. FB03 is a document display and is probably the most used display code, because users constantly need to check what a posting looks like. If a clearing is done incorrectly, FBRA will reset and undo the clearing.

FAGLB03 – General ledger account balances. FS10N – Balances by month. FAGLL03 – General ledger account line items with flexible selection options. F-03 is used to manually clear a GL account while F.13 is used to automatically clear many accounts at once which is useful at month end. OB52 is for opening and closing posting periods so nobody posts into a period that is already nailed down.

Accounts Payable (AP) Transaction Codes (Tcodes)

Accounts Payable handles everything vendor related from opening the supplier to paying the final invoice. A well-controlled payables process helps to protect supplier relationships and enables the company to take advantage of early payment discounts.

XK01 is used to create vendor master data with complete vendor record or FK01 for accounting view only. It is modified by XK02 or FK02 and shown by XK03 or FK03. Blocking a vendor for posting or payment is done with FK05 or XK05. A key control in finance is having clean vendor master data with the correct bank details and payment terms.

There are several ways invoices are posted. FB60 is used to enter vendor invoices directly in finance. F-43 is an alternative screen to do the same. MIRO is used when the invoice is associated with a purchase order and a goods receipt. This is the normal flow for the purchase of materials and services. Posting vendor credit memos with FB65 or F-41

FBL1N shows vendor line items, FK10N shows vendor balances and S_ALR_87012078 shows vendor due date analysis for review. F110 is the automatic payment program. F-53 posts manual outgoing payments for payments. F-44 clears vendor accounts manually. This is necessary when a credit memo needs to be matched to an invoice without a payment.

AR Transaction Codes

Accounts Receivable is about customers and what they owe. The key is to get the billing right, collect on time and have a clear view of what is overdue.

Create customer master data using XD01 (all views) or FD01 (accounting view). Changed with XD02 or FD02 and displayed with XD03 or FD03. FB70 or F-22 to post customer invoices FB75 or F-27 to post customer credit memo’s In many companies the customer invoices are created from the Sales and Distribution module. So FB70 is mainly used for items which do not originate from a sales order.

When the money comes in, F-28 posts the received payment against the open invoices. In F-32, customers' accounts are cleared manually, which can be handy for reconciling credit memos to invoices. Reporting-wise, FBL5N will display customer lines and FD10N customer balances. Collections-wise, F150 is where the dunning run happens for generating the payment reminders, and FD32 manages the customer's credit limit. A thorough understanding of these codes will enable you to manage cash flow better and reduce arrears.

FB50, FB60 and FB70: Document Entry

FB50, FB60 and FB70 are the three posting codes which finance users are introduced to first since they deal with the three most commonly used manual entries, i.e., a journal entry, a vendor invoice and a customer invoice.

F110 and F-53: Payment Run and Outgoing Payments

Payables to suppliers is a critical process in finance, and SAP provides two main ways of doing this.

The first one is the automated payments through the F110 program, also called the SAP automatic payment program. This enables one to make payments for hundreds or even thousands of invoices at once through one single controlled process. One begins by inputting the date and identification number that will define the run. Under the parameter section, one needs to provide the company codes, methods of payments, next payment run date and vendor range to include. The system automatically selects the invoices that need to be paid based on the due dates and payment terms among other things. This suggestion can be reviewed and blocked or adjusted. After review, one schedules the payment run.

F110 provides robust control. The system uses configured payment means, house bank and discount configuration, and logs all the steps. With such an ability to make numerous payments, the crucial point is the proposal review procedure.

F-53 is the posting tool to perform the manual payment. In order to perform the operation, the user must specify the document date, company code, bank account, amount and the vendor to perform. After the user identifies the items to be paid, the system makes the payment and clears the identified invoices. F-53 is helpful when performing urgent payments, advance payments, one-time payments and payments requested by the vendor outside the run. In most of the cases, F110 should be applied for ordinary payments, while F-53 is an exception.

FS00 and FSP0: GL Account Master Maintenance

The GL account master record influences the behavior of the account on postings and reporting. Since all transactions will be based on the above settings, extra caution is required in master data maintenance.

FS00 is the transaction that deals with GL accounts. You can use this transaction to create, modify, display, block for posting or delete an account. It includes the functionality of the chart of accounts master and the company code master on a single screen. The fields that you need to fill out on the chart of accounts side include the account number, account type like balance sheet or profit & loss, and the account group. The fields to be filled in on the company code side include the currency, the tax category, if the account is a reconciliation account, and if the open item management and line item display are possible or not.

FSP0 is employed solely for the maintenance of the chart of accounts. It may prove beneficial in those organizations where a central finance or master data team maintains the account structure across the group while each company code extends the account in its own manner through another transaction, that is FSS0. Such a segregation helps to ensure consistency across the group chart of accounts.

A few settings must be considered in special detail. Open item management is to be enabled for accounts like clearing accounts where individual items need to be reconciled. Line item display must be activated for accounts for which users require line item display. Accounts for reconciliation cannot be posted manually, thereby ensuring the consistency of sub-ledger with the general ledger system. Any changes made to GL master data would affect reporting for years, hence should always be documented.

FBL1N, FBL3N and FBL5N – Line Item Reports

Line Item Reports are the daily reports that help investigate what exists within the account. These reports have similar screens and layouts, hence the skills can be transferred from one to another.

FBL1N shows Vendor Line Items. This report is used to investigate what invoices are open, paid and the payment status of a particular vendor. FBL3N shows GL Account Line Items. It is used to investigate all the postings made to the account like a clearing account or an expense account. FBL5N shows Customer Line Items. It is used to investigate outstanding invoices and payments.

In the selection screen, you provide the account number, company code and the status of the items you would like to view. Open items, cleared items, or all items can be provided as statuses. If open items are selected, then you provide the key date as to what was open in the past date, which is useful in the case of month end and year-end reconciliation. In the output, you get the list that can be sorted, filtered, subtotaled and downloaded to an excel spreadsheet. The report can be customized by selecting columns you want to display, including reference, document type, due date or assignment.

The reports are used for account reconciliations, vendor and customer statements, audit queries, aging analysis and to resolve payment disputes. When a supplier calls up asking why the invoice has not been paid, FBL1N is generally the first report opened by the finance user.

Common Mistakes While Working With FI Tcodes

Experienced professionals can also make mistakes in the SAP FI process, but the majority of them are avoidable by just showing a bit of discipline.

Posting in the wrong period is one of the most common mistakes. It can happen due to inaccurate inputting of the posting date or an open period after the end of the month. As the consequence of that, the expenses or income will be posted in the wrong month, which makes the reports false. Double-check your posting date and ensure the closing of the period by the finance department using OB52.

Skipping the simulation step is another very common mistake. It can lead to incorrect postings, because the user saves a document without checking whether the correct GL account, tax code or cost center is selected.

Rushing into F110 without due diligence on the proposal can result in very costly errors, such as duplicating payments, paying blocked or incorrect vendors, or paying invoices that are not yet authorized. Always ensure that you review the proposal, review the exception list and get it cleared by a second person for large runs where policy demands it.

Not clearing your uncleared items is another practice that lands you in a fix. If you make payments that are not matched with the invoices, the account balances of the vendor and customers are overstated, making the reconciliation and aging very difficult. Ensure you always clear uncleared items through F.13.

Other errors involve use of the wrong company code, Entry of incomplete and inconsistent reference text, postings to reconciliation accounts by workaround, and alteration of master data without prior authorization. These reduce the quality of financial information.

The best defense is adopting some simple practices Ensure dates are checked before postings, simulate before posting, assess proposals prior to payment, clean postings regularly, reconcile accounts on a monthly basis and follow master data authorization procedures. The users who adopt such practices work faster, make fewer corrections and generate better financial reports.

We have established an SAP FICO WhatsApp group to provide transaction codes which are frequently used in a concise and practical manner. This WhatsApp group is meant for finance professionals, accountants, students and SAP newcomers who want to work faster in SAP and learn SAP FICO online. Each day, you will receive easy explanation of commonly used transaction codes including FB50, FB60, FB70, F110, F-53, FS00 and FBL1N together with examples and tips.