Report the guarantee event using the correct party and clock
Guarantees within the Foreign Exchange Management (Guarantees) Regulations, 2026 are reported to an authorised dealer bank quarterly, within 15 calendar days after quarter-end, by the person assigned the obligation under regulation 7. The AD bank has a separate 30-calendar-day quarter-end deadline for onward reporting. A customer cannot treat the bank’s later deadline as its own.
Determine coverage before choosing a form
FEMA 8(R)/2026-RB is dated 6 January 2026 and commences on Gazette publication. It covers the specified guarantee arrangements involving a resident party and a non-resident party, subject to its exemptions and permissions. Regulation 4 excludes, among other specified cases, guarantees given in accordance with the Overseas Investment Regulations, 2022. Do not put every overseas guarantee into GRN without first checking which framework applies. Sources were checked on 22 October 2026.
Regulation 5 tests the underlying transaction and, subject to its stated exceptions, the surety’s and principal debtor’s eligibility to lend and borrow from each other under the Borrowing and Lending Regulations. Regulation 6 addresses a resident creditor obtaining a guarantee in the specified circumstances. Reporting is separate from this permissibility analysis: a timely GRN does not cure a prohibited underlying arrangement, and paying a late fee does not create substantive permission.
Regulation 7 assigns reporting first by the resident surety in the stated case, then by the principal debtor who arranged the guarantee where the surety is non-resident, or by the creditor in the specified remaining/arranged cases. Prepare a party-and-residency matrix and record who arranged the guarantee. Where the facts create an overlap or uncertainty, resolve the responsible reporting party with the AD using the actual regulation rather than omitting the report or duplicating it without explanation.
Use the three GRN event files and retain the transaction number
The RBI Circular 01 dated 1 April 2026 identifies Form GRN Issue for issuance, Form GRN Modification for subsequent changes in amount, period extension or pre-closure, and Form GRN Invocation for invocation. The AD submits through CIMS and provides a unique Guarantee Transaction Number for each issuance before submitting it to RBI. Carry that identifier into the connected event trail so the issue, later change and invocation do not become unrelated records.
Keep issuance date, original amount/currency, changes, invocation date and liability created toward the surety separate. A guarantee’s face amount is not necessarily the amount invoked. A modification without a cash flow is still a reportable event within regulation 7; absence of a flow affects the late-fee base as clarified below, not whether a covered modification should be reported.
Apply the April clarification before calculating a late fee
Regulation 8 prescribes ₹7,500 + 0.025% × A × n, rounded upward to the nearest ₹100. The regulation describes n as the years of delay, rounded upward to the nearest month and expressed to two decimals; A is the relevant INR amount. Use 0.00025 as the decimal multiplier for 0.025%, and round the resulting total upward rather than to the nearest hundred.
Circular 01 makes the amount base event-specific. For delayed GRN Issue and GRN Modification, A is nil because those returns do not capture flows. For delayed GRN Invocation, A is the liability created toward the surety on invocation. Consequently a large face-value guarantee does not by itself produce an ad valorem late fee for its issue report. Equally, a delayed invocation should not be calculated with A nil merely because the original issue report was a non-flow event.
The examples below assume the applicable delay parameter has been correctly determined and accepted, except the separate deadline arithmetic case. They illustrate the statutory formula, not a substitute for the AD/RBI’s actual fee assessment, currency-conversion basis or examination of other contraventions. Retain receipt of submission and actual payment/closure evidence; an internal fee estimate is not proof that delayed reporting has been regularised.
Worked illustrations
The following cases use fictional figures and stated assumptions. Amounts are Indian rupees unless a different unit is expressly shown. They illustrate preparation controls and do not represent real client results.
Illustrative example 1: the customer and AD have different quarter-end dates
For a covered event in the quarter ending 30 September 2026, ordinary addition of 15 calendar days gives the customer’s date of 15 October 2026. Addition of 30 calendar days gives the AD’s onward date of 30 October 2026. A customer submission on 20 October is five calendar days beyond its stated date; it does not become timely because 30 October has not arrived. No specific extension is assumed.
Illustrative example 2: a late issue report has a nil amount base
Assume a ₹10 crore face-value guarantee and a delayed GRN Issue report. Under Circular 01, A = 0 for this report. With a valid applicable delay parameter, the formula gives ₹7,500 + 0.00025 × 0 × n = ₹7,500. The face amount is not substituted for A merely because the guarantee is large.
Illustrative example 3: an amount modification is still a non-flow report
Assume a covered guarantee increases from ₹4 crore to ₹6 crore, an increase of ₹2 crore, and the GRN Modification report is late. The circular nevertheless specifies A = nil for delayed Modification. The formula result remains ₹7,500, not a calculation using ₹6 crore or the ₹2 crore increase. The change itself still needs reporting.
Illustrative example 4: an invocation requires upward hundred rounding
Assume the liability created toward the surety on invocation is ₹1,00,00,000 and the correctly determined n is 0.25 years. The variable component is ₹1,00,00,000 × 0.00025 × 0.25 = ₹625. Total before final rounding is ₹8,125; rounding upward to the nearest ₹100 gives ₹8,200. Ordinary nearest-hundred rounding would give the wrong result.
Illustrative example 5: a one-year delay on the invocation liability
Assume invocation creates liability ₹2,40,00,000 toward the surety and n = 1.00. The variable component is ₹6,000 and total is ₹13,500. It is already an exact multiple of ₹100, so upward rounding leaves ₹13,500 unchanged. The example assumes the full stated amount is the appropriate INR liability base.
Illustrative example 6: partial invocation is not the face amount
A guarantee has face amount ₹10 crore but the particular invocation creates liability ₹2 crore toward the surety. With correctly determined n = 0.50, A is ₹2 crore for this invocation working: ₹7,500 + ₹2,00,00,000 × 0.00025 × 0.50 = ₹10,000. Substituting the ₹10 crore face amount would instead produce ₹20,000, which is not the stated circular-based amount base for these facts.
Ten-step verification table
| Step | Verification | Evidence to retain |
|---|---|---|
| 1 | Check the governing guarantee framework and exemptions. | Coverage and OI/non-OI analysis. |
| 2 | Identify surety, debtor, creditor and residency. | Party matrix and underlying agreement. |
| 3 | Verify the substantive permission conditions. | Underlying-transaction and lending/borrowing review. |
| 4 | Assign the reporting obligation under regulation 7. | Responsible-party and arranger record. |
| 5 | Classify issuance, modification or invocation. | Event dates and GRN file selection. |
| 6 | Retain the Guarantee Transaction Number. | AD-issued identifier and connected event trail. |
| 7 | Calculate the customer’s quarter-end plus 15-day deadline. | Calendar and submission receipt. |
| 8 | Track the separate AD reporting status. | Onward submission evidence where available. |
| 9 | For delay, apply the event-specific A and supported n. | Circular 01 base, delay and upward-rounding working. |
| 10 | Retain actual regularisation and payment evidence. | Fee advice, payment and reporting closure records. |
Sixteen practitioner FAQs
1. Does every cross-border guarantee use the same framework?
No. Check regulation 4 exemptions, including guarantees given in accordance with the Overseas Investment Regulations.
2. Who must report a resident surety’s covered guarantee?
Apply regulation 7(1), which assigns reporting to the resident surety in that stated case.
3. Why record who arranged the guarantee?
That fact matters in the other reporting-party cases under regulation 7.
4. Is timely reporting sufficient to make a guarantee permissible?
No. The underlying arrangement and substantive permission conditions must independently be satisfied.
5. Which file reports the initial issue?
Circular 01 identifies Form GRN Issue.
6. Which file records extension or pre-closure?
Form GRN Modification addresses the specified subsequent changes, including period extension and pre-closure.
7. Does invocation need its own event report?
Yes. The circular identifies Form GRN Invocation.
8. What links the reports together?
Retain the unique Guarantee Transaction Number supplied by the AD for issuance and its connected event references.
9. Is the customer deadline 30 days after quarter-end?
No. The customer’s stated reporting deadline is 15 calendar days; the AD’s onward deadline is 30 calendar days.
10. Are these working-day deadlines?
The regulation expressly uses calendar days.
11. Does a no-flow modification escape reporting?
No. The reporting requirement and the nil late-fee amount base are separate matters.
12. What A is used for a delayed Issue report?
Circular 01 specifies nil for delayed GRN Issue.
13. What A is used for a delayed Modification report?
The same circular specifies nil for delayed GRN Modification, including the stated amount-change context.
14. What A is used for delayed Invocation?
Use the liability created toward the surety on invocation, as clarified by Circular 01.
15. How is the calculated total rounded?
Upward to the nearest ₹100; do not use ordinary nearest-hundred rounding.
16. Does the calculated late fee settle other breaches?
No. It addresses the specified reporting delay; other substantive contraventions and actual regularisation require separate examination.
Organising the supporting working
Keep the underlying records, calculation and conclusion linked to the same entity and period. When organising work with assurePractice and the assureOffice tools, retain these supporting schedules alongside the final output and use only the features confirmed for the version available to you.
Conclusion
A sound guarantee file separates permission, reporting responsibility, event type and deadline. For delayed reports, choose A from the current event-specific clarification before applying the formula and retaining actual regularisation evidence.