Politics

Caplin Brings One-Tap Confirmation to OTC Commodities Trades

A corporate treasurer can agree a commodity hedge with a bank and still have to print, sign and return the confirmation before the bank’s records catch up. Caplin Systems has extended its Client Portal to let corporate and institutional counterparties approve or dispute over-the-counter commodities trades electronically. The November 18 release takes a workflow already used in foreign exchange and applies it to another part of the dealing relationship. For a bank weighing the investment, the important question is what happens to the trade record after the client taps the screen.

Caplin says the portal automatically updates connected reporting systems. That addresses two separate sources of delay. One is the time spent waiting for a signed document to come back. The other is the work required to locate the right trade and enter the response into the bank’s systems. A faster customer interface solves the first problem. The second depends on whether the response reaches every team that relies on it, with enough detail to identify the transaction and establish precisely what the customer accepted.

Where a Confirmation Break Starts

Consider a company that hedges a commodity purchase and agrees several transactions with the same dealer in one week. Its treasury team may remember the commercial purpose of each hedge, while its accounts team organises outgoing payments by date. Caplin’s portal provides high-level trade summaries and reports organised by transaction and payment date. Those views serve different questions. A treasurer can look for the deal just agreed, while a colleague investigating a particular day’s cash flows can begin with the payment schedule.

A discrepancy can emerge even when both sides recognise the trade. If the customer expects a different payment date, a quick approval would simply move a bad record downstream. The option to dispute the confirmation therefore carries as much operational weight as the approval button. Back-office staff have an operations blotter and an audit trail. The test for a bank is whether staff can follow a disputed item from the original terms through the correction and identify which version the customer eventually approved.

There is a precedent in BidFX’s integration of Finastra’s confirmation matching service. Matching asks whether records describing a transaction agree. Client approval captures a counterparty’s response to the terms it sees. These functions can complement each other. An operations team still needs to know whether the approved record corresponds to the version used for reporting and payment, particularly if someone amended the booking while the customer was reviewing it.

What Banks Can Reuse From FX

Banks already offering the portal for FX have a starting point in their customer access arrangements. Caplin supports single sign-on and an open API, as well as multiple product types and execution styles. A corporate client using one bank for currency and commodity hedges could have fewer places to check for outstanding confirmations. On the bank side, common access makes it easier to offer a consistent process, although the people authorised to confirm a currency transaction may differ from those responsible for a commodity hedge.

Other FX projects illustrate why the underlying permissions matter. Société Générale and Capitolis automated FX options novations, where the parties must establish consent to a change in counterparty. The commercial event differs from confirming a new hedge, but both require a record of who agreed to what. Meanwhile, work on FX workflows around shorter securities settlement cycles illustrates the cost of discovering an exception late, when fewer people or funding options may be available to resolve it.

“Banks’ corporate clients shouldn’t have to print, sign and return physical documentation to confirm trades,” said Tom Darvall, Caplin’s managing director. His broader proposition is that banks could grow commodities hedging volumes with the same back-office resources. Whether that holds will depend partly on the existing mix of work. A desk that spends hours chasing routine confirmations has a different opportunity from one where most staff time already goes into a small number of complex disputes.

How to Measure the Time Saved

A bank can assess that proposition by following a cohort of comparable trades before and after rollout. Time to customer response is one measure. Time to a consistent record across connected systems is another. Separating routine approvals from disputed confirmations would show whether the bank has removed administrative work or merely concentrated it in an exception queue. The age of the oldest unresolved items can tell managers more about operational risk than a faster average across thousands of straightforward approvals.

Caplin puts deployment at as little as a few months, depending on integration requirements. Its earlier white-label digital asset desk launch also highlighted the appeal of buying infrastructure that can sit behind a bank’s own distribution. In commodities, the critical implementation decisions include linking customer identities to the right legal entities, mapping trade identifiers across systems and defining who owns an exception when an update fails. An audit trail has practical value when staff can use it to reconstruct that sequence without searching several inboxes.

Confirmation also has a specific place in the trade lifecycle. It records agreement on terms. Subsequent obligations can include payments and other contractual steps. Projects such as Capitolis’s use of LCH FX Smart Clearing address a different question about counterparty exposure. For commodities teams, keeping those stages distinct makes the business case easier to evaluate. The first evidence of success would be fewer trades awaiting agreement and less work reconciling the records that depend on it.