Mark-to-market for FX forwards: what auditors want

The basics, briefly

A forward contract is an executory commitment. On day one, neither side owes the other anything. By day 30, if AUD/USD has moved, one side is sitting on a paper gain and the other on a paper loss. The accounting question is what that paper position looks like on the balance sheet, and what evidence you need to back it up.

Under AASB 9 (the Australian implementation of IFRS 9) and the fair value framework in AASB 13, a forward contract is a derivative measured at fair value through profit or loss by default. Mark-to-market isn't optional. The only thing that changes is whether the gain or loss flows through P&L immediately or sits in OCI under hedge accounting designation. That choice has real consequences when the auditors arrive.

Below is what auditors actually look at when signing off on forward MTM, the documentation they expect to see, and the issues that typically slow down a year-end close.

How the MTM is calculated

Auditors don't expect you to be a quant. They do expect you to explain, in plain terms, where the number came from.

The standard approach for a vanilla forward is straightforward present-value maths. You take the forward rate at inception, the contract notional, the contract maturity, and the prevailing market forward rate for the same maturity at reporting date. The mark-to-market is the discounted difference between the two settlement amounts.

For a forward bought at rate F0 with notional N in foreign currency, due at time T:

MTM (in domestic currency) = (N / Ft − N / F0) × DF

Where Ft is the current market forward rate for the original maturity date and DF is the discount factor for that maturity. The discount factor uses the relevant currency's risk-free curve, in practice usually a swap curve.

That's the mechanical answer. The audit-relevant questions sit one layer up.

The first thing auditors actually check

The first audit question is almost never "is the maths right." It's "where did the inputs come from, and can you reproduce them."

Three things matter in practice.

The price source needs to be independent of whoever booked the trade. If your treasurer's broker is also providing the year-end mark, that's a control issue regardless of whether the number is correct. Auditors expect the MTM input rates (spot, forward points, discount curves) to come from a recognised market source, separately from the dealing relationship.

The valuation date must be consistent. Reporting-date close-of-business prices, captured at the same time across all instruments. Mixing London close on some trades with Sydney close on others creates a reconciliation nightmare that auditors will pull on.

The methodology must be documented before year-end, not constructed during the audit. A short valuation policy stating which curves you use, which day-count convention applies, how you treat bid/offer spreads, and which entity captures the rates is enough. A few pages, signed by the CFO. Nobody is asking for a quant model document. They're asking for evidence that the same method is applied consistently.

Hedge accounting changes the conversation

Default MTM treatment runs every fair value movement through P&L. For a business hedging a forecast import payment, that's operationally awful. You book a forward to stabilise margin, and the forward's quarterly MTM swings show up as P&L volatility before the underlying transaction has even happened. The very volatility you were trying to remove ends up in the income statement anyway, just one row up.

Hedge accounting fixes this. Designate the forward as a cash flow hedge of a forecast foreign-currency payment, document it properly, demonstrate effectiveness, and the effective portion of the MTM movement parks in OCI (the cash flow hedge reserve) until the hedged transaction occurs. At that point it gets recycled into P&L alongside the underlying purchase, and the matching is what gives you the smooth margin you actually wanted.

Auditors care a lot about hedge accounting because the bar for designation is high and the consequences of getting it wrong are also high. A forward you intended to designate but documented inadequately gets defaulted back to FVTPL, and you may have to restate prior-period OCI movements through profit and loss. That conversation is uncomfortable.

What auditors look for in hedge documentation

Hedge accounting under AASB 9 requires documentation at the inception of the hedge. Not at year-end. Not when the auditor asks. At inception, meaning the same day or close to it as the trade is booked.

A compliant designation memo identifies five things.

First, the hedging instrument: the forward contract itself, with trade date, notional, currency pair, maturity, contract rate, and counterparty.

Second, the hedged item: the specific forecast transaction or recognised exposure. For a forecast import, that means the supplier, the expected payment date, the expected currency amount, and the basis on which it qualifies as "highly probable." Usually that's a confirmed purchase order or supply agreement.

Third, the type of hedge: cash flow hedge, fair value hedge, or net investment hedge. For supplier payments, it's almost always a cash flow hedge.

Fourth, the risk management objective and strategy. A short paragraph explaining why this hedge is being taken, consistent with a board-approved or management-approved hedging policy. Auditors will ask for the policy. If you don't have one, draft one before they arrive.

Fifth, the effectiveness assessment methodology. Under AASB 9 the rigid 80-125% bright-line test from the old standard is gone, but the requirement to demonstrate an economic relationship between the hedging instrument and the hedged item, and the absence of credit-risk dominance in that relationship, remains. Most SME-scale hedge programs use a critical-terms-match approach. The forward has the same notional, currency, and approximate maturity as the forecast payment, so the relationship is self-evident.

The hedge ratio also needs stating, usually 1:1 for a critical-terms-match hedge where the notional of the forward matches the notional of the forecast payment.

A board-approved template for this memo, used consistently across all hedge designations, is the single most useful piece of documentation a finance team can have. Auditors will sample two or three designations and check the templates were completed contemporaneously. If the metadata on the file shows it was created the day before the auditor arrived, that's a finding.

Effectiveness testing

Two pieces of effectiveness testing matter at year-end.

Prospective testing demonstrates that the hedge is expected to be effective going forward. For a critical-terms-match cash flow hedge, this is qualitative. The terms match, the economic relationship is intact, the forecast transaction remains highly probable. A short note confirming this, signed at each reporting date, is sufficient.

Retrospective measurement quantifies the actual ineffectiveness for the period. The dollar-offset method is the most common: compare the change in fair value of the hedging instrument to the change in fair value of the hedged item attributable to the hedged risk. Any mismatch is the ineffective portion, which goes through P&L. The effective portion sits in OCI.

For SME-scale hedges of supplier payments, ineffectiveness is usually small. The most common sources are timing mismatches (the forward matures a few days before or after the actual payment date), deteriorating credit risk on the hedging instrument, and partial hedges where the notional doesn't perfectly track the underlying.

Auditors will look at your ineffectiveness calculations. If the answer is consistently zero on every hedge, every period, that's a flag. Real hedges have small amounts of ineffectiveness. A clean nil tells the auditor that either the calculation isn't being done properly or the hedged item isn't being measured carefully.

CVA and DVA

Auditors increasingly ask about credit valuation adjustments on derivative positions, even at SME scale. Under AASB 13, fair value must reflect non-performance risk. For a forward that's in-the-money to your business, your counterparty's credit risk reduces the value you can recover if they fail. For an out-of-the-money position, your own credit risk reduces what the counterparty can recover from you.

In practice, for a 90-day forward with a major bank or AFSL-licensed specialist, CVA and DVA are usually immaterial and most SMEs don't book them. But the auditor will want to see that you considered them and concluded they were immaterial, with a documented threshold. A simple memo stating the policy, for example "CVA/DVA adjustments are not booked for forward contracts under 12 months with counterparties rated A- or higher," covers it.

For longer-dated forwards, multi-million-dollar notional, or positions with weaker counterparties, the auditor will expect to see an actual calculation. The standard approach uses CDS-implied probabilities of default applied to expected exposure profiles. Most SMEs in this situation rely on their hedge counterparty or treasury management software to provide the number.

Disclosures under AASB 7

Financial statement disclosures under AASB 7 around derivatives and hedge accounting are extensive, and auditors work through them as a separate checklist.

The notional amounts of derivatives by type and maturity bucket. The fair values, separated into asset and liability positions. The fair value hierarchy classification under AASB 13: forwards are almost always Level 2, because the inputs (spot, forward points, swap curves) are observable but the instrument itself isn't directly quoted.

A reconciliation of cash flow hedge reserve movements: opening balance, gains and losses recognised in OCI, amounts reclassified to P&L (usually to cost of sales or finance costs depending on the hedged item), and closing balance.

Sensitivity analysis showing the impact of reasonably possible changes in FX rates on profit and equity.

Hedge effectiveness disclosures, including sources of ineffectiveness and any hedges that were discontinued during the period.

The auditor will reconcile the disclosures to the underlying ledger and to the bank confirmations. Discrepancies between the back office subledger and the disclosed figures are a recurring problem, usually arising from late-booked roll trades or unwound positions that didn't make it into the cut-off.

Common audit issues

A few patterns turn up year after year.

The biggest is documentation that postdates the trade. A forward booked in March, designated as a cash flow hedge in October when the auditor schedule arrives. AASB 9 doesn't allow that. The fix is contemporaneous documentation, full stop. If you can't get the memo signed within a few days of the trade, you can't designate it.

Second is hedging non-existent forecasts. A business books forwards on assumed future supplier payments, but the supplier orders haven't been placed and the underlying purchase agreements aren't in place. If the forecast isn't highly probable, the hedge designation fails and the forward defaults back to FVTPL. The standard test is whether you have a confirmed purchase order, supply contract, or comparable evidence supporting the forecast cash flow.

Third is over-hedging. The notional of the forward exceeds the notional of the forecast underlying. Only the matched portion qualifies for hedge accounting. The excess sits at FVTPL. Treasury teams sometimes don't realise this until the auditor splits the position.

Fourth is sloppy roll accounting. When a forward is rolled, the closing P&L on the original contract and the opening MTM on the replacement contract need to be tracked separately. Lumping the two together obscures the realised gain or loss and complicates the OCI reconciliation.

Fifth is relying on counterparty MTM statements without independent verification. The bank's number is fine as a starting point. It isn't, on its own, sufficient evidence of fair value. Auditors expect to see the figure independently recalculated, or at least reasonableness-tested against an internal model.

A practical workflow that survives audit

Finance teams that move through derivatives audit smoothly tend to run a similar process.

A hedge policy document, board-approved, that sets out which exposures get hedged, by what instruments, with what tenors, and against what limits. Updated annually.

A standard designation memo template completed at the trade date for every hedge. Stored centrally alongside the dealing confirmations.

A monthly MTM run using independently sourced rates, reconciled to counterparty statements, with any variance over a defined materiality threshold investigated.

A quarterly effectiveness assessment for each open hedge. For critical-terms-match hedges this is brief, but it gets done and gets signed.

A clean derivatives subledger that reconciles to the general ledger and to the bank confirmations. Run monthly, not at year-end.

A disclosure pack drafted in October or November ahead of a June year-end, populated as new positions are added through the period.

A finance team running this process can produce the supporting evidence for any audit question within a working day. A team that isn't tends to spend the audit period in firefighting mode, which is when mistakes get made.

Closing

Mark-to-market accounting for forwards isn't intrinsically complicated, but the audit conversation usually isn't about the maths. It's about whether the documentation, controls, and source data hold up under scrutiny.

The single best investment for a finance team using forwards regularly is the same one that helps with most audit conversations: contemporaneous documentation, independent price sources, a written policy, and a clean reconciliation between the dealing system and the ledger. None of it is exotic, and all of it is what auditors actually want to see.