For an in-scope foreign-currency advance that creates a non-monetary asset or liability, Appendix B of Ind AS 21 fixes the relevant transaction date at initial recognition of that advance. Multiple advances require separate dates. Do not translate an entire later invoice at one delivery-date rate and thereby overwrite the advance layers. The controlling guidance is Ind AS 21, Appendix B, paragraphs 4–9, and the core monetary-item provisions.
Decide whether the advance is actually non-monetary
Appendix B applies only where advance consideration creates a non-monetary asset or liability before recognition of the related asset, expense or income. A prepayment for specified goods can differ from a refundable cash deposit. A label such as supplier advance is not the analysis: establish whether the right is to goods/services or a fixed or determinable number of currency units. The examples assume contractual non-monetary advances except where expressly identified as monetary.
The Appendix excludes initial measurements at fair value, and the specified cases measured using fair value of consideration at another date; it need not be applied to income taxes or the specified insurance contracts. Its effective date is annual periods beginning on or after 1 April 2018. The official compendium also incorporates the 2025 lack-of-exchangeability amendment. All rates below are fictional, observable spot-rate inputs in exchangeable currencies; no example estimates a blocked currency rate or applies hedge accounting.
Build the invoice from rate layers
Create one schedule per contract showing foreign-currency amount, recognition date, spot rate, functional-currency carrying amount and later allocation. Each advance retains its own historical layer for the related asset, expense or income when that advance is derecognised. The unadvanced part follows its own transaction-date recognition under the relevant standard. Appendix B determines the exchange-rate date; it does not independently determine when inventory, an asset or revenue is recognised.
If consideration remains unpaid after recognition, identify the monetary payable separately. Its closing-rate translation and subsequent settlement differences are not a reason to rewrite the advance-based historical asset cost. Similarly, cash received in advance may leave a non-monetary contract liability while the foreign-currency bank account remains monetary. The two balances can therefore have different subsequent exchange treatment.
Controls for delivery, partial use and closing
Tie the sum of advance derecognition and newly recognised payable or receivable to the related recognised transaction. Where part of an advance is consumed, use a supported contractual allocation and preserve the unused layer. Do not invent a universal FIFO or weighted-average method for unrelated contracts. Test the nature of any refundable right separately if contractual terms change; a conversion from a goods right to a cash claim needs its own assessment at that date.
Keep tax bases, import duties, recoverable taxes, financing components, hedge accounting and fair-value effects in separate supported workings. The examples isolate currency mechanics, assume INR functional currency and ignore those other components. Rates are INR per USD. Figures are rounded only at the stated rupee result; historical layers and monetary closing adjustments should reconcile to the general ledger without hiding exchange differences inside the supplier-advance account.
Six worked illustrations
All facts and amounts below are fictional. Assumptions describe the model, not additional statutory rules.
Illustrative example 1: Full non-monetary advance for goods
USD 10,000 is paid and initially recognised as a qualifying non-monetary advance at ₹82 per USD. The advance carrying amount is ₹8,20,000. Goods are recognised later when the spot rate is ₹85. For this fully advanced component, cost remains ₹8,20,000; translating it at ₹85 would produce ₹8,50,000 and overstate that component by ₹30,000. Other cost elements are outside this example.
Illustrative example 2: Partial advance and an unpaid balance
Goods consideration is USD 10,000. A USD 4,000 qualifying advance is recognised at ₹82, giving ₹3,28,000. At goods recognition, the remaining USD 6,000 payable uses the assumed spot rate ₹85, giving ₹5,10,000. Total isolated purchase cost is ₹8,38,000. Recasting the whole USD 10,000 at ₹85 would overstate it by ₹12,000.
Illustrative example 3: Two advance tranches
An asset is fully advanced through USD 3,000 at ₹81 and USD 7,000 at ₹83. Separate historical amounts are ₹2,43,000 and ₹5,81,000, totalling ₹8,24,000. An invoice-date rate of ₹84 does not replace those two layers; USD 10,000 at ₹84 would be ₹8,40,000, a ₹16,000 difference.
Illustrative example 4: Separate closing translation of the payable
Use the USD 6,000 payable initially recognised at ₹85 in example 2. It remains outstanding at year-end when the closing rate is ₹86. The monetary payable becomes ₹5,16,000 and the isolated exchange loss is ₹6,000, assuming ordinary profit-or-loss treatment. The ₹8,38,000 historical purchase-cost working is not retranslated merely because this payable changed.
Illustrative example 5: Advance receipts and later revenue
A customer pays USD 2,000 at ₹80 and USD 3,000 at ₹82, each creating a qualifying non-monetary contract liability. Historical layers total ₹1,60,000 + ₹2,46,000 = ₹4,06,000. When all the related revenue is appropriately recognised, these layers supply the currency translation for the fully advanced component. A later ₹84 rate would give ₹4,20,000 and incorrectly increase that component by ₹14,000.
Illustrative example 6: Refundable monetary deposit boundary
A distinct USD 5,000 deposit is contractually refundable in that fixed currency amount and is established to be monetary. Initial rate ₹82 gives ₹4,10,000; closing rate ₹84 gives ₹4,20,000, an isolated ₹10,000 exchange gain for the holder under the assumed ordinary treatment. It does not qualify for Appendix B’s non-monetary-advance treatment merely because an accounts ledger calls it an advance.
Ten-step verification table
| Step | Action | Evidence |
|---|---|---|
| 1 | Confirm the reporting framework | Ind AS applicability, functional currency and transaction scope. |
| 2 | Read contract rights | Goods/services entitlement versus fixed-currency refund evidence. |
| 3 | Check Appendix B exclusions | Fair-value measurement, taxes, insurance and other relevant scope decisions. |
| 4 | Identify each advance recognition date | Contract, bank evidence and ledger entry for every tranche. |
| 5 | Support the spot rates | Dated rate source and INR-per-foreign-unit convention. |
| 6 | Preserve historical layers | Foreign units, rate and functional-currency carrying amount by tranche. |
| 7 | Allocate to the recognised transaction | Supported delivery/performance allocation and advance derecognition. |
| 8 | Identify the unpaid monetary balance | Payable or receivable separately reconciled at initial recognition. |
| 9 | Perform closing and settlement translation | Closing rates and exchange differences without rewriting historical layers. |
| 10 | Tie the final financial statements | Contract schedule, ledger, tax/other cost workings and disclosure review. |
Sixteen practitioner FAQs
1. Does Appendix B apply to every supplier advance?
No. Establish that a non-monetary asset or liability arises before recognising the related item.
2. What date governs an in-scope advance component?
The date the non-monetary advance asset or liability is initially recognised.
3. Can multiple advances use one invoice-date rate?
The Appendix requires a date for each advance payment or receipt.
4. Does delivery reset all historical layers?
No. Preserve the in-scope advance component’s transaction-date rate.
5. What about the unpaid part of an invoice?
It needs its own initial recognition and monetary-balance analysis.
6. Does the whole invoice become non-monetary because part was advanced?
No. Separate the historical advance layer from an unpaid monetary payable or receivable.
7. Is a fixed-currency refundable deposit automatically protected from retranslation?
No. Such rights can be monetary and require the applicable closing translation.
8. Can management rely only on the ledger account name?
No. Contractual rights and obligations determine the classification.
9. Does this guidance create revenue on receipt of cash?
No. Recognition of revenue follows the relevant standard; Appendix B addresses the exchange-rate date.
10. Are advance receipts covered as well as payments?
Yes, where they create the in-scope non-monetary liability before related income recognition.
11. Does a historical contract liability freeze the foreign-currency bank balance?
No. Cash is monetary and requires its own subsequent exchange treatment.
12. Do fair-value transactions always follow these examples?
No. Appendix B has specific fair-value scope exclusions.
13. Must this Appendix be applied to income taxes?
Its paragraph 6 states that application is not required for income taxes and specified insurance contracts.
14. Are the rates in the examples current market quotations?
No. They are expressly fictional spot-rate inputs for demonstrating the calculation.
15. What if the currency cannot be exchanged normally?
Apply the amended exchangeability requirements and estimation/disclosure analysis separately; this article assumes exchangeability.
16. What evidence should survive year-end closing?
Contract classification, advance dates and rates, layer allocation, monetary balance reconciliation and supported exchange differences.
Conclusion
Apply Appendix B of Ind AS 21 to non-monetary advances, retain a rate for each tranche, and separately translate and settle the unpaid monetary balance.