Oracle GL 2026 (1Z0-1054-26) study materials
Oracle GL 2026 (1Z0-1054-26) study resources

Rent Allocation Skips a Cost Center and Leaves a Rounding Residual

Oracle GL 2026 (1Z0-1054-26) · Put your knowledge to work in context.

All case studies

Rent Allocation Skips a Cost Center and Leaves a Rounding Residual

Arboria Group charges 120,000 EUR of shared facility rent each month from cost center 9900 to three operating cost centers: 1100, 1200, and 1300. The allocation rule uses cost center 9900 as the source, a statistical account 9910 (Headcount) as the basis, and each target cost center as the target, with the rent liability account as the offset. Headcount for the period is 60 in 1100, 30 in 1200, and 10 in 1300, but the 1300 statistical balance was never loaded because the HR feed failed for that department. The allocation was run and posted, producing 80,000 to 1100 and 40,000 to 1200, nothing to 1300, and a 0.01 residual. The department manager for 1300 is disputing her zero rent charge, and the controller is asking why the total allocated still equals 120,000 when one cost center was skipped. The team also wants a repeatable answer for the 0.01.

1. Explain why cost center 1300 received nothing and why 1100 and 1200 absorbed the full 120,000. What is the correct correction path?

Read the worked answer

The allocation computes each target's share from its basis as a percentage of total basis. With 1300 at zero, total basis is 90 rather than 100, so 1100 gets 60/90 and 1200 gets 30/90: the full source amount is still distributed, but across two targets instead of three. Nothing is left behind in 9900, which is why the controller sees a balanced 120,000 that is nevertheless wrong. The correction is not a manual journal to 1300. Reverse the allocation journal that was generated for the period, or delete it if it is still unposted, load the missing statistical balance for 1300, and rerun the allocation. Then verify the percentages and post the new journal. A manual top-up would fix one month but would not stop the same error next period, and it would break the audit trail from rule to journal. Also check whether the allocation batch can be set to fail or warn when a target has zero basis, so the HR feed failure is caught before posting rather than after a manager complaint.

2. How should the 0.01 rounding residual be handled, and how do you make the treatment repeatable month after month?

Read the worked answer

Allocation percentages rarely divide evenly, so the generated lines will not sum exactly to the source. The rule should specify where the residual lands, typically through a rounding option that assigns the difference to a designated target or to the offset line, so that the journal balances and the source account clears to zero. Review the allocation rule's rounding setting and confirm which line absorbs the difference; if the setting is not granular enough, define the convention explicitly, for example the largest target absorbs the residual, and document it in the allocation rule description. Do not post a separate 0.01 journal each month: it multiplies entries, obscures the rule-to-journal link, and invites questions at close. After changing rounding, run the allocation in a test period and reconcile source, target, and offset to the cent before promoting the rule. The test is that 9900 nets to zero and the target total equals 120,000 exactly.

3. The controller asks whether a recurring journal would be simpler than the allocation for this rent. What do you advise?

Read the worked answer

It depends on whether the split is stable. A recurring journal is right when the proportions are fixed by contract and do not change with headcount: it is simpler, faster, and easier to audit because the amounts are explicit. An allocation is right when the basis moves month to month, as it does here, because it reads the current statistical balances and computes the split automatically. Given headcount of 60/30/10 and known volatility from hiring, an allocation is the better control, provided the statistical feed is monitored and the zero-basis condition is trapped. A hybrid is common and defensible: use a recurring journal for a genuinely fixed portion of the rent and an allocation for the variable remainder, but do not run both against the same source account without clear documentation, or the source will be double-charged. Decide based on the lease terms, then write the rationale into the rule description so the next accountant does not switch methods mid-year.