Discounts, Refunds & Charges

Three related approval workflows for money that moves outside the normal order/payment cycle: a discount granted after HO already approved an order, money owed back to a customer, and money AIR levies on a customer. Each is a separate link in the Billing navigation group, but they share the same approve/reject/cancel shape, so this guide covers them together.

Where these fit

All three relate back to a customer's running account. A PAD reduces what a customer still owes on an order; a refund pays money back out; a charge adds to what they owe. See Payment Vouchers for how money comes in, and Sale Orders for the order an outstanding balance is measured against.

Post-Approval Discounts (PAD) Partial

A Post-Approval Discount is a discount granted on a sale order after Head Office has already approved it — for example a goodwill reduction agreed with a customer once the order is in flight. In the console it appears under Post Approval Discounts in the Billing navigation group. Viewing the list needs pad.view. Each row can also be opened to a read-only detail view (below).

Raising a PAD (November 2026)

There is no New PAD button on this list. Raise one from the order instead: open the sale order, go to its Adjustments tab and use Raise discount in the Post-approval discounts table (orders that are Approved for despatch, In despatch or Completed; needs pad.create and pad.submit). Pick the Reason, optionally a Line (blank = whole order), the Amount and remarks; a TDS reason also asks for the TDS deductor and TAN, and a reason whose partner is Custom asks for the invoice customer. The dialog shows how much is still outstanding; an amount above that is refused with a message. The PAD is created and sent straight to Pending Approval, where it is decided here. The field app and API can still raise PADs too.

Columns

ColumnShows
PAD numberThe PAD's reference (pad_number), shown as a badge. Searchable, sortable.
CustomerThe customer's full name.
ReasonThe configured discount reason (reason.name) — this is what decides, behind the scenes, whether approving the PAD also posts a journal entry.
AmountThe discount amount, in ₹. Sortable.
StateA state badge — colours below. Draft Draft, Pending Approval Pending Approval, Approved Approved, Posted Posted, Cancelled Cancelled.
Booking dateThe date the discount was booked. Sortable.

Filter

A State filter lets you narrow the list to any one of the five states above.

Screenshot placeholderThe Post Approval Discounts list — PAD number, customer, reason, amount, state badge and booking date columns, with the State filter panel open.

Viewing a PAD Built

Use the View row action to open a PAD's detail page — read-only, gated by the same pad.view permission as the list. It has three info panels and no child table:

Everything here is read-only — a PAD is driven through its lifecycle by the Approve / Reject / Cancel actions below, not edited as a form.

Screenshot placeholderThe PAD detail page: a "Discount" info panel (PAD number, state badge, customer, reason, amount, booking date), an "Applied to" panel (sale order, sale-order line, package, invoice customer), and an "Approval & audit" panel (submitted by, approved by, linked journal entry).

Actions

ActionPermissionFrom stateDetails
Approvepad.approvePending Approval → ApprovedConfirmation only, no form. Refused (422) if the discount amount exceeds the sale order's remaining outstanding balance. If the PAD's reason is configured to post a journal entry, approving it automatically creates and posts that entry and the PAD advances straight through to Posted in the same step.
Rejectpad.approvePending Approval → CancelledConfirmation with a form: reason (Textarea, required, max 1000). There is no distinct "Rejected" state — a rejected PAD lands on Cancelled, same as a cancelled one.
Cancelpad.cancelDraft, Pending Approval or Approved → CancelledConfirmation only, no form. Refused (409) if the PAD has already reached Posted with a linked journal entry — "reverse the journal entry first" on the Accounting page.
Why Cancel can still be refused

Cancel is offered on rows at Draft, Pending Approval or Approved. If, between opening the page and confirming, the PAD advanced to Posted in another tab or because your own Approve just auto-posted its journal entry, the cancellation is refused and you're told to reverse the journal entry first instead.


Refund Requests Partial

A Refund Request is money AIR owes back to a customer. It appears under Refund Requests in the Billing group. Viewing the list needs refund.view. Each row can also be opened to a read-only detail view (below).

Requesting a refund (November 2026)

A refund always gives back money a particular payment voucher paid, so it is raised from that voucher: open it on Payment Vouchers and use Request refund (refund.create + refund.submit; the voucher must still be reallocatable, e.g. Cleared). The dialog lists every order line the voucher paid, with what it paid; enter how much goes back on each (you cannot enter more than the voucher paid on that line), choose Cheque, NEFT (optionally the AIR bank account it is paid from) or Adjustment, and give a reason. The refund is created and sent straight to Submitted, and you land on its page to approve, reject or issue it. The field app and API can still raise refunds too.

Columns

ColumnShows
Refund numberThe refund's reference (refund_number), badge. Searchable, sortable.
CustomerThe customer's full name.
Total amountThe refund amount, in ₹. Sortable.
StateDraft Draft, Submitted Submitted, Approved Approved, Issued Issued, Rejected Rejected.
Refund methodHow the money will go back — Cheque, NEFT or Adjustment. This decides which fields the Issue form asks for.

Filter

A State filter narrows the list to any one of the five states.

Screenshot placeholderThe Refund Requests list — refund number, customer, total amount, state badge and refund method columns.

Viewing a refund Built

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

Below the panels, a read-only Items table: one row per sale-order line the refund covers, showing the refund amount, the allocated amount, the PAD amount and any remarks. Everything here is read-only — a refund is driven through its lifecycle by the Approve / Reject / Issue actions below, not edited as a form.

Screenshot placeholderThe Refund Request detail page: "Refund", "Source & bank" and "Approval & audit" info panels, with an "Items" table below (per sale-order line: refund amount, allocated amount, PAD amount, remarks).

Actions

ActionPermissionFrom stateDetails
Approverefund.approveSubmitted → ApprovedConfirmation only, no form.
Rejectrefund.approveSubmitted → RejectedConfirmation with a form: rejection_reason (Textarea, required, max 1000).
Issuerefund.issueApproved → IssuedConfirmation with a form whose required fields depend on the refund's method (see below).

The Issue form

The form always offers the same three fields, but which ones you must fill depends on the record's refund_method:

FieldTypeRequiredNotes
refund_cheque_numberTextOnly if method is ChequeThe cheque number issued to the customer.
refund_cheque_dateDateOnly if method is ChequeThe date on the cheque.
Pay from bank accountPick from AIR's bank accountsOnly if method is NEFTThe account the refund was transferred from (pre-filled if chosen when the refund was requested).

If the method is Cheque and you leave the cheque fields blank, or the method is NEFT and you leave the bank account blank, the action is refused with a validation error rather than issuing an incomplete refund.

What issuing does to the money (November 2026)

Issuing a refund can post to the ledger

If refund accounting is switched on in System Configuration — an opt-in flag plus a debit and a credit account under the accounting group — then issuing a refund also creates and posts a balanced double-entry to the ledger in the same step, linked back to the refund. If the flag is off, or either account is left blank, nothing is posted — so a journal entry only appears for refunds issued while accounting is configured. The entry, once posted, shows up on the Accounting — Journal & GST page. These refund.* account settings are shared across all refunds (refunds have no per-type accounting).


Charges Partial

A Charge is money AIR levies on a customer — for example a cheque-bounce fee. It appears under Charges in the Billing group. Viewing the list needs charge.view. Each row can also be opened to a read-only detail view (below).

Adding and notifying a charge

Add a charge from the sale order: Adjustments tab → Charges → Add charge (pick an active charge type; leave the amount blank for the type's default rate). Charge types ship switched off — if the Type list is empty the dialog says so; turn one on under Billing → Charge Types. A new charge is a Draft; Notify customer on this list (charge.notify, November 2026) sends it and moves it to Notified, after which you can Resolve or Cancel it. If the customer objects, Record dispute on the notified charge (charge.dispute) takes their response and moves it to Disputed; the response and date then show on the charge's page. Resolve or cancel it from there.

Columns

ColumnShows
Charge numberThe charge's reference (charge_number), badge. Searchable, sortable.
CustomerThe customer's full name.
TypeThe configured charge type (chargeType.name) — e.g. cheque-bounce.
AmountThe charge amount, in ₹. Sortable.
StateDraft Draft, Notified Notified, Disputed Disputed, Resolved Resolved, Cancelled Cancelled.
ResolutionOnce resolved, whether the charge was Levied or Waived. Blank until resolved.

Filter

A State filter narrows the list to any one of the five states.

Screenshot placeholderThe Charges list — charge number, customer, type, amount, state badge and resolution columns.

Viewing a charge Built

Use the View row action to open a charge's detail page — read-only, gated by the same charge.view permission as the list. It has two info panels and no child table:

Everything here is read-only — a charge is driven through its lifecycle by the Resolve / Cancel actions below, not edited as a form.

Screenshot placeholderThe Charge detail page: a "Charge" info panel (charge number, state badge, resolution badge, customer, type, amount) and a "Resolution & audit" panel (resolved by, created by, linked journal entry, remarks).

Actions

ActionPermissionFrom stateDetails
Resolvecharge.resolveNotified or Disputed → ResolvedConfirmation with a form: resolution (Select — Levy or Waive, required); resolution_notes (Textarea, optional, max 1000).
Cancelcharge.cancelDraft, Notified or Disputed → CancelledConfirmation only, no form.
Levy or Waive

Resolving a charge always asks you to record the outcome: Levy confirms the customer is charged, Waive writes it off with no payment. Either way the charge moves to Resolved — the choice is recorded, not enforced by a further state.

A levy can post to the ledger

If the charge's charge type is configured for accounting (an opt-in flag plus a debit and a credit account), resolving it as Levy also creates and posts a balanced double-entry to the ledger in the same step, linked back to the charge. Waive posts nothing, and a charge type left unconfigured posts nothing either way — so a journal entry only appears for levied charges under a configured type. This accounting configuration lives on the charge type and is set through the API, not this console; the entry, once posted, shows up on the Accounting — Journal & GST page.

Related pages: Payment Vouchers · Sale Orders · Accounting — Journal & GST · Bank Reconciliation.