House Account POS Guide 2026: Track Unpaid Balances

When regular customers want to buy now and pay later, a generic “other payment” button is not enough. Your business needs to know who owes the money, which purchases created the balance, when payment is due, and whether the next sale should be allowed. Without those connections, convenient checkout can become an unreliable accounts-receivable process.

The buying priority: choose a POS house account workflow that connects named customers, invoices, credit limits, payments, and adjustments. Evaluate it as a controlled receivables system, not simply another tender type. This guide focuses on retail and trade-counter buying decisions; restaurant tabs and hospitality room charges can involve different products and controls.

POSadvice.com helps you compare POS systems. We are a national research and comparison site, not a lender, POS vendor, or installer. The product example below comes from official documentation reviewed on October 2, 2026. Evaluation recommendations are not a claim of hands-on testing or a guarantee that a particular plan contains every feature.

What is a POS house account?

A house account lets an approved customer charge purchases to an account held by the merchant and settle the balance later under agreed terms. Retail software may call this an on-account sale, customer credit account, or invoice account. The important question is not the label: it is whether the sale produces an identifiable obligation that later payments can reduce.

Do not confuse this arrangement with store credit issued after a return. In a house account, the customer owes your business. With a prepaid balance or return credit, your business generally owes the customer goods or value. A software screen may display both, but their meaning and accounting treatment are different. Ask the provider to demonstrate each separately.

A saved card is also not the same as a credit account. It is a payment mechanism, not proof of permission to charge any future amount or an explanation of unpaid invoices. Establish appropriate customer authorization and use the processor’s supported storage workflow rather than putting sensitive payment data into customer notes.

Compare the main approaches

These are workflow choices, not claims that every POS offers them. A store serving a few established commercial accounts may value checkout visibility more than elaborate billing automation. A larger operation may need a specialist receivables system, but the counter still needs a dependable answer about whether an account can buy.

What one vendor’s documentation actually confirms

Lightspeed Retail R-Series documents credit-account sales and invoice payments. Its available-credit calculation subtracts outstanding invoice balances from the credit limit and excludes deposits. That provides a concrete reason to ask how a quoted system treats prepaid funds versus credit already used.

The same page says sending invoices to collect outstanding balances is available to merchants using Lightspeed Payments, and it warns that some invoicing features are in beta and may not be available in every account. These limitations belong in a buying conversation. Do not assume that a feature shown in an article is active in your proposed account or included with a different payment arrangement.

Its credit-account management documentation describes permissions for credit limits and refunds, account statements, outstanding balances, and overdue filters. It also states that all employee roles can adjust payment terms when saving or sending invoices. If restricted term changes matter to your business, require a demonstration of the available controls rather than assuming every financial field has a separate permission.

This is a documented retail example, not a recommendation for every business. Lightspeed has multiple product families, and its R-Series guidance specifically distinguishes these credit accounts from Lightspeed Golf house accounts. Your proposal should name the edition, region, payment arrangement, and feature availability.

Six controls to insist on before choosing a system

1. Correct customer and purchaser identification

A trade customer may have one billing account and several authorized buyers. Ask whether the system can capture the purchaser, purchase-order reference, and invoice recipient without creating separate balances accidentally. Have the provider retrieve an account with a similar name and demonstrate how staff avoid selecting the wrong one.

2. Meaningful credit-limit behavior

Test a purchase that would exceed the remaining credit. Does the register block it, allow partial payment, show a warning, or permit an override? Those are different controls. Define what you need and test a second register as well, especially if simultaneous purchases or delayed synchronization could affect the available amount.

3. Invoice-level payment allocation

A customer may pay the oldest invoice, a disputed invoice’s undisputed portion, or several invoices together. Ask staff to show exactly which amounts the payment settles. A reduced total balance is helpful, but it does not explain whether the customer and your bookkeeper agree on which invoices remain unpaid.

4. Due dates and actionable aging

Require a practical way to identify amounts due now and overdue under the customer’s agreed terms. If a dashboard only reports total outstanding dollars, billing staff may still need a separate spreadsheet. Test the report with invoices issued on different dates and a partial payment against just one of them.

5. Traceable adjustments and refunds

Returns, credits, write-offs, and payment corrections should remain distinguishable. Ask who can authorize each action and what history is retained. A manual balance edit that erases the explanation may be quick today but expensive to investigate when a customer challenges a statement next month.

6. Clear settlement status

Payment received, payment pending, and payment settled are not interchangeable. Ask how a pending bank payment affects the displayed balance and available credit, and what happens if it fails. Lightspeed’s cited documentation describes in-transit direct-debit payments, which illustrates why this is a separate test rather than a detail to leave until launch.

Run a $500 credit-limit demonstration

Use a test customer with a hypothetical $500 limit. Record an initial $180 purchase and a second $220 purchase. With no other adjustments, the outstanding balance is $400 and the remaining credit is $100. Attempt another $150 charge and inspect the exact block, warning, split-payment, or approval behavior.

Now apply a $100 payment specifically to the first invoice. The outstanding total should become $300, while that invoice has $80 left. The second invoice should still show $220. Ask for a customer statement and an invoice-level export. If either cannot explain those numbers, the demo has not proved the allocation workflow.

Next, enter a $40 return against the second purchase using the provider’s supported process. The expected account total becomes $260 if the return is applied as a credit to that unpaid invoice. Confirm the remaining invoice amounts and trace the inventory return separately. Do not assume a refund sent to a card has the same account effect as a credit applied against debt.

Finally, test a pending payment that later fails, using the vendor’s demonstration tools rather than a live customer account. Ask how the failed payment restores the receivable and affects available credit. Record any manual actions required. This exception often reveals more than a polished example in which every payment succeeds immediately.

Pros and cons of offering house accounts

Pros

• Approved repeat buyers can purchase without arranging payment for every individual visit.
• Account-linked transactions can give billing staff a clearer purchase history.
• Statements can consolidate the discussion about outstanding invoices.
• Credit controls can make the merchant’s policy more consistent at checkout.

Cons

• Your business carries the risk that a customer pays late or does not pay.
• Credit approvals, disputes, and collection work require staff time.
• Unclear permissions can let ordinary checkout actions change financial terms.
• Separate POS and accounting systems can disagree unless the integration is carefully designed.

A house account should solve a real purchasing problem, not become an informal favor that nobody monitors. Set written terms and decide who reviews new accounts, changes limits, and handles overdue balances. The software should enforce or clearly expose those decisions, but it cannot make the underlying credit decision for you.

Compare costs and cash-flow exposure

Request the full software price, invoicing or receivables add-ons, accounting connector fees, training, and any fees for collecting payments. Ask whether invoice links depend on a particular processor and whether card and bank payment methods have different charges or settlement behavior. Do not compare only the base register subscription.

For a hypothetical planning example, forty active customers averaging $300 outstanding represent $12,000 in receivables. That is money awaiting collection, not a subscription expense. Separately, if staff spend three hours weekly reviewing accounts at an assumed labor value of $25 per hour, the workload is $75 per week. Use your own measured figures before deciding whether automation is worth its added cost.

Have your bookkeeper inspect exports for the sale, later payment, return credit, and write-off. A payment against an existing invoice should not inadvertently become a second sale in the connected books. Our POS accounting synchronization guide explains how to compare connection methods and reconciliation records.

Plan permissions and the switch from your old system

Define separate responsibilities for creating customer accounts, approving credit, collecting payments, issuing credits, and reviewing overdue balances. Smaller businesses may assign several responsibilities to one person, but the boundaries should still be clear. Use our POS staff permissions guide to structure the roles and test their limits.

Before migration, choose a cutoff date and export the old system’s open invoices, remaining amounts, customer identifiers, and relevant terms. Ask whether the new system imports invoice detail or only opening balances. If it only imports balances, preserve the historical invoice records in a retrievable location and explain how later payments will be allocated.

Reconcile a small sample with customers before expanding the rollout. Ensure the same opening debt is not imported twice through both the POS and accounting connector. Keep responsibility for each system explicit: one tool should own the authoritative receivable, even if several screens display it.

What to send when requesting quotes

Include the number of credit customers, monthly on-account sales, usual terms, locations, accounting software, and required collection methods. Ask providers to perform the credit-limit demonstration, explain restrictions, and identify every dependency in writing. Request sample statements and exports using fictional data.

Choose the system whose balance a cashier, customer, and bookkeeper can all explain. If the demonstration requires hidden manual corrections, include that work in the comparison. A simple, auditable workflow is more useful than a long feature list that leaves staff uncertain about what a customer actually owes.

Frequently asked questions

Is a POS house account the same as store credit?

No. A house account generally records money the customer owes the merchant. Prepaid funds or return credit generally represent value the merchant owes the customer. Test how the POS separates those balances.

Does a credit limit always block an over-limit purchase?

No. Systems can block, warn, allow split payments, or provide overrides. Demonstrate an over-limit purchase in the exact configuration you plan to buy and confirm which employee roles can proceed.

Can one payment settle several house-account invoices?

Some systems support allocation across invoices, but the process and payment channels differ. Ask the provider to demonstrate invoice-level allocation and show the remaining balances on a statement and export.

What should I check when moving existing house accounts?

Reconcile open invoices at a cutoff date, determine whether invoice detail or only opening balances can be imported, preserve historical records, and prevent the same receivable from being imported twice.