For SAP Project Implementation, Project Support, Placement, Training and Certification reach me at "SAPISPTC@gmail.com"
SAP - FI AR : Configuration of Dunning - Customer / Vendor
SAP - FI AR BK: Electronic Bank Reconciliation
Each uploaded electronic bank statement will be assigned with a unique no. in SAP and can be printed retrospectively.
1. Electronic Bank Statement file (in SWIFT MT940 format) is extracted from BANK
2. Data (SWIFT MT940 for BANK) is imported into a temporary dataset in SAP
3. Batch input sessions are generated (per bank statement: one session for G/L Accounting and one for Subledgers- AR/ AP). Bank accounting and subledger accounting batch session can be executed separately or jointly
4. Posting rules and account determination are defined in TR-CM customization
5. As an electronic bank statement is being imported, the system identifies the transactions in it and determines how they are posted.
6. The note-to-payee fields in the electronic bank statement contain various information relevant to open item clearing. Note to payee fields can be interpreted by document number or reference document number for the clearing transaction (example: standard algorithm). If the algorithms we deliver are not sufficient, it is possible to program a user exit tailored to your business (e.g. change the posting rule; influence account determination by means of account modification).
7. Post-processing for posting proposals(line items) which cannot be cleared
Note:
Electronic Bank Statement format SWIFT MT940 is compactable with SAP TR-CM. Standard algorithm for clearing documents is available in the predefined form in SAP. Customisation, as stated in point 6 above, will be needed to cope with AAA specific requirements on Bank Reconciliation. The review task will be performed on the Detail Design Phase, detail of which will be incorporated into the respective customisation functional specifications.
Step-by-Step Procedure for Customizing an Electronic Bank Reconciliation Statement
- Create House Bank and Account ID (FI12)
- Setup EDI Partner Profile for FINSTA Message Type (WE20)
- Configure Global Settings for EBS (IMG)
- Create Account Symbols
- Assign Accounts to Account Symbols
- Create Keys for Posting Rules
- Define Posting Rules
- Create Transaction Types
- Assign External Transaction Types to Posting Rules
- Assign Bank Accounts to Transaction Types - Define Search String for EBS(Optional)
- Search String Definition
- Search String Use - Define Program and Variant Selection
Additional information is also available in the SAP Library under:
Financial Accounting > Bank Accounting (FI-BL) > Electronic Bank Statement >
Electronic Account Statement Customizing
Difference between VF04 & VF06
VF04 is used to MAINTAIN BILLING DUE LIST based on the Delivery date as default, Means the Delivery documents which has the same date and for which the Billing has to create on a particular date uses this Transaction
VF06 is used to create the Billing for all the Deliveries irrespective of Date,
You have to give the Billing data for VF04 and it is not required for VF06 (in summary).
In VF06, you can also schedule the invoice printing with required date and time. Once the system date and time reaches this, it will run in background.
SAP FI: Cross Comapny Code Transaction
2. Transaction posts to accounts in several company codes
3. In order to balance debits and credits within these documents, the system generates automatic line items which are posted to clearing accounts, for payables or receivables.
4. These documents linked by cross-company code transaction number
5. In this case tax is not distributed between the company codes according to their expenses.
6. Therefore this function may only be used if the transaction itself is not tax-relevant or if the company codes form a taxable entity.
7. Tax calculated is always posted to the company code of the first item – so invoice item always must be entered first
8. Certain countries’ tax regulations require that the tax amount are posted in the company codes in which the expenses occurred - therefore the tax must be distributed from the first company code to the other company codes according to their expense amount – RFBUST10
9. Clearing accounts:
> Must define in every company code before a CCC transaction carried out
> Clearing accounts may be GL accounts, customer, or vendor accounts
> Must assign to every possible combination of two company codes
> Posting keys must be assigned to the clearing account to identify their account types.
> CCC Document number is a combination of the document number of the first company code, first company code number, and the fiscal year.
> Stored in the document header of all of the documents created for a complete audit trail
> CCC document may be reversed
10. Cross Company codes of a cross-company code transaction may have different local currenciesExamples: Central Purchase / Central Payment.
SAP FI / MM / SD : Tax
i. Tax on sales/purchases
ii. US sales tax
iii. Additional taxes (country-specific)
iv. WHT
§ With the provision for two taxation types:
i. Federal/country level - national level, with uniformly defined rates.
ii. State/jurisdiction level - rates defined by state/jurisdiction
§ In some countries taxes are even levied on both levels.
§ System supports:
i. Calculating the tax amount
ii. Posting to defined tax accounts
iii. Performing tax adjustments - for cash discounts or other form of deductions
iv. Tax reporting
§ Calculates the tax amount from:
i. Base amounts w (gross) or w/o (net) a cash discount (exp / revenue)
ii. Tax codes to check or calculate the tax amount
§ National regulation determine whether tax base amount is gross / net – you have to define which is to be used for each CC or for the highest level of the jurisdiction code.
§ Tax on sales and purchases: is the balance of the output tax and input tax
i. Output: on the net value of the goods and is billed to customer – liability of company to tax authorities
ii. Input: on the net invoice amount and billed bye vendor – receivable by company from tax authorities
iii. Tax payable: output tax (-) input tax
§ US Tax on S&P – Sales & Use tax
i. Both are different
ii. Both are apply to goods consumed by the customer
iii. Goods used in production / for resale to 3rd party remain untaxed
iv. Taxable good is sold either sales or use tax is levied – so goods taxed only once
v. Sales tax is collected by a vendor on a sale and remitted to the jurisdiction of the customer
vi. If customer are exempt – can specify in master record by entering appropriate indicator (Sales Area – Billing tab)
vii. Sales tax based on – Material & Customer location - posts in SO mgt & Purchasing mgt.
viii. Customer only has to pay use tax – if he was not charged sales tax by the vendor
ix. This may be the case if the vendor does not have a “presence” in the state of the customer or if the customer has a “self-assessment permit”
x. Customer determines the use tax amount and remits it to the jurisdiction where the goods are consumed
§ Tax Calculation Procedure:
i. Assigned to every country
ii. Contains:
1. order of steps:
2. tax types (condition types): that apply for the country – necessary for tax calculation
3. account key / transaction key: for additional specifications & automatic account determination
iii. TAXUSJ: including use of jurisdiction codes - TAXUSX: when employing an external tax package
iv. Condition types are tax calculations that are valid for the country
v. Base amount is the rev / exp item.
§ Jurisdiction Code:
i. Combination of the codes of tax authorities that tax movements of goods and use their own tax rates
ii. 4 possible levels below national level: State – Country – City or sub-city
iii. Using involves 2 steps:
1. have to define length of the individual element of the code for the format of the jurisdiction code
2. code must define on every level
iv. STATE - COUNTRY CODE - CITY CODE - DISTRICT CODE
v. When you post taxes with JC, you can enter taxes per J level / per tax level
§ Tax Code:
i. You can enter tax code when you post the document – this is the main connection – this depends on country uses as tax calculation procedure with tax jurisdiction codes or not
ii. Linked with either of the following:
1. Country key
2. Combination of country key and tax jurisdiction code
3. Tax codes within a jurisdictional taxation method are date-specific – you can choose whether the document date or posting date is valid for the tax calculation.
iii. Contains the tax rates.
iv. Tax rates assigned to tax types used in the procedure
v. A tax code may have several tax rates entered for different tax types (if line item is to be taxed with several tax types), but usually only one tax is entered.
vi. Zero tax :
1. exempt but have to reported to tax authorities – for this separate tax code is created
2. goods issue, goods movement, and so on – special tax code must be assigned to these transactions
vii. Tax type determines if the base amount is “percentage included” or “percentage separate”
viii. Check indicator: To detect the deviation between the tax calculated and the tax amount entered – either issue an error message (indicator set) or a warning message (indicator not set) - not for input tax codes because user must post the tax amount from the invoice regardless of whether it is correct or not
§ Tax Postings:
i. Separate line item to a special tax account
ii. Taxes with certain transaction/event keys are distributed to the relevant expense/revenue item (this is the case for sales tax payables or other non-deductible input taxes)
iii. For each transaction event key ( Posting key, Rules & Tax accounts)
iv. Exchange rate differences occur because of tax adjustments in foreign currencies – these are posted to normal account for ex rate differences
v. For each company code you can specify that the exchange rate for tax items can also be entered manually or is determined by the posting or the document date – the resulting differences posted to a special account
§ Tax Accounts:
i. Tax code properties determines whether or not the tax posted is I/O tax.
ii. Accounts to which tax items are posted define by entering the “Tax category” in GL:
1. “ “ - non tax-relevant postings (e.g., bank postings)
2. “-“ - postings that require an input tax code
3. “+” - postings that required an output tax code
4. “*” - postings which require any tax code
5. “xx” - predefined tax code
iii. “Post automatically only” must be selected if you don’t want to post tax manually
iv. “Posting without tax allowed”
1. can post to this GL without specifying tax code
2. necessary for tax postings within a jurisdiction code tax calculation procedure to foreign customers who do not have a jurisdiction code
v. Accounts for cash discounts need an entry in “Tax category” field if the system is supposed to post tax adjustments
§ READ 303 PAGE FOR EU RELATED TAX STUFF
SAP FI:Terms of Payment and Cash Discounts:
ii. TOP – assigned to – C/V - proposed by the system / enter by user – used in processing transaction.
iii. Base line date (posting , entry, document date, no default)
iv. Cash discount terms, Cash discount % - %, no. of days, fixed date, additional months,
v. Fixed day, additional months
Cash Discount:
i. To calculate, you enter % rate in TOP
ii. Also enter no. of days that the % is valid
iii. Also add fixed days and months
iv. Days & months are used in conjunction with the baseline date to calculate correct cash disc.
v. You can enter up to 3 cash discount periods
vi. Base amount – is net value (total of G/L and FA line items, taxes not included / gross value (including taxes)
vii. Global parameters of a company code
TOP in Credit Memos:
i. Invoice related credit memos: you can link credit memo to original invoice enter original invoice number in “Invoice Reference” field during document entry – in this case both documents become due on the same date
ii. Other Credit memos: TOP are invalid – due on base line date – enter “V” in “Invoice Reference” field.
Day limit:
i. Date specific TOP in one TOP key.
ii. calendar day to which the TOP are valid
iii. you can store single or multi-part TOP in one TOP key
iv. Several versions can define with each version having a different day limit.
v. Is the baseline date up to which payment term version applies.
Description: automatic – can replace – SO mgt text for printing
Account type
Payment Control: Block key & Payment method - default on first time if not set the indicator / default on change on setting the indicator.
Fixed day : used to overwrite the calendar day of the baseline date Installment:
i. Portion of invoice amount may be retained for payment at a later date
ii. Total invoice amount is divided into partial amounts due on different dates
iii. System carries out this split automatically if installment payment is defined in the TOP – create a line item for each installment specified
iv. Define an installment number, a percentage rate (total must be 100%), and terms of payment for each installment
v. Line item amounts correspond to the % of the total amount – total of all line item = total amount of document Posting the Cash Discount – Gross Procedure:
i. Enter either manually or automatically by the system
ii. You can still change the cash discount after you post the invoice
iii. When you clear C/V – cash discount automatically post to the “cash disc expense/received” Posting the Cash Discount - Net Procedure:
i. Cash discount amount is automatically posted when the invoice is posted. (this amount reduce from exp or B/S account )
ii. System carries out a clearing posting to the cash discount clearing account
iii. If invoice paid after cash disc deadline, cash discount loss is posted to a separate account
iv. Cash discount clearing account must be managed on an open item basis.
SAP FI: Document Reversal
> Entering a standard reversal posting – increases the transaction figures.
> Negative Posting – no increase in the transaction figures
i. Company code must permit negative postings
ii. Reversal reason must be defined for negative reversal.
> Negative – also used to perform transfer posting of incorrect line items
> Document type also should allow for negative
2. Reversal reason: have to enter – controls the reversal date (whether it is differentiated from posting period)Cleared documents must reset before reversing
SAP FI: Document Change Control
2. Doc Header – Reference & Doc Header text
3. Doc Line Item – not allow (amount, posting key, account or any other field which affect the reconciliation of a posting)
4. Log: field, new & old, who made, time & date
5. Condition for Field Change:
> Posting period not closed
> line item not cleared
> posting as DR in a Customer account / CR in Vendor account
> document must not be a credit memo for an invoice / from a down payment
6. Differentiate between the document change rules:
> Account type:
> Transaction class: only used for Sp. G/L CC: if the field is blank, rule applies to every CC
SAP: Default Values
1. Parameter ID allow users to set default values for fields whose values does not change very often (CC, Currency)
2. Using the “editing options”
> Document entry
> Document display
> Open items
> Line items
> Cr.mgt
> Cash journal
> Pmt adv
3. System proposes the CC based on the previous entry in the document At company code level, enter the max differences permitted between the exchange rate in the doc header
SAP: Document Control
2. Every document identified uniquely by following fields:
> Document Number
> Company Code
> Fiscal Year
3. Doc Header & Doc Line item (2 – 999)
4. Two important control keys:
> Document type for header
> Posting key for line item
5. A business transaction can create one or more documents (one is in MM and another is in FI)
6. Some business transaction creates the document but no effect for accounting (PO)Documents that are connected to each other are linked in the system
SAP: Posting Key
2. Controls:
> type of account to be posted
> Dr/Cr
> field status of the additional details
> whether it is connected to a payment transaction or not
> sales-relevant
3. In Enjoy transaction Posting key labeled as Dr and Cr
4. For asset and materials may only be used if the corresponding SAP components are installed
SAP: Document Number Range
2. External: alphanumeric – user enters the original document number / number is transferred automatically from a pre-invoicing system – no current number status
3. Must be defined for the year in which it is used
> To a fiscal year in the future - not restarts at the first number
> For each fiscal year - at the beginning of each FY starts again
4. One number range can be assigned to several document types You can copy the intervals from (one CC to another) & (one FY to another)
SAP: Bank Accounts
1. Bank master records stored centrally in bank directory.
2. BNKA table
3. Every record is identified by the bank country and the bank key.
4. Includes the address data (SWIFT code, postal giro data, and bank group – for payment optimization).
5. Banks used by your company are ‘House Bank’.
6. House Bank – for electronic payment, bank accounts, G/L accounts per bank account.
7. Bank master data - 4 ways can create:
- In C/V master record / House Bank
- Create Bank transactions in AR/P master data menu
- Bank Directory can be imported from disk/tape using – RFBVALL_0 – Country specific transfer of bank data.
- Customers that use the lockbox – can create using batch input session that automatically update customer banking information in the master record.
8. Partner Bank type – to differentiate between two different banks.
9. Each bank account is reflected in SAP by a combination of HB and Account ID.
10. Bank account data contains the number of the account at your bank, the account currency, and the relevant G/L accountFor every bank account, a G/L account must be created. This G/L account is assigned to the bank account and vice versa. Both accounts have to have the same account currency.
SAP: Alternative Payer / Payee
1. At the client and company code level you can enter an Alternative payee / payer
2. Entry in CC level as higher priority
3. Individual specifications indicator when creating an invoice, you can enter information about an individual payer/payee for a C/V that has not been created
4. if an alt payer/payee is an existing C/V, you can enter the C/V account number as permitted payee/payer in the master record
5. When you enter an invoice, you can choose one of these payers/payees using matchcodes.
6. If you enter an alternative payer, the amount to clear the due open items in the account is paid by the alternative payer.
7. If you enter an alt payee, the amount that the company has to pay to clear the open items due is paid to the alt payeeIf you set the ‘payment data’ indicator in the ‘additional selections’ area in the report for the C/V list – you can see the alternative payer for the respective customer or alternative payee for the vendor when you print the report
SAP : Account Group (GL, Customer, Vendor)
- Controls the – number range of the accounts.
- Controls thewhether account is one time or not
- Controls the status of the field.
- Once C/V (Customer / Vendor) account has been created, you can no longer change the account group. But you can change the account group of the C/V.
- If you use partner roles in SD in some cases you can change the account group from an ordering address to a ship-to address.
- Separate number ranges for C&V accounts.
- Number range must not overlap.
- If you want to know how many numbers are still available in a specific number range, you can display the current number.
- Current number can’t be displayed with external number assignment.
- Each number range can be assigned to one/more account groups.
- One time account master records does not contain any information about a specific C/V, since the account is used more than once.
- C/V specific field should be therefore be hidden.
- C/V specific data have to enter for one-time C/V in document when posting.
- Layout of C/V master data screens can be effected bye several factors:
> Account group-dependent control
> Transaction-dependent control
> Company code dependent control - All of the above used and the field status with the highest priority is used.
- ‘Display’ status field can be either ‘suppress’/’display’.
- If you don’t want 2 & 3 , you can put the status in ‘optional’ for all fields