Reserve movements appear on both sides of a balance report
Keep each ledger entry, but pair documented counterparts as one reserve movement before totaling its effect. Stripe identifies reserve_hold and reserve_release as reserve-balance counterparts to reserved_funds entries. Their appearance on different balance records does not make them separate losses. Match references, account, currency and direction; then trace any later release separately. Count a fee only from a record that identifies a fee, and leave unmatched entries unresolved rather than forcing a pair.
For: A research-only merchant comparing an actual reserve hold or release across payment-provider balance records.
Begin with the provider, account, report name, covered dates and currency. Keep the available-balance record separate from the reserve-balance record. A debit in one location and its counterpart in another describe where funds moved; stripping away the balance label can make both rows look like additional deductions from the business.
Stripe's balance-transaction documentation uses type to describe the movement and source to identify its originating object. It recommends reporting_category for grouping. Retain those fields when available, together with the individual balance-transaction reference and the signed amount. Do not replace an unfamiliar type with a general expense label just because its amount has a minus sign.
This method concerns the paired movements of an existing reserve. The notice or agreement supplies the separate question of why funds were held and under what terms. A technical transaction type does not establish contractual release rights or a release date.
Pair counterparts without deleting the evidence
On Stripe, reserve_hold and reserve_release identify entries in the reserve balance that are counterparts to reserved_funds. Use the documented source relationship and available references to connect the two sides. Preserve their original signs and note which balance increased or decreased. Confirm that the records describe the same account context and currency before treating them as a pair.
Equal amounts alone are insufficient. Several movements can share an amount, and a report can omit the other side because of its scope or selected period. If the reference does not establish the relationship, mark the candidate pair unconfirmed and retain the report filters. Ask for the specific missing counterpart or mapping rather than declaring a second loss.
In a combined tracing worksheet, label both records as sides of the same documented movement. In the reconciliation of one balance, retain the entry that actually changes that balance. Do not delete a valid ledger row to make the combined view look simpler, and do not sum the absolute values of both sides as total funds lost. That distinction preserves both the movement history and each balance's own reconciliation.
Trace a release as its own event
A hold and its immediate counterpart establish the transfer into reserve. A later release is another movement with its own references and dates. Match the release to the reserve history only to the extent that the actual records establish the association. Do not assume every release maps one-to-one to a single earlier hold or that a smaller closing reserve balance proves a particular hold was released.
Record the portion that the release records actually identify. Keep any still-held amount or unexplained difference separate. A reserve release also does not by itself prove a bank deposit: Stripe documents payouts as movements to the bank, with cancellation and failure entries returning funds. If the question is whether released funds reached the bank, it needs a payout record and bank receipt in addition to the reserve records.
A movement labeled as a fee belongs in a separate fee row, with its own reference and amount. A hold reduces the funds available in that balance, but the counterpart does not create a second fee. Neither a release nor a reserve reduction establishes the merchant's accounting or tax treatment.
Keep reserve categories separate in the conclusion
Stripe's reporting categories distinguish reserved_funds grouped as risk_reserved_funds from reserve_transaction grouped as connect_reserved_funds. Do not merge those categories simply because both names contain reserve. The balance owner and originating record matter. Network reserve and payout minimum balance also have distinct transaction types; their entries should not be pulled into this pairing merely to make a total agree.
Finish with a concise result for each movement: counterpart confirmed, release documented, fee separately identified, or mapping still unresolved. For an unresolved item, state the existing reference and the exact missing relationship. This lets the provider answer the record question without being asked to endorse an invented loss calculation.
If the issue accompanies a processing or provider website question, a PRISM processing consultation can begin with the business description and a summary of the unresolved movement. Confirm any requested statement-analysis assistance, scope, fees and terms before work. The provider controls reserves and account terms. Use the public form for the website, research-only products and question, not private statements or customer records; follow-up is by email and the inquiry is not a processing application or purchase.
Reserve movement pairing table
Use one copy for each movement being traced. Enter non-sensitive references, signed amounts and currencies from the real records. A confirmed pair explains movement between balances; a missing counterpart remains unresolved and must not become an invented fee.
Worksheet entries are not submitted by Prism’s worksheet and are not saved by the site. Use record types, availability, anonymized observations, or match/mismatch results. Do not enter government identifiers, customer names or addresses, customer messages, receipt-access links, card or bank details, passwords, or keys. Send sensitive documents only through the provider’s verified secure channel.
Reserve movement pairing table. The last column is for temporary notes.
Pairing item
Evidence to retain
Interpretation check
Your record
Originating hold reference
Evidence to retainProvider, account label, originating source reference, transaction reference and recorded date.
Interpretation checkThe relationship must identify the actual movement; an equal amount is not enough.
Available-balance movement
Evidence to retainThe signed amount, currency, type and reporting category on the relevant balance record.
Interpretation checkKeep its effect on this balance even when the reserve counterpart is paired in the combined view.
Reserve-balance counterpart
Evidence to retainThe reserve_hold or reserve_release entry and the record connecting it to reserved_funds, where applicable on Stripe.
Interpretation checkRecord the other side once as a counterpart, not as a second loss.
Release reference
Evidence to retainThe later release reference, date, amount and documented connection to the reserve history.
Interpretation checkDo not assume a one-to-one hold match or that release means payment to the bank.
Separate fee if any
Evidence to retainThe fee's own label, reference, amount, currency and supporting statement or terms.
Interpretation checkA negative reserve movement alone does not establish a fee.
Category and balance owner
Evidence to retainRisk-reserve or Connect-reserve category and the account or platform balance identified in the report.
Interpretation checkKeep distinct categories and owners apart even when their descriptions sound similar.
Unmatched remainder
Evidence to retainMissing counterpart, differing currency, incomplete period or unexplained amount, with the report filters.
Interpretation checkAsk for the missing record or relationship; do not force the worksheet to balance.
These are temporary notes. Leaving or reloading this page may clear them. Worksheet entries are not sent automatically. If you copy notes into the consultation message and submit the form, Prism receives them as part of your request.
Limits
Stripe's type and category names apply to Stripe records. Another provider needs its own documented mappings.
Pairing technical movements does not determine accounting treatment, legal rights, release timing or processing eligibility.
Do not enter card numbers, authentication codes, full bank details, credentials or customer records in this worksheet or the public inquiry.
Stripe balance transaction types — checked 2026-09-29. Type describes the movement and source identifies its origin. reserve_hold and reserve_release are reserve-balance counterparts to reserved_funds; payouts, fees and other reserve-related types remain distinct. These labels do not establish release rights or timing.
Stripe reporting categories and types — checked 2026-09-29. reserved_funds groups as risk_reserved_funds, while reserve_transaction groups as connect_reserved_funds. These are technical categories rather than universal accounting conclusions.
Prism solutions — checked 2026-09-21. The provider decides reserves and account terms. PRISM's published support and any requested work have scope, fees and terms discussed before work.
Prism contact — checked 2026-09-21. An inquiry supplies the website, products and question without card details, passwords or customer records. Email follow-up does not make the request an appointment, purchase or processing application.
Discuss my processing options
Want to talk through your own processing situation?