Knowledge Sharing Session-1

Currency:

 A system of money in general use in a particular country called currency

 Types of currencies
 Functional currency/Accounted currency/ Primary currency (Local currency)
 Entered currency / Foreign currency (Foreign currency)
 Reporting currency (Head quarter currency)
 These three currencies called monitory currencies and (Ratios, meters and feet) called non
monitory currencies.

Calendar:

 A chart of series of pages showing the days, weeks and months of particular year called
calendar
 Types of calendars
 Accounting calendar (Standard accrual concept)
 Calendar year (Jan-Dec)
 Fiscal year (Apr-Mar Depends on accounting methods)
 Transaction calendar
 It is used in the average balance concept to identify which day is the working day and which
day is holiday.

Chart of Accounts Structure:

The chart of accounts structure provides the general outline of the chart of accounts and determines
the number of segments, the type, the length, and the label (qualifier) of each segment. This forms
the foundation of the chart of accounts definition object.

For each chart of accounts structure, it is possible to associate one or more chart of accounts
structure instances. Chart of accounts structure instances for the same structure share a common
configuration with the same segments, in the same order, and the same characteristics. Using one
chart of accounts structure with multiple instances simplifies your accounting and reporting.

Ledger:

Ledger is a reporting entity. In which recording day to day transactions and it will determine the 4 c’s
in the organization. One business group contains multiple ledgers but one ledger must be associated
with only one business group.

Legal entity:

Legal entity is nothing but tax authority for generates tax report. One ledger entity contains multiple
legal entities but one legal entity must be associated with one ledger

Journals

It is used to record day to day business transaction of the organization. It contains debit and credit
lines. Always debit equals to credit, Journal contains two types of categories.

 Journal Header
 Journal Lines
Methods of journals

We have two methods

 Manual method – entering journals manually

 Automatic – System generated automatically

Manual method

 Single journal
 Batch journal

Multiple ways to enter journals

 Manual
 FBDI (File Based Data Import)
 ADFDI (Application desktop Framework Development Integration)
 Automatic Journals (Mass allocation and Revaluation)

Journal Source:

 It is a Journal component; it is used to identify the ORIGIN of the journal.

 When we import data from legacy systems to GL we require source names
 Importing journal Reference:
 To import detailed information from summary journals we use this option
 Require Journal approval:
 This field is used to get the journal approval by higher management for different journal
sources
 Import using key: This is used to define whether journals will be imported using source key
or not

Journal Category

 Journal Category determines the purpose or type of the journal entry

 When you enter a journal, you specify a journal category.

Reporting currencies/ ledger

Reporting Currency are the currency used for financial, legal & management reporting. If the
reporting currency is not same as that of ledger currency, we can use foreign currency translation
process or reporting currencies functionality to convert the ledger account balances in the reporting
currency. Reporting currency can be based on primary or secondary ledger. A reporting currency can
differ from its source ledger in its currency and some processing options, but shares the same chart
of accounts, accounting calendar, and accounting method with its related ledger.

Conversion Rules

We have three types of conversion rules

 Balance
 Journal
 Sub ledger
Just for getting more advice.

Enterprise structure (India)

 Enterprise.
 2. Division.
 Primary ledger (INR)
 4-Legal Entity: (Hyderabad LE, Mumbai LE, Pune LE)
 5- BU (Branch): Hyderabad LE has two Branches one for Selling and revenue, second for
Purchasing and project operations. Same for other LE too
 6- Inventory organization (Warehouse or distribution centre for inventory to resell, each BU
has two Inventory organization)

Knowledge Sharing Session- 2

Accounts payable is money owed by a business to its suppliers shown as a liability on a company's
balance sheet. It is distinct from notes payable liabilities, which are debts created by formal legal
instrument documents

 AP works at Business Level.

 AP Is the sub ledger application in Oracle ERP.
 To determine or calculate outstanding payables amounts means liabilities at organization
level
 Work Benches: We have 3 work benches in AP, and these three will control the AP.
 Supplier workbench
 Invoice workbench
 Payment workbench

Supplier Work Bench:

 Supplier data
 Supplier types
 Supplier Pay groups
 Supplier Payments methods
 Supplier bank accounts

Invoice Work Bench:

 Manual
 Standard invoice (Positive)
 Debit memo (Negative)
 Credit memo (Negative)
 Prepayment
 Automatic
 Interest invoice
 Payment request
 WHT (withholding tax)

Payment Work Bench:

  Single payment
 Batch payment (Payment process request (PPR))
 Refund to vendor

Roles to be assigned to user:

 Accounts Payable Manager

 Accounts Payable specialist
 Accounts Payable supervisor
 Accounts Payable invoice supervisor
 Accounts Payable Payment supervisor
 Supplier Manager (For creating supplier)

Setups Configurations:

 Manage common options for payables and procurement (BU Level)

 Manage payment Terms. (M)
 Manage distribution sets. (O)
 Manage invoice tolerance. (O)
 Manage documents sequence for payables. (O)
 Manage payment methods. (O)
 Manage payment formats. (O)
 Manage Banks. (M)
 Manage Bank branches. (M)
 Manage bank accounts. (M)
 Manage payable documents. (M)
 Manage payment process profile. (M)
 Manage Aging periods. (O)
 Manage invoice options. (M)
 Manage payment options. (M)
 Payable open periods (include GL also)

Matching Ways:

We have 3 ways of matching

 Two-way matching (INV with PO)

 Three-way matching (INV with PO and GRN)
 Four-way matching (INV with PO, GRN and DC (inspection)) - In this matching we have one
extra entry for inspection

Goods moved to sub inventory (On Completion of inspection and goods accepted)
Knowledge Sharing Session - 3
 Accounts Receivables - It is the one of the Sub Ledger applications is Oracle ERP. It works at
BU level
 In AR we have two KFF’s
o Sales Tax KFF
o Territory KFF

Roles:

 Accounts Receivables Manager

 Accounts Receivables Specialist
 Billing Manager
 Billing specialist
 Billing Accountant
 Revenue Analyst

Setups Configurations:

 Manage Receivables system options

 Manage Transaction Types
 Manage Transaction Source
 Manage Auto accounting rules
 Manage Receivables Payment Terms
 Manage statement cycles
 Collectors’ creation
 Manage Receivables customer Profile Class
 Reference data set for customer site
 Manage Business Unit set assignment
 Customer Creation and assign customer profile class at address and site level
 Create Remit- to- Addresses
 Create Memo Lines
 Create Receivable activities
 Create Receipt classes & Methods
 Create Receipt Source
 Manage Data access set to user
 Open Receivables period

Customer -

For customer creation we don’t need any additional roles. Customer nothing but debtor in our
books, customer consist of 4 stages

 Customer Name / Header

 Customer Addresses
 Customer contacts
 Customer Bank Accounts
  We can create customer in two ways
o Manual
o Spreadsheet
 Types of customers
o Organization
o Person

Account types in Receivables

o External account
o Internal account

Knowledge Sharing Session - 4

Asset Application works at ledger level.

We have 3 KFF's:

o Asset Category KFF- Major, minor

o Asset Location KFF country, state, city, building
o Asset KEY KFF.

It integrates with AP, GL and PPM.

 AP to Asset – Mass Addition

 Asset to GL – Journal entries, Asset Cost account, Asset clearing account.
 PPM to Asset – Asset entries.

Types of Books in FA

 Corporate: A book that you use to track financial information for your balance sheet.
 Tax Book: A book that you use to track financial information for your tax reporting
authorities.
 Budget: A book that use to track planned capital Expenditures.

Asset Types in FA

o Capitalize
o Expense
o CIP
o Group of Assets

Roles:

o Asset Accounting Manager

o Asset Administrator
o Asset Accountant

Oracle Fusion Assets Configuration:

 Create value sets for category KFF

 Create value sets for Location KFF
  Create value sets for Asset key KFF
 Create Category KKF structure
 Create location KFF structure
 Create Asset key KFF structure
 Create Category KKF structure Instance
 Create Location KFF structure Instance
 Create Asset key structure Instance
 Create segment values for 3 KFF segments
 Create system controls
 Create fiscal calendar
 Define Asset calendar/ Depreciation calendar
 Define prorate convention
 Define prorate calendar
 Create Asset book
 Create Asset categories

Assign FA roles to user

 Provide data access for user

 Run LDAP program

Knowledge Sharing Session - 5

Period/Month end process of Accounts Payable:

Ways of Closing Period

We have two ways of closing periods.

 Soft Close: No issues during month/period & moving to next period.

 Hard Close: We have issue and moving to next period. We can sweep issue to next period.

Report to be run

 Run “Validate Payable invoice” program

 To validate all open/outstanding invoices
 In real time client will run this report.
 This program can run daily or monthly

Check the result if you get any hold invoices then run another report

 Run “Payables matching holds report”

 This program runs at BU level
 To identify all hold and discrepancies
 Need to review output

We can have only count of invoices which are on hold

 Run “Payable unaccounted transactions report”

Identify invoices to be accounted, review and to be fixed for invoices and payments, user will fix. We
can suggest running this report daily, so that it will easy at the period end.
  Re Run “Validate Payable Invoice” program

There shouldn’t be any pending data

 Run “Create Accounting” Program

 Run “Mass Additions create” program – To transfer assets to FA
 Run “Payables Posted Payment Register” – (posted invoices in GL, Optional, but we should
suggest)
 Run “AP Trial Balance” Report
 Run “Period Close Exceptions Report (XML)” – if any exceptions run SR
 Run “Sub-Ledger Period Close Exceptions Report”.
 Reconciliation between AP GL

We will do reconciliation always for liability account only

Last Month TB outstanding + Present month Payable Posted Invoice Register – Present month
Payables Posted Payment Register = APTB outstanding >>> APTB o/s should be transferred to GL &
posted

Compare with GL TB of Liability Account.

Knowledge Sharing Session - 6

Enterprise Structure/Primary GL Setups Configurations:

 Manage Currencies.
 Manage Calendars.
 Manage Value sets.
 Manage Structures.
 Manage Structures Instances.
 Deploy Flex field.
 Manage Legal address.
 Manage legal entity.
 Manage legal Reporting unit.
 Manage Legal entity registration.
 Manage Primary ledger.
 Manage Specify ledger options.
 Assign Balancing Segment values to legal entity.
 Assign legal entity to ledger.
 Assign ledger to data access set.
 Open periods.
 Review and submit accounting configuration.
 Create Reference set.
 Manage Locations.
 Manage Business units.
 Assign business unit business function.
 Manage business unit set assignments.
 Manage Business unit data access for users.

HCM Setups Configurations:

  Manage Locations
 Manage Enterprise.
 Manage Divisions. (Optional)
 Manage Legal address.
 Manage Legal entity
 Manage Legal entity registration.
 Manage legal entity to ledger
 Manage Reference Data
 Manage Location for Business unit.
 Manage business unit.
 Manage Territories.
 Manage legal jurisdiction. (Optional)

GL Setups Configurations:

 Create COA
 Create COA structure.
 Create Manage Structure instance.
 Manage accounting calendar.
 Manage Currencies. (Already enabled)
 Manage Primary ledger.
 Manage Specify ledger options.
 Run the review submits accounting programmed.
 Assign Balancing Segment values to legal entity.
 Assign business unit business function.
 Assign Data access set to data access users
 Manage business unit set assignment.
 Manage Cost Organization.
 Manage Payment terms.
 Manage common options for payable and procurement.
 Manage invoice options.
 Manage payment options.
 Manage Receiving Parameters.

Inventory setups Configurations:

 Manage location for factory.

 Manage inventory organization.
 Create master org
 Create child org
 Manage Sub inventory & Locations.
 Manage cost Organization data access for users.
 Manage Cost books.
 Manage functional area catalog.
 Manage item category.
 Manage Item classes.
 Manage items.
 Manage Cost Organization relationship.

Purchasing Setup Configurations:

  Manage purchasing line type.
 Manage unit of measures.
 Manage carrier lookups.
 Manage Free on-Board lookups.
 Manage Freight term lookups.
 Manage purchasing document approval.
 Configure procurement Business function.
 Configure Requisitioning business function.
 Manage procurement document number.
 Manage legislative data group.
 Assign legislative group to legal entity.

Knowledge Sharing Session - 7

Revenue Recognition:

It is a generally accepted accounting principle (GAAP) that determines the specific conditions in
which revenue is recognized or accounted for. Generally, revenue is recognized only when a critical
event has occurred, and the amount of revenue is measurable.

In Revenue Recognition we have two concepts in oracle apps.

 Invoicing Rule.
 Accounting Rule.

Invoicing Rule:

Invoice rules will be determined the accounting period in which receivables are recognized.

There are 2 types of Invoice Rules:

 Bills in advance
 Bills in Arrears

Bills in advance: System will recognize the invoice amount as a advance or starting of a project. In
case of Bill in advance Unearned Revenue will come into the picture.

If you enter an invoice with a Bill in Advance invoicing rule, Receivables creates the following journal
entries.

In first Period:

Receivables A/c.....Dr

 To Unearned Revenue A/c......Cr

 To Tax A/c ...........................Cr
 To Freight A/c.......................Cr

In all periods of the rule for the portion that is recognized:

 Unearned Revenue A/c ......Dr

 To Revenue...........Cr
Bills in Arrears: System will recognize amount at the end of the contract or project. In case of Bills in
Arrears " Unbilled Receivable" will come into the picture. If you enter an invoice with a Bill in Arrears
invoicing rule, Receivables creates the following journal entry:

In first Period, Second period till the last period the following entry will be generated.

 Unbilled Receivable A/c.......DR

 To Revenue ..............CR

At the completion of Project and at the last Period the following entry will be generated by system.

o Receivables A/c..............DR
 To Unbilled Receivables A/c.............CR
 To Tax.........................................CR
 To Freight...................................CR

Accounting Rules:

Accounting Rules will determine the Accounting Period in which Revenues are recognized.

There are 2 types of accounting rules:

 Fixed Schedule
 Variable Schedule

Fixed Schedule:

We will define duration of the project and % of Revenue of each accounting period, at the time of
fixed scheduled accounting rule setup.

Variable Schedule:

At the time of set up the Variable Schedule Rule we will not enter duration of the project & % of
Revenue for each accounting period.

We enter only first period Revenue % at the time of accounting rule set up. Duration of the project
will be entered at the time of invoice entry.

Configure Auto accounting for Revenue Recognition (Unbilled revenues and Unbilled receivables)

Create Revenue Schedules (Accounting Rule)

Create Transaction including invoicing rule, revenue schedules

Run “Revenue Recognition”

Knowledge sharing about Inter company.
 Intercompany Transactions in Oracle Fusion Financials--- A Comprehensive Overview
 Intercompany transactions are financial transactions between different legal entities within
the same corporate group.
 These transactions often involve the exchange of goods, services, or funds.
 In Intercompany module is designed to streamline and automate these transactions,
ensuring accurate accounting and reporting.

Key Concepts:

 Provider Legal Entity: The entity that provides goods or services.

 Receiver Legal Entity: The entity that receives goods or services.
 Intercompany Balancing Rules: These rules define how intercompany transactions are
accounted for, including the appropriate accounts to be used for receivables, payables, and
the offsetting entries.
 Intercompany Transactions: These are the specific transactions entered into the system, such
as sales, purchases, or transfers of funds.

Scenarios and Explanations:

Scenario 1: Intercompany Sales

 Provider: Entity A sells goods to Entity B.

 Receiver: Entity B purchases goods from Entity A.

Accounting:

 Entity A records a sale and an intercompany receivable from Entity B.

 Entity B records a purchase and an intercompany payable to Entity A.
 Intercompany Balancing Rule: The rule defines the accounts to be used for the intercompany
receivable and payable, ensuring that the transaction is accurately recorded in both entities'
books.

Scenario 2: Intercompany Loan

 Provider: Entity A lends money to Entity B.

 Receiver: Entity B borrows money from Entity A.

Accounting:

 Entity A records a loan receivable from Entity B.

 Entity B records a loan payable to Entity A.

Intercompany Balancing Rule: The rule defines the accounts to be used for the intercompany loan
receivable and payable, including the interest accrual and amortization.

Scenario 3: Intercompany Service Charges

 Provider: Entity A provides services to Entity B.

 Receiver: Entity B receives services from Entity A.

Accounting:
  Entity A records a service revenue and an intercompany receivable from Entity B.
 Entity B records a service expense and an intercompany payable to Entity A.

Intercompany Balancing Rule: The rule defines the accounts to be used for the intercompany
receivable and payable, as well as the appropriate revenue and expense accounts.

Key Benefits of Intercompany---

 Automation-- Automates the creation of intercompany transactions, reducing manual effort

and errors.
 Accuracy-- Ensures accurate and consistent accounting treatment across all legal entities.
 Efficiency--- Streamlines the intercompany process, improving efficiency and productivity.
 Compliance: Helps organizations comply with intercompany accounting standards and
regulations.
 Reporting--- Provides comprehensive reporting capabilities to track intercompany
transactions and their impact on financial performance.

Knowledge Sharing Session - 8

Rapid implementation:

It is a way to configure a financial enterprise and financial reporting structures quickly using sheets in
a workbook that upload lists of

 Companies (legal entities)

 Ledgers by country
 Business units
 Chart of accounts and segment values
 Segment value hierarchies
 Financials sequences
 Required sub ledger accounts
 Once the sheets have been uploaded, the application creates:
 Chart of accounts structure and instance
 Segment value hierarchies
 Key accounts such as retained earnings
 Required sub ledger accounts
 Accounting calendar
 Primary ledger for each country represented on the legal entities sheet
 Legal entities and their locations
 Business units
 Document and journal sequencing

Disadvantages

 You can’t upload intercompany

 You can’t upload multiple ledger with same currency
 You can’t upload Reporting ledger, secondary ledger only primary ledger you can create
 Assignment segment values will not use

Setups:
  Download rapid implementation sheet
 Fill the template with details
 Validate the templates
 Upload the template
 Verify the setup

Secondary Ledger:

 Additional reporting requirement (4 c’s difference)

 Additional accounting needs (Accounting methods, Gaaps)
 Additional statutory reporting needs (Corporate book and tax book)
 When there are any differences arises in any c’s (4 C’s) then we will bring secondary ledger in
concept
 When there is the difference in currencies (remaining should same) then we will bring
reporting ledger
 We have two scenarios in creation
o Take the already defined COA
o Create the new COA

Setups

1st scenario:

 Manage secondary ledger

 Specify ledger options
 Complete primary to secondary ledger mapping
 Run review and Submit accounting configuration
 Assign data access to secondary ledger
 Open secondary ledger period
 If you want to do a few more steps or else ignore this
 Manage ledger set
 Assign data access
 Enter Journal and post in primary ledger
 Enter adjustment category journal in secondary ledger
 Run trial balance report

2nd scenario

 Create COA value sets

 Create structure
 Create new structure
 Create COA value sets values
 Deploy COA
 Manage secondary ledger
 Specify ledger options
 Manage COA mapping
 Complete primary to secondary ledger mapping
 Run review and submit accounting configuration
 Assign data access
 Open periods for secondary ledger
 Enter journal and post in primary ledger
  Verify the journal entry in primary and secondary ledger

Configuring payments to banks in Oracle Fusion requires a series of setup steps to ensure smooth
payment processing from initiation to completion. Here’s an overview of the key steps involved:

1. Define Bank Accounts

 Create Bank: In Setup and Maintenance, navigate to Manage Banks to create a bank record.
 Define Bank Branch: For each bank, define branches where your accounts reside.
 Set Up Bank Account: Create a bank account under the branch with details like currency,
account number, and the owner (Legal Entity or Business Unit).
 Assign Usage: Specify how the bank account will be used (e.g., for payments, receipts, or
both) and assign it to the respective legal entities or business units.

2. Define Payment Methods

 Go to Manage Payment Methods to define the methods used for payment

processing, such as electronic, check, wire, etc. Assign each method to payment
types (supplier, employee, etc.).

3. Create Payment Document

 Under Manage Payment Documents, set up a payment document for each bank account.
Configure parameters like check numbers for printed checks or reference numbers for
electronic payments.
 Assign the payment document to a disbursement bank account, defining the document
sequence to ensure unique identifiers for each payment.

4. Define Payment Process Profiles

 In Manage Payment Process Profiles, create a profile for each payment type (e.g., EFT,
check). Profiles control processing steps, file formats, and transmission methods.
 Define rules for file generation, specify any remittance requirements, and link the profile to
the relevant bank account and payment method.

5. Set Up Payment Formats

 In Manage Formats for Extracts, define payment formats for each payment type, such as
SEPA, ISO20022, or custom formats. Ensure the format meets bank requirements.
 Link payment formats to the payment process profile, so the correct layout is used when
generating payment files.
6. Configure Payment Transmission

 Set up transmission configurations under Manage Transmission Configurations to specify

how payment files are sent to banks (e.g., via FTP, SFTP).
 Assign transmission configurations to the bank account or payment process profile for
automatic file transmission.

7. Define Payment Sources

 In Manage Disbursement Payment Sources, configure payment sources for each module
(e.g., Payables, Payroll) that will initiate payments through the bank account.
 Specify parameters for each source, such as default currency, processing type, and
associated payment methods.

8. Manage Payment Approval Rules

 Go to Manage Approval Rules for Payments to define rules for approving payments before
they are sent to the bank.
 Set up rule criteria based on amount thresholds, payment method, business unit, etc., to
ensure necessary approvals are obtained.

9. Set Up Payment Process Request Templates

 In Manage Payment Process Requests Templates, define templates for commonly used
payment batches. Specify criteria such as invoice selection criteria, payment method, and
bank account.
 Templates streamline the payment batch creation process, allowing you to quickly initiate
payments based on pre-set parameters.

10. Configure Payment Reconciliation (Optional)

 If your bank provides statements or files for reconciliation, set up Bank Statement
Reconciliation under Cash Management to automatically match bank statements with
payments.
 Configure matching rules to reconcile payments and identify discrepancies between bank
records and system records

11. Test the Setup

 Run a test payment batch using a small number of transactions to verify configurations.
 Confirm that the payment files are generated in the correct format, are approved, and can be
transmitted to the bank without issues.
 Make any necessary adjustments to formats, approval rules, or transmission settings based
on test results.

These steps cover the fundamental configuration for managing payments to banks in Oracle Fusion.
For each setup area, ensure all required permissions are in place, and coordinate with your bank to
validate payment file formats and transmission methods. Let me know if you’d like more details on
any specific step or if you need help with any troubleshooting.
Through the setup steps for the Accounts Payable (AP) module in Oracle Fusion, including navigation
paths. Here’s a general overview of the setup process. These steps may vary slightly depending on
the Oracle version and any customizations.

1. Define Supplier and Supplier Sites

 Navigation: Home > Procurement > Suppliers

 Steps:
 Create a supplier and configure supplier sites.
 Define necessary information, including address, payment methods, and tax details.

2. Define Banks, Branches, and Bank Accounts

 Navigation: Home > Payments > Bank Accounts

 Steps:
 Set up banks and branches.
 Define bank accounts for your organization, which will be used to process payments.

3. Set Up Payment Methods

 Navigation: Home > Payments > Payment Methods

 Steps:
 Configure payment methods, such as EFT, check, wire, and others that your
organization uses for supplier payments.

4. Manage Payment Terms

 Navigation: Home > Payables > Payment Terms

 Steps:
 Define payment terms, including discount options and due dates.
 Assign payment terms to suppliers.

5. Set Up Distribution Sets (Optional)

 Navigation: Home > Payables > Distribution Sets

 Steps:
 Define distribution sets to automate the distribution of invoice lines to various
accounts.

6. Configure Invoice Matching Options

 Navigation: Home > Payables > Manage Invoice Options

 Steps:
 Set up the matching level (two-way, three-way, four-way) as per your business
requirements.
 Define tolerances for matching.

7. Set Up Approval Workflow for Invoices

 Navigation: Home > Tools > Transaction Console > Approvals

 Steps:
 Configure invoice approval workflows, roles, and rules based on organizational
policies.
8. Define Financial Options

 Navigation: Home > Financials > Setup and Maintenance > Search for Financial
Options
 Steps:
 Set up financial options for accounts payable, including default liability and expense
accounts.

9. Configure Invoice and Payment Options

 Navigation: Home > Payables > Manage Invoice Options / Manage Payment Options
 Steps:
 Set parameters for invoice creation, payment processing, and other key AP
functionalities.

10. Set Up Supplier Withholding Tax (if applicable)

 Navigation: Home > Tax > Manage Withholding Tax

 Steps:
 Define withholding tax options, rates, and rules for supplier payments if required by your
organization.

11. Run Required Initial Processes and Validate Setup

 Steps:
 Validate all setups by entering test data and running necessary reports.
 Review trial balances, supplier balance reports, and payment status reports to
ensure correct setup.

Knowledge Sharing Session - 9

Purchasing Configurations:

 1. Manage purchasing line types (Mandatory)

 2. Manage unit measures (Optional)
 3. Manage carrier lookups (Optional)
 4. Manage Free On board (FOB) lookups (Optional)
 5. Manage fright term lookups (Optional)
 6. Manage purchasing document approvals (Mandatory)
 7. Configure procurement business function (Mandatory)
 8. Configure requisition business function (Mandatory)
 9. Manage procurement document numbering (Mandatory)
 10. Manage procurement agents (Mandatory)
 11. Manage document styles (Optional)
 12. Define translation rules (Mandatory) (TAD)
 13. Manage users (Employee as a user) (Mandatory)
 14. Define supplier (Mandatory)
 15. Create purchase order (Mandatory)

Oracle Fusion Tax Configurations:

 Regimes to Rates Flow Minimum Tax Configuration

 Defining a Minimum Tax Configuration demonstration
 Configure Withholding Tax Configuration
 Create Tax Regimes
 Create Jurisdictions and Rates
 Create applicable Taxes
 Create Tax Rates and Tax Recovery Rates
 Create Tax Exceptions
 Create Party Tax Profiles
 Create Tax Registrations
 Configuring Transaction-Based Fiscal Classifications
 Configuring Party Classifications
 Configuring Product-Based Fiscal Classifications
 Configuring Tax Rules
 Manage Configuration Owner Tax Options
 Configuring Simulator Transactions
### 1. What is a Single Org and Multi Org in R12?

 Single Organization (Single Org) Structure: In a Single Org structure, all business activities are
managed under one legal entity or operating unit. The organization has a single ledger, and
all transactions are recorded under that entity.
 Multi Organization (Multi Org) Structure: A Multi Org structure allows a company to manage
multiple legal entities or operating units within the same instance of Oracle EBS. You can
track and report financial data at different levels, such as by company, division, or region.
This setup is especially useful for global businesses operating in different countries or
regions, allowing for centralized data management but with different sets of rules,
currencies, and reporting for each entity.

### 2. AP invoice is created but not posted in GL, what is the reason for this?

 Several reasons could cause an Accounts Payable (AP) invoice to be created but not posted to
the General Ledger (GL):
 Unposted Invoice: If the invoice hasn't been processed correctly in the AP module, it may not
automatically trigger a posting to GL. The invoice needs to go through the appropriate
validation and accounting process.
 Mismatch between AP and GL Periods: The accounting period in AP may be closed, or there
could be a period mismatch between AP and GL.
 Accounting Method Issue: If the accounting method or setup in AP does not match the
accounting method in GL, posting could fail.
 Posting Process Failure: There may be an issue in the automatic or manual posting process
(e.g., a failure in the batch process or a setup issue in the posting configuration).
 Error in Distribution Setup: If the distribution lines of the invoice are incomplete or have
errors, it might prevent posting to the GL.

### 3. What is the approval hierarchy?

 The approval hierarchy in Oracle EBS refers to the structure or workflow of approval levels
through which transactions (like invoices, purchase orders, expenses, etc.) must pass before
they can be processed, paid, or finalized. It defines who can approve transactions at different
levels (e.g., manager, department head, finance department) and ensures that financial
controls are followed.
 Approval Rules: Define who can approve based on predefined rules (e.g., dollar limits,
department, etc.).
 Workflow: Automated routing of documents to different approvers based on the defined
hierarchy and approval rules.

### 4. How do we do bank transfer in R12 and R13?

In R12 and R13 (the core Oracle EBS and cloud-based systems like Oracle Fusion), the process for
bank transfer generally involves the following steps:

Create Bank Account: Set up your bank account in the system under the Cash Management module.

Bank Transfer Process:

 Navigate to the Cash Management Module: In R12, go to Cash Management > Bank
Transfers.
  Initiate Transfer: Choose the "Create Bank Transfer" option and enter the details such as the
transfer amount, source, and destination bank accounts.
 Approval: If applicable, the transfer might require approval based on the approval hierarchy
set up.
 Post the Transfer: Once approved, the transfer can be posted in the system to update the
balances of the bank accounts involved.
 Reconcile Bank Statements: In R12, after performing the transfer, reconcile the bank
statements to match the Oracle system with actual bank data.
 For Oracle Fusion (R13), the process is similar but streamlined through the cloud interface.
You will typically work with Payments and Cash Management modules to handle bank
transfers.

Knowledge Sharing Session - 10

File Based Data Import (FBDI) Process –

Auto Invoice:

When you talk about auto invoice creation it’s all about loading the open transactions into
receivables as a part of data conversions.

Auto Accounting Configuration for all account types (If you want to import any auto invoices or if you
want to create auto invoices in the receivables based on the any external system or order
management, sales order information we have to complete auto accounting configuration for all
types)

 Transaction source: Imported

 Create Line transaction Descriptive Flex field (If you want to load the auto invoice
information receivables this setup is mandatory)
 Download FBDI template form OER (Oracle Enterprise Repository)
 Prepare with Data
 Convert into CSV
 Load to Interface
 Import into base tables

How to Disable a Secondary Ledger Already Created?

 Once you disable the conversion of Secondary Ledgers, it immediately prevents the
propagation of journals from the Primary Ledger to the Secondary Ledger.
 The disabled Secondary Ledger is still available for historical reporting and manual journal
entries.
 Note: Balance level Secondary Ledgers cannot be disabled.
 To stop transferring balances from the source representation (Primary Ledger or balance
level reporting currency) to the balances level Secondary Ledger, stop running
consolidations.

Note: Adjustments only Secondary Ledgers cannot be disabled because journals are not
automatically transferred to this Secondary Ledger.

To disable the conversion of Secondary Ledgers:

• Navigate to the Accounting Options page.

• In the Secondary Ledgers region, select the Disable Conversion icon for the Secondary Ledger to be
disabled.

Note: Once the conversion of a Secondary Ledger is disabled, the status of the Secondary Ledger is
changed to Disabled.

See How to Disable a Secondary Ledger Already Created (Document:761380.1)

Knowledge Sharing Session - 11

Translation:

It is the process of translating account balances from functional currency to foreign currency. This
process translates balances only. It doesn’t translate individual transactions. While doing translation
makes sure previous month period status should be open.

Translation rates

 Expenses & Revenue - Average rate

 Assets & Liabilities - Period end rate
 Equity & Owner ship - Historical rate

Configurations:

 Define Translation adjustment account and period end, period average rates at specify ledger
options
 Manage Conversion rates for period end, period average rates
 Manage Historical rates conversion
 Create translation ledger
 Run translation process
 Run General ledger trail balances report
Knowledge Sharing Session - 12
Auto Post:

 We can post the journals automatically by specifying some criteria in the Auto post criteria
set.
 Criteria could be: combinations of ledger or ledger set, journal source, journal category,
balance type, and period.
 Once you define an Auto Post criteria set, run the Auto Post program to select and post any
journal batches that meet the criteria defined by the criteria set.
 You can also schedule the Auto Post program to run at specific times and submission
intervals.
 You can submit the Auto Post program or schedule Auto Post runs directly from the Auto
Post Criteria Sets window. Alternatively, you can use the Submit Request window

 Manage auto post criteria sets

 Create multiple journals for testing
 Run auto post

Auto Reversal:

It is nothing but, reversing journal automatically based on the criteria that we specify in the criteria
sets

Criteria could be:

 Journal category
 Reversal Method
 Reversal period

If you routinely generate and post large numbers of journal reversals as part of your month end
closing and opening procedures, you can save time and reduce entry errors by using Automatic
Journal Reversal to automatically generate and post your journal reversals.

 Manage Journal reversal criteria set

 Assign criteria set to ledger options
 Enter journals against the category mentioned in reversal criteria set
 Open Next period
 Review auto reversal
 Oracle Cloud Financials Interview Questions
1. How many Balancing Segments can define in the Fusion? (or) How many Balancing Segment Labels
are there in Fusion?
Ans: Primary Balancing Segment, Second Balancing Segment and Third Balancing Segment.

2. How many segments are mandatory to create a Chart of Accounts?

Ans:
1. Company as a Primary Balancing Segment
2. Natural Accounts Segment
(Note: Minimum two segments are mandatory, and Maximum 30 Segments we can create)

3. How many ways we can add values in the value set?

Ans: Three Types
1. Manual
2. Spread sheet
3. Rapid Implementation

4. How many types of calendars available in fusion?

Ans: Three Types
1. Accounting Calendar
2. Transaction Calendar
3. Inventory Calendar

5. How many adjustment periods are available in fusion?

Ans: There are 8 adjustment periods are available, these are;
1. Once at beginning of year and once at end of the year
2. Once mid-year and once at year end
3. Once mid-year and twice at year end
4. Once at year end
5. Twice at year end
6. None
7. Other
8. Quarterly

6. What are mandatory accounts to use the financial category?

Ans:
1. Accounts Payable
2. Accounts Receivable
3. Asset Clearing
4. Cash Account
(Note: We will call these accounts as Control Accounts)

7. How many sub ledger accounting methods available in the fusion?

Ans:
1. Standard Accrual
2. Standard Accrual with Encumbrances
3. Standard Accrual for China
8. What are prerequisites for Primary Ledger?
Ans: It consists of 4 C’s
1. Chart of Accounts Structure Instance
2. Calendar
3. Currency
4. Convention Accounting Method.

9. Can we override the accounting method at any time after implementation?

Ans: Yes, we can override the accounting method at any time.

10. How many accounts we can assign at the primary ledger level?
Ans: Seven Accounts, these are;
1. Retained Earnings Account
2. Cumulative Translation Adjustment Account
3. Rounding Account
4. Entered Currency Balancing Account
5. Default Suspense Account
6. Net Income Account
7. Reserve for Encumbrance
(Note: 1-6 are relating to Standard Accrual Method. And remaining account is relating to Standard
Accrual with Encumbrance means budget-based method)

11. What are different concurrent programs will run after submission of Review and Submit
Accounting program?
Ans:
1. Complete Accounting Configuration: Create Balances Cubes
2. Complete Accounting Configuration: Load Chart of Account Values
3. Complete Accounting Configuration

12. How many types of ledgers available in the fusion?

Ans: 3 Types of Ledgers available in the fusion, these are;
1. Primary Ledger
2. Reporting Ledger
3. Secondary Ledger

13. What is the main purpose (or) objective of a balance cube?

Ans: It stores financial balances in a multidimensional cube for real time, interactive financial
reporting and analysis.

14. How many seeded data sets provided by Oracle?

Ans: Two seeded data sets available.
1. Common Set
2. Enterprise Set

15. Can we customise the reference data set?

Ans: Yes, we can customise the reference data set.
16. How many configuration levels available in the configuration Lookup?
Ans: Three Types.
1. System
2. Extensible
3. User.

17. Can we assign more than one Balancing segment value at Legal entity level?
Ans: Yes, we can assign more than one Balancing segment value at Legal entity level.

18. Can we assign one Business Unit to more than one Legal Entity?
Ans: Yes, we can assign one Business Unit to more than one Legal Entity.

19. What are various roles need to add for AP?

Ans:
1. Accounts Payable Manager
2. Accounts Payable Supervisor
3. Accounts Payable Specialist
4. Accounts Payable Invoice Supervisor.
5. Accounts Payable Payment Supervisor.
(Note: Last two roles have been added recently)
20. Can we change Legal Entity and Business Unit names at any time?
Ans: Yes, we can change Legal Entity and Business Unit names at any time

21. Do we need to add any steps in the GL, while closing books in the month end?
Ans: Yes, we need add financial categories for mandatory accounts.

22. What is the procedure we should follow, when we add new values in the value set values?
Ans: We should check with GL Consultant for tree versions and tree structure level changes.

23. What is first setup we have to do in the Accounts Payable?

Ans: we have to setup for the “Manage Common Options for Payables and Procurement”.

24. How many types of Accrual Expenses methods available in the fusion?
Ans: Two methods
1. At Receipt
2. At Period End

25. When we are creating Liability Account, where it will locate as a default account?
Ans: Payables assigns Liability account as a default account at the below levels.
1. Common Options of Payables and Procurement
2. Supplier and site assignments
3. Invoice Header.

26. What are different options of Accounts for Payment?

Ans:
1. At Payment Issue
2. At Payment Clearing
3. A Payment Issue and Clearing
27. How many types of Receipt Routings available in the fusion?
Ans: Three Types.
1. Standard Receipt
2. Direct Delivery
3. Inception Required

28. Can we able to over-ride the Non-PO, Non-Inventory based Invoices?

Ans: Yes, we can override the account facility and redo the accounting.

29. What is the significance of Procurement Agent? What are functionalities he will handle?
Ans: Procurement agents will do requisitions, supplier data and supplier qualifications.

30. What are different types of orders?

Ans:
1. Purchase Order
2. Blanket Purchase Agreement
3. Contract Purchase Agreement

31. What is the hierarchy for vendor?

Ans:
● Vendor Name – Header
● Site/ Addresses
● Site Assignments
● Contacts
● Bank Accounts

32. What is Purchase Price Variance?

Ans: The difference between standard item cost and PO level Item cost.

33. What is Invoice Price Variance?

Ans: The price variance between PO level item price and the invoice level item price.

34. What is the Account type of Inventory AP Accrual Account?

Ans: The Account type for Inventory AP Accrued account is Liability.

35. What are different types of Matchings available in fusion?

Ans:
1. Two Way Matching
2. Three Way Matching
3. Four Way Matching

36. What are different types of Purchase Orders available in the EBS and Fusion?
Ans:
1. Standard Purchase Order
2. Planned Purchase Order These three types are available in the Fusion
3. Blanket Purchase Agreement
4. Contract Purchase Order
(All 4 types available in the EBS)
37. What are different types of Requisitions available in Oracle Applications?
Ans:
1. Purchase Requisitions
2. Internal Requisitions
3. Imported Requisitions
4. Paper Requisitions

38. How many Types of RFQs available in the Oracle applications?

Ans: There are 3 types of RFQ’s
1. Standard RFQ
2. Catalog RFQ
3. Bid RFQ

Bid: Used for a specific, fixed quantity, location, and date. For example, a Bid would be used for a
large or expensive piece of equipment that you’ve never ordered before, or for an item that incurs
transportation or other special costs. You cannot specify price breaks for a Bid quotation or RFQ.
Standard: Used for items you’ll need only once or not very often, but not necessarily for a specific,
fixed quantity, location, and date. For example, you could use a catalog quotation or RFQ for office
supplies, but use a Standard quotation or RFQ for a special type of pen you don’t order very often. A
Standard quotation or RFQ also includes price breaks at different quantity levels.
catalog: Used for high–volume items or items for which your supplier sends you information
regularly. A catalog quotation or RFQ also includes price breaks at different quantity levels.

39. How many Types of Quotations Available in the Oracle Applications?

Ans: Like RFQs, there are three types of Quotations.
1. Standard Quotations
2. Catalog Quotations
3. Bid Quotations

40. What are different levels to control matching approvals?

Ans:
1. Supplier Site Level
2. Item Site Level
3. Receipt Option Level

41. How many accounts will control at PO level?

Ans: Three Accounts,
1. PO Charge Account
2. PO Accrual Account
3. PO Variance Account

42. Can we override Charge Account at PO level?

Ans: We can’t override the Inventory type PO charge account. But we can override the expense type
PO.

43. Can we reopen the closed period?

Ans: If it is in closed status we can reopen. And we can’t reopen, if it is in permanently closed status

44. How can we define the PO relates to which class as a financial functional consultant?
Ans: We can define the PO class by “Destination Type”, while creating the purchase order.
45. What are different types of Invoices in AP?
Ans:
1. Standard
2. Prepayment
3. Debit Memo
4. Credit Memo
5. Withholding Tax
6. Interest
7. Payment Request
Below Invoices had been used in EBS, and the same invoices have obsoleted in Fusion.
1. Transportation
2. Mixed
3. Retainage
4. Expense Report

46. How many types of Prepayments available in AP?

Ans: Two types
1. Temporary
2. Permanent

47. What are different types to enter the Invoice?

Ans:
1. Manual
2. Automatic Invoice generation from PO (Self Billing (or) Auto invoice (or) Pay on Receipt)
3. FBDI (File Based Data Import)
4. OCR (Optical Code Reading (or) Optical Character Recognition)
5. ADFDI (or) Spreadsheet
6. Import Invoices from Source Systems

48. What would be the reason, when we are unable to see the vendor details (After creation of
vendor) while creating the invoices?
Ans: We need to check the supplier site level pay site has been enabled or not.

49. What are different types of Invoice lines?

Ans:
1. Freight
2. Item
3. Miscellaneous

50. Can we delete the invoice, once we validated?

Ans: We can’t delete the invoice after validation process.

51. What are different types of Payment Methods?

Ans: Mainly we will use below two payment methods for payment purpose
1. Check
2. Electronic Fund Transfer
But we can find some more methods to make a payment, these are;
1. Cash
2. Inter-bank Payment order
3. Postal Order
4. Credit Card
5. Debit Card
6. Direct Debit

52. Can we restrict payment limit, while running the payment batch?
Ans: Yes, we can restrict payment limit in the Payment setups level.

53. How many types Banks available in Oracle?

Ans: Two Types;
1. Internal Bank
2. External Bank

54. Can we make the payment of Invoice without accounting?

Ans: Yes, we can pay the invoice before posting to ledger.

55. Is there any option to make the partial payment from invoice page?
Ans: We can’t make the partial payment from the invoice page.

56. Can we do the accounting for payment without doing the invoice accounting?
Ans: No, we can’t do the accounting for payment before post into GL.

57. Where can we check the Invoice discount eligibility in the invoice page?
Ans: Open the invoice and go to Manage Instalments under Invoice Actions.

58. How many types of Prepayments available in Oracle?

Ans: Two Types;
1. Temporary Prepayment
2. Permanent Prepayment

59. How Prepayment can be decided by system as temporary or permanent prepayment?

Ans: If “Allow Prepayment Application” option enable in the invoice, then the invoice will be
temporary prepayment invoice. Otherwise, it will be the permanent prepayment invoice.

60. Can we do the partial payment against prepayment invoice?

Ans: No, we can’t do the partial payment against prepayment invoices.

61. Are we able to cancel the prepayment invoice (or) standard invoice after prepayment applied to
standard invoice?
Ans: No, we can’t cancel once we applied the prepayment to standard invoice.

62. Can we use the void the check for payments in future?
Ans: No, we can’t use the check once it’s voided.

63. What are invoice actions available at payment hold level?

Ans:
1. None
2. Cancel Invoice
3. Place hold on Invoice
64. How many ways document sequences can define at the ledger level?
Ans:
1. Ledger wise
2. Legal Entity wise
3. Business Unit wise
4. Tax Authority wise

65. Can we override the Retained Earnings account?

Ans: Yes, we can override the Retained earnings account in the ledger options.

66. What is the sequence for period end closure?

Ans:
For Period End
1. Inventory
2. Accounts Payable
3. PO
4. Accounts Receivable
5. Fixed Assets
For Receipt
1. Inventory
2. PO
3. Accounts Payable
4. Accounts Receivable
5. Fixed Assets

67. What is the main objective of unaccounted transactions report?

Ans: This report main objective to show the unaccounted transactions for month wise

68. What is the formula of period end for reconciliations?

Ans: Previous month AP TB + Present month posted invoice register -present month posted payment
register = AP TB latest balance.

69. How many key flex fields available in Fixed Assets?

Ans: 3 Flex Fields;
1. Asset Category
2. Asset Location
3. Asset Key

70. What is the main objective of Fixed Assets Application?

Ans: The objective of Fixed Assets, to capitalise the assets and run the depreciation.

71. What are different types of books in FA?

Ans:
1. Corporate
2. Tax Book

72. What are various asset types available in FA?

Ans:
1. Capitalise
2. Expense
3. CIP (Construction in Progress)
4. Group of Assets

73. Assets application works at which level?

Ans: Assets application works at Ledger level.

74. Can we implement the security segment rule for FA?

Ans: Yes, we can implement the security segment rule for FA.

75. How many segments we can create at category flex field in FA?
Ans: We can create up to 7 segments at category flex field in FA.

76. How many types of calendars available in FA?

Ans: Three Types;
1. Fiscal Calendar
2. Depreciation Calendar
3. Prorate Calendar

77. How many types of Divide Depreciation Models in FA?

Ans: 2 Types-
1. By Days
2. Evenly

78. Can we able to create foreign currency assets other than functional currency?
Ans: No, we can’t create the asset with foreign currency.

79. Can we Install/Capitalize the asset without making the payment?

Ans: Yes, we can capitalize the asset without payment made.

80. Can we able to assign the Asset Category in AP Invoice Level?

Ans: Yes, we can assign the asset category under asset option in Invoice line level.

81. What are the types of Mass Additions in FA?

Ans:
1. PO based Invoice creation
2. PO and GRN based Invoice creation
3. Non-PO based Invoice creation

82. Is there any option to open the period in FA?

Ans: No, there is no option to open the period in FA.

83. What are different Queue statuses/Mass addition statuses available in FA?
Ans:
1. New
2. Post
3. Posted
4. Cost Adjustment
5. Delete
6. Error 7. Merged 8. On Hold 9. Split

84. Can we able to create the asset directly in FA?

Ans: Yes, we can create the asset directly in FA.
Knowledge Sharing Session - 13
Leger set

 It allows you to access multiple ledgers at a time. We can book multiple ledgers in single user.
 User can enter journals against all ledgers without changing access.
 User can open/close periods for all ledgers without changing access.
 User can run report for all ledger in one go
 Note: All ledgers should share the same COA & Calendar

Setups-

 Manage ledger set

 Assign ledger set to role
 Open/Close period using ledger set
 Enter journals
 Run Report

Data Access set:

 It is a functionality that gives the user privileges like Read only, Read and write for specific
balancing segments
 Data access controls two ledgers
 Full ledger (We can enter journals in all balancing segments like HYD, Chennai, Bang, Mum)
 Primary Balancing segment (We can enter Journals in Few balancing segments)

Setups-

 Manage data access set

 Assign data access set to role
 Book the journal

Knowledge Sharing Session -14

Withholding tax

It’s all about calculating the tax and holding from the invoice the tax amount means if we are going
to create the transaction if withholding tax is applicable system will create the separate invoice with
the tax amount which we have to pay to tax authority

Setups

 Create withholding tax authority as a supplier

 Create payables calendar (special calendar (EBS)) (optional)
 Manage withholding tax options
 Manage tax codes
 Create tax classification (Task group (EBS))
 Assign tax group (tax classification) to standard supplier
 Create standard invoice
 System create WHT invoice with tax authority

Interest Invoice:

Interest invoice will come in to the picture when late payment is done.
Setups

 Enable “Create interest invoice” at invoice options

 Enable Create interest invoice at supplier site level ( In EBS we enable at supplier level but in
fusion enable at supplier site level)
 Define interest rates
 Create invoice with past date with immediate payment term
 Create Payment today

Foreign currency / Multi currency invoice:

 For this first we have to make sure we have a bank account which allows to process foreign
currency payments.
 Enable currency conversion rate entry, realized gain or loss and conversion rate variance gain
loss account details at common options for payables and procurement
 Enable currency conversion rete entry at Payment Options
 Enable multi-currency option for Bank account
 Manage daily rates
 Create invoice for foreign currency and payment

Knowledge sharing about Document Sequence.

Yes, in Oracle Fusion, you can set up and manage Document Sequences to ensure unique numbering
for documents like invoices, receipts, and orders. This setup is typically part of the Financials or SCM
modules, depending on the type of document.

1. Define Document Sequence -- You first need to define a document sequence in Oracle Fusion---

1. Navigate to Setup and Maintenance--

 Go to the>>> Setup and Maintenance work area.

 Search for the task: Manage Document Sequences.

2. Create a Document Sequence---

 Click Create and define the document sequence properties, such as:
 Name: The name of the sequence.
 Type: Choose between Automatic or Manual.
 Start Value: Define the starting number.
 Increment By: Specify the increment value (e.g., 1).

3. Save the configuration.

2. Assign Document Sequence to a Document Category

 To use the sequence, assign it to a document category

 Navigate to Manage Document Sequence Assignments
 In the Setup and Maintenance area, search for Manage Document Sequence
Assignments.
 2. Assign to a Category---
 Select the appropriate document category (e.g., AR Invoices, AP Payments).
 Assign the previously created sequence.
 3. Specify Conditions (if needed)
  You can configure conditions (e.g., based on business unit or document type) to
determine when the sequence is applied.
 4. Save the assignment.
 3. Load Document Sequence Assignments Using File-Based Data Import (FBDI)

If you need to load document sequence assignments in bulk, use the FBDI method

 Download the FBDI Template

 Go to>> Setup and Maintenance and search for the task>> File-Based Data Import for
Document Sequences.
 Download the relevant template (e.g., for document sequence assignments).
 Populate the Template
 Fill in details like document sequence name, category, application, and assignment
conditions.
 Upload the File
 Use the Scheduled Processes work area to upload the completed FBDI file
 Process Name: Load Interface for Import.
 Import the Data
 Run the corresponding import process to load the document sequence assignments.
 Test and Validate
 Once setup or loaded, test the document sequence by creating a document in the respective
module (e.g., an invoice in Accounts Payable) and ensure it is using the correct sequence.

Knowledge Sharing Session - 15

Payment Batch (PPR)

Bunch of Payment with single run, why should I go for the single check payment. I will the run the
payment batched daily basis, I want to print the 100 or 50 checks on the daily basis. Payment batch
always run based on due date. Payment batch main objective to reduce the manual work to make
the bunch of payments with in the single time.

Payment batch can run based on the below criteria.

 Pay through date

 Supplier type
 Supplier Name
 Invoice batch/ Group name
 Payment method (Most of the clients used through this)
 Pay group
 Business Unit
 Currency
 Legal entity (Fusion)
 Source (Fusion)
It consists of below status or stages.

 Check Payment method

 2. EFT (Electronic Fund transfer)
 Select
 Build
 Format
 Print
 File will generate and send to Banker
 Confirm
 Select the payment batch form above criteria (invoice group name or payment method). It
will pick the all-eligible invoices based on the today due date.
 Then you can review the selected invoice.
 You can modify the amount 100000 to 90000 or 50000 you can’t increase the amount but
you can decrease the amount.
 You can add the invoice if it has any discounts.
 You can remove any high-volume invoice is there, you can pay in the next batch.
 It have built to build the payment.
 Then what is the format to be consider the for the printing.
 The check format will go to the printer to print the check.
 That check sends to banker then confirm.

Pre-requisites for Payment Batch.

1. 1. Invoice should be validated - It will work for payment batch

2. Invoice Validated and Accounted - It will work
3. 3. Only the invoice header is entered and the line forget - It will not work for the payment
batch
4. Only invoice header, line and distribution entered but not validated. It will not work for the
payment batch
5. Entered the invoice header validated but kept on hold - It will not work
6. Partial invoice - It will not work

It will consider invoice types for Payment Batch.

 Standard
 Credit Memo
 Debit Memo
 Prepayments

Setups:

 Payment Methods
 Payment Templates
 Payment Format
 Payment process Request (PPR)
 Internal Bank accounts
 Check books
 1,2,3 done by the Technical team.
How transactions will create module wise

 (GL)
Level-> Journal Entry
Transactions are created as manual journal entries, imported journals.
 (AP) ->
Level: Invoice Level and Payment Level.
 (AR) ->
Level: Invoice Level and Receipt Level.
 FA)->
Level: Asset Level
Transactions are created for asset additions, adjustments, retirements, and transfers.
 (CM)
Level: Bank Statement and Cash Transactions Level.

GL--- Ledger level

AP--- Business Unit level
AR--- Business Unit level
FA--- Ledger level
CM--- Legal Entity level

Balance Forward Billing (BFB):

 In EBS R11i, we call it as consolidated billing.

 In EBS R12, Balance forward billing.
 In fusion, Balance forward billing (BFT) we can used for consolidate billing purpose.

Instead of billing the customer for each and every transaction separately multiple transaction you
can take in to one bill generation by using this balance for billing functionality.

Now if you want to create the consolidated bill for multiple transactions against the specific
customer what setups we have to do.

1. Create balance forward billing cycle (Here we will specify how often we do the billing to the
customer).
2. Create BFB payment terms.
3. Create BFB customer profile class.
4. Crete BFB new customer and assign profile class to customer.
5. Create few transactions.
6. Run “Balance for Billing” report.

When we compare with the EBS in system options level we have one show billing number option if
you enable this for each transaction system will display along with the transaction number it shows
that invoice is part of which balance for billing the number it will be displaying but in fusion we don’t
have option.

File Based Data Import (FBDI) Process – Auto Invoice:

When you talk about auto invoice creation it’s all about loading the open transactions into
receivables as a part of data conversions.

1. Auto Accounting Configuration for all account types (If you want to import any auto invoices
or if you want to create auto invoices in the receivables based on the any external system or
order management, sales order information we have to complete auto accounting
configuration for all types)
2. Transaction source: Imported
3. Create Line transaction Descriptive Flex field (If you want to load the auto invoice
information receivables this setup is mandatory)
4. Download FBDI template form OER (Oracle Enterprise Repository)
5. Prepare with Data
6. Convert into CSV
7. Load to Interface
8. Import into base tables.

Knowledge sharing about Allocation ->>>>>>>>>

What is the meaning of Allocation?
Allocation refers to the process of distributing a specific amount of money or resources across
different accounts, cost centers, or other organizational units based on predefined rules or criteria.

Allocation creation stepwise -->>>>

Creating GL Allocations in Oracle Fusion >>>>>>
Step 1: Define Allocation Rule
 Navigation->>>>Go to General Accounting > Journals > Task Panel > Create Allocation Rules.
 Create Rule Set->>Click Create Allocation Rules.
 Provide details such as---->>>>Rule Set Name: A meaningful name (e.g--Expense Allocation).
 Description---Describe the purpose of the allocation.
 Rule Set Code--- A unique code identifier.
 °°Module---Choose General Ledger.
 °°°Define Rule Components--->>>
 Add Rule Name, Description, and Calculation Method-->>>
 Examples°°°°°
 Fixed Percentage->>> Allocate costs based on predefined percentages.
 Spread Evenly->>> Distribute amounts equally across accounts.
 Factor-Based: Allocate using statistical data (e.g., headcount).

Step 2: Define the Allocation Formula

1. Source Definition---
Specify the source of the amount to allocate>>>
 Ledger, Accounts, Journals, or Statistical Accounts.
 Define specific account ranges or account combinations.

2. Target Definition->>>
 Define the target accounts where the allocation will post:
 Define account segments (e.g., cost centers, departments).

3. Formula Configuration---
Use simple formulas (e.g., percentage) or advanced formulas with SQL expressions to calculate
allocation amounts.

Step 3: Validate Allocation Rule

1. Run Validation->>

 After defining the allocation formula, click Validate to ensure the rule logic is correct.
 Resolve any errors or warnings before proceeding.

Step 4>>Assign Rule to a Rule Set

1. Add the rule to an existing rule set or create a new one.

2. Ensure the sequence of execution for multiple rules is correctly defined.

Step 5->>>Run Allocation Process

1. Navigation>>>>
 Go to General Accounting > Journals > Task Panel > Generate General Ledger Allocations.
2. Run the Allocation Process->>>>
 Select the rule set and ledger.
 Specify the accounting period.
°°°°Submit the process.

3. Review Results->>
 Navigate to Journals > Manage Journals to review the generated allocation journal entries.

Step 6-- Post Allocation Journals

1. Review and approve the allocation journal entries (if required).

2. Post the journals to the General Ledger.

Additional Notes*****

 Dynamic Allocation>--If allocation data changes frequently, consider using statistical journals
to input dynamic factors (e.g., headcount, square footage).
 Audit Trail•••Allocation journals maintain a clear audit trail with rule references.
 Scheduling••••Automate recurring allocations by scheduling the allocation rule process.

 Allocation rules cannot be directly defined at the ledger set level. They must be defined
separately for each ledger. Similarly, you need to run the allocation request separately for
both the primary and secondary ledgers.
 Primary and Secondary Ledgers may have different chart of accounts, currencies, or
accounting calendars. Allocations must align with the configuration of each ledger, which
requires defining the rules separately.

 Ledger Sets primarily allow for easier management of tasks (e.g., running reports, processing
journals) across multiple ledgers but do not support centralized allocation rule definitions.
Is Allocation the same as Mass Allocation?

 No, Allocation and Mass Allocation are not the same, although they are closely related.
 Allocation-> Refers to the broader process of redistributing amounts from one account to
others based on predefined rules or formulas. It includes both simple and complex allocation
methods. Allocations i are set up using Allocation Rules within the General Ledger.
 Mass Allocation-> A specific type of allocation used in legacy Oracle EBS systems (not directly
in Fusion) to allocate amounts across multiple accounts or dimensions simultaneously, based
on statistical measures like headcount or square footage. In Fusion, mass allocation has been
largely replaced by Advanced Allocation Rules, which offer more flexibility.

Practical Examples of Statistical Journals/Headcount/Square Footage ------******

Statistical Journals•••

 These journals capture non-monetary data (like headcount, square footage, machine hours)
that can be used for allocations or reporting.

Example>> Recording the headcount in various departments (HR, Finance, Operations) for cost
allocations.

Practical Examples••••

1. Headcount-->>

 Used to allocate costs like employee benefits or HR expenses.

Scenario@-->>

 The HR department incurs $50,000 in expenses. You allocate these costs based on the
number of employees in each department.
 HR: 10 employees → 20% allocations
 Finance: 20 employees → 40% allocations
 Operations: 20 employees → 40% allocations

2. Square Footage:

Used to allocate costs like rent or utilities.

Scenario@->>An office's monthly rent of $30,000 is distributed based on the square footage
occupied by each department.

 HR occupies 1,000 sq. ft. → 25% allocation.

 Finance occupies 2,000 sq. ft. → 50% allocation.
 Operations occupies 1,000 sq. ft. → 25% allocation.
 Statistical Measure (e.g., Machine Hours) ••
 Used for production-related allocations.

Scenario@->>Factory maintenance costs of $20,000 are allocated based on machine hours.

 Machine A->> 40 hours → 40% allocation

 Machine B->> 60 hours → 60% allocation.

Knowledge Sharing Session -16

Withholding Tax:
It’s all about calculating the tax and holding from the invoice the tax amount means if we are going
to create the transaction if withholding tax is applicable system will create the separate invoice with
the tax amount which we have to pay to tax authority.

Setups:

1. 1.Create withholding tax authority as a supplier

2. Create payables calendar (special calendar (EBS)) (optional)
3. Manage withholding tax options
4. Manage tax codes
5. Create tax classification (Task group (EBS))
6. Assign tax group (tax classification) to standard supplier
7. Create standard invoice
8. System create WHT invoice with tax authority

Pay Alone:

By default, system will allow us to process the payment for multiple invoices with one check; by using
one check we can issue the payment for multiple invoices. If you have a requirement of setting the
restrictions on document usage for the invoices we can use the pay alone, if you enable or set the
pay alone control system will for each document or each check system will generate the separate
check. To implement that condition in the application we can use the pay alone concept

Ex: If we have 10 invoices with the same supplier and same site system will create the check for all 10
invoices it won’t create the one check to all 10 invoices

Setups:

1. Enable Pay Alone option at supplier Level

2. Create two invoices
3. Payment

Knowledge Sharing Session - 17

Multi Period Accounting (MPA)

We are the paying the expenditure and converting to the multiple period expenditure, will pay the
amount one time but it will give the service for further months.

Ex: We paid the Internet charges 12000 in this month but they provide service for next 3 months.

When we paid the money entry is

 Accrued expense/Prepaid expenses DR 12000

 Liability CR 12000

In the Last Month entry is

 Liability DR
 Cash Clearing CR

For this system will generate the below entries for the total months

 Nov-24
 Dec-24
  Jan-25

 Internet expenses DR 2000 Accrued expenses CR 2000

Like this system will generate the remaining two month like Nov, Dec and Jan

In AP vice versa (Bill in advance)

 Create Invoice
 Go to Home page
 Click on Payables
 Go to Invoice
 Go to Task list
 Click on Create invoice
 Give the header details then go to lines and give the amount
 Select the line go to action and then click on Columns then go to Multi period accounting and
give the start date, end date and accrual account

Then go to multiple accounting tab in the lines give the start date, end date and accrual account

 Go to distribution then give the charge account is internet expense because of we are
creating the Multi period accounting
 Validate and post it
 Do the payment
 Run the Create Multi period accounting at the month end
 Go to navigation
 Click on Tools
 Click on New schedule Process
 Run the report Create Multi period accounting program
 Give the details and save
 Submit

Knowledge Sharing Session - 18

Payables to General ledger reconciliation:

 In case of EBS it’s completely manual Process where we have to run the reports and
manually, we have to verify.
 In case Fusion they did some enhancement for such kind of processes which can do
manually. If you want to reconcile Payables with General Ledger application first, we have to
run.

1. Set the financial category for control accounts (Account payable).

2. Run “Payables to Ledger Reconciliation” Process

1.Set the financial category for control accounts (Account payable):

 While we are doing the reconciliation between AP to GL we have to set the financial category
as source account means Accounts payable.
 Go to setup and maintenance.
  Setup: Financials.
 Functional Area: Financial Reporting Structure.
 Task: %Manage % chart % account% value% set% values%.
 Select Manage Chart of Accounts Values Set Values.
 Query the control account and check the financial category.
 Then only system will allow us to reconciliation
 Save and close.

2. Run “Prepare to Payables to General Ledger Reconciliation” Process:

 Go to ESS (Enterprise Schedule Service) job Page nothing but Schedule Process.
 Click on Navigator click on tools then click on Schedule new process.
 Instead of doing all time like this just mark as favorites.
 Run “Prepare to Payables to General Ledger Reconciliation”.
 Give the Request name (this name use in the report).
 Give the account condition means for which account you want to run this report
 Submit.
 After completed this go to payables work bench.
 Go to task list then click on Payables to Ledger Reconciliation.
 Then one page will open in that you can see the details.
 Save and close.

What is PPV?

PPV stands for Purchase Price Variance. It is a concept used in procurement and accounting to track
the difference between the purchase order price and the actual invoice price of goods or
services received.

What is IPV?

IPV stands for Invoice Price Variance. It is used to track and manage the difference between the
purchase order price (or the receipt price) and the invoice price at the time of supplier invoice
matching. This variance typically occurs when the supplier's invoice price does not match the agreed-
upon purchase price.

Knowledge Sharing Session - 19

Manage Transaction Types

 Transaction type will control the process of the transaction, how you want to create
transactions, the transaction needs to be created against the which class of the transaction,
if you want to create debit memo transaction or credit memo transaction and in these
transactions which sign amount will enter that is positive or negative like this.
 To define the process of transaction we have to create the transaction type without this you
can’t create the transaction in the receivables.
 Go to setup and maintenance.
 Setup: Financials.
 Functional area: Customer billing.
 Task: %Manage% transaction % type%
 Select Manage Transaction Types.
 Click on + to create type.
  Give the details and this transaction will assign to business unit go to reference accounts tab.
 Click on + icon to assign business unit you can one or multiple business units for this.
 Give the Transaction type set is Reference data set, where ever you see the set just you can
remember that is data set.

We have 5 transaction classes:

1. 1.Bills receivables
2. Chargeback
3. 3.Credit memo,
4. Debit memo,
5. 5.. Invoice (In this present doesn’t have deposit and guarantee in next releases those may
come).

We have 4 Transaction status:

1. Open, 2. Closed, 3. Pending, 4. Void.

 Generate Bill nothing but Print option if you want print just keep it as yes or else no.
 Open receivable: It will update supplier balances.
 Allow fright: If it is enabled while entering the transaction fright column will appear.
 Post to GL: If it is enabling then only this transaction will transfer to GL.
 Allow adjustment posting: customer amount (bad debt) can be adjusted.
 Natural application only: If you create the transaction with this transaction type you can
create the receipt up to transaction amount only.
 Allow over application: Means more than the invoice amount will enable
 Give the BU and if you want to give the account details or else we can set as constant.
 Click on save and close.

Knowledge Sharing Session - 20

Manage invoice options:

 Go to set up and maintenance.

 Set up: Financials/Procurement.
 Functional area: payables
 Task: %manage% invoice% option%.
 Select Manage invoice options.
 Scope should be our BU.
 Under Invoice entry enable the all options except require invoice group.
 All data bases should be invoice data bases except pay data base is should be
discount data base.

Required invoice group: Acts like invoice batch, in this you can add number of invoices like Batch
names (RT-123) under this batch we have so many invoices like (INV-1,2,3,4) like this.

 Allow document category override: It assigns a unique number like

 AP INV-145 (When you enter invoice with 145 Starting invoice number)
 AP INV-167 (When you enter invoice with 167
 Starting invoice number).
 Allow adjustments to paid invoices: When I am creating invoice wrongly entered debit
account instead of advertisement expenses debited telephone expenses, if you enable this you can
edit the invoice.
 Allow remit to supplier override for third party payments: If you want to pay the money to
third party you can enable this ex: Invoices will be one supplier but payment should pay to another
party (third party) along with this supplier
 Recalculate invoice instalments: When you change the due for payments then system
automatically change the dates also Ex: NET10 (FEB 23) change the payment term from this to
NET50(MAR20) then system will change the due date feb23 to mar 20
 Hold unmatched invoiced: We have PO and NON-PO based invoice if you enable this it holds
the NON-PO based invoices because it doesn’t have any matching PO
 Payment terms: It depends on suppliers.

Term data basis: In which date system will generate the payment is called Term data basis we have
below dates

 Goods receipt date

 Invoice receipt date
 System date
 Invoice date

This option give importance is supplier level, if info not available in this then it goes to invoice option
level

Pay date basis: If you enable this on the date of discount date payment will run otherwise normal
payment.

Accounting date base:

 Note: In EBS we have profile option enable but in cloud we don’t have
 Under matching tab enable only one option like allow matching distribution
override.
 Under Discount tab enable only one option like always take discount.
 Under prepayments tab give the payment terms and show available prepayments
during invoice entry.
 Under interest tab enable the Create interest invoices and give the account of
interest expenses distribution and minimum interest amount is 10
 Under payment request give the payment terms

Click on save and close.

Knowledge Sharing Session - 21
Journal Source:

1. It is a Journal component; it is used to identify the ORIGIN of the journal.

2. When we import data from legacy systems to GL, we require source names.
3. Importing journal Reference:
2. To import detailed information from summary journals we use this option
3. Require Journal approval:
4. This field is used to get the journal approval by higher management for different journal
sources
5. Import using key: This is used to define whether journals will be imported using source key
or not.

Creation:

 Go to set up and maintenance.

 Set up: Financials.
 Task: %Manage % journal %Source%.
 Select Manage journal source.
 Click on + to create source
 Give the details.
 Freeze journals - Yes.

Freeze Journals:

 Yes- You can’t change the journal

 No- You can change the journal
 Partial- You can change few things in the journal

Effective date Rule:

 Fail: Journal Import will reject transactions when the effective date is not a valid business
day. No posting takes place.
 Leave Alone: Journal import will accept all transactions regardless of the effective date.
 Roll Date: Journal Import will accept the transaction, but roll the effective date back to the
nearest valid business day within the same period. If there is no prior valid business day
within the same period, the effective date is rolled forward.
 Note: The Effective Date Rule field will not appear unless you have average balance
processing enabled for at least one ledger.
 Save and close

Knowledge Sharing Session - 22

Auto Post:

 We can post the journals automatically by specifying the some criteria in Auto post criteria
set.
 Criteria could be: combinations of ledger or ledger set, journal source, journal category,
balance type, and period.
 Once you define an Auto Post criteria set, run the Auto Post program to select and post any
journal batches that meet the criteria defined by the criteria set.
  You can also schedule the Auto Post program to run at specific times and submission
intervals.
 You can submit the Auto Post program or schedule Auto Post runs directly from the Auto
Post Criteria Sets window. Alternatively, you can use the Submit Request window.
1. Manage auto post criteria sets.
2. Create multiple journals for testing.
3. Run auto post.

1. Manage auto post criteria sets

 Go to set up and maintenance

 Set up: Financials
 Task: %Manage % auto% post%
 Select Manage auto post criteria set
 Click on + to create criteria set
 Give the details of auto post details
 Click on + to create criteria details
 Sources Payables, Receivables, Spreadsheet we have to define different priority wise
depends on client request except Manual Journals
 Process all criteria
 Yes: It will process all criteria
 No: It will bring the batches wise
 Save and close

2. Create Multiple Journals for testing

 Go to navigator
 Go to General accounting
 Select the Journals
 Go to Task icon
 Create journal
 Give the details and Save it
 Create the few more journals for testing purpose

3. Run Auto post

 Go to navigator
 Go to General accounting
 Select the Journals
 Go to Task icon
 Click on Run Auto post
 Auto post Criteria should be your criteria set
 Click on Submit
 Query the journal and check weather posted or not
Knowledge Sharing Session - 23
 Subsidiary Ledgers: Subsidiary ledgers help manage and store specific information regarding
each of the control accounts in your GL.
 Accounts Payable: Manage Suppliers and Payments
 Accounts Receivable: Manage Customers and Receipts.
 Inventory: Manage Item Prices and Movements.
 Fixed Assets: Manage Fixed Assets and Depreciation.
 Projects: Manage various projects with their costing and Billing.
 Cash Management: Manage cash and its reconciliation with bank.
 Payroll: Manage salaries and wages – Calculations and Payments.

General Ledger Syllabus - Process:

1. 4 c’s, Legal entity and primary ledger creation

2. Journals
3. Single journal
4. Batch journal
5. Reversal journal
6. Foreign currency journal
7. Auto copy journals
8. Mixed currency journals
9. Source and category
10. Account aliases
11. Accounting and reporting sequences
12. Reporting currencies/ ledger
13. Revaluation
14. Auto copy and Auto post
15. Allow dynamic inserts
16. Manage code combination
17. Translations
18. Ledger set
19. Data access set or define access set
20. Suspense account
21. Intercompany / intra company
22. Account inspector / Account query
23. Cross validation rules (CVR)
24. Security rules (SR)
25. Secondary ledger
26. Rapid implementation
27. Mass allocation
28. Recurring journals

What are the setup configuration required for Fixed Assets Fusion.

1. 1 FA-001 Manage System Controls

2. 2 FA-002 Manage Fiscal Years
3. 3 FA-003 Manage Asset Calendar
4. 4 FA-004 Manage Prorate Conventions
5. 5 FA-005 Manage Fixed Assets Flexfield Value Sets
 6. 6 FA-006 Manage Fixed Assets Flexfield Value Sets Values
7. 7 FA-007 Manage Fixed Assets Key Flexfields - Manage Structure
8. 8 FA-008 Manage Fixed Assets Key Flexfields -Manage Structure Instance
9. 9 FA-009 Manage Depreciation Method - SLM, WDV
10. 10 FA-010 Manage Asset Book
11. 11 FA-011 Manage Tax Book
12. 12 FA-012 Manage Asset Categories
13. 13 FA-013 Manage Asset Tax Book Categories
14. 14 FA-014 Manage Fixed Asset Lease Categories
15. 15 FA-015 Create Group Assets in Tax Book
16. 16 FA-016 Assign Group Assets In Tax Book Categories
17. 17 FA-017 Manage Asset Location
18. 18 FA-018 Manage Asset Keys
19. 19 FA-019 Manage Fixed Assets Descriptive Flexfields
20. 20 FA-020 Manage Fixed Asset Lookup
21. 21 ORA_FA_ALLOW_TAX_SOURCE_LINES
22. 22 ORA_FA_ALLOW_TAX_DIRECT_ADD
23. 23 ORA_FA_ALLOW_GROUP
24. 24 ORA_FA_ALLOW_LEASE
25. 25 ORA_FA_ALLOW_REVAL
26. 26 FA_MASS_ADD_PREPARE_RULES
27. 27 ORA_FA_ALLOW_CAP_THRESHOLD
28. 28 FA-021 Manage Data Access Set
29. 29 PO-001 Manage Mapping Set
30. 30 PO-002 Manage CatLog
31. 31 PO-003 Manage Transaction Account Definitions: Purchasing

1. What are the data conversion strategies?

 Data conversion strategies involve transferring data from a legacy system to Oracle Fusion.
Common strategies:
 Manual Entry=>For small datasets.
 FBDI => Upload data using predefined templates.
 ADFDI =>> For interactive uploads.
 Direct SQL/Data Loader=> For technical users.
 Third-Party Tools=>> Tools like Informatica, Boomi, or custom scripts.

2. What are the data conversion strategies for the open invoices and partially paid invoices?

 Use FBDI templates to load open and partially paid invoices.

 Load=>>>
 Open invoices as standard invoices with open balances.
 Partially paid invoices with an adjustment for the paid amount.
 Ensure correct mapping of terms, due dates, and payments from legacy systems.
3. Is it possible to make the payment whenever the invoice currency and ledger currency are
different?

 Yes, payment in a different currency by enabling cross-currency payments=>>

 Define exchange rates in the Currency Rates Manager.
 Configure currency conversion rules.
 Payments are processed in the currency of the invoice or the payment currency with
conversion.

4.What are the third-party control accounts?

Third-party control accounts are used to track transactions with third parties (e.g., suppliers,
customers) in the General Ledger:

 Accounts Payable Control Account (for supplier transactions).

 Accounts Receivable Control Account (for customer transactions). These accounts
automatically reconcile with subledgers.

5. Is it possible to modify the journals that are coming from subledgers?

A.No, journals imported from subledgers are typically not modifiable.

Adjustments can be made in the originating subledger.

6. Can you briefly explain on FRS and Smart View?

 FRS => A web-based tool for creating financial reports directly from Oracle Fusion.
 Smart View=>> An Excel-based tool for retrieving, analyzing, and reporting data from Oracle
Fusion using Oracle Analytics.
 BPM Workflow in Oracle Fusion=> Automates and streamlines approval processes (e.g.,
invoice approvals, expense approvals).

Configured via Oracle BPM Worklist.

 Key elements=>
 Participants, rules, and conditions.
 Approvals based on roles or hierarchies.

8.Can you briefly explain the auto-lock box?

 Auto Lockbox automates the receipt and application of customer payments=>

 Payments are imported from bank files.
 Matched to invoices automatically or manually.
 Improves efficiency in cash application.

9.Can you explain the process of loading the AP open invoices from the legacy system?

 Use the Payables Open Invoice FBDI template.

 Populate data for invoices and distributions.
 Load the data via File Import and Export.
 Run the Load Interface File for Import process.
 Validate using the Invoice Validation Report.
10.How did you reconcile the opening invoices data? What are the programs to run?

 Run the Invoice Aging Report to verify open balances.

 Compare totals with legacy system reports.
For discrepancies:
 Use the Invoice Validation Process and corrections.

11. Can you explain withholding tax?

Withholding tax is deducted at the source=>>

 Set up withholding tax codes in Oracle Fusion.

 Automatically calculates and deducts withholding tax during invoice creation or payment.