Counter sales — card-present payment that posts to the ERP in real time

Introduction

Counter sales payments on Clarity Payment Hub bring card-present credit card acceptance to the parts counter, the will-call window, the clinic front desk, the permit window, and the school bookstore, with customer account lookup from the ERP, charge-on-account support, and real-time posting. The counter sale behaves like a point of sale for the buyer standing in front of you, but it posts to the same ERP ledger as every other transaction. Staff take in-store payments by credit card chip, contactless tap, or saved method, apply them to the buyer's open invoices, and print or email a receipt, and the cash receipt lands in your ERP before the buyer leaves.

What counter sales look like in a Payment Hub shop

Counter sales are the part of your operation where the buyer shows up in person. For a distributor, it is the parts counter, the trade desk, and the will-call window. For a clinic, it is the front desk. For a school, it is the bookstore, cafeteria, or registration office. For a municipality, it is the permit window or utility office. Counter sales see a different kind of transaction than online portal AR, and most retail POS software does not handle it well, because it treats every transaction as an anonymous shopper rather than a buyer whose history and terms already live in your ERP.

Clarity Payment Hub gives counter sales what the rest of the organization already has: a view of the buyer's ERP account, the ability to apply payment to open invoices, the option to charge to account on Net terms, and the card-present credit card acceptance, on any major credit card, that earns the lower interchange tier. The counter experience feels like a point of sale but behaves like your ERP. Most counter sales payments are credit card transactions, and Payment Hub keeps every credit card on the lower card-present interchange tier.

How Payment Hub powers the counter

Eight capabilities run counter sales on Payment Hub, turning the counter into a point of sale that posts to the ERP. Each one is Payment Hub doing work that would otherwise fall on a separate POS system, a staff-kept spreadsheet, or a next-morning reconciliation meeting.

Customer lookup at the counter

Staff search by name, phone, account number, PO, or email, and the buyer's ERP-sourced record loads instantly: open invoices, credits, saved methods, credit limit, terms, and recent history. The counter sees what AR sees.

Certified card-present terminals

Credit card EMV chip, contactless tap, and magstripe fallback run on Verifone, Ingenico, PAX, and Castles hardware through whichever gateway you use. Payment Hub drives the terminal, so staff do not manage two systems.

Tap to Pay on iPhone and Android

Where your gateway supports it (Stripe, Adyen, Square-family, and others), the counter staff's phone becomes the terminal, with no extra hardware and no dongle. This suits second-counter lines, outdoor service desks, and small branch counters.

Virtual Terminal for keyed entry

Phone-in orders, email orders, and card-not-present counter moments all key through the same Virtual Terminal interface, with the same customer lookup, the same saved methods, and the same ERP posting as card-present transactions.

Tokenized saved methods for repeat customers

B2B repeat customers' saved credit cards and ACH tokens live at the gateway vault. Staff can charge a stored method by confirmation rather than re-keying, and raw PAN never touches Payment Hub or your server.

Charge-on-account for Net-terms customers

For B2B walk-ins on Net 15, 30, or 45, staff can post the counter sale order to the account as a new invoice rather than collecting payment now. The invoice posts to the ERP immediately, and the buyer walks out with a receipt showing the charge-to-account and the updated balance.

Receipt print, email, and SMS

Counter receipt printers print a physical receipt, or the receipt printers are skipped and the counter emails one to the buyer's address on file, or texts one, in any combination. The same receipt printers serve every counter. Receipts include the sale detail, any applied payments, account balance updates, and the transaction reference that AR can trace to the ERP.

Real-time ERP posting

Sales, cash receipts, charge-on-account invoices, and credit applications all write to your ERP through Clarity Connect the moment the terminal authorizes. There is no end-of-day batch and no morning reconciliation meeting. The cash drawer and the sales order both update in the ERP as the sale posts, so sales tracking is current and the point of sale never drifts from the ledger. Per-counter sales tracking rolls up across sales counters in every branch.

The counter-sales workflow: customer walks up to receipt printed

Here is what happens when a B2B buyer shows up at the parts counter for a $240 purchase, also wants to pay $500 on an outstanding invoice, and wants to charge an $1,800 back-counter service order to their account. The whole thing fits in one counter visit with one receipt.

Buyer identifies themselves. The buyer gives their account number, company name, or phone to the counter. Staff type or scan it into Payment Hub and the buyer's ERP record loads: open invoices ($1,240 total outstanding), saved payment methods (Visa ending 4421, ACH on file), credit limit, Net 30 terms, and recent purchase history.

Staff ring up the $240 parts sale. The counter enters the line items for the walk-in sales order: part number, quantity, price. Payment Hub validates the buyer's ERP credit limit, which is clear. The sale subtotal appears with tax rolled up from the buyer's ship-to jurisdiction.

Buyer also wants to pay $500 against an open invoice. The counter brings up the $1,240 outstanding balance. The buyer picks invoice #4208, an $800 invoice, and pays $500 against it. Payment Hub adds this as a second line in the counter transaction, and invoice #4208 will close to a $300 remaining balance after posting.

Back-counter service order charged to account. The service tech brings out an $1,800 charge for a back-shop repair. The buyer wants to charge it to the account on Net 30 rather than pay at the counter. The counter adds it to the transaction as a charge-on-account line, and the new invoice will post to the ERP against the buyer's account on the Net 30 terms they are on.

Counter totals and method selection. Payment Hub summarizes: a $240 counter sale plus a $500 invoice payment is $740 due now, with the $1,800 charge-on-account to be invoiced separately. Staff select the tokenized Visa credit card on file for the $740 portion, or the buyer taps their credit card on the terminal. The buyer can override to ACH if preferred.

Card-present authorization runs. The terminal authorizes the $740 credit card transaction by EMV chip or contactless tap, qualifying for card-present credit card interchange rates that are lower than keyed. The gateway returns approval, and Payment Hub records the transaction reference.

The ERP posts three records: sale, receipt, account charge. Payment Hub writes three records to the ERP through Clarity Connect, all linked to the sales order: a $240 counter-sale order invoice paid immediately, a $500 cash receipt applied against invoice #4208 (closing it to $300), and a new $1,800 invoice charged to the buyer's account on Net 30, each with the correct GL, customer account, and invoice reference.

Receipt prints and emails, and the buyer walks out. The counter prints a receipt showing all three transaction lines, the sale, the invoice payment, and the charge-on-account, plus the updated account balance and the new open-invoice total. The same receipt emails to the buyer's contact on file. The transaction is complete, and the buyer is out the door in under two minutes.

The counter-sales scenarios Payment Hub handles without switching systems

Real counter traffic is not all the same buyer or the same transaction type. These counter sales patterns each run as a counter sale order that with the same ERP posting, the same receipt flow, and the same tokenized security model.

B2B walk-in, charge-to-account

An existing Net-30 trade-account customer does not want to pay at the counter. Staff look up the account, ring up the sale, and post it as a new invoice to the buyer's account. The invoice joins their next regular AR cycle, with no card authorization and no chase cycle, because they are on Net 30.

B2B walk-in, counter-pay with saved credit card

An existing customer who prefers to pay at the counter has a credit card on file from prior visits. Staff ring up the sale, select the tokenized saved method, and the terminal confirms, or the buyer re-authenticates with signature or PIN. There is no re-keying, no PAN exposure, and the transaction earns card-present interchange.

Non-account consumer walk-in

For a one-time cash or card customer with no account, staff ring up a cash sale under the generic counter-cash customer, a quick order entry with no lookup. The customer taps their credit card on the terminal, Payment Hub takes the payment, optionally prompts for an email or phone for the receipt, records the cash sale, and posts a one-time sale invoice to the ERP. No customer record is created unless the cashier opts to add one.

Phone order, staff keyed entry

A customer calls the counter and gives their account number and order detail. Staff key the sale in the Virtual Terminal, with the same customer lookup, the same invoice and charge-on-account options, and the same saved-method support. Card-not-present keyed interchange rates apply, higher than card-present but still posting correctly to the ERP.

Will-call pickup, paid online first

A customer who paid online shows the pickup reference. The counter scans or keys it, Payment Hub confirms the invoice was already paid in the ERP, and prints a pickup receipt. There is no second payment collection and no second ERP entry, because the pickup workflow replaces pay-then-pickup.

Cash and check at the counter

When a customer pays in cash or by check, staff record it in Payment Hub rather than processing it through a gateway. The amount applies to the sale, invoices, or charge-on-account as if it were a tokenized method, and the ERP posts a cash-receipt record with the method marked Cash or Check. Drawer-balance tracking stays consistent with the ERP's cash GL.

Industries where the counter actually matters

Not every Clarity vertical has counter sales. Where counter sales happen, the point of sale is the ERP. Distribution does, at the parts counter and will-call. Healthcare does, at the front desk and cashier. Education does, at the bookstore, cafeteria, and registration. Government does, at the permit window and utility office. Subscription and professional services usually do not. Payment Hub applies the counter pattern where it fits the vertical.

B2B Distribution and Wholesale

The parts counter, will-call window, trade desk, and branch counter are where counter sales matter most. Trade customers walk up to the trade desk, accounts look up in the ERP, charge-to-account or counter-pay, Net terms are honored, and card-present interchange applies on the card portion, across multiple branches with centralized ERP posting and phone orders through the Virtual Terminal.

Manufacturing

Aftermarket parts-counter and service-desk counter sales cover dealer commercial cards at the counter, service contracts invoiced to account, and warranty-adjusted lines. The volume is lower than distribution, but the workflow is the same.

Healthcare and Life Sciences

Front-desk counter sales, check-in and check-out, co-pay collection, and balance-of-care payment after services rendered all run here, with patient account lookup from the practice-management system, HSA and FSA card acceptance, and saved-method support for recurring patients.

Nonprofit and Fundraising

Counter sales like event tickets, silent-auction payment, cash sales of merchandise and gift-shop items, and fundraiser drive-up counters all fit. Tap to Pay on iPhone lets volunteer staff run counters without dedicated hardware, which is useful for one-off events.

Education

Bookstore and cafeteria counter sales, registration counters and sales counters, continuing-ed signups, activity fees, and parking permits all run at the counter. Parent or student account lookup ties the sale to the existing SIS or ERP record, and volume is often event-spike driven, such as the start of a semester or registration week.

Government and Public Sector

Permit-counter sales, utility offices, citation windows, business-license counters, and tax-and-fee windows all apply, with citizen account lookup from the financials ERP, fee pass-through where applicable, and CEDP Level 3 on commercial cards at the counter.

Professional Services and Agencies

Most professional-services firms do not have a counter in the literal sense. Where the counter applies, such as a CPA firm collecting a walk-in client's deposit or a real-estate office taking a deed-transfer fee, Tap to Pay on iPhone plus the Virtual Terminal covers the pattern without dedicated hardware.

Subscription, SaaS, and Membership

Subscription businesses typically run fully digital, so counter sales are rare. Where they happen, such as a gym or fitness-studio front desk collecting a walk-in class fee or a co-working space selling a day pass at the sales counter, Tap to Pay on iPhone plus the Virtual Terminal covers the counter pattern.

ERP integration: the counter writes to the same ledger as everything else

Running counter sales through Payment Hub matters because is that the counter transaction lands in your ERP alongside every other transaction, rather than in a separate POS-system silo that someone has to reconcile. Clarity Connect, Payment Hub's integration engine with more than 25 ERP connectors, writes counter activity to your ERP in real time.

Inbound from the ERP

The customer record, open invoices, credits, saved-method tokens, credit limit, terms, tax jurisdiction, ship-to, and pricing all pull in real time as the counter looks up the buyer.

Outbound to the ERP

Counter-sale invoices, cash receipts, charge-on-account invoices, credit applications, tokenized-method references, cash and check records, and gift-card redemptions all write the moment the terminal authorizes.

More than 25 ERP connectors

NetSuite, Acumatica, Microsoft Dynamics 365 Business Central (BC) and F&O, Microsoft Dynamics GP and NAV, SAP S/4HANA Cloud and ECC, Sage 100, 300, and Intacct, Oracle EBS, Epicor P21, Kinetic, Eclipse, and Eagle, Infor SX.e and CloudSuite, SYSPRO, Workday, Tyler, and more. Clarity Connect uses only documented, supported integration points, with no schema changes, no ERP-side custom code, and no plugins to maintain. Payment Hub is certified for Microsoft Dynamics 365 Business Central. For shops running counter sales in Business Central, Payment Hub embeds card-present acceptance in the Business Central sales order and counter sale flow, so the cash drawer, the sales order, and the receipt all post inside Microsoft Dynamics. Whether you run Microsoft Dynamics 365 Business Central, Microsoft Dynamics GP, or another ERP, the counter sales post the same way, and sales tracking stays in Microsoft Dynamics rather than a separate point of sale.

For multi-branch operations, Payment Hub supports per-branch cash drawer reconciliation, per-branch tax-jurisdiction handling, and per-branch routing in the ERP, so a branch in one state and a branch in another can both run the counter workflow while their sales post to the correct entity, warehouse, and tax record automatically.

Security, PCI scope, and counter-staff controls

Counter sales touch card-present hardware, staff-keyed entry, and tokenized saved methods. Payment Hub pushes your deployment to the lightest compliance scope available while giving you the staff role controls the counter needs.

Certified terminals from Verifone, Ingenico, PAX, and Castles encrypt card data at the device with point-to-point encryption where supported, so the PAN never appears in clear text between the terminal and the gateway. Saved payment methods used at the counter are tokenized at the gateway's PCI-scoped vault, and raw PAN and raw bank credentials never touch Payment Hub's infrastructure, your counter computer, or your servers. Card-present transactions through certified P2PE terminals typically qualify for SAQ B-IP, lighter than keyed-entry scope, while Virtual Terminal transactions qualify for SAQ C-VT, and mixed deployments combine both appropriately.

Counter staff order entry runs under configurable roles: a junior cashier can process counter sales up to a dollar threshold, a branch manager can process larger sales or override credit limits, and a controller can void or refund. The audit trail records which staff member authorized each transaction. Cash and check recorded at the counter tie into the ERP's cash drawer and cash-GL reconciliation with per-drawer, per-shift totals, so end of day reconciliation matches the cash drawer, so the branch's end-of-day balance checks against the ERP. Where a counter customer opts into saved ACH for future use, authorization is captured at the counter by electronic signature or a verbal-and-audit-logged record with the two-year retention NACHA requires. Clarity Ventures operates to SOC 2 Type II standards, with security, availability, confidentiality, and data-handling controls independently audited on an ongoing basis. For on-premise ERPs, the outbound-only agent means no inbound firewall ports, no VPN tunnel, and no public ERP exposure.

Frequently Asked Questions