By Eric Kuvykin. Reviewed October 17, 2026. This practical guide replaces an earlier general commentary article at the same address.
A monthly statement review is easier to repeat when unresolved questions live in an anomaly register. Instead of starting from a blank page each month, the owner can see which differences are new, which have a supported explanation and which remain open. The register is a record of questions and evidence, not a presumption that every unfamiliar line is an error.
Choose the review boundary
Identify the merchant account, statement period, bank destination and related software invoices. Record the person performing the review and the source files used. Reconcile the sales and deposit records before comparing percentages. A cost ratio built from one account’s fees and another account’s sales can look precise while explaining very little about the actual business.
Give each anomaly a unique reference, category, amount, supporting document, owner and next action. Useful categories include missing funding, duplicate entry, unfamiliar fee, refund mismatch and timing difference. Keep an unresolved category for a question that does not yet fit. Label estimates and hypotheses so they cannot later be mistaken for verified conclusions.
Ask questions a provider can answer
For an unfamiliar fee, cite the statement line and request the relevant agreement or schedule. For a missing deposit, provide the batch reference and expected amount through the verified support route. For a transaction mismatch, identify the business event and the records that disagree. A specific packet reduces the chance of receiving a generic explanation that never addresses the original question.
Consider a hypothetical month in which the deposit total is lower than the sales total. Refunds, adjustments, fees, timing and unresolved exceptions should be investigated from the actual records. Do not simply declare the difference to be processing cost. The register should show the supported bridge from sales to deposits and keep unexplained amounts visible.
Close items with evidence
A case is ready to close when the explanation matches the records and any correction is visible. Save the provider’s response and the location of the confirming entry. If the same question returns, link the new case to the earlier one instead of deleting it as familiar. Repeated anomalies can reveal a training problem, a configuration issue or a recurring service responsibility that needs clarification.
Use the full processing-statement checklist for the review sequence and the data-export test to improve the records available next month. Consult Visa’s merchant fee resources for network context rather than treating every fee as interchange. The New Jersey business guide provides a wider business-record path. A useful monthly review ends with a reconciled position and a short owned list of open questions, not a folder of statements nobody can explain.
