What is Host-To-Host (H2H) Banking Integration?

While H2H remains a de facto standard for high-volume treasury operations, in-house implementation can take months per bank. Modern treasury platforms offer pre-built H2H connections that reduce deployment time while maintaining enterprise-grade security.

Your finance team watches the clock as treasury flows hang in limbo. Manual reconciliation means another few hours before anyone leaves the office. Meanwhile, at a competitor down the street, payments have been flowing automatically between their ERP and banks all day. The difference? Host-to-host integration.

How does host-to-host connectivity work?

Host-to-host (H2H) banking is a direct, encrypted connection between your ERP and bank systems. It lets you process batch payments automatically, skipping the manual portal login entirely. H2H has been the piping behind high-volume treasury operations for decades, though custom built in-house implementations are extensive and time-consuming. Modern treasury platforms now offer pre-built H2H connections that cut deployment time while keeping enterprise-grade security.

When you initiate a payment batch in your ERP, H2H connectivity takes over. Your system generates a payment file containing hundreds or thousands of transactions. That file travels through a secure channel directly to your bank, is processed, and the confirmation flows back to your ERP. No human touches it. No one logs into a portal. No one needs to download CSV at close of business and manually process the file.

Secure file transfer protocol (SFTP) and PGP encryption

For Host-2-host connection, the banking industry uses SFTP (Secure-File-Transfer-Protocol) with PGP (Pretty-Good-Privacy) encryption or other encryption methods as the standard. SFTP creates an encrypted tunnel between your systems and your bank, preventing anyone from eavesdropping on or modifying data in transit.

But SFTP only protects data in motion. Once a file lands on a server, another layer of protection is required. That’s why PGP (or other encryption standards) adds a second layer, protecting data at rest. Even if someone was to get hold of the payment file, they can’t read it without your private decryption key. Banks typically require both protocols for corporate connections, and this dual-layer approach is standard across most tier-1 banking institutions.

Bi-directional communication

H2H isn’t a one-way street. Your company sends large payment files to your bank. The bank then automatically returns bank statements, payment confirmations, and account balances to feed into your ERP. This two-way data flow closes the loop: your financial position thereby updates itself.

Here’s what that may look like in practice: your AP team approves 5,000 supplier payments on Wednesday morning. Those payments execute Thursday. By Friday, your ERP already knows which payments have cleared and which bounced. Your treasury team sees real cash positions instead of guessing based on yesterday’s portal login.

Host-to-host vs. API integration: which is better?

It depends on what you’re doing, not which technology is newer or better.

APIs work well for real-time, single transactions. For example, you might need an instant balance check before releasing a payment? A quick API call tells you yes or no in seconds. You want to verify account details during supplier onboarding? Also easy with an API call. These tasks suit API calls because they’re lightweight, immediate, and event-driven.

H2H wins when you’re moving at a serious volume. For example, think of a mid-market retailer processing, for example, 15,000 supplier payments per week across multiple entities. APIs would trigger 15,000 individual calls while H2H bundles those into optimised batch files that banks are built to handle in bulk.

When you’re settling millions daily, batch processing matters. Your bank’s systems are optimised for it. Your audit trails are cleaner. And you’re not paying per-transaction API fees on industrial volumes.

The strategic advantages of H2H for UK companies

Why a CFO typically signs off on an H2H project:

High-volume batch processing (Bacs and CHAPS)

The UK payment infrastructure runs largely on batch processing. In February 2026, CHAPS processed 4.0 million payments worth £7.8 trillion over 20 settlement processing days, according to Bank of England data.

Your treasury isn’t sending one payment at a time. You may be automating thousands of payroll payments via Bacs, executing high-value supplier settlements through CHAPS, and managing it all from a single ERP connection. H2H gives you the infrastructure to match how UK payment rails actually work.

Achieving true straight-through processing (STP)

Straight-through processing means a payment travels from ERP approval to final bank settlement with zero human intervention. Done properly, STP delivers shorter processing cycles, reduced settlement risk, and lower operating costs. However, only a fraction of B2B cross payments are typically processed this way.

H2H builds the foundation for enabling straight-through processing. As an example, your AP approval in the ERP could trigger payment file generation, secure transmission, bank processing, and automatic reconciliation. Fraud risk could decrease because fewer people touch the transaction. Manual errors could also decrease because automated systems don’t make transcription mistakes. Your team focuses on exceptions instead of routine execution, which is exactly what finance department automation should deliver.

SWIFT and the ISO 20022 migration

Since November 2025, SWIFT’s network has required ISO 20022-compliant messages for cross-border payment instructions, phasing out the legacy MT format. If you’re handling international payments through SWIFT, your H2H infrastructure needs to support this richer, more structured data format.

What does ISO 20022 actually give you? Better data parsing for increased automation, potentially enabling higher straight-through processing rates, and improved reconciliation. The companies that prepared early have built H2H connections that handle ISO 20022 natively, have been able to use regulatory change as an operational advantage.

The hidden challenges of building H2H in-house

Every bank may require a separate implementation also depending on payment rail and usecase. It could be that Lloyds may use formats such as pain.001 files for Bacs transfers. HSBC could have different field requirements for CHAPS. Barclays might need specific certificate management. With all these individual requirements, different formats and rails, your IT team will need to become experts in bank-specific quirks instead of working on strategic projects.

Security maintenance also never stops. Certificate renewals, encryption key rotations, protocol updates, and vulnerability patches. Miss one, and payments stop flowing. Your treasury team calls IT. IT calls the bank. Two days later, you may have to explain to suppliers why payments are delayed.

ISO 20022 migration also requires constant updates and validation. When format standards change again in the future, you rebuild everything from scratch or pay consultants to do it.

The resource drain adds up. What started as “implement one bank connection” becomes “maintain five connections across three countries while handling four format migrations.” Your CFO approved H2H to save money. Instead, you’ve built an internal banking integration team.

Streamlining bank connectivity with a modern TMS to skip the pain

Modern treasury management systems flip the model. Instead of building point-to-point H2H connections yourself, a treasury platform like Embat maintains pre-built, enterprise-grade connections to major banks. You get H2H functionality without the engineering overhead.

Automated reconciliation without IT burden

Your finance team sees automated reconciliation and full cash visibility straight away. Your IT team doesn’t get pulled into banking integration maintenance. The platform manages ERP connectivity bidirectionally, so payment approvals in your ERP trigger automatic execution through your banks, and confirmations flow back to close your accounting loop.

You get the security and reliability of H2H with the flexibility of a managed service. No more explaining to your CFO why you need three developers dedicated to maintaining bank connections.