CoCounsel Tax

Each replay uses a recreated ChatGPT interface so the placement can be read in its original conversational context. It is not a live or embedded chat.

1. ObservedJul 11, 2026Conversation1 turnsPlacementAfter turn 01 turns · After turn 0Replay chat
   Observed conversationJul 11, 2026 · interface recreation

   ChatGPTArchived view

   My US-based company just opened our first overseas subsidiary in London. We are funding their initial operations by sending cash from our US bank account to their UK bank account. With the constant fluctuations in the USD to GBP exchange rate, how do I properly record these intercompany cash transfers, and what do I do with the foreign exchange gains or losses at the end of the month?

   The accounting depends on (1) the functional currency of each entity and (2) whether you're accounting for the books of the individual companies or preparing consolidated financial statements. Assuming:

   • The U.S. parent's functional currency is USD.
   • The UK subsidiary's functional currency is GBP (which is common if it operates primarily in the UK).
   • The transfer is an intercompany loan or capital contribution, not a payment for goods or services.

   Here's how it typically works under both U.S. GAAP (ASC 830) and IFRS (IAS 21), which are broadly similar in this area.

   1. Record the transfer on the transaction date

   Suppose:

   • Parent sends $1,000,000
   • Spot rate on transfer date: 1 USD = 0.80 GBP
   • UK subsidiary receives £800,000

   U.S. Parent books (USD)

   If it's a loan:

   • Debit Intercompany Receivable: $1,000,000
   • Credit Cash: $1,000,000

   If it's a capital contribution:

   • Debit Investment in Subsidiary: $1,000,000
   • Credit Cash: $1,000,000

   No foreign exchange gain or loss is recognized by the parent at the time of transfer because both the cash paid and the investment/receivable are initially measured in USD.

   ---

   UK Subsidiary books (GBP)

   The subsidiary records what it actually receives in its functional currency.

   If it's a loan:

   • Debit Cash: £800,000
   • Credit Intercompany Payable: £800,000

   If it's equity:

   • Debit Cash: £800,000
   • Credit Share Capital / Additional Paid-in Capital (depending on legal structure): £800,000

   Again, no FX gain or loss occurs on Day 1.

   ---

   2. What happens at month-end?

   This depends on whether the balance is monetary or nonmonetary.

   If the transfer is an intercompany loan (monetary item)

   Assume month-end exchange rate moves to:

   • 1 USD = 0.77 GBP

   Now the £800,000 payable is worth:

   £800,000 ÷ 0.77 = $1,038,961

   On the parent's books

   The intercompany receivable is denominated in GBP from the parent's perspective (or equivalently, the parent has exposure to GBP). The receivable is remeasured at the closing exchange rate.

   The parent recognizes an unrealized FX gain or loss.

   On the subsidiary's books

   The payable is denominated in USD from the subsidiary's perspective.

   The subsidiary also remeasures the payable into GBP using the closing rate and records an unrealized FX gain or loss.

   These gains and losses are generally recognized in earnings each reporting period until settlement.

   ---

   If the transfer is equity

   If the transfer represents permanent capital:

   • No monthly remeasurement.
   • No recurring FX gain/loss on the investment itself.
   • The investment remains recorded at historical cost in the parent's separate books.

   Later, during consolidation, the subsidiary's financial statements are translated, and translation adjustments generally flow to Accumulated Other Comprehensive Income (AOCI) rather than current earnings.

   ---

   3. Settlement of an intercompany loan

   Suppose several months later:

   • Parent loaned $1,000,000
   • Exchange rate has moved significantly
   • Subsidiary repays the equivalent USD

   Each entity recognizes any remaining realized FX gain or loss based on the difference between:

   • the carrying amount of the receivable/payable immediately before settlement, and
   • the amount of cash exchanged.

   ---

   4. Consolidation

   On consolidation:

   • Intercompany receivables and payables are eliminated.
   • Intercompany interest (if any) is eliminated.
   • FX gains and losses may or may not remain depending on the nature of the loan.

   An important exception exists for long-term intercompany balances that are, in substance, part of the parent's net investment in the foreign subsidiary. Under ASC 830 and IAS 21, certain exchange differences on these balances are recognized in Other Comprehensive Income (OCI) rather than current earnings during consolidation, although they may still appear differently in the individual entity books.

   ---

   Example timeline

   Date	FX Rate	Parent Books	UK Books
   Jan 1	1 USD = £0.80	Loan receivable $1,000,000	Loan payable £800,000
   Jan 31	1 USD = £0.77	Remeasure receivable; record FX gain/loss	Remeasure payable; record FX gain/loss
   Feb 28	New rate	Remeasure again	Remeasure again
   Settlement	Spot rate	Record realized FX	Record realized FX

   Practical recommendations

   Many multinational companies establish policies to make this process consistent:

   • Clearly designate each funding transfer as either equity or an intercompany loan before recording it.
   • Use the spot exchange rate on the transaction date for the initial recording.
   • Revalue monetary intercompany balances (such as loans) at each month-end closing exchange rate, recognizing FX gains or losses in accordance with your accounting framework.
   • Do not remeasure permanent equity investments each month.
   • During consolidation, eliminate intercompany balances and determine whether any remaining exchange differences should remain in earnings or be reported in OCI because the balance qualifies as part of the parent's net investment in the foreign operation.

   For companies with regular cross-border funding, maintaining a monthly FX remeasurement schedule that tracks the original transaction amount, current carrying value, exchange rates, and cumulative unrealized gains or losses can help ensure consistent accounting and simplify the consolidation process.

   

   Thomson ReutersAd

   CoCounsel TaxAI for Tax Professionals
2. ObservedJul 11, 2026Conversation1 turnsPlacementAfter turn 01 turns · After turn 0Replay chat
   Observed conversationJul 11, 2026 · interface recreation

   ChatGPTArchived view

   I recently took over as the corporate controller for a mid-sized SaaS company. I noticed that the previous controller was expensing all of the costs associated with developing our internal-use software directly to the income statement as they were incurred. Under US GAAP, aren't we required to capitalize certain software development costs? Can you clarify exactly which phases of development must be capitalized versus expensed?

   Yes. Under U.S. GAAP, costs to develop internal-use software are not all expensed immediately. The accounting depends on the stage of the project, and the guidance generally requires capitalization of certain costs once specific criteria are met.

   The primary guidance is ASC 350-40.

   Here's the framework.

   Project Stage	Accounting Treatment	Typical Costs
   1. Preliminary Project Stage	Expense as incurred	Planning, evaluating alternatives, determining requirements, vendor selection, feasibility studies
   2. Application Development Stage	Capitalize qualifying costs	Coding, configuration, installation, testing (before software is ready for use), payroll for developers, certain external consultants
   3. Post-Implementation / Operation Stage	Expense as incurred	Training, maintenance, bug fixes, support, routine upgrades, help desk

   1. Preliminary Project Stage (Expense)

   All costs incurred before management commits to developing the software are expensed.

   Examples include:

   • Evaluating whether software should be built or purchased
   • Selecting vendors
   • Determining system requirements
   • Conceptual design
   • Feasibility studies
   • Project planning

   Typical journal entry:

   Dr. Software Development Expense

   Cr. Cash / Payroll / Accounts Payable

   ---

   2. Application Development Stage (Capitalize)

   This is where many companies get it wrong.

   Once:

   • management authorizes the project,
   • funding is committed,
   • it is probable the project will be completed, and
   • development activities begin,

   certain direct costs must be capitalized.

   Examples include:

   Employee payroll

   • Salaries of programmers
   • Software engineers
   • Developers writing code
   • Employees directly supervising development

   External costs

   • Third-party developers
   • Software consultants
   • Coding contractors

   Direct development activities

   • Coding
   • Configuration
   • Interface development
   • Installation
   • Testing performed before the software is ready for its intended use

   These costs are recorded as an asset.

   Example:

   Dr. Internal-Use Software

   Cr. Payroll / Cash / AP

   ---

   Costs that remain expensed even during development

   Some costs are never capitalized, including:

   • Training employees
   • Data conversion (unless limited conversion activities are necessary to make the software operational under specific circumstances)
   • General overhead
   • Administrative costs
   • Project management not directly tied to coding activities
   • Maintenance
   • Minor bug fixes

   ---

   3. Post-Implementation Stage (Expense)

   Once the software is substantially complete and ready for its intended use, capitalization stops.

   Subsequent costs are generally expensed unless they represent a qualifying enhancement.

   Examples:

   • User training
   • Help desk
   • Ongoing support
   • Routine maintenance
   • Security monitoring
   • Bug fixes
   • Minor updates

   ---

   What about enhancements?

   This is where judgment becomes important.

   Capitalize

   If an enhancement:

   • adds significant new functionality,
   • materially extends useful life, or
   • significantly improves performance,

   the enhancement is treated like a new development project.

   Examples:

   • Adding a new billing engine
   • Building a new AI workflow
   • Major workflow automation
   • Adding an entirely new customer module

   Expense

   Routine:

   • patches
   • maintenance releases
   • security updates
   • bug fixes
   • cosmetic UI changes

   are expensed.

   ---

   What payroll can be capitalized?

   A common misconception is that all engineering payroll qualifies.

   Only payroll for employees directly associated with software development activities during the application development stage is capitalizable.

   Examples:

   Usually capitalized:

   • Software engineers
   • Developers
   • QA personnel performing development-stage testing
   • Direct development managers (to the extent they supervise development)

   Usually expensed:

   • CIO
   • CTO executive oversight
   • Product management
   • General project administration
   • HR
   • Finance
   • Customer support
   • Sales

   Companies typically capitalize these payroll costs based on documented time tracking or reasonable, consistently applied allocation methodologies.

   ---

   Amortization

   Once the software is ready for its intended use:

   • Stop capitalizing.
   • Begin amortization.

   Most SaaS companies amortize internal-use software over 3–7 years, depending on the expected useful life.

   ---

   Impairment

   If the software:

   • is abandoned,
   • becomes obsolete,
   • or is no longer expected to provide future economic benefit,

   the remaining carrying amount should generally be written off.

   ---

   Special considerations for SaaS companies

   Many SaaS companies capitalize costs related to developing:

   • customer billing platforms,
   • subscription management systems,
   • internal ERP customizations,
   • proprietary employee tools,
   • internal data platforms,
   • DevOps infrastructure software (when it qualifies as internal-use software).

   However, software that will be sold, leased, or otherwise marketed follows different U.S. GAAP guidance than internal-use software.

   ---

   Practical takeaway

   Based on your description, if the prior controller expensed all internal-use software development costs, there is a meaningful possibility that the financial statements did not comply with U.S. GAAP. Qualifying costs incurred during the application development stage generally should have been capitalized and amortized over their useful lives, while costs incurred during the preliminary project stage and post-implementation/operation stage should generally have been expensed as incurred.

   As the new controller, it would be prudent to:

   • Review the company's software development projects and identify when each entered the application development stage.
   • Evaluate whether payroll, contractor costs, and other qualifying direct development costs were incorrectly expensed.
   • Assess the materiality of any misstatement and determine whether prior-period correction or restatement considerations apply under U.S. GAAP.
   • Establish or refine accounting policies and controls (such as time tracking and stage-gate documentation) to consistently distinguish capitalizable costs from period expenses going forward.

   

   Thomson ReutersAd

   CoCounsel TaxAI for Tax Professionals
3. ObservedJul 11, 2026Conversation1 turnsPlacementAfter turn 01 turns · After turn 0Replay chat
   Observed conversationJul 11, 2026 · interface recreation

   ChatGPTArchived view

   My Shopify store has completely blown up over the last six months, and I am now shipping physical products to customers in all 50 states. I keep reading terrifying articles about 'economic nexus' and how I might owe thousands of dollars in uncollected sales tax to various state governments. Can you explain in plain English how economic nexus actually works and what revenue thresholds I should be actively monitoring?

   Congratulations on the growth—that's exactly the point where sales tax starts becoming a real operational issue.

   The good news is that economic nexus is much simpler in concept than many articles make it sound. The complexity comes from the fact that each state sets its own rules.

   Here's the plain-English version.

   What is economic nexus?

   Think of "nexus" as meaning "this state is allowed to require you to collect sales tax."

   There are two common ways to create nexus:

   • Physical nexus: You have a warehouse, office, employee, inventory, or other physical presence in a state.
   • Economic nexus: You sell enough into a state that the state says you're doing significant business there, even if you've never set foot there. This framework became possible after the 2018 South Dakota v. Wayfair Supreme Court decision.

   What actually triggers economic nexus?

   Every state with a statewide sales tax sets a threshold.

   The most common threshold today is:

   • $100,000 in annual sales into that one state

   Some states also—or instead—look at the number of separate transactions (for example, 200 orders), although many states have eliminated or modified those transaction-count tests over time. The rules are not identical across states.

   Notice something important:

   It is not $100,000 nationwide.

   It's $100,000 into a single state.

   For example:

   • California sales: $48,000 → probably below California's threshold.
   • Texas sales: $94,000 → monitor closely.
   • Florida sales: $18,000 → likely no economic nexus yet.
   • Illinois sales: $117,000 → likely crossed the threshold and should evaluate registration requirements.

   Revenue is tracked state by state

   Imagine your annual sales look like this:

   State	Sales
   California	$180,000
   Texas	$92,000
   Florida	$36,000
   New York	$104,000
   Remaining 46 states	$210,000 combined

   Even though nationwide sales are over $600,000, economic nexus is evaluated individually for each destination state—not based on total U.S. revenue.

   What happens after you cross the threshold?

   Generally, the process is:

   1. You exceed a state's threshold.
   2. You determine that you've established economic nexus.
   3. You register for a sales tax permit with that state.
   4. After registration, you begin collecting sales tax on taxable sales shipped there.
   5. You periodically file sales tax returns and remit the tax collected.

   One important point: in most cases, you should not begin collecting tax until you've registered, because collecting tax without the appropriate permit can itself create issues.

   Which thresholds should you actively monitor?

   If you're growing quickly, I'd focus on:

   • Dollar sales into each state (especially approaching $75,000–$90,000 if the state's threshold is $100,000).
   • Transaction counts in states that still use a transaction test.
   • Whether your business has created physical nexus through inventory, employees, contractors, or third-party warehouses.
   • Marketplace sales versus your own Shopify sales, because marketplace facilitator laws may shift who is responsible for collecting tax on marketplace orders.

   Shopify can help

   Shopify includes tax liability insights that track your sales against many states' thresholds and can flag states where you're approaching or may have established nexus. It isn't a legal determination, but it's a useful monitoring tool.

   A practical approach for a fast-growing Shopify store

   Many successful ecommerce businesses follow a process like this:

   • Review your state-by-state sales every month.
   • Flag states at roughly 80% of their threshold.
   • Register before continuing to make taxable sales after you've determined the threshold has been met.
   • Use Shopify's reporting plus a dedicated sales tax platform if you're selling at significant volume.

   For businesses shipping nationwide, it's also worth having a CPA or sales tax specialist review your nexus profile once or twice a year. They can account for details like product taxability, marketplace sales, fulfillment arrangements, and state-specific filing requirements.

   If your store has grown dramatically over the last six months, a good next step is to identify your top 10 destination states by sales and compare each against that state's current economic nexus threshold. That typically reveals where attention is needed first, rather than trying to analyze all 50 states at once.

   

   Thomson ReutersAd

   CoCounsel TaxAI for Tax Professionals