PC 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 & 11Crashes, 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 minuteiTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Reverse-charge e-invoice errors usually have two separate causes: the invoice may not be within the supplier-side e-invoicing requirement, or the submitted payload may contain an invalid reverse-charge value or transaction classification. Start by confirming that a notified supplier is issuing an invoice for its own supply attracting reverse charge under section 9(3), then validate the transaction type and serialized JSON sent to the Invoice Registration Portal (IRP).
Error 2159 means the reverse-charge applicability field contains an invalid value. Error 2162 means reverse charge was marked for a transaction type the portal does not accept, including the non-B2B case identified in IRP guidance. The practical fixes are to correct the scope decision, repair the ERP-to-IRP mapping, and check the complete payload rather than repeatedly toggling a field on the invoice screen.
This guide reflects IRP material available on 13 October 2026. GST notifications, schemas, validation behavior and correction procedures can change, so verify the live rule and portal instruction before taking a tax or reporting action.
Quick diagnosis of the two RCM errors
| IRP response | What it indicates | First checks |
|---|---|---|
| 2159 — Invalid value for reverse charge applicable field | The request contains an invalid value for the reverse-charge applicability attribute. | Inspect the serialized payload; compare the field’s type and permitted value with the current request JSON schema; check ERP mapping, casing, blank or null handling, and transformations between the user interface and API. |
| 2162 — Reverse charge is not applicable for this transaction | The request marks reverse charge for a transaction type that the portal does not accept for this flag. IRP guidance identifies the listed case as a transaction other than B2B. | Recheck transaction classification, document type, counterparty status, supplier and buyer roles, and whether the document is the supplier-issued invoice that should be reported. |
Use the exact code returned by the portal. If the response names a GSTIN, item-tax, total-value or another field, troubleshoot that field separately instead of assuming every rejection is an RCM problem. The IRP troubleshooting page lists common responses at https://einvoice6.gst.gov.in/content/kb/troubleshooting-common-errors/, and the current validation material is at https://einvoice6.gst.gov.in/content/validation-rules/.
#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
Do not begin by changing the reverse-charge flag. E-invoicing and reverse-charge tax payment are related but different questions. The relevant question is whose invoice is being reported, who made the supply, and whether that supplier is covered by the current notification.
Notified supplier making its own section 9(3) supply
The 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.” Its example is a notified firm of advocates supplying services to a company that pays the reverse-charge liability. In that fact pattern, the notified supplier issues its own invoice and reports the document to the IRP, even though the recipient discharges the tax.
That statement is not a blanket rule for every payment made under reverse charge. Check all three elements:
Recommended Free Tools
- The supplier is a person covered by the e-invoicing notification in force for the relevant period.
- The document is an invoice for a supply made by that supplier, rather than a recipient-created record or an internal accounting entry.
- The supply attracts reverse charge under section 9(3), and the transaction details support the classification being sent to the portal.
Recipient-side liability does not automatically create a supplier e-invoice
A recipient may be responsible for paying RCM without that fact alone proving that a supplier-side e-invoice must be generated. Separate the recipient’s tax-payment obligation from the supplier’s reporting obligation. The supplier, buyer, registration status, document type and applicable notification all matter.
Unregistered-supplier and import cases
The FAQ distinguishes the notified-supplier example from supplies received from an unregistered person and from imported services. It says e-invoicing does not arise in the described cases where the supply is received from an unregistered person or through import of services. Apply the current notification and the actual facts before relying on that distinction: a recipient’s RCM accounting entry is not automatically a supplier-issued e-invoice.
Why this scope check prevents false fixes
If an invoice is outside the e-invoicing requirement, forcing an RCM value into an e-invoice payload can create a classification error that no field edit will cure. If it is in scope, omitting or misrepresenting the field can produce a rejection or an inaccurate downstream return record. Record the scope decision with the supplier’s notification status, document type, supply category and counterparty status before changing the ERP mapping.
What happens after a successful report
GSTN describes e-invoicing as reporting specified GST document details to a notified Invoice Registration Portal and receiving an Invoice Reference Number (IRN). The IRN is the unique reference returned after portal validation. The GST E-Invoice System FAQ says that, on successful reporting, the invoice payload including the IRN is saved in the GST System.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
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
The same process can make the invoice data available for the supplier’s GSTR-1. If the document is absent or inconsistent in the return, check the return data and follow the system’s discrepancy or correction process; an IRN alone is not a reason to ignore a separate GSTR-1 mismatch.
GSTN states that IRN generation on its listed portals is free. That does not remove the need for a correct ERP payload, valid credentials, notification coverage and reconciliation controls.
Error 2159: “Invalid value for reverse charge applicable field”
Error 2159 is a payload-value problem. The IRP has received the reverse-charge applicability attribute, but the value does not conform to the current request schema. The error does not by itself prove that reverse charge is legally inapplicable; it says that the submitted representation is not valid for that field.
Common causes
- Wrong data type: the ERP sends a number, Boolean, label or other type where the schema requires a different representation.
- Unsupported text: a user-facing term such as a long description, local-language label or internal code is passed through instead of the API value.
- Casing or whitespace: a value that looks correct on screen is serialized with different capitalization, trailing spaces or hidden characters.
- Blank and null conversion: an empty UI selection becomes an empty string, null, a default value or an inherited value in the outbound JSON.
- Transformation between systems: the invoice application, middleware and IRP connector apply different mappings, so the value shown to the operator is not the value transmitted.
- Stale schema or connector logic: a validator or integration was built against an older request definition and still emits a value no longer accepted by the live portal.
Fix 2159 step by step
- Save the complete response. Record the error code, message, document number, timestamp and connector log. Do not discard the failed payload.
- Capture the serialized request. Inspect the exact JSON sent over the API, not only the invoice form. Identify the reverse-charge applicability property, its value, its JSON type and whether it is present once or more than once after transformation.
- Check the current schema. Compare the property name, allowed value and data type with the live request JSON schema referenced by the IRP guidance. Do not infer permitted values from a different portal, an old integration document or a screen label.
- Trace the mapping. Follow the value from the tax determination rule through the invoice table, export routine, middleware and final API request. Look for internal codes, Boolean-to-text conversions, trimming failures and hard-coded defaults.
- Resolve an empty selection deliberately. If the transaction is not reverse charge, the system should produce the representation required for a non-RCM transaction under the current schema; it should not silently send a blank or null value. If the transaction is RCM, ensure the legal classification is selected before serialization.
- Regenerate the payload. Correct the mapping or transaction master data, recreate the JSON and validate it locally against the current schema where your integration supports that check.
- Submit once and retain the result. Keep the corrected request and response with the invoice audit record. Repeated submissions without checking the response can create a duplicate-registration issue.
Do not “fix” 2159 by changing the tax amount, rate or invoice total unless another error specifically identifies those values. This code concerns the representation of the reverse-charge field.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsError 2162: “Reverse Charge is not applicable for this transaction”
Error 2162 is a classification conflict. The request asserts reverse charge, but the transaction type does not permit that flag in the portal’s validation. IRP material identifies the listed failure as marking reverse charge for a transaction other than B2B.
Checks to perform before retrying
- Confirm B2B classification. Verify that the document is classified as B2B in the payload and that the buyer’s GSTIN and registration status support that classification.
- Check the counterparty roles. Ensure the supplier GSTIN belongs to the entity issuing the invoice and the recipient details belong to the buyer. A reversed or substituted party can turn a valid-looking invoice into a prohibited transaction type.
- Review document type. Confirm that the document is an invoice eligible for the intended reporting route, not a record that should be handled as a credit note, debit note, receipt voucher or another document category.
- Verify the supply facts. Check whether the supply actually falls under the relevant reverse-charge provision and whether the supplier is the party issuing the document.
- Check transaction flags together. Export, SEZ, deemed export, e-commerce and other transaction attributes may alter validation. Correct the underlying classification rather than toggling only the RCM field.
Two legitimate outcomes
If the invoice is a notified supplier’s B2B invoice for its own section 9(3) supply, correct the B2B and related party fields so the reverse-charge assertion describes the actual transaction. If it is not a qualifying B2B supplier invoice, remove the inappropriate e-invoice submission or correct the document workflow according to the applicable GST procedure. Do not force a B2B value merely to make the portal accept an RCM flag.
Why changing one checkbox can make the record worse
The portal validates a set of related fields. Altering the RCM flag while leaving an incorrect buyer GSTIN, document type or transaction category may replace 2162 with a different rejection or produce a record that does not match the books. Make the classification decision first, then regenerate all dependent fields.
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
Other validation failures that can appear with an RCM invoice
The validation page covers broader payload checks. An RCM error may coexist with, or be mistaken for, another defect.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Supplier and recipient GSTINs
Check the supplier GSTIN, recipient GSTIN, state information and registration status independently. A malformed, inactive or incorrectly mapped GSTIN can cause a rejection even when the reverse-charge value is valid. Confirm that the GSTIN in the payload belongs to the entity whose invoice is being reported and that the buyer classification is consistent with the document.
Item-level tax aggregation
Reconcile each line’s taxable value, rate, tax amounts and exempt or non-taxable treatment to the invoice totals. The portal may validate item-level aggregation separately from the RCM field. A correct reverse-charge classification cannot compensate for line-level totals that do not add up.
Total-value treatment for RCM and export-with-payment transactions
An older IRIS explanatory article notes that, for reverse-charge and export-with-payment transactions, the total item value may match with or without tax values according to business requirements. Treat that as a validation note, not permission to alter amounts casually. Reconcile the payload to the issued invoice and apply the current schema and validation behavior for the document. If the portal returns a total-value error, preserve the original calculation, identify which total the message names and obtain tax advice when the treatment affects liability or reporting.
Duplicate or already registered requests
The troubleshooting guidance warns about duplicate registration cases. Before retrying an invoice that failed after a timeout, check whether an IRN already exists for the document. The FAQ describes the IRN as the unique reference returned after successful portal validation. Search the portal or your integration log using the document identifiers and preserve any returned IRN before sending another request.
Release-specific validation changes
An IRP release note dated 1 February 2026 discusses relaxed validations for RSP-based calculations. That change is not a general relaxation for reverse-charge invoices. Do not use it as a reason to bypass the RCM field, transaction classification or total reconciliation.
A complete troubleshooting workflow for finance and ERP teams
- Freeze the evidence. Save the invoice PDF or source record, outbound JSON, response JSON, error code, connector log, timestamp and operator notes.
- Identify the reporting party. Write down the supplier issuing the invoice, recipient, supplier notification status, document type and supply category.
- Make the scope decision. Determine whether this is a notified supplier’s own section 9(3) supply, a recipient-side RCM entry, a supply from an unregistered person or an import of services.
- Read the exact response. Use 2159 for a reverse-charge field representation issue, 2162 for the transaction-type conflict, and the named code for any unrelated defect.
- Inspect raw JSON. Compare the transmitted field names, values and types with the current request schema. Do not rely on the display screen.
- Validate B2B and roles. Confirm buyer GSTIN, supplier GSTIN, document type and the B2B condition identified in the 2162 guidance.
- Reconcile amounts. Check item taxable values, tax aggregation and totals. Apply the transaction-specific treatment required by the current validation rules.
- Correct the source mapping. Fix the tax rule, master data, transformation or connector rather than editing only a single generated JSON value if the defect will recur.
- Regenerate and submit once. Create a fresh payload, run available schema validation and submit it with a controlled retry process.
- Confirm the result. Store the IRN and response, verify that the invoice appears as expected in the GST system and reconcile the resulting data to GSTR-1.
For recurring failures, have the ERP or integration owner produce a field-level mapping document showing the source column, transformation rule, final JSON property, data type and test case. That document makes a 2159 or 2162 incident reproducible instead of dependent on one operator’s memory.
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
What to do when an e-invoice is already wrong
An accepted IRN is not normally edited 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 cases where the cancellation window has passed. The FAQ content used for that procedure was originally published in 2022, so treat the 24-hour figure and the available correction path as a procedure to verify against current GST guidance and portal behavior, not as an exception-free guarantee for every document.
- Preserve the original. Retain the issued invoice, original payload, IRN, response, accounting entry and tax determination.
- Check the time and document status. Establish when the IRN was generated, whether cancellation is still available and whether the document has already been used in a return or downstream process.
- Determine the correction mechanism. Follow the current portal and GST procedure for cancellation, replacement documentation, credit note or return correction as applicable to the facts.
- Reconcile all systems. Update the ERP, tax ledger, customer communication, GSTR-1 data and any recipient-facing record consistently.
- Escalate material exposure. Consult a qualified GST professional when the error changes tax liability, period, recipient credit, document identity or the validity of a filed return.
Never cancel and recreate an invoice solely to clear an error message without first confirming whether an IRN was already generated and whether the correction is legally permitted.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Controls that prevent repeat RCM errors
Maintain a notification and scope matrix
Keep a dated matrix of supplier categories covered by e-invoicing, document types, section 9(3) supply categories and exceptions relevant to your business. Link each tax rule to the party issuing the invoice so a recipient-side RCM entry is not mistaken for a supplier e-invoice.
Separate display labels from API values
Use a controlled mapping table for every enumerated field. Store the API value separately from the operator-facing description, validate the data type before serialization and reject unknown, blank or stale values before the request reaches the IRP.
Test the complete payload
Test combinations of B2B status, RCM applicability, document type, GSTIN, export or SEZ flags and line-level tax values. A unit test that checks only the RCM checkbox will not catch a buyer-role or document-classification error that produces 2162.
Use idempotent retries
When a network timeout occurs, query for an existing IRN before resubmitting. Store the document key and returned IRN together so the integration can distinguish a failed request from an accepted request whose response was lost.
Reconcile after registration
Compare the accepted payload and IRN with the ERP invoice and the supplier’s GSTR-1 data. Investigate omissions or inconsistencies promptly instead of assuming that successful portal acceptance guarantees every downstream record is correct.
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
Monitor schema and release changes
Assign an owner to review current IRP validation rules, request schema changes and release notes. The February 2026 note about RSP-based calculations illustrates why a change affecting one validation area should not be generalized to RCM fields.
Frequently asked questions
Does error 2159 tell me that reverse charge is legally wrong?
No. It specifically identifies an invalid representation of the reverse-charge applicability field in the submitted request. The legal classification still needs to be established from the transaction facts, but the immediate technical check is the serialized value and its schema definition.
Can a recipient generate the supplier’s e-invoice because the recipient pays RCM?
Not automatically. The cited FAQ’s e-invoicing example is a notified supplier reporting an invoice for its own supply. A recipient’s liability to pay tax does not, by itself, convert the recipient’s accounting record into that supplier-issued e-invoice.
Free tools Windows power users keep installed
One-click scans. No signup required.
Is an IRN the same thing as a GSTR-1 filing?
No. The IRN confirms successful reporting and supplies data to the GST system, where it can flow into the supplier’s GSTR-1. Return data should still be checked and reconciled.
Should I keep submitting the same payload after a timeout?
No. First determine whether the portal registered the invoice and returned an IRN. Uncontrolled retries can trigger duplicate-registration handling and complicate the audit trail.
Can I rely on the 24-hour cancellation period for every incorrect invoice?
Use it as the procedure described in the FAQ, then verify the current rule, document type, timing and portal status. Where cancellation is unavailable, the appropriate return-level or credit-note treatment depends on the facts and should be confirmed before posting a correction.
Frequently Asked Questions
What is the fastest first check for an RCM e-invoice rejection?
Read the exact IRP code, confirm whether the invoice is a notified supplier’s own section 9(3) supply, and inspect the raw JSON value sent for the reverse-charge field.
Which error usually points to an invalid field value?
Error 2159: “Invalid value for reverse charge applicable field.” Compare the transmitted type and value with the current request JSON schema.
Which error points to a transaction-classification conflict?
Error 2162: “Reverse charge is not applicable for this transaction.” Recheck B2B status, document type and the supplier and buyer roles before retrying.
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.
