Customer Advance and Pre-Order Deposit Reconciliation for Indian Drone Manufacturers

Terra Insight Reconciliation Infrastructure

Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →

Published 11 May 2026

Domain expertise

TDS Reconciliation GST Input Credit Platform Settlements NACH Batch Matching Bank Reconciliation Form 26AS Matching ERP Integrations Enterprise Finance Ops

Reviewed by

Navin Krishnan

Managing Director & Founder — Terra Insight

Ex Amazon India · Intuit QuickBooks · Tata nexarc

ISO 27001:2022 Patent Pending Incorporated 2024

Knowledge Card

Problem

Drone OEMs operate a pre-order / deposit driven sales model with large defence, agriculture and survey customers paying 20-50% advance against orders ranging from ₹50 lakh to ₹50 crore, creating multi-month gap between cash receipt and goods dispatch — with GST time-of-supply rules under Section 13 of the CGST Act (Notification 66/2017 exempting advance on goods from GST at receipt but services chargeable at receipt), advance receipt voucher under Rule 50, refund mechanism under Section 54 on cancellation, and Ind AS 115 revenue-recognition only on transfer of control at dispatch.

How It's Resolved

Book each advance as customer-advance current liability on receipt, evaluate goods-vs-services classification per order line under Section 13 time-of-supply, issue advance receipt voucher under Rule 50 with proper detail, age customer-advance liability by customer and pre-order date, defer revenue recognition until transfer of control at dispatch under Ind AS 115, reconcile bank credit against the order's expected advance schedule, manage cancellation refunds against the original ARV with Section 54 refund claim on any service-portion GST collected and reversed.

Configuration

Customer master with deposit schedule by order, order master with goods/services line split for GST classification, advance receipt voucher format compliant with Rule 50, bank-credit matching against expected advance amount and order reference, ageing buckets on customer-advance liability (0-30/31-90/91-180/180+ days), cancellation workflow with refund voucher and Section 54 refund tracking on any service-portion GST.

Output

A monthly customer-advance reconciliation dashboard showing total deposit liability by customer and order, age buckets, advance receipt voucher register reconciled to bank credits, deferred revenue under Ind AS 115 ready for dispatch trigger, cancellation refund queue, Section 54 GST refund register for service-portion reversals, and dispatch-ready orders against held advances.

A drone OEM in Hyderabad with ₹50 crore annual revenue closes April books and pulls the customer-advance ledger: ₹14.6 crore total deposit liability across 47 enterprise customers (agriculture cooperatives, state survey departments, defence systems integrators, large industrial inspection firms), spread across 73 active orders ranging from ₹38 lakh to ₹8 crore. The oldest deposit sat 11 months in the books against a defence systems integrator order where the certification of the proposed drone model is delayed. The newest deposit, ₹1.5 crore — 30% advance on a ₹5 crore order from an agriculture cooperative — arrived three days earlier and triggered ARV issuance the same day. The drone customer advance deposit reconciliation India stack runs four interlocking ledgers — customer-advance liability, ARV register, GST treatment per order, and refund/cancellation workflow — and each month-end has to reconcile all four against the bank statement.

Quick reference

Item	Value
Governing section (GST timing)	Section 13 of the CGST Act 2017
Notification governing goods-advance	CBIC Notification 66/2017
GST on advance for goods	Not chargeable at receipt (taxpayers other than composition dealers)
GST on advance for services	Chargeable at receipt (time of supply triggers on payment)
Advance Receipt Voucher rule	Rule 50 of the CGST Rules
Refund mechanism on cancellation	Section 54 of the CGST Act
Refund voucher rule	Rule 51 of the CGST Rules
Accounting standard	Ind AS 115 (Revenue from Contracts with Customers)
Typical drone OEM advance %	20% to 50% of order value
Typical order tenor	1-9 months from advance to dispatch

How does Section 13 time-of-supply actually work for goods vs services

Section 13 establishes time of supply for goods as the earlier of:

Date of invoice or date by which invoice ought to have been issued
Date of receipt of payment

On a literal reading, an advance received before invoice would trigger GST at receipt. CBIC Notification 66/2017 (issued under Section 148) overrides this for goods — taxpayers other than composition dealers do not pay GST at receipt of advance for supply of goods. GST is payable only at invoice/dispatch. The notification has applied continuously since November 2017 and continues to govern.

For services, no such notification exists — Section 13’s “earlier of invoice or payment” rule operates in full force and GST is payable on advance for services at the time of receipt.

A drone OEM supplying a drone (clearly goods) takes the advance with no immediate GST liability. The same OEM offering a separate service component — pilot training, maintenance AMC, fleet management service, mission planning service — must split the advance between goods and service portions and apply GST on the service portion at receipt.

How is the advance receipt voucher structured under Rule 50

Rule 50 of the CGST Rules prescribes the ARV format. Every registered person receiving an advance towards any supply must issue an ARV at the time of receipt. The ARV captures:

Supplier name, address, GSTIN
A consecutive serial number per supplier per FY
Date of issue
Recipient name, address, GSTIN where applicable (B2B) or state where B2C
Description of the proposed supply
Amount of advance received
Rate of tax (CGST + SGST or IGST as applicable)
Amount of tax charged on the advance — nil for goods advance under Notification 66/2017, full GST rate for services advance
Place of supply with state name and code for inter-state supplies
Signature or digital signature of supplier

For a drone OEM the ARV is issued for every advance, even when no GST is payable (goods advance), because the documentation step is statutorily required. Without the ARV the input-tax-credit chain at the customer’s end (when the customer claims ITC eventually on the dispatch invoice) lacks the required audit trail.

How is the customer deposit booked in the GAAP ledger

The advance is a balance-sheet liability — not revenue — until transfer of control occurs.

Entry on receipt of advance:

Dr Bank                          ₹1,50,00,000
   Cr Customer Advance              ₹1,50,00,000

Entry at dispatch (against ₹5 crore order with 18% GST on drones):

Dr Customer Advance              ₹1,50,00,000
Dr Trade Receivable              ₹4,40,00,000
   Cr Revenue                       ₹5,00,00,000
   Cr Output IGST 18% on ₹5 cr        ₹90,00,000

(The ₹5 crore order grosses up to ₹5.9 crore with IGST; the ₹1.5 crore advance applies as a partial settlement; the receivable for the balance ₹4.4 crore remains open for collection.)

Under Ind AS 115, revenue is recognised at the point of transfer of control to the customer — typically at dispatch for a standard goods supply, with bill-of-lading / proof-of-delivery being the operational trigger. For more complex contracts (drone fleet with integration, training, customisation) the revenue may be recognised over time per Ind AS 115’s continuous-performance criteria.

How is the deposit liability aged

A long-tenor customer-advance sitting unconverted to revenue draws scrutiny at audit and possibly at tax assessment. Reconciliation should age the advance liability:

0-30 days: healthy, awaiting production
31-90 days: standard production cycle, monitor
91-180 days: extended cycle, confirm with customer that order is live
180+ days: structural delay, often indicating certification delay, design change, or order rework — provision evaluation under Ind AS 37, customer communication mandatory

A 180+ day customer-advance liability against a ₹2.1 crore agricultural cooperative deposit, with the proposed drone model awaiting an R4 type-certification successful attempt, is a real-world reconciliation example — the advance sits liability, ARV is on file, no GST is at risk, but commercial communication and provisioning evaluation must be active.

What happens on cancellation and refund

If a customer cancels the order before dispatch, the OEM refunds the advance. Since no GST was collected at receipt for the goods component (Notification 66/2017), there is no output GST to reverse — the entry is straightforward:

Dr Customer Advance              ₹1,50,00,000
   Cr Bank                          ₹1,50,00,000

Rule 51 of the CGST Rules requires a refund voucher referencing the original ARV. The refund voucher must include all the same fields as the ARV plus the refund amount and the original ARV reference.

If the original advance included a service component on which GST was collected at receipt, refund of that GST is claimed under Section 54 of the CGST Act — refund of tax paid on supply of services not provided. The Section 54 refund application is filed in Form GST RFD-01 with supporting documentation (original tax invoice or ARV, refund voucher, customer communication on cancellation, bank statement showing refund processed). Reconciliation must maintain the Section 54 refund register against any service-portion GST reversal.

Worked example — ₹5 crore drone order with ₹1.5 crore 30% advance

Order value (drone hardware, classification as goods): ₹5 crore
GST rate applicable on drones (standard category): 18%
Advance: ₹1.5 crore (30%)
Advance receipt date: 1 April 2026
ARV issued: 1 April 2026, serial ARV/2026-27/0117
GST on advance: nil (Notification 66/2017)
Customer-advance liability booked: ₹1.5 crore current liability
Production cycle: 80 days
Dispatch date: 20 June 2026
Tax invoice issued: 20 June 2026, ₹5 crore + ₹90 lakh IGST = ₹5.9 crore
Advance adjusted: ₹1.5 crore against invoice → balance receivable ₹4.4 crore
Output GST liability triggered: ₹90 lakh in June GSTR-1 / GSTR-3B
Bank reconciliation: advance bank credit on 1 April matched to ARV/2026-27/0117; balance receivable ₹4.4 crore collected per contract terms

If the same order had included a separate ₹15 lakh pilot training service component with advance on it:

Service component advance: ₹4.5 lakh (30% of ₹15 lakh)
GST on service advance: 18% on ₹4.5 lakh = ₹81,000 at receipt under Section 13
Output GST in April GSTR-3B: ₹81,000 on service advance
On training completion, balance ₹10.5 lakh + GST collected and adjusted against the original service advance

Section 393 cross-reference

When the customer is a business buyer above turnover thresholds, the customer may deduct Section 393(1)(k) TDS at code 1012 (legacy 194Q) at 0.1% on the purchase value above ₹50 lakh aggregate per FY. The TDS is on the buyer’s side and reflects in the OEM’s Form 26AS. Reconciliation should monitor 26AS reflections against expected TDS on the order. See Section 393 TDS new Income Tax Act reconciliation and TDS payment codes 1001-1092 India.

CBIC authority reference

For Section 13 time-of-supply text, Notification 66/2017 on goods-advance, advance receipt voucher format under Rule 50, and Section 54 refund mechanism see the Central Board of Indirect Taxes and Customs (CBIC).

What automated reconciliation changes

Manual customer-advance reconciliation across 47 customers and 73 active orders with ARV register, ageing buckets, GST goods-vs-services split and cancellation refund handling is a 4-6 day month-end exercise at a meaningful drone OEM. Purpose-built reconciliation software India configures the customer-advance flow as a structured workflow with order master goods/services split, ARV register, bank-credit matching, ageing dashboard and Section 54 refund tracker. TransactIG carries 24+ industry presets. Customer outcomes include match-rate improvement from 51% to 88% on receivables ledgers. Build is two-to-four weeks on AWS Mumbai (ISO 27001:2022). For the inbound procurement match see three-way matching software India.

Primary reference: Central Board of Indirect Taxes and Customs (CBIC) — for GST time-of-supply rules under Section 13 of the CGST Act, Notification 66/2017 on advance for goods, advance receipt voucher format under Rule 50, and Section 54 refund mechanism on cancelled supplies.

Frequently Asked Questions

When does GST become payable on a customer advance for a drone supply?

Under Section 13 of the CGST Act, time of supply for goods is the earlier of date of invoice or date of receipt of payment. However, CBIC Notification 66/2017 (current law) exempts taxpayers other than composition dealers from paying GST at the time of receipt of advance for supply of goods — GST is payable only at invoice/dispatch. For services, the position is different: GST is payable on advance receipt as time of supply triggers on payment. A drone OEM supplying a drone (goods) takes the advance with no immediate GST liability; if the same order included a separate component for pilot training or service support (services), advance against that service component would attract GST at receipt.

What is an advance receipt voucher and when is it issued?

Rule 50 of the CGST Rules requires a registered person receiving an advance towards any supply (goods or services) to issue an advance receipt voucher (ARV) at the time of receipt. The ARV captures the advance amount, supplier and customer details, GSTIN where applicable, description of the proposed supply, and the rate of tax. For drone OEMs taking advances on goods supply (currently not GST-chargeable at receipt per Notification 66/2017), the ARV is still required as a documentation step. On final dispatch the tax invoice supersedes the ARV and any GST liability triggers on the invoice amount.

How is the customer deposit booked in the accounting ledger?

The advance/deposit is a liability on the OEM's balance sheet — not revenue. The accounting entry on receipt is debit Bank, credit Customer Advance (current liability). Revenue recognition under Ind AS 115 happens only on transfer of control to the customer (typically at dispatch for goods, with appropriate revenue-recognition trigger). On dispatch the entries reverse: debit Customer Advance against the invoice value, credit Revenue (for the goods portion) and credit Output GST (on the invoice). Reconciliation must age the customer advance liability by customer and pre-order date — long-tenor deposits sitting above 12 months attract scrutiny under audit and possibly under tax assessment for revenue-recognition disputes.

What happens if a drone order is cancelled and the advance has to be refunded?

When an order is cancelled before dispatch, the OEM must refund the advance to the customer. Since GST was not collected at receipt (goods advance under Notification 66/2017), there is no output GST reversal on the OEM's books. The advance liability is simply extinguished against the bank outflow. If GST had been collected (services advance) and refunded, the OEM claims the refund under Section 54 of the CGST Act for tax paid on supply of services not provided. The advance receipt voucher must be referenced in the refund voucher (Rule 51) and the GSTR-1 / GSTR-3B return adjusted in the next filing.

How does Section 13 time-of-supply interact with milestone production stages?

For drone supplies typically structured as advance-on-order plus balance-on-dispatch, the goods-supply rules apply at dispatch — GST triggers on the full invoice value at dispatch with the advance adjusted against the invoice. For larger fleet orders structured with milestone payments (advance, design freeze, first article, bulk production, delivery), if the contract is for goods supply the time of supply remains at each dispatch event with no GST at any earlier milestone. If the contract is structured as a composite supply with explicit service components (training, integration, maintenance), the service portions trigger GST at payment receipt and the goods portions at dispatch. Reconciliation must split each milestone payment between goods and service consideration where applicable.