Checkout looks simple from the customer’s side: tap, insert, swipe, scan, or pay cash.
For many small businesses, the point of sale can be a countertop terminal, tablet, mobile reader, online checkout tied to the same sales system, or a payment link attached to an invoice.
The POS system is the tool. The POS transaction is the sale, refund, void, exchange, authorization, or payment event the tool records.
If you’ve seen the phrase point of sales transactions, the standard business term is point-of-sale transactions or POS transactions.
The Bank of Canada’s Methods-of-Payment Survey page says contactless card payments remain the dominant in-person payment method in Canada, accounting for more than 60% of transactions by both volume and value.
Authorization is not the same as settlement
One of the most common POS misunderstandings is thinking an approved card payment is the same thing as money in your bank account. It isn’t.
U.S. Treasury’s Card Acquiring Service describes card processing in two broad parts: authorization, then clearing and settlement. The same distinction matters for retail merchants. The approval message tells your POS whether the card issuer approved or declined the payment at that moment. Settlement is the later process that reconciles transactions and moves funds through the payment system.
Payments Canada also lists point-of-sale transactions among the electronic payment streams in Canada’s retail batch payment system. In practice, your checkout screen, processor report, and bank deposit are related records, not replacements for one another.
The sale total is created. The POS adds items, quantities, taxes, tips, discounts, gift cards, loyalty credits, and any other payment adjustments.
The customer chooses a payment method. They may tap a card, insert a chip card, use a mobile wallet, enter card details online, pay cash, use store credit, or split payment across methods.
The authorization request is sent. For card payments, the terminal or gateway sends the request through your processor or acquirer, through the card network, and to the card issuer.
The issuer responds. The card issuer approves or declines the transaction. If it’s declined, the sale should not be treated as paid.
The POS records the result. An approved transaction should create a transaction ID, receipt record, payment reference, and sale entry in your reporting.
The transaction is captured and settled. Approved card transactions are later sent for clearing and settlement. Deposit timing depends on your processor, batch timing, contract terms, weekends, holidays, and risk review.
The deposit hits your business account. Depending on your processor, fees may be deducted from deposits or billed separately. That’s why reconciling the POS total to the processor report and bank deposit matters.
Common types of POS transactions
Not every POS transaction is a simple full-price sale. Your system should handle the payment situations your business actually sees.
Cash sale: The customer pays with cash, and the POS records the sale, change due, drawer movement, and receipt.
Card-present payment: The customer taps, inserts, or swipes a physical card at a terminal.
Mobile wallet payment: The customer pays with a phone or wearable using a wallet connected to a card or account.
Card-not-present payment: The customer pays online, by invoice link, over the phone, or through another remote method. These transactions may carry different fraud rules and processor costs than in-person payments.
Split tender: The customer uses more than one payment method, such as part gift card and part credit card.
Gift card or store credit: The POS reduces an issued balance instead of processing a new card or cash payment.
Void: A transaction is usually cancelled before it settles. Exact rules depend on the processor and timing.
Refund: A completed transaction is reversed after payment has been processed. Refunds should link back to the original sale whenever possible.
Exchange: A return and new sale happen together, often with a balance owed by either the customer or business.
Pre-authorization and capture: A card is authorized first and captured later, which is common in some service, rental, hotel, fuel, and deposit-based workflows.
What your POS should record every time
A POS transaction is only useful if the record can explain what happened later. That matters for customer questions, staff accountability, inventory, tax reporting, refunds, and accounting.
The Canada Revenue Agency says businesses must keep records of transactions that support income and expense claims, and income records should include the date, amount, and source of income. The CRA generally requires records to be kept for at least six years from the end of the tax year they relate to. If you operate outside Canada, check the recordkeeping rules that apply in your jurisdiction.
At minimum, your POS should make it easy to find these details:
Unique transaction or order ID
Date, time, location, register, and device
Staff login or employee ID
Items sold, SKUs, quantities, categories, and modifiers
Subtotal, taxes, discounts, tips, service charges, and total
Payment method, tender type, and split-payment details
Card authorization code or processor reference when available
Receipt method, such as printed, emailed, or texted
Refund, exchange, or void links to the original transaction
Batch or settlement ID when your system provides it
Notes for exceptions, manual adjustments, or customer service issues
The goal is not to collect every possible field. The goal is to keep enough context to answer three questions later: what happened, who handled it, and where did the money go?
Why POS transactions matter beyond checkout
Your POS is one of your business systems of record. If it produces vague or incomplete transactions, every synced tool inherits that weakness.
Your sales report should match reality
A daily sales total is not enough. You need to know which products sold, which categories are growing, which discounts were used, which staff members handled sales, and which channels generated revenue. Generic buttons such as miscellaneous sale or custom item make checkout faster in the moment, but they weaken every report later.
Your inventory needs the exact item
If the POS records the wrong SKU or skips a modifier, your stock counts drift. That can lead to reordering the wrong products, marking items as available when they’re sold out, or missing theft and breakage patterns. The transaction should reduce the right inventory item at the right location.
Your cash flow depends on reconciliation
Your POS total, processor total, and bank deposit often differ because of fees, refunds, chargebacks, tips, batch timing, or multiple settlement deposits. That doesn’t automatically mean something is wrong. It does mean you need a repeatable reconciliation process.
Keep your payment deposits landing in a dedicated business account whenever possible. If you’re still comparing options, Tech Help Canada’s RBC Digital Choice Business™ Account Package review looks at one digital-heavy business banking option for Canadian businesses.
Refunds and disputes need a trail
A refund should not be a mystery entry in your accounting system. Your POS should show the original sale, refunded item, staff member, reason, refund method, and date. That trail makes customer service faster and reduces confusion during chargebacks or month-end review.
Staff accountability should be built in
Shared logins create weak records. If everyone uses the same PIN, you can’t tell who approved a discount, processed a refund, opened the cash drawer, or changed a price. Unique staff accounts protect honest employees and make unusual activity easier to spot.
Security and compliance basics for POS transactions
Payment security is not only an enterprise issue. The PCI Security Standards Council says PCI DSS is intended for entities involved in payment card processing, including merchants, processors, acquirers, issuers, and service providers. Its FAQ for small merchants says PCI DSS is intended for merchants regardless of size or transaction volume, while validation requirements are determined by payment brands.
For most small businesses, the practical goal is to reduce card-data exposure and confirm with your processor or acquirer what validation steps apply to your setup.
Use payment hardware and software from trusted providers. Follow their setup instructions, especially for terminals, gateways, and hosted checkout pages.
Do not store sensitive card data manually. Avoid keeping full card numbers, CVVs, card photos, or card details in notes, spreadsheets, email, chat, or customer profiles.
Use unique staff accounts. Give each person their own login and remove access when someone leaves.
Turn on multi-factor authentication for admin access. This is especially useful for owner, manager, reporting, refund, and remote-access accounts.
Patch POS software and devices. Unsupported tablets, old terminals, outdated apps, and unpatched operating systems create avoidable risk.
Restrict high-risk actions. Limit who can issue refunds, void sales, export data, edit taxes, change prices, or adjust inventory.
Separate guest Wi-Fi from POS devices. Customers should not be on the same network as your payment terminals or back-office systems.
Inspect terminals. Train staff to notice loose parts, damaged seals, unexpected attachments, or swapped devices.
Control remote access. Only allow remote support when needed, know who has access, and require strong authentication.
If ecommerce is part of your POS setup, ask whether the checkout is fully hosted by the provider or embedded on your site. A provider can reduce your card-data exposure, but your website, plugins, redirects, scripts, and admin security may still affect payment security.
Fees, contracts, and merchant rights deserve attention
The processor fee line is not the only cost. Your total cost of accepting payments may include interchange or network fees, processor markup, monthly platform fees, terminal rental or purchase costs, chargeback fees, PCI-related fees, batch fees, next-day deposit fees, hardware replacement costs, and early termination clauses.
For Canadian merchants, the Financial Consumer Agency of Canada says the Code of Conduct for the Payment Card Industry in Canada was introduced in 2010, revised in 2015 and 2024, and agreed to by major payment card network operators in Canada. The Code is designed to make merchants aware of card acceptance costs, encourage pricing flexibility, and allow merchants to choose the payment options they accept.
Before signing a POS or processing agreement, ask for a sample monthly statement and make the provider explain it line by line. If the pricing only looks good in a sales deck, it may not look as good after transaction volume, card mix, refunds, chargebacks, and add-on fees are included.
How to choose the right POS setup
Start with your transaction reality, not a feature list. A café, trades business, online retailer, salon, event vendor, and multi-location retail store all need different transaction workflows.
List every way customers pay you. Include tap, chip and PIN, mobile wallet, cash, invoices, online checkout, recurring payments, gift cards, store credit, deposits, and partial payments.
Map your refund and exchange process. Test whether staff can find the original transaction quickly and whether refunds connect back to the sale.
Check tax and tip settings. Confirm GST/HST, PST, service charges, tips, delivery fees, and taxable or non-taxable items are handled correctly for your business.
Review reporting before buying. Ask to see daily close reports, settlement reports, product sales reports, staff reports, tax reports, and export options.
Test the accounting connection. A sync that creates messy entries is not really saving time. Make sure the data lands in your accounting system in a way your bookkeeper can use.
Ask how offline mode works. Some systems can queue transactions when internet service drops, but that does not always mean the payment is approved. Know the risk before relying on it.
Confirm data portability. If you switch providers later, you should know what sales, customer, inventory, and product data you can export.
Understand hardware ownership. Clarify whether terminals are purchased, leased, rented, locked to one processor, or returnable at the end of the agreement.
Check support hours. If you sell evenings, weekends, or during events, weekday-only support may not be enough.
A simple daily POS workflow for small teams
A good POS workflow reduces end-of-day surprises. It also makes training easier because staff know the right way to handle normal transactions and exceptions.
Before opening
Make sure terminals are charged, connected, and assigned to the correct location or register. Confirm product prices, tax rules, discounts, and staff logins. If you use cash drawers, start with a counted float and record the starting amount.
During checkout
Select the exact product or service whenever possible. Avoid generic buttons unless you have a clear policy for when they’re allowed. Verify the total before the customer pays, and add notes for unusual transactions such as manual discounts, custom orders, deposits, or returns without receipts.
At close
Close the batch if your processor requires it. Count cash, record overages or shortages, and save the daily close report. Compare POS payment totals against your processor dashboard so problems are caught while the day is still fresh.
Weekly or monthly
Reconcile settlement deposits to your bank account, review refunds and voids, check discounts, confirm inventory adjustments, export reports, remove old staff access, and update POS software. The larger your volume, the more often you should review exceptions.
Point-of-sale transaction checklist
Use this checklist before you buy a POS system, switch processors, or audit your current setup.
Every sale, refund, void, exchange, and split payment gets a unique transaction record.
Staff use individual logins, not shared accounts.
Taxes, tips, discounts, and service charges are set up before checkout starts.
Refunds and exchanges link back to the original sale.
Daily POS totals can be matched to processor reports and bank deposits.
Inventory changes are tied to specific SKUs, quantities, and locations.
Reports can be exported in a format your bookkeeper or accountant can use.
Payment devices and software are updated and supported.
High-risk permissions are limited to the right people.
Your processor has confirmed which PCI validation steps apply to your setup.
You understand all contract costs, not just the advertised transaction rate.
You know what happens if internet service, hardware, or the processor goes down.
If your current setup depends on manual fixes, shared logins, generic product buttons, or end-of-month detective work, fix the workflow before volume grows. The more transactions you run, the more each small POS mistake multiplies.
Get new small business insights by email
Practical ideas and useful articles to help you make better business decisions.
Tech Help Canada Staff researches, writes, and reviews practical content for business owners and professionals. Our coverage spans business, marketing, SEO, technology, and the tools and systems people use to grow and operate online. We focus on clear, useful information backed by research, hands-on experience, and editorial review. Learn more about our team and editorial standards. Need help with something? Contact Us
