Sales
Take Payment, Split Tender, Partial Payment and Wallet
Tender is where the cart becomes money evidence. The cashier must match pay amount, payment labels, due amount and receipt preview before saving.
- Menu path
- Home -> New Sale -> PAY
- Verified from
- Posnic demo and current POS source reviewed on 2026-09-08
Technical source evidence
frontend/modules/sales_write.html tender denomination, sale summary, payment, Paid toggle and Save controls, frontend/static/script/js/modules/js/sales.js openTenderModel, showMultiPaymentMode, Partial_amount, wallet_balance and unpaid_payment_toggle handlers, frontend/static/script/js/modules/js/sales.js cartOrderSubmit payment_mode, multi_payment, enable_multi_payment and denomination_values payload, frontend/modules/settings_write.html Payments -> Split Payment, Payment Modes and Cash Denominations
Open Tender
- Review the sale cart first.
- Click PAY.
- Confirm the sale summary or receipt preview matches the cart.
- Check customer identity if the sale will be partial or unpaid.
- Confirm the amount shown at the top of PAYMENT.
- Choose the correct payment method label.
- Enter or confirm Pay amount.
- Enter cash received in Tender when the cashier needs return-balance and denomination help.
- Use the denomination buttons/counts when the shop wants the cash breakdown saved.
- Save only when amount, method and Paid/Unpaid state are correct.
Read the Tender Drawer
| Area | What it controls | Operator check |
|---|---|---|
| DENOMINATION | Note/coin buttons and counts for the cash received. | Use it when the shop reconciles physical cash by denomination. |
| Tender field | Cash given by the customer and return balance calculation. | Do not confuse tendered cash with Pay amount on card/wallet sales. |
| SALE SUMMARY | Receipt preview generated from cart rows and print type. | Fix mistakes before Save. |
| PAYMENT total | The sale amount to settle. | Must match the cart Pay Total. |
| Paid switch | Turns payment controls on for paid/partial sales; off means unpaid/due. | Only account customers should normally leave with unpaid or partial balances. |
| Pay amount | Amount collected now for paid/partial account sale. | Less than total creates a due balance. |
| Payment method buttons | Cash, gateway and configured method labels. | Pick the label that matches the real collection source. |
| Add | Opens the payment-method creation path. | Managers should create labels before checkout rush begins. |
Paid, Partial and Unpaid
| Tender state | Use when | What to review |
|---|---|---|
| Paid | The customer paid the full sale amount now. | Payment method label, Pay amount and receipt preview. |
| Partial | The customer pays part now and owes the rest. | Customer account, due amount and collection plan. |
| Unpaid | The Paid switch is off and the sale remains due. | Credit limit, customer identity, terms and pending payment report. |
| Refund/return tender | The operator is processing a return. | Original sale, return amount and refund method. |
Split Payment
Split Payment lets one sale be paid through more than one method, such as Cash plus UPI or Card plus Wallet. It makes checkout flexible, but it also makes close-time review stricter.
- Enable Split Payment in Settings -> Core Settings -> Payments.
- Create clear payment method labels before training cashiers.
- Each split amount should match a real drawer count, card slip, UPI settlement or wallet record.
- The split amounts must add back to the sale total.
- When split payment is enabled, the sale payload stores the method map in multi_payment and the combined method label in payment_mode.
- Review Payment Reports and Day-End Summary after split-payment training.
Wallet and Due Amount
When a customer account has wallet balance or partial balance behavior, the tender drawer can show wallet use and due amount. This should never be used on the wrong customer account.
- Confirm customer identity before applying wallet balance.
- Do not edit wallet payment casually after it is applied.
- If the customer pays less than the total, confirm the due amount shown on screen.
- When wallet is checked, the tender logic adjusts payment and partial-balance state against the selected customer's balance.
- Review pending payments after any account sale.
- Use customer credit settings to control who can owe money.
Cash Denominations
When cash-register behavior is used, the tender path can show denomination buttons from shop settings or currency defaults. Denominations help the cashier count physical cash without losing the payment context.
- Use shop-defined denominations when the default currency set is not right for the counter.
- Count cash before saving when the customer gives mixed notes and coins.
- The save payload can include denomination_values for the sale.
- Compare cash-denomination totals with the register close, not only the sale receipt.