National payment operations resource

Payment Statements, Reporting & Reconciliation

A practical framework for connecting sales activity, processor reports, adjustments, deposit batches, bank activity, and accounting records without relying on one report to explain the entire payment flow.

Start with the transaction path

Know what each report is designed to show

A checkout record, batch report, processor statement, bank deposit, and accounting entry describe different points in the same workflow. Reconciliation becomes easier when each source has a defined owner, date basis, identifier, and purpose.

Sales activity

Capture completed sales, tips when applicable, refunds, voids, and other transaction events from the system where staff operate.

Processing activity

Use provider reports to identify batches, transaction status changes, adjustments, disputes, and the references needed for support.

Deposit activity

Match processor deposit references and dates to bank activity while accounting for timing differences and separately reported events.

Business records

Post activity using the business's approved accounting method and retain the supporting documents selected with its bookkeeper, accountant, or tax adviser.

Important: Report names, timing, fields, retention requirements, tax treatment, and accounting entries vary. Confirm provider-specific details directly and obtain qualified accounting or tax guidance for the business.

Statement reading

Review the summary, then trace the detail

Confirm the period and account

Check the merchant account, business entity, location or channel, reporting period, time zone, and date convention before comparing totals.

Separate activity from settlement

Transaction activity can be grouped by authorization, capture, batch, funding, or report date. Document which date each system uses instead of assuming that daily totals should always match.

Identify adjustments as distinct events

Keep refunds, disputes, reversals, reserves, corrections, and other adjustments visible. Ask the provider what an unfamiliar line means before assigning it an accounting treatment.

Preserve the support trail

Retain the statement period, batch or transaction reference, amount, date, report name, and case number used to investigate an exception.

Repeatable workflow

Reconcile from source activity to the bank

1. Close the operating period

Confirm the expected stores, terminals, websites, invoices, users, and batches are represented. Note late closures or offline activity.

2. Compare transaction totals

Group gross sales, refunds, voids, and other events consistently. Preserve differences instead of forcing reports to agree.

3. Match deposits

Use batch and deposit references where available. Track deposits that combine batches or arrive after the operating date.

4. Resolve and document

Assign every exception an owner, evidence, status, next action, and resolution date, then update the business record through the approved process.

Exception management

Investigate differences without losing the audit trail

Missing transaction

Confirm the correct channel, status, date range, time zone, batch, and account. Do not re-run a payment simply because it is absent from one report.

Deposit mismatch

Check whether the deposit represents one or multiple batches and whether refunds, disputes, adjustments, or timing differences appear elsewhere.

Duplicate-looking activity

Compare unique transaction references, timestamps, amounts, and status history. Escalate suspected duplicates through the provider's current workflow.

Unfamiliar statement line

Record the exact label and period, then request the definition and supporting detail from the responsible provider before categorizing it.

Controls and access

Protect reports while keeping work reviewable

Use named access

Give staff individual accounts and only the permissions needed for reporting, refunds, settings, and support tasks.

Separate preparation and review

When practical, have one role prepare the reconciliation and another review exceptions, changes, and completion evidence.

Store reports safely

Use approved storage and retention practices. Do not copy complete card numbers, security codes, passwords, bank credentials, or secret keys into reconciliation files.

Review access and sources

Periodically confirm that active users, locations, devices, payment channels, providers, and bank accounts still match the documented workflow.

Evaluation questions

Questions to ask a reporting provider

Which dates drive each report?

Ask how authorization, capture, batch close, adjustment, and deposit dates affect filters and totals.

Which identifiers connect systems?

Confirm which transaction, batch, deposit, location, invoice, order, and support references are available.

How are corrections represented?

Ask where refunds, reversals, disputes, and other adjustments appear and whether prior reports change.

How can data be reviewed?

Confirm available exports, access controls, report history, support documentation, and escalation routes for the current service.

Common questions

Statements and reconciliation FAQ

Why does a sales total differ from a bank deposit?

The records may use different dates or grouping rules, and the deposit may reflect multiple batches or separately reported events. Trace the provider's references before deciding that a transaction is missing.

What should a reconciliation record include?

Keep the period, source reports, totals compared, identifiers, exceptions, responsible person, evidence, actions, and review or completion date.

Should statement details be copied into a spreadsheet?

Only copy the minimum approved information. Avoid complete card numbers, security codes, credentials, and secret keys, and use the business's approved storage and access controls.

Who explains an unfamiliar report field?

Use the responsible provider's current documentation and support route. Preserve the exact label, period, account, and related reference so the question can be investigated.

Last editorial review: August 11, 2026. Sources reviewed: IRS business recordkeeping guidance and Publication 583, SBA financial-management guidance, and PCI SSC small-merchant resources.

Next step

Map your reporting and reconciliation workflow

Payments Max can help organize channels, systems, reports, identifiers, access, and provider questions before you compare available options.

Contact Payments Max

To learn more about how TSYS can help improve the way your organization accepts payments, markets to new customers, or manages its HR responsibilities, get in touch by calling 585-981-8463 to get started.

CONTACT US