Hourly Rate to Annual Salary in Australia: Where the Simple Sum Goes Wrong
6 min read · Published by EasyPayCalc, easypaycalculator.com.au
Sources behind this guide last checked 15 August 2026. How we check the numbers
Two job ads offer the same hourly rate. One is casual, one is permanent. If you multiply both by your hours and call it a year, you will get the same annual figure for two jobs that do not pay the same at all.
Converting an hourly rate into a yearly number is the easiest sum in payroll and the one most likely to mislead you. The arithmetic never fails. The assumptions hiding inside it fail all the time. This guide is about those assumptions, because once you can see them you can decide which ones hold for your job.
The sum everyone does
Take the rate, multiply by the hours you work in a week, multiply by the weeks in a year. Every quick conversion, including the ones people do on the back of a payslip, is some version of that line.
For the sum to land on money you will actually see, everything it quietly takes for granted has to be true at once.
| The sum takes for granted | Holds when | Breaks when |
|---|---|---|
| The rate means what you think it means | You know whether loading is inside it | A loaded and an unloaded rate are compared as equals |
| Your weekly hours repeat all year | Fixed roster, permanent role | Shifts move around, or quiet weeks are unpaid |
| The rate itself stays put | Inside a single financial year, usually | The annual wage review moves the base under you |
The first assumption does the most damage, so it goes first.
Two rates that look the same
Casual work in Australia comes with a loading, an extra slice added onto the base rate to make up for the paid leave and job security a casual does not get. That slice is not a bonus. It is the price of the entitlements you are not receiving, folded into the hourly figure.
Which creates a trap. A casual rate on a job ad usually has the loading already inside it. A permanent rate never does, because a permanent employee gets the entitlements themselves instead. Put the two rates side by side and you are not comparing pay. You are comparing one number that contains compensation for missing leave against another that has the leave waiting outside it.
The number is the same. What is inside it is not.
The trap has a second layer. If you believe a loaded rate is a base rate, you will add the loading again when you estimate your pay, and everything downstream inflates. We fixed exactly this mistake in an earlier version of our own casual calculator, which taught us how easy it is to make. When a rate already contains its loading, the only correct thing to add is nothing.
So before any conversion, settle one question: is this rate loaded or not. The job ad often will not say. Your award does, and so does a payslip once you have one, where base and loading appear as separate lines.
The same discipline applies when you are weighing a casual offer against a permanent one. Stripping the loading out of the casual rate gives you two base rates you can honestly compare. Leaving it in means the casual job looks better by exactly the value of the leave it does not include, and people accept jobs on that illusion. Whichever way you compare, do it on rates that mean the same thing.
The hours assumption
A conversion needs a number of hours per week, and whatever number you choose becomes a claim about your whole year. Use a standard full week and you have assumed you will work a standard full week every week, without gaps, from July to June.
Permanent workers can lean on that assumption, because paid leave fills the weeks they are away. For casuals the floor is missing. A week not worked is a week not paid, and the quiet stretch in winter, the two weeks a cafe closes over Christmas, the roster that drops when a new hire starts, all of it lands directly on the annual total.
The multiplication is honest. The assumption underneath it is the part that moves. If your hours vary, a year built from your best week is a ceiling, not an estimate, and a year built from an average of real weeks is worth far more than either.
Building that average is not complicated, but one detail decides whether it is worth anything. Count the empty weeks. Take a recent stretch of payslips, add up the hours, divide by the number of weeks that passed rather than the number of weeks you worked. An average that skips the gaps is just the optimistic sum wearing a disguise. An average that includes them is the closest thing a variable roster has to a salary.
What an hourly rate is made of
An hourly rate is not one number. It is a stack, and the stack is set mostly by your award, the industry ruling that fixes minimum pay and conditions for your kind of work.
At the bottom sits the base rate. On top of it, depending on who you are and when you work, sit the casual loading, penalty rates for weekends and nights and public holidays, and allowances tied to the role. On any given shift, only some of the stack applies to you, which is why two people on the same award can be paid quite differently for the same clocked hours.
The national minimum wage is the floor under all of it, and your award can sit above that floor, sometimes well above. Which means the useful question is rarely what the national minimum is. It is what your award says for your classification, at your age or experience level, on the shifts you actually work.
The stack also refuses to stay still. The national minimum wage and award base rates are reviewed every year, with changes landing at the start of July. Because the loading is calculated as a share of the base, it moves whenever the base does. Any annual figure you worked out from last year's rate quietly went stale at the same time. We do not print the current amounts here for that exact reason. They belong in the calculator, which is updated when they change.
Which of this matters for you
The loaded or unloaded question matters every single time. Getting it wrong skews the whole year by the size of the loading, in either direction, and no calculator can catch it because only you know which rate you typed in.
The hours assumption matters in proportion to how much your weeks move. A steady roster can ignore it. A seasonal or on-call pattern cannot, and averaging several ordinary weeks beats guessing.
The July reset, by contrast, needs no vigilance at all. You cannot miss it, your payslip will show it, and nothing you calculate today is damaged by it as long as you redo the sum on this year's rate rather than a remembered one.
Putting a number on it
The structure above is the part that stays true from year to year. The current rates, the loading, the tax that comes out of the annual figure once you have one, all of that is live data, so put your rate and hours into the calculator and read the result at today's values.