About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
An Australian business's busiest computing days are set by its calendar: pay runs, BAS lodgment and the end of the financial year. Because those dates are known months ahead, the extra capacity they need can be planned rather than rushed. Mark the peaks for the coming year, measure how much each one adds, and for each choose either to keep enough headroom all year or, if your plan allows temporary increases, to book one before the peak and remove it afterwards. Temporary increases suit large, short peaks; year-round headroom suits small or frequent ones.
Why it matters
A slow accounting system on a BAS due date, or a payroll server struggling with the final pay run in June, lands on the people who can least afford delay. Paying for peak capacity every month of the year can be wasteful if the peak lasts a fortnight. Planning both sides, the deadline and the cost, turns a yearly scramble into a booked change.
How it works
Build the peak calendar
Start with the dates the business must meet. For BAS, the ATO lists the quarterly due dates: "July, August and September | 28 October | 2. October, November and December | 28 February | 3. January, February and March | 28 April | 4. April, May and June | 28 July". For monthly reporters, "The due date to lodge and pay your monthly BAS is the 21st day of the month following the end of the reporting period". The ATO also notes that if you use a registered tax or BAS agent, different due dates may apply.
For payroll, the ATO asks employers to "Check and finalise your Single Touch Payroll (STP) data by 14 July". The same item adds that the declaration is due by 14 July "(later for closely held payees)", such as family members on the payroll of a family business. The item was written for finalising the 2025-26 year; check the ATO's current page each year. For most employers, that puts the last pay run of June, end-of-year adjustments and finalisation into one short window.
Add the business's own peaks: month-end invoicing, stocktake, a retail season, enrolment periods, or a yearly audit.
Measure what each peak adds
Using last year's figures, compare each peak with a normal week:
- How much higher did processor and memory peaks go?
- Did storage jump (for example, year-end reports and archives) and stay up?
- Which servers were affected: the accounting server, the database, the remote desktop servers?
A peak that adds 10 per cent for two days is different from one that doubles the load for three weeks.
What to choose and why
Year-round headroom or a temporary increase
| Peak | Better choice | Why |
|---|---|---|
| Small (within your headroom policy) | Year-round headroom | Nothing to change, nothing to remember |
| Frequent (every month-end) | Year-round headroom | A monthly up-and-down change adds risk and effort |
| Large and short (EOFY, a season) | Temporary increase, if your plan allows it | Pay for the extra only while it is needed |
| Storage that stays | Permanent growth | Year-end records are kept after the peak |
The table is editorial guidance, not a rule from the sources.
Book temporary increases like any change
- Ask early. Request the increase a few weeks before the peak, in writing, with the removal date.
- Check what needs a restart. On a VMware-hosted server, Broadcom's memory hot-add article lists what live-add needs, starting with the host licence feature "Hot Pluggable Virtual Hardware", the option enabled on the virtual machine beforehand, and guest support. Without those, book a short window before the peak and another after it. Adding is not the same as removing: the article covers adding memory to a running server, not taking it away, so plan to reduce the server after the peak as a change made while it is powered off, in an agreed window. Our article on which changes need a restart covers the details.
- Check whether your plan allows temporary increases at all, and how it charges for them; not every hosting plan does.
- Plan the reduction carefully. Microsoft notes that "Scaling down or scaling in can have implications on the availability and performance of the workload". Remove the extra after the deadline has passed and the data is safely lodged, not on the day.
- Do not plan to shrink disks. Extra storage is easy to add and hard to take back; treat it as permanent.
An illustrative example
A 40-person wholesale business lodges quarterly BAS and runs weekly payroll. Its accounting server is comfortable in normal weeks, but last June it ran near its memory limit for the final three weeks of the financial year. The plan: the last week of BAS quarters stays within normal headroom; for June, extra memory is booked for 1 June to 20 July, applied in an evening window and removed in another after STP finalisation. The example is illustrative.
Read next
Related articles you may want next.
- HostingRight-sizing over-provisioned servers: reclaiming CPU and memory safelyHow a business proves a hosted server has more processors or memory than it needs, reduces them in measured steps without hurting peak work, and keeps a way back if it goes wrong.Read article
- HostingForecasting capacity from a year of measurements: when is the next upgrade due?How a business turns twelve months of storage, memory and processor figures into a likely date and budget line for its next hosted-server upgrade, using two simple forecasting methods with worked arithmetic.Read article
- HostingHow much headroom to keep: thresholds and lead time for hosted resourcesHow a business sets written trigger levels for storage, memory and processor on hosted servers, so upgrades are ordered early enough, peaks are absorbed and nobody argues about when to buy more.Read article
Risks and limits
- Dates change. The ATO updates its pages and agents can have different dates. Re-check each year.
- Peaks move with the business. A new product line or acquisition shifts load; re-measure after changes.
- Two windows, not one. A temporary increase that needs restarts means two planned interruptions. Count them.
- Software licensing may apply. Some software is licensed by processor cores; ask the software vendor or your licensing adviser whether a temporary processor increase changes what you owe, before adding processors even briefly.
- The bottleneck may not be the server. A slow peak can come from the application, the database design or the network. Measure before buying.
Sources
Opened 15 November 2026; the ATO pages and Broadcom 311579 reopened 16 November 2026.
- Australian Taxation Office: Due dates for lodging and paying your BAS, last updated 17 September 2026.
- Australian Taxation Office: Finalise your STP data by 14 July, published 3 June 2026.
- Broadcom Knowledge: Adding hot memory to a virtual machine fails or the option is greyed out, article 311579, opened 16 November 2026.
- Microsoft Learn: Architecture strategies for optimizing scaling and partitioning, Azure Well-Architected Framework, updated 30 October 2025.
Related service: Cloud hosting.
Learning notes
- Quarterly BAS is due 28 October, 28 February, 28 April and 28 July; agents may differ.
- For most employers, STP finalisation is due by 14 July (later for closely held payees), so June and early July are a payroll peak; re-check the ATO each year.
- Small or frequent peaks: keep headroom. Large, short peaks: book a temporary increase.
- Temporary processor or memory changes may need two restart windows.
- Remove the extra after lodgment, and treat added storage as permanent.
This article was originally published on .