Finance and procure-to-pay

Coding That Stays Right: Controls in a Housing Chart of Accounts

Stop miscoding at the point of entry. How related values, defaults and a simple change process keep a housing chart of accounts clean in Oracle Fusion.

November 8, 2026
4 min read

A new chart of accounts starts clean.

It stays clean when the system offers each user only the codes that fit. In Oracle Fusion that is done with related values, sensible defaults and a short change process.

Offer only what fits

Each choice narrows the next one.

  • Pick a company, and only that company's cost centres appear.
  • Pick a cost centre, and only its estates, blocks and properties appear.
  • The cost centre sets the tenure, so the user never chooses it.

A commercial subsidiary's team sees its own cost centres. A shared ownership block always carries the shared ownership tenure. The same rules check postings from interfaces, so feeder systems are held to the same standard as people.

Defaults for the common case

Every dimension has a "not analysed" value. Each colleague has a default expense code, and only the account changes by expense type. Most lines need two or three choices.

A change process people follow

New cost centres and accounts arrive every month. Agree one route for them:

  1. The finance lead approves the new code.
  2. The configuration record and master list are updated.
  3. The code is loaded with its related values and hierarchy parent.
  4. Hierarchies are republished and reporting cubes refreshed.
  5. Finance One picks up the code in its next daily feed.

Check after every data load

Large loads sometimes need controls relaxed for a short time. Build the step that switches them back on into the load plan, and check it afterwards.

Stop the journals before they happen

Bring a month of correcting journals and we will show you which rules would have stopped them.

Clean at go-live, and clean a year later.