Batch and settlement basics

What Is Manual Batch Close?

Manual batch close is an operator-initiated step used in some payment systems to finalize or submit a group of transactions. The exact action, timing, and terminology vary, so the safest procedure is the one documented for your processor, gateway, POS platform, and terminal configuration.

Plain-language definition

Manual close puts a person in control of the closeout step

Instead of relying entirely on a scheduled close, an authorized user reviews the day's payment activity and starts the close or settlement command. Depending on the system, that may submit eligible transactions, settle open tipped payments, produce a closeout report, or complete several related tasks.

Terms are not universal: batch close, settlement, close of day, end-of-day report, and transfer cutoff may describe different functions. Confirm what the button actually does before using it.

Before closing

Review the records that can affect a clean closeout

Open payments

Look for transactions awaiting a tip, completion, capture, or another required action. Follow the provider's instructions for resolving them without changing valid customer amounts.

Pending and offline activity

Confirm whether the device has unsent or pending transactions. Do not reset, sign out, or disconnect equipment until provider guidance says those records are protected.

Voids and refunds

Review whether adjustments appear in the expected business day and whether they require separate handling. A close command should not be used to conceal an unresolved exception.

Operator access

Use an authorized account and preserve the audit trail. Record who performed the close and the displayed result without saving cardholder data.

Controlled procedure

Use a repeatable closeout checklist

1. Confirm the business day

Check the location, register, date, time zone, and reporting period. This reduces the risk of reviewing or closing the wrong group of transactions.

2. Resolve documented exceptions

Follow the official workflow for open checks, unsettled tips, pending payments, and offline records. Escalate anything you cannot identify.

3. Run the approved command

Use the exact close or settlement function documented for the system. Do not assume a report-only action also submits transactions.

4. Save the result

Confirm the on-screen status and retain the appropriate batch or closeout reference. Compare it with the provider portal before considering the process complete.

Know the boundaries

Closing, reporting, and bank transfer are related but distinct

A manual close may finalize eligible payment records, while an end-of-day report summarizes activity and a transfer schedule determines how a provider groups funds for movement. One action does not necessarily guarantee that all three occurred, and a completed close does not by itself establish a bank-arrival time.

Avoid timing promises: provider rules, account settings, transaction state, weekends, holidays, and bank processing can affect later steps. Use the provider portal for the current status.

Troubleshooting

If the batch will not close, preserve the evidence

Capture safe details

  • Exact error message and time
  • Location, register, and terminal identifier
  • Batch or closeout reference
  • Count of open or pending records
  • Steps already completed

Keep secrets out

  • No full card numbers or security codes
  • No PINs, passwords, or bank credentials
  • No secret API keys
  • No unredacted receipts
  • No unsupported guesses about a transaction

Common questions

Manual batch close FAQ

Is manual close required every day?

It depends on the provider and configuration. Some systems use scheduled closing, while others require or allow an operator step. Check the current account and device instructions.

Is printing a report the same as closing?

Not necessarily. A report can summarize activity without submitting or settling transactions. Confirm the function and resulting status in the provider portal.

What if open payments remain?

Do not force the close or invent a resolution. Follow the documented process for tips, checks, captures, or pending records and contact provider support when the status is unclear.

Should I reset a terminal after a close error?

Only when official instructions call for it and pending or offline transactions are protected. First record the error and confirm transaction status.

Last editorial review: August 12, 2026. Sources reviewed: current official Square settlement, close-of-day reporting, and close-of-day timing guidance.

Next step

Document the closeout procedure for each payment setup

Confirm the responsible person, cutoff, exception checks, exact close command, and saved result using current provider instructions.

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