This article is written by Cobase
Starting a career in treasury can feel intimidating. The numbers are big, the consequences are real, and the room is often filled with people who have been doing this work for decades. Decisions made in treasury do not stay theoretical for long. They affect cash availability, business continuity, and trust across the organization. In this environment, credibility is not optional. It is foundational. Without it, even the best analysis struggles to carry weight. For early career professionals, that reality becomes clear very quickly. Credibility is something that must be earned early, built carefully, and reinforced consistently over time.
Ed Farrow, Senior Treasury Analyst at JCB, understands this reality well. From the start of his career, he saw that credibility in treasury does not come from sounding confident or holding the right job title. It comes from how you show up every day. From being prepared when questions arise, from following through on commitments, and from taking responsibility for the details others rely on. Much of this work happens quietly, without recognition, and often when no one is watching. Yet over time, those small, consistent actions shape how colleagues, stakeholders, and partners learn to trust you.
Treasury sits close to risk in a way few other functions do. Cash, liquidity, funding, and financial exposure are not abstract ideas or long term considerations. They influence whether a business can operate smoothly from one day to the next. When treasury works well, the impact is felt across the organization, even if it is rarely visible.
Because of this proximity to risk, trust becomes essential. Stakeholders need to believe that treasury understands what it is doing, often before results are visible or confirmed. They rely on treasury to see problems early, assess them accurately, and act in the best interest of the business. That trust is built over time, through consistent decisions and reliable outcomes.
Unlike many other roles, treasury frequently deals with decisions that cannot be easily reversed. Once a payment is made, a hedge is placed, or funding is secured, the consequences are real. There is little room for trial and error. That reality makes credibility a requirement, not a bonus. Without it, treasury’s input struggles to carry the weight it needs to influence decisions.
Many early career treasurers encounter a surprising dynamic. Responsibility often arrives before authority. You may find yourself monitoring cash positions, supporting funding activities, or helping manage financial exposures long before you feel fully confident in your own expertise.
This gap can feel uncomfortable. You are expected to contribute meaningfully while still learning the role. Yet it is precisely in this space that credibility begins to take shape. How you handle responsibility, even when you are still finding your footing, leaves a lasting impression.
Showing care, asking the right questions, and taking ownership of your work matters more than projecting certainty. Over time, these early experiences become the foundation on which trust is built, both in your own confidence and in how others perceive you.
Ed Farrow joined JCB straight from his academic studies, stepping directly into a global treasury environment with real responsibility from the outset. There was no extended adjustment period or theoretical runway. From day one, his work connected to real decisions with real consequences for the business.
Treasury at JCB spans international operations, liquidity management, and financial risk. That means cash flows across borders, exposure to market movements, and decisions that support the day to day functioning of a global organization. Being part of that environment early in his career made it clear that treasury is not an abstract discipline. It is practical, time sensitive, and closely tied to how the business operates.
The learning curve was steep, and expectations were high. There was little room to observe from the sidelines. Instead, Ed was expected to engage, learn quickly, and take ownership of his responsibilities. That intensity shaped how he approached his role and how seriously he took the trust placed in him.
Rather than rotating through multiple functions or learning treasury at a distance, Ed learned by doing. He experienced treasury from the inside, seeing how decisions moved from analysis to action and how those actions affected the wider business.
This hands on exposure helped him understand not just what needed to be done, but why it mattered. Cash visibility was not just a report. It was a prerequisite for confident decision making. Risk management was not a theoretical exercise. It was about protecting the business from real uncertainty.
Learning treasury this way shaped how Ed thought about credibility from the start. Being close to the impact of decisions made it clear that credibility is built through care, attention to detail, and a strong understanding of the business context behind the numbers.
One of the first challenges many early career treasurers encounter is perception. Age can work against you, especially in a function where responsibility is high and experience is often equated with credibility. In meetings with banks, auditors, or senior stakeholders, assumptions are made quickly. Experience is often assumed rather than tested, and credibility is not automatic.
Ed experienced this dynamic early on. Sitting at the table with people who had spent years, sometimes decades, in finance, he became aware that his voice carried weight only when it was backed by substance. Speaking louder or trying to appear more senior was not the answer. Instead, he focused on being right, being prepared, and being reliable.
Over time, that approach changed how others responded. Questions became more open. Trust increased. Credibility grew not because of how long he had been in the role, but because of how consistently he delivered. It was a reminder that in treasury, perception shifts slowly, but it shifts decisively when trust is earned.
In treasury, mistakes rarely stay small. A missed payment, an incorrect assumption, or a delayed decision can have immediate and visible consequences. Cash does not wait, markets do not pause, and errors often ripple beyond the treasury function itself. This reality adds pressure, particularly when you are still learning.
For early career professionals, that pressure can feel intense. Every decision seems to carry extra weight. The margin for error feels narrow, and the cost of getting something wrong can feel personal as well as professional.
That pressure, however, can shape you in different ways. It can undermine confidence if it leads to hesitation or fear of making decisions. Or it can sharpen focus, encouraging greater preparation, attention to detail, and accountability. Ed learned to channel that pressure into discipline. By treating each task with care and learning from small missteps, he built resilience alongside credibility.
A job title might open the door, but it does not keep you in the room. In treasury, credibility is built through delivery rather than designation. People remember whether you follow through on commitments, whether your numbers are accurate, and whether your insights stand up when questions are asked.
Ed learned this quickly. Early on, he saw that credibility was not something you achieved once and then carried forward automatically. It had to be earned repeatedly, often in small and unremarkable moments. A report delivered on time. A question answered clearly. A risk flagged early enough to make a difference.
Over time, these moments add up. Colleagues begin to trust your input. Stakeholders rely on your assessments. Banks respond with confidence. Credibility becomes less about how you introduce yourself and more about how others speak about you when you are not in the room.
In treasury, being visible is far less important than being consistent. Loud contributions or dramatic interventions rarely build lasting trust. What does build trust is showing up prepared, delivering what you promise, and doing it again and again without drawing attention to yourself.
Ed focused on reliability rather than recognition. He made sure his work was thorough, his assumptions were sound, and his follow through was dependable. Over time, this approach created a quiet reputation. One that did not rely on self promotion or constant visibility.
That kind of reputation travels quickly and organically. People remember who they can rely on, especially in moments of pressure. In treasury, consistency speaks louder than visibility ever could.
Preparation is one of the most effective ways to build credibility early in treasury. Knowing your data, understanding the drivers behind it, and being able to explain it clearly makes a noticeable difference. In a function where decisions are often challenged and scrutinized, preparation creates confidence, both for you and for the people relying on your input.
Ed focused on being meticulous from the start. If a question came up, he wanted to already know the answer or, at the very least, know exactly where to find it and how quickly he could get there. That level of readiness reduced uncertainty in conversations and made interactions more productive. Instead of scrambling for information, he could focus on discussing implications and next steps.
Over time, this approach built trust. Stakeholders began to rely on his numbers, not because they were perfect, but because they were well understood and thoughtfully presented.
The shift from reacting to anticipating is subtle, but it is powerful. Early in a career, it is natural to respond to questions as they come. With experience and preparation, that response turns into anticipation.
When treasury professionals begin to think one step ahead, trust grows naturally. Questions are addressed before they are asked. Risks are flagged before they escalate. Conversations move faster because the groundwork has already been done.
This is where credibility starts to compound. Each prepared interaction builds on the last, creating a sense of reliability that others come to depend on.
Curiosity plays an important role in how credibility develops over time. Asking thoughtful questions shows engagement and care, not uncertainty. Ed approached his work with a genuine desire to understand how things fit together, not just within treasury, but across the wider business.
By staying curious, he learned why certain processes existed, where assumptions came from, and how decisions affected other teams. That broader understanding strengthened his judgment and improved the quality of his contributions. Curiosity helped him move beyond execution and into insight, which is where credibility truly takes hold.
In treasury, preparation builds trust, but curiosity sustains it.
Curiosity is often underestimated in treasury, especially early in a career. There can be a fear that asking questions will be seen as a lack of knowledge or confidence. Ed experienced the opposite. He found that asking thoughtful, well considered questions helped him understand the business more deeply and make better decisions.
Good questions show engagement, not weakness. They signal that you care about getting things right rather than simply getting them done. By asking why a process existed, how a number was derived, or what assumptions sat behind a decision, Ed gained insight that went beyond surface level execution. Over time, this curiosity strengthened his judgment and made his contributions more relevant.
Asking better questions also builds trust. Colleagues recognize when someone is genuinely trying to understand the bigger picture. That effort creates stronger collaboration and leads to better outcomes for the business.
Some of the most meaningful gains in credibility come from small, quiet improvements. Not every contribution needs to be visible or celebrated to be valuable. Ed focused on identifying areas where processes could be simplified, automated, or made more reliable.
Automating a manual step, cleaning up a report, or reducing reconciliation effort may seem minor in isolation. But these changes remove friction from daily work. They save time, reduce errors, and make treasury operations smoother for everyone involved.
Often, these improvements go unnoticed in the moment. There is no announcement or recognition. Yet they change how people experience working with you. Over time, colleagues associate your work with clarity, efficiency, and reliability. That association becomes a powerful form of credibility, built quietly and sustained through consistent action.
Technology played an important role in helping Ed reduce risk in day to day treasury work. Manual processes leave room for mistakes, especially when volumes are high and time pressure is constant. By automating repetitive tasks, Ed was able to remove many of those points of failure.
Automation reduced errors and increased consistency. Numbers became more reliable, processes more predictable, and outputs easier to trust. That reliability translated directly into credibility. When stakeholders no longer needed to double check the data, conversations shifted. Time was spent discussing implications rather than validating inputs.
Consistent systems create confidence. When information can be relied on, trust in the people behind it grows naturally.
Reducing manual effort did more than improve accuracy. It changed how time was spent. Technology created space to step back and think rather than constantly react. That space allowed Ed to analyze trends, challenge assumptions, and look ahead instead of focusing solely on execution.
With fewer hours spent on repetitive tasks, he could contribute at a higher level. Discussions became more forward-looking. Insights became more strategic. Over time, this shift moved his role beyond execution and into influence.
Technology did not replace judgment. It amplified it. By freeing time and reducing noise, it allowed human thinking to take center stage, which is where credibility continues to grow.
Bank relationships depend heavily on trust. In treasury, credibility with external partners is not built through impressive language or complex explanations. It is built through reliability. Doing what you say you will do, when you say you will do it, matters more than sounding confident or sophisticated.
Ed approached these relationships with care and consistency. He focused on being dependable, accurate, and clear in every interaction. If he committed to providing information, he delivered it on time. If assumptions changed, he communicated openly. If there was uncertainty, he acknowledged it rather than overpromising.
Over time, this approach shaped how banks and stakeholders responded. Conversations became easier and more constructive. There was less friction and more collaboration. Trust reduced the need for constant verification and created space for more meaningful dialogue. Credibility, once established, made every interaction smoother.
One of the most formative aspects of Ed’s career was being trusted with responsibility early on. That trust was not always comfortable. It brought pressure and raised expectations, but it also accelerated learning in a way few other experiences could.
Being responsible for real outcomes forces growth. It sharpens focus and highlights gaps in understanding quickly. Ed learned by doing, by owning his work, and by understanding the consequences of his decisions. That responsibility pushed him to prepare more thoroughly, think more critically, and act with greater confidence over time.
Training provides knowledge, but responsibility builds judgment. Being trusted early shaped Ed’s development and reinforced a core lesson of treasury. Credibility grows fastest when responsibility is real and accountability is shared.
Many early career professionals believe that credibility comes from projecting confidence or seniority before they truly feel it. In treasury, this instinct is understandable. The environment is serious, the stakes are high, and no one wants to appear unprepared. Yet trying to sound more experienced than you are often backfires.
In treasury, overstating certainty can damage trust quickly. Stakeholders value accuracy and honesty more than polished delivery. When something is presented with too much confidence and later proves incorrect, credibility takes a hit that is difficult to recover from. Ed learned that it was better to be precise than impressive.
Honesty, paired with preparation, goes much further. Saying you will confirm an answer, explaining assumptions clearly, or acknowledging uncertainty shows maturity rather than weakness. Over time, people learn that your input can be trusted because it is grounded in reality, not performance.
Credibility is not a milestone that you reach and move past. It is a daily practice that is built and reinforced through small, consistent actions. Every interaction, every report, and every decision contributes to how others perceive you.
Ed’s experience shows that credibility grows through consistency, curiosity, and care. It grows when you prepare thoroughly, ask thoughtful questions, and take responsibility for your work. It grows when you follow through, communicate clearly, and remain accountable even when things are challenging.
In treasury, credibility compounds quietly. Over time, those daily habits turn into trust, and that trust becomes influence. Not because it was demanded, but because it was earned.
Earning credibility early in treasury is challenging, especially in a function where the stakes are high and experience is often assumed to be the primary currency. Yet it is also one of the most valuable foundations a professional can build. Ed Farrow’s perspective shows that credibility does not come from job titles, age, or confidence alone. It is built through preparation, reliability, and a genuine commitment to doing the work well, even when that work goes unnoticed.
Treasury rewards those who earn trust quietly. It rewards consistency over performance, judgment over appearance, and care over speed. Over time, that trust compounds. Conversations change, responsibilities expand, and influence grows naturally. A seat at the table is not demanded or granted all at once. It is earned through daily actions, thoughtful decisions, and the willingness to carry responsibility long before recognition follows.
Treasury Masterminds is a community of professionals working in treasury management and those interested in learning more about topics such as cash management, foreign exchange management, and payments. To register and connect with Treasury professionals, click [HERE] or fill out the form below to get more information.
This article is written by our partner, FIS
Receivables finance (RF) has long been a cornerstone of corporate finance, enabling businesses to convert outstanding invoices into immediate liquidity. By selling their receivables to a funder, companies may access cost-effective funding and reduce risk, while investors may gain exposure to short-duration, diversified assets at a competitive return.
However, as recent events surrounding First Brands Group illustrate, this structure remains vulnerable to risks beyond credit, such as fraud. These vulnerabilities highlight the need for greater scrutiny and the adoption of new technologies.
Fraud in RF transactions typically manifests through misrepresentation of receivables quality, double pledging of assets and fabrication of invoices. These risks arise because RF relies heavily on the integrity of the originator’s reporting and servicing processes. If invoices are falsified or pledged to multiple financiers, the asset base becomes compromised, exposing investors and lenders to significant losses.
The First Brands case underscores these vulnerabilities. The U.S. auto parts supplier, which filed for Chapter 11 reorganization in September 2025, allegedly engaged in widespread financial misconduct, including doctoring invoices and double-counting receivables to secure billions of dollars in financing.
Several market features of RF contribute to fraud risk:
These factors can make RF particularly vulnerable when governance fails or liquidity pressures incentivize aggressive accounting.
The First Brands saga has accelerated calls for digital transformation in RF oversight. Advanced technology and reporting platforms can reduce fraud risk through:
The collapse of First Brands is a cautionary tale for all stakeholders in the RF ecosystem. While RF remains a powerful liquidity tool, its resilience depends on effective governance and technological safeguards. Platforms that deliver real-time transparency, automated controls and immutable records are no longer optional: They are essential to maintaining trust and confidence in this asset.
In essence, resilient frameworks are often built on digital efficiency and the irreplaceable insight of experienced practitioners.
As institutional investors continue to seek exposure to trade finance assets and corporates aim to unlock working capital, the combination of advanced technology and human expertise within complex RF structures will help to shape the market’s future.
While digitalization may stand as the frontline defense against fraud, it’s equally vital to maintain effective human oversight by having seasoned professionals conduct independent reviews and engage in regular dialog with originators and funders.
This interplay between technological innovation and expert judgment helps ensure that not only are anomalies flagged automatically, but also the nuances of complex transactions are properly understood and addressed. In essence, resilient frameworks are often built on digital efficiency and the irreplaceable insight of experienced practitioners.
Treasury Masterminds is a community of professionals working in treasury management or those interested in learning more about various topics related to treasury management, including cash management, foreign exchange management, and payments. To register and connect with Treasury professionals, click the button below.
This article is written by Nomentia
Why are manual treasury processes expensive?
Manual treasury processes become expensive because they require recurring effort to collect balances, prepare payment files, update forecasts, check approvals, and reconcile data. Even when each task seems manageable, the combined impact can reduce efficiency, slow down decision-making, and increase operational risk.
Treasury teams are used to making imperfect systems work.
A spreadsheet here. A bank portal there. A local ERP export from one entity, a payment file from another, and a cash forecast that still depends on email updates from the business. None of these workarounds may look dramatic on their own. In many organisations, they are even seen as normal.
The problem is that “normal” can become expensive.
Manual treasury operations rarely create one large, visible cost line. Instead, they create a pattern of hidden costs: time spent collecting data, delays in decision-making, duplicated effort, payment exceptions, outdated forecasts, missed visibility, and control gaps that only become urgent when something goes wrong.
That is why treasury automation ROI should not only be discussed as a technology question. It is also an operating model question. How much time does treasury spend managing the process instead of managing cash, liquidity, payments, and risk?
The cost of manual work is often underestimated because it is distributed across people, entities, systems, and routines.
A treasury analyst may spend hours preparing a daily cash position. A regional finance team may manually upload payment files. Another person may validate bank data, check approvals, update forecasts, or investigate why one bank statement does not match the expected format.
Each task may be manageable. Combined, they create a significant operational burden.
This is also why many teams struggle to build a cash forecasting business case. The value of better forecasting is not limited to “faster reporting”. It is the value of better decisions: knowing earlier where liquidity is needed, reducing dependency on outdated data, improving confidence in funding decisions, and giving leadership a clearer view of what may happen next.
External research points in the same direction. PwC’s 2025 Global Treasury Survey notes that treasury teams are under pressure to improve cash visibility, cost efficiency, and risk management, while leading organisations increasingly adopt real-time liquidity tools, AI-enhanced forecasting, and centralised payment models. HSBC also highlights that cash flow forecasting has remained a key treasury priority, reflecting the need for precise and timely forecasts in a volatile environment.
In other words, manual treasury processes are not only inefficient. They can slow down the organisation’s ability to respond.
Cash visibility is one of the clearest examples of hidden treasury cost.
When balances are collected manually across banks, accounts, currencies, and entities, treasury may technically have the data, but not necessarily in time to act on it. The team may know yesterday’s position, but not today’s. It may have a consolidated view, but only after several people have updated files, checked bank portals, and reconciled different formats.
That delay matters.
Without timely visibility, companies may keep too much cash idle in one place while borrowing elsewhere. They may struggle to identify trapped cash. They may make liquidity decisions based on incomplete information. They may also spend valuable time explaining numbers instead of improving them.
Nomentia positions its Smart Treasury Suite around visibility, control, and predictability across payments, cash, liquidity, and risk, integrating with ERPs, banks, and other systems. For companies operating across multiple banks and entities, that integration layer is not just technical infrastructure. It is the foundation for turning fragmented data into usable treasury insight.
Payments are another area where manual processes can appear cheaper than they really are.
At first glance, uploading files through bank portals or managing payments across local workflows may seem acceptable. The team knows the process. The banks are connected somehow. Payments are executed. Work continues.
But payment operations carry a high cost when they depend on scattered portals, inconsistent approvals, manual file handling, and local exceptions.
The hidden costs include time spent preparing and checking payment files, resolving format issues, validating approvals, tracking payment statuses, and answering questions from subsidiaries, AP teams, banks, and auditors. More importantly, weak payment control can increase exposure to duplicate payments, missed cut-offs, fraud attempts, and compliance issues.
This is where payment automation benefits become easier to explain. Automation is not only about faster payment execution. It is about standardising the process, improving traceability, reducing manual intervention, and making payment control easier to prove.
Forecasting is often where manual treasury processes become most visible to leadership.
The CFO does not necessarily see how many files were collected, how many emails were sent, or how many adjustments treasury made before the forecast was ready. But the CFO does see when the forecast is late, when confidence is low, or when the numbers change without a clear explanation.
A manual cash forecast can still be useful. Many experienced treasury teams are excellent at working around incomplete data. But as the business grows, expands into new markets, adds banks, or inherits systems through acquisitions, the limits become harder to ignore.
Forecasting depends on data quality, timing, ownership, and repeatability. If treasury spends too much time gathering inputs, it has less time to analyse drivers, challenge assumptions, and model scenarios. A forecast that takes days to prepare may already be outdated when it reaches decision-makers.
This is why the business case for treasury automation should include both time savings and decision quality. Faster data collection is valuable. But the larger value often comes from giving treasury more time to interpret what the numbers mean.
Manual controls are often built around expertise. The team knows which approvals are needed, which files need checking, which bank deadlines matter, and which exceptions require escalation.
That works until complexity increases.
As more entities, banks, users, and payment types are added, control becomes harder to manage consistently. Processes may differ across countries. Approval rules sit outside the system. Audit trails may require manual reconstruction. Exceptions depend on individual knowledge rather than embedded workflows.
In a stable environment, this may go unnoticed. During growth, restructuring, audit, staff changes, or periods of financial pressure, it becomes a risk.
The Nomentia Treasury Trends Report 2026 describes treasury teams facing pressure to deliver real-time insights, stronger controls, and more strategic input, often while dealing with fragmented systems and limited IT support. The report is based on 384 treasury and finance leaders across the Nordics, DACH, Benelux, and the UK.
That is the reality many treasury teams recognise: expectations are rising faster than operational capacity.
A strong treasury automation ROI discussion should not begin with software features. It should begin with operational impact.
From there, TMS cost savings become easier to frame. The value may come from fewer manual hours, lower operational risk, more efficient payment execution, improved cash visibility, reduced dependency on spreadsheets, or stronger audit readiness.
The most useful business case is not a generic promise that automation saves money. It is a structured estimate of where the organisation currently loses time and where better treasury processes could create measurable improvement.
Treasury Masterminds is a community of professionals working in treasury management or those interested in learning more about various topics related to treasury management, including cash management, foreign exchange management, and payments. To register and connect with Treasury professionals, click the button below.
This article is written by Cobase
For an industry built on numbers, banking has always struggled with something more basic: speaking the same language.
Ask any treasury team trying to connect to banks globally and you’ll hear a familiar frustration. The expectation is simple – money is digital, banks are global, so connectivity should be straightforward. In reality, it rarely is. What looks like a plumbing issue is something deeper: a system that was never designed to be unified in the first place.
Modern banking didn’t emerge as a coordinated network. It grew in fragments. National systems were built to serve domestic economies, shaped by local regulation, infrastructure, and political priorities. Payment schemes evolved independently. Messaging formats were defined in isolation. Even basic concepts like how to confirm a payment or report a balance took different forms depending on where you looked.
The result is not just variation, but incompatibility.
SWIFT is often held up as the closest thing to a global standard. And in one sense, it is. It created a common messaging layer that banks across the world could use. But it never standardised what happens after the message is sent. Two banks can receive the same SWIFT instruction and process it in entirely different ways – different cut-off times, different validations, different interpretations.
This is where the idea of “bank connectivity” begins to unravel. The challenge is not just reaching a bank, but dealing with how each bank behaves once you do.
Over the years, the industry has made repeated attempts to smooth this out. None have fully succeeded. Not because the technology wasn’t good enough, but because the incentives never aligned. Banks compete. Regulators don’t coordinate globally. And legacy systems – often decades old – continue to run critical infrastructure that no one is willing to replace lightly.
The expectation of a unified system persists. But it’s built on a false premise.
Banking isn’t fragmented because something went wrong. It’s fragmented because that’s how it was built.
Few ideas in banking have generated as much optimism in recent years as APIs.
They arrived with the promise of simplicity. Clean, modern interfaces. Real-time data. Standardised access. Compared to the heavy, file-based integrations of the past, APIs looked like a reset moment, a chance to finally make bank connectivity behave like the rest of the digital world.
And in some ways, they delivered.
Large banks began exposing endpoints for payments and reporting. Developers could interact with bank systems without navigating layers of legacy protocols. In controlled environments, things worked exactly as advertised.
But step outside those environments, and the picture changes.
APIs in banking are not a single standard. They are dozens, sometimes hundreds, of individual implementations. Each bank defines its own structure, its own authentication methods, its own limits. Even when two banks claim to follow the same framework, the differences show up quickly – in edge cases, in error handling, in performance under load.
The regulatory push behind open banking added momentum, but also confusion. PSD2 created a baseline, but it was never designed for corporate treasury. It focused on retail use cases, with limited scope for bulk payments, complex approval flows, or multi-entity structures. For large organisations, it solved a small part of a much bigger problem.
Meanwhile, neo-banks and aggregators entered the picture, offering simplified access and faster onboarding. They improved the experience at the edges, particularly for account opening and basic transactions. But they didn’t remove the need to engage with traditional banks. In many cases, they simply added another layer to manage.
The result is a familiar pattern in financial infrastructure. New technology doesn’t replace the old – it accumulates around it.
APIs didn’t eliminate fragmentation. They made it more dynamic.
From the outside, bank connectivity looks deceptively simple. Payments go out, balances come in, and everything appears to move through a single system.
What’s less visible is the machinery underneath.
For companies operating across multiple countries, connectivity is not one connection, it’s dozens. Each bank brings its own requirements. File formats differ. Security models vary. Some require certificates, others tokens. One bank processes payments in batches, another in real time. Cut-off times shift by region, sometimes by product.
Even within the same bank, behaviour can change depending on the channel used. An API might support one set of payment types, while host-to-host supports another. Documentation doesn’t always reflect reality. Test environments behave differently from production. Exceptions are handled inconsistently.
None of this is unusual. It’s the normal state of the system.
This is why, despite all the talk of innovation, older methods remain firmly in place. Host-to-host connectivity – direct, file-based integration – continues to handle a large share of corporate payments. It’s not elegant, but it’s predictable. It does what it’s supposed to do, at scale, without surprises.
In certain markets, local standards dominate. EBICS, for example, is deeply embedded in parts of Europe. It works not because it’s globally relevant, but because it reflects the specific needs of those markets. In those contexts, it often outperforms more “modern” approaches simply by being consistent.
And then there’s SWIFT, still acting as the global fallback. When no direct connection is available, SWIFT is usually there. Not perfect, not always efficient, but broadly accepted.
Put all of this together, and a pattern emerges. There is no single best way to connect to banks. There is only a set of trade-offs.
The real work is not choosing one method, but managing all of them at once, and making them behave as if they were one.
That work increasingly sits in a layer most corporates never set out to build, but inevitably do: an orchestration layer that absorbs differences between banks, channels, and formats, and presents something coherent on top.
This is where platforms like Cobase operate.
Rather than trying to standardise banks themselves, Cobase standardises the interaction with them. It connects across SWIFT, EBICS, APIs, and host-to-host channels, translating between formats, normalising data, and embedding bank-specific behaviour into a central system. A payment instruction created once can be converted automatically into whatever each bank requires. Data coming back – balances, statuses, confirmations – is aligned into a consistent structure.
The complexity doesn’t disappear. It is relocated.
Instead of sitting in day-to-day treasury operations spread across teams, spreadsheets, and manual fixes, it is contained within a controlled layer designed to handle it.
Because in the end, the hardest part of bank connectivity is not building connections.
It’s making them invisible.
Treasury Masterminds is a community of professionals working in treasury management or those interested in learning more about various topics related to treasury management, including cash management, foreign exchange management, and payments. To register and connect with Treasury professionals, click the button below.
