Finance Index
How should AP structure and manage its bank accounts for disbursements?
Reference guide to bank account management AP, including payment timing, method choices, control points, reconciliation, and vendor communication.
AP disbursement structure is a control decision: most teams run a dedicated disbursement account (debit-blocked, funded as needed) separate from operating and receivables accounts, with approval routing tied to the account being debited. How many accounts - single, per-entity, or per-method - depends on entity structure, banking relationships, and reconciliation tolerance, but segregation by function is the constant.
At a Glance
| Aspect | Short Answer | Why It Matters |
|---|---|---|
| AP structure | AP disbursement structure is a control decision: most teams run a dedicated disbursement account (debit-blocked, funded as needed) separate from operating and receivables accounts, with approval routing tied to the account being debited. | Keeps evidence clear and reduces control risk. |
| How many accounts should AP | Start from function, not convenience: a disbursement account that only pushes payments out (and is blocked from inbound debits) limits fraud blast radius and simplifies reconciliation. | Reduces payment errors, timing issues, and reconciliation cleanup. |
| Add a new company bank | Set it up at the bank (with debit block/positive pay), add it in the ERP and payment system with the correct GL mapping, map its approval chain, verify it through the payment platform, and enroll it in positive pay before the first. | Reduces payment errors, timing issues, and reconciliation cleanup. |
| Payment impact | Typically micro-deposits (small test amounts you confirm over a few days) or instant verification (real-time validation through a bank-data connection); instant is faster, micro-deposits are the fallback - both confirm you control the account before it can disburse. | Keeps evidence clear and reduces control risk. |
| Workflow | Usually wrong account/routing entry, the deposits posting after the confirmation window, or the bank filtering small credits; re-confirm the details, check the statement for the test amounts, extend or restart the window, or switch to instant verification. | Keeps vendor records and payment decisions reliable. |
How many accounts should AP disburse from?
Start from function, not convenience: a disbursement account that only pushes payments out (and is blocked from inbound debits) limits fraud blast radius and simplifies reconciliation. Multi-entity companies choose between a centralized paying entity (one disbursement account funding all subsidiaries via intercompany entries) and each entity paying its own - centralization simplifies operations and bank relationships; decentralization keeps entity cash and approvals cleanly separated.
How do I add a new company bank account for disbursements?
Set it up at the bank (with debit block/positive pay), add it in the ERP and payment system with the correct GL mapping, map its approval chain, verify it through the payment platform, and enroll it in positive pay before the first run.
How does bank account verification work when connecting an account to a payments platform?
Typically micro-deposits (small test amounts you confirm over a few days) or instant verification (real-time validation through a bank-data connection); instant is faster, micro-deposits are the fallback - both confirm you control the account before it can disburse.
Micro-deposit verification failed twice - common causes and next steps?
Usually wrong account/routing entry, the deposits posting after the confirmation window, or the bank filtering small credits; re-confirm the details, check the statement for the test amounts, extend or restart the window, or switch to instant verification.
How do we manage payments across multiple banks without logging into five portals?
Run all accounts through one payment workflow that connects to the banks once, so AP releases from a single surface instead of juggling portal logins - consolidating execution removes both the keying labor and credential sprawl.
What's the process when the company changes banks?
Sequence it: open and verify the new disbursement account, migrate recurring debits and positive pay, run the old and new accounts in parallel until outstanding checks clear, redirect vendor payments to the new account, and only then close the old one - outstanding checks are the trap.
How should bank signers and online payment permissions be reviewed, and how often?
At least quarterly and immediately on any departure or role change: confirm each signer/permission is still appropriate, remove stale access, and keep named (never shared) credentials - access creep on payment accounts is a top audit finding.
How do multi-entity companies structure disbursement accounts?
Either a centralized paying entity (one account funds all subsidiaries with intercompany entries) for operational simplicity, or each entity pays from its own account for clean cash and approval separation - size and entity autonomy drive the choice.
What is an in-house bank / payment factory and at what size does it make sense?
A centralized treasury structure that pays on behalf of all entities, nets intercompany flows, and standardizes controls; it makes sense at larger multi-entity scale where the efficiency and control gains justify the setup complexity.
We acquired a company with its own banks and payment processes - what's the 90-day plan?
Inventory their accounts, signers, and outstanding payments; bring disbursements under your controls (segregation, positive pay, approval routing); migrate vendors and recurring items; run parallel until their checks clear; then consolidate accounts and close redundancies.
Who should be able to see full bank account numbers, and how should they be masked?
Restrict full account-number visibility to a minimal set of treasury/finance roles, mask the number everywhere else, and log access - exposed account numbers feed counterfeiting and fraud, so masking by default is the right posture.
Stampli perspective
Stampli supports bank-account management in Direct Pay by connecting funding accounts to payment workflows, approval rules, account verification, and ERP-aligned reconciliation. Finance teams can manage payments from multiple bank accounts while preserving separation of duties, funding-account ownership, and 1-to-1 payment records. The ERP remains the system of record, while Stampli keeps payment preparation, approval, execution status, and reconciliation context connected to the AP workflow.