On-account sales

On-account sales let you charge part or all of a sale to a customer's account instead of collecting payment now. Bitta Retail POS models this entirely with standard Business Central mechanics: the posted invoice's customer ledger entry stays open in Accounts Receivable, and the customer later pays through your normal AR process (cash receipt journal, payment reconciliation). This page covers the cashier flow and the credit policy behind it.

Charging a sale on account

1. Attach a customer to the sale: tap the register's customer chip and search, or use the quick-create entry in the customer lookup (name, phone, or email creates a POS customer on the spot).
2. Open the tender screen and tap On Account. With an empty amount, Add takes the whole remainder in one tap; enter a partial amount to split with cash or card.
3. Complete the sale. The register confirms with a banner: " charged on account to ."

The On Account button is dimmed with the hint "Attach a mapped customer to charge to account." until the sale carries a customer who maps to a real, non-blocked Business Central customer.

On Account mixes safely with every other tender, including an integrated card payment for the remainder - the credit check runs and the on-account line is recorded before any card processor is called. See Tender screen and split payments and Card payments at the register.

The credit policy check

At completion, Bitta Retail POS compares the customer's standard Business Central Credit Limit (LCY) against their current balance plus this charge. What happens on an over-limit charge is controlled by On Account Credit Policy in POS Setup:

Policy	Behavior
Block (default)	The tender is refused with the balance and limit figures. The sale stays open and its payments stay editable - nothing is half-recorded.
Warn	The sale completes, and the confirmation carries an over-limit warning alongside the charged-on-account banner.
Allow	The sale completes silently.

Two standard Business Central conventions apply:

• A Credit Limit of 0 means no limit configured - the charge is always allowed.
• There is no separate POS "credit hold" flag. To stop on-account sales to a customer, block the customer in Business Central; the register's availability gate respects the Blocked state.

The check runs at completion on both surfaces - the register tender screen and the back-office Tender and Complete dialog.

How on-account lands in Business Central

The seeded ONACCT tender method carries the ONACCOUNT Business Central payment method, whose balancing account is deliberately blank. That blank is the whole design:

• When the day posts, the on-account slice of the invoice does not settle into any cash, clearing, or bank account. The invoice's customer ledger entry remains open in Accounts Receivable.
• The customer's balance rises by the charged amount, and the open entry is later applied by a normal AR payment.
• Under Per-tender settlement, the same intent is expressed by leaving the ONACCT method's settlement account blank: every other tender slice settles into its configured account, while the on-account slice intentionally stays open.

See End of day for the day-close flow and Consolidated posting for how sales become posted invoices.

Setup summary (back office)

Setting	Where	What it does
On Account Credit Policy	POS Setup	Block, Warn, or Allow on over-limit charges (default Block).
Credit Limit (LCY)	BC Customer card	Standard field the check reads; 0 means no limit.
Requires Customer	ONACCT tender method	Gates the button until the sale has a postable mapped customer. Seeded on.
Settlement Account No.	ONACCT tender method	Leave blank so the on-account slice stays open in AR.

Related pages

• Tender screen and split payments - the tender model and split payments.
• Per-tender settlement - why a blank settlement account keeps the slice in AR.
• End of day - posting the day's sales.