Financial Model with a Custom Fiscal Year
Set your fiscal year end and keep annual, quarterly, monthly and weekly results aligned to the same real dates.
30 September year end · FY2026–FY2027
Preview · Illustrative values · EUR thousandsIncome Statement
| Line item | FY2026 | FY2027 |
|---|---|---|
| Revenue | 12,968.9 | 14,006.4 |
| Net income | 1,719.6 | 1,898.6 |
Balance Sheet
| Line item | FY2026 | FY2027 |
|---|---|---|
| Total assets | 14,024.3 | 15,634.9 |
| Cash & Cash Equivalents | 4,006.6 | 5,122.9 |
Cash Flow Statement
| Line item | FY2026 | FY2027 |
|---|---|---|
| Cash flow from operations | 2,107.8 | 2,276.0 |
| Change in cash | 983.9 | 1,116.3 |
Free · No signup · Choose granularity in the model
Choose an explicit Fiscal Year End
Set the month and day in model setup or the existing Periods settings. The setting applies across the model’s scenarios and is undoable. Fiscal-year labels identify the year containing the year end. The model period reference explains calendar settings and source behavior.
Use the dates your company reports
With a 30 September year end, FY2027 runs from 1 October 2026 through 30 September 2027. With 31 March, FY2027 runs from 1 April 2026 through 31 March 2027; with 30 June, it runs from 1 July 2026 through 30 June 2027. A non-calendar year belongs within this financial model, without a separate spreadsheet calendar.
Plan quarters within the fiscal year
Fiscal Q1 starts at the beginning of the financial year. For a September year end, Q1 covers October–December and Q2 January–March. Quarterly identities follow the fiscal year, not a calendar-quarter label. Explore quarterly financial modeling for direct assumptions at that interval.
Keep monthly and weekly identities intact
Months retain their calendar-month identities; weeks retain Monday–Sunday ISO identities. Their real-date intersections determine fiscal membership. A week crossing a fiscal-year boundary stays one column, while its exposure contributes to the appropriate periods. See weekly modeling for ISO weeks and week 53.
Forecast across year-end boundaries
Changing Fiscal Year End remaps annual assumptions and relevant scenario or What-If addresses. Monthly and Weekly inputs retain their real-date identities; saved records outside the new horizon stay inactive until included again. Review period selections and unresolved work after a change. A calendar setting is not a second financial model.
Use fiscal dates consistently in analysis
DCF discount timing and LBO period selections use the existing shared period/date logic; their horizons are selected independently of visible statement columns. Review the DCF reference and LBO reference for valuation assumptions. The three-statement model remains the operating source, with scenarios using the same model-wide fiscal setting.
Frequently asked questions
Can I use a fiscal year ending in September?
Yes. Set Fiscal Year End to 30 September. FY2027 then covers 1 October 2026 to 30 September 2027.
How are fiscal quarters defined?
Quarter boundaries follow the beginning of the fiscal year. For a 30 September year end, Q1 is October–December, Q2 January–March, Q3 April–June and Q4 July–September.
What happens when a week crosses a fiscal-year boundary?
The ISO week keeps its identity. Dated intersections assign its exposure to the relevant fiscal periods.
Does Fiscal Year End change separately for each scenario?
No. It is a model-wide setting across scenarios. The existing change workflow is undoable.