Summary of "Fusion Cloud:- Oracle Multiperiod Accounting"

Purpose / concept

Multi-Period Accounting (MPA) lets you apportion a one-time expense across multiple reporting periods (for example, a 1‑year software license) so expense recognition is spread over time rather than recognized in full at purchase.
The Oracle Fusion implementation is presented as simpler than Oracle EBS for the default prorating scenario.

Prorate by number of periods (default, no SLA customization required) — covered in this tutorial.
Prorate by number of days in each period (accounts for months with 28/30/31 days) — requires custom SLA rules/profile and is not covered in detail here.

User must have an AP role such as Accounts Payable Manager, Specialist, or Supervisor.
Business unit must be assigned to the role/user.
The invoice must be created and validated before running MPA programs.

Create AP invoice
- Enter supplier, invoice number/date, header amount and invoice line(s).
- Set the charge (expense) distribution and the accrual/deferred expense account.
Enter Multi-Period Accounting details on the invoice line
- Show multi-period accounting columns, enter start date, end date, and accrual (deferred) account.
Save and validate the invoice (validation is required).
Run Create Accounting
- Posts initial accounting in final mode and transfers to GL if requested.
Run Create Multi-Period Accounting program
- Also ensure the Create Multi-Period Accounting Execution Report runs.
- Parameters are similar to Create Accounting: ledger, subledger (Payables), period, final accounting flag, post to GL option.
- In production, schedule this monthly (month-end) to generate recurring monthly recognition entries.
Review accounting output
- Use View Accounting on the invoice or check the program output/report to see MPA journal lines.

Example invoice total: 16,350 (charge 15,000 + tax 1,350).
Initial accounting on invoice:
- Deferred (accrued) expense debited; liability credited (tax lines also posted according to tax setup).
After running MPA:
- Monthly journals move amounts from Accrued/Deferred Expense to the Expense account.
- Charge apportionment: 15,000 / 12 = 1,250 per month to expense.
- Tax apportionment: 1,350 / 12 = 112.50 per month (may be split among tax components, e.g., 81.25 + 31.25).
Tax treatment notes:
- Non-recoverable (non-recordable) tax is allocated to the same expense/deferred accounts and gets apportioned.
- Recordable/recoverable tax is typically handled differently (recovery via AR/offsets); MPA apportioning may not include such taxes.

Run Create Multi-Period Accounting monthly or as part of month‑end close to produce each period’s recognition journals.
All MPA entries for an invoice can be viewed via the invoice’s View Accounting.

Observed error message:

“journal entry was not created because no data could be formed… multi-period transaction data must be available in the subledger transaction objects until the last period journal entry has been accounted.”
Oracle confirmed this is caused by an internal database bug. Recommended workaround:
- Apply the steps in Oracle Note ID 2581275.1 (set a specific profile option value, then rerun MPA and AP accounting).
- After applying the workaround, the program should complete successfully.

Program names:
- Create Multi-Period Accounting
- Create Multi-Period Accounting Execution Report
Oracle Support note: 2581275.1 (workaround for MPA bug)

YouTube channel presenter / Oracle Financials instructor (unnamed; host of the tutorial).
Oracle Support note ID 2581275.1 (referenced for the bug/workaround).