A small B2C invoice is not a universal permission to omit recipient information
For an ordinary tax invoice subject to rule 46, clause (e) requires the unregistered recipient’s name and address, delivery address, State name and code where taxable supply value is ₹50,000 or more. Below ₹50,000, clause (f) requires those details when the recipient requests them. Exactly ₹50,000 is on the mandatory side of clause (e). Read rule 46(e)–(f), its proviso and rule 54.
For the online-service cases covered by the proviso, the recipient’s State name must be recorded irrespective of value and is deemed the address on record. Do not make a low-value digital checkout bypass that field. This guide was checked on 25 October 2026 and addresses recipient-data controls, not a complete invoice-format, e-invoicing, e-way-bill or place-of-supply manual.
Classify the invoice before applying the ordinary threshold
First establish whether the recipient is registered. Clause (d) governs the registered-recipient particulars; the ₹50,000 unregistered-customer rule is not an exemption from recording a registered buyer’s required GST details. Next identify whether rule 54 provides a special document arrangement for the actual supplier or service, including specified banking, transport or other cases. Rule 46 begins subject to rule 54, so a one-size checkout rule is inadequate.
For an ordinary unregistered case, use the legally determined taxable supply value for the clause (e) test, keeping GST and any other relevant invoice values separately reconciled. Do not select the invoice grand total merely because it is the most visible figure. Apply the actual valuation provisions and any relevant adjustments first. The examples stipulate the correct taxable values and use an assumed 18% rate only for arithmetic, not as a rate determination for a named product.
Request-based details below ₹50,000 need a recorded workflow
Provide a practical route for the recipient to request the details before invoice completion. Record the information accurately and preserve the request or transaction evidence. An unregistered customer’s wish for an identified invoice is different from an unsupported request for someone else’s GSTIN; do not convert a B2C supply into a false registered-recipient transaction.
A conclusion that clause (e) does not automatically require the full details in an ordinary low-value case does not eliminate the other invoice particulars, delivery-address requirements, relevant place-of-supply evidence or another applicable law. Nor does it authorise artificial splitting of a single supply to manufacture smaller values. Correct the data model around the real transaction.
Online supplies require a recipient-State collection mechanism
CBIC Circular 242/36/2024-GST, dated 31 December 2024, explains the proviso for taxable services supplied by or through an electronic commerce operator, OIDAR supplies and the specified online gaming cases. Its clarification includes online services supplied through the supplier’s own digital facility as well as independent platforms, with examples such as digital subscriptions. Read the circular, especially paragraphs 4.3–4.5.3.
Collect the recipient State before supply and retain a defensible transaction record. The circular connects that recorded State to the address-on-record analysis under IGST section 12(2)(b), in the covered circumstances. Do not turn this into a rule that every service in every jurisdiction always uses section 12(2): special domestic service rules and cross-border provisions still need their own application.
Review common implementation failures
The recurring errors are using “more than” where clause (e) says ₹50,000 or more, comparing gross invoice value instead of the applicable taxable value, omitting a valid request below the threshold, and collecting only the supplier’s State for digital services. Keep the recipient-State field separate from the supplier location, delivery address and tax-head decision. A correctly calculated tax amount does not compensate for missing mandatory particulars.
Six worked illustrations
All facts and amounts below are fictional. Assumptions describe the model, not additional statutory rules.
Illustrative example 1: Just below the ordinary boundary
Assume an ordinary domestic taxable supply to an unregistered buyer, no special-rule case and no request. Taxable value is ₹49,999. It is ₹1 below ₹50,000, so clause (e)’s automatic full-detail threshold is not met. Other invoice and transaction requirements remain applicable.
Illustrative example 2: Exactly at the boundary
On the same ordinary-case assumptions, taxable value is ₹50,000. Clause (e)’s “or more” condition is met. The required recipient and delivery details, including State and code, cannot be omitted by treating the threshold as strictly greater than ₹50,000.
Illustrative example 3: Request below the threshold
Taxable value is ₹40,000 and the unregistered recipient requests an identified invoice with the stated particulars. Although the value is ₹10,000 below the clause (e) boundary, clause (f) requires the requested details for these facts.
Illustrative example 4: Tax raises the grand total
Assume taxable value ₹49,000 and a correctly established model GST rate of 18%. Tax is ₹8,820 and gross invoice value ₹57,820. The taxable value is still ₹1,000 below ₹50,000; the gross total alone does not change this ordinary clause (e) test. Check any recipient request and other requirements separately.
Illustrative example 5: Tax-inclusive amount at the boundary
Assume evidence establishes that a ₹59,000 inclusive price at the model 18% rate has taxable value ₹59,000 ÷ 1.18 = ₹50,000 and tax ₹9,000. Clause (e)’s threshold is met on the correctly established taxable value.
Illustrative example 6: Small online-service invoice
Assume a taxable online service falls within the rule 46(f) proviso and the circular. Taxable value is ₹500; model GST at 18% is ₹90, total ₹590. The recipient-State requirement applies despite the taxable value being ₹49,500 below ₹50,000.
Ten-step verification table
| Step | Action | Evidence |
|---|---|---|
| 1 | Identify recipient status | Registered or unregistered, with appropriate evidence. |
| 2 | Classify the document | Ordinary rule 46 invoice or applicable rule 54 arrangement. |
| 3 | Establish taxable value | Valuation working and tax-inclusive/exclusive reconciliation. |
| 4 | Apply the boundary | ₹50,000 or more for the ordinary clause (e) case. |
| 5 | Capture below-threshold requests | Customer request and the specified recipient details. |
| 6 | Screen digital supplies | Rule 46(f) proviso and Circular 242 scope. |
| 7 | Collect recipient State | Validated State name/code before covered online supply. |
| 8 | Review addresses separately | Recipient, delivery, supplier location and place-of-supply evidence. |
| 9 | Validate the final invoice | Mandatory particulars and correct tax treatment for the actual case. |
| 10 | Retain the transaction trail | Request, source data, issued document and correction history. |
Sixteen practitioner FAQs
1. Does exactly ₹50,000 trigger clause (e)?
Yes. The wording is ₹50,000 or more.
2. Is the test automatically based on the grand total?
No. Apply the rule’s taxable-supply-value test using the legally established value.
3. Can a ₹40,000 customer request details?
Clause (f) requires the stated details where its request condition is met.
4. Can an unregistered buyer supply another person’s GSTIN?
Do not use false recipient details; identify the actual transaction and buyer.
5. Does the B2C threshold excuse registered-recipient particulars?
No. The registered-recipient clause is a different requirement.
6. Are only the name and mobile number enough above the threshold?
Clause (e) specifies name, address, delivery address, State name and code.
7. Does a missing request settle every low-value invoice question?
No. Other invoice, address and place-of-supply requirements may still apply.
8. Can one supply be split artificially to omit details?
Do not manufacture smaller transaction values; reflect the actual supply.
9. Is the online State requirement limited to large invoices?
No. The proviso applies irrespective of value for its covered supplies.
10. Does an own-platform digital service escape the circular?
The clarification addresses covered online services through the supplier’s own digital facility as well as independent platforms.
11. Can the supplier’s State replace the recipient’s State?
No. They are different data fields and legal facts.
12. When should the covered online information be collected?
The circular calls for a suitable mechanism to obtain it before making the supply.
13. Does this mean every service uses the general domestic place-of-supply rule?
No. Check special service rules and cross-border provisions where applicable.
14. Does rule 54 matter?
Yes. Rule 46 is expressly subject to its special arrangements.
15. Is ₹50,000 also a complete e-way-bill or e-invoice conclusion?
No. Those frameworks require their own scope and value tests.
16. What is a useful billing control?
A classification-driven check of recipient status, taxable value, request, digital-service scope and required State/address fields.
Conclusion
Ordinary rule 46(e) requires the specified unregistered-recipient details at taxable supply value of ₹50,000 or more; below it, rule 46(f) responds to the recipient’s request. The online-service proviso requires recipient-State information irrespective of value. Check special rule 54 cases separately.