When you miss a day — the back-date workflow without breaking margin.
To backdate an expense or revenue entry for a small business: enter it against the date it actually happened, not today. nouz lets you backdate within 30 days; the entry uses the COGS and tax rules that were live on that historical date, so your margin reporting stays accurate. Here's the full workflow.
Everyone misses a day. The flu hits. You close early for a family emergency. The closer forgets. The till freezes and reboots into a state nobody can read. The question is not whether it happens — it's whether the recovery is clean or whether the missed day quietly bends your reporting for the next three months.
This is the recovery workflow we use at nouz. Four steps, usually 5–10 minutes, no compromise on margin accuracy. The key idea: enter what actually happened on the day it actually happened, not as a lump on today.
The one rule
When recovering a missed day, every entry — revenue, expenses, waste — gets tagged with the date it happened, not the date you're recording it. The single most common backdate mistake is to enter Friday's missed close-out as a Monday entry. It "balances the week" only in the most superficial sense; it tells your reporting that Monday's margin was twice as good as it was, and Friday's was zero. Both are wrong. The truthful version uses Friday's date.
The four-step workflow
Run this as soon as you notice the missed day — same evening if you can, the next morning at the latest.
- 01Open the missed date in the revenue tab.
On the revenue screen, click into the missed day. nouz will show an empty entry; that's the gap you're filling.
- 02Reconstruct revenue first.
Pull the missed day's Z-tape from your POS or look at the card-terminal report. Enter cash and card separately, tagged to the missed date.
- 03Add expenses against the missed date.
Any invoices, petty cash, or variable costs that landed that day. The expenses screen accepts backdated entries directly — same 30-day window.
- 04Confirm fixed costs auto-pro-rated.
Don't enter anything for fixed costs — they slice into the missed day automatically. Just check the P&L screen and confirm the slice landed.
Total time: 5 minutes if the day was a normal trading day with a clean Z-tape. 10–15 if you're reconstructing from less complete information.
Reconstructing what actually happened
The harder case is when the data sources for the missed day are incomplete or disputed. The Z-tape rolled over. The card terminal's daily batch was already settled. The cash got swept into the safe without a count. Here's a hierarchy of sources, best to worst:
| Source | Quality | Use when |
|---|---|---|
| POS Z-tape from that day | Best | Always your first choice; trust this number |
| Card processor settlement report | Very good | Reliable for card; pulls from the processor portal |
| Bank deposit slip | Good for cash | Tells you what was deposited; subtract float to get revenue |
| Staff memory | Mixed | For waste, invoices, petty cash; check against gut |
| Comparable-day average | Last resort | When nothing else exists — average the prior 4 same-day-of-week revenues |
Why margin stays honest (even when you backdate weeks later)
This is where the COGS-snapshot design earns its keep. When you backdate a sale to a date three weeks ago, nouz applies the COGS snapshot that was live at that historical date — not the current COGS. Same for tax rates, transaction fee rates, and active fixed costs.
Concrete: if you backdate a flat-white sale to a date when bean cost was €0.42, the entry records €0.42 — even if today's bean cost is €0.51. The historical margin stays the historical margin. You can't "accidentally improve" past weeks by entering late data at current rates.
This matters most when you're backdating into a period you've already reviewed or shared with your team. The numbers don't shift around under you.
I was off sick for four days in November. When I came back I was dreading the reconstruction — last year on a spreadsheet I never really recovered, that whole month's margin was rubbish. This time it took me 25 minutes, four days backdated cleanly, COGS snapshots correct. November's number was real.
Beyond 30 days, and beyond a week of missed days
Two harder edges.
Past the 30-day window
You can still add the entry — nouz won't lose data — but you'll be prompted for a reason and the entry shows a "late" flag in audit reports. The COGS snapshot logic still applies, so margin is still honest. The flag exists so that if you later wonder why the trailing 90-day report shifted, the late entries are findable.
When you miss more than a few days
If you missed a full week or more (extended illness, holiday closure with no close-out), the workflow stays the same but you batch the reconstruction. Take an hour, work through each missed day in order — oldest first. The order matters because some entries depend on others (a delivery on day 3 affects the COGS of sales on day 4 if there's a unit-cost change). Working forward keeps the sequence clean.
- For the closed days (the actual holiday), enter zero revenue, zero variable costs. Fixed costs still pro-rate; that's correct.
- For the trading days you missed entering, work through each day in turn. Pull the Z-tape, enter, move to the next.
- For invoices that arrived during the missed week, backdate each to its actual delivery date.
If you're running on a spreadsheet, the workflow is structurally identical — find the missed columns, fill them in, don't lump into "today." The only thing the spreadsheet won't do for you is auto-apply the right historical COGS; you'll have to remember if a supplier price changed mid-week. See the daily-P&L template post for the spreadsheet shape.
For the in-app version, the missed-multiple-days walkthrough in the help centre covers the batch case step-by-step. The recovery is real — a missed day or week doesn't have to mean a corrupted month.
FAQ
What if I genuinely don't know what the revenue was on the missed day?
Best case: pull the POS Z-tape (most POS systems retain at least 90 days of daily totals). Next: pull the card-processor portal report for that day. Last resort: use the average of the prior four same-days-of-week as a placeholder, tag it as an estimate, and replace it if better data surfaces.
Will backdating an entry change my reported margin for that period?
Yes — and that's the point. The entry was missing; adding it makes the period's margin more accurate, not less. Because nouz applies historical COGS snapshots, the change is in the direction of "more truthful," never "retroactively cooked."
Does the system warn me if a backdated entry would put a day into negative EBIT?
No — it just records what you tell it. A negative-EBIT day is sometimes the truth (a closed day with rent still slicing in). The system trusts your input; it's your judgment that decides whether the result is reasonable.
What about backdating revenue to the wrong VAT period — does that cause tax problems?
Backdating within a VAT period is harmless. Backdating across a period boundary (e.g. moving a sale from July into June after July's VAT return is filed) is something to flag to your accountant. nouz tracks the dates accurately; the question is how your VAT filing handles the late entry.
Can I undo a backdated entry if I made a mistake?
Yes — edit or delete within the 30-day window, same as any entry. Beyond 30 days, you can still edit, but the change is logged in the audit trail. The data integrity is preserved; the system just keeps a record of what changed and when.