A financial period divides time into reporting slices for schedule cost control. In P6, financial period calendars are what Store Period Performance writes into: each period gets the actual units and costs recorded during it, so a cost report can show “spent in October” rather than only “spent to date”.
Financial periods aren’t accounting periods, although they usually line up with them. An accounting fiscal period controls what can post to the ledger. A financial period only labels a slice of schedule progress.
How it works
- Define the calendar. A financial period calendar is a list of named periods with start and finish dates, usually calendar months. In P6 Professional you can keep more than one calendar, assign one to each project and set a default for new projects.
- Link the actuals. The project’s calculation settings must link actual to date with actual this period units and costs. As each update records progress, the increase since the last store builds up in the actual this period fields.
- Update to the period end. The scheduler moves the data date to the end of the period and records actual starts, finishes, units and costs.
- Store. Store Period Performance saves the actual this period values into the chosen financial period for each selected project, then resets them to zero for the next period.
- Report. Financial period columns show stored actuals period by period. Earned value and planned value are stored alongside, so period cost and schedule performance can be reported later exactly as they stood.
Worked example
Illustrative (sample data): a project uses calendar-month financial periods, with the data date moved to the last day of each month before storing.
| Financial period | Actual cost to date | Stored this period | Earned value this period |
|---|---|---|---|
| Aug 2026 | $2.8M | $0.6M | $0.7M |
| Sep 2026 | $3.5M | $0.7M | $0.6M |
| Oct 2026 | $4.2M | $0.7M | $0.8M |
In November the cost engineer finds a $40,000 equipment invoice that belonged to September. The correction is entered in the November update, so November’s period cost carries it and September stays as it was reported to the owner. Re-storing September after editing its actuals would have changed a number the owner already had.
If the October store had been skipped, the actual this period fields would not have been reset at the end of October. The November store would then put October’s $0.7M into November along with November’s own cost, and October would show nothing.
Financial period vs related periods
| Period | What it controls | Where it lives |
|---|---|---|
| Financial period | Which slice stored schedule actuals belong to | Schedule (P6 or similar) |
| Fiscal period | Which accounting period an entry posts to, and whether it’s open | Accounting system |
| Update period | The interval between schedule updates | Schedule procedure |
| Data date | The point in time progress is reported up to | Each schedule version |
Why it matters
Owners and lenders usually want monthly cost and earned value figures that don’t change after they’re reported. Without stored periods, “this month” has to be reconstructed from to-date figures, and a later correction silently rewrites history.
Stored periods also make the schedule easier to reconcile with accounting. If financial periods match the contractor’s fiscal months, the schedule’s actual cost for October can be compared with October’s job cost after month-end close. Differences then point to timing, such as invoices posted late or costs loaded on the wrong activity, rather than to periods that cover different dates.
They also give the history that forecasting needs. Period-by-period actual cost and earned value show whether performance is improving or slipping, which feeds the estimate at completion. Cumulative to-date figures alone can hide a bad month inside a good average.
Common mistakes
- Storing before the update for the period is finished, so the period holds only part of its cost.
- Skipping a store, so the next period carries two periods of actuals.
- Re-storing an old period after correcting actuals, which overwrites a reported month in P6.
- Forgetting the setting that links actual to date and actual this period, so there’s nothing correct to store.
- Defining financial periods that end on different dates from the accounting months, which makes every reconciliation harder.
- Moving a project to a different financial period calendar after periods have been stored without checking what happens to the stored history.
How os.construction handles it
Financial periods are set per project or company-wide on Schedule › Resources & cost › Costs & EVM, or copied from an Accounting fiscal year as read-only company periods. Periods of one scope can’t overlap, and their dates can’t change once created. See Period performance and earned value.
FAQ
What is a financial period in Primavera P6?
It is a named date range, usually a month or a week, defined in a financial period calendar. When a scheduler runs Store Period Performance, P6 saves each activity's and assignment's actual this period units and costs into the chosen financial period, so the project keeps a record of what was spent in each period.
Is a financial period the same as an accounting period?
No. An accounting fiscal period controls what can post to the general ledger. A P6 financial period only labels a slice of schedule progress for cost reporting. Most contractors line the two up, usually as calendar months, so schedule cost reports can be compared with job cost from accounting.
What happens to actual this period after storing?
In P6 Professional, storing period performance saves the actual this period values into the selected financial period and then sets them to zero, ready for the next update. The project must have the option that links actual to date and actual this period units and costs turned on.
Can a stored financial period be changed?
Yes. Oracle's help says you can store into the same period more than once, and the new values overwrite the old ones. Past period values can also be edited in financial period columns. Both are convenient, and both can change a figure that has already been reported, so many teams restrict who can do them.
Should financial periods be weekly or monthly?
Monthly is the usual choice because owner reports, pay applications and accounting close are monthly. Weekly periods give more detail on short, fast projects, but every period has to be stored on time, so they add work for the scheduler.