NavigatingU.S. GAAP

U.S. GAAP Explained. What it is and why it matters. If your company operates in the U.S., you've probably heard the term U.S. GAAP, especially around financial statements, audits, investors, or reporting back to a parent company. But what exactly is it, and when do you actually need it? U.S. GAAP is the accounting framework used to prepare financial statements in the United States. The standards are set by the Financial Accounting Standards Board, or FASB, and organized in the Accounting Standards Codification, which is why you'll hear accountants reference things like ASC 606 or ASC 842. For private companies, simply operating in the U.S. does not automatically mean you're required to prepare U.S. GAAP financial statements. But there are several situations where they can become important or required. For example, a bank or lender may request GAAP-compliant financial statements as part of financing. U.S. investors may ask for them during a fundraising round. If you're preparing audited U.S. financial statements, the stakeholders requesting the audit may require them to be prepared under U.S. GAAP. And certain government loans, grants, subsidies, or other programs can also have GAAP financial reporting requirements. They can also become important during an acquisition, due diligence process, or other transaction. But here's another important distinction: U.S. GAAP is not the same thing as U.S. tax accounting. Your tax return calculates taxable income under U.S. tax law. U.S. GAAP is designed to report the financial position and performance of the business. That means the same transaction can be treated differently for financial reporting and tax purposes. And if your parent company uses IFRS or another local accounting standard, those financials may not automatically translate to U.S. GAAP either. The frameworks share many concepts, but important differences remain. So for an international company, the real questions are: Do we need U.S. GAAP reporting? Where does it differ from our current accounting? And what do we need to change? In the next video, we'll start with one of the most important areas: revenue recognition.

Revenue recognition under U.S. GAAP. A customer signs a $120,000 annual contract and pays you the full amount up front. You've got the cash. You've sent the invoice. So you've made $120,000 in revenue. Right? Not necessarily. Under U.S. GAAP, revenue recognition is primarily governed by ASC 606. The basic idea is that revenue is recognized as you satisfy your promises to the customer, not simply when you invoice them or receive payment. For example, imagine that $120,000 is for a service you provide evenly over 12 months. You may receive all $120,000 on day one, but if the service is provided over the year, the revenue would generally be recognized over that service period. The amount received before you've earned it sits on the balance sheet as a contract liability, often referred to as deferred revenue. ASC 606 uses a five-step framework. First, identify the contract. Second, identify the performance obligations. Third, determine the transaction price. Fourth, allocate the price. And fifth, recognize revenue as obligations are satisfied. But you don't need to memorize all five steps. The practical lesson is that the contract matters. If you sell software plus implementation, products plus services, offer discounts, refunds or bonuses, or change a contract halfway through, the accounting may depend on exactly what you've promised the customer and when you deliver it. For international teams, ASC 606 and IFRS 15 are substantially aligned, so much of this may look familiar, but differences can still arise in particular circumstances. The biggest takeaway? Don't build your revenue accounting from invoices alone. Finance needs visibility into the underlying contracts and any significant changes to them, because under U.S. GAAP, getting paid and earning revenue aren't necessarily the same thing. In the next video, we'll look at the other side of the income statement, when a cost becomes an expense and when it becomes an asset.

When is a cost an expense versus an asset? Your company spends $500,000 developing a new product. You've created something that could generate revenue for years. So that $500,000 must be an asset. Right? Again, not necessarily. One of the important questions under U.S. GAAP is whether a cost should be recognized immediately as an expense or capitalized on the balance sheet and recognized over time. And the answer depends on what you spent the money on. Buy a piece of equipment you'll use for several years? That will typically become an asset, with the cost recognized gradually through depreciation. Buy inventory? That cost generally remains an asset, until the inventory is sold and it moves into cost of goods sold. But research and development is different. Under U.S. GAAP, R&D costs are generally expensed as they're incurred, subject to specific exceptions and separate guidance for areas like software. And this is particularly important for international companies. Under IFRS, research costs are also expensed, but qualifying development costs are capitalized once certain criteria are met. So the same development activity can produce different expenses and assets depending on the accounting framework. Software adds another layer. Different guidance can apply depending on what the software is being developed for. So companies shouldn't assume that every technology or development cost receives the same treatment. The practical takeaway is simple. Creating something valuable doesn't automatically mean you can record an asset. Finance needs to understand what costs were incurred, what they relate to, and which accounting guidance applies. In the next video, we'll look at three other areas that commonly create important U.S. GAAP adjustments: leases, stock compensation, and deferred taxes.

Leases, Stock Compensation, and Deferred Taxes Under U.S. GAAP. Some of the most important U.S. GAAP entries don't come from a normal customer or vendor invoice. Three common examples are leases, stock-based compensation, and deferred taxes. First, leases. Under ASC 842, most leases lasting more than 12 months create both a right-of-use asset and a lease liability on the balance sheet. So if your company signs a five-year office lease, the accounting isn't simply recording the rent expense each month. The contract itself generally creates an asset and liability that need to be measured and tracked. Next, stock-based compensation. If employees receive stock options or other share-based awards, there may be no cash payment by the company. But that doesn't mean there's no expense. ASC 718 generally requires companies to measure and recognize compensation costs for share-based awards over the applicable service period. So equity compensation can affect your P&L even when no cash leaves the bank. And finally, deferred taxes. Your financial statements and tax return often recognize the same item differently or at different times. For example, an asset might be depreciated one way for U.S. GAAP and another way for tax purposes. That difference can affect taxes you expect to pay or recover in future periods. ASC 740 captures those future tax effects through deferred tax assets and deferred tax liabilities. This is one of the clearest examples of why your tax return and your U.S. GAAP financial statements aren't interchangeable. And while leases, stock compensation, and deferred taxes aren't concepts that exist only in the U.S., their treatment under U.S. GAAP can create significant adjustments that international teams need to understand. In the next video, we'll look at the areas that become especially important when you're accounting across different countries, currencies, and legal entities.

U.S. GAAP for cross-border companies. Let's say you have a French parent company and a U.S. subsidiary. The parent reports in euros. The U.S. company invoices customers in dollars. Some intercompany transactions are in euros, and the group needs to consolidate everything at year-end. This is where several U.S. GAAP concepts become especially important for international companies. First, currency. Every entity has a functional currency, essentially the currency of the primary economic environment in which it operates. For many U.S. businesses, that's the dollar, but you shouldn't determine functional currency simply from where a company is incorporated. Factors such as the currencies driving sales, expenses, and financing all matter. Once that's established, transactions in other currencies can create foreign exchange gains or losses. There's also an important difference between remeasuring foreign currency transactions and translating an entire foreign operation into another reporting currency. Those currency effects don't necessarily appear in the same place in the financial statements. Next comes intercompany accounting. Your U.S. subsidiary may invoice its parent, receive funding from another group company, pay management fees, or buy inventory from a related entity. Those transactions exist on the individual company's books, but when the group is consolidated, intercompany balances and transactions are generally eliminated. That makes clean intercompany reconciliation critical. If one company records a $100,000 receivable and the other records a different payable, perhaps because of timing, currency, or inconsistent treatment, consolidation gets messy quickly. And if the parent reports under IFRS while the U.S. entity reports under U.S. GAAP, accounting differences may also need to be adjusted as part of the group's reporting process. The takeaway? For a cross-border group, you need clarity around three things. First, accounting framework. Second, functional and reporting currencies. And third, intercompany reconciliation. Get those right early and group reporting becomes significantly cleaner. In our final video, we'll bring everything together and look at how your accounting records actually become U.S. GAAP financial statements.

From the Books to U.S. GAAP Financial Statements. Your accounting system is up to date, the bank is reconciled, every invoice is entered. Does that mean you automatically have U.S. GAAP financial statements? No. Your general ledger is the starting point. Preparing U.S. GAAP financial statements may still require the types of adjustments we've covered throughout this series. Deferred revenue, capitalized costs, leases, stock-based compensation, foreign exchange, intercompany eliminations, and deferred taxes. Those adjustments ultimately feed into the company's financial statements. And the notes matter, too. U.S. GAAP isn't only about getting the final numbers right. Financial statements also include disclosures that provide context around accounting policies, significant estimates and judgments, commitments, risks, and other information needed to understand those numbers. This process can also create a bridge between the accounting used elsewhere in your organization and U.S. GAAP. And remember, your U.S. GAAP income still isn't automatically your U.S. taxable income. Different financial reporting and tax rules can create book-to-tax differences, including the deferred tax assets and liabilities we discussed in the previous video. Finally, there's documentation. If you're preparing for an audit, financing round, acquisition, government program, or simply stronger internal reporting, you need to be able to support the numbers. That means maintaining reconciliations, contracts, schedules, accounting policies, and support for significant judgments throughout the year, rather than trying to rebuild everything after year-end. And that's the biggest takeaway from this series. U.S. GAAP isn't simply a different format for your financial statements. It's a framework that can change when something is recognized, how it's measured, where it's reported, and what information needs to support it. For international companies operating in the U.S., identifying those differences early makes financial reporting much more consistent and manageable. Thanks for watching!