Rule of the week: Weekend/Holiday Expenses

The error, and why it happens

You're reconciling a monthly expense claim batch and there's a line for "Office Supplies — Bunnings Warehouse — $187.50" dated a Saturday. Nothing else about it looks wrong. The receipt is attached, the GST is coded correctly, the category matches the chart of accounts. But the business is a professional services firm that closes at 5pm on weekdays and doesn't open Saturdays at all. Nobody was in the office to need supplies.

This is one of the most common blind spots in expense claim review, because everything about the transaction looks clean. The coding is right. The tax treatment is right. The only thing wrong is the date, and dates don't usually get checked — they get accepted as metadata, not evidence. Staff submit claims in batches, often weeks after the purchase, and a receipt dated a Saturday slides through with ten others dated on business days. Nobody stops to ask why someone bought office supplies on a day the office was shut.

It's not always fraud. Sometimes it's a genuine mix-up — a receipt from a personal weekend shop that got scanned into the wrong pile. Sometimes it's a legitimate weekend operation the reviewer doesn't know about. But weekend and public holiday dates on non-travel categories are a pattern worth a second look every time, because the base rate of genuine business need on those days, for most office-based businesses, is low.

A worked example

A mid-sized consultancy runs monthly expense claims for 14 staff. In October's batch:

• Bunnings Warehouse — $187.50 — Office Supplies — Saturday 14 October
• David Jones — $95.00 — Staff Amenities — Monday 6 October (Labour Day, VIC)
• Qantas — $612.00 — Travel: Airfares — Saturday 14 October

The first two sit in non-travel categories on non-business days, with no accompanying evidence of a weekend event, offsite, or on-call arrangement. The third is a weekend flight booked for a Monday client meeting interstate — entirely normal, because travel doesn't respect office hours. That's the distinction that matters: the category, not just the date.

How to find it manually

You'll need the expense claim export (date, amount, category, payee) and a public holiday calendar for the relevant state or states — Australian public holidays aren't uniform, so a claim dated a Monday could be a holiday in Victoria and an ordinary business day in Queensland.

1. Export the claim batch with dates and categories intact.
2. Add a helper column using a weekday formula (WEEKDAY() in Excel, checking for Saturday/Sunday) to flag weekend dates.
3. Cross-reference the remaining dates against the applicable state's public holiday list for the claim year.
4. Filter out travel-related categories — airfares, accommodation, car hire, mileage — since weekend and holiday travel is routine and not itself a signal.
5. Review what's left line by line against context you have to hold in your head: does this business operate weekends, is this employee on-call, was there a known offsite.

For a batch of 40–50 lines this takes 20–30 minutes if you already know the relevant public holiday calendar cold. It takes longer, and gets less reliable, across multiple states or when the reviewer doesn't have that context memorised. The method itself doesn't fail — the fatigue of doing it the same way every month does.

FAQ

What counts as a weekend or holiday expense claim red flag? An expense claim dated on a Saturday, Sunday, or public holiday, coded to a non-travel category, with no supporting context (rostered weekend work, an approved offsite, an on-call allowance) explaining why the spend happened outside normal business days.

Why do expenses dated on weekends need extra scrutiny? Because the coding and tax treatment can be entirely correct while the date itself is the anomaly — a receipt that doesn't match how or when the business actually operates, which is a pattern associated with misclassified personal spending or misdated documentation.

How the rule checks this automatically

It will miss genuine weekend operations it hasn't been told about — retail, hospitality, on-call rosters — and it will flag those the same way it flags anything else, so severity on this rule varies rather than being fixed, and a flag still needs a human to confirm context. What it does reliably is exclude travel categories automatically, check dates against public holiday calendars by state, and apply the same weekend logic to every line in every batch, every month, without the reviewer having to hold the holiday calendar in their head.

Finanomaly is currently waitlisted.