PROCESS RITE · PAYMENT WORKFLOW GUIDE
Salon Payment Report Mismatch: Find and Resolve the Difference
Trace differences between salon sales, tips, deposits, processor activity and bank settlement. Start with the records and date filters before changing systems or collecting again.
In this guide
Identify the two numbers that do not match
Start with a precise statement: “Tuesday’s salon card-tender report shows one amount, but the processor batch shows another.” That is a more useful problem than “the POS is wrong.” Record the report names, date filters, location, user filters and totals before changing anything. Save the original exports so another person can reproduce the comparison. Screenshots alone may hide filters or omit the rows that explain a difference.
A salon has several legitimate totals: service sales, product sales, tips, payments collected, staff production and bank deposits. They answer different questions. A stylist’s production figure does not necessarily equal card collections, and collections do not necessarily equal the next bank deposit. Establish what each report measures before treating the difference as missing money. Then follow the individual records between systems.
Use a three-stage reconciliation
First compare the salon’s payment record with processor transactions. Next compare processor transactions with the settlement or batch record. Finally compare settlement with the bank entry. This separates a posting problem from a timing or funding question. If the first comparison fails, jumping directly to the bank statement usually adds confusion because the bank may combine activity or reflect later adjustments.
Keep a short worksheet with the source total, comparison total, difference, period and evidence. List each reconciling item rather than writing one unexplained adjustment to force equality. Assign an owner and a follow-up date to anything unresolved. Once a documented timing difference clears, link the later record and close the item. Preserve the explanation so next month’s reviewer does not investigate the same event again.
Match business dates and batch boundaries
Check whether both reports use the same time zone, start time and end time. An appointment that finishes late in the evening may appear in one business-day report and a different processor period. An employee report filtered by appointment date can also differ from a payment report filtered by collection date. Write down those definitions using the software’s actual report labels.
Select one transaction near the boundary and trace it through both exports. Do not change automatic closeout settings simply to make today’s totals agree; first understand the current arrangement and confirm the implications with the provider. Bank weekends, holidays and the account’s actual funding arrangement may affect the bank comparison. Use documented settlement detail, not an assumed universal next-day schedule, when deciding whether a deposit is late.
Separate tips from service and product revenue
A payment can include a service amount, a product and a tip, while the salon sales report lists those in separate categories. Check whether the processor figure includes the complete payment. Then inspect whether the staff report includes tips, excludes them or allocates them to a different employee. A report used for compensation should have an approved interpretation rather than being chosen because its grand total looks convenient.
For an illustrative transaction, a $100 service, a $20 product and a $15 tip create a $135 payment before any other applicable amounts. Comparing $120 of sales with $135 collected produces a $15 difference without any missing payment. Confirm the real configuration and accounting treatment with the salon’s responsible adviser. This example explains report scope; it does not prescribe how tips or taxes should be accounted for.
Trace appointment deposits across both visits
Online deposits often arrive before the appointment. At the visit, the booking system may apply that deposit while the terminal collects only the remaining balance. Compare the payment history and appointment ledger, not just today’s completed-service total. Look for deposits recorded as another sale during checkout, deposits not applied at all and deposits attached to the wrong appointment after rescheduling.
Suppose a customer paid $30 last week toward a $120 appointment and pays $90 today. Today’s service and today’s new collection describe different activity. The combined history should identify the $30 and $90 collections and the balance they satisfy. A staff note is not enough if a second employee cannot locate the original transaction. Confirm how the booking and payment applications represent the deposit in their respective exports.
Check gift cards, packages and account credits
Gift-card redemption can settle a salon ticket without producing a new card transaction that day. Gift-card issuance may produce a card payment while appearing separately from completed services. Packages and salon credits can create similar differences. Identify the system that stores each balance and verify whether the report totals represent issuance, redemption, service delivery or cash collected.
Inspect a mixed payment using a gift balance and a card. Confirm that the POS attributes only the card portion to the card tender and that the remaining gift balance is correct. If an old gift programme remains active after a system change, keep its redemption records distinguishable. Do not assume a provider migration transferred balances simply because customers can still present the same branded card.
Distinguish voids, refunds and discounts
Discounts change the sale under the salon’s approved rules. Voids and refunds affect records differently depending on the transaction state and system. Compare the original transaction reference, correction reference, amount, status and effective date. A refund entered today against last week’s payment can make today’s payment total differ from today’s service activity even when both records are correct.
Look for a correction applied in only one application. A receptionist may cancel an appointment without refunding its payment, or refund through the processor without updating the booking ledger. Do not issue another refund until the source status has been checked. Record the approved correction procedure and who can perform it. Keep customer communications consistent with the actual confirmed status rather than promising an unverified bank posting date.
Investigate split tender and uncertain transactions
A customer may pay partly in cash and partly by card, or use two cards. Reconcile each tender against the correct destination. The ticket total should not be compared with just one card payment. Check whether a partially paid ticket was incorrectly marked complete or whether staff created a second ticket while trying to finish the original one.
For an uncertain approval, search the supported processor transaction view using safe references, time and amount before retrying. A stalled screen does not prove that the charge failed. If two charges are found, have an authorised employee follow the provider’s correction process and retain both references. Avoid editing salon totals first and investigating later; the original records are needed to understand what actually happened.
Keep separate businesses and locations separate
Where independent professionals operate under their own payment arrangements, do not combine their collections with the salon’s processor account merely because appointments share a calendar. Identify the legal business, location and merchant account associated with each payment. A booth-rental or shared-reception arrangement needs an agreed operating procedure; a single device does not establish the correct funds flow.
For multiple salon locations, check whether an export includes all locations by default. Match the merchant account and bank destination before investigating a total. Also distinguish the employee who performed a service from the employee who collected payment. Moving an appointment between staff members can change production reporting without moving the original payment to another processor account.
Use transaction identifiers rather than customer names
Names can be misspelled, duplicated or changed. Build the reconciliation around stable references where the systems provide them: booking or ticket identifier, processor transaction reference, batch reference and settlement reference. Record how those identifiers connect. If an integration does not export a common reference, ask the provider to demonstrate a reliable matching method using the fields actually available.
A useful exception row includes the expected amount, actual amount, transaction time, source system, status and next action. Use only the customer information needed by authorised staff. Do not copy full card numbers or unnecessary client records into a shared spreadsheet or ordinary support email. Demonstrations and public examples should use synthetic records rather than exposing a real client’s appointment and payment history.
Read settlement deductions instead of estimating them
Once salon and processor transactions agree, inspect the settlement record. Determine whether fees are deducted from deposits, billed separately or handled through another documented arrangement. Identify refunds, disputes and other adjustments by their actual references. A different bank amount does not, by itself, establish that the quoted processing rate changed or that the processor withheld unexplained funds.
For example, if an identified settlement record starts with $2,000 and lists a $50 refund and a $20 documented deduction, $1,930 is the arithmetic result of those entries. The explanation is valid only if those are the real entries for that settlement. Never infer a fee or create a fictional deduction merely because it makes the bank total balance. Escalate unsupported differences with the relevant evidence.
Prepare a support request that can be investigated
State the expected result, actual result and first known occurrence. Include the report names, date filters, affected location and safe transaction references. Explain whether the problem affects one ticket, one employee, one batch or every transaction since an update. This helps the support team decide whether to examine report configuration, an integration, payment processing or settlement.
Send the issue to the party that owns the failing stage. Booking allocation belongs with the booking or integration provider; processor transaction and settlement questions belong with the appropriate payment provider. Process Rite’s support page helps organise an enquiry and callback request. Confirm availability and escalation arrangements directly. An online intake form is not evidence of continuous staffed human coverage.
Make corrections traceable and limited
Before changing a record, identify which system is authoritative for that field and obtain the required approval. Correct the underlying issue through the supported process, then verify downstream reports. Keep the original reference, correction reason, employee and time. Do not erase history or post an unexplained cash adjustment simply to remove a visible variance.
If a connector is responsible, request a test showing how a repeated event is handled. The solution should avoid duplicate payment posting when an event is delivered or retried more than once. Have a second employee check a small sample after the fix. A corrected dashboard total is not sufficient if appointment balances, refunds or staff attribution are now wrong in another report.
Set a daily close and a weekly exception review
Daily close should identify obvious missing payments, duplicate collections, drawer variances and unposted corrections while staff still remember the events. The weekly review should follow open settlement and posting differences through to resolution. Give each exception a status, owner and due date. Use a documented escalation threshold approved by the owner rather than allowing small unexplained differences to accumulate indefinitely.
Record the report settings used for every close. When software changes, compare the old and new report definitions before assuming the business suddenly developed a collection problem. Train a backup employee to repeat the process from the written instructions. The goal is a control the salon can maintain during staff absence, busy periods and provider updates, not a spreadsheet that only its original author understands.
Test the fix with a small acceptance set
Use synthetic or provider-approved test transactions covering a standard service, product addition, tip, earlier deposit, gift redemption and partial refund. Write down the expected sales, tender and staff-report effects before the test. Trace the records through settlement where the test environment supports it, or agree a controlled verification procedure with the provider for the remaining stage.
After a real operating day, review the exception log and first affected settlement. Compare the next full statement against the written arrangement if cost was part of the problem. For broader setup decisions, use the salon POS guide and salon online-payment guide. Replacing a device should follow an identified need; it is not an automatic solution to a report-definition mismatch.
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.