How to make treasury technology work for the business

💲 We simplify Corporate Treasury Concepts - 🎙️ From the podcast Corporate Treasury 101

How to make treasury technology work for the business

Treasury teams face a practical challenge: supporting new ways of doing business without losing control of cash. Additional payment options and sophisticated systems can help, but neither automatically solves the operational problems behind a transaction.

The difficulty often lies between advertised capability and everyday use. A payment may arrive without enough information to reconcile it, while a system may automate routine processes but struggle with the exceptions that treasury still needs to handle.

On Treasury Leaders, treasury professional Simon Ostrozlik, CFA, Group Treasury Manager at ITSP Services GmbH, brings 12 to 13 years of experience across start-ups, mid-sized businesses and global companies. His practical work with cryptocurrencies and treasury management systems provides a grounded perspective on these decisions.

The sections below break down how to connect treasury technology to business requirements, introduce crypto payments with appropriate controls, manage the resulting liquidity, and select a treasury management system that remains useful when operations become difficult.

Solve the cash problem before choosing treasury technology

Technology decisions should begin with the business activity treasury must support. Expansion, changing payment preferences and new financial processes create different requirements, so the starting point is understanding where cash needs to move and why.

Understand how business decisions affect cash

A new market can require additional accounts, unfamiliar currencies and different arrangements with customers or suppliers. Treasury therefore needs visibility of business plans before those requirements become urgent, rather than discovering them through a payment request that existing processes cannot accommodate.

Bring internal stakeholders into the requirements

A treasury management system, or TMS, may also need to serve accounting, tax and other finance processes. Requirements should reflect those connections, including foreseeable needs, rather than treating treasury as an isolated function with a self-contained software purchase.

Relationships matter here as much as functionality. Established contacts across the business make it easier to understand upcoming changes, while external banking relationships can become particularly valuable when conditions become difficult.

Describe the work, not just the feature

A requirement labelled ‘payments’ leaves too much open to interpretation. Some systems expect a bank-ready file from the enterprise resource planning system, or ERP; others can use invoice and supplier data to construct the payment file and select a processing route.

  • Identify the business activity being supported.
  • Map the accounts, currencies and counterparties involved.
  • Include connected finance and IT requirements.
  • Specify the actual processing steps.

This preparation gives selection a practical basis. A useful system is one that supports the required workflow, not simply one that demonstrates the longest list of features.

Add crypto payments only where demand justifies the work

Crypto can provide an additional payment route where suppliers or customers want it. That does not make it a replacement for conventional banking, nor remove the need to establish custody, compliance and reconciliation processes.

Treat crypto as an additional payment route

Dollar-linked stablecoins may offer an alternative where international payments involve intermediary banks, delays or substantial fees. Customer demand can also arise on online platforms, although the practical experience described here points to a relatively small, business-specific share of payment activity.

Choose custody before accepting funds

Self-custody places responsibility for access, passwords, recovery phrases and backups inside the company. Individual or dual-signature arrangements and procedures for staff departures need attention because recovery cannot simply be delegated to a bank’s password-reset process.

A specialist institution or exchange offers another starting point. Ostrozlik recommends this route for initial processing, while noting that know-your-customer checks can resemble bank onboarding and, in his experience, take two to three months.

Build the information channel alongside the payment channel

A blockchain transfer does not necessarily carry the familiar payment details found on a bank statement. Reconciliation may therefore require separate remittance information, a customer profile within a platform or a transaction hash supplied by the payer.

Self-custody also does not remove later compliance requirements. Converting crypto through an exchange can introduce KYC and proof-of-funds checks, so retaining information about the source of receipts remains part of the process.

  • Confirm genuine customer or supplier demand.
  • Choose custody and recovery arrangements.
  • Allow time for provider onboarding.
  • Agree how each receipt will be identified.

The payment route is only ready when funds can be received, identified and accounted for. Transfer capability alone does not establish a workable treasury process.

Control crypto liquidity before balances accumulate

Accepting crypto creates a liquidity decision as well as a payment capability. Treasury needs to establish how much is required for operations, how long balances should remain outstanding and when conversion into fiat makes sense.

Forecast receipts against operational payments

Expected inflows and outflows provide the starting point for deciding what to retain. Where receipts broadly cover upcoming payments, holding an operational balance may avoid unnecessary conversions; a forecast surplus or shortfall calls for a different decision.

Timing matters alongside total volume. Planning several months ahead can help prevent a surplus being converted into fiat only for treasury to buy crypto again shortly afterwards and incur another spread.

Distinguish stablecoins from volatile assets

Dollar-linked stablecoins and Bitcoin should not be treated as identical exposures. Bitcoin’s price volatility makes the size and duration of holdings particularly relevant, while a stablecoin linked to the US dollar introduces a different currency consideration for the business.

The amount retained should reflect operational needs and the company’s willingness to hold that asset. Receiving a cryptocurrency does not, by itself, justify keeping a large balance in it.

Include conversion costs and provider exposure

Conversion fees and spreads belong in the liquidity plan, rather than appearing as an afterthought. Costs depend on the cryptocurrency, transaction volume and commercial agreement, and can be higher than those associated with exchanging major fiat currencies.

Balances held with exchanges also create counterparty exposure. Keeping amounts modest, spreading holdings where appropriate and converting surplus funds can reduce dependence on a single provider without repeatedly exchanging money needed for upcoming payments.

  • Forecast inflows, outflows and timing differences.
  • Retain balances needed for operations.
  • Include conversion fees and spreads.
  • Review exposure to each provider.

The objective is a deliberate operating balance. Forecasting links the payment service offered to customers and suppliers with the liquidity and exposure treasury is prepared to maintain.

Select a TMS that supports payments under pressure

A convincing demonstration cannot establish how a TMS will handle real files, awkward exceptions or urgent failures. Selection needs evidence of practical capability, clear contractual scope and dependable support after implementation.

Test imports, exports and exceptions

Automatic connectivity does not eliminate the need for manual imports. Corporate card balances or investment accounts without a suitable feed may still need to enter the system, while less common ERP systems require detailed integration checks with IT.

Export limits deserve equal scrutiny. Simon Ostrozlik encountered a 10,000-row cap that required multiple extracts for monthly transaction volumes of several tens of thousands, illustrating why apparently basic capabilities belong in selection testing.

Put the required functionality in the agreement

A capability shown during a demonstration may sit outside the modules included in the final contract. Payment types, currencies, import and export formats, and processing responsibilities should therefore be documented explicitly rather than left to an assumption about what a TMS normally does.

Investigate support after the project team leaves

A quick response is not the same as a resolved payment failure. Contract discussions should address support arrangements and escalation, while reference calls should test what happens after implementation, when the dedicated project contact is no longer handling every issue.

A named relationship contact can help when a ticket becomes urgent. Support teams familiar with the customer’s configuration may also avoid the delay of repeatedly reconstructing how the system has been set up.

  • Demonstrate required files and transaction volumes.
  • Confirm included modules in writing.
  • Check post-implementation customer references.
  • Agree an urgent escalation route.

A TMS decision should account for the difficult operating day, not just the successful demonstration. Functional fit and responsive support both belong in the purchasing judgement.

Conclusion

Effective treasury technology connects business activity with controlled cash processes. Its value depends less on novelty than on whether payments, information and operational responsibilities work together.

The first priority is a clear business requirement. Understanding expansion plans, counterparties and connected finance processes gives treasury a sound basis for choosing tools and identifying gaps before they disrupt operations.

The second is operational readiness. Crypto payments need custody arrangements, recovery processes and a reliable way to identify receipts, not simply a wallet capable of receiving funds.

The third is deliberate liquidity management. Forecasting expected payments and receipts helps treasury decide what to retain, what to convert and how much exposure to leave with providers.

A practical next step is to trace one required payment from initiation through reconciliation, including exceptions and support. Any missing capability can then become a specific requirement to test and document before committing to a provider.

FAQs

What should guide treasury technology decisions?

Business requirements should lead, followed by testing of payment workflows, data connections, exceptions and support arrangements.

Does accepting crypto mean replacing conventional payments?

No. It can provide an additional route for customers or suppliers where there is specific demand.

How can treasury reconcile crypto receipts?

Separate remittance information, platform customer records or transaction hashes can help connect a transfer to the correct payer.

Should operational crypto receipts always be converted immediately?

Not necessarily. Forecast outflows may justify retaining an operational balance, subject to the company’s willingness to hold the asset.

What should TMS reference calls cover?

They should test practical system performance and post-implementation support, particularly how urgent payment problems are handled and resolved.

If you liked the article, why not spreading the Treasury word? :)

Leave a Reply

Your email address will not be published. Required fields are marked *