A processing statement is useful when it explains the path from customer sales to bank deposits. Begin with a specific reporting period and keep the statement, transaction export, refund log and bank record together. Comparing a quoted rate with a single total can hide timing differences and operational mistakes.
Build a bridge from sales to deposits
Record gross sales, refunds, other adjustments, fees and the deposits associated with the period. Ask the provider how its batch cutoff and funding schedule affect that comparison. A deposit arriving in the next reporting period should remain an identified timing item, not disappear into an unexplained balancing entry.
Separate pricing questions from transaction exceptions
Keep two lists. On the first, record each charge whose description or calculation you cannot explain. On the second, record missing deposits, duplicate-looking transactions, unexpected reversals and unresolved refunds. A pricing discussion will not by itself resolve an uncertain customer payment.
For each item, retain the statement page, transaction or batch reference, amount, date and support case number. Use approved references rather than copying full payment-card details into an email or spreadsheet. Ask the provider to explain the calculation in writing and identify the relevant agreement or fee schedule.
Compare channels and locations consistently
If a business operates in Florida, New York and New Jersey, separate each location and sales channel before combining totals. Different hours, customer payment methods or reporting cutoffs can make aggregate comparisons misleading. This is an accounting organization step, not a claim that a state determines processing prices.
Use the AMS regional operating guides to organize location records. Keep the legal entity and location identifiers that actually appear on provider and bank documents consistent.
Create an exception log that can be handed off
Assign one owner, a next action and a follow-up date to every unresolved item. When an item closes, record the explanation and the supporting entry. Review recurring exceptions with the staff who close batches or issue refunds so that a documentation problem does not become a monthly ritual.
Related reading: uncertain payments and reconciliation, and testing a usable data export. This article does not estimate a merchant’s fees or recommend changing acceptance rules.
By Eric Kuvykin. Revised October 17, 2026. Examples are illustrative operating scenarios.
