This article is written by Cobase
Treasury is often described through its outputs: dashboards, payment files, liquidity forecasts, and risk reports. Clean numbers, clear structures, controlled outcomes. From the outside, it can look almost effortless, as if the work simply produces itself. But none of those outputs exist in isolation. Behind every figure on a screen is a person making a decision in real time. Someone deciding what matters most in that moment, what can wait, and what cannot. Someone assessing risk not just as a percentage or a model, but as a real consequence for the business, the team, and the people who depend on that decision being right.
Those decisions are rarely made with perfect information. Forecasts are never complete, markets move, and circumstances change faster than reports can be refreshed. Still, at some point, a choice has to be made. A payment has to be approved. A position has to be taken. A message has to be sent. Treasury professionals make those calls knowing that their work is often invisible when it goes well, and highly visible when it does not. That quiet responsibility sits behind every stable outcome and every smooth day the business experiences.
Treasury has always been human. It has always relied on judgment, experience, and the ability to stay calm under pressure. We just forgot to talk about that part.
Treasury usually tells its story through structure and precision. It shows up in board decks and management updates as rows of neatly aligned numbers, carefully designed charts, and risks that appear quantified and neatly categorized. Everything looks orderly and under control. From the outside, treasury can seem calm, predictable, almost mechanical in the way it presents itself.
In many ways, that presentation is intentional. Treasury is one of the few functions where success is defined by stability. By things not going wrong. By payments being made on time, liquidity being available when needed, and risks being identified and contained before they become visible problems for the wider business. When treasury does its job well, there is no drama to report. The absence of issues becomes the achievement.
What dashboards and reports do not capture is the thinking that happens before those numbers ever appear on a slide. They do not show the moment a treasurer pauses over a forecast that looks perfectly reasonable on paper, yet feels slightly off based on experience and context. They do not show the decision to pick up the phone and speak directly to a bank rather than send an email, because tone, timing, or nuance mattered in that moment. They do not show the hesitation before approving a transaction that technically meets every requirement, but still raises a quiet internal question.
Treasury rarely documents doubt, judgment, or intuition, because those things do not fit neatly into reports. Yet they are present in almost every decision. Behind the clean outputs and controlled outcomes sits a constant process of questioning, weighing, and choosing. Those human elements may be invisible in the final numbers, but they are what make those numbers possible in the first place.
Treasury often becomes aware of issues long before they surface elsewhere in the business. Before operational teams feel the impact. Before leadership starts asking questions. Before risks appear in reports or dashboards. This early visibility is one of treasury’s greatest strengths, but it also carries a quiet weight.
Seeing something coming changes how you experience your day. Once a potential issue is visible, it cannot be unseen or ignored. It sits in the back of your mind while meetings continue and the business moves on as usual. You track it, question it, and think through possible outcomes, knowing that if it materializes, treasury will be expected to have anticipated it.
That responsibility is not always shared in the moment. Often, it is carried quietly until there is clarity or resolution. Sometimes it is discussed openly. Other times it is held alone, managed through careful monitoring and small, deliberate actions that prevent a problem from ever becoming visible to others.
Treasury work does not always fit neatly into standard office hours. Markets move continuously, time zones overlap, and liquidity does not wait for convenient moments. The rhythm of the role is shaped as much by global timing as it is by internal schedules.
There are early mornings spent checking positions before the business wakes up, making sure nothing has shifted overnight. There are late calls to align across regions, clarify exposures, or resolve issues before the next market opens. Decisions are sometimes made with incomplete information because waiting for perfect clarity is not an option when cash and risk are involved.
Much of this pressure is invisible. When treasury does its job well, the result is stability. Payments flow. Liquidity holds. Risks remain contained. And because everything runs smoothly, the effort behind it fades into the background. The work disappears into the outcome.
In many roles, progress is visible and tangible. Growth is celebrated. Innovation is applauded. Success comes with clear milestones and recognition. Treasury operates differently.
In treasury, success often means that nothing happened. No missed payments. No liquidity surprises. No risk events escalating into real issues. The best possible result is that the business continues without interruption, unaware of how close it may have been to a different outcome.
That creates a unique kind of pressure. The pressure to be right quietly, day after day. To make sound decisions consistently, often without acknowledgement. To carry responsibility without applause. Treasury professionals learn early that recognition is not guaranteed, but responsibility always is. And still, they show up, because stability matters, even when it goes unnoticed.
Treasury decisions are often described as technical, driven by models, policies, and predefined rules. On paper, they appear logical and repeatable. But in practice, they rarely work that way. Even the most structured treasury environments depend on human judgment at critical points, often more than people realize.
Automation can process data, systems can flag exceptions, and frameworks can guide decisions. Still, someone has to decide which assumptions are reliable in the current context. Someone has to determine whether an exception is a one-off anomaly or the early sign of a larger issue. Someone has to weigh the level of risk that feels acceptable, not just according to policy, but according to the realities of the business at that moment.
These choices are rarely black and white. They require judgment that sits somewhere between experience, responsibility, and instinct. That human layer is what turns information into action.
Two treasurers can look at the same data and arrive at different conclusions, and both can be right. The difference often lies not in the numbers themselves, but in the experience behind the interpretation. Past situations, previous outcomes, and learned patterns all influence how data is read and understood.
Context plays an equally important role. A decision that feels reasonable in a stable environment may feel risky during periods of uncertainty. Business dynamics matter, whether the company is growing, restructuring, or navigating external pressure. Timing matters too. The same decision made today or next week can carry very different implications.
This is where the human side of treasury truly lives. Not in spreadsheets or systems, but in the space where frameworks stop providing clear answers and judgment begins to guide the way forward.
Treasury often acts as a buffer between uncertainty and the rest of the organization. It sits at the point where external volatility and internal decision-making meet, translating complexity into something the business can work with. Long before uncertainty becomes visible to other teams, treasury is already dealing with it.
Market movements, changing funding conditions, and shifts in cash flow all arrive first at treasury’s door. These signals are rarely clear or neatly packaged. They come in fragments, trends, and early indicators that require interpretation. Treasury professionals take that uncertainty, assess its potential impact, and decide how much of it the business needs to see and when.
In doing so, treasury carries risk on behalf of the organization. It absorbs fluctuations, smooths out volatility, and creates stability so other teams can focus on operating, growing, and planning. Much of this work happens quietly, without fanfare, but it plays a critical role in keeping the business steady in uncertain conditions.
Treasury operates in a constant balancing act. Move too slowly, and the business risks missing opportunities or becoming constrained by caution. Move too quickly, and exposure increases, sometimes before the consequences are fully understood. Every decision sits somewhere between protection and progress.
Finding that balance cannot be delegated to systems or policies alone. It requires judgment built through experience, confidence developed over time, and an understanding of the broader business context. Treasury professionals are often asked to make calls where there is no perfect answer, only the best possible one under the circumstances.
At times, that means having the confidence to say no when the risk outweighs the reward. At other moments, it means saying yes, even when certainty is limited, because standing still carries its own risks. These decisions are rarely visible once they are made, but they shape how safely and how quickly a business can move forward.
Automation is often discussed as a disruption or even a threat to treasury roles. In reality, many treasurers experience it very differently. For them, automation feels like relief. Not because it removes responsibility, but because it removes friction.
By taking away manual tasks, constant reconciliation, and fragmented processes, technology creates breathing room in the day. It reduces the mental load of chasing data across systems and spreadsheets. It replaces repetition with reliability. What remains is space. Space to think more clearly, to analyze what the numbers actually mean, and to look ahead rather than constantly reacting to what already happened.
Automation does not replace treasurers. It raises expectations for what treasury can contribute. With cleaner data and more consistent processes, the focus shifts from producing information to interpreting it and acting on it.
When systems handle repetitive and time-consuming tasks, people can concentrate on what they do best. Judgment, context, and strategic thinking come back to the center of the role. Decisions are no longer rushed simply because information arrived late or incomplete.
This shift changes how treasury feels day to day. There is less firefighting and fewer last-minute surprises. Preparation replaces constant reaction. Noise fades, and clarity increases. Treasury becomes a function that anticipates rather than responds, supported by technology but guided by human insight.
Over time, this creates a different rhythm of work. One that is calmer, more deliberate, and better aligned with the responsibility treasury carries.
Visibility is often discussed as a technical improvement, something that delivers better data or more accurate reports. In practice, its impact goes much deeper. Visibility changes how treasurers experience their role and how they are perceived by the rest of the business.
When treasurers can see the cash clearly and in a timely way, confidence follows naturally. Decisions become faster because less time is spent questioning the data itself. Conversations shift from explaining what happened to discussing what comes next. Treasury moves away from reporting on the past and begins to actively shape future decisions.
With confidence comes influence. When treasury speaks with clarity and conviction, its voice carries more weight. Leaders listen earlier. Questions become more strategic. Treasury is invited into discussions at the right moment rather than brought in after decisions have already been made.
Over time, this changes the role fundamentally. Treasury stops being the function that reacts too late to manage risk and becomes the one that helps shape the yes responsibly. It provides guardrails without blocking progress and insight without hesitation.
Frameworks, models, and best practices have their place. They provide structure, consistency, and a shared language. But they rarely capture what it actually feels like to carry responsibility in treasury.
They do not teach you how to earn credibility when authority is not automatically given. They do not show you how to sit with doubt when the data is incomplete. They do not explain how to balance risk with opportunity when the answer is not obvious and the consequences are real.
Those lessons are learned through experience. Through listening to others who have faced similar moments. Through stories that reflect the reality of the role, not just its theory. Human treasury stories create connection, recognition, and understanding in a way no framework ever could.
Humans of treasury exists to put people back at the center of the conversation. In a profession often defined by systems, processes, and outputs, it creates space to talk about the individuals who carry the responsibility behind the numbers.
This is not about celebrating perfection or presenting idealized career paths. It is not about promoting tools or highlighting transformation projects. Instead, it is about reflecting the reality of treasury as it is actually lived. A role shaped by responsibility, curiosity, pressure, and pride. A role where decisions matter, even when they happen quietly and without recognition.
Treasury is evolving. It is becoming more strategic and more visible within organizations. Expectations are rising, and the scope of the role continues to expand. At the same time, treasury is becoming more openly human. Judgment, experience, and confidence are no longer hidden behind reports. They are recognized as essential to good decision-making.
The future of treasury is not being built by systems alone. Technology plays an important role, but it does not define the function. What truly shapes treasury is the people behind it. Their choices, their questions, and their willingness to carry responsibility every day are what move the profession forward.
Treasury will continue to modernize. Technology will keep advancing, systems will become more connected, and data will move faster and with greater accuracy. These changes will reshape how treasury work is done and what is expected from the function. Processes will become more efficient, and insight will become more immediate.
But the core of treasury will not change.
Behind every number, there will still be a person making a decision. Someone weighing risk against opportunity. Someone protecting the business while enabling it to move forward. Someone trying to make the right call with the information available at that moment.
No system can replace that responsibility. Models can inform decisions, and technology can support them, but judgment remains human. It always has been.
The future of treasury is not just digital. It is deeply human.
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 [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.
