🏦 Enabling a Bank Account to Send Payments
---
📋 Prerequisites
Before enabling a bank account for payments, ensure you have:
✅ System Administrator or Treasury Manager role
✅ The bank account already set up in Trovata TMS
✅ Bank connectivity established (SWIFT, ACH, FedWire, etc.)
✅ Required approvals from your banking team
---
🔧 Step-by-Step Setup
Step 1: Navigate to Bank Account Setup
ATOM Menu → Cash Management → Bank Accounts → Account Maintenance
Search for the account you want to enable
Open the account record
Step 2: Configure Payment Settings
In the account record, locate the Payment Configuration section and set:
Field | Description |
Payment Enabled | Toggle ON to allow outgoing payments |
Payment Method | ACH, Wire, SWIFT, Check, Internal Transfer |
Payment Currency | Default currency for outgoing payments |
Daily Limit | Maximum payment amount per day |
Single Payment Limit | Max amount per individual payment |
Cut-off Time | Latest time payments can be submitted |
Step 3: Set Up Bank Connectivity
Choose your transmission method:
Method | Use Case |
SWIFT MT101 | International wire transfers |
ACH (NACHA) | US domestic batch payments |
FedWire | Large-value US domestic wires |
Host-to-Host | Direct bank file transmission |
API | Real-time payment connectivity |
Step 4: Define Payment Approval Workflow
Configure who can approve payments from this account:
Payment Workflows → New Rule → Select Account → Set Approval Tiers
Tier | Example Rule |
Tier 1 | Payments < $100K → 1 approver |
Tier 2 | Payments $100K–$1M → 2 approvers |
Tier 3 | Payments > $1M → CFO approval required |
Step 5: Configure Payment Line Codes
Each payment type needs a line code mapped to the account:
Line codes identify the specific account/purpose combination
Format example:
JPM6260-ABC,BOFA1234-PAYThese are used when creating payments (e.g.,
createPayment)
Step 6: Set Up Signatories
Define authorized signatories for the account:
Add authorized users with signing limits
Configure dual-control requirements if needed
Set up digital signature certificates for electronic payments
Step 7: Test the Connection
Before going live:
✅ Run a test transaction (small amount or $0.01)
✅ Verify bank acknowledgment/confirmation
✅ Confirm payment appears in bank statement
✅ Test the full approval workflow end-to-end
Step 8: Activate the Account
Account Record → Status → Set to ACTIVE for Payments
---
🔐 Security Considerations
Control | Description |
Positive Pay | Send issued check list to bank to prevent fraud |
Dual Control | Require two users for payment creation + approval |
IP Restrictions | Limit payment access to specific IP addresses |
Audit Trail | All payment activity logged automatically in ATOM |
Segregation of Duties | Separate payment creation from approval roles |
---
📁 Required Documentation
Typically needed for bank-side activation:
Board resolution authorizing electronic payments
Authorized signatory list
Completed bank connectivity agreement
Security token/certificate enrollment
---
🆘 Common Issues & Fixes
Issue | Solution |
Payment rejected | Check cut-off times and daily limits |
Account not appearing | Verify account status is ACTIVE |
Approval stuck | Check workflow configuration and approver availability |
Bank connectivity error | Verify SWIFT/ACH credentials and certificates |
Line code not found | Ensure line code is mapped to the correct account |