Friday, December 31, 2010

SAP Treasury

  1. Treasury / Bank

  1. Define House Bank
  • Tcode: FI12
  • Display all bank master records: SE16 – BNKA
  • Display Changes to all Bank Master data : SE8- RFBKABL0
  • Explanation:
    • House bank: A HB is identified by a unique bank key. A HB is tied to a company code.
    • Bank key: Enter the bank key. Available in US, Europe
    • Bank Account number: Bank a/c number given in the bank statement
    • GL a/c: GL account from COA to which this bank a/c is tied up
    • Control Key: Used for US bank to identify whether a checking a/c (01) or a saving account (02). If no entry system defaults to checking account (01)
    • The payment program uses the House bank ID and Account ID to determine the bank to be used for payment to customer / vendor
    • Bank GL a/c in FS00 : Account ID together with the ID for the house bank uniquely defines a bank account

  • Data:
Company codeHBA/C IDGL A/CCurrencyBank

  1. Electronic and Manual Bank statement:
  • EBS: It is an electronic statement sent by the bank which gives details of transactions done by the account holder. The EBS can be in the format SWIFT, BAI, Multicash etc. This statement is uploaded in SAP and it clears the various clearing account such as check out, check in to the main bank account
  • GL codes in our scenario:
ParticularsMainCheck InCheck OutBank Charges
Account IDMAIN
Bank a/c number135791000210003
GL a/c number113400113108113101479000

  • Accounting Entries:
    • Check Issues to Vendors:
      • Vendor a/c Dr.
        • To Check Out ( 113101)
    • Check Received from Vendors:
      • Check In ( 113108) Dr
        • To Vendor a/c
  • When Bank statement (EBS) is uploaded in SAP following entries passed:
    • For checks issues to vendors:
      • Check out (113101) Dr
        • To Main a/c ( 113400)
    • For checks received from Vendors:
      • Main a/c (113400) Dr
        • To Check In (113108)

  1. Make Global settings for EBS
  • Tcode: SPRO – Financial accounting – Bank Accounting – Business Transactions- Payment Transactions – EBS – Make Global settings for EBS
  • Explanation:
  1. Enter COA: CAUS
  2. Create Account Symbols.
  3. Assign these account symbols to GL accounts
  4. Create keys for posting rule
  5. Define Posting Rule: Here assign posting rules to the accounts symbols created. For define posting rule refer to Top jobs Bank config.

COACAUSGL accountPosting Rule
MAINBANKMain Bank Account113400
CHECKINCheck Received In113108A104
CHECKOUTCheck Issued Out113101A101

  1. Additional steps for manual settings:
  • Tcode: SPRO – Financial accounting – Bank Accounting – Business Transactions- Payment Transactions- Manual Bank Statement – Create & assign business transactions
  • Explanation:
    • Create Account Symbols.
    • Assign these account symbols to GL accounts
    • Create keys for posting rule
    • Define Posting Rule: Here assign posting rules to the accounts symbols created. For define posting rule refer to Top jobs Bank config
  • Data:
TransactionPosting ruleText
CHINA104Check received in
CHOUA101Check Issued Out
BKCHA105Bank Charges

  1. Define variants for manual Bank statement
  • Tcode: SPRO – Financial accounting – Bank Accounting – Business Transactions- Payment Transactions- Manual Bank Statement- Define variants for manual bank statement

  1. Define Posting keys and posting rule for check deposit
  • Tcode: SPRO – Financial accounting – Bank Accounting – Business Transactions- Check deposit – Define posting keys and posting rule for check deposit
  • Data:
    • ACHK


  1. Create and assign business transactions;
  • Tcode: SPRO – Financial accounting – Bank Accounting – Business Transactions- Check deposit – Create and assign business transactions

  1. Define Variant for check deposit
  • Tcode: SPRO – Financial accounting – Bank Accounting – Business Transactions- Check deposit – Define variant for check deposit
  • Data:
    • A0001

  1. Define number range for checks
  • Tcode: FCHI
    • Checks can be printed on site using MICR (Micro encoding printer). MICR should be configured only to PRA / PRD. To avoid misuse of checks

  1. Cash Journal
  • << Refer TFIN>>

  1. Manual Check Deposit
  • Tcode: FF68
  • Explanation:
    • Before entering checks you need to define what entry variant you'd like to use and how do you want to post process the checks. Select from the menu path Settings – Specifications
    • In the field Processing type you can also use key 4 – Further processing online, instead of 2 – Further processing as batch input (generate batch). In such case, after posting of checks, the system will not create batch input session, but will post the documents automatically. However, to complete the process you need to use the transaction code FEBA (Post process) to check the results of this automatic posting and eventually complete the postings
    • Click Transfer value date
    • Click <checkbox> Int. bank determin. . Instead of entering full bank account number, you can now use short bank name, defined in the system
    • When you enter the check data and save your statement, the system will display a report (log) presenting which items have been cleared automatically and what is the number of items that still need to be cleared manually. This report shows postings separately for GL account and for sub-ledger (AR). In the column Errors you can see how many transactions needs to be processed manually. In this example
    • Also refer the end user documentation
  • Accounting ® Financial Accounting ® Banks ® Incomings ® Check Deposit ® FEBA - Post process

Field Name
Start variant
You can change the variants at any time during memo record processing.
Example: A0001
Customer matchcode IDUsing this matchcode ID, the system searches for customers
Example: D
Processing typeUse this field to control whether postings via batch input are carried out online or as a background job.
Example: 4

  • FEBA Table:
    • FEBKO

  1. Import Electronic Bank Statement (FF_5)
  • Tcode: FF_5
  • Explanation:
    • Using this function you can import bank statements into the system and then process them. This report can perform automatic postings or create batch input session. It posts to G/L accounts and to sub-ledger accounts
    • For incoming payments, the notes to payee lines of the account statement can be searched either for document numbers or reference document numbers by specifying the selection field (BELNR or XBELNR). Thus, the relevant information for clearing customer payments is obtained.
    • If you do not specify a selection field, the note to payee fields are not interpreted and you need to clear open items manually (use transaction FEBA – Post process)
    • For outgoing payments, the system always searches for the document number
    • BELNR number interval: Specify search criteria for incoming payments. The account statement will be searched for FI document numbers. This information is necessary for clearing customer payments.
    • After posting electronic bank statement use transaction FEBA Post process account statement to check have all the documents been posted and post / clear manually some documents, if necessary

  1. Create Bank Master Record (FI01)
  • Tcode: FI01
  • Explanation:
    • Bank Master Records are stored in the bank directory. Their details are stored also in Customer / Vendor Master Data and are used by payment program to prepare payment documents. You can create new Bank Master Record using transaction FI01
    • Bank Key: Bank key is the bank code. This field is country specific. Usually the bank key consists of first 8 digits of your full bank account number and is followed by "hyphen" –

  1. Change Bank Master Data
  • Change Bank Master Data: FI02
  • Display Bank Master Data: FI03
  • Display Bank Master Data Changes : FI04
  • Explanation:
    • On this screen system usually displays all the fields that were changed. In our example the value of the field Name of Bank was changed. To display more details regarding changes, double-click on this field. To check who is "responsible" for these changes, click Bank name field

  1. Mark for Deletion Bank Master Data
  • Mark for Deletion Bank Master Data : FI06
  • Explanation:
    • Cannot delete your bank master directly. Can only mark bank master for deletion. To completely remove the bank master from the database need to run a special archiving program

  1. Edit Bank Chain
  • Edit Bank Chain : FIBPU
  • Display Bank Chain for Creditors/Debtors: FIBPS
  • Explanation:
    • Bank chains are used to make payment via more than one bank, for example via the correspondence banks of the house bank, the recipient bank, or the intermediary banks. This document describes how to create a bank chain for customers and vendors
    • Prerequisite: Customer / Vendor master records need to contain bank data: bank account & bank key
    • Refer to top job documentation on FIBU

  1. FEBA Post process
  • Explanation:

    The transactions (line items) marked with green ticks have been processed automatically – system has found the relevant open items, based on reference document number and customer name and cleared them automatically. The transactions marked with red ticks need to be processed manually

    Double-click the required check statement. System will display a document overview

    To process this document, select from the menu path: Line items-Post

    Account: Code identifying the Customer account

    Select the required open item and click Save

S_ALR_87009895VAT ReportUse this SAP transaction to view VAT reporting and to post VAT settlement.

Transaction is run at month end after transactions have been completed. When settlement is run the balances of the 11005001 output tax and 22010000 input tax accounts are zeroed out and the balance of each is moved to the 12600000 VAT Settlement account.
SM35 Batch Input MonitoringUse this SAP transaction to monitor and process batch input sessions to post all the applicable documents and perform all the database updates.



  1. Adding VAT Codes

  1. Check Calculation Procedure
  • Tcode: IMG - Financial Accounting- Financial Accounting Global Settings- Tax on Sales/Purchases- Basic Settings - Check Calculation Procedure – Define Procedure
  • Tcode : OBYZ
  • Explanation:
    • Copy tax procedure TAXGB. Change it to TAXIN
    • These are standard Tax calculation procedure provided by SAP.

  1. Assign Country to calculation procedure (Check country assigned to a tax calculation procedure)
  • Tcode: OBBG
  • Tcode: IMG - Financial Accounting- Financial Accounting Global Settings- Tax on Sales/Purchases- Basic Settings - Check Calculation Procedure – Assign country to calculation procedure
  • Explanation:
    • Each country has a tax calculation procedure assigned to it.
    • Here we can check what tax calculation procedure has been assigned to the concerned company code.

  1. Check Access Sequences, Tax Condition Type
  • Tcode: OBYZ

  1. Tax Jurisdiction structure
  • Tcode: OBCD

  1. Sales & Use Tax Automatic assignment
  • Tcode: OB40

  1. Define Tax codes for Sales and Purchases
  • Tcode: IMG - Financial Accounting- Financial Accounting Global Settings- Tax on Sales/Purchases- Calculation – Define tax code for sales and purchases
  • Tcode: FTXP
  • Explanation:
    • Here we define the tax rate for the tax code. Also map the G/L account to which tax amount postings are made
    • Easiest way to create a new tax code is to copy the existing tax code whose tax rate has to be changed in FTXP. Change description & rate

  1. Steps in SAP for creating a new VAT code : EMEA
(For Company code 730 Neon & reporting country XX say PT (say tax procedure TAX_NB):

  1. Check for the gaps in the table T007A for the new tax code to be created. (We need to check that a 2 digit tax code can be created, & it does not exist already)
  2. Go to Tcode FTXP. Copy from the existing tax code, change the %, change the description, check the account mapping & save the new tax code
  3. Please note the following before creating the tax codes
Tax procedure
Tax code
Should be same

  1. In different tax procedures, same tax code can be created. However the mapping of Transaction Key& Account should NOT change.
    1. For example:
    2. Tax code1V can be created in Tax Procedure TAXAR, TAXPT & TAX_NB. However, Transaction Key VST = 11005000 in all the tax procedures.
  2. Never change an existing account mapping as that will affect countries which are already using that code
  3. A tax code like 1V can have different tax rates in different tax procedures but ACCOUNT MAPPING remain the same. To check all tax rates used for a tax code use report S_ALR_87012365

  1. VAT new Tax code Creation Business Process:
  2. A Kintana is always required.
  3. Approval should be taken from Winco Rebergen before creating any tax code.
  4. We first create the tax codes in PSQ and ask the user to test them in PSQ. At testing stage also, Winco Rebergen, Florence ten Cate and Matti Uoti should be kept informed.
  5. Once user tests the tax codes successfully, attach the sign off to the Kintana, create the new tax codes in PRD and inform all the parties mentioned above.

  1. Advance Return for Tax on Sales/ Purchase
  • Tcode: S_ALR_87012357
  • Explanation:
    • Page 1 shows totals for Output tax by Tax Code.
    • Page 2 shows totals for Input tax by Tax Code.
    • Page 3 shows totals for each company code selected, by Tax Code.
    • Page 4 shows totals for all company codes selected, by Tax Code.
    • It is necessary to clear the amounts in the Tax Clearing account to ensure that the tax payable/receivable to Accounts Payable or Accounts Receivable, is created in order to be paid via the automatic payment program (F110) or paid and cleared via the Incoming Payments (F-28) procedure. Although the above procedure calculates and posts the tax payable/receivable to the tax payable/receivable account, this account needs to be cleared and paid.
    • The tax payable/receivable Account is managed as 'Open Item' and as such a clearing procedure needs to occur in order to pay the values to the Statutory Authorities. Therefore, the value of Tax to be paid needs to be identified. This can be achieved by an inquiry on the tax payable/receivable account in the general ledger by posting dates and unclear items.

  1. Tax Posting (AP/AR)
  • Tcode: FB41

  1. VAT Configuration

Tax on Sales/Purchases
Basic Settings    
Check calculation procedureCheck calculation procedure - condition typesOBQ1
Check calculation procedureCheck calculation procedure - access sequencesOBQ2
Check calculation procedureCheck calculation procedure - proceduresOBQ3
Check country assigned to calculation procedure  OBBG
Check and change settings for tax processing  OBCN
Fiscal Regional CodesDefine fiscal regional codes for Italy/SpainOBAD
Fiscal Regional CodesDefine fiscal regional codes for other countriesOBAE
Define taxes on sales/purchases codes  FTXP
Specify base amount  OB69
Define tax accounts  OB40
Define account for exchange rate difference posting  OBYY
Allocate tax codes for non-taxable transactions  OBCL

  1. Configuration steps : Basic Settings, Calculation, and Posting
    1. SAP uses condition types (e.g., MWAS sales tax and MWVS input tax) as the basis of a calculation procedure, which enables integration between the SD, MM, and FI modules.
    2. Create an Access Sequence (MWST Tax Indicator) and underneath it an access code (10 (Table 3) Tax Code).
    3. Create a calculation procedure for each country or jurisdiction for which you need one (for example, TAXF = sales tax for France and TAXIT = sales tax for Italy). Behind this you put a control procedure, which defines the calculation steps (TAXF).
    4. Procedure TAXF Sales Tax – France:
StepsControlCondition TypeDescriptionFrom
1000BASBBase Amount
1100MWASSales Tax100
1200MWVSInput Tax100
1400MWVNNon Deductible input tax100
1500NLXAAcquisition tax credit100
1600NLXVAcquit ion tax debit150

  1. Next assign a country to a calculation procedure (AT Austria = TAXAT).
  2. Check and change settings for tax processing as follows:

TextOutput Tax
Tax Type1 Output Tax
Not deductibleNot used here
Posting indicator2 Separate line item

  1. Define tax codes, which will be used in transactions. (Tcode: FTXP)
Country keyFR
Tax codeD1
Tax TypeV
Behind the VAT code define its properties
Tax codeD1 Deferred input tax - standard rate 19,6%
Tax TypeV Input tax
CheckSelect if SAP to check calculation
Target tax code V1This tax code transfer input tax to code V1 when related invoices area paid
Assign GL a/c to the tax code
  1. Tcode FTXP / OB40. Maintained in table T030K
  2. When entering tax codes with no tax rate, entering 0 rate allows accessing them. Also need to assign GL a/c to these tax codes.

  1. Finally, tax codes have to be allocated for non-taxable transactions, outside the scope of VAT (e.g., general ledger journal entries between accounts which require a valid tax code) – e.g.:
  2. Input VN and Output AN. The codes are created in the normal way first, but with a zero percentage rate. Use Tcode OBCL to jump directly to where these tax codes are defined.

  3. VAT Return configuration
  4. When configuring VAT processing it is also necessary to maintain Table TRVOR (with transaction code SM31) and enter the company code and fiscal year against the ABAP which runs the advance tax return (e.g., RFUMSV20 for Italy and Spain prior to Release 4.6C) and against the ABAP which runs the document journal (RFBELJ10). Otherwise the report will not run and the error report does not tell you much except to point you towards Table TRVOR.
  5. This table links the company codes to the ABAP used to run the document journal RFBELJ10 and to the ABAP used to generate the advance tax return RFUMSV00 (and previously RFUMSV20). It is essential to maintain it or the advance tax return will not run.