Skip to main content

Sales and Payments

Open Store Operations > Sales & Payments to reconcile sales and payment activity for the selected store. The page requires transaction read access. Its default date range is the last 30 days.

Find a sale or payment​

  1. Confirm the selected store.
  2. Set From and To to the period you need.
  3. If you have a reference, enter the exact transaction number, processor reference, POS ID, or Gateway ID in Transaction or payment reference.
  4. Optionally choose one or more Channels. Select Clear to remove the channel filter.
  5. Review the result columns:
    • Date and Txn # identify the record;
    • Source identifies its channel and transaction type;
    • Lifecycle shows the transaction state;
    • Payment shows the method and any displayed fee;
    • Amount shows the transaction total;
    • Sync shows whether the payment record is connected to the corresponding sale; and
    • Identifiers shows the available POS or payment reference.
  6. Use Previous and Next when the result spans more than one page.

If a banner says some payment data is temporarily unavailable, the page is showing in-store transactions only. Treat that result as incomplete and retry before declaring the period reconciled.

Inspect transaction details​

Select a row to open Transaction Details. Compare the following sections with the receipt or processor reference you are investigating:

  • Payment Summary: method, reference, subtotal, tax, tip, fee, discount, total, tender amounts, and change when available;
  • Line Items: product, quantity, unit price, and line total;
  • Receipt Preview: store, date, totals, processor reference, and the customer-facing receipt or item detail;
  • Card Authorization: card type, masked last four digits, authorization code, and entry method when supplied;
  • Settlement: batch status and linked batch identifiers for card payments; and
  • Customer and Compliance Checks when those records exist and your role can view them.

Select a linked batch identifier to open its record in Settlement Batches. Select Open hosted receipt when a hosted version is available. Transaction readers can also use Email Receipt or SMS Receipt to resend the receipt to a destination they enter.

A synced payment can appear before its POS transaction detail is available. If the portal asks you to select the owning store, switch to that store before reopening the detail.

Understand viewing and action access​

Transaction read access opens the list and detail. The portal exposes additional controls only when the role has the required permissions and the transaction is in an eligible state:

  • Capture requires store.transactions.write and is available for an authorized transaction.
  • Refund, Tip Adjust, and Void Transaction require both store.transactions.write and store.transactions.admin.
  • Return Items requires store.returns.write and store.transactions.admin, and the original transaction must contain a returnable product line.
  • Export requires store.reports.read.

A card transaction cannot be voided after its batch has closed. A void of an uncaptured authorization restores reserved inventory; voiding a completed sale before settlement does not change inventory. Use the confirmation copy shown by the portal before proceeding.

Do not repeat a payment-changing action merely because the screen response is delayed. Reload the transaction first and verify its current lifecycle, refund, or batch state.

Export the reviewed period​

If your role has report read access:

  1. Set the selected store and date range.
  2. Open Export.
  3. Choose CSV, Excel, or PDF.
  4. Save the generated file and confirm that it represents the same store and dates you reviewed.

The export uses the selected transaction date range for the selected store. It is separate from the organization-wide invoice receivables export.

Finish reconciliation​

A review is complete when you have confirmed:

  • the correct store and date range;
  • the expected transaction lifecycle and sync status;
  • payment method, amount, reference, and receipt details;
  • refund or return outcomes, if any;
  • the linked settlement batch for card activity, when assigned; and
  • any degraded-data warning has cleared or is accounted for.

Use Returns and Settlement Batches to audit return records and Gateway batch history. If a duplicate charge, failed refund, missing payment detail, or unsettled batch remains unexplained, follow Troubleshooting and provide Peak Support with the store, transaction or Gateway reference, time, amount, and exact message shown.