Payment Vouchers

A payment voucher records money received from a customer — cash in the field, a cheque, a bank transfer, or a gateway payment. This page covers the Payment Vouchers list, its 10-state lifecycle, and the two actions the console lets you drive: Approve and Cancel.

Where vouchers come from

You cannot create a payment voucher from this console — there is no New voucher button. Vouchers are created by the Sales-Executive field app when an SE collects money, by the public API, or automatically by the payment-gateway webhook (Razorpay/CCAvenue) and bank-statement reconciliation described on the Bank Reconciliation page. The HO console's job is to review each voucher and approve or cancel it — not to originate it.

The Payment Vouchers list

Nav: Billing → Payment Vouchers. Permission required to view the list: payment.view. There is no create or edit form — vouchers are originated elsewhere (see above) — but each row can be opened to a read-only detail view (below); every action still happens directly from the row.

ColumnShows
voucher_numberThe voucher's reference number. Shown as a badge, searchable and sortable.
CustomerThe paying customer's name (customer.user.profile.full_name).
AmountThe amount received, formatted in ₹ (amount), sortable.
Payment methodBadge showing how the money arrived — see the full list of methods below.
CompanyBadge showing which AIR group company the voucher belongs to: Air, Ais, Ainfo, or Ala.
StateThe voucher's current lifecycle state — badge, coloured as in the diagram below.
procuring_dateThe date the money was actually collected/received, sortable.

Payment methods (payment_method, shown as a plain badge with no colour map): Cash, Cheque, DD, NEFT, RTGS, IMPS, Razorpay, CCAvenue, COD, Wallet, QR.

Filters

FilterNarrows by
StateAny of the 10 PaymentVoucherState values (see the diagram below).
Payment methodAny of the 11 payment methods listed above.

Viewing a voucher Built

Use the View row action to open a voucher's detail page — read-only, gated by the same payment.view permission as the list. It has five info panels plus three child tables:

Below the panels, three read-only tables: Allocations (how the voucher's amount is split across sale-order lines), Account allocations (any cross-customer or account-level allocation — its Move balance to wallet button, with payment.account_allocate, puts the voucher's unallocated amount on its customer's account; it is credited to the customer's wallet as soon as the voucher is Cleared), and Recoveries (recovery records raised against this voucher after a dishonour). The voucher itself is driven through its lifecycle by the Approve / Cancel actions and the dishonour flow, not edited as a form.

With payment.allocate, the Allocate button on the Allocations table maps the voucher onto the customer's sale orders (voucher in Pending Amount Allocation, Sales Department Approval or Cleared). Each row: pick the Sale order (shown with its total and what is still due; only the voucher customer's open orders — not completed or cancelled — with money still due are listed), then a Sale order line of that order (listed by product name) — the Amount fills in with the line's due, which you can change — and enter any Gateway charges. All rows save together or not at all, and the total cannot exceed the voucher's unallocated amount.

A voucher that arrived without a customer — typically an unidentified bank receipt in Suspense — shows a Set customer button (on its row and on its detail page) to anyone with payment.allocate. It is available only until the voucher is approved, and only while no customer is set. A Suspense voucher then moves to Pending Amount Allocation, ready to allocate here or through Record payment on its bank line (which keeps these allocations and lets you add more, but refuses a different customer while they exist).

Check for a duplicate first

A Suspense voucher is an unidentified bank credit — the Sales Executive may already have recorded the same payment as their own voucher. Allocating both would show the order as paid twice. If the payment was already recorded, use Match existing voucher on the bank line instead: it cancels the Suspense voucher and removes its allocations.

Screenshot placeholderThe Payment Voucher detail page: "Voucher", "Amounts", "Collection & approval", "Dishonour" and "Linked records" info panels, with "Allocations", "Account allocations" and "Recoveries" tables below.

The voucher lifecycle

Vouchers follow the client's flow. The number is the step; the state name is what the console shows.

StepStateHow the voucher gets here
1SuspenseRaised automatically for an unidentified bank-statement credit (no customer yet).
2Pending Amount AllocationThe customer is added — Set customer on the voucher, or Record payment on its bank line. A field-app voucher arrives here when the SE submits it (from Draft).
3Sales Department ApprovalAn amount is allocated to the customer's sale orders (or put on their account).
4Account ApprovalSales Department approves (Sales approve, payment.approve).
5aApproved for DepositAccounts approve (Account approve, payment.account_approve). A voucher from a bank-statement line skips steps 5–6 and goes straight to Cleared — the money is already in the bank — and its bank line is marked matched.
5bHold – Not DepositedPut on hold from steps 3–5a; released back to any of them.
6Deposited in BankThe cheque/DD is banked (deposit date + AIR bank account).
7aClearedThe bank confirms it (or, for cash, straight from Approved for Deposit). Any amount on the customer's account now reaches their wallet.
7b1Returned to CustomerThe cheque/cash is handed back undeposited, from Approved for Deposit or Hold. Final; the voucher's allocations are released so the orders show as unpaid again.
7b2Bounced / DishonouredThe deposited instrument bounces (reason + date).

Draft (a field-app voucher not yet submitted) and Cancelled sit outside the numbered flow. Internally the states keep their original stored names (e.g. submitted, allocated, sales_approved), so the field app and API are unaffected.

Screenshot placeholderThe Payment Vouchers list — columns for voucher number, customer, amount, payment method, company, state and procuring date; the State and Payment method filters open above the table.

Sales approve and Account approve Built

Approval is two steps, each a row button with optional remarks and a confirmation:

Cancel Built

Cancels a voucher outright. Visible only on vouchers in state Draft, Submitted or Dishonoured.

Permissions

Requires payment.cancel (or super-admin).

  1. Find a cancellable voucher

    Filter by State = Draft, Submitted or Dishonoured.

  2. Select Cancel

    Icon: x-circle, colour danger.

  3. Add remarks (optional)

    Same remarks textarea as Approve — optional, up to 500 characters.

  4. Confirm

    A confirmation dialog asks you to confirm before proceeding.

  5. Result

    The voucher moves to Cancelled and any existing allocations and account-allocations against it are deleted.

Cancelling deletes allocations

Cancelling a voucher removes any record of it being allocated against a customer's outstanding orders. Only cancel a voucher you are sure is invalid — for example, a duplicate entry or a payment that will never actually clear.

Screenshot placeholderThe Cancel confirmation dialog on a Draft/Submitted/Dishonoured voucher — confirmation message plus the optional Remarks textarea.
A third source state exists for Cancel — but no button offers it

Behind the scenes, the service that powers Cancel also allows cancelling from Suspense. This path is used internally by bank reconciliation's auto-match (it cancels a duplicate suspense voucher once a real match is found) — it is not something you trigger from a button here. See Bank Reconciliation.

What is a Suspense voucher?

A Suspense voucher records money that has definitely arrived — for example, a bank credit or a gateway settlement — but that has not yet been matched to a specific customer. It sits apart from the main Draft→Cleared chain: it isn't created by moving a Draft voucher forward, and it doesn't automatically progress on its own. Bank reconciliation's auto-match works through unmatched bank-statement lines and, where it finds a genuine match, clears the correct voucher and cancels any duplicate suspense voucher left over. See Bank Reconciliation for the full matching flow.

Request refund New 2026-11-11

To give money back to the customer, open the voucher that paid it and use Request refund (needs refund.create and refund.submit; shown while the voucher can still be reallocated and has order-line allocations). Choose how much goes back on each line it paid, the method (Cheque, NEFT or Adjustment — kept as wallet credit) and a reason. Approving and issuing happen on the refund's page; when issued, the amount comes off those lines (the orders show it due again) and, for Cheque/NEFT, out of the voucher for good. See what issuing does to the money.

Change state

The Change state button (on each row and on the voucher's page) moves a voucher to one of its allowed next states. The dropdown lists only the moves possible from the current state that you have permission for; each runs the real step, so its checks and side effects still apply.

FromCan move toAsks forPermission
DraftPending Amount Allocation (submit — only the person who collected it, or an approver), Cancelled—, remarkspayment.submit, payment.cancel
SuspensePending Amount Allocation (asks for the customer — same as Set customer), Cancelledcustomer; remarkspayment.allocate, payment.cancel
Pending Amount Allocation, BouncedCancelledremarkspayment.cancel
Sales Department ApprovalAccount Approval (once the whole amount is mapped), Holdremarkspayment.approve, payment.hold
Account ApprovalApproved for Deposit (or Cleared for a bank-line voucher) — once the whole amount is mapped, Holdremarkspayment.account_approve, payment.hold
Approved for DepositDeposited in Bank (cheque/DD/bank methods), Cleared (cash), Hold, Returned to Customerdeposit date + AIR bank account; cleared date; remarkspayment.deposit, payment.clear, payment.hold, payment.cancel
Hold – Not DepositedBack to the step it was held at (release), Returned to Customerremarkspayment.hold, payment.cancel
Deposited in BankCleared, Bounced / Dishonouredcleared date; dishonoured date + reasonpayment.clear, payment.dishonour

Two moves happen elsewhere: Suspense → Pending Amount Allocation by setting the customer, and Pending Amount Allocation → Sales Department Approval by allocating. Cleared, Returned to Customer and Cancelled are final.

Dishonour can post a reversal to the ledger

When a deposited voucher is dishonoured, the payment that was expected to clear is reversed: the customer's balance is re-opened (they owe again) and the bank/cash that never cleared is credited back. If bounced-payment accounting is switched on in System Configuration — an opt-in flag plus a debit and a credit account under the accounting group (the bounced.* keys) — then dishonouring a voucher also creates and posts a balanced double-entry to the ledger in the same step, linked back to the voucher. If the flag is off or either account is blank, nothing is posted; the dishonour itself still goes through. The entry, once posted, appears on the Accounting — Journal & GST page. (This is separate from any cheque-bounce Charge raised against the customer.)

Permissions

payment.submit, payment.approve (Sales), payment.account_approve (Accounts), payment.deposit, payment.clear, payment.dishonour, payment.hold and payment.cancel (also used for Returned to Customer) gate the moves above, in the console and the API alike.

See also