How Foreign Currency Standards (ASC 830/IFRS 21) Intersect with Revenue Recognition Standards (ASC 606/IFRS 15)🌍

In today’s global market, businesses often sell goods and services to customers in different countries, leading to contracts priced in various currencies. This introduces a critical question for accountants: How do you accurately record revenue when the amount you receive can change with daily fluctuations in foreign exchange rates?

The answer lies in the powerful synergy between two sets of accounting standards:

  • Revenue Recognition Standards: ASC 606 (U.S. GAAP) and IFRS 15 (IFRS)
  • Foreign Currency Standards: ASC 830 (U.S. GAAP) and IAS 21 (IFRS)

Understanding how these standards work together is essential for any company with international sales.

The Foundation: Revenue Recognition (ASC 606 & IFRS 15)

Before we can account for foreign currency, we must first determine when and how much revenue to recognize. Both ASC 606 and IFRS 15 are largely converged standards that provide a single, principles-based framework for this. They establish a five-step model for recognizing revenue from contracts with customers:

  1. Identify the contract with the customer.
  2. Identify the performance obligations in the contract.
  3. Determine the transaction price.
  4. Allocate the transaction price to the performance obligations.
  5. Recognize revenue when (or as) the performance obligations are satisfied.

The key to our discussion is Step 3: Determine the transaction price. This is where the foreign currency component comes into play.

The Intersection: Bringing in Foreign Currency (ASC 830 & IAS 21)

The foreign currency standards, ASC 830 and IAS 21, provide the rules for handling transactions denominated in a currency other than the company’s functional currency (the currency of the primary economic environment in which it operates).

The relationship between the two sets of standards is straightforward:

  • ASC 606 / IFRS 15 dictates when and how much revenue to recognize.
  • ASC 830 / IAS 21 dictates how to handle the foreign currency effects on that revenue and the subsequent cash collection.

Here’s how they work together:

When a company enters into a contract to sell goods or services in a foreign currency, it must first measure the revenue in its functional currency (for example, a U.S. company with USD as its functional currency).

On the date the company satisfies its performance obligation (for example, ships the goods), it must recognize revenue. According to ASC 830 / IAS 21, the company translates the foreign currency amount using the spot exchange rate on that specific date. Any future fluctuations in the exchange rate won’t change the amount of revenue already recognized.

What happens if the customer pays later, and the exchange rate has changed? The difference is recorded as a foreign exchange gain or loss, not an adjustment to the revenue account.

Example 1: Sales Transaction

Let’s imagine a U.S. company with a USD functional currency sells a product to a customer in Europe for €10,000.

  • On October 15 (shipment date): The company ships the product, satisfying its performance obligation. The exchange rate on this date is 1 EUR = 1.10 USD.
    • Revenue Recognition (ASC 606): The company recognizes revenue.
    • Foreign Currency Conversion (ASC 830): The revenue is measured in USD using the spot rate.
    • Journal Entry:
      • Debit Accounts Receivable: $11,000 (€10,000 x 1.10)
      • Credit Revenue: $11,000
      • The amount of revenue is now fixed at $11,000.
  • On November 15 (payment date): The customer pays the invoice. The exchange rate has since dropped to 1 EUR = 1.05 USD.
    • Cash Received: The company receives €10,000, which converts to $10,500 in USD.
    • Foreign Currency Gain/Loss (ASC 830): The difference between the cash received and the initial accounts receivable is a foreign exchange loss.
    • Journal Entry:
      • Debit Cash: $10,500
      • Debit Foreign Exchange Loss: $500
      • Credit Accounts Receivable: $11,000
      • The original revenue of $11,000 remains unchanged.

Example 2: Subscription Service

Consider a U.S. software company with a USD functional currency that offers a monthly subscription to a customer in the U.K. for £100.

  • January 1 (subscription starts): The company satisfies the performance obligation for the first month. The exchange rate is 1 GBP = 1.25 USD.
    • Revenue: The company recognizes $125 in revenue.
  • February 1 (payment received): The customer pays the invoice. The exchange rate has increased to 1 GBP = 1.30 USD.
    • Cash: The company receives £100, which converts to $130 in USD.
    • Foreign Exchange Gain: The company records a $5 foreign exchange gain. The revenue for the month remains at $125.

Summary of the Relationship

Think of it as a two-part process:

  1. ASC 606 / IFRS 15 determines the “slice” of the revenue pie you can recognize and when you can recognize it.
  2. ASC 830 / IAS 21 then tells you how to “cut” that slice into your functional currency and how to handle any changes in the pie’s value due to currency fluctuations.

By working together, these standards ensure that companies accurately report both their revenue and the financial effects of operating across international borders. ✈️

Leave a comment