Truebell - Fin - Ap - Config - Account Payable

Configuration Document
Financial Accounting and Controlling

ACCOUNT PAYABLE
TRUEBELL MARKETING & DISTRIBUTION SERVICES PVT LTD
SAP S/4 HANA 1610 IMPLEMENTATION PROJECT
FINANCIAL ACCOUNTING AND CONTROLLING
CONFIGURATION DOCUMENT
ACCOUNT PAYABLE
Prepared by
SEAL INFOTECH PVT LTD
Truebell Marketing & Distribution Pvt Ltd _ Configuration Document _ FICO_ACCOUNT PAYABLE Page 1
ACCOUNT PAYABLE
CONTENTS Page Numbers

1. Account Payable Introduction--------------------------------------------------------------------------------------------------------------- 4
1.1. Define Account Groups with Screen Layout (Vendors)----------------------------------------------------------------------------4
1.2. Create Number Ranges for Vendor Accounts---------------------------------------------------------------------------------------- 5
1.3. Assign Number Ranges to Vendor Account Groups--------------------------------------------------------------------------------5
2. Business Partner Introduction-------------------------------------------------------------------------------------------------------------- 6
2.1 Define BP Roles------------------------------------------------------------------------------------------------------------------------------ 7
2.2 Define Number Ranges for Business Partner---------------------------------------------------------------------------------------- 7
2.3 Define Groupings and Assign Number Ranges--------------------------------------------------------------------------------------8
2.4 Define Number Assignment for Direction BP to Vendor--------------------------------------------------------------------------9
3. Define Tolerances for Customers/Vendors-------------------------------------------------------------------------------------------- 10
4. Define Accounts for Cash Discount Taken---------------------------------------------------------------------------------------------- 11
5. Define Alternative Reconciliation Account for Down Payments------------------------------------------------------------------12
6. Define Document Type for Vendors----------------------------------------------------------------------------------------------------- 14
7. Define Posting Keys-------------------------------------------------------------------------------------------------------------------------- 14
8. Define Account for Tax Clearing---------------------------------------------------------------------------------------------------------- 15
9. Define Payment Terms---------------------------------------------------------------------------------------------------------------------- 17
10. Define Payment Block Reasons-------------------------------------------------------------------------------------------------------- 33
11. AUTOMATIC PAYMENT PROGRAM (APP)------------------------------------------------------------------------------------------- 34
11.1 Set Up All Company Codes for Payment Transactions---------------------------------------------------------------------------34
11.2 Set Up Paying Company Codes for Payment Transactions----------------------------------------------------------------------35
ACCOUNT PAYABLE
11.3 Set Up Payment Methods per Country for Payment Transactions-----------------------------------------------------------38
11.4 Set Up Payment Methods per Company Code for Payment Transactions--------------------------------------------------42
11.5 Set Up Bank Determination for Payment Transactions--------------------------------------------------------------------------45
ACCOUNT PAYABLE
1. Account Payable Introduction
The Accounts Payable application component records and manages accounting data for all vendors. It is
also an integral part of the purchasing system:
Deliveries and invoices are managed according to vendors. The system automatically triggers postings in
response to the operative transactions. Payables are paid with the payment program. The payment
program supports all standard payment methods (such as checks and transfers) in printed form as well as in
electronic form (data medium exchange on disk and electronic data interchange). Postings made in
Accounts Payable are simultaneously recorded in the General Ledger where different G/L accounts are
updated based on the transaction involved (payables and down payments, for example). The system
contains due date forecasts and other standard reports that you can use to help you monitor open items.
1.1.Define Account Groups with Screen Layout (Vendors)
We determine the account groups for vendors. When creating a vendor account, an account group must be
specified.
IMG Financial Accounting (New)Accounts Receivable and Accounts

Menu Path PayableVendor AccountsMaster Data Preparations for Creating Vendor
Master DataDefine Account Groups with Screen Layout (Vendors)
Transaction Code OBD3
ACCOUNT PAYABLE
1.2.Create Number Ranges for Vendor Accounts
We create the number ranges for vendor accounts. We specify the following under a two-character key:
 A number interval from which the account number for the vendor accounts is to be selected.
 The type of number assignment (internal or external number assignment)
Assign this number ranges to the account groups for vendors.
IMG  Financial Accounting (New) Accounts Receivable and Accounts

Menu Path PayableVendor Accounts Master Data Preparations for Creating Vendor
Master DataCreate Number Ranges for Vendor Accounts
Transaction Code XKN1
ACCOUNT PAYABLE
1.3.Assign Number Ranges to Vendor Account Groups
We have created number ranges and account groups to vendors. We have assigned vendor account group to
number range

Menu Path PayableVendor Accounts Master Data Preparations for Creating Vendor
Master DataAssign Number Ranges to Vendor Account Groups
Transaction Code OBAS
ACCOUNT PAYABLE
2. Business Partner Introduction

A person, organization, group of persons, or group of organizations in which a company has a business
interest.

We use this business object for a variety of business transactions. We create and manage centrally
business partners (BPs) and the roles they assume for your company. For this purpose, you define the
general data of the business partner once and we assign business partner roles (BP roles) to the
business partner. Specific data is stored for each business partner role.
When you first create a business partner in the system, the BP role General Business Partner is
automatically assigned to the business partner.
Structure
We identify each BP with a unique business partner number (BP number).
We create and manage the following general elements of a BP:
 General data, such as name, address, and communication data
 Identification data, such as industry, identification numbers, and tax numbers
 Status data, such as the status of the business relationship
We create and manage the specific data for a BP role once you have assigned a specific role to the BP.
Integration
In an integrated system landscape with SAP Enterprise Resource Planning (SAP ERP) and SAP
Transportation Management (SAP TM), the ERP system is frequently the leading master data system. In
this case, the customer and Vendor master data is maintained in the ERP system from where it is
transferred to SAP TM using the SAP Core Interface (CIF) as locations and business partners.
ACCOUNT PAYABLE
2.1 Define BP Roles

We define the business partner roles and their attributes. We also define the role categories with other
relevant data.
We define Business Partner for Vendor & Customer Master data
IMGCross-Application Components SAP Business Partner Business Partner

Menu Path
Basic SettingsBusiness Partner RolesDefine BP Roles
Transaction Code SPRO
2.2 Define Number Ranges for Business Partner

We define number ranges for business partners. The defined number ranges are assigned to groupings in
the Define groupings and assign number ranges activity. Number ranges for business partners are valid
throughout a client.

Menu Path
Basic SettingsNumber Ranges and Groupings Define Number Ranges
Transaction Code BUCF
ACCOUNT PAYABLE
2.3 Define Groupings and Assign Number Ranges

We maintain groupings for business partners. The number ranges for business partners are defined.

Menu Path
Basic SettingsNumber Ranges and Groupings Define Number Ranges
ACCOUNT PAYABLE
2.4 Define Number Assignment for Direction BP to Vendor

We assign account groups for the vendor master records to the business partner groupings to ensure that the
system updates the vendor at the same time as we process business partners as part of vendor integration.
When you make this assignment, we choose whether the vendor master record is created with an account
with internal or external number assignment or with identical numbers.
IMGCross-Application Components Master Data Synchronization

Customer/Vendor Integration Settings for Vendor Integration Field
Menu Path
Assignment for Vendor Integration  Assign Keys Define Number Assignment
for Direction BP to Vendor
ACCOUNT PAYABLE
3. Define Tolerances for Customers/Vendors
The Customer / Vendor tolerances are used for dealing with payment differences and residual items that
may arise when payment clearing is carried out. The tolerances in one or more tolerance groups are assign
a tolerance group to each customer/vendor using the master record. Tolerances, up to which payment
differences arising from open item clearing can be automatically, posted to expense or revenue accounts
IMG  Financial Accounting (New) Accounts Receivable and Accounts Payable 

Menu Path Business TransactionsOpen Item ClearingClearing DifferencesDefine
Tolerances for Customers/Vendors
Transaction Code OBA3
ACCOUNT PAYABLE
4. Define Accounts for Cash Discount Taken
We define the account number of your cash discount received accounts. The system posts the cash
discount amount to these accounts when clearing open items.

Menu Path PayableBusiness TransactionsOutgoing PaymentsOutgoing Payments
Global SettingsDefine Accounts for Cash Discount Taken
Transaction Code OBXU
ACCOUNT PAYABLE
5. Define Alternative Reconciliation Account for Down Payments
We define an account in which the vendor down payments are managed in the general ledger. The down
payment posting is then automatically made to this account instead of to the normal payables account
(reconciliation account).

Menu Path Business TransactionsDown Payment MadeDefine Alternative Reconciliation
Account for Down Payments
Transaction Code OBYR
ACCOUNT PAYABLE
ACCOUNT PAYABLE
6. Define Document Type for Vendors
We create document types for customer, vendor and general ledger business transactions in Financial
Accounting. Document types differentiate business transactions and control document filing. We specify a
number range for each document type. Document numbers are chosen from this number range.

Menu Path Business TransactionsDown Payment MadeIncoming Invoices/Credit Memos
Make and Check Document Settings Define Document Types
Transaction Code OBA7
7. Define Posting Keys
We define posting keys. Users specify a posting key before entering a line item. The posting key controls
how the line item is entered and processed. For each posting key, we define among other things:
 which side of an account can be posted to,
 which type of account can be posted to, and
 These fields the system displays on the entry screens and whether an entry must be made (field
status).

Make and Check Document Settings Define Posting Keys
Transaction Code OB41
ACCOUNT PAYABLE
8. Define Account for Tax Clearing
We define an input tax clearing account. This account is needed if you display down payments gross in the
vendor account.

Make and Check Document Settings Define Posting Keys
Transaction Code OBXD
ACCOUNT PAYABLE
ACCOUNT PAYABLE
9. Define Payment Terms
We define rules with which the system can determine the required terms of payment automatically. The
rules are stored under a four-character key. We assign the terms of payment specified to the vendors in the
master record via the key. The key and the terms determined with it are proposed when entering a
document to the vendor account. We can use the same key for the terms of payment for both customers
and vendors who have the same payment terms. However, we use different terms of payment keys for
customers and vendors and limit the permitted account type correspondingly within the terms of payment.

Menu Path Business TransactionsIncoming Invoices/Credit MemosMaintain Terms of
Payment
Transaction Code OBB8
Pay. Day Sales text / Account Default for No. of Fixed Add.
term limi Own type Baseline days date Mths
s t explanation Date
Z030 0 Net due in Custome 30 31

30 days r
Vendor
ACCOUNT PAYABLE
Pay. Day Sales text / Own Account Default No. Fixed Add.
term limit explanation type for of date Mths
s Baseline day
Date s
Z045 0 Net due in 45 Customer 45 31

days
Vendor
ACCOUNT PAYABLE
Pay. Day Sales text / Account Default No. Fixed Add.

term limi Own type for of date Mths
s t explanation Baseline day
Date s
Z060 0 Net due in Customer 60 31

60 days
Vendor
ACCOUNT PAYABLE

Date s

75 days
Vendor
ACCOUNT PAYABLE

Date s

90 days
Vendor
ACCOUNT PAYABLE

Date s
ZLCS 0 LC payment Customer 0 0

at sight
Vendor
ACCOUNT PAYABLE

term limit Own type for of date Mths
s explanation Baseline day
Date s
ZCOD 0 Cash/Chequ Customer Document

e on Date
Delivery Vendor
ACCOUNT PAYABLE

Date s
ZCAD Cash Customer No 15

against Default
Documents Vendor
ACCOUNT PAYABLE

Date s
ZD/P Documents Customer No

against Default
Payment Vendor
ACCOUNT PAYABLE

Date s
ZD/A Documents Customer No

against Default
Acceptance Vendor
ACCOUNT PAYABLE
Pay. Day Sales text / Account Default No. Fixe Add.

term limi Own type for of d Mths
s t explanation Baseline day date
Date s
ZADV Advance Custome Document

Payment r Date
Vendor
ACCOUNT PAYABLE

Date s
ZL30 LC 30 days Customer 30

from BL
date Vendor
ACCOUNT PAYABLE

Date s
ZL45 LC 45 days Customer No 45

from BL Default
date Vendor
ACCOUNT PAYABLE

Date s

from BL Default
date Vendor
ACCOUNT PAYABLE

Date s

from BL Default
date Vendor
ACCOUNT PAYABLE

Date s

from BL Default
Vendor
ACCOUNT PAYABLE
date
10. Define Payment Block Reasons
Using payment blocking reasons, we can differentiate why invoices are to be blocked for payment. For each
block indicator, you must decide whether to Changes are allowed in the payment proposal. If the indicator is
ACCOUNT PAYABLE
not set, the reason for blocking cannot be set nor removed when a payment proposal is processed.
Documents defined with the block key are also not to be cleared during manual payment entry.

Menu Path Business TransactionsOutgoing PaymentsOutgoing Payments Global Settings
Payment Block ReasonsDefine Payment Block Reasons
Transaction Code OB27
11. AUTOMATIC PAYMENT PROGRAM (APP)
11.1 Set Up All Company Codes for Payment Transactions
We make specifications for all company codes involved in payment transactions. For each company code,
you make the following specifications:
ACCOUNT PAYABLE
Paying company code: We assign a paying company code to each company code. This means that you can
have one company code process payment transactions centrally for several company codes

Business TransactionsOutgoing PaymentsAutomatic Outgoing Payments
Menu Path
Payment Method/Bank Selection for Payment Program Set Up All Company
Codes for Payment Transactions
Transaction Code FBZP
ACCOUNT PAYABLE
11.2 Set Up Paying Company Codes for Payment Transactions
We make the following specifications for the paying company codes:
 Data for controlling the payment program - We specify the minimum amount for which an
incoming or outgoing payment is created
 Forms and sender details for advice notes - We wish to print payment advice notes specify the
form name. Specify also the SAP script text modules that contain details about the sender that are
to be printed on the payment advice note.
ACCOUNT PAYABLE

Payable Business TransactionsOutgoing PaymentsAutomatic Outgoing
Menu Path
Payments Payment Method/Bank Selection for Payment Program Set Up
Paying Company Codes for Payment Transactions
Transaction
FBZP
Code
ACCOUNT PAYABLE
ACCOUNT PAYABLE
11.3 Set Up Payment Methods per Country for Payment Transactions
We specify which payment methods are to be used in each country. We enter the following details for the
payment method:
Country-Specific Specifications for the Payment Method:
 Payment method either for incoming or outgoing payments

 Characteristics for classifying payment method - We specify the type of payment method such as
check, RTGS or bank transfer and any other features of that payment method.
 Required entries in master record - We determine which specifications in the master record control
whether the payment method is used (such as bank details or collection authorization).
 Posting specifications - We specify how the payment is to be posted.
 Which procedure is to be used to issue the accompanying payment form

Menu Path Payment Method/Bank Selection for Payment Program Set Up Payment
Methods per Country for Payment Transactions
ACCOUNT PAYABLE
ACCOUNT PAYABLE
ACCOUNT PAYABLE
ACCOUNT PAYABLE
11.4 Set Up Payment Methods per Company Code for Payment Transactions
We specify which payment methods can be used per company code and determine the conditions under
which a payment method should be used. Amount limits for payments within which the payment program
can select the payment method

Menu Path Payment Method/Bank Selection for Payment Program Set Up Payment
Methods per Company Code for Payment Transactions
ACCOUNT PAYABLE
ACCOUNT PAYABLE
ACCOUNT PAYABLE
11.5 Set Up Bank Determination for Payment Transactions
We make settings that the payment program uses to select the banks or bank accounts from which payment
is to be made.
 Ranking order of banks: which house banks are permitted and rank them in a list.
 Bank accounts: For each house bank and payment method (and currency, if required), we specify
which bank account is to be used for payments.
 Available amounts: For each account at a house bank, we enter the amounts that are available for
the payment run. We enter separate amounts for incoming and outgoing payments. Specifying
available amounts enables you to control which bank account is to be used for payments. We can
specify the amounts depending on the value date at the bank.
 Value date: How many days elapse between the posting date of the payment run and the value date
at the bank, dependent on the payment method, bank account, payment amount, and currency We
can have the system determine the value date, taking into account the bank calendar and any
individual arrangements made with the bank.

Menu Path
Payment Method/Bank Selection for Payment Program Set Up Payment
Methods per Company Code for Payment Transactions
ACCOUNT PAYABLE
Ranking Order
Bank Accounts
ACCOUNT PAYABLE
Available Amounts
Value Date

Truebell - Fin - Ap - Config - Account Payable

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Truebell - Fin - Ap - Config - Account Payable

Uploaded by

Copyright:

Available Formats

Configuration Document

Financial Accounting and Controlling

TRUEBELL MARKETING & DISTRIBUTION SERVICES PVT LTD

SAP S/4 HANA 1610 IMPLEMENTATION PROJECT

FINANCIAL ACCOUNTING AND CONTROLLING

SEAL INFOTECH PVT LTD

CONTENTS Page Numbers

1.1. Define Account Groups with Screen Layout (Vendors)----------------------------------------------------------------------------4

1.2. Create Number Ranges for Vendor Accounts---------------------------------------------------------------------------------------- 5

1.3. Assign Number Ranges to Vendor Account Groups--------------------------------------------------------------------------------5

2. Business Partner Introduction-------------------------------------------------------------------------------------------------------------- 6

2.1 Define BP Roles------------------------------------------------------------------------------------------------------------------------------ 7

2.2 Define Number Ranges for Business Partner---------------------------------------------------------------------------------------- 7

2.3 Define Groupings and Assign Number Ranges--------------------------------------------------------------------------------------8

2.4 Define Number Assignment for Direction BP to Vendor--------------------------------------------------------------------------9

3. Define Tolerances for Customers/Vendors-------------------------------------------------------------------------------------------- 10

4. Define Accounts for Cash Discount Taken---------------------------------------------------------------------------------------------- 11

5. Define Alternative Reconciliation Account for Down Payments------------------------------------------------------------------12

6. Define Document Type for Vendors----------------------------------------------------------------------------------------------------- 14

7. Define Posting Keys-------------------------------------------------------------------------------------------------------------------------- 14

8. Define Account for Tax Clearing---------------------------------------------------------------------------------------------------------- 15

9. Define Payment Terms---------------------------------------------------------------------------------------------------------------------- 17

10. Define Payment Block Reasons-------------------------------------------------------------------------------------------------------- 33

11. AUTOMATIC PAYMENT PROGRAM (APP)------------------------------------------------------------------------------------------- 34

11.1 Set Up All Company Codes for Payment Transactions---------------------------------------------------------------------------34

11.2 Set Up Paying Company Codes for Payment Transactions----------------------------------------------------------------------35

11.3 Set Up Payment Methods per Country for Payment Transactions-----------------------------------------------------------38

11.5 Set Up Bank Determination for Payment Transactions--------------------------------------------------------------------------45

1. Account Payable Introduction

1.1.Define Account Groups with Screen Layout (Vendors)

IMG Financial Accounting (New)Accounts Receivable and Accounts

1.2.Create Number Ranges for Vendor Accounts

Assign this number ranges to the account groups for vendors.

IMG  Financial Accounting (New) Accounts Receivable and Accounts

1.3.Assign Number Ranges to Vendor Account Groups

IMG  Financial Accounting (New) Accounts Receivable and Accounts

2. Business Partner Introduction

2.1 Define BP Roles

We define Business Partner for Vendor & Customer Master data

IMGCross-Application Components SAP Business Partner Business Partner

2.2 Define Number Ranges for Business Partner

IMGCross-Application Components SAP Business Partner Business Partner

2.3 Define Groupings and Assign Number Ranges

IMGCross-Application Components SAP Business Partner Business Partner

2.4 Define Number Assignment for Direction BP to Vendor

IMGCross-Application Components Master Data Synchronization

3. Define Tolerances for Customers/Vendors

IMG  Financial Accounting (New) Accounts Receivable and Accounts Payable 

4. Define Accounts for Cash Discount Taken

IMG  Financial Accounting (New) Accounts Receivable and Accounts

5. Define Alternative Reconciliation Account for Down Payments

IMG  Financial Accounting (New) Accounts Receivable and Accounts Payable 

6. Define Document Type for Vendors

IMG  Financial Accounting (New) Accounts Receivable and Accounts Payable 

7. Define Posting Keys

 which side of an account can be posted to,

 which type of account can be posted to, and

IMG  Financial Accounting (New) Accounts Receivable and Accounts Payable 

8. Define Account for Tax Clearing

IMG  Financial Accounting (New) Accounts Receivable and Accounts Payable 

9. Define Payment Terms

IMG  Financial Accounting (New) Accounts Receivable and Accounts Payable 