USD CAD transaction exposure in operating cash plans is the gap between expected and actual cash when some sales or bills are priced in one currency and the balance is held in the other. The main condition is size and timing: small or spread-out flows need only a simple forecast, but flows that cluster in the same weeks need two checks before the plan can be trusted.

Where USD CAD exposure enters an operating cash plan

Many small and mid-sized companies build a cash plan in one currency because the bank account, payroll, and rent all sit in that currency. The trouble starts when a Canadian customer pays in Canadian dollars, or a supplier in Toronto invoices in CAD, and the plan records those amounts at whatever rate the spreadsheet happens to hold. Nothing looks wrong until the month closes and the bank balance disagrees with the forecast.

I find it useful to separate exposure from loss. A receivable in CAD is not a problem by itself. It becomes one when the cash it turns into is smaller or later than the plan assumed. That depends on three things: the rate you used, the day the money lands, and whether you hold any Canadian dollars at all. Each of those is a planning question, not only an accounting one.

The entry point is usually the sales or purchase ledger, not the treasury screen. A bookkeeping system such as QuickBooks, NetSuite, or Sage Intacct records each invoice in the currency it was issued, and that is correct for recordkeeping. A cash plan needs one more step: converting the open items into the currency of the bank account, using an assumption you can name and defend in a meeting.

Revenue recognition adds a second timing gap. Under ASC 606, revenue is recorded when the performance obligation is satisfied, which can come well before the customer pays. For a cash plan that distinction matters. The sale in the books and the dollars in the account are two different events, and currency movement can widen the distance between them.

That is why exposure belongs in the operating cash plan and not only in a year-end review. A plan that ignores it tends to look fine until a month with heavy CAD receipts and heavy USD payroll falls together. The question to ask is whether your plan shows the cash you will actually have, or only the cash you invoiced.

Mapping the USD and CAD flows before you forecast

Before running either check, list every flow that touches a currency other than the one your bank account uses. Include customer receipts, supplier bills, card settlements, and any loan or lease payments in the other currency. A list of ten items is usually more useful than a model with forty variables, because you can see at a glance which flows can move the balance.

To make this concrete, consider a hypothetical Boston software company I will call Hypothetical Co. It bills most US customers in USD and pays payroll and rent in USD. It also has one Toronto customer billed in CAD at about 60,000 CAD per month on net 30 terms. Its USD operating outflows run about 180,000 USD per month, and it keeps a cash buffer of 20,000 USD above its minimum balance. All of these figures are invented for the example.

For each flow, record the currency it is priced in, the currency it settles in, the expected date, and the amount in the plan's base currency at the planning rate. Keep those fields next to the receivables and payables so the plan updates when the ledger does. A separate spreadsheet that only one person opens is where mismatches tend to hide.

Hypothetical Co. mapped its flows like this:

FlowPriced inSettles inTiming source

US customer invoicesUSDUSDPayment terms in the ledger Toronto customer invoicesCADUSD after conversionNet 30 terms and expected pay date US payroll and rentUSDUSDPay calendar and lease schedule US card settlementsUSDUSDProcessor payout schedule

The map also shows which direction the exposure leans. In this case, the main risk is a CAD receipt that buys fewer USD if the Canadian dollar weakens against the US dollar. A company with large CAD bills to pay would face the opposite problem. Knowing the direction tells you which check deserves more of your time.

A map is a snapshot. It covers the exposure already in the ledger, not the Canadian deal that might close next quarter or the currency mix a new customer will bring. Refresh it when the ledger changes, and write down which items are firm and which are only expected.

Check one: do USD and CAD cash arrivals line up week by week?

The first check asks whether the currency flows land in the right order. A CAD receipt that arrives in one week and a USD payroll that leaves in another is harmless, because the company can convert in between. The risk appears when a large outflow falls in a week where the money to pay it has not yet been converted, even though the monthly total looks fine.

Run the check on weekly buckets for the next quarter rather than on monthly totals. A monthly view hides timing. Hypothetical Co.'s month balances at the total, but the weekly view shows that its Toronto receipt of 60,000 CAD arrives in week three, while a supplier run of 30,000 USD goes out on day one of that same week. Conversion takes two business days, so for that stretch the payment is covered only by the USD side of the account. Hypothetical Co. could pay from its buffer, but that would spend money it wants to keep for a late customer.

For each week with a gap, ask three questions. How much of the outflow is not covered by inflows in the same currency? Does the timing sit on a date you control, such as a supplier run you can move? And how long does conversion take once you count bank cut-off times and settlement days? The answers decide whether the fix is a calendar change, a conversion booked earlier, or a draw on cash.

Write the facts for each mismatched week so the review is repeatable:

The outflow amount, its currency, and the date it must leave The inflow that covers it, with its currency and expected date The conversion lead time in business days, including the bank cut-off Whether the payment can move without harm to the vendor or to payroll Who approves a change to the payment calendar

Does this still work? If every week closes with the right currency on hand, the timing is sound and you can move on to the second check. If a week fails, the first fix is usually operational: move a supplier run, ask a customer for an earlier date, or book the conversion before the receipt lands. Changing the planning rate does nothing to a timing gap, so do not reach for the rate first.

Check two: does the planning rate still protect the cash buffer?

The second check asks how much a rate move would cost before the buffer stops covering it. Every cash plan carries a planning rate, a single number used to turn CAD into USD for the whole period. It keeps the spreadsheet readable. It is also a guess, and this check measures how wrong that guess can be before the plan stops working.

Set two rates: the planning rate and a less favorable rate that you can justify for the period. Choose the less favorable rate by reasoning about the business and the currency environment, not by copying one number from one source. Then run the same weekly flows through both rates and compare the closing USD balance. Keep the rates in the plan, with the reason written next to each one.

Using Hypothetical Co. again, the planning rate is 1.30 CAD per USD, so the 60,000 CAD receipt is worth about 46,154 USD. At a less favorable rate of 1.40 CAD per USD, the same receipt is worth about 42,857 USD. The difference is about 3,297 USD for the month. Against a 20,000 USD buffer, that is a cost the company can absorb, and the plan can say so in plain terms.

The picture changes with size. If the Toronto receivable were three times larger, at 180,000 CAD, the same rate move would cost about 9,900 USD, close to half the buffer. If that customer also paid late, the buffer would be carrying both the rate loss and the timing gap at once. That combination, more than either risk alone, is what this check is meant to catch.

A useful way to present this is a short sensitivity line beside the forecast, not a full model. Show the closing balance at the planning rate, the closing balance at the less favorable rate, and the buffer that remains after the worse of the two. A reader can then see in one glance whether the rate assumption is the thing that threatens the plan.

This check does not predict where the rate will go. It tests whether the buffer can absorb a plausible move in the direction that hurts you. If the answer is no, the options are a larger buffer, a deliberate hold on expected CAD receipts, or a smaller CAD exposure from the start. Each option has a cost, and the plan should show that cost next to the others.

What Hypothetical Co. changed after both checks

After the weekly review, Hypothetical Co. found one timing gap and one rate sensitivity. The supplier run that fell on day one of week three moved to day three, after the Toronto receipt had converted. That single change removed the need to draw on the buffer for a payment that was already scheduled.

The rate check showed the buffer could absorb the less favorable rate on the expected receipt. It could not absorb that same move plus a late payment from the Toronto customer. So the company added a simple rule: if a CAD invoice passes its expected date without payment, the finance owner reviews the rate line and decides whether to convert the expected amount early or hold it for a later week.

The change was small and mostly procedural. Nobody needed a new forecasting system. The team kept its existing ledger, added currency and expected-date fields to the receivables list, and reviewed both checks once a month, with the weekly view refreshed whenever a payment slipped.

The result is not a guarantee. The plan still depends on the Toronto customer paying, on the rate staying inside the range the company tested, and on the bank converting when it says it will. The checks reduce surprises. They do not remove the exposure, and the plan says so in its notes.

The more useful outcome is speed. When a payment is late or the currency moves, the team can see which line changes, how much of the buffer is affected, and who approves the response. That is what a cash plan should do, even when the numbers are small.

Who owns the rate assumption and the payment calendar

Recordkeeping and planning are related jobs, but they are not the same job. The bookkeeper records each invoice in the currency it was issued and reconciles the bank account. That work has to be accurate and timely. It does not decide which rate the plan should use or whether a payment should move. Those decisions belong to whoever owns the cash plan.

In a small company, the owner, a controller, or an outside finance lead may hold that role. The question is who signs off on the planning rate and on any change to the payment calendar. If nobody does, the plan drifts. Someone sets a rate during a busy month, and nobody revisits it until the bank statement disagrees with the spreadsheet.

SetupWhere the rate livesWho updates itMain risk

Spreadsheet owned by one personA single cellThe plan ownerA stale rate that nobody else sees Plan linked to the ledger in QuickBooks, NetSuite, or Sage IntacctA rate field tied to the ledger setupThe controller or finance leadRate changes without review if permissions are loose Enterprise planning on SAP S/4HANAA rate table with an approval stepThe finance team, by assigned rolesOverhead a small company may not need

The table compares setups, not products to buy. A single spreadsheet can work for a small set of flows if it has a named owner and a date beside the rate. A linked system helps when the ledger changes often, but only if someone checks what the link carries across. An enterprise planning system is rarely needed to answer the two questions in this article.

Does the setup still work? Ask whether someone other than the plan owner can see the rate, the date it was set, and the reason behind it. If the answer is no, the plan is a private opinion, not a control anyone else can review.

Where an outside finance lead supports the plan, write the scope down: which flows they review, how often, and who makes the final call on the rate. Avoid any arrangement that leaves the rate with whoever entered the last invoice. That is a recordkeeping habit, and it can quietly become a planning decision nobody approved.

Where these two checks stop being enough

Two checks are a tool, and every tool has a boundary. The timing check depends on the expected dates in the ledger being right. If a customer's payment date is a guess, the weekly view is only as good as that guess. Hypothetical Co. handled this by marking each receipt as firm or expected and running the test on both versions.

The rate check tests one move in one direction. It does not show what happens if the currency moves the other way and a USD-priced cost rises for a Canadian supplier, or if several flows move together. A company with heavy exposure in both directions needs a fuller view, perhaps with scenarios set on both sides of the planning rate.

Exposure also changes when the business changes. A new Canadian customer, a Canadian contractor, a second bank account, or a move of prices into CAD all shift the map. A plan built on last quarter's flows can pass both checks and still miss the new exposure. The map has to be refreshed when sales or vendors change, not only at the start of a budget cycle.

The limits of the checks matter too. A passed check does not mean the plan is right. It means the plan survives a specific test under specific assumptions. Write those assumptions down so a reader can see when they stop being true.

Finally, the checks do not answer whether the business should carry that currency exposure at all. Some owners invoice outsourced CFO support in Massachusetts USD to avoid it, and others accept it for a customer they want to keep. That is a commercial decision, and the cash plan should describe its cost clearly instead of hiding it in a rate cell.

What to do with your USD CAD cash plan this month

Start with the map, even if it is rough. List the flows that touch the other currency, mark each one as firm or expected, and attach a payment date. This takes less time than most owners expect, and it shows quickly whether either check is worth running at this stage.

Next, run the timing check on the next quarter in weekly buckets. Mark every week where an outflow in one currency is not covered by inflows in that currency on the same date. For each gap, decide whether to move the payment, convert earlier, or accept a draw on the buffer, cepem.wiki and write down who made that call.

Then run the rate check with a planning rate and one less favorable rate that you can explain. Show the closing balance under both and the buffer that remains. If the buffer holds under the less favorable rate even when the largest receivable pays late, the plan is in reasonable shape for this particular test.

Keep the rates, the date each was set, and the reason for it in one place that more than one person can read. Revisit both checks when a large CAD or USD flow appears, and at least once a quarter. A plan reviewed on a steady schedule is more useful than one that looked perfect on the day it was built.

If the checks show a problem you cannot fix with timing or the buffer, the next step is a decision about the exposure itself. Raise it with whoever owns the business plan before the currency moves, not after.