Prepare B2B sales data for GSTR-1 by matching each relevant supply to the correct registered recipient, preserving its document identity and validating the values and reporting category. A correct sales total is insufficient if an invoice appears under the wrong GSTIN or supply type.
The recipient uses supplier-reported information in its inward-supply and credit review. The supplier should therefore check invoice-level accuracy as well as its own liability totals. The following process focuses on preparation and review; the legal treatment still depends on the actual supply and applicable rules.
Confirm the recipient registration
Consider an illustrative Chennai industrial controls supplier selling to a customer with separate Tamil Nadu and Karnataka registrations. The customer’s purchasing employee provides a familiar company name but the invoice must identify the appropriate GSTIN for the transaction.
Verify the registration details and source instruction before finalising the invoice and reporting record. Do not choose a GSTIN merely because it is the first result in the customer master or because another branch paid the bill. The contractual recipient, delivery arrangement and relevant place-of-supply facts require review.
Keep legal name, trade name, State code and registration status checks where relevant. Resolve invalid or mismatched GSTINs with the customer promptly. A successful upload proves that a field passed the portal’s validation, not that the correct branch was selected.
Preserve the invoice identity
Maintain supplier GSTIN, financial year, document type, number and date in the preparation file. Keep recipient GSTIN as an essential matching attribute. Avoid spreadsheet conversions that remove leading zeros, change date formats or turn long identifiers into scientific notation.
For example, invoice TC/0268 is not automatically the same source document as TC-0268. A normalised comparison field can help detect likely matches, but preserve the original number and verify differences rather than overwriting it silently.
Where one invoice has several rates, retain line or rate-level detail while recognising that the invoice total belongs to one document. Repeating the total invoice value on every line can inflate summaries if the transformation is not designed correctly.
| Field group | Key review |
|---|---|
| Recipient | Correct GSTIN and transaction relationship |
| Document | Number, date, financial year and type |
| Supply classification | Ordinary B2B, SEZ, deemed export or other applicable category |
| Location and tax | Supported place of supply and tax heads |
| Values | Taxable amount, rate-wise tax and invoice total |
| Source status | Issued, cancelled, amended or already furnished |
The same registered customer can have transactions requiring different flags or categories. A customer master should assist the review without determining every supply automatically.
Validate values and tax heads
Suppose, illustratively, a valid invoice has taxable value ₹2,00,000 and ₹36,000 GST using an assumed applicable 18% rate. Confirm whether the facts support IGST or CGST plus SGST, and compare the full ₹2,36,000 invoice value with the rate-wise taxable and tax components.
Do not infer interstate or intrastate treatment solely from the billing address. Place-of-supply rules and special circumstances can change the result. If the tax heads are wrong, a matching grand total does not cure the error.
Check freight, discounts and other charges under the relevant valuation treatment. A ledger’s net amount may differ from the taxable value because of how charges were posted. Trace the invoice components before changing the return data.
Review auto-populated and separately entered records
Where e-invoice data reaches the GSTR-1 draft, compare it with the final issued invoices and cancellation history. Do not upload the same document again simply because it appears in the sales export. Use an explicit status to identify what is already present.
Investigate missing and errored records before generating the final summary. A failed row should remain on an exceptions list until corrected or otherwise resolved through the appropriate process. Counting only successfully processed records can conceal an incomplete upload.
For QRMP, identify records already furnished through IFF in the first two months. They should be included in the quarter’s reconciliation without being furnished again as duplicate quarterly entries.
Keep notes and corrections distinct
Credit and debit notes have their own number, date, type and values. Maintain an internal relationship to the affected invoices and commercial reason. GSTN permits delinked portal reporting in specified note workflows, but that does not remove the need to explain what the note corrects.
A revised invoice record and a separate note can duplicate an adjustment if used without reviewing their combined effect. Establish whether the issue requires an amendment, a note or another route under the current rules and filing status.
Eligible same-period errors can be reviewed for GSTR-1A before the related GSTR-3B, subject to the facility’s conditions. Earlier-period corrections need their own assessment rather than being inserted as new current sales with invented dates.
Review customer-master changes around the closing date. If a customer supplied a different GSTIN after invoicing, preserve the original document and assess whether a valid correction is required. Do not silently replace identifiers in the reporting spreadsheet while leaving the issued invoice unchanged. The customer, invoice and return record should tell a coherent story supported by the proper correction trail.
Reconcile by recipient and category
Compare document counts, taxable values and tax heads between the register and final draft. Review large customers separately and investigate invoices routed to unexpected registrations. Keep special categories distinct from ordinary B2B totals.
After any change, review the regenerated summary and preserve the version approved for filing. Save the filed acknowledgement and data with the reconciliation so later customer questions can be answered factually.
Accurate B2B reporting depends on identity and context as much as arithmetic. Confirm the correct recipient, preserve the issued document, validate classification and values, and trace every exception. The final GSTR-1 should explain the supplies actually made to each registered recipient, with a reliable trail back to the underlying invoices.