GST invoice preparation for Uttar Pradesh service businesses
For a Noida project or a recurring Lucknow client, keep the service period, invoice timing and payment record clear. Confirm who receives the service and what the contract requires before preparing the bill. These examples help you organise the details without assuming that a monthly reminder decides GST treatment.
By Invoodle · Updated · Guidance reviewed October 2026
India mode selects INR and a supplier GST-number input. It does not select a state registration, determine place of supply, split CGST/SGST/IGST, generate an IRN or file GST returns. Review the required particulars and PDF limits before issue.
Record Uttar Pradesh as code 09 and verify the actual customer
Uttar Pradesh uses 09 in a two-character GST state-code field; the official numeric master displays it as 9. Delhi is a separate jurisdiction, code 07. An NCR address is not enough to identify the recipient registration.
Confirm the supplier establishment, customer legal entity, relevant GSTIN and establishment receiving the service. A matching 09 prefix does not validate a complete GSTIN, active status or entitlement to collect GST.
The Uttar Pradesh State Tax Department links official taxpayer services, jurisdiction resources, Acts and manuals. Use the appropriate official service for a real registration check; Invoodle does not perform that lookup.
Check the recipient rule separately from the contract schedule
The first two fictional cases assume a taxable ordinary domestic B2B service supplied from a Noida establishment to an identified registered recipient. They exclude property, event and other specific service rules, SEZ, cross-border and special treatment.
Under the general registered-recipient rule, review the recipient location before comparing it with the supplier location. The third case asks a different question: when to issue a bill under a contract already confirmed to meet the continuous-supply provisions.
| Fictional arrangement | Fact to establish | Check before preparing the bill |
|---|---|---|
| Noida supplier provides an ordinary B2B service to a registered Lucknow recipient | Recipient location is Uttar Pradesh | CGST plus Uttar Pradesh SGST under the stated assumptions |
| Noida supplier provides the same ordinary service to a registered Delhi recipient | Recipient location is Delhi | IGST under the stated assumptions |
| A qualifying continuous service contract has payment due on 31 October | The contract fixes that payment date; assume no earlier advance or other trigger | Review issue on or before 31 October under section 31(5)(a) |
Do not treat every repeat invoice as continuous supply
Check the statutory definition first: it covers continuous or recurrent contractual services exceeding three months with periodic payment obligations, and notified cases. A label such as “monthly support” does not by itself establish that treatment.
For a qualifying contract, section 31(5) distinguishes an ascertainable payment date, payment without an ascertainable due date and payment linked to an event. Review advance and other applicable provisions too. The fictional date is not a universal deadline for service invoices.
Keep the contract, service period, agreed milestones and evidence together. Unregistered persons must not collect GST as though registered; document choice and current treatment still need review.
Keep a partial payment separate from the tax calculation
Assume one completed service period has a correctly determined INR 6,000 taxable base at 18%, with no order discount or shipping. Tax is INR 1,080 and gross is INR 7,080. A verified INR 2,000 payment received against that issued invoice leaves INR 5,080 due; it does not reduce the original taxable base to INR 4,000.
This is ordinary invoice-balance arithmetic, not a service classification, rate recommendation or advance-payment tax calculation. In a correctly determined ordinary intra-state case at the assumed rate, tax would illustrate INR 540 CGST plus INR 540 Uttar Pradesh SGST; a corresponding inter-state case would illustrate INR 1,080 IGST. The editor exports one general Tax total, not that split.
Record each payment against the correct issued reference and reconcile it with evidence. A reminder for the balance is not a second invoice for the same supply. This example stays separate from your saved documents.
| Stage | Arithmetic | Amount (INR) |
|---|---|---|
| Taxable base assumption | Reviewed base for one service period | ₹6000.00 |
| Assumed tax | ₹6,000 × 18% | ₹1080.00 |
| Original gross invoice | ₹6,000 + ₹1,080 | ₹7080.00 |
| Verified payment against the issued invoice | Recorded separately after issue | ₹2000.00 |
| Remaining balance | ₹7,080 − ₹2,000 | ₹5080.00 |
Prepare the invoice particulars and supporting records
Collect the invoice reference and date, supplier and recipient details, service description and period, classification, reviewed taxable value, tax rate, components and required place-of-supply or reverse-charge particulars. Confirm any special wording and reporting requirements before issue.
Read CBIC’s historical particulars with current amendments and the applicable supply rules. Neither a recurring schedule nor this checklist establishes a complete tax invoice. Keep the issued copy and correction trail with the underlying contract and payment evidence.
Review the INR editor and repeat-billing limits
The action selects invoice mode, India and INR, not an Uttar Pradesh registration. Supplier GST-number entry is available; dedicated buyer GSTIN, HSN/SAC, place-of-supply and reverse-charge controls are absent. It does not validate registration or determine tax treatment.
The PDF has one general Tax total. One document-level percentage applies to subtotal before the separate order discount. The editor does not resolve mixed line rates, adjusted statutory taxable values, separate tax heads, IRNs or GST filing. A due date or duplicate draft does not implement a statutory timing decision.
Repeat invoices need review of the new period, amount, reference and payment details. Payments, reminders and sending require manual action. Guest records stay in this browser without automatic device sync; export backups and keep a financial-year reference register because the suggested counter uses calendar years. Sharing/account features have separate data handling.