Open Sales → Receipts in the retail workspace or Money → Receipts in the service workspace. Both use the same receipt-history and receipt-detail screen; Money retains its own navigation and direct receipt route. Opening a receipt is detail UI state: CentriPOS stores it as openSaleId and keeps the receipt list’s search, date, customer/association, location, register, user, status, report receipt-set, and saved-view scope intact. Do not confuse openSaleId with saleId; saleId filters the list to a receipt set. Receipt surfaces contain private customer and financial data, so the Harbor & Hearth capture was intentionally rejected rather than published.

Before you beginConfirm the customer-safe sale or order reference, its location, and its current fulfillment status before making a change.

Step by step

  1. Open Receipts from Sales or, in a Money workspace, Money → Receipts. Confirm the business, location, register, user, and any active receipt-status filter before interpreting results. Roles can limit records to permitted sales and operating scopes.
  2. Start with All sales, Continue sale, or a pinned/saved receipt view. Continue sale is a workflow view for saved sales that can be resumed; it is not a second copy of completed receipt history. Opening a saved view reapplies its stored filters to current data.
  3. Use the receipt search for supported receipt text, amount, customer, and other indexed sale values. Apply Status, date/time range, user, location, register, customer, household/company association scope, or report-provided receipt set as needed. More filters moves the full filter set into a compact sheet on smaller layouts.
  4. Read active filter chips and the refined-search label before concluding a receipt is missing. Clear only the suspect filter first. Clear all filters returns to the default receipt scope but does not grant broader permissions or reveal records outside role/location/register restrictions.
  5. Use Views to create a Personal or Shared saved filter configuration. Shared view management requires its permission. A user can update a personal view they created; shared edits require shared-view authority. Names must be unique within the applicable scope, and only the configured maximum number of views can be pinned for quick access.
  6. Select a receipt row/card. CentriPOS adds openSaleId to the URL and expands the receipt details where you are without changing the underlying list query. Closing the panel removes only openSaleId. Changing the receipt search intentionally closes the previously open detail because the result set changed.
  7. Read the receipt header, lifecycle/status badges, receipt number/date, location/register, selling user, customer, total, balance, fulfillment, communications, and payment/accounting indicators before using an action. An authorized or pending payment is not settled cash; inspect the payment status and source record. Use related customer, fulfillment, external order, or QuickBooks links only when present.
  8. Review every receipt line including quantity, product/variant, price, discounts, tax, fulfillment method/status/date, returned quantities, connected purchase order, and notes. Then reconcile subtotal, discount, tax, payment/tender rows, refunds/returns, account balance, and total rather than trusting a single headline.
  9. Use fulfillment status/date controls only when the receipt and permissions allow it. A row can link into Fulfillment Center, identify unscheduled open fulfillment, or show completed/other lifecycle state. Updating fulfillment is an operational change, not a receipt-note edit.
  10. Use Continue sale only for an eligible saved sale. CentriPOS checks the original register/location, register session, active editing window, and the single Sell-workspace lock on this device. It may require switching context or opening a closed register with an opening float/note. Do not bypass a lock by duplicating tabs.
  11. Use Process return or the refund control only when the receipt is eligible and the effective user has pos.refund. Review original quantities, prior returns, payment path, and refund destination before confirming. An uncertain processor result must be traced before retrying.
  12. Use Edit sale only with pos.edit_sale and only for fields the edit dialog supports. Use Void only when lifecycle rules and pos.void permit it; saved-sale abandonment/cancel flows can require a disposition, configured reason, notes, and a decision about reactivating fulfillment. These are auditable changes, not ways to hide a mistaken receipt.
  13. Use Email receipt to review To, optional CC/BCC, subject, message, Receipt style, Store policies, and Receipt template. Standard receipt, gift receipt, and delivery-sheet output have different disclosure. Never add an address that should not receive the customer’s receipt.
  14. Use Print to choose Print style, supported Paper size, Store policies, and Receipt template, then inspect the browser/system destination before printing. Use the separate Star PassPRNT option only on the supported iPad/iPhone path. Print one safe test before a batch.
  15. Use Log interaction or open a submitted interaction only when communications tracking applies. Invoice attachments can be viewed/downloaded or managed according to permission; do not upload or expose files unrelated to the customer account invoice.
  16. For QuickBooks, distinguish a linked invoice, Send to QuickBooks for an eligible account receipt, match/relink controls, and More actions. Never repair an accounting link merely because the button exists; verify tenant, customer, receipt/invoice, amount, QBO target, and the complete sync path first.
  17. When more rows exist, use Load more rather than changing filters mid-investigation. After any return, void, edit, fulfillment update, email, print, interaction, attachment, processor, or accounting action, refresh the receipt detail and verify the intended state plus its activity/audit evidence.

Screen and contract reference

Control or areaWhat it means
All salesDefault receipt-history view using the active filters and permissions.
Continue saleSaved-sale workflow view for receipts eligible to resume in Sell.
ViewsPersonal and shared saved receipt-filter configurations.
Pinned viewQuick-access saved view; pinned count is capped by the sales-view configuration.
Modified saved viewActive filters differ from the saved configuration and can be saved as a new view or updated when authorized.
Receipt searchSearches supported receipt text, amount, customer, and indexed sale fields.
StatusLifecycle filter such as completed, saved, voided, returned, or account state as supported by the current model.
Date / time rangePreset or custom receipt period serialized into the URL.
UserSelling-user filter; own-sales-only permission can further restrict results.
Location / registerOne or more operating scopes, still subject to user and restricted-register permissions.
Customer / association scopeSpecific customer IDs or household/company association receipt scope.
Receipt set / saleIdReport- or URL-provided set that filters which receipts belong in the list.
openSaleIdSelected detail-panel state only; it must not rerun the list against a different receipt set.
Refined search labelHuman-readable description of a report/refined result scope.
Clear all filtersReturns to default filters without changing permissions.
Receipt row/cardSummary with lifecycle, date, customer, location/register, amount, fulfillment, interaction, attachment, integration, and closeout indicators when available.
Detail panelExpanded receipt inspection kept in place within the current list.
Close sale detailsRemoves openSaleId and collapses the selected detail without clearing the list.
Customer profileOpens the linked customer when the receipt has a customer ID.
Fulfillment CenterOpens related fulfillment work for eligible receipt lines.
WooCommerce orderExternal order link when the receipt carries the connection.
Items and totalsLine quantity/product/variant/price/discount/tax/fulfillment/return context plus reconciled receipt totals.
Payments / balance dueTender, account, refund, and remaining-balance evidence; verify against processor and A/R records when applicable.
Continue sale lockPrevents simultaneous Sell editing on the same device and enforces session/context checks.
Process return / refundPermission- and lifecycle-gated return/refund workflow.
Edit salepos.edit_sale-gated dialog for supported receipt changes.
Void / saved-sale dispositionPermission- and lifecycle-gated cancellation or abandonment decision with reason/note and possible fulfillment handling.
Email receiptRecipient, subject/message, style, policies, and template workflow.
PrintReceipt/gift/delivery style, paper, policies, template, and browser/system destination.
Log interactionCreates or opens communication evidence connected to the receipt.
Invoice attachmentsCustomer account-invoice files with controlled download/actions.
QuickBooks controlsLinked invoice, send, match/relink, or more actions shown only for supported accounting state.
Load moreFetches the next receipt page without changing active filters.
Activity / audit evidencePost-action verification for receipt lifecycle, communication, fulfillment, payment, and accounting changes.
No public screenshotThe Harbor & Hearth receipts capture exposed customer, receipt, phone, amount, date, location, and status data and was rejected; this guide intentionally has no invented replacement.

Expected result

The selected receipt opens in place without changing the receipt list’s date, location, register, status, search, or saved-view scope.

Troubleshooting

  • Keep the current receipt or order filters in place while opening details.
  • Check the record status and activity before repeating a send, return, or fulfillment action.
  • Use a safe receipt or order reference when contacting support.

More guides

Build an itemized payment in MoneyUse Products or Amount & description to build one receipt, attach the customer, and follow the appropriate payment or service-estimate workflow.
Take a one-time payment in Virtual TerminalReview a one-time amount, tax and contact at the correct payment station, use its verified secure checkout, and recover the original receipt after an uncertain result.
Review booking payments, refunds and earned careKeep a booking’s customer payments, unused advances, completed care, cancellation fees and refunds distinct, then read a correctly scoped accrual report.
Configure booking properties and customer pagesSet accommodations, service packages, availability, required intake and payment terms, then review the correctly branded booking page before sharing it.