Independent treasury and FX advisory for commercial and mid-market companies +1 (403) 879 6537 · info@bastioncm.com
Request Free Audit
Home / Currency & Payments
Currency & Payments

Currency and payments workflow support

Improve how your finance team collects, holds, converts, pays, approves, tracks, and reconciles money across currencies and markets.

Global payments operating layerFrom receipt to reconciliation
01
Collect locally

Account details where available

02
Hold currency

Keep balances visible by currency

03
Convert when needed

Link FX timing to exposure

04
Pay suppliers or partners

Use approved payment workflow

05
Reconcile and report

Bring activity back to finance

Treasury control, approval rules, FX timing, settlement visibility
Execution and payments through Ebury

Bastion supports the treasury workflow. Ebury provides the payment and FX infrastructure.

Bastion’s core role is advisory, workflow support, relationship support, and practical FX decision context. Where clients need FX execution, hedging, currency accounts, international payments, collections, or mass payment capability, those services are provided through Ebury Partners Canada Limited.

Ebury provides the regulated platform, onboarding, compliance, payment infrastructure, account and collection capabilities, and money movement. Bastion helps clients connect those capabilities back to the treasury process, including exposure, timing, approvals, reporting, reconciliation, and decision discipline.

Bastion helps finance with

  • Treasury workflow
  • Exposure and FX timing
  • Payment approval process
  • Reporting and reconciliation
  • Relationship support

Ebury provides

  • Regulated platform
  • Onboarding and compliance
  • Payment infrastructure
  • Account and collection capabilities
  • Money movement
Operating workflow

Operate more locally without building a banking footprint in every market.

For companies collecting from global customers or paying international suppliers, the problem is often not just the FX rate. It is the operating friction around account setup, customer payment preferences, deductions, settlement timing, approvals, reconciliation, and visibility.

Through the Ebury platform, clients may be able to use local currency accounts, collection account details or IBANs where available, international and local payment rails, mass payment workflows, and platform reporting. Bastion helps finance teams decide how those capabilities should fit into the broader treasury workflow, including exposure ownership, conversion timing, payment approvals, reporting, and reconciliation.

Currency and payment workflow map

From collection or payment need to approval, FX timing, settlement, and reconciliation.

Money movement
01

Customer or supplier need

Customer receipts, supplier invoices, partner payouts, payroll-style flows, or recurring cross-border obligations.

02

Local account or payment route

Local currency accounts, collection account details, IBANs, or local and international payment rails where available.

03

Currency balance and FX decision

Hold, convert, or time currency conversion based on exposure, liquidity, payment date, and internal policy.

04

Payment release or collection settlement

Execute the approved payment or manage incoming receipts through the supported platform workflow.

05

Reporting and reconciliation

Bring settlement details, fees, payment status, receipts, and FX activity back to finance.

Finance control layer
01

Ownership

Who owns the exposure, payment, collection, or approval decision?

02

Approval

What approvals are needed before conversion or payment release?

03

Timing

When should the team convert, hold, pay, or wait?

04

Evidence

What confirmations, payment details, and audit trail are retained?

05

Review

How does the activity feed reporting, reconciliation, and future decision routines?

Bastion helps design and support the finance workflow around these capabilities. Ebury provides the regulated platform, onboarding, compliance, account and payment infrastructure, and money movement where available.

Capability stack

The payment capability stack.

Currency and payment capability should be organized around how finance actually operates: accounts and collections, FX decisions, payment release, controls, reporting, and integration.

Layer 1

Accounts and collections

Local currency accounts, collection accounts, account details or IBANs where available, so customers can pay in familiar currencies and finance can manage receipts, balances, conversion timing, and reconciliation.

Local collectionCurrency balancesAccount detailsReconciliation
Layer 2

FX and currency conversion

Spot conversions, planned future currency needs, and execution planning where appropriate, reviewed in the context of exposure, liquidity, policy, and payment timing.

Spot FXForward planningExposure timingPolicy fit
Layer 3

Payments and mass payments

International, local, recurring, or high-volume payments where available, including supplier batches, contractor payments, payroll-style workflows, partner payouts, file uploads, API-enabled processes, approvals, and reconciliation.

Supplier paymentsMass paymentsFile uploadsAPI-enabled flows
Layer 4

Platform, controls, and integration

Approved-user platform access, permissions, templates, payment controls, reporting, and planning support for file uploads, API connectivity, ERP, accounting-system, or TMS-style workflows.

PermissionsTemplatesReportingERP and TMS planning
Safety and regulatory context

Put payment capability inside a controlled treasury process.

Payment and account capability only creates value if finance can control how it is used. Bastion helps clients think through ownership, permissions, approval points, provider visibility, settlement evidence, reporting, and reconciliation before payment volume or currency complexity becomes harder to manage.

Access and authority

  • User permissions
  • Approval levels
  • Payment templates
  • Beneficiary review

Execution and evidence

  • Provider visibility
  • Payment confirmations
  • Settlement details
  • FX and fee records

Reporting and review

  • Finance reporting
  • Reconciliation support
  • Exposure review
  • Future process improvement

Execution support is ancillary to Bastion’s advisory and workflow role. The objective is to help finance use payment and FX capability with better visibility, control, and decision discipline.

Use cases

Where this usually helps first.

01

Importers

Situation

Supplier invoices, inventory costs, and payment timing depend on foreign currency.

What improves

Clearer payment routes, FX timing, approval workflow, exposure review, and reporting.

02

Exporters

Situation

Customers pay in foreign currency or prefer local payment details.

What improves

Cleaner collections, foreign-currency receipt visibility, conversion timing, USD/CAD exposure review, and finance reporting.

03

Supplier payments

Situation

Overseas vendors create recurring payment, beneficiary, settlement, and reconciliation work.

What improves

More consistent beneficiary setup, payment templates, approvals, settlement tracking, and reconciliation.

04

Foreign collections

Situation

The business wants to receive in multiple currencies without opening bank accounts in every market.

What improves

Local currency account use, collection account details or IBANs where available, receipt visibility, conversion timing, and reconciliation.

05

Payroll, contractor, or partner payouts

Situation

The team manages recurring cross-border payments to people, partners, platforms, or contractors.

What improves

Batch payment workflow, approval rules, templates, payment tracking, and reporting.

06

Recurring USD/CAD or cross-currency volume

Situation

The business converts currencies regularly but decisions are still reactive.

What improves

A more consistent process for timing, approval, reporting, exposure review, and execution context.

Review your currency and payment workflow.

Find friction before it becomes cost, settlement delay, approval risk, reconciliation noise, or avoidable FX exposure.

Request workflow review