Station 7 of 10
Subledger accounting and the close in Oracle Fusion
What you leave this station with
Understanding how a journal is built by rule rather than by code, running a correct close order, and separating revaluation from translation from consolidation.
This is the most important station on the path, and the idea that separates people who know this product from people who use it.
The question it answers is: who wrote this journal? In smaller systems the answer is “the program, that is how it was written”. Here it is something else entirely: a written rule the customer owns and can change without a single line of code.
What subledger accounting is
Between the transaction — an invoice, a receipt, a shipment — and the journal in the general ledger sits a separate layer that reads the transaction and builds the journal.
| Component | Its job |
|---|---|
| Accounting method | The whole package, attached to a ledger |
| Journal entry rule set | Which event produces which journal |
| Journal line rule | Debit or credit, and under what condition |
| Account rule | Where each segment of the account combination comes from |
| Supporting references | Analytical data stored with the journal for later reporting |
What that means in practice shows in one example: a single purchase invoice, in a company with a local statutory ledger and a secondary ledger on group standards. The invoice is one; the accounting treatment differs between the ledgers; and both journals are generated from the same transaction by two different rules. This is what the market calls multi-GAAP, and it is why listed groups buy this tier.
The methodological consequence to carry away: when you are asked to change the account a value lands in, the right answer is an account rule, not a code change and not a monthly adjusting journal. Handle it with a manual journal every month and you have created a permanent job for somebody correcting a machine.
Draft before final
The create accounting process runs in two modes: draft, which is visible and not posted, and final, which posts.
Draft is the only serious testing instrument in this product. Change a rule and run it straight to final in a real environment and you correct with reversals. Run it in draft and you read the journal that would have been written, and then decide.
Make it a habit: every rule change is tested on a sample in draft, and its result compared against a journal you wrote by hand first. The gap between the two is what you had not understood.
The close order
The close here is not a button. It is an order, and breaking it means closing a month and reopening it.
| # | Step | Why here |
|---|---|---|
| 1 | Stop transactions in the subledgers | Nothing closes while it still moves |
| 2 | Clear the exceptions: held invoices, rejected interface lines, unapplied receipts | Each one is a number missing from the statements |
| 3 | Run create accounting in final for every subledger | Journals do not reach the ledger before this |
| 4 | Reconciliations: accrual, bank, intercompany | Differences are found here rather than after the close |
| 5 | Foreign currency revaluation | Before the period closes, after every journal |
| 6 | Close the subledger periods, then the ledger period | In that order, never the reverse |
| 7 | Translation, then consolidation | After the close, not before |
Step two is what actually lengthens a close. Which is why the previous three stations were written the way they were: run the holds, the interface and the receipts daily and you close in two days; defer them and you close in twelve.
Three processes that always get conflated
| Process | What it does | When |
|---|---|---|
| Revaluation | Adjusts foreign currency balances to the closing rate inside the same ledger | Monthly, before the close |
| Translation | Restates whole ledger balances into another currency for reporting | After the close |
| Consolidation | Combines group ledgers and eliminates intercompany | After everything is translated into one currency |
The difference between the first two is the commonest interview question in this field, and the most commonly failed.
Revaluation creates a journal, because an exchange difference on an open balance is a real gain or loss. Translation creates no journal in the source ledger, because it is a presentation of the same balances in another currency. Conflate them and you end up with translation differences booked as profit — a guaranteed audit note.
This capability in particular is what is being paid for at this tier, and its published price is in the Oracle Fusion Cloud ERP guide.
The three reporting layers
| Layer | For whom | What it suits |
|---|---|---|
| Balance reporting on the cube | Finance | Financial statements and interactive balance analysis |
| Operational analytics | Management | Dashboards and indicators over live data |
| Document reporting | Everybody | A printed document in a fixed format: invoice, cheque, return |
Picking the wrong layer is the commonest cause of a slow report in these systems. Build a financial statement on the operational analytics layer and you aggregate millions of rows on every run, while the balances are already computed and stored in the cube.
The rule: balances from the cube, transactions from analytics, documents from the document engine.
What you actually do in this station
- Trace one invoice from transaction to journal, and name the rule that determined each segment.
- Run create accounting in draft after a rule change, and compare it against a journal you wrote by hand.
- Write a close checklist with the seven steps, an owner per step, and a due time.
- Run a revaluation on a foreign currency balance and read the journal it produces.
- Explain on paper how an intercompany sale between two entities is eliminated on consolidation.
- Revisit the finance cycle for the general principle.
The three commonest mistakes
One: fixing an accounting error with a monthly manual journal. The cure is a rule corrected once, not manual work repeated a hundred times.
Two: closing the ledger before the subledgers. Then finding journals that never arrived, and reopening the period — an event that is logged and asked about.
Three: conflating revaluation and translation. Translation differences booked as profit.
The acceptance test for this station
- Explain how one invoice produces two different journals in two ledgers.
- Name the components of the subledger accounting layer and each one’s job.
- Show your close checklist in order, and explain why subledgers precede the ledger.
- Distinguish revaluation, translation and consolidation in one sentence each, and say which creates a journal.
- Pick the right layer for three reports: an income statement, a held-invoice listing, and a printed invoice.
What comes next
You have the engine. The next station puts it in front of the state: tax and e-invoicing — ZATCA and the UAE, and the separately priced line the demo never mentions.