Why Australian indie devs must forecast revenue in AUD, not USD. FX exposure, tax, and cash flow planning explained for solo programmers.
You land a client deal. $15,000 USD per quarter. That sounds like about $23,000 AUD at today's rates—solid income. You mentally add it to your quarterly forecast, pat yourself on the back, and move on.
Three months later, the AUD has strengthened. Your $15,000 USD invoice now converts to $22,100 AUD. You're down nearly $900 without changing a single line of code. Or the opposite happens: the AUD weakens, and suddenly your $15,000 USD is worth $24,200 AUD. Great, right? Except you already budgeted for $23,000, and now you're scrambling to figure out whether that windfall is real or temporary.
This is the trap that catches most Australian solo developers. You earn in USD (or GBP, or EUR), live in AUD, pay tax in AUD, and plan your business in... well, usually a mix of both, which is chaos.
Forecasting in USD when you live and operate in Australia isn't just sloppy accounting. It's a silent business risk that erodes your ability to answer the two questions every solo programmer needs answered: How much should I actually be making this quarter? and How's the business really doing? Currency volatility, tax treatment, and cash flow timing all hinge on which currency you use as your baseline.
This explainer walks through why Australian indie developers need to forecast in AUD, not USD—and what that actually means for your revenue planning, tax obligations, and business health metrics.
Currency exposure is the risk (or opportunity) that changes in exchange rates will affect the value of money you've earned or are about to earn. For Australian solo developers, this is unavoidable if you work with international clients, which most of you do.
Here's the mechanics: When you invoice a US client $15,000 USD, you haven't actually received AUD yet. The USD is sitting in your bank account or waiting to be converted. The moment you convert it—or the moment you spend it—the exchange rate at that time determines how many AUD you actually get. The AUD/USD exchange rate fluctuates daily, sometimes by 1–2% in a single week.
Over a quarter, that's not trivial. A 5% swing in the AUD/USD rate (which happens regularly) on $60,000 USD of annual revenue means a $3,000 AUD swing in your actual take-home. For a solo developer working on thin margins or trying to hit a specific quarterly target, that's the difference between a comfortable quarter and a stressful one.
The problem deepens when you forecast in USD but plan your life and business in AUD. You tell yourself, "I'll earn $60,000 USD this year." But you need to know: How much AUD is that, really? And the answer isn't a single number—it's a range, because the exchange rate will move.
According to financial forecasting guidance from William Buck Australia, effective forecasting requires clarity on the currency in which you're actually operating and planning. For Australian businesses, that means AUD. The moment you mix currencies in your forecast, you introduce uncertainty that doesn't just blur your numbers—it makes it impossible to set realistic targets or flag when you're falling behind.
Here's where forecasting in USD becomes a legal and financial headache. The Australian Taxation Office (ATO) requires you to report income in AUD. Full stop. Your tax return is in AUD. Your business activity statement (BAS) is in AUD. Your taxable income is determined in AUD.
When you earn USD and convert it to AUD, the ATO wants to know the exchange rate you used on the day of conversion (or the day you received the payment, depending on your accounting method). If you've invoiced a US client on January 1 at an AUD/USD rate of 0.65, but you don't convert the money until February 15 when the rate is 0.68, the difference is a foreign exchange gain—and that gain is taxable income.
Conversely, if the rate moves the other way, you can claim a foreign exchange loss, which reduces your taxable income. But here's the kicker: you have to track this properly, and it only works if you're clear about which currency you're forecasting in.
The ATO's guidance on foreign exchange gains and losses makes it clear that these FX movements are treated as either income or deductions, depending on the direction. If you're forecasting revenue in USD and then surprised by FX losses when you convert, you might end up with a lower taxable profit than you expected—but you also might have less cash in the bank.
This is why forecasting in AUD is essential: it forces you to think in the currency you actually pay tax in. When you forecast $15,000 USD per quarter, you're not really forecasting. You're guessing. When you forecast $23,000 AUD per quarter (based on a reasonable AUD/USD assumption), you're making a deliberate choice about currency exposure and tax liability.
Most solo developers conflate revenue and cash flow. They're not the same thing, and the difference becomes acute when you're dealing with multiple currencies.
Revenue is the money you invoice. Cash flow is the money that actually hits your bank account. When you invoice a US client $15,000 USD, that's revenue. When you convert it to AUD three weeks later at a slightly worse rate than you expected, that's cash flow. The gap between the two is where currency exposure lives.
If you forecast in USD, you're essentially ignoring this gap. You tell yourself, "I'll invoice $60,000 USD this year," and you assume that's $92,000 AUD (at 0.65 rates). But when you actually convert the money, you might only get $90,500 AUD because rates moved. You've just lost $1,500 of expected cash flow—and you didn't see it coming because you weren't forecasting in the currency you actually use.
Forecasting in AUD forces you to think about cash flow timing and FX conversion as explicit variables. You might forecast: "I'll invoice $60,000 USD this year, which I expect to convert to $92,000 AUD at average rates of 0.65. But I'll assume a 2% FX headwind, so I'll budget for $90,000 AUD of actual cash in." That's a real forecast. It accounts for currency risk. It's honest.
According to Grant Thornton's perspective on financial forecasting, Australian businesses that forecast effectively distinguish clearly between revenue recognition and cash receipt. This distinction matters especially for businesses with international income streams, where the timing and rate of currency conversion can materially affect cash availability.
Let's say you set a quarterly revenue target. Many solo developers do this intuitively: "I want to earn $50,000 this quarter." But $50,000 what? If you say USD, you're setting a target in a currency you don't actually control and don't actually spend.
Now imagine it's mid-quarter. You've invoiced $35,000 USD so far. You're on track, right? Maybe not. If the AUD has weakened against the USD since you set your target, that $35,000 USD is now worth more AUD than it would have been at the start of the quarter. You might actually be ahead of your AUD target without realizing it. Conversely, if the AUD has strengthened, you're further behind than your USD forecast suggests.
This is more than a psychological trick. It affects real decisions. If you think you're on track when you're actually behind, you won't push for additional work or raise rates. If you think you're behind when you're actually on track, you might undercut yourself or overcommit.
Forecasting in AUD gives you a clear, unambiguous target: "I want to earn $75,000 AUD this quarter." Now, when you invoice $35,000 USD mid-quarter, you can convert it at today's rate and see exactly where you stand. No ambiguity. No second-guessing.
Here's a scenario that catches many solo developers off guard: You have three main clients. One pays in USD, one in GBP, one in AUD. Each represents roughly a third of your revenue. You think you're diversified. You're not—you're exposed to three different currency risks simultaneously.
If you forecast in each client's native currency, you're managing three separate forecasts and three separate conversion risks. If you forecast in AUD, you can see the real picture: your revenue is geographically diversified, but your currency exposure is concentrated in USD and GBP. That concentration is a risk, and it's invisible if you're not forecasting in AUD.
Moreover, client concentration—the risk that one or two clients represent too much of your revenue—is a critical business health metric. But you can only measure it accurately in a single currency. If Client A pays $40,000 USD and Client B pays $30,000 AUD, what's your actual concentration? You can't tell unless you convert both to AUD and see that Client A represents 65% of your revenue while Client B represents 35%.
This is where Cashierr's revenue planning tools become valuable for solo developers. By tracking revenue in AUD and flagging client concentration, you can see whether you're over-reliant on a single income stream—and whether that stream is exposed to currency volatility. An AI agent that monitors these metrics can alert you before the risk becomes a crisis.
Here's a subtle but important point: the AUD/USD exchange rate doesn't move in a vacuum. It's influenced by relative inflation rates, interest rates, and economic conditions in Australia vs. the US.
When the Australian inflation rate is higher than the US inflation rate, the AUD typically weakens against the USD over time (all else equal). This means that even if your USD invoices stay the same, their AUD value gradually decreases—not because of short-term volatility, but because of long-term purchasing power differences.
The Australian Bureau of Statistics publishes Consumer Price Index data that shows inflation trends in Australia. If Australian inflation is running at 3.5% while US inflation is at 2%, the AUD is likely to depreciate over time. That means your USD invoices will be worth less AUD in real terms as the year progresses.
This is why forecasting in AUD matters for long-term planning. If you forecast $60,000 USD revenue for the year, you might assume it converts to $92,000 AUD. But if the AUD depreciates by 3% over the year due to inflation differentials, your actual AUD conversion might be closer to $89,000. That's a $3,000 difference—and it's entirely predictable if you're paying attention to economic fundamentals.
When you forecast in AUD, you're forced to think about these dynamics. You might set your target at $90,000 AUD and explicitly assume a 2% FX headwind due to expected inflation differentials. That's a realistic forecast. It accounts for macroeconomic conditions. It's defensible.
Okay, so you're convinced. You need to forecast in AUD. How do you actually do it?
Start by listing your revenue sources. For each client or project, note:
Finally, sum everything up in AUD. That's your quarterly revenue forecast. It's not a guess. It's a deliberate assumption about currency exposure, conversion timing, and economic conditions.
Here's an example:
Client A (USD): $15,000 USD/quarter
That's your real target. Not $60,000 USD (which sounds better but is misleading). Not an optimistic $50,000 AUD (which ignores FX risk). It's $47,768 AUD, based on realistic assumptions about currency exposure and conversion timing.
Now, when you hit mid-quarter, you can convert your actual invoices at today's rates and see exactly where you stand against this target. No ambiguity. No currency confusion.
Once you're forecasting in AUD, you need a system for tracking actual FX movements so you can report them correctly to the ATO.
Here's the basic approach:
This is why forecasting in AUD is so important for tax planning. If you forecast $60,000 USD revenue and assume a 0.65 rate, you're budgeting for $39,000 AUD of taxable income from FX conversion alone. But if rates move and you only get 0.63, your actual taxable income is $37,800—a $1,200 difference. If you hadn't forecasted the FX impact, you'd be surprised come tax time.
When you use Cashierr to track your revenue and expenses, you can log these FX movements as they happen and see their tax impact in real time. Instead of discovering FX losses at tax time, you're monitoring them throughout the year, which means you can adjust your quarterly targets and cash flow plans accordingly.
The Australian exchange rate doesn't move randomly. It's influenced by the Reserve Bank of Australia's monetary policy, interest rate differentials, commodity prices (especially iron ore and coal), and global risk sentiment.
Understanding these drivers helps you make better assumptions about forward exchange rates in your forecast. For example, if the RBA is signaling interest rate cuts while the US Federal Reserve is holding rates steady, the AUD is likely to weaken over the next quarter. That means your USD invoices will be worth more AUD—a tailwind for your forecast.
Conversely, if commodity prices are rising (which typically strengthens the AUD), you might assume a headwind on USD conversion.
The RBA's bulletin on the Australian economy provides regular updates on economic conditions and monetary policy. While it's not a crystal ball, it gives you context for your forward rate assumptions. A solo developer who understands that the RBA is likely to cut rates in the next quarter can reasonably assume a weaker AUD and build that into their forecast.
Similarly, Treasury's analysis of RBA foreign exchange intervention shows how the RBA manages exchange rate volatility. This context helps you understand whether current exchange rate moves are temporary (and likely to reverse) or structural (and likely to persist).
None of this is guesswork. It's informed forecasting based on economic fundamentals. And it's only possible if you're thinking in AUD.
Some solo developers work with clients across multiple regions: US, UK, EU, Australia, Canada. Managing three or four different currencies simultaneously is complex, but the principle remains the same: forecast everything in AUD, your home currency.
Here's how to handle it:
This feedback loop is where Cashierr's AI agents add real value for solo developers. Instead of manually tracking conversion rates and adjusting assumptions, an agent can monitor your actual FX outcomes, flag when your assumptions are drifting from reality, and suggest updated forward rate assumptions for next quarter. That's the difference between a static spreadsheet forecast and a living, breathing forecast that adapts to reality.
Once you're forecasting in AUD, you can build a real business health dashboard. Here are the metrics that matter:
Quarterly Revenue Target (AUD): Your forecast, adjusted for FX assumptions and risk buffers.
Actual Revenue to Date (AUD): Your invoices converted at actual rates. This tells you whether you're on track.
Gap to Goal (AUD): The difference between your target and actual. If you're $5,000 AUD short of your quarterly target with two weeks left, you know exactly how much work you need to land to hit your number.
Client Concentration (%): What percentage of your AUD revenue comes from each client? If one client is 60% of your revenue, that's a risk flag.
FX Impact (AUD): How much did currency movements help or hurt your actual revenue vs. your forecast? If you forecasted $50,000 AUD and invoiced $75,000 USD (which should convert to $50,000 AUD at your assumed rate), but actually received $48,000 AUD due to FX headwinds, that's a $2,000 FX impact. Tracking this tells you whether your FX assumptions are realistic.
Monthly Burn Rate (AUD): How much do you spend each month in AUD? Combined with your revenue forecast, this tells you your runway and whether you need to adjust rates or workload.
Each of these metrics is meaningless if you're mixing currencies. A "$60,000 quarterly target" in USD doesn't tell you whether you're on track if your expenses are in AUD. But a "$90,000 AUD quarterly target" with "$75,000 AUD actual to date" tells you everything. You're 83% of the way there. You need to close $15,000 AUD more in deals. You know exactly where you stand.
Here are the traps that catch solo developers who don't forecast in AUD:
Mistake 1: Forecasting in USD, budgeting in AUD. You tell yourself, "I'll earn $60,000 USD this year," but you budget your living expenses in AUD. When the AUD strengthens and your $60,000 USD is worth less, you're suddenly short of cash. You didn't realize you had a currency risk.
Mistake 2: Assuming exchange rates stay constant. You invoice a client $15,000 USD at 0.65 rates and assume you'll get $23,000 AUD. Three months later, rates have moved to 0.62, and you only get $22,200 AUD. You're surprised and annoyed, but you shouldn't be—currency moves are normal.
Mistake 3: Not accounting for FX losses in tax planning. You invoice $60,000 USD, assume it converts to $92,000 AUD, and budget your tax liability accordingly. But when you actually convert it, you get $90,000 AUD due to FX headwinds. Now your tax bill is based on $92,000, but your cash is only $90,000. You're short.
Mistake 4: Conflating revenue and cash flow. You tell yourself you earned $50,000 this quarter, but you haven't converted your USD invoices yet. You don't actually have the cash. When you finally convert, you get less than expected due to FX movements. Now you're short for expenses.
Mistake 5: Not monitoring client concentration in AUD. You have three clients: one pays $30,000 USD, one pays £15,000 GBP, one pays $20,000 AUD. You think they're balanced. But in AUD terms, the USD client might represent 55% of your revenue, the GBP client 30%, and the AUD client 15%. You're heavily exposed to USD. If that client leaves, you're in trouble.
Each of these mistakes is preventable if you forecast in AUD from the start.
Let's say you're starting from scratch. You've never forecasted before, or you've been forecasting in USD and want to switch. Here's how to build your first AUD forecast:
Step 1: List your current clients and revenue. Write down every client, how much they pay, in what currency, and how often. Be honest about whether the amount is fixed or variable.
Step 2: Assign exchange rate assumptions. For each non-AUD currency, pick a forward rate. If you're conservative, assume rates move 2–3% against you. If you're optimistic, assume they move 1% in your favor. Write down your assumption and the date you made it. You'll revisit this quarterly.
Step 3: Convert everything to AUD. Multiply each client's revenue by your assumed rate. Sum it all up. That's your quarterly revenue forecast in AUD.
Step 4: List your quarterly expenses. How much do you spend on software, hosting, equipment, professional services, and living expenses each quarter? Add it all up in AUD.
Step 5: Calculate your quarterly net. Revenue (AUD) - Expenses (AUD) = Net. Is it positive? If not, you need to increase revenue or decrease expenses. How much would rates need to improve, or clients need to increase, for you to hit your target?
Step 6: Set a quarterly target. Based on your net, what's a realistic revenue target for next quarter? Maybe you want to earn $100,000 AUD. Write it down. That's your goal.
Step 7: Build a simple tracker. Create a spreadsheet (or use a tool like Cashierr) that tracks:
Step 8: Reflect and adjust. At the end of the quarter, ask:
Forecasting in AUD isn't just about currency math. It's about clarity. It's about knowing, with real precision, whether your business is healthy or struggling. It's about being able to answer the two questions every solo programmer needs answered:
How much should I be making this quarter? When you forecast in AUD, you have a real answer. Not "$60,000 USD," which is ambiguous. But "$90,000 AUD, assuming average FX rates of 0.65 and accounting for a 2% conversion headwind." That's a target you can actually work toward.
How's the business actually doing? When you track revenue and expenses in AUD, you can see exactly where you stand. You know your client concentration. You know your FX exposure. You know whether you're on track or falling behind. You can make decisions based on data, not gut feel.
Most solo developers operate on gut feel. They invoice clients, convert the money eventually, and hope it adds up to enough at the end of the year. Some years it does. Some years it doesn't. They're flying blind.
Forecasting in AUD changes that. It forces you to be intentional about currency exposure, realistic about FX assumptions, and honest about your actual cash flow. It's not complicated, but it requires discipline. You have to sit down, make assumptions, write them down, and then track actual results against those assumptions.
That discipline is what separates solo developers who are running a business from solo developers who are just taking on work. It's the difference between knowing you're making progress and wondering whether you're on track. It's the difference between being surprised by tax bills and knowing exactly what you owe. It's the difference between having a plan and hoping things work out.
And it all starts with a single decision: forecast in AUD, the currency you actually live in, spend in, and pay tax in. Not USD, not GBP, not the currency your biggest client uses. AUD. Your currency. Your home. Your business.
Once you make that shift, everything else becomes clearer. The spreadsheet makes sense. The quarterly targets become achievable. The business health metrics actually tell you something useful. You stop being surprised by FX movements and start planning for them. You know your real quarterly revenue, not an inflated number in a foreign currency.
That's not just better forecasting. That's actually knowing how your business is doing. And for a solo developer juggling code, clients, and invoices, that clarity is worth more than any productivity tool or automation hack.
Start with your first AUD forecast this week. List your clients, pick your forward rate assumptions, convert everything to AUD, and set a real quarterly target. Then track it. Every week, update your actual revenue and expenses in AUD. At the end of the quarter, you'll know exactly how you performed and why.
That's the foundation of a business you can actually manage. And it all comes down to forecasting in the right currency.
Master the 3-bucket system for solo developers: operating, tax, and profit accounts. Stop leaving money on the table and make tax season painless.
Master your solo dev finances in 30 minutes every Friday. Track revenue, expenses, goals, and cash flow with this step-by-step ritual.
Master revenue forecasting by tracking just 5 metrics. Learn which data points drive 80% of forecast accuracy for freelance developers.