Study guide

8.1 Payables Calendars and Payables Accounting Period Statuses

Oracle Fusion Cloud Financials Payables and Expenses 2026 Implementation Professional Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Exam Overview, Enterprise Structures & Security

1.1 Exam Facts, Hands-On Format & How to Use This Guide 1.2 Enterprise and Financial Reporting Structures & the Data Security Model 1.3 Business Units and Reference Data Sets

2 Chapter 2: Master Data, Taxes & Cash Management Setup

2.1 Supplier Master Data: Profile, Addresses, Sites and Site Assignments 2.2 Supplier Controls: Registration, Income Tax Details, Site Holds and Third-Party Payments 2.3 Bank Account Master Data: Banks, Branches, Internal Accounts and Security 2.4 Transaction Tax Setup for Procure-to-Pay 2.5 Configuring Cash Management for Payables: Statements, Reconciliation Rules and Clearing

3 Chapter 3: Supplier Invoices — Options, Entry & Matching

3.1 Invoice Options and Common Options for Payables and Procurement 3.2 Supplier Invoice Processing: Invoice Types, Components and Distribution Sets 3.3 Matching Invoices to Purchase Orders, Receipts and Consumption Advice

4 Chapter 4: Supplier Invoices — Tolerances, Holds & Approvals

4.1 Invoice Validation, Invoice Tolerances, Holds and Releases 4.2 Invoice Approval Rules: Workflow, Spreadsheet Rules and Approval Actions 4.3 Prepayments, Recurring Invoices, Credit and Debit Memos

5 Chapter 5: Invoice Automation, AI & Subledger Accounting

5.1 AI in the Supplier Invoices Process: IDR, Document IO, the Payables Agent and Intelligent Defaulting 5.2 Importing Invoices: File-Based Data Import, Import Payables Invoices and Corrections 5.3 Setting Up Subledger Accounting for Payables

6 Chapter 6: Payments — Configuration

6.1 Payment Options, Payment Methods, Defaulting Rules and Payment Terms 6.2 Payment Process Profiles, Formats, Payment Systems and Transmission 6.3 Disbursement System Options, Payment Security and Payment Approval Rules

7 Chapter 7: Payments — Processing, Withholding, Accounting & AI

7.1 The Payment Process and Payment Process Request Templates 7.2 Completing Payments: Printing, Electronic Confirmation, Bank Acknowledgments, Single Payments, Stops and Voids 7.3 Withholding Tax Setup and US 1099 Reporting 7.4 Payment Accounting: Issue and Clearing, Gains and Losses, Discounts, Cross-Currency Payments and Bills Payable 7.5 AI in the Payments Process: the Payments Agent, Discount Intelligence, Virtual Cards and Fraud Controls

8 Chapter 8: Accounts Payable Balances & Period Close

8.1 Payables Calendars and Payables Accounting Period Statuses 8.2 Payables to General Ledger Reconciliation 8.3 The Payables Period Close Process: Unaccounted Transactions, Sweep and Close Exceptions 8.4 Balancing, Accruals and Year-End Activities in Payables 8.5 Accounts Payable Analysis and Reporting: Landing Pages, Dashboards, Aging Periods and Key Reports

9 Chapter 9: Expenses — Processing, Setup & Policies

9.1 Expenses Processing: From Expense Entry to Reimbursement 9.2 Expenses System Options, Expense Report Templates and Expense Types 9.3 Managing Expense Policies: Categories, Rate Determinants and Enforcement 9.4 Mileage and Per Diem Policies, Oracle Maps and Cumulative Mileage 9.5 Conversion Rate Policies, Receipt Requirements and Payment Hold Rules

10 Chapter 10: Expenses — Approvals, Cards, Advances, Audit & Travel

10.1 Configuring Expense Approval Rules in the BPM Worklist 10.2 Configuring Corporate Card Programs: Payment Options, Transaction Files and Accounting 10.3 Managing Cash Advances: Policies, Approval, Accounting and Application 10.4 Managing Audit Rules, the Expense Audit and Reimbursement 10.5 Configuring Travel Integration: Travel Partners, Itineraries and Trip Expense Reports

11 Chapter 11: AI, Mobile, Automation & Redwood

11.1 AI, Mobile and Automation in Expenses: Expense Assistant, Email Receipts and Touchless Expenses 11.2 Enabling Redwood Capabilities and Their Impact on Existing Configurations

8.1 Payables Calendars and Payables Accounting Period Statuses

Key Takeaways Explain This Topic AI

Payables calendars are used for automatic withholding tax, payment terms, key indicator reporting and recurring invoices, and their periods are separate from accounting calendar periods.

Payables calendar frequencies are 4-4-5, 4-5-4, 5-4-4, Monthly, Quarterly, Weekly and Other; Other means you enter periods manually.

In a 4-4-5 calendar the 3rd, 6th, 9th and 12th periods have five weeks; in 5-4-4 the 1st, 4th, 7th and 10th; in 4-5-4 the 2nd, 5th, 8th and 11th.

Period generation uses the period frequency, periods per year, start date and period name format; weekly and quarterly names combine the frequency, the period number and the year, for example Quarter1-15.

Payables accounting periods move through Never Opened, Future, Open and Closed, and finally Permanently Closed, which can't be reopened.

Last updated: October 2026

The published objective is Manage Payables Calendars . It's easy to confuse with the accounting calendar that a ledger uses. Oracle is explicit: periods in Payables calendars are separate from the accounting periods defined on Manage Accounting Calendars. Payables needs both.

What Payables calendars are for

You create Payables calendars on Manage Payables Calendars . Oracle lists four uses:

Use How the calendar is used

Automatic withholding tax Period-based withholding limits and rate schedules, for example a yearly threshold per supplier (section 7.3). If a needed period is missing, validation places a Withholding Tax hold.

Payment terms Calendar -based due dates assign the due date to the period that includes the terms date, for example to avoid weekends or holidays. You can't assign a calendar-based term to an invoice if no period is defined for its terms date.

Key indicator reporting Periods for the Payables Key Indicators report

Recurring invoices The Create Recurring Invoices spreadsheet uses a Payables calendar, of type General Purpose in Oracle's example, and a from and to period range (section 4.3)

Period frequencies

  • Frequency Periods per year Pattern
  • 4-4-5 12 Every period has four weeks except the 3rd, 6th, 9th and 12th , which have five
  • 4-5-4 12 Four weeks except the 2nd, 5th, 8th and 11th , which have five
  • 5-4-4 12 Four weeks except the 1st, 4th, 7th and 10th , which have five
  • Monthly 12 Each month is a period
  • Quarterly 4 Each period is three months
  • Weekly 52 Each period is seven days
  • Other You decide Periods are entered manually
  • How periods are generated

When you create a calendar or add years, four attributes control generation:

Period frequency , for example Monthly or 5-4-4. Other means manual entry.

Periods per year , calculated from the frequency.

Start date : the first day of the calendar and of its first period.

Period name format : the naming convention.

For weekly and quarterly frequencies, the period name combines the frequency, the period number and the year. With a Quarterly frequency starting 1 January 2015, the first period is Quarter1-15 .

Oracle's 4-4-5 example

A 4-4-5 calendar with a start date of 1 January 2015 and name format MMM generates periods like these:

  • Period Start End Length
  • Jan-15 1 Jan 2015 28 Jan 2015 4 weeks
  • Feb-15 29 Jan 2015 25 Feb 2015 4 weeks
  • Mar-15 26 Feb 2015 1 Apr 2015 5 weeks
  • Apr-15 2 Apr 2015 29 Apr 2015 4 weeks
  • … … … …
  • Dec-15 26 Nov 2015 30 Dec 2015 5 weeks

Notice that period names don't match calendar months: "Mar-15" ends on 1 April. That's why a calendar-based payment term can give a different due date from a "Day of Month" term.

Payables accounting periods and their statuses

Payables keeps its own accounting period statuses , maintained with the Payables Manage Accounting Periods task for the ledger. They follow the ledger's accounting calendar, which is separate from Payables calendars.

Status Meaning in practice

Never Opened The period has never been used. A recurring invoice created for a Never Opened period gets a closed-period hold until the period is opened and the invoice revalidated (section 4.3).

Future Opened for entry ahead of time. Transactions can be dated in it, but accounting waits until the period is open.

Open Normal processing: entry, validation, payment and accounting

Closed Closed after the period's work is accounted and transferred. Can be reopened if needed.

Permanently Closed Final. Can't be reopened.

How Payables and General Ledger periods interact

Payables periods are opened and closed independently of General Ledger periods, but they follow the same accounting calendar.

Oracle's close guidance (section 8.3): close a Payables period after accounting entries are created and transferred to the general ledger .

Run the Payables Unaccounted Transactions and Sweep process, which can move unaccounted transactions to an open or future period, then close the period.

Review the Payables Period Close Exceptions Report when closing.

Open the next Payables period and run the interface processes.

Adjustment periods : the Payables to Ledger Reconciliation report runs only for non-adjustment periods of the primary ledger. Payables activity belongs in regular periods.

Exam patterns

"Calendar" payment term won't default on an invoice. There is no Payables calendar period that covers the terms date. Generate more periods or years.

Withholding stops with a Withholding Tax hold. Check the period-based limits that rely on the Payables calendar.

Recurring rent invoices for next year are on hold. Those Payables periods were Never Opened. Open them and validate.

An auditor wants a year locked for good. Use Permanently Closed , which can't be reversed. Use Closed if you might need to reopen.

Loading diagram...