PROCESS RITE · PAYMENT WORKFLOW GUIDE

Salon POS Reporting: Services, Products, Deposits, Tips and Daily Close

Set up a salon reporting pack that separates service activity, retail stock, deposits, package redemptions, staff attribution and settlement.

In this guide

Give each report one defined purpose

A salon owner needs to distinguish completed services, money collected, future appointment deposits, product movement and amounts prepared for payroll. Those questions may use different reports. A single dashboard total is not a reliable substitute when it combines records with different meanings or date boundaries.

Name the report and owner for each task. Reception may need an unpaid-appointment list; the stock owner needs product sales and returns; payroll needs the approved staff and tip record; reconciliation needs tender and settlement detail. Save the filters and reporting period beside each scheduled export. Explain what the report excludes so another employee does not use it for an unrelated decision.

Define service and retail categories before launch

Keep services and retail products recognisable in the catalogue and reports. A product added to a service ticket should reduce the correct stock record without becoming a service performed by the receptionist. Ask the provider to show the category and attribution of each line, not just the final receipt total.

Use consistent service names and maintain the mapping when prices or staff change. An employee creating a near-duplicate service can divide the history across records. Assign permission to catalogue maintenance and retain a correction process. Your accounting adviser should approve tax and account mappings rather than accepting a device’s defaults as the business policy.

Report deposits by appointment and collection date

A deposit collected this week can relate to an appointment next month. Keep the collection date, intended appointment and applied amount identifiable. A deposit report is useful only if reception can connect its entries to the booking record and identify unapplied balances.

Test a rescheduled appointment and a new deposit taken while the guest pays for today’s visit. The new collection should not silently inflate completed service activity. Have the bookkeeper approve accounting treatment separately from the technical allocation. A report’s label does not establish whether an amount is earned revenue or how it belongs in the financial accounts.

Keep package redemption separate from a general discount

Identify the system that owns remaining package services or gift balances. A redemption may reduce an entitlement without creating a new card payment at that visit. If the salon uses a generic discount button instead, reports may show reduced service sales without explaining the remaining obligation to the guest.

Demonstrate one redemption with a separately paid product. Inspect the appointment, package balance, tender and receipt. Confirm how refunds or cancellations affect the remaining balance through the supported workflow. Before migration, reconcile opening balances and retain the records needed to resolve a later question rather than assuming every entitlement imports with the client list.

Approve staff and tip attribution with payroll

Confirm whether the staff report credits the appointment owner, service professional or payment taker. Those can be different people. A receptionist closing a ticket should not unexpectedly receive every service and tip in the report used by payroll. Test a visit with two professionals and an adjusted service line.

Keep voluntary tips and service charges identifiable. The payroll owner should approve calculations, distribution and corrections under the salon’s policy and applicable advice. Record when the export becomes final and how later adjustments are handled. Do not treat the name of a software report as confirmation that the underlying payroll treatment is correct.

Create a repeatable reception closeout

At close, check completed appointments, open balances, deposits applied, tender totals and supported refunds. Compare product activity with stock changes separately. A package redemption and a new card collection are different events even if both appear on completed appointments.

Retain the report generation time and business-day cutoff. A late appointment completion or tip adjustment can explain why a later export differs. Save the original packet and record the approved update rather than overwriting the only evidence. Give a backup receptionist the procedure and ask them to reproduce the close using the same filters.

Match payment records to provider settlement

The salon’s net service sales are not automatically its card batch or bank deposit. Product sales, tax, tips, cash, refunds and deposit collections can affect the relationship. Use provider settlement detail and references to bridge the card activity to the bank, including only documented deductions and adjustments.

For an illustrative appointment, a $180 service with a $40 earlier deposit leaves $140 before other approved additions. A $25 product paid at checkout adds another collection requirement, but its stock and sales category remain separate. Trace each component rather than comparing the combined receipt to a service-only report and assuming money is missing.

Control exports and recurring report delivery

Decide which employees receive staff, sales and client-related information. A report can contain more personal detail than a manager needs for a daily total. Use the salon’s approved access and retention process, and remove access when staff responsibilities change.

Check scheduled report delivery and ownership of failures. A useful report that nobody receives or reviews does not complete the control. Record who investigates exceptions and how another employee takes over. Avoid sending full client records or payment credentials to a general support address simply because an export makes it easy to include them.

Test the packet before changing the reporting routine

Use a fictional visit with an existing deposit, two professionals, a product purchase, package redemption and a product-only return across suitable test records. Verify the appointment, stock, staff, tender and settlement references. Confirm which tasks are included in the quoted software plan and which require another application or manual step.

Have reception, payroll and the reconciliation owner approve their parts of the packet. Preserve the existing definitions before changing categories or cutoff settings. Review the first week’s exceptions and the first complete statement after rollout. Reporting setup is complete when the team can explain the records and repeat the process, not merely open a dashboard.

Keep appointment balances and staff attribution clear

Identify the booking platform that owns the appointment, client record and service ticket. A payment device should not become an accidental second appointment ledger. If the systems remain separate, write down how reception confirms the amount, checks the payment result and marks the appointment complete. If a connector is proposed, demonstrate its exact supported handoff and correction process.

Show an appointment whose agreed services change during the visit. Reception needs the final amount and service attribution before the guest pays. Confirm who can change a price, how the change reaches the ticket and who approves exceptions. Repeated manager overrides may indicate a service-catalogue problem rather than a reason to replace the payment device.

Apply an existing deposit to the final balance, then book a future appointment with a separate new deposit. The two amounts should remain distinguishable. A booking confirmation showing a deposit does not prove it was applied to the right visit. Test rescheduling and a deposit attached to an incorrect appointment, using the provider’s supported process.

Include a retail product and a product-only return. Confirm stock changes without reversing the service or its staff credit. For packages or gift balances, verify the remaining entitlement rather than substituting an arbitrary discount. Before migration, establish who reconciles opening balances and what historical records remain accessible.

Tips and service charges need distinct records and an approved payroll handoff. Check which professional receives the service and tip attribution when reception takes payment or multiple people serve one guest. The salon’s advisers should confirm treatment and distribution. A software report can support that process without establishing the correct payroll policy by itself.

Run a traceable acceptance exercise

Use an appointment with a deposit, two service professionals and a product-only return as the starting scenario. Keep the records fictional or use the provider’s supported test facilities. Define the expected result before the demonstration: the amount due, responsible employee, payment status and final state of the booking and service ticket. This prevents an impressive screen transition from replacing a meaningful outcome check.

Have the receptionist, service professional, manager and payroll owner each inspect the part they rely on. One person may confirm a device approval while another still sees an unpaid balance or an incorrect operational record. Record those differences rather than assuming the first success proves the entire process. Ask the employee to repeat the workflow under the permissions proposed for normal use.

For this reporting configuration, capture a normal case, a correction and an interrupted handoff. Record whether each step is automatic, manual or unsupported in the quoted configuration. Include the application and provider that perform the step. A test led by an administrator should be repeated with the intended staff role wherever the task depends on permissions.

Save the relevant non-sensitive references and the report filters. Recheck the result after the applicable business-day or settlement boundary. A later adjustment may change what the first screen showed, so the acceptance record needs a time as well as an amount. Resolve any contradiction before treating the workflow as complete.

Make the evidence usable for the next employee

Keep a short procedure beside the test record. It should tell the next employee how to locate the appointment, confirm its payment status, identify the authoritative booking and service ticket and find the correct support route. Include the stopping point when a result is uncertain. A procedure that merely says “contact the manager” leaves the manager without the references needed to investigate.

The reception manager should approve the closing check and the ownership of unresolved exceptions. Give each open item a description, reference, amount where relevant, responsible person and next action. Retain the original evidence rather than overwriting it with a corrected total. The history should explain why the final record is now considered correct.

Keep credentials, full card details and unnecessary customer information out of the worksheet. Arrange secure document sharing when a provider requires more evidence. A redacted report can still expose sensitive details if identifiers are left in notes or filenames, so review the whole document before sharing it.

After the first operating period, look for repeated exception categories. A recurring manual adjustment may indicate a configuration or training dependency that belongs in the implementation scope. Review that evidence before adding another location, device or sales channel. The objective is a repeatable process your staff can verify, not a one-time demonstration that only the vendor can explain.

Prepare the review without exposing private records

Summarise the business, current software, payment channels, locations and the specific appointment problem you want resolved. Include a non-sensitive example and the outcome you expected. That gives a review more direction than a general request for better rates or a new device. List existing components you want to retain so proposals account for them.

Process Rite helps organise the payment requirements, provider questions and written comparison. Availability, integration, account approval, implementation and service terms need confirmation in the applicable proposal and provider agreement. Hardware, software, applications and processing charges should remain identifiable. Request a custom proposal based on the configuration and channels your business actually needs.

Use the website enquiry for the summary, then arrange document sharing after contact. Do not submit payment credentials, bank logins, passwords or private customer records. Include your town and preferred callback time so the conversation starts with the right context. Consultations and any site work are arranged directly. Confirm the responsible support contact and available service hours in the proposal.

Why do completed services differ from money collected?

Today’s collections may include deposits for future visits, retail products, tax and tips, while today’s completed appointments may redeem earlier deposits or packages. Define those components before comparing totals. Keep their appointment and payment references visible. The reporting packet should explain the relationship and give payroll, stock and reconciliation owners the records they need without treating one dashboard number as every answer.

Continue with a related workflow guide

Acceptance record to keep with the decision

Use fictional test records and your approved operating policy
Check Evidence Owner
The existing deposit reduces the correct appointment balance. Record the observed result and reference. Name the staff or provider owner.
Service and tip credit stay with the approved staff record. Record the observed result and reference. Name the staff or provider owner.
A retail return does not reverse the completed service. Record the observed result and reference. Name the staff or provider owner.
Rebooking creates a separate, clearly identified future appointment. Record the observed result and reference. Name the staff or provider owner.

Discuss your actual setup

Tell Process Rite your business type, current software, payment channels and the problem you want resolved. We arrange document sharing after contact. Do not include card details, bank credentials or customer records in the enquiry.

Request a free payments review · Understand the complete cost · Find the right support route

Hardware, software, apps and implementation are separately quoted. Availability, integration, pricing and approval require confirmation in the written proposal. A review does not guarantee savings or approval.

Secure lead review

Request a Focused Payments Review

Tell us your current software, business type and the workflow you want to improve. Arrange document sharing after contact.

Text preferences (optional)

Support frequency varies; promotions: up to 4/month. Message and data rates may apply. Reply STOP to opt out or HELP for help. Consent is optional and not a condition of purchase or service.

Scroll to Top