Oracle Fusion Financials Setup, Ledger to Business Units

A practical walkthrough of how an Oracle Fusion Cloud Financials implementation is set up, in the order we follow on projects.

We start in the Setup and Maintenance work area. We choose the Financials offering and opt in to the functional areas and features you need. Then we build the enterprise structure: legal entities, the chart of accounts, the accounting calendar, currency and accounting method, the primary ledger and business units. We show where the rapid implementation spreadsheet saves time, and how to set up Payables and Receivables basics on top of the ledger. We close with how configuration is exported and imported between environments.

This video uses a demo environment and demo data. For the full reference, see Oracle's official Fusion Financials documentation at docs.oracle.com.

Presented by the Egisedge Oracle Finance team.
Learn more: https://egisedge.com

#OracleFusion #OracleFinancials #OracleERP

Transcript

[Scene: Presenter on camera, Egisedge branded background. Lower third: "Egisedge Oracle Finance team".]

PRESENTER: In this video we walk through how an Oracle Fusion Cloud Financials implementation is set up. We follow the same order we use on projects. We use a demo environment and demo data throughout.

[Scene: Screen recording. Sign in to a Fusion demo pod. Open the Navigator and go to My Enterprise, then Setup and Maintenance.]

PRESENTER: Everything starts in the Setup and Maintenance work area. This is where you choose what to implement and where you find every setup task.

[Scene: Chapter card, "Offering, functional areas and features".]

PRESENTER: First, pick the offering. For finance, that is Financials. An offering is broken into functional areas, such as General Ledger, Payables, Receivables and Cash Management. Opt in only to the areas you are implementing now. You can add more later.

[Scene: Show the opt-in page. Highlight the checkboxes for functional areas. Then open the features list for one area.]

PRESENTER: Inside each area there are features. Some are optional and need an explicit opt-in. Read the description before you tick a feature. A feature switched on by mistake can change screens and processes your users see.

[Scene: Chapter card, "Legal entities and enterprise structure". Simple diagram: Legal Entity, Ledger, Business Unit, with arrows.]

PRESENTER: Next, the enterprise structure. This is the design decision that is hardest to change later, so settle it on paper first. Who are your legal entities? Which ledgers do they post to? Which business units run transactions? Get agreement from finance leadership before you touch the system.

[Scene: Screen recording. Open the task list for enterprise structures. Show where legal entities, legal addresses and jurisdictions are created.]

PRESENTER: Create the legal entities with their registered addresses and jurisdictions. These records drive tax and statutory reporting, so check them with your tax team.

[Scene: Chapter card, "Chart of accounts, calendar, currency".]

PRESENTER: A ledger needs four things. People call them the four Cs. Chart of accounts. Calendar. Currency. And the accounting method, which is often called the convention.

[Scene: Show the chart of accounts structure and value sets. Highlight segments such as company, cost centre, account and intercompany.]

PRESENTER: Design the chart of accounts for reporting, not for today's spreadsheet. Keep segments few and meaningful. Add an intercompany segment if you trade between entities. Decide your account hierarchies early, because reporting depends on them.

[Scene: Show the accounting calendar setup, with twelve monthly periods and an adjusting period.]

PRESENTER: Set up the accounting calendar to match your financial year. In India that usually means April to March. Add an adjusting period if your auditors expect one.

[Scene: Chapter card, "Primary ledger and business units".]

PRESENTER: Now create the primary ledger. Attach the chart of accounts, the calendar, the currency and the accounting method. Then assign legal entities to the ledger.

[Scene: Open the rapid implementation spreadsheet template for General Ledger. Show the tabs for chart of accounts, hierarchies, ledger, legal entities and business units.]

PRESENTER: For a new implementation, the rapid implementation spreadsheet saves a lot of clicking. You fill in the chart of accounts, hierarchies, ledger, legal entities and business units in one workbook, then upload it. We still review every generated record on screen afterwards.

[Scene: Show business unit creation and the assignment of business functions to the business unit.]

PRESENTER: Business units are where transactions happen. Assign the business functions each unit performs, such as payables invoicing or billing, and link it to the right ledger.

[Scene: Chapter card, "Payables and Receivables basics".]

PRESENTER: With the ledger in place, you can set up the subledgers. For Payables, that means options such as invoice and payment settings, payment terms, and payment methods. For Receivables, it means transaction types, receipt methods and customer defaults. Subledger accounting then turns these transactions into journal entries in your ledger.

[Scene: Quick screen tour of the Payables and Receivables setup task lists. Do not deep-dive.]

PRESENTER: Test with a small set of real scenarios. One domestic invoice. One foreign-currency invoice. One customer receipt. Check the journal entries each one creates.

[Scene: Chapter card, "Moving configuration between environments".]

PRESENTER: Once setup is signed off in test, move it to production in a controlled way. Setup and Maintenance lets you export setup data as a configuration package and import it into another environment. Keep a record of what was moved and when.

[Scene: Show the export and import configuration pages at a high level.]

[Scene: Chapter card, "Recap". Presenter back on camera.]

PRESENTER: To recap. Choose the offering and opt in carefully. Design the enterprise structure on paper first. Build the four Cs and the ledger. Set up business units and subledgers. Test with real scenarios. Then move configuration with a package. For the full reference, use Oracle's Fusion Financials documentation on docs dot oracle dot com. If you want help with your own setup, visit egisedge dot com.

[Scene: End card with egisedge.com and a link to the next video, "Quarterly update testing in 6 steps".]