a Sagan program ยท currently in private beta

Multi-tenant Payments App Agent

Your EDI file contains dual-approved vendor payments in Butterfield's upload format, replacing twelve portal logins with one batch. Bank-detail changes require Approver authorization before the payment runs.
before

Bookkeeper logs into Butterfield Bank portal, enters vendor name and bank details, enters amount, submits. Waits for email 2FA code. Approver logs into a different Butterfield account, reviews the payment, approves, retrieves a second 2FA email. Process repeats for every vendor. No audit trail. Bank details can be changed by anyone with portal access. Vendor emails can be intercepted and payments redirected.

after

Submitter selects vendors from the secure vendor database, enters amounts, sees them grouped by currency, submits the batch. Approver reviews the batch in Multi-tenant Payments App Agent, authorizes with 2FA, and the EDI file is generated. Submitter downloads the file and uploads it to Butterfield once. Every action is logged: who selected vendors, who approved, when the file was generated, when it was uploaded. Bank-detail changes require Approver authorization before they take effect.

financial services / accounting / law firms / corporate services / offshore banking / payment processing / compliance / operations / fulfillment / Butterfield Bank / QuickBooks Online / Better Auth /  financial services / accounting / law firms / corporate services / offshore banking / payment processing / compliance / operations / fulfillment / Butterfield Bank / QuickBooks Online / Better Auth / 
the problem

Manual bank logins create fraud risk and operational bottlenecks

Cayman accounting firms and law firms pay vendors by logging into Butterfield Bank portals one payment at a time.

01
Twelve daily logins

Encompass has a dedicated person logging into 12 Butterfield accounts every day to pay vendors one by one.

02
Intercepted vendor emails

Attackers intercept vendor payment notifications and redirect the payment to attacker-controlled accounts. The current manual process has no controls to prevent this.

03
No segregation of duties

One person with portal access can change vendor bank details and release payments without a second person's knowledge or approval.

the math, if you want to look

Batch payments with dual approval and audit trails

proof 01
One batch instead of twelve logins

Select all vendors for the day, group by currency automatically, submit once. The EDI file is ready for bank upload without re-entering payment details.

proof 02
Dual approval enforced

Submitter selects vendors and amounts. Approver reviews and authorizes with 2FA. Neither role can release payments alone.

proof 03
Bank details locked behind authorization

Changing a vendor's bank account number requires Approver sign-off. The change goes into a pending state until approved, preventing the intercepted-email fraud vector.

proof 04
Immutable audit log

Every action is recorded: vendor add, bank-detail change request, approval, EDI generation, upload confirmation. The log cannot be deleted or edited, so fraud forensics are possible.

Multi-tenant Payments App Agent replaces manual portal logins with a single workflow: select vendors, batch by currency, authorize with 2FA, download the Butterfield-format EDI file. Bank-detail changes go into a pending state that requires Approver authorization before they take effect, so a bookkeeper cannot redirect payments by changing vendor account numbers. Every action is logged: who selected which vendors, who approved the batch, when the EDI file was generated, when it was uploaded to the bank. The audit trail is immutable and queryable, so fraud forensics are possible.

how it works

From vendor selection to bank-uploadable EDI file

Multi-tenant Payments App Agent turns a multi-step manual process into a single workflow. Submitter picks vendors and amounts, the system groups by currency, Approver authorizes with 2FA, and the EDI file is ready for download.

step 01
Submitter selects vendors and enters amounts

Pick vendors from the secure vendor database, enter the amount to pay each one. The system auto-groups payments into a KYD batch and a USD batch.

step 02
Review batch before submitting

See the total per currency, vendor count, and line-by-line list. Edit amounts or vendor selection before you submit. Once submitted, the batch is locked.

step 03
Approver authorizes with 2FA

Approver sees the pending batch in their queue, reviews it, and authorizes with a TOTP code from Authy or Google Authenticator. The batch transitions to approved.

step 04
EDI file is generated

Multi-tenant Payments App Agent generates a Butterfield Bank-compatible EDI file for each currency. The file contains payee bank details, amounts, references, and dates in Butterfield's exact format.

step 05
Download and upload to Butterfield

Download the EDI file from Multi-tenant Payments App Agent and upload it to the Butterfield Bank portal by hand. Confirm the upload in Multi-tenant Payments App Agent so the audit log captures the full handoff.

ai agent · estimator console inputs transform outputs public preview
inputs
Vendor database +

Secure, multi-tenant vendor records with name, bank details, currency (KYD or USD), email, and Cayman-specific fields. Per-tenant isolation enforced on every query.

Payment amounts +

Submitter enters the amount to pay each selected vendor. Amounts are grouped by currency automatically.

Approver 2FA code +

Approver provides a TOTP code from Authy or Google Authenticator to authorize the batch.

transformation
Auto-group by currency +

Selected payments are grouped into a KYD batch and a USD batch. Mixed-currency batches cannot be submitted.

Dual-approval workflow +

Submitter creates the batch. Approver reviews and authorizes with 2FA. Neither role can release payments alone.

EDI file generation +

For each approved batch, Multi-tenant Payments App Agent generates a Butterfield Bank-compatible EDI file with payee bank details, amounts, references, and dates.

Audit log entry +

Every action is recorded: vendor selection, batch submission, approval, EDI generation, upload confirmation. The log is immutable and queryable.

outputs
EDI file (KYD batch) +

Butterfield Bank-compatible EDI file containing all KYD payments from the approved batch, ready for download and manual upload to the bank portal.

EDI file (USD batch) +

Butterfield Bank-compatible EDI file containing all USD payments from the approved batch, ready for download and manual upload to the bank portal.

Immutable audit log +

Complete record of every action: who selected vendors, who approved the batch, when the EDI file was generated, when it was uploaded to the bank. Queryable per tenant.

draft ready for estimator review _
tech used
Butterfield Bank EDI file generationBetter Auth with TOTP 2FAPostgres multi-tenant isolationHono backend on Node.jsRailway hosting
tool alternatives
Browserbase for automated bank portal login and EDI upload (v2 only)
honest qualification

Is this for you?

built for you if
  • + Accounting firms managing offshore entity payments - Firms that handle vendor payments for multiple client entities benefit from per-tenant isolation, dual approval, and audit trails. Each client gets their own isolated vendor database and payment queue.
  • + Law firms with corporate service practices - Law firms managing entity formation, compliance, and payments for offshore clients need secure, auditable payment workflows. Multi-tenant Payments App Agent enforces segregation of duties and captures forensic-grade audit logs.
  • + Corporate service providers - Companies managing legal entities, bank accounts, and payments for offshore businesses operate at scale. Multi-tenant Payments App Agent's multi-tenant architecture and role-based access support dozens of client organizations in one system.
  • + Businesses paying vendors in both KYD and USD - Cayman businesses transact in both currencies. Multi-tenant Payments App Agent auto-groups payments by currency and generates separate EDI files for each, eliminating manual sorting.
not for you if
  • - Businesses that do not use Butterfield Bank - Multi-tenant Payments App Agent generates EDI files in Butterfield's format. Other Cayman banks (CIBC, RBC, Cayman National, Scotiabank) have different EDI formats. Multi-bank support is planned for a future phase.
  • - Businesses that need automated bank uploads - In v1, the EDI file is downloaded and manually uploaded to the Butterfield portal. Automated upload via browser automation is planned for v2.
  • - Businesses that pull invoices from accounting software - Multi-tenant Payments App Agent requires manual entry of payment amounts in v1. QuickBooks Online integration to pull bills and invoices is planned for v2.
  • - Payroll-specific use cases - Multi-tenant Payments App Agent is designed for vendor payments, not payroll. Payroll has different approval workflows, tax withholding, and regulatory requirements.
pricing

Pricing and build model

to build

Multi-tenant Payments App Agent is a custom build for Carl Brenton (Encompass Cayman) and James (Cayman-based accountant and law firm operator). The build is scoped as a dedicated senior AI engineer placement on a weekly sprint cadence, with a cost ceiling of sub-six-figures. Milestone 1 (M1) delivers a working prototype for internal use by Encompass and James. Milestone 2 (M2) onboards a friendly external customer (likely one of James's law firm clients). Milestone 3 (M3) opens self-serve onboarding for any Cayman business.

then
  • Scoped build with dedicated senior engineer on weekly sprint cadence.
  • M1 = internal use by Encompass and James. M2 = friendly external customer. M3 = open onboarding.
  • Cost ceiling is sub-six-figures. Scope discipline prioritized over feature expansion.
  • Usage-based pricing model for external customers is deferred to M2 and M3 planning.
FAQ
Do I need to use Butterfield Bank to use Multi-tenant Payments App Agent?

Yes. Multi-tenant Payments App Agent generates EDI files in Butterfield Bank's format. Other Cayman banks (CIBC, RBC, Cayman National, Scotiabank) use different EDI formats. Multi-bank support is planned for a future phase.

Can Multi-tenant Payments App Agent automatically upload EDI files to Butterfield, or do I have to upload manually?

In version 1, you download the EDI file from Multi-tenant Payments App Agent and upload it to the Butterfield portal by hand. Automated upload via browser automation is planned for version 2.

How does Multi-tenant Payments App Agent prevent fraud when changing vendor bank details?

When someone requests a change to a vendor's bank account number, the change goes into a pending state that requires Approver authorization before it takes effect. This prevents the intercepted-email fraud vector where attackers redirect payments to attacker-controlled accounts.

What happens if I reject a payment batch as an Approver?

Rejected batches return to the Submitter with comments explaining why the batch was not approved. The Submitter can then edit the batch and resubmit it for approval.

Can I pull vendor payment data directly from QuickBooks Online into Multi-tenant Payments App Agent?

Not in version 1. Multi-tenant Payments App Agent requires manual entry of payment amounts. QuickBooks Online integration to pull bills and invoices is planned for version 2.

Is Multi-tenant Payments App Agent suitable for payroll payments?

No. Multi-tenant Payments App Agent is designed for vendor payments. Payroll has different approval workflows, tax withholding, and regulatory requirements that are outside Multi-tenant Payments App Agent's scope.

How many people need to approve a payment batch before it can be released?

Dual approval is the default: a Submitter selects vendors and amounts, and an Approver reviews and authorizes with 2FA. The configuration is per tenant, so some organizations may start with a single approver and add a second later.

Can I see a complete audit trail of all payment actions in Multi-tenant Payments App Agent?

Yes. Every action is recorded in an immutable audit log: who selected vendors, who approved the batch, when the EDI file was generated, when it was uploaded to the bank, and any changes to vendor bank details. The log cannot be deleted or edited, so fraud forensics are possible.

related builds
backflow-test-filing-automation-system-439116d8pharmatrack-prd-v1-0-a134448bcustomer-health-diagnostic-agent-prd-v1-0-c089c2a5rent-roll-parser-agent-prd-v1-0-a6644eb0self-storage-sourcing-agent-prd-v2-0-6e730be6
next step

Ready to eliminate manual bank logins and enforce dual approval on vendor payments.

Multi-tenant Payments App Agent is in active development for Encompass Cayman and James's law firm clients. If you are a Cayman accounting firm, law firm, or corporate service provider managing vendor payments across multiple entities, contact us to discuss your payment workflow and fraud-prevention needs.