4-5-4 Calendar Reporting in Xero: Why Retail and F&B Use It, and How to Run It

A homewares retailer with six stores sits down to review March. Sales are down 5% on last year, and the founder wants to know what went wrong.

Mostly, nothing did. Last year's March started on a Saturday and had five of them. This year's March started on a Sunday and had four, with an extra Tuesday in place of the missing Saturday. For a shop that takes a quarter of its week on Saturdays, that swap alone costs three or four per cent of the month.

Calendar months aren't equal units of trade. The 4-5-4 calendar is how retailers and F&B groups fix that, by reporting in whole weeks instead. This post covers what a 4-5-4 calendar is, why a business would run its management reporting on one, why doing it from Xero can be challenging, and what a setup that makes it routine looks like.

What a 4-5-4 calendar is

A 4-5-4 calendar builds the financial year out of weeks. Fifty-two weeks make four quarters of 13 weeks each. Each quarter splits into three periods of four, five and four weeks. Every week ends on the same weekday, usually Saturday, so every period does too.

The retail version most people mean is the one the US National Retail Federation publishes. Its year ends on the Saturday nearest 31 January, after the Christmas returns have washed through. Here's the first quarter of fiscal 2026 on that convention:

The periods borrow month names but don't match calendar months, i.e. Fiscal March this year runs to 4 April while Fiscal April only starts on 5 April.

There's one wrinkle. Fifty-two weeks is 52 x 7 = 364 days, so the year drifts a day or two against the calendar each year. Every five or six years it needs a 53rd week to catch up, usually added to the last period of the year. It works kind of like the extra day in a leap year. On the NRF's rule, fiscal 2012, 2017 and 2023 had 53 weeks, and the next one falls in fiscal 2028.

There are cousins. A 4-4-5 calendar puts the long period at the end of each quarter and is common in manufacturing. A 5-4-4 puts it first. Plenty of F&B groups skip quarters altogether and run 13 four-week periods. Every period is identical, so period 6 compares cleanly with period 5 as well as with last year's period 6, which no calendar month or 4-5-4 period can offer. The price is a 13th period that doesn't fit a quarter. The mechanics is mostly the same and this post applies to all of them.

Why companies report on a 4-5-4 calendar

The 4-5-4 calendar is not something you adopt because your accountant asked for it. It mostly comes from the strategic finance side of the business, where structuring economic periods right elucidates real world trends and supports strategic decision-making.

Trade runs on a weekly cycle

For most retailers and F&Bs, the week has a shape: quieter early on, building through Friday, peaking at the weekend, then the same again the following week. In F&B the peak is sharper still: Friday and Saturday nights can carry a large share of the week's takings. Seasons and holidays sit on top of that cycle, but the week is the unit that repeats. A calendar month cuts this particular cycle at an arbitrary point and holds four or five of each weekday depending on the year, so no two months hold quite the same trade. A period built from whole weeks always does.

Like-for-like comparisons

Fiscal March 2026 has exactly as many Saturdays, Sundays and Tuesdays as fiscal March 2025. When sales are down, it's because trade was down, not because the calendar shifted. For a retailer or a restaurant group, like-for-like sales growth is the number the business is judged on, and a 4-5-4 calendar is what makes it like-for-like.

Equal quarters

Every quarter is 13 weeks. Calendar quarters run from 90 to 92 days and carry a different mix of weekends each year.

Periods end when the business stops

Stocktakes tend to happen at the end of a trading week, not on the 31st. Weekly payroll, rosters, deliveries and store reporting all run in weeks. So do labour and food cost, the two numbers an F&B operator watches most. A period that ends on a Saturday lines up with all of them. A month that ends on a Wednesday cuts through the middle of a pay week and a stock cycle.

Finance speaks the same language as the shop floor

Buyers, merchandisers, store managers and venue managers already plan in weeks: week 1, week 27, the four weeks to Christmas. A finance pack in calendar months is a translation exercise every time someone asks a question.

The trade-offs

It has costs. Periods aren't equal within a quarter, because a five-week period is 25% longer than its neighbours, so month-on-month comparisons are meaningless and everything is measured against the same period last year. Accruals, rent and monthly subscriptions need more care. And the 53rd week has to be handled every few years.

That's why many businesses use the 4-5-4 calendar for management reporting only. The statutory year stays on a calendar month-end, the books stay in calendar months, and the 4-5-4 pack is a second view of the same ledger. Accounting standards allow a 52- or 53-week statutory year too, but most small and mid-sized retailers and F&B groups don't need to go that far.

Where native Xero stops

Xero is built on calendar months. That's fine for the statutory books but awkward for a 4-5-4 calendar in almost every place it matters.

There's no way to define fiscal periods

Xero's financial year end is a fixed day and month. There's no setting for a period pattern, a weekday or a 53rd week. Requests for 13-period and 4-4-5 accounting have sat on Xero's product ideas board since 2013 with no official response, and a newer request for custom accounting periods has comments from 4-4-5 businesses, one calling comparisons in Xero impossible without exporting to Excel.

A custom date range gives you one period at a time

You can run the Profit and Loss for 1 March to 4 April, which is fiscal March exactly. The trouble starts with the comparison. Xero's newer P&L compares a custom range with the same dates a month, quarter or year earlier, or with a period of the same length just before it. None of them is right. The same dates last year start on a Saturday instead of a Sunday, which is the exact mismatch the 4-5-4 calendar exists to remove. And the 35 days before fiscal March aren't a period at all: they're the last week of fiscal January plus all of February. A 13-period calendar fares a little better, because its periods are all 28 days and the same-length comparison does land on the previous period. Last year's same period is still out of reach: the same dates a year earlier are 365 days back, not 364.

Multi-period reports step by calendar month

Ask Xero for twelve comparison columns and you get calendar months, quarters or years, or equal-length blocks, which a 4-5-4 year with its five-week periods doesn't have. The API's P&L only steps by month, quarter or year. There's no option for "the previous 12 fiscal periods", and no weekly columns at all.

Budgets are monthly

Budget Manager holds one figure per calendar month, so every budget comparison Xero makes is built on calendar months. A budget phased by fiscal period has nowhere to live. Spreading monthly budgets across days, as some connectors do, puts a weekday-blind average onto a calendar whose whole point is not being weekday-blind. (Why the native budget vs actual report falls short covers the rest of Budget Manager's limits.)

The year end won't sit still

A 52/53-week year ends on a different date each year: 31 January 2026, 30 January 2027, 29 January 2028. Xero's year end doesn't move with it, and changing it is a deliberate operation, not a yearly habit. One user on the product ideas board reports year-end transactions being pushed into the following year when the date shifts. This is the strongest argument for keeping Xero on calendar months and building the 4-5-4 view outside it.

The 53rd week breaks every comparison

A 53-week year has an extra week to report, and the year after it needs a restated comparative so that like weeks still line up. The NRF's method shifts every week of the 53-week year back by one. Xero has no concept of either.

What the DIY version costs every period

Here's a single organisation's 4-5-4 pack for one period, built by hand from native Xero:

1. Run the P&L for the period's exact dates. Export it.
2. Run it again for the same weeks last year. Export that too. Look up the dates, because they're not the same dates.
3. Run year-to-date for both years, using the fiscal year's start date, not Xero's.
4. Re-phase the budget from calendar months into fiscal periods, or keep a separate budget sheet by period.
5. Paste it all into the pack, check the account rows still line up, and reconcile each column to the export it came from.

That's four P&L runs and a budget re-phase per period, before any analysis. A group with five organisations, such as a restaurant group with each venue in its own Xero file, does it five times. If the business also wants weekly trading figures, as most F&B operators do for prime cost, add a date-range run per week. Then, once every five or six years, rebuild the comparatives for the 53rd week.

Nobody has done anything wrong in that process. It's simply what a calendar the software doesn't support costs, paid in finance hours every period. The same pattern shows up in retail reporting by store and SKU and in F&B groups that watch prime cost by the week.

What a good 4-5-4 reporting setup looks like

1. The calendar is defined once, as data. The weekday the week ends, the pattern (4-5-4, 4-4-5, 5-4-4 or 13 × 4), the year-end rule and where the 53rd week goes. Every report reads from that one table. Nobody types period dates into a report.
2. Each period is pulled by its exact dates. Fiscal March is 1 March to 4 April, straight from the ledger, and it ties to Xero's own P&L run for the same dates.
3. Comparatives use the same weeks, not the same dates. Last year's fiscal March, not last year's 1 March to 4 April. In the year after a 53-week year, the restated comparative is labelled as restated.
4. The budget is phased by period. Ideally by week, so a five-week period gets five weeks of budget and Christmas week gets Christmas-week budget.
5. Weeks are available when the business wants them. A weekly trading view for the shop floor or the kitchen, and the period pack for the board, both from the same calendar.
6. The statutory view still reconciles. Calendar-month figures for the statutory year and tax come from the same ledger, and a reconciliation explains the few days at each end of the year where the two calendars differ. The balance sheet is the easy part: Xero runs one at any date, so a period-end balance sheet is just a different date.

The workarounds, ranked

1. Custom date ranges and a spreadsheet. The routine above. It's exact, because every number comes straight from Xero, and it's the right place to start. It's also slow, and the comparatives are where errors creep in.

2. A general ledger export with a date lookup. Export the transactions, add a table mapping every date to its fiscal week and period, and pivot. Comparatives and weekly views come for free once the table exists. It breaks when the export columns change, when the file gets too big for the spreadsheet, or when the person who built it leaves.

3. Build it from the Xero API. Call the P&L once per period with exact dates, or pull transactions and bucket them by date. This is the only route that's both exact and repeatable. It's also real engineering: rate limits, pagination, and the fact that Journals, the most efficient endpoint, now sits behind Xero's Advanced API pricing tier. There's more on that in building on the Xero API.

4. Force fiscal periods into the books with journals. Some businesses post reversing journals to shift a few days' trading so that calendar months approximate fiscal periods. Don't. It distorts the statutory ledger to suit a management view, and the next person to open the file has no idea why March's revenue is wrong.

Where Cheetah fits

A 4-5-4 calendar is a definition problem, not an accounting one, and definition problems are what software is good at. With Cheetah, you tell us your calendar once: the weekday your weeks end on, your pattern, your year-end rule and where the 53rd week goes. Cheetah turns it into a period table and builds your pack from it.

Each period is pulled from Xero by its exact dates and ties to Xero's own P&L for those dates. Last year's same weeks sit beside it, with a restated comparative in the year after a 53-week year. The budget is loaded by period. If you run several organisations, every store or venue uses the same calendar. For an F&B group, that puts labour and food cost in the same periods as the rosters and stocktakes that drive them. Xero stays on calendar months for the statutory books, and nothing in your ledger changes.

The pack arrives in Google Sheets with plain formulas and an Excel download, and it can refresh on a schedule, so period close stops including a morning of P&L exports. A new year is a new row in the calendar, not a rebuild.

If your business trades in weeks and your reporting still runs in months, it's worth a conversation.

The short version

A 4-5-4 calendar reports in whole weeks, so every period holds the same weekdays as the same period last year and comparisons finally mean something. Retailers and F&B groups use it because that's how they trade. Xero can't run on it: no fiscal periods, comparisons by calendar month, monthly budgets and a fixed year end. The ledger has every number you need, though. Report each period by its exact dates against the same weeks last year, and the 4-5-4 pack becomes a routine instead of a monthly rebuild. For the reporting layer underneath it, see what a custom Xero report actually takes to build.