Introduction
Every
inventory-carrying organization has to answer a deceptively simple accounting
question: when do we know how much inventory we have, and what it cost us?
There are
two ways to answer it — perpetual and periodic inventory accounting. This post
covers what the two methods mean, how GAAP and IFRS treat them, the practical
trade-offs, and then goes deep into how Oracle Fusion Cloud Cost Accounting is
configured around this — including a point many consultants still get wrong:
Fusion is not perpetual-only. It now supports a native Periodic Average Cost
Method alongside its perpetual costing methods.
1. Perpetual vs. Periodic — The Accounting
Definition
Perpetual
inventory system: Every purchase, issue, transfer, and sale updates the inventory
asset account and, where applicable, Cost of Goods Sold (COGS) in real time,
transaction by transaction. The general ledger inventory balance is always
current.
Periodic
inventory system: Purchases are accumulated in a temporary “Purchases” account
during the period. Inventory on hand is not tracked transaction-by-transaction;
instead, a physical count is taken at period end, and COGS is derived
arithmetically:
Beginning
Inventory + Purchases − Ending Inventory (per physical count) = COGS
What
GAAP and IFRS say, in brief
Neither
framework mandates one system over the other — both focus on measurement, not
on how a company arrives at the numbers operationally.
• Under US
GAAP, guidance sits in ASC Topic 330, Inventory; GAAP does not mandate a
required inventory system — the periodic system simply uses a Purchases account
to satisfy recognition requirements, while the perpetual system updates the
Merchandise Inventory account automatically at each purchase.
• Under IFRS,
the equivalent guidance is International Accounting Standard (IAS) 2,
Inventories, which is procedurally neutral in the same way.
• Both
converge on the core measurement rule: inventory must be measured at the lower
of cost and net realizable value (NRV) under IFRS, or lower of cost and market
(LCM) under GAAP, so it's never carried above what it can realistically be sold
or used for. The one notable divergence relevant to costing method choice: LIFO
is permitted under US GAAP but prohibited under IFRS.
2. Oracle Fusion Cloud — Cost Accounting Setup
Fusion Cost
Accounting gives you both a perpetual and a periodic path, and the choice is
made at the cost book level, not at the application level. A given cost
organization can have one cost book running perpetual (Standard, Perpetual
Average, or Actual/FIFO) and another cost book, for the same items, same
transactions — running the Periodic Average Cost method for statutory or
group-reporting purposes. That's the key architectural fact to internalize
before you configure anything.
2.1
Core Fusion Cost Accounting setup sequence (perpetual and periodic share this
backbone)
1. Cost
Organizations and Cost Books : define one or more Cost Organizations
(mapped to inventory organizations) and attach Cost Books to them. A single
cost organization can report through multiple cost books (e.g., one book on
Perpetual Average for management reporting, a second book on Periodic Average
for local statutory reporting).
• Task: Manage Cost
Organizations
• Task: Manage Cost
Books
2. Cost
Organization Relationships
Map inventory organizations to the cost
organization structure.
• Task: Manage
Accounting Cost Organization Relationships
•
3. Valuation
Structure
Configure at the cost organization/book
level: cost element granularity, valuation unit (item or category), and the
level at which cost profiles are assigned.
• Task: Manage
Valuation Structures
•
4. Cost
Profiles
Assign a Costing Method per item, item
category, or cost organization default. For a perpetual book this is Standard,
Perpetual Average, or Actual (FIFO). For a periodic book, the cost book itself
must be enabled for the Periodic Average Cost method — unlike the other cost
methods, the cost processor only calculates and uses periodic average cost for
a book once that book is specifically enabled for it.
• Task: Cost
Profiles
5. Cost
Component Mappings
Map incoming cost elements (material,
overhead, freight, landed cost) to internal cost elements; a default cost
component mapping can be configured so that initial receipts with no cost are
processed at a designated zero-cost element rather than erroring out.
• Task: Manage
Cost Component Mappings
6. Cost
Accounting Distributions
Run Create Cost Accounting Distributions,
which maps incoming cost components to cost elements based on the mappings
above and calculates costs for pre-processed transactions, with parallel
processing across subprocesses for throughput.
7. Cost
Reports Processor
Generates inventory valuation, item cost, and
gross margin data that feeds OTBI and BI Publisher reports, at the inventory
organization, sub-inventory, locator, project, task, and country-of-origin
level.
2.2
How the Periodic Average Cost method actually works
This is
where Fusion's periodic engine differs meaningfully from perpetual costing, and
it's worth walking through precisely because it changes how you explain
variances to a client.
The periodic
average cost of an item is calculated for a given cost organization, cost book,
and valuation unit combination, for a specific period, using this formula:
Periodic Average Cost = [(prior period
average cost × prior period ending balance) + SUM(transaction cost ×
transaction quantity) + overheads + adjustments] / (prior period ending balance
+ transaction quantity for the period)
Only
cost-owned transactions feed this calculation. Cost-owned transactions include
purchase order receipts, adjustments, WIP completions/returns, resource or
overhead transactions, RMAs referenced to the original sales order, returns to
vendor, and miscellaneous receipts/issues with a cost attached. Cost-derived
transactions — miscellaneous transactions without cost, negative material
issues, component issues to and returns from WIP, direct transfers within the
same valuation unit, and similar movements — are costed using the periodic
average cost once it's calculated, not the other way around.
A practical
detail that matters for reconciliation: within the period, all receipts are
processed at their actual receipt cost, but issues are costed using the single
periodic average cost — a composite of all cost-owned transactions for that
period. And the periodic average cost carries forward from period to period
even when on-hand quantity drops to zero, so an item never loses its cost basis
between periods.
2.3
The periodic period-close cycle
Periodic
Average Costing runs on its own period lifecycle inside Cost Accounting,
distinct from a perpetual book:
• While the
period is Open, you can run Create Cost Accounting Distributions repeatedly.
For a periodic-enabled book, these distributions are provisional, not final —
you can review them on the Review Cost Accounting Distributions page, correct
them with the Manage Periodic Average Cost Adjustments task, revise resource
rates or overhead rules, and rerun distributions as many times as needed.
• You then set
the period to Pending Close, which stops new transactions from flowing into
costing and triggers a final periodic average cost calculation along with
automatic period validations — unprocessed transactions, adjustments,
over/under absorption, and processing errors all get flagged here for
correction before you commit.
• Only once
the period is Closed do the accounting distributions freeze. The Create Cost
Accounting Events process runs automatically, after which you run Create
Accounting in Final mode to post to the General Ledger, and finally set the
period to Permanently Closed.
This
provisional-until-closed behavior is the single biggest operational difference
from perpetual costing, where a transaction is costed and posted essentially
transaction-by-transaction rather than accumulated and finalized once a month.
2.4
Practical guidance for statutory periodic requirements
Given that
Fusion now supports Periodic Average Costing natively, the realistic design
options for a client with a statutory periodic requirement are:
• Enable a
dedicated cost book for Periodic Average Cost for the legal entity/cost
organization with the statutory requirement, and keep a separate perpetual book
(Standard or Perpetual Average) running in parallel for day-to-day management
reporting and planning visibility.
• Where the
periodic requirement is purely a reporting/reconciliation exercise rather than
a book-of-record requirement, it may still be simpler to run a single perpetual
book and reconcile to a period-end position through OTBI rather than
maintaining a second book — this is a design choice, not a platform limitation.
• Use the
account-combination derivation feature (the
CST_DERIVE_CCID_DISTRIBUTIONS_FOR_PAC profile option and associated mapping
sets) if the business needs visibility into likely GL impact during the period,
before the period actually closes and distributions freeze.
On
Oracle EBS, for context
EBS Cost
Management has long supported an equivalent parallel Periodic Average Costing
(PAC) engine layered on top of its mandatory perpetual costing methods
(Standard, Average, FIFO, LIFO). With Fusion's Periodic Average Cost Method now
available, the two platforms are much closer in capability on this specific
point than they were a few years ago. The meaningful differences today are more
about maturity of surrounding tooling and reporting than about the core costing
method being available at all.
3. Closing Thoughts
For a Fusion
consultant, the perpetual-vs-periodic conversation is an accounting-policy
question (GAAP and IFRS are silent on which system you use) meeting a
configuration question (which cost book design fits the client's statutory and
management-reporting needs). Fusion's multi-cost-book architecture means you
don't have to choose one globally. You can run perpetual for management
visibility and periodic for statutory compliance on the same items, in the same
cost organization, at the same time. Get the cost book design right at
blueprint stage, because retrofitting a periodic book onto a live perpetual-only
implementation is a much heavier lift than designing it in from day one.
References
Oracle
Documentation
• Periodic
Average Cost Method — https://docs.oracle.com/en/cloud/saas/supply-chain-and-manufacturing/26c/fapma/periodic-average-cost-method.html
• Periodic
Average Costing Process — https://docs.oracle.com/en/cloud/saas/supply-chain-and-manufacturing/26a/fapma/periodic-average-costing-process.html
• Enable
Account Combination Derivation for Costing Distributions with the Periodic
Average Cost Method — https://docs.oracle.com/pls/topic/lookup?ctx=fa26a&id=u30261867
• Oracle
Fusion Applications — Supply Chain Managerial Accounting Implementation Guide
(Cost Organizations, Cost Books, Cost Profiles) — https://docs.oracle.com/cd/E36909_01/fusionapps.1111/e22767/F464976AN36CA5.htm
• Oracle
Fusion Cloud SCM — Using Supply Chain Cost Management Guide — https://docs.oracle.com/cd/G55130_01/trans/G51981-01/using-supply-chain-cost-management.pdf
• Oracle
Fusion SCM Analytics — Costing Frequently Asked Questions — https://docs.oracle.com/en/cloud/saas/analytics/25r4/fascm/scm-costing-faqs.html
GAAP
/ IFRS Standards
• FASB
Accounting Standards Codification — Topic 330, Inventory — https://asc.fasb.org/330/
• IFRS
Foundation — IAS 2, Inventories — https://www.ifrs.org/issued-standards/list-of-standards/ias-2-inventories/
• KPMG —
Inventory accounting: IFRS Accounting Standards vs. US GAAP — https://kpmg.com/us/en/articles/2026/inventory-accounting-ifrs-accounting-standards-vs-us-gaap.html