Pet business payments and reporting should be visible where the work happens
Finance workflows are operational workflows. Deposits, invoices, refunds, subscriptions, payouts, and commissions need to connect back to bookings, pets, staff, and branches.
When payment state is unclear, staff hesitate, customers wait, and owners lose confidence. A strong pet business platform makes money movement visible without forcing staff into finance tools.
Review payment state from the booking drawer
Trace one refund end to end
Check subscription repeat billing
Audit payout and payment reports
Why Collar is different: connected work, not just a calendar
Collar brings the pet-business journey into one operating picture: a customer books for a specific pet, the team delivers the service, and the related order, payment and follow-up stay connected. Depending on the business, that same platform can also support products, memberships, staff, branches and field routes. The value is in how the enabled parts work together—not a claim that other tools cannot offer them.
01Booking
→
02Pet + customer
→
03Service delivered
→
04Order + payment
→
05Follow-up
Ask in a product demo
Why it matters
What to check in Collar
Does the pet record stay with the booking?
Staff can find the right instructions for the right pet.
Follow a two-pet household from booking to service.
Do service and charges flow into the order?
The owner and team can understand what was sold and paid.
Add a service extra, take a deposit, then inspect the balance and receipt.
Can the setup support how our business actually works?
Groomers, daycares, boarders and mobile teams do not share one workflow.
Test the modules, roles and locations you plan to use; confirm limits before buying.
Four numbers that should not be mixed up
Use these plain definitions when checking a dashboard or asking why it differs from your bank statement.
Number
What it tells you
Simple example
Booking
A service was requested or reserved.
One grooming visit next week.
Order
What the customer bought.
A £100 groom.
Payment
Money collected toward the order.
£20 deposit, then £80 later.
Payout
Money sent to your bank after processing.
May arrive days after the visit.
Connect payments to orders
Every deposit, invoice, refund, and payment adjustment should be traceable to the order or appointment it belongs to.
Service and product orders
Deposits and balances
Recorded payments
Refunds and adjustments
Treat subscriptions as operations
Memberships and recurring billing affect calendars, staff workload, customer communication, and reporting.
Subscription repeats
Retry and payment actions
Membership changes
Revenue visibility
Report for owners and accountants
Branch billing reports, payouts, commissions, and payment views help the business improve margins.
Payment history
Payouts and processor reconciliation
Commission statements
Branch revenue trends
Reconcile a real service story
A £100 fictional service can have a £20 deposit and an £80 later payment. Reporting should show one £100 service, two payment events and a zero remaining balance after settlement, not £120 of revenue. Add a partial refund and verify the new balance and cash movement. This simple test exposes whether a report mixes orders, invoices, payments and payouts.
Choose the date basis for each report: booking, service, invoice, payment or payout date.
Distinguish recorded payment from money settled by a payment processor.
Reconcile credits, packages, refunds and failed payments without double counting.
Export a sample period and agree definitions with the person responsible for finance.
Define every number before using it in a decision
A booking, bill, card payment and bank payout are different things. A chart is confusing when it mixes them. Use one sample visit with a deposit, an extra service and a partial refund. Check where each amount appears.
Report service value and cash collected separately; two payment events do not create two services.
Choose whether a report uses booking date, service date, invoice date, payment date or settlement date.
Check how tax, tips, gift credit, package redemptions and refunds affect each measure.
Ask your finance person to check a short real period before using reports to set staff pay or growth targets.
Give each report a clear date basis
An owner may book in January, visit in February, pay a balance in March and receive a refund in April. A report grouped by booking date will not match a bank statement grouped by settlement date. Specify the event and date behind every chart so managers can interpret differences instead of assuming an error.
Label service, invoice, payment and payout totals explicitly.
Treat deposits as cash collected against an order, not an extra service sold.
Document how refunds and credits affect historical periods.
Explain differences between gross amount, fees and net payout.
Test access and auditability
Front desk may need to see that a balance is paid; finance needs the detailed transaction trail. Give each role the minimum useful access and test who can make a refund or edit a charge. If the system records changes, staff should know how to find the history.
Use separate test accounts for frontline, manager and finance roles.
Try a partial refund and a failed payment in the same sample period.
Export a small report and compare it with original orders.
Decide how often to check reports against payment records and who fixes differences.
