Calder & Vance International Sanctions & Compliance Counsel

Licensing & Authorizations · OFSI

OFSI vs Australia: Payment authorisations: what businesses miss

A payment is due. The counterparty's account is frozen under UK financial sanctions. Your compliance team pulls the OFSI licensing guidance. Meanwhile, your Australian subsidiary faces the same counterparty under the Autonomous Sanctions regime – and the rules are not the same document, not the same test, and not the same regulator. Which authorisation route applies? What does each regime actually require? Miss the distinction and you face either a blocked transaction or an unlicensed payment: both carry serious consequences.

Payment authorisations under OFSI (the Office of Financial Sanctions Implementation, the UK's financial-sanctions licensing authority) and Australia's Autonomous Sanctions regime follow structurally similar but operationally divergent paths. Both require a licence before funds move to or through a designated person. The tests for eligibility, the timelines, and the risk of enforcement diverge in ways that routinely catch cross-border businesses off guard. As of May 2026, neither regime operates a blanket general licence for ordinary commercial payments touching a designated counterparty.

This analysis sets out the payment-authorisation regimes side by side, identifies the points of divergence that matter most in practice, and explains when a business operating across both jurisdictions needs dedicated counsel before it acts.

What governs payment authorisations in each regime?

Under OFSI, the legal authority for financial-sanctions licensing sits in the Sanctions and Anti-Money Laundering Act (SAMLA) and the relevant thematic sanctions regulations made under it. OFSI administers the licensing function within HM Treasury. It issues both specific licences (case-by-case authorisations for a defined transaction) and, in certain programmes, general licences (standing authorisations that permit a defined category of activity without a separate application). For payment authorisations specifically, the relevant question is whether an applicable general licence already covers the payment – and if not, whether the transaction falls within one of OFSI's enumerated licensing grounds, such as basic needs, legal fees, or prior contractual obligations.

In Australia, the governing instrument is the Autonomous Sanctions Act and the regulations made under it. The Department of Foreign Affairs and Trade (DFAT) administers the regime, including licensing. DFAT does not operate the same tiered general-licence architecture as OFSI. Instead, exemptions are built into the regulations themselves, and a separately granted permit is required for payments that do not fit an existing exemption. The absence of an explicit general-licence layer means that Australian businesses often find there is no standing authorisation to check first – the analysis begins with whether a permit is needed at all.

Two things follow immediately. First, a payment that is permitted under an OFSI general licence is not necessarily permitted in Australia, and vice versa. Second, the applicable country regime in each case is the one that governs the party making the payment, the intermediary processing it, and – in some cases – the currency in which it is denominated.

How does each licensing test work in practice?

OFSI assesses specific-licence applications against defined grounds. The applicant must identify the applicable licensing ground and demonstrate that the payment falls squarely within it. Common grounds for commercial payments include: prior contractual obligations (a payment due under a contract signed before designation), legal costs, and in some programmes basic needs or extraordinary expenses. OFSI will not authorise a payment simply because the parties want to close a transaction. The burden is on the applicant to make the case, and OFSI's published guidance sets out what supporting documentation is expected.

In our cross-border practice, the most common error at this stage is conflating eligibility with entitlement. A business that believes it has a strong commercial reason for the payment may still be refused if the reason does not map onto a recognised ground. Have you identified not just why you want the payment made, but which specific licensing ground it falls under?

Australia's permit framework is less granular in its published licensing grounds. DFAT retains significant administrative discretion. The published guidance identifies broad categories – humanitarian needs, legal services, and pre-existing contractual obligations are recognised – but the assessment is more bespoke and the processing times are not codified to the same degree as OFSI's published benchmarks. Practitioners advising on DFAT matters note that early engagement with the authority, and a clear factual presentation of the payment's purpose, materially affects the outcome.

One further structural difference: OFSI has published enforcement guidance and a monetary-penalties regime with a clear statutory basis. DFAT's enforcement posture on licensing violations is less transparently documented, but the absence of published penalty guidance does not mean the risk is lower. Criminal liability for unlicensed transactions exists under the Australian regime, and that exposure is not bounded by a civil-penalty cap in the way OFSI's civil process is.

The position above covers the standard case. Your facts – the counterparty, the goods, the route, the regime in play – change the analysis.

For a confidential review of a payment authorisation question under OFSI or the Australian regime, contact Calder & Vance at info@caldervance.com.

Where do the regimes diverge on ownership and control?

Both regimes apply an ownership and control test to determine whether a non-listed entity is caught because a listed person owns or controls it. The threshold and the mechanics differ in ways that affect whether a payment is prohibited before the licensing question even arises.

Under OFSI and the relevant UK sanctions regulations, a non-listed entity is treated as controlled by a designated person where that person owns it 50 percent or more, or where the person holds the right to appoint a majority of the board, or otherwise controls its activities through other means. The UK ownership test is closer to the EU position than to the US. Control – not just formal ownership – is the question. A shareholder with a 45 percent stake who effectively directs corporate decisions may bring an entity within the prohibition even below the ownership floor.

Australia applies a similar structure. A legal person is subject to the regime's restrictions where a designated person owns or controls it. The control concept in the Australian regulations follows the DFAT guidance, which focuses on practical control over assets and decisions rather than a fixed numerical threshold. This creates a parallel risk: where OFSI and the Australian regime both apply, a business must satisfy both control tests before concluding that a counterparty is unaffected by the designation.

In a recent matter, a financial institution processing a cross-border payment identified that its counterparty's parent was listed under a UK thematic programme. The entity itself was not on any list. We mapped the ownership chain under both OFSI and DFAT tests. The UK analysis turned on control rights embedded in a shareholders' agreement, not the headline shareholding percentage. The Australian analysis required a separate review of Australian-law corporate documents. The two analyses produced different interim conclusions before the full picture was assembled. The lesson: a single screening pass does not substitute for a regime-by-regime ownership assessment.

What are the procedural timelines and reporting obligations?

OFSI's published processing benchmarks give applicants a workable expectation. Routine specific-licence applications are processed within a published target window; complex or novel applications take longer. Applicants who require an urgent determination can request expedited review, though the threshold for urgency is applied carefully. The licensing decision may be a grant, a refusal, or a grant with conditions – each of which has a different downstream consequence for the payment in question.

OFSI also imposes reporting obligations that directly interact with the licensing process. A person who knows or suspects that they hold funds or economic resources belonging to a designated person must report that to OFSI. Importantly, the reporting obligation is distinct from the licensing obligation. A business that identifies a potential match must report regardless of whether it intends to apply for a licence, and the report should be made without delay. Failure to report is itself a potential offence, separate from any unlicensed payment.

Australia's regime includes an equivalent reporting obligation. A person who holds a freezable asset belonging to a designated person must notify DFAT. The notification timeline is set in the regulations. As with OFSI, the obligation bites at the point of knowledge or suspicion, not only after a confirmed match. In our experience, businesses operating across both jurisdictions sometimes identify the UK obligation but miss the Australian parallel, particularly where the asset is held in an Australian-incorporated entity that is not the primary compliance focus.

Processing times at DFAT for permit applications are not published in the same structured way as OFSI's benchmarks. This makes timeline planning harder for transactions with Australian nexus. We regularly advise clients to build a contingency window into any transaction that requires a DFAT permit, rather than relying on an assumed timeline derived from the OFSI experience.

If a transaction has already been flagged, or a filing has been refused, an early review can preserve options that narrow with time. Write to us at info@caldervance.com.

What is the US extraterritorial risk for payments touching both regimes?

A payment that is properly authorised under both OFSI and the Australian regime may still carry US sanctions exposure. OFAC's jurisdiction extends to US persons wherever they are located, to transactions in US dollars processed through the US correspondent-banking system, and to entities organised under US law regardless of where the transaction is booked. This extraterritorial reach means that a payment cleared under an OFSI licence and a DFAT permit may nonetheless breach US primary sanctions if it involves a person on the SDN List (OFAC's list of Specially Designated Nationals and blocked persons) and is cleared in US dollars.

The 50 percent rule (OFAC's rule treating any entity owned 50 percent or more by one or more blocked persons as itself blocked) applies here with mechanical precision. Where an OFSI analysis has concluded that control – rather than formal ownership – is the relevant test, the OFAC analysis may reach a different conclusion. A 48 percent stake held by an SDN does not trigger the OFAC 50 percent rule, but may still trigger the OFSI control test. A business optimising only for the UK result may unknowingly clear a payment that is blocked under US rules.

The cross-regime interaction creates a sequencing imperative: screen under all applicable regimes before any payment moves. Where US dollar clearing is unavoidable, the OFAC analysis is not optional. Currency routing is not a compliance tool; the rules apply to the underlying transaction as well as to the payment leg.

What a cross-border business should do about payment authorisations: a decision sequence

The practical question for a business with payment obligations touching both the UK and Australian regimes is not which regime to comply with, but how to satisfy both simultaneously. The following decision sequence reflects the approach we take in practice.

Step one: identify the applicable regimes. Map every jurisdiction with a connection to the transaction – the payer's jurisdiction of incorporation, the payee's jurisdiction, the currency and clearing route, the governing law of the underlying contract, and the location of any intermediary. Each connection is a potential jurisdiction of obligation.

Step two: run the designation check under each applicable list. Screen the counterparty and its full ownership chain against the OFSI Consolidated List, the Australian Autonomous Sanctions List, and the OFAC SDN List as a minimum. Apply the ownership and control test under each regime's standard, not a single composite test.

Step three: assess whether an existing general licence or exemption covers the payment. Under OFSI, check whether a general licence applies before proceeding to a specific-licence application. Under the Australian regime, check the regulatory exemptions first. If either regime is covered by an existing authorisation, document the basis before processing the payment.

Step four: where a specific licence or DFAT permit is required, build the timeline. OFSI's application process runs to a published benchmark; DFAT's does not. Structure the transaction timeline to accommodate the slower of the two processes, and notify counterparties of the regulatory position without transferring funds before authorisation is received.

Step five: comply with reporting obligations in parallel. The UK and Australian reporting obligations run independently of the licensing process. Both must be satisfied as soon as the relevant knowledge or suspicion arises. Do not hold the report pending resolution of the licensing question.

Situation A – the payment touches a UK-connected entity under an OFSI programme with an applicable general licence: the fastest route is to confirm the general licence scope, document the reliance, and process the payment with the documentation on file.

Situation B – the payment requires a specific OFSI licence and a DFAT permit: both applications must run in parallel; the longer process governs the transaction timeline; neither can be assumed from the other's outcome.

Situation C – the transaction also has a US dollar component: the OFAC analysis must be resolved before either the OFSI or DFAT outcome, because an unlicensed US-dollar payment cannot be remedied by UK or Australian authorisation after the fact.

Common mistakes and risk flags in cross-regime payment authorisations

In our practice, the same patterns recur across matters where a payment authorisation has gone wrong. Each represents a risk that is avoidable with adequate pre-payment analysis.

The first is assuming that a UK OFSI general licence covers the Australian position. It does not. General licences are issued by OFSI under UK law; they have no force under the Australian regime. A business that relies on an OFSI general licence without separately checking the Australian position is exposed on the DFAT side of the transaction.

The second is ignoring the currency routing question. A cross-border payment in US dollars processed through a US correspondent bank is subject to OFAC review regardless of the UK and Australian analysis. Businesses that focus their licensing work on the primary-relationship regimes sometimes overlook this entirely.

The third is treating the reporting obligation as optional pending the licensing outcome. The reporting obligation bites at the point of knowledge or suspicion. It does not await a licensing decision. A business that holds a report until it knows whether the licence will be granted may already have missed the reporting window.

The fourth – and perhaps the most underappreciated – is assuming that the control test under OFSI and Australia will produce the same answer for the same entity. They will not always do so. A shareholders' agreement that gives a designated person control rights under UK law may be analysed differently under Australian law. The two analyses require separate work; they cannot be run as one.

Is your compliance programme designed to run both analyses independently, or does it treat them as a single check?

Related practices

Frequently asked questions

Where do the regimes diverge on payment authorisations?
OFSI operates a tiered licensing structure – general licences and specific licences – with published grounds and benchmark processing times. Australia's DFAT regime uses regulatory exemptions and individual permits, without the same published-grounds architecture. The control test for capturing non-listed entities also differs: OFSI applies a control-focused test, while DFAT follows a similar but separately documented standard. Most critically, an authorisation granted by one regime does not carry over to the other; each must be satisfied independently.
Which regime is stricter on payment authorisations?
Strictness depends on the specific ground being asserted. OFSI's published licensing grounds provide defined routes, but the evidentiary standards are applied closely. The Australian regime is less prescriptive in its published guidance, which gives DFAT more administrative discretion and makes outcomes less predictable. For a business seeking certainty on a commercial payment, OFSI's defined grounds are more transparent; for a payment with a genuine humanitarian or contractual basis, both regimes generally provide a route. Applying both simultaneously is the operative challenge, not choosing between them.
What should a cross-border business do about payment authorisations?
The first step is to identify every regime with jurisdiction over the transaction – by reference to the parties' locations, the currency, the clearing route, and the contractual governing law. The second is to run the ownership and control analysis under each regime's specific test. The third is to assess available authorisations (general licences, exemptions, or permit grounds) before processing any payment. The fourth is to comply with reporting obligations as soon as knowledge or suspicion arises, regardless of the licensing position. Businesses with regular cross-border payment flows should have a written procedure covering all four steps for each applicable regime.

Talk to Caldervance

For a scoped view of your exposure, contact info@caldervance.com.

Discuss your matter

This publication is general information and does not constitute legal advice. For advice on your situation, contact info@caldervance.com.