Free tools Windows power users keep installed
One-click scans. No signup required.
When an Indian e-invoice fails on a reverse-charge field, begin with two separate checks: whether the notified supplier is reporting its own invoice for a supply that attracts reverse charge under section 9(3), and whether the submitted payload contains a reverse-charge value that the current Invoice Registration Portal (IRP) schema accepts for that transaction. Error 2159 points to an invalid value in the reverse-charge field; error 2162 means reverse charge has been marked for a transaction type the portal does not accept, including the non-B2B case identified in IRP guidance. Fix the classification and the transmitted payload before retrying, and check for an existing IRN before submitting again.
Scope and date: This guide is for GST-registered businesses, tax practitioners and ERP teams in India. It reflects official IRP material available on 13 October 2026. E-invoice notifications, schemas, validation logic and correction procedures can change, so verify the live portal instructions before taking a filing action.
As an Amazon Associate I earn from qualifying purchases.
First decide whether this is an e-invoice obligation at all
Reverse-charge tax liability and supplier-side e-invoice reporting are related but different questions. The GST E-Invoice System FAQ states that e-invoicing applies when a notified person issues an invoice for a supply made by that person that attracts reverse charge under section 9(3). Its example is a notified firm of advocates supplying services to a company that pays the reverse-charge liability. The recipient’s responsibility to pay tax does not, by itself, turn every reverse-charge transaction into a supplier e-invoice.
| Question | What to establish | Why it matters |
|---|---|---|
| Who issued the document? | Identify the supplier that made the supply and the legal entity issuing the invoice. | The cited FAQ addresses a notified supplier’s own invoice, not a document created merely because a recipient has an RCM payment obligation. |
| Does the supply attract section 9(3) reverse charge? | Check the current notification and the actual nature of the supply. | Do not infer section 9(3) treatment from an internal tax label alone. |
| Is the supplier a notified person? | Confirm the supplier’s current e-invoicing coverage, including the applicable turnover and exemption rules. | Notification status determines whether the document must be reported to an IRP. |
| What kind of transaction is it? | Check the buyer’s GST status, document type and B2B classification. | Error 2162 is a transaction-classification conflict, not simply a bad tax amount. |
The FAQ distinguishes the described supplier-issued section 9(3) case from supplies received from an unregistered person and from imported services. Those distinctions should be applied to the facts and the current notifications; avoid a blanket rule that every RCM payment produces an e-invoice.
#1 Best Overall
- Two-Part Carbonless Invoice Book: Each invoice book has 50 sets of invoices, each with a white/light yellow section, with the yellow section retained in the invoice book to maintain detailed records.
- Consecutively Numbered: Enlarged red 6-digit numbers in the upper right corner of each invoice receipt book help you quickly navigate through your orders.
- Wraparound Divider Flap: A thick folded cardboard divider is integrated into the back of each invoice book for use between each two-part sales order to prevent the written content from rubbing off on subsequent copies of the invoice, resulting in wasted invoices.
- 2 Packs/50 Sets (100 Sets Total): Each invoice book provides 50 sequentially numbered carbonless sets of 2 invoice books for long-term use.
- Customizable Space: Each invoice book for small business has space at the top to add a company seal or sticker.
What errors 2159 and 2162 actually mean
| IRP response | Meaning | First action |
|---|---|---|
| 2159 — Invalid value for reverse charge applicable field | The request contains a reverse-charge applicability value that fails the portal’s expected representation. | Inspect the serialized request and compare the field’s type and permitted value with the current request JSON schema. The IRP directs taxpayers to that schema in its troubleshooting guidance. |
| 2162 — Reverse Charge is not applicable for this transaction | The payload marks reverse charge for a transaction type the portal does not accept for that flag. IRP guidance identifies the non-B2B situation as a listed case. | Recheck transaction classification, document type, counterparty status and the supplier/recipient roles before changing the field. |
| Another validation code | The rejection may concern GSTINs, item tax, totals, dates, document numbering or another payload attribute. | Repair the field named by the actual code instead of assuming every rejection is an RCM error. |
The wording shown by the portal is a diagnostic clue, not a substitute for checking the whole invoice. A valid reverse-charge value cannot make an incorrectly classified transaction valid, and a correct classification cannot rescue a malformed serialized field.
Fixing error 2159: invalid reverse-charge field value
Error 2159 is usually an interface or mapping problem. The invoice screen may display a friendly label while the API receives a different value, an empty string, the wrong data type or a value left over from an earlier integration.
- Save the complete failed response. Record the error code, message, request identifier and timestamp. Do not rely on a screenshot of the user interface.
- Capture the exact outbound payload. Obtain the JSON after all ERP transformations and immediately before it is sent to the IRP. A source invoice export is not enough if middleware changes the field.
- Locate the reverse-charge attribute. Check the field used by the current schema for reverse-charge applicability, including its nesting and spelling. Compare it with the current IRP validation rules and request JSON schema.
- Check representation details. Inspect data type, permitted value, letter case, whitespace, null handling, blank handling and any conversion from a database Boolean, checkbox or business label. A blank value that is silently converted to an empty string can fail even when the screen appears unselected.
- Trace the mapping chain. Follow the value from the tax determination rule through the invoice table, export routine, middleware and API serializer. Look for mappings such as “RCM,” “reverse,” “yes/no” or numeric flags being passed where the schema expects a different representation. Do not invent a replacement value; use the value currently specified by the schema used for your integration.
- Rebuild the payload from corrected source data. Correct the transaction record and regenerate the JSON rather than editing a single character in a stored request. This prevents a later retry from restoring the old mapping.
- Validate before submission. Run your ERP’s schema or integration validation, then compare supplier GSTIN, recipient GSTIN, document type, dates, item tax and totals with the invoice. Submit once and retain the complete response.
If the portal still returns 2159, compare the raw request generated by a known-good transaction of the same type with the failed request, field by field. Escalate the difference to the ERP or integration owner, including the schema version and the unmodified IRP response.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Rank #2
- QUALITY INVOICES: Adams Order books provide a professional invoice or customer receipt; a great way to create and maintain a professional image for small businesses and service providers
- 50 TWO-PART CARBONLESS FORMS: Customers get the perforated white top copy; retain the canary and pink copies for your records
- WRAP-AROUND COVER: Fold the back cover between sets to keep invoices neat and legible
- ROOM FOR CUSTOMIZATION: A blank space at top leaves room for your company stamp; a big savings over custom-printed forms
- CONSECUTIVELY NUMBERED: Large 6-digit numbers in the upper right hand corner help you thumb through orders quickly
Fixing error 2162: reverse charge is not applicable for this transaction
Error 2162 is a classification warning expressed as a rejection. It indicates that the reverse-charge flag conflicts with the transaction type accepted by the portal. The listed IRP case is a transaction other than B2B, so changing the flag without checking the underlying sale can create a tax and reporting error.
- Confirm the buyer and supplier roles. Make sure the payload identifies the actual supplier as the document issuer and the actual recipient as the buyer. Do not use a recipient-side RCM journal as though it were the supplier’s invoice.
- Check the B2B classification. Verify the recipient GSTIN, registration status and the transaction category selected in the invoice. If the transaction is not eligible for the B2B classification used by the portal, stop and determine the correct reporting treatment.
- Check document type and source. Confirm whether the document is the supplier’s tax invoice or another document such as a credit note, debit note or a document generated for a different business event. The reverse-charge flag must fit the document and transaction rules together.
- Reconfirm the legal basis. Establish that the supply actually falls under section 9(3) and that the supplier is within current e-invoice notification coverage. A payment posted to an RCM ledger is not proof that the supplier-issued invoice belongs in this category.
- Correct the classification at source. Update the tax determination and transaction-type fields in the ERP, regenerate the payload and review all dependent totals. Do not simply toggle the reverse-charge field in the API while leaving a contradictory transaction type.
- Submit only after checking duplicates. If an earlier attempt succeeded, a new submission may be treated as a duplicate. Search your IRP records and integration logs for an IRN first.
When the rejection is not 2159 or 2162
The IRP validation material covers broader checks, including supplier GSTIN, item-level tax aggregation and invoice totals. Read the complete response and isolate each named field. A payload can contain a valid reverse-charge setting and still fail because a GSTIN is malformed, item taxes do not add up, or a total is inconsistent with the transaction.
GSTIN and party data
Check that the supplier and recipient GSTINs belong to the entities shown on the invoice, that the state code and address data are consistent, and that a test or inactive identifier has not been carried into production. Correct the master data, regenerate the payload and revalidate.
Rank #3
- QUALITY INVOICES: Adams Invoice books provide a professional invoice or customer receipt; easily customize by using the extra space at the top and your company stamp
- 50-TWO PART CARBONLESS FORMS: Customers get the perforated white top copy; retain the yellow copy for your records
- WRAP-AROUND COVER: Fold the back cover between sets to keep invoices neat and legible
- CONSECUTIVELY NUMBERED: Large 6-digit numbers help you thumb through invoices quickly
- STOCK UP: Each book includes 50 white/canary sets; order several to keep your favorite forms on hand
Item tax and aggregation
Reconcile taxable value, rate, tax amount, quantity, unit price, discounts and invoice-level adjustments from the item lines through the summary fields. An integration that rounds each line differently from the ERP total can produce a rejection even when the printed invoice looks correct.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Total-value treatment in reverse-charge transactions
An older IRIS explanatory article notes that, for reverse-charge and export-with-payment transactions, total item value may match with or without tax values according to business requirements. Treat that statement as a validation note, not permission to alter amounts. Reconcile the payload to the actual invoice and apply the current schema and validation rule for your transaction.
A controlled troubleshooting workflow
Use this sequence for every failed submission so that a correction does not introduce a second error.
Rank #4
- This value 3 pack of Adams Invoice Books give you 150 two part carbonless invoices with a perforated white customer receipt and yellow duplicates for your records; 3 50-invoice books per pack
- Unique horizontal invoice sheets capture the purchased by and shipped to addresses; a compact 5-9/16 x 8-7/16 page still leaves plenty of room for details on up to 12 items sold
- Wraparound back cover prevents write-through between sets; pull out the perforated white customer receipt and the yellow carbonless duplicates stay behind for your records
- Unique 6 digit invoice numbers help you thumb through orders quickly; blank space up top gives you room for a company stamp—an affordable custom touch
- In value packs with three 50-invoice books for your small business; buy ahead to keep on site or take on the road for pop-up shop sales
- Classify the business event. Record supplier, recipient, registration status, supply type, section 9(3) basis, document type and whether the document is supplier-issued.
- Determine applicability. Check the current notification coverage and the FAQ distinction for unregistered-supplier receipts and imported services.
- Freeze the evidence. Save the source invoice, the exact JSON, ERP mapping version, API response, user and timestamp.
- Read the actual code. Separate 2159 field-format failures from 2162 transaction-classification failures and from unrelated validation codes.
- Compare against the current schema. Review field names, nesting, data types, permitted values and required/optional behavior in the current IRP material.
- Correct the source record. Fix master data, tax determination or document classification in the ERP instead of patching only the outbound message.
- Regenerate and test. Rebuild the complete payload, run internal checks and compare all totals and identifiers with the invoice.
- Check for an existing IRN. Search integration logs and IRP records before retrying. A successful prior report can make a later attempt a duplicate.
- Submit and reconcile. Store the IRP response, IRN and payload, then confirm that downstream return data is available and consistent.
What happens after a successful report
GSTN describes e-invoicing as reporting specified GST document details to a notified IRP and receiving an Invoice Reference Number (IRN). The GST E-Invoice System FAQ says that, on successful reporting, the invoice payload including the IRN is saved in the GST System. GSTN’s overview states that IRN generation on the listed portals is free.
The FAQ also says invoice data can flow into the supplier’s GSTR-1. If the invoice is absent or inconsistent there, check the return data and follow the system’s discrepancy process rather than creating a second invoice. Preserve the IRN and the successful payload as the audit trail.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →If an e-invoice is already wrong or already registered
An e-invoice is not amended in place. The GST E-Invoice System FAQ describes cancellation within 24 hours of generation and a later return-level correction route, including a credit note in situations where the cancellation window has passed. That FAQ content was originally published in 2022; treat the 24-hour figure as a procedure to verify against the current portal and GST rules for the document and facts, not as an exception-free guarantee.
Best Value
- 2 part carbonless forms (White originals, Canary duplicates) for invoicing customers
- Wraparound cover attached to back to place between sets
- Consecutively numbered within each book
- 50 sets per book
- Space at top for company stamp
- Stop duplicate submissions. Preserve the original invoice, JSON, IRN, error or success response and timestamps.
- Assess the error. Determine whether the problem is a reverse-charge classification, a field representation, an amount, a party identifier or another material fact.
- Check the live procedure. Confirm whether cancellation is still available for that IRN and document type, and whether any return filing has already occurred.
- Use the permitted correction route. If cancellation is available, follow the current IRP process and issue a corrected document as required. If it is not, apply the applicable return-level mechanism, which may involve a credit note.
- Obtain professional advice for material exposure. A wrong RCM treatment can affect tax payment, input-tax-credit timing and returns. A qualified GST professional should assess significant cases.
Controls that prevent recurring reverse-charge errors
- Version-control the schema. Record the request schema and validation-rule version used by each integration release. Review changes before deploying an IRP connector update.
- Use one controlled tax determination. Keep section 9(3) logic, supplier notification status and B2B classification in a governed rule set rather than allowing users to override each independently.
- Test the serialized payload. Automated tests should inspect the outbound JSON, not only the invoice form. Include null, blank, unexpected-case and legacy-value tests for the reverse-charge field.
- Separate source correction from retry. Require a new payload generation after a mapping or classification change and block blind resubmission of an unchanged request.
- Build duplicate protection. Store document number, financial year, supplier GSTIN, request identifiers and IRN responses so users can identify a successful submission before retrying.
- Reconcile downstream data. Match successful IRNs to the GST System and GSTR-1, investigate omissions and retain the discrepancy trail.
- Train users on RCM versus e-invoice scope. A recipient’s tax liability, a supplier’s invoice-reporting obligation and the portal’s B2B classification should be presented as separate decisions in the workflow.
Illustrative cases
Case 1: the screen says reverse charge, but the API sends an unsupported value
A notified supplier’s section 9(3) invoice is correctly classified as B2B, but an integration converts the ERP checkbox into a blank text value. The portal returns 2159. The remedy is to inspect the serialized field, correct the mapping to the current schema representation and regenerate the complete payload. Changing the printed invoice is unnecessary if the legal classification and source data were already correct.
Case 2: a recipient posts RCM on a receipt from an unregistered supplier
The finance team tries to create a supplier e-invoice because it has recorded an RCM liability. The FAQ’s distinction means the recipient’s RCM entry does not automatically establish the supplier-side e-invoice obligation described for a notified person’s own section 9(3) supply. Confirm the current rules and document the reason for the reporting treatment instead of forcing the transaction through the IRP.
Case 3: reverse charge is selected on a non-B2B transaction
The payload carries a reverse-charge flag, but the transaction classification is not B2B. The portal returns 2162. Recheck the buyer’s status, document type and supplier-issued nature of the invoice. The correct fix may be a change to the transaction classification or a conclusion that this document is not reportable in the assumed form; it is not automatically a change to the tax amount.
Quick checklist before you press retry
- Supplier is the party that made the supply and is within current notification coverage.
- Supply has a documented section 9(3) reverse-charge basis, if that basis is being used.
- Recipient status and transaction classification support the B2B treatment required by the portal.
- Document type and invoice source are correct.
- Reverse-charge field matches the current request schema in type, casing, permitted value and null handling.
- Raw JSON has been inspected after ERP and middleware transformations.
- Supplier GSTIN, recipient GSTIN, item taxes and totals reconcile to the invoice.
- No prior IRN exists for the same document.
- Successful response, IRN and payload will be stored for GSTR-1 reconciliation.
For live action, use the current IRP troubleshooting page and validation rules, then verify the applicable GST notification and correction procedure for your document. The safest fix is the one that makes the legal transaction, ERP source record and transmitted payload agree before another submission is made.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
