A business keeps operating funds and reserves in separate accounts inside your software. After receiving a large customer payment, it wants to move $5,000 into reserves. When both accounts are eligible for a book transfer, your product can make that movement internally, without sending an ACH payment or wire.
The same mechanism can support payments between different customers or distributions from an operational account. For teams building financial products, book transfers provide a way to connect business activity to money movement while keeping both sides of the transaction visible.
This guide explains how book transfers work, when to use them, and what your software should track.
TLDR:
- A book transfer moves funds between accounts at the same bank through a debit and a corresponding credit, without using an external payment network.
- Supported uses can include transfers between one customer’s accounts, payments between different customers, and distributions to customer accounts.
- Account eligibility, authorization, and available funds determine whether a transfer can proceed.
- Unit calls these transfers “book payments” and processes eligible payments instantly and free of charge, with a transaction recorded in each account.
How Book Transfers Move Money Between Accounts
A book transfer moves money by debiting one account and crediting another at the same bank. In this article, “internal transfer” refers to that movement. Unit uses the term “book payment” in its payment documentation.
Consider a hypothetical business moving $5,000 from an operating account into a reserve account. Assume both accounts qualify for the transfer and the operating account has sufficient available funds.
| Account | Before transfer | Transfer | After transfer |
|---|---|---|---|
| Operating | $20,000 | -$5,000 | $15,000 |
| Reserves | $2,000 | +$5,000 | $7,000 |
| Combined balance | $22,000 | $0 net change | $22,000 |
The business still holds $22,000, but the money is now distributed differently between its accounts. Each account has a transaction recording its side of the movement.
This differs from assigning a “reserves” label to funds within a budgeting interface. A label can organize how money is presented without moving it between accounts. A book transfer changes the underlying account balances, giving the product a concrete transaction to display and trace.
Which accounts are eligible for internal transfers?
Book-transfer eligibility depends on the underlying accounts and the provider’s supported arrangement. Two accounts appearing in the same app are not enough to establish eligibility.
Unit’s transaction documentation defines a book payment as a payment between accounts at the same bank. Its book-payment overview also specifies accounts under the same Unit organization. That organization can include accounts belonging to different end customers; it does not mean every account has the same owner.
Before initiating a transfer, your product should establish:
- Whether the source and destination belong to the supported account arrangement.
- Whether the initiating person or service is authorized to move the funds.
- Whether sufficient funds are available, taking account of holds.
- Whether account restrictions prevent the movement.
An eligible pair of accounts can still produce a rejected payment. For example, the source may lack available funds or the destination may be frozen. Distinguishing these problems helps the product give a useful next step rather than a generic “transfer failed” message.
When internal account transfers are useful
Book transfers are useful when your product needs to move existing funds between eligible accounts as part of a customer workflow.
Organizing money across a customer’s accounts
A business may use separate accounts for operating expenses, reserves, or individual locations. Internal transfers let it allocate money as needs change. In the running example, the business moves $5,000 into reserves after receiving a payment. Later, it might move some of those funds back to cover an expense.
Software can connect these movements to customer instructions or rules your team builds. For example, a customer might choose to maintain a target operating balance and move excess funds to reserves. The application defines when and how much to transfer; the book payment executes the movement.
Paying another customer within the product
Separate ownership does not automatically require an external payment. Imagine a property management business paying a maintenance company, with both holding eligible accounts in the same program. A permitted book transfer could move the payment between them while the application links it to the completed job.
This is a hypothetical workflow. Its suitability depends on the account arrangement, authorization, and program requirements.
Distributing funds to customer accounts
An operational or clearing account can serve as the source for transfers to eligible customer accounts. The application determines each recipient and amount, then connects the resulting transfers to the relevant business records.
The funds must be available to distribute. A book transfer moves an existing balance; it does not make an unsettled incoming payment available or supply additional funding.
Book transfers compared with ACH and wires
The first question is whether the destination qualifies for an internal transfer. If it does, a book transfer can avoid routing the payment through an external network. If it does not, the product needs another supported payment method.
| Consideration | Book transfer | ACH | Domestic wire |
|---|---|---|---|
| Account reach | Eligible accounts within the supported same-bank arrangement | Accounts reachable through ACH | Accounts reachable through the applicable wire system |
| Processing | Internal debit and credit entries | ACH network processing | Wire-system processing |
| Common uses | Internal allocations and payments between eligible customers | External funding, collections, and recurring payments | External business payments, including large or time-sensitive transfers |
| Timing and fees | Instant, no fee at Unit | Depend on service, processing windows, and provider terms | Depend on processing, cutoffs, and provider terms |
External payment methods follow their own schedules. ACH processing windows and Fedwire operating hours help determine when payments can be processed, alongside your provider’s submission cutoffs.
Speed alone does not determine the route. The destination, amount, authorization, and supported capabilities also matter. A recurring instruction can use an internal transfer when the accounts qualify; recurrence does not inherently require ACH.
Keep external-payment timing separate from the internal-transfer experience. For background on those methods, see our guides to ACH transfers and wire transfers.
What software should track during a book transfer
Each transfer should connect the customer’s instruction to a payment outcome and the resulting account activity. Record the source, destination, amount, purpose, and a reference to the business event, such as a job or distribution batch.
After submitting the payment, use its documented status to determine what the product displays. Unit’s book-payment resource reports Sent or Rejected. A successful payment creates a book transaction in each account, allowing the movement to be traced from both sides.
Descriptions help customers recognize activity, while tags connect payments to application records. Display balances from the account system rather than independently adding or subtracting amounts whenever your application receives an update.
Build retry handling around the original instruction. Unit’s idempotency guidance explains how reusing the same idempotency key can prevent a network-error retry from creating the payment more than once. Use a distinct key for each intended payment and preserve it when retrying that payment.
A confirmed rejection and a missing response require different handling. Unit documents rejection reasons including insufficient available funds and a closed or frozen counterparty account. An application timeout, however, does not establish rejection. Check the existing payment before prompting another submission.
How Unit supports money movement between accounts
Unit supports book payments between eligible accounts under the same organization at the same bank. They can move funds between accounts belonging to one customer or different customers, and from operational or clearing accounts to customer accounts.
The book payments overview documents support across deposit accounts, wallet accounts, and financial business FBO accounts within the supported arrangement. Each successful payment creates one book transaction in each account.
Through the book-payment API, your software specifies the originating account, destination account, amount, and description. Optional tags are copied to transactions created by the payment, helping connect money movement to orders, jobs, or other business activity. An optional idempotency key supports safe retries.
These capabilities let teams build internal transfers into the workflows their customers already use. The application determines the allocation or payment instruction, while Unit processes the book payment and provides the related records on its native ledger.
Building a clear internal-transfer experience
Start with the customer’s task: allocate reserves, pay another customer, or distribute funds. Establish which accounts can participate, then make the transfer’s purpose and outcome easy to understand. Talk to our team about the account flows you want to build.
FAQ
Can book transfers support marketplace seller payouts?
Yes, when the source and seller accounts meet the provider’s eligibility requirements and the payout is authorized. Unit supports book payments between different customers’ accounts within the same organization at the same bank. Available funds must cover the payout.
Should recurring transfers use book payments or ACH?
Use a book payment when both accounts qualify for an internal transfer. Otherwise, use ACH if the destination and payment type support it. The recurring schedule determines when to initiate the payment; account eligibility determines which method can carry it.
How should you test a book-transfer workflow?
Test successful transfers, insufficient funds, closed or frozen destinations, and recovery from a lost response. Confirm the payment outcome, both transaction records, and updated balances. Use Unit’s documented idempotency behavior to test retries without duplicate payments.
The content in this article is provided for general informational and educational purposes only and should not be construed as legal, tax, accounting, or regulatory advice. Unit does not warrant or guarantee the accuracy, completeness, adequacy, or currency of the information provided, and the content may not reflect all considerations relevant to a particular business, product, or use case.
Unit is a financial technology company and is not a bank. Banking services are provided by Unit's bank partner(s), Members FDIC. Unit provides technology infrastructure and program management services to enable clients to offer financial products.
