Reports

Trace Individual Sale Payment Transactions

This tab is the bill-level trail for completed and partially returned sales. Use it when a payment-method total does not match the till or external provider.

Menu path
Reports -> Money -> Payment -> Sale Payment Transactions
Verified from
Posnic demo and current POS source reviewed on 2026-09-08
Technical source evidence

frontend/modules/paymentReport.html, frontend/static/script/js/modules/js/report_payment.js paymentransaction, api/src/controllers/sales.controller.js paymentSalesTranscationReportTable, api/src/repositories/sale.repository.js paymentSalesTransactionReportPage

Sale payment transaction trailLive demo captured 2026-09-11. The first five of 14 rows show the newest recorded sale payments first.

Find a Payment

  1. Open Reports -> Money -> Payment.
  2. Choose Sale Payment Transactions.
  3. Open Filter and select date range and branches.
  4. Select one payment method when investigating a specific tender, or keep All.
  5. Apply.
  6. Locate the Sale ID and compare its Date, User, Method and Amount with Sales History and settlement evidence.

What Each Row Proves

FieldMeaningLimit
SaleSaved Posnic sales identifier.It is not an external card or UPI reference.
DateSale date used for filtering and newest-first sorting.The screen formats updated_date for display, so retain the report scope during an audit.
UserUser saved on the sale.Shared credentials weaken attribution.
MethodSale-level payment_mode value.A split sale's method detail may be better represented in the Types summary and original bill.
AmountThe sale's items_total.It is not necessarily net cash movement after later returns.

Reconcile an Unexpected Transaction

  1. Open the matching Sale ID in Sales History.
  2. Confirm the customer, items, total and tender choices.
  3. For split tender, inspect the original payment breakdown instead of assuming this one row lists every component.
  4. Compare card, UPI or wallet evidence with the provider using the same time window.
  5. Check Return Sale Payment Transactions for later refunded money.
  6. Document any correction or unresolved variance.

Export and Access

  • Export All To CSV requests every matching row and creates payment-sales-reports.
  • CSV fields are SaleId, Date, UserName, PaymentMethod and Amount.
  • Pagination controls show 5, 10, 25, 50 or 100 rows on screen.
  • The endpoint requires Report Read permission.
  • A session-filtered user can receive a narrower permitted date scope.

Troubleshooting

ProblemCheckAction
Sale cannot be foundExact Sale ID and branchSearch Sales History in the same branch.
Method does not show split componentsOriginal bill multi-payment dataUse the bill and Types totals together.
Amount differs after a returnReturn transaction and current sale stateReconcile gross collection and refund separately.
Expected row is absentSale process, date, branch and method filterWiden the correct scope; eligible processes are Add, Edit and PartialReturn.
CSV button is disabledWhether matching rows existCorrect filters and access before exporting.

Related Manual Pages

Reports Payment Method Reconciliation The Types tab is the payment-method control total. Run it for the same branch and time window as the till close, then compare each method with the drawer, terminal, bank or wallet evidence. Reports Return Payment Transactions The return-payment tab is the refund trail for partial and full returns. An empty result means no matching return records in the selected scope, not that returns are disabled. Reports Day-End Summary Day-End Summary is the owner and cashier close report for the selected date range and branch. It ties sold items, tender totals, discounts, tax and shop identity into one review.