Oracle Fusion Financials Implementation Steps: Setup Sequence

Oracle Fusion Cloud Financials is configured through Setup and Maintenance. The screens will let you do the steps in almost any order. The result will not work in any order. Many steps depend on earlier ones, and some early decisions, such as the chart of accounts structure, are very hard to reverse once transactions exist.

This guide sets out the sequence Egisedge follows on Fusion Financials projects. It is written for consultants running the build and for finance leaders who want to know what should be decided when. For detailed field-level guidance, use the Implement guides in the Oracle Fusion Cloud Financials documentation.

Before you touch the system: design decisions

Configuration is the easy part. The hard part is agreeing the design. Settle these points in workshops and record them in a signed design document before anyone opens Setup and Maintenance.

A common mistake is to design the chart of accounts around current reports. Design it around the questions management will ask for the next several years, and keep detail such as customer or employee in subledgers, not in segments.

The Fusion Financials setup sequence

1. Create the implementation project

In Setup and Maintenance, create an implementation project for the Financials offering. Opt in to the functional areas you are implementing (for example General Ledger, Payables, Receivables, Cash Management, Assets, Expenses) and the features within them. Only enabled features appear as tasks, so this step shapes everything after it.

2. Define the enterprise, legal jurisdictions and legal entities

Set up the enterprise, then the legal jurisdictions and legal authorities that apply to you. Create each legal entity with its registrations. In India this includes the entity details your GST setup will depend on later.

3. Build the chart of accounts

This is the most important step in the project. Work in this order:

1. Create value sets for each segment.
2. Define the chart of accounts structure and its segments, and assign segment labels (balancing, cost centre, natural account).
3. Create the structure instance and deploy the flexfield.
4. Load value set values. Large value lists are best loaded from a file rather than entered by hand.
5. Build account hierarchies (trees) for reporting and allocations, and publish them.

Test a few account combinations with cross-validation rules before moving on.

4. Define the accounting calendar and currencies

Create the accounting calendar with its period type and any adjusting periods. Confirm the currencies you need are enabled, and set up conversion rate types.

5. Create the ledgers

A primary ledger combines four things: chart of accounts, calendar, currency and accounting method. Create it, then add secondary ledgers or reporting currencies only if there is a clear statutory or management need. Every extra ledger adds reconciliation work each month.

6. Complete ledger options and assign legal entities

Assign legal entities and their balancing segment values to the ledger. Complete ledger options such as retained earnings account, suspense and rounding accounts, and journal approval if required. Then submit the accounting configuration.

7. Define business units

Create business units and assign business functions (for example Payables Invoicing, Billing and Revenue Management, Procurement). Link each business unit to its primary ledger and default legal entity. Decide whether you use shared service arrangements where one business unit processes for others.

8. Configure security and data access

Create data access sets for ledgers and assign job roles with the correct data scope. Review segregation of duties early. Security left to the last month causes UAT delays because testers cannot see their data.

9. Set up tax

Configure tax regimes, taxes, tax statuses, rates, jurisdictions and rules. For India, set up GST with first-party registrations for each GSTIN and third-party registrations for suppliers and customers. Test tax calculation on sample invoices before subledger testing starts.

10. Configure the subledgers

Set up Payables, Receivables, Cash Management, Fixed Assets and Expenses. Typical items include payment terms, invoice options, receipt methods, asset books and categories, expense templates and policies. Review subledger accounting rules and only customise them if the standard rules do not meet a clear requirement.

11. Banks, branches and accounts

Create banks, branches and internal bank accounts, and link them to legal entities and business units. Set up payment methods and payment process profiles, then bank statement formats and reconciliation rules in Cash Management.

12. Load masters and opening balances, then reconcile

Load suppliers, customers, assets and opening balances, usually with FBDI templates. Reconcile record counts and balances against the legacy system. See our guide on validating FBDI data migration and the FBDI validation playbook.

Stage checklist

Use this as a quick gate before moving to the next stage.

• Design document signed, including chart of accounts and ledger design
• Implementation project created with the correct offerings and features
• Chart of accounts deployed; hierarchies published; cross-validation rules tested
• Primary ledger accounting configuration submitted without errors
• Business units created with business functions and ledger links
• Data access sets and job roles assigned to test users
• Tax calculation tested on sample purchase and sales invoices
• Subledger setups complete; sample transactions account correctly
• Bank accounts and payment process profiles tested with a test payment file
• Opening balances loaded and trial balance matches the legacy system

Moving configuration between environments

Once the design is stable in the development pod, use Setup and Maintenance export and import (configuration packages) to move setup data to test and production. Keep a log of every manual step that the package does not cover. Rebuilding production by hand from memory is how differences between environments creep in.

Common pitfalls

• Too many segments. Every segment adds data entry and validation effort. Keep only what drives reporting or control.
• Late tax design. Tax affects Payables, Receivables and Procurement. Leaving it to the end forces retesting.
• Security as an afterthought. Build test users with real roles early.
• Ignoring the quarterly update cycle. Fusion is updated every quarter. Build a regression pack during the project so it can be reused after go-live. See how to test Oracle Fusion quarterly updates.
• Manual data fixes after load. Fix data at the source and reload, so the process is repeatable for mock loads and cutover.

Building the team's skills

Consultants new to Fusion can use Oracle's Financials bite-size learning to get familiar with each module. Walk through the Implement guides with the setup sequence above in hand; they make more sense in order.

How Egisedge helps

Egisedge Technologies is an Oracle Partner delivering Oracle Fusion Cloud ERP, HCM and SCM implementations. Our directors bring long Oracle finance backgrounds: Anshuman Yadav has 20+ years in Oracle EBS and Fusion and finance transformation, and Nikhil Yadav has 16+ years in Oracle Finance, SCM and OTM. We have delivered Oracle-related finance work such as billing integrations with Oracle Fusion Receivables for a telecom operator in Ghana and an aviation services company in Nigeria, delivered as part of an implementation partner's team, and we follow the setup sequence in our Fusion Financials setup playbook. We work from offices in India, with teams covering GCC, UK/Europe, US and Australia/NZ working hours.

Planning a Fusion Financials rollout or reviewing an existing design? Email info@egisedge.com or book a demo with our team.

Frequently asked questions