Keep the payment event and GST invoice distinct.

Use the Razorpay companion when the required India payment flow and objects are confirmed as supported for the intended case. Start with the actual source record, people and exception rather than a polished demonstration. The right fit should keep the amount, authority, current state and next action understandable when a normal input changes or a required detail is missing. Confirm the applicable plan and configuration before treating the example as your operating design.

The page does not claim every Razorpay method, settlement behavior, region or tax workflow, and it does not provide tax advice. A page title does not extend the documented product scope or decide a legal, tax, financial or contractual conclusion. Keep the responsible delivery, payment, books and professional-review processes in their established systems, and verify any material assumption before it changes an invoice, customer balance or published commitment.

Test a successful event, failed event, fee difference, incomplete reference and partial customer payment. Use a controlled billing record without real customer data and include one changed term, missing reference, partial amount or delayed decision. Ask a second reviewer to identify the current owner and next action without verbal guidance. Record any required integration, permission and plan limit as a pass-or-fail condition rather than assuming it from a general feature label.

Razorpay owns the payment event, Invoicera owns the invoice and allocation, and the responsible tax and finance processes retain their conclusions. Name the object, direction, trigger, failure owner and authoritative system before implementation. A familiar vendor logo or exported file does not prove that every field or state is supported. Reconcile one small controlled batch first, retain the source evidence and keep ambiguous records open until a responsible reviewer resolves them.

Use current official product information, a controlled workflow review and attributable customer evidence where available. Do not substitute invented outcomes, generic badges or an unverified screenshot for proof. Record the evaluation date, assumptions, required plan, limitations and decision owner so another reviewer can reproduce why the product path was accepted.