Batch troubleshooting
Why Is a Transaction Missing From a Batch?
A transaction can appear missing because it was not completed, belongs to another batch or location, used a non-card tender, is waiting to sync, or is hidden by report filters. Trace the payment record before changing a batch or charging the customer again.
Start with the payment
Confirm whether the transaction actually completed
Search the POS and provider dashboard using the receipt or transaction reference, date, amount, last four card digits when permitted, device, location, and team member. Read the recorded status rather than relying only on a printed receipt, customer alert, or checkout screen.
Completed
A completed payment should have a durable provider record. If it is absent from the expected batch, compare its completion time, location, device, and settlement grouping.
Pending or incomplete
An interrupted checkout or unresolved step may not enter the same reporting flow as a completed payment. Follow the provider's current status guidance.
Failed, declined, or voided
These attempts may appear in a status or exception report instead of a completed batch. Keep the exact result and transaction reference for review.
Check the report
Remove filters that can hide a valid record
Review the date and batch boundary
Compare the transaction timestamp with the processor's batch close, business-day, and time-zone settings. A payment near the boundary may belong to the previous or next batch.
Confirm location and device
Multi-location accounts can separate reports by location, merchant account, register, or device. Search the account scope that accepted the payment.
Expand status and source filters
Include all relevant statuses, payment sources, channels, and team members. Some dashboards separate API, ecommerce, invoice, keyed, terminal, and POS activity.
Check the tender type
A sale recorded as cash, check, gift card, house account, or another tender may affect sales totals without entering a card-processing batch.
Sync and reporting
Look for delayed data before altering records
Offline or disconnected payments
Confirm the device is online and that any permitted offline payments have uploaded. Do not sign out, delete the app, reset hardware, or clear data until pending records are protected.
Open ticket or incomplete checkout
A saved order, open ticket, partial tender, signature step, or confirmation screen may leave the sale outside the completed-payment batch.
Report generation delay
Compare the live transaction view with the exported or scheduled report. Provider reporting incidents or generation delays can make a report temporarily incomplete.
Wrong account context
Verify the merchant account, location, environment, and user permissions. A record can be present but invisible to a user with limited scope.
Reconcile safely
Build a simple evidence trail
Compare source records
- Receipt or order reference
- POS transaction history
- Provider dashboard status
- Batch detail and exception reports
- Device, location, and tender records
Protect sensitive data
- Use sanitized transaction references
- Share only the last four digits when appropriate
- Never send full card numbers or security codes
- Do not include passwords, PINs, or API keys
- Keep screenshots free of customer data
Related resources
Review connected parts of the payment workflow
Common questions
Missing batch transaction FAQ
Does a receipt prove the payment settled?
No. Use the provider's transaction status and batch detail. A receipt or customer notification alone may not show the final processing state.
Could the transaction be in another batch?
Yes. Completion time, batch cutoff, time zone, device, location, or merchant-account routing can place it in a different reporting group.
Should I close the batch again?
Not until you understand the current status and provider workflow. Re-closing or altering records can complicate reconciliation without recovering the payment.
When should I contact support?
Escalate when the transaction status and reports remain inconsistent after checking filters, account scope, tender, device sync, and known reporting issues.
Last editorial review: August 12, 2026. Reviewed against current official Square transaction-search and payment-status guidance and PayPal reporting guidance.
Next step
Trace the transaction before changing the batch
Confirm the recorded status, broaden report filters, check location and tender, protect offline records, and escalate with sanitized evidence if the mismatch remains.
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