How to Choose a Merchant Statement Audit Service

A useful merchant statement audit should explain what you paid, identify the evidence behind each finding, and give you a practical next step. Compare services by the quality of that work, the information they require, and who helps resolve an issue after the report arrives.

An attractive savings estimate is only part of the evaluation. Ask how it was calculated and what would need to change for the business to realize it.

Swipesum Audit supports statement analysis. Businesses can request a free statement audit from the payments team to understand their current processing costs and potential next steps.

Define the question you want answered

Start with the problem. You may want to understand a bill, check charges against an agreement, investigate a recent increase, compare a new proposal, or review costs across multiple accounts.

Tell the reviewer which decision the audit should support. A one-month explanation of fees and an ongoing portfolio review are different scopes. If you need monitoring, specify which accounts and periods are covered, how changes are reported, and who investigates them.

Separate reviewing your own merchant costs from buying statement-analysis software for an ISO or platform. The latter also requires evaluation of workflow, access, data handling and outputs across the accounts you are authorized to manage.

Ask what information is needed

Recent processing statements are a practical starting point. Ask whether the reviewer also needs the pricing agreement, amendments, gateway bills, equipment charges or other records relevant to your question. Confirm the period and accounts covered.

A statement may not establish whether a fee matches the contract if the reviewer has not seen the relevant agreement. Ask the reviewer to identify missing evidence instead of treating an assumption as a confirmed billing error.

Use the provider's designated submission process and ask who can access the files, how they are used, and how retention or deletion requests are handled. Avoid sending unrelated sensitive information merely because it appears in a larger business file.

Evaluate the report before the headline estimate

Ask for an anonymized example of the proposed deliverable or a description of its structure.

Cost breakdown

• What a buyer should be able to determine: Which accounts, periods and cost categories were included

Finding record

• What a buyer should be able to determine: The statement line, agreement term or calculation supporting the observation

Comparison

• What a buyer should be able to determine: Which assumptions are held constant and which costs differ

Action list

• What a buyer should be able to determine: What should happen, who owns it and which evidence is still missing

Verification plan

• What a buyer should be able to determine: How an implemented change will be checked in later records

An observation, an estimate and a verified outcome belong in separate fields. That distinction makes the report more useful when finance, operations and the provider discuss what to do.

Require a comparable baseline

For a proposed alternative, ask the reviewer to use the same payment volume, transaction count and available mix information. Include applicable gateway, account and other charges rather than comparing a complete current bill with a single proposed rate.

Ask how seasonal changes or an unusual month affect the comparison. When information is unavailable, request an explicit assumption and explain how the estimate might change. Do not interpret every effective-rate increase as a discretionary provider markup increase without investigating its components.

Clarify implementation and commercial terms

Who contacts the current provider about a disputed charge? Who evaluates a proposal, coordinates a change, and checks the next statement? Find out which services are included and which require another engagement.

Ask how the reviewer is paid, whether a recommendation involves a provider relationship, how any performance-based fee is calculated, and what continuing obligation the business accepts. Compare the written scope rather than assuming every free review or paid engagement works the same way.

You can also ask whether improvements within the existing setup will be evaluated. A review should help you decide among the available options; it should not require you to assume a processor change before the findings are understood.

Take the next step with your current records

Swipesum reviews processing costs and can discuss the implementation or ongoing support a business needs after the findings. Keep the initial audit question focused: what are you paying, what deserves investigation, and what would justify a change?

Request your free statement audit. Bring a recent statement and describe the issue you want to resolve. For ongoing account or portfolio analysis, discuss the required scope with the payments team.

Want to organize the numbers before speaking with a reviewer? Our AI merchant statement analysis guide includes a reusable prompt and a process for checking the figures against your documents.

Common buyer questions

Can an audit help without changing processors?

Yes. The review can identify questions to investigate within your existing setup. Swipesum's free audit offer carries no obligation to switch processors. The findings determine which next steps deserve consideration.

Is a free statement audit the same as an Audit software subscription?

The free statement review is a starting point with Swipesum's payments team. Ongoing software, account or portfolio analysis is a separate scope to discuss and price for the work required.

Does an effective-rate increase prove that my markup increased?

No. Investigate the cost components and the underlying payment mix. Compare the relevant charges and written agreement before describing the change as a markup increase or billing error.