Free tools Windows power users keep installed
One-click scans. No signup required.
Most reverse-charge e-invoice rejections are resolved by separating two questions: is this a supplier invoice that falls within e-invoicing for a section 9(3) reverse-charge supply? and does the submitted payload contain a valid reverse-charge value for its transaction type? Error 2159 means the reverse-charge field value is invalid. Error 2162 means reverse charge was marked for a transaction type the portal does not accept, including a transaction classified as other than B2B in the cited IRP guidance.
This guide reflects official material available on 13 October 2026. Portal schemas, notifications, validation behavior and correction procedures can change, so verify a live filing against the current IRP instructions and the facts of the invoice.
As an Amazon Associate I earn from qualifying purchases.
What the two main IRP errors mean
Read the exact code before changing an invoice. The reverse-charge flag is only one attribute in an e-invoice payload; a rejection can instead concern a GSTIN, item tax aggregation, document classification or total.
Recommended Free Tools
| IRP response | Meaning | First action |
|---|---|---|
| 2159 — Invalid value for reverse charge applicable field | The request contains a value that does not meet the reverse-charge attribute’s current schema requirements. | Inspect the serialized request sent to the IRP. Compare the field’s type, spelling, case, null handling and permitted values with the current request JSON schema. |
| 2162 — Reverse charge is not applicable for this transaction | The payload marks reverse charge for a transaction type that the portal does not accept for that flag. The IRP guidance identifies transactions other than B2B as the listed case. | Recheck transaction type, buyer and supplier roles, counterparty status and whether this is the supplier-issued invoice that should be reported. |
The IRP troubleshooting guide describes these responses and points taxpayers to the request schema. The IRP validation rules contain broader checks. Do not keep toggling the reverse-charge field when the returned code identifies a different defect.
#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.
First decide whether the invoice belongs in e-invoicing
Supplier-side reporting and recipient-side liability are different
Reverse charge describes who pays GST; it does not automatically answer who must generate or report an e-invoice. The official GST E-Invoice System FAQ states: “If the invoice issued by notified person is in respect of supplies made by him but attracting reverse charge under Section 9(3), e-invoicing is applicable.” In that example, a notified firm of advocates supplies services to a company, and the company discharges the reverse-charge liability. The invoice is still the notified supplier’s invoice for its own supply.
Start by identifying the issuer named on the document. Confirm that the issuer is a person covered by the current e-invoicing notification, that the document is an invoice or other reportable document, and that the supply made by that issuer attracts section 9(3) reverse charge. The recipient’s obligation to pay tax is a separate analysis.
Cases that should not be treated as an automatic supplier e-invoice
The same FAQ distinguishes the supplier-invoice example from supplies received from an unregistered person and from imported services. Those cases may create a recipient’s reverse-charge accounting or reporting obligation, but they do not, by themselves, establish that the recipient must create a supplier e-invoice on behalf of the transaction. Check the current notification coverage and the actual supply before deciding.
Check the transaction classification before editing data
- Confirm the buyer’s GST registration status and the GSTIN used in the payload.
- Confirm that the supplier is the party issuing the document and making the supply.
- Confirm the document type and transaction category selected in the ERP or portal.
- Confirm that the section 9(3) treatment is supported by the relevant notification for the supply and date.
- Keep the tax calculation and accounting entry aligned with the legal classification; do not use the e-invoice flag to compensate for a wrong tax decision.
Prepare a clean diagnostic record
Before changing anything, save the rejected request and response. A useful record includes the invoice number and date, supplier and buyer GSTINs, document type, transaction classification, reverse-charge field as displayed to the user, reverse-charge field as serialized in JSON, the complete IRP error code and any correlation or submission reference.
Compare three versions of the same invoice:
- The source invoice or accounting entry approved by the business.
- The values shown on the ERP or e-invoice screen.
- The exact JSON request transmitted to the IRP.
Differences between the screen and the serialized payload are common causes of 2159. A screen may display a business label such as “Reverse charge,” while a connector sends an unsupported text value, an empty string, a wrong data type or a transformed value.
Rank #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 2159: invalid reverse-charge field value
1. Locate the transmitted attribute
Search the raw JSON for the reverse-charge applicability attribute named by your integration or schema version. Do not rely on a screenshot of the invoice form. Verify that the attribute is present where the current request schema expects it and that there is only one authoritative mapping.
2. Compare the value with the current schema
The schema, not a remembered value from an older integration, defines the accepted representation. Check:
- Whether the field expects a text, Boolean, code or another data type.
- The exact permitted values, including capitalization and spelling.
- Whether the field may be omitted, must be supplied, or rejects null and blank strings.
- Whether your connector converts a user-facing “yes/no” choice into the required API code.
- Whether an import, spreadsheet or middleware rule changes the value during serialization.
Do not invent a replacement value. Copy the permitted value from the current request JSON schema used by your IRP integration.
3. Trace ERP and middleware mappings
Check the mapping from the tax code or supply type in the ledger to the e-invoice field. A common failure is a generic reverse-charge tax code being mapped to every transaction, including transactions where the reverse-charge attribute should not be sent. Another is a three-state accounting value—yes, no, unknown—being flattened into a blank or unsupported string.
Review transformation logs at each boundary: accounting system to e-invoice module, e-invoice module to connector, and connector to IRP. If the UI shows the schema-compliant value but the request does not, the defect is in serialization or middleware rather than in the invoice screen.
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
4. Test a corrected payload without changing the tax substance
Correct only the representation that caused 2159. Preserve the invoice’s actual supplier, buyer, taxable values, tax rates and section 9(3) treatment. Submit through the authorised integration or portal after validating the complete JSON. A successful submission returns an Invoice Reference Number (IRN); save the accepted response and the final payload.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
5. If 2159 persists
- Capture the current schema version and the rejected JSON.
- Check for hidden whitespace, quotation marks, case conversion or a numeric value where text is required.
- Check whether a null value is being converted to an empty string.
- Confirm that the connector is using the current IRP endpoint and schema rather than a cached definition.
- Escalate with the full error response and a redacted payload, not only the invoice PDF.
Fixing error 2162: reverse charge is not applicable for this transaction
1. Recheck B2B classification
IRP guidance lists error 2162 when reverse charge is marked for a transaction other than B2B. Verify the transaction type in the payload, the buyer GSTIN and the counterparty’s registration status. An invoice incorrectly classified as B2C, export, non-GST or another category can trigger the response even when the accountant believes the supply is subject to reverse charge.
2. Confirm the parties’ roles
Ensure that the payload represents the notified supplier’s invoice for its own supply. A recipient’s self-accounting entry, an import-of-services record or a document relating to an unregistered supplier is not automatically the same as a supplier-issued B2B e-invoice. Correct the document workflow or classification rather than forcing the reverse-charge flag onto an unsupported transaction.
3. Check document type and supply details
Review whether the document is an invoice, credit note or another document type and whether the selected supply category matches the actual transaction. Verify place-of-supply and GSTIN fields as required by the current validation rules. If the transaction is not eligible for the reverse-charge attribute in that classification, remove or change the flag only after the tax treatment has been independently confirmed.
4. Reconcile the tax decision
Do not treat a portal acceptance as proof that the underlying tax classification is correct. Have the tax owner document why section 9(3) applies, who pays the tax, and why the supplier’s document is within the notified e-invoicing scope. If the classification is genuinely B2B and the supply is a notified supplier-side reverse-charge invoice, investigate the payload and integration rather than simply deleting the flag.
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
When the error is not really an RCM error
The validation service checks more than reverse charge. Read the returned code and repair the named field independently. Common unrelated checks include:
- Supplier or recipient GSTIN validity and relationship to the document.
- Item-level taxable values, tax rates and aggregated tax amounts.
- Document totals and rounding.
- Document number, date, type and duplicate registration.
- Mandatory fields for the selected transaction category.
Total-value validation needs transaction context
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 arbitrarily. Reconcile the payload to the approved invoice, the accounting entry and the current schema before changing a total.
A release note dated 1 February 2026 concerns relaxed validations for RSP-based calculations. It is not a general relaxation for reverse-charge invoices. Do not apply that change to an RCM rejection unless the current validation documentation expressly covers your field and transaction.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Check for an existing IRN before retrying
Repeated submissions can create a duplicate-registration response when the original request already succeeded or partially completed. Search your IRP records and internal logs using the supplier GSTIN, document number, document date and submission reference. The IRP FAQ describes the IRN as the unique reference returned after validation.
If an IRN exists, reconcile the accepted payload with your ledger and GSTR-1 data instead of submitting a second invoice. The official FAQ says that, after successful reporting, invoice data including the IRN is saved in the GST System and can flow into the supplier’s GSTR-1. If it is missing or inconsistent, use the return system’s discrepancy process and retain evidence of the accepted IRP response.
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
GSTN states that IRN generation on the listed portals is free. A fee claim from an intermediary is therefore not a prerequisite for obtaining an IRN, although businesses may separately pay for software or implementation services.
What to do when the invoice was accepted but is wrong
Preserve the original evidence
Save the accepted JSON, IRN, signed response, invoice copy, accounting entry and any GSTR-1 transmission record. Record exactly what is wrong: reverse-charge classification, buyer details, taxable amount, tax amount, document number or another field. This evidence is essential for deciding whether correction is possible and for explaining the change in an audit.
Cancellation is time-limited
The GST E-Invoice System FAQ describes cancellation within 24 hours of generation and says that e-invoices are not amended in place. Treat the 24-hour period as the FAQ’s stated procedure, not an unconditional promise that every document can be cancelled in every circumstance. Confirm the current portal rule, document type and whether the invoice has already been used in a return or downstream document.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, 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 minuteAfter the cancellation window
The FAQ describes return-level correction, including a credit note where the cancellation window has passed. The correct route depends on the document, the nature of the error and the applicable GST procedure. Do not overwrite the original IRN or silently edit the accounting record. For a material tax or reporting exposure, obtain advice from a qualified GST professional before issuing a credit note, replacement document or return adjustment.
A practical end-to-end workflow
- Classify the supply. Establish whether the notified supplier’s own section 9(3) supply and document fall within current e-invoicing coverage.
- Read the exact IRP response. Separate 2159, 2162, duplicate responses and unrelated validation codes.
- Inspect the raw payload. Compare the serialized reverse-charge field, transaction type, GSTINs and totals with the approved invoice.
- Repair the smallest valid unit. Fix representation for 2159; fix transaction classification or party roles for 2162; fix other fields only when their codes identify them.
- Validate before resubmission. Use the current schema and validation rules, and retain the pre-submission and post-submission payloads.
- Verify the result. Record the IRN, check that the accepted data reaches the GST System and reconcile the supplier’s GSTR-1.
- Handle an accepted error under the correction procedure. Check the current cancellation window and return-level route before taking action.
Controls that prevent repeat failures
- Version-control the request schema and connector mappings.
- Use separate accounting codes for supplier-side section 9(3) invoices, recipient self-accounting and imports.
- Reject blank or unmapped reverse-charge values before the payload leaves the ERP.
- Run a B2B and GSTIN consistency check whenever reverse charge is selected.
- Log the exact JSON and IRP response for every submission.
- Reconcile IRNs to invoice registers and GSTR-1 on a defined schedule.
- Review portal release notes before changing validation logic.
The fastest reliable fix is not a blind field toggle. Establish that the invoice is in scope, identify whether the failure is a value-format problem (2159) or a transaction-classification problem (2162), then correct the transmitted payload and preserve the resulting IRN trail.
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.
