The Sovereign Gateway: Unifying Australia’s Big 4 Banking Core

"The ABA file sitting on your desktop is a loaded gun."

In the modern Australian financial stack, there is a dangerous gap between your ERP and your Bank.

On one side, you have a sophisticated cloud ERP like Dynamics 365 Business Central or Finance. On the other, a trillion-dollar banking mainframe.

In the middle? A text file. Downloaded to a laptop, unencrypted, editable by anyone with Notepad, and manually uploaded via a web browser.

This is the Silo Tax. It creates friction, invites internal fraud, and breaks the chain of custody.

At Demiton, we do not believe in "connectors." We build Sovereign Infrastructure. We have engineered a unified Host-to-Host (H2H) mesh that orchestrates the flow of capital between your ERP and Australia’s "Big 4"—CommBank, Westpac, NAB, and ANZ.

The Problem: Four Banks, Four Languages

While every major Australian bank supports "Host-to-Host" connectivity via SFTP, they all speak different dialects.

For a Solution Architect or internal IT team, building and maintaining these integrations is a nightmare of edge cases:

1. Westpac (iLink): The gold standard for Corporate Online, but it demands heavy lifting on PGP encryption. Key exchange and rotation schedules must be managed precisely, or payments fail.
2. Commonwealth Bank (CommBiz): Requires strict file naming conventions (timestamps unique to the second) and rigid character set enforcement (Latin-1). Send a UTF-8 character, and the mainframe rejects the batch.
3. NAB (Direct Link): Notoriously strict on network security. They reject connections from dynamic IP addresses common in Azure/AWS serverless environments.
4. ANZ (Fileactive): Supports sophisticated "Hybrid" workflows, where files are pushed via SFTP but require human authorization in the Transactive Global portal.

The Solution: The Universal Adapter

Demiton abstracts the complexity of the Big 4 into a single, immutable configuration layer. You define your intent in the ERP ("Pay Vendor Batch A"), and our engine handles the cryptographic handshake and protocol negotiation specific to your bank.

• We handle the PGP: Our cryptography micro-service encrypts your payment file in-memory. Unencrypted financial data never touches a disk.
• We handle the Network: Demiton operates a Sovereign Cloud NAT. All traffic originates from a reserved, static Australian IP address that we whitelist with the banks on your behalf.
• We handle the Logic: We map the reconciliation files (BAI2) directly back to your General Ledger, ensuring zero-touch reconciliation.

Why Not Just Use an Aggregator?

You might ask: "Why not use Stripe or Airwallex to pay bills?"

Because you lose the float.

Aggregators act as a wallet. You have to move money out of your Tier 1 bank account (losing interest and offsetting capabilities) into their tech wallet to make a payment.

Demiton is not a wallet. We do not touch your money. We are the armored tunnel that the money travels through.

1. Keep your Capital: Your funds stay in your CommBank or Westpac interest-bearing account until the second they are paid.
2. Keep your Relationship: You maintain your direct commercial relationship with the bank, ensuring your credit lines and lending history remain intact.

The Architecture of Trust

We built Demiton for the "Paranoid CFO."

• Data Sovereignty: All keys and data reside in australia-southeast1 (Sydney).
• Immutable Logs: Every file transmission is hashed (SHA-256). We prove mathematically that the file the bank received is identical to the file the ERP generated.
• Governance: Approvals happen in Microsoft Teams before the file is even generated.

Stop manually uploading files. Stop risking internal fraud.

Build your financial operations on infrastructure, not administrative tasks.

Pilot the Banking Mesh →