Automating Lease Accounting Compliance in Oracle EBS for BFSI & Manufacturing

In short: Oracle E-Business Suite has no native Ind AS 116 lease-accounting engine, which is a real gap for BFSI enterprises with large branch networks and manufacturers with multiple plant, warehouse and equipment leases — both lease-heavy sectors where getting this wrong at scale is expensive. There are three honest paths to compliance on an EBS estate, and which one fits depends on lease volume and how much of your Financials footprint you are prepared to move.

Why BFSI and manufacturing feel this gap more than most sectors

Ind AS 116 compliance is a volume problem before it is a technical problem. A bank or NBFC with a branch network can easily be tracking several hundred to several thousand premises leases, each with its own escalation clauses, renewal options and sometimes co-located ATM or signage sub-leases. A manufacturer with multiple plants typically carries a mix of land, building, equipment and vehicle leases, often with different lease terms negotiated at different times by different regional teams. Both sectors hit the same wall: Ind AS 116 requires every one of those leases to be individually assessed, discounted, and tracked for remeasurement triggers, and Oracle EBS has no built-in module that does this the way Oracle Fusion Cloud's lease-accounting capability does.

Option 1 — a dedicated third-party lease-accounting tool integrated with EBS

Purpose-built lease-accounting software calculates the ROU asset and liability, handles remeasurement, and produces the required disclosure schedules, then posts summary or detailed journal entries into EBS General Ledger through a standard interface. This is generally the most scalable option for genuinely high lease volumes, because the tool is built for exactly this calculation, but it introduces a second system of record for leases that has to be kept reconciled with the lease register and with EBS.

Option 2 — a controlled spreadsheet-and-journal-upload process

For a lease portfolio in the low hundreds rather than thousands, a rigorously controlled spreadsheet model — with version control, a documented discount-rate methodology, and a formal review-and-approval step before each journal upload to EBS GL — can be a legitimate, audit-defensible approach. The risk is entirely in the discipline: an uncontrolled spreadsheet with ad hoc formula changes is exactly the failure mode Ind AS 116 audits flag most often. This option works when the process around it is treated as seriously as the calculation itself.

Option 3 — run lease accounting on Fusion Cloud while EBS stays operational

It is possible to run Oracle Fusion Cloud's lease-accounting module as a targeted addition alongside an EBS estate that otherwise stays exactly where it is — the lease-accounting result posts into EBS GL via integration, without requiring a full Financials migration. This gets access to Fusion's native ROU/liability calculation and disclosure reporting without forcing a broader EBS-to-Fusion decision that the business may not be ready to make yet, though it does mean operating and integrating two platforms rather than one.

Choosing between them

Lease volume is the main decision driver: under roughly a few hundred leases with strong internal financial-control discipline, a well-governed spreadsheet process can work. Above that, the reconciliation burden of manually tracking remeasurement triggers across hundreds of individual leases usually justifies either a dedicated lease-accounting tool or the targeted Fusion Cloud addition. The second factor is where the business already sits on its Fusion migration roadmap — if a broader EBS-to-Fusion move is already planned within a year or two, bringing lease accounting onto Fusion first can be a sensible first step rather than investing in a third-party tool that becomes redundant once the wider migration happens.

What we look at in an assessment

Before recommending an approach, the honest starting point is a lease inventory — how many leases, what type (premises, equipment, vehicles), how complex the escalation and renewal terms are, and how far out the broader Fusion migration conversation already is. That inventory, not a generic recommendation, is what determines whether a spreadsheet process, a third-party tool, or a targeted Fusion addition is the right call for a specific BFSI or manufacturing estate.

Written & reviewed by

Rajkumar Awasthi

Vice President — Oracle Delivery, ROSTAN Technologies

Rajkumar Awasthi leads Oracle delivery at ROSTAN Technologies, overseeing Oracle ERP implementation, Oracle E-Business Suite support and EBS-to-Fusion Cloud migration engagements for enterprise customers across India and the GCC. More from Rajkumar →