.png)
Frameworks, core principles and top case studies for SaaS pricing, learnt and refined over 28+ years of SaaS-monetization experience.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
In an increasingly globalized business landscape, companies routinely engage with clients and vendors across borders, denominating contracts in one currency while settling payments in another. This dual-currency approach—using both a contract currency and a settlement currency—has become essential for SaaS companies expanding internationally. Yet, many finance executives struggle with the operational complexity this creates, particularly when it comes to invoicing accuracy, revenue recognition, and foreign exchange (FX) risk management.
According to a 2023 survey by Deloitte, 78% of multinational companies reported that currency fluctuations significantly impacted their financial planning, with invoicing discrepancies being a primary concern. The challenge isn't just theoretical—mismanaged currency invoicing can lead to revenue leakage, strained customer relationships, and compliance issues that regulatory bodies like the SEC or IFRS Foundation scrutinize closely.
This article explores the practical framework for invoicing with contract and settlement currencies, providing SaaS executives with actionable strategies to streamline operations while minimizing risk.
What Are Contract Currency and Settlement Currency?
Before diving into implementation, it's crucial to understand the distinction between these two currency types:
Contract Currency (also called "invoicing currency" or "functional currency") is the currency in which you denominate the agreement with your customer. For example, a SaaS company based in the United States might sign a contract with a European client specifying all fees in euros (EUR), even though the company's books are maintained in USD.
Settlement Currency is the actual currency used to complete the payment transaction. Using the same example, while the contract is denominated in EUR, the customer might choose to pay in British pounds (GBP) or even USD, depending on their treasury preferences or banking relationships.
This separation creates flexibility for both parties but introduces operational complexity that requires careful management.
Why Do Companies Use Different Contract and Settlement Currencies?
Several strategic and practical reasons drive this approach:
Customer Preference and Competitive Advantage: Offering contracts in a customer's local currency reduces their FX risk and simplifies their internal accounting. According to research by JP Morgan, 64% of B2B buyers prefer to transact in their home currency, making this a competitive differentiator in crowded markets.
Hedging and Treasury Management: Large enterprises often have sophisticated treasury operations that consolidate payments in specific currencies to optimize FX hedging strategies. Accommodating settlement currency preferences can be essential to closing enterprise deals.
Banking Infrastructure: Some regions have currency controls or limited banking infrastructure for certain currencies. A company might contract in a stable reserve currency (like USD or EUR) but settle in the local currency to facilitate easier bank transfers.
Revenue Recognition Requirements: Under ASC 606 and IFRS 15, revenue must be recognized in the functional currency of the entity. However, contracts can be denominated differently, requiring careful translation and documentation.
How to Structure Your Invoicing Process
Implementing a dual-currency invoicing system requires careful planning across your quote-to-cash workflow. Here's a structured approach:
1. Define Currency Terms in the Contract
Your contract should explicitly state both the contract currency and acceptable settlement currencies. Include specific language such as:
- The contract amount and all fees denominated in the contract currency
- Acceptable settlement currencies (if multiple options exist)
- The FX rate mechanism (spot rate, forward rate, or specific rate source like Bloomberg or Reuters)
- The timing of FX rate determination (date of invoice, date of payment, or specific measurement date)
- Who bears the FX risk if settlement occurs in a different currency
According to PwC's Revenue Recognition Guide, ambiguity in currency terms is one of the top five causes of revenue recognition disputes during audits.
2. Invoice Generation Best Practices
Your invoice should clearly display both currencies when applicable:
Primary Display: Show the contract currency amount prominently, as this is what the customer agreed to pay.
Secondary Display: If settlement will occur in a different currency, show the converted amount with:
- The FX rate used
- The rate source
- The date of the rate
- A clear notation that the contract currency amount governs in case of dispute
For example:
Amount Due: €10,000 (Contract Currency)Settlement Amount (if paying in USD): $10,850FX Rate: 1.0850 (ECB Rate as of Invoice Date)3. Select an FX Rate Methodology
Consistency in FX rate selection is critical for both operational efficiency and compliance. Common approaches include:
Spot Rate at Invoice Date: The most straightforward method, using the rate on the day you generate the invoice. This is the approach recommended by FASB for most commercial transactions.
Monthly Average Rate: Some companies use a monthly average to smooth volatility. This works well for subscription businesses with predictable billing cycles.
Forward Rate: For large contracts, companies might lock in a forward FX rate at contract signing, eliminating uncertainty for both parties.
Customer-Specific Rate: In some cases, enterprise customers negotiate fixed rates for contract duration, essentially having the vendor absorb FX risk in exchange for business certainty.
Salesforce, in their investor documentation, notes that they primarily use spot rates for international invoicing but offer forward rate locks for contracts exceeding $500,000 annually.
4. System Configuration Requirements
Your billing system must support:
- Multi-currency price books
- Automatic FX rate updates from reliable sources (ECB, Federal Reserve, OANDA)
- Rate lock functionality for specific dates or contracts
- Revaluation capabilities for revenue recognition
- Audit trails showing which rates were applied and when
Modern billing platforms like Zuora, Stripe Billing, or Chargebee offer these capabilities, but legacy ERP systems may require custom development or middleware solutions.
Managing Foreign Exchange Risk
The gap between contract and settlement currencies exposes your business to FX risk. Here are strategies to mitigate this exposure:
Natural Hedging
If you have expenses in the same currency as your revenue, you've created a natural hedge. For example, if you invoice European customers in EUR and also have server costs from European data centers billed in EUR, fluctuations affect both sides of your P&L, partially offsetting the risk.
Financial Instruments
Treasury teams can use:
- Forward Contracts: Lock in exchange rates for future settlement dates
- Options: Provide downside protection while preserving upside potential
- Currency Swaps: Exchange currency at current rates with an agreement to reverse at future date
According to the Association for Financial Professionals, 65% of companies with annual revenue over $500 million actively use FX derivatives to manage currency exposure.
Settlement Currency Limitations
You can reduce FX risk by limiting the currencies you accept for settlement, even while offering flexibility in contract currency. For example, you might contract in any major currency but only settle in USD, EUR, or GBP, forcing the customer to handle conversion if they prefer another settlement approach.
Pricing Buffers
Some companies build an FX buffer into their pricing for international contracts. For instance, if your cost structure is USD-based, you might price EUR contracts with a 3-5% premium to absorb normal currency fluctuations.
Revenue Recognition Considerations
The intersection of multiple currencies and revenue recognition standards creates complexity that CFOs must navigate carefully.
Functional Currency Determination
Under both US GAAP and IFRS, each legal entity must determine its functional currency—typically the currency of the primary economic environment in which it operates. According to ASC 830-10-45-2, factors include:
- Currency that mainly influences sales prices
- Currency of the country whose competitive forces mainly determine sales prices
- Currency that mainly influences labor, material, and other costs
Even if you invoice in multiple currencies, revenue must ultimately be recognized in your functional currency.
Translation Methodology
When your contract currency differs from your functional currency, you must translate amounts for revenue recognition. The general approach under ASC 606:
- Determine the transaction price in the contract currency
- Translate to functional currency using the rate at contract inception (for fixed consideration) or at the date revenue is recognized (for variable consideration)
- Remeasure monetary assets/liabilities at each balance sheet date using current rates
- Record resulting gains/losses in the income statement
This creates a potential discrepancy between what you invoice and what you recognize as revenue—a point of frequent audit scrutiny.
Documentation Requirements
Maintain detailed documentation of:
- FX rates used and their sources
- Timing of rate determination
- Basis for functional currency determination
- Policies for rate lock periods
- Reconciliation between invoiced amounts and recognized revenue
EY's 2024 Technical Line guidance emphasizes that insufficient FX documentation is among the most common deficiencies found during revenue recognition audits.
Operational Workflow: A Step-by-Step Example
Let's walk through a practical scenario:
Situation: Your US-based SaaS company (functional currency: USD) signs a contract with a UK customer for £100,000 annual subscription, but the customer prefers to settle in EUR.
Step 1: Contract Signing
- Contract specifies: Amount due = £100,000 GBP
- Settlement currency options: GBP or EUR
- FX rate mechanism: ECB spot rate on invoice date
- Customer selects EUR settlement
Step 2: Invoice Generation (First Quarter)
- Invoice date: January 1
- ECB spot rate GBP/USD: 1.2500
- ECB spot rate EUR/GBP: 1.1500
- Invoice displays:
- Contract amount: £25,000
- Settlement amount: €28,750 (£25,000 × 1.1500)
- Note: "FX rate applied: 1.1500 per ECB as of Jan 1"
Step 3: Revenue Recognition
- Transaction price: £100,000
- Translate to USD at contract inception: $125,000 (£100,000 × 1.2500)
- Recognize quarterly: $31,250
- Note: This amount may differ from cash received due to FX movement
Step 4: Payment Receipt
- Customer pays €28,750 on Jan 15
- Spot rate EUR/USD on Jan 15: 1.0800
- Cash received in USD equivalent: $31,050 (€28,750 × 1.0800)
- FX gain/loss vs. receivable: Recorded separately from revenue
Step 5: Reconciliation
- Revenue recognized: $31,250
- Cash received: $31,050
- Receivable FX adjustment: $(200) loss
- Separate line items in financial statements
Technology Solutions and Automation
Manual management of dual-currency invoicing doesn't scale. As your international customer base grows, automation becomes essential.
Billing System Requirements
Modern subscription billing platforms should offer:
Multi-entity Management: Support for multiple legal entities, each with its own functional currency
Dynamic FX Rates: Automatic daily rate updates from authoritative sources
Rate Override Capabilities: Manual rate lock for specific contracts or customers
Revenue Recognition Engine: Automated translation and remeasurement calculations
Audit Trail: Complete history of rates applied, dates, and sources
Integration Considerations
Your billing system must integrate seamlessly with:
ERP System: For general ledger posting, revenue recognition, and financial reporting
Payment Gateway: To process settlements in multiple currencies (providers like Stripe, Adyen, or PayPal support 130+ currencies)
Treasury Management System: For hedging activities and cash flow forecasting
CRM: To ensure sales teams know which currencies are offered and approved
Companies like Dropbox and Zoom have publicly discussed their investments in integrated, multi-currency finance tech stacks, attributing significant efficiency gains to automation.
Data Analytics and Reporting
Build reporting capabilities to track:
- FX exposure by currency and customer segment
- Win/loss rates when offering local currency vs. USD-only
- Average days to payment by settlement currency
- FX gains/losses as percentage of revenue
- Currency mix trending over time
This data informs treasury strategy, pricing decisions, and market expansion planning.
Common Pitfalls and How to Avoid Them
Ambiguous Contract Language
Problem: Contract states "all amounts in EUR" but doesn't specify what happens if customer pays in different currency.
Solution: Explicitly state that contract currency governs, and any conversion for settlement convenience uses specified rate methodology at customer's risk.
Rate Timing Mismatches
Problem: Using different rate dates for invoicing, payment processing, and revenue recognition creates reconciliation nightmares.
Solution: Document a clear policy: typically spot rate at invoice date for A/R, spot rate at payment date for cash, and contract inception rate for revenue recognition.
Inadequate FX Controls
Problem: Sales team promises custom FX terms without finance approval, creating risk exposure or revenue recognition complexity.
Solution: Implement approval workflows for non-standard currency terms, with finance sign-off required before contract execution.
Poor Customer Communication
Problem: Customer receives invoice in unexpected currency or with unexplained conversion, leading to payment delays and support tickets.
Solution: Clearly communicate currency terms during sales process, send proactive notifications before first invoice, and provide accessible FX rate information.
System Limitations
Problem: Legacy billing system can't handle dual-currency display or lacks proper audit trails.
Solution: Evaluate modern billing platforms or build middleware to supplement ERP capabilities. The cost of manual workarounds typically exceeds technology investment within 18-24 months for companies with 50+ international customers.
Regulatory and Compliance Considerations
Tax Implications
Different jurisdictions have specific rules about currency conversion for tax purposes. For example:
US: IRS generally requires use of average exchange rate for the taxable year, though specific transactions can use spot rates (IRS Publication 538)
EU: VAT calculations must follow specific ECB rates and timing per EU Directive 2006/112/EC
UK: HMRC accepts various rate methodologies but requires consistency (Customs Notice 195)
Work with international tax advisors to ensure your invoicing approach complies with local regulations.
Transfer Pricing
For multinational SaaS companies with intercompany transactions, currency choices can impact transfer pricing arrangements. Ensure your intercompany agreements specify currencies and rate mechanisms that align with arm's-length pricing principles.
Anti-Money Laundering (AML)
When accepting payments in multiple currencies, especially from high-risk jurisdictions, ensure your payment processing includes adequate AML controls. Document the business rationale for unusual currency combinations and maintain enhanced due diligence for high-value transactions.
Strategic Considerations for SaaS Executives
Beyond operational mechanics, currency management involves strategic decisions that impact growth and profitability.
Market Entry Strategy
When entering new markets, consider:
Early Stage: Offer USD pricing only, testing market demand without currency complexity
Growth Stage: Introduce local currency pricing for key markets, typically starting with EUR, GBP, and AUD
Scale Stage: Comprehensive multi-currency support becomes a competitive necessity, especially for enterprise sales
HubSpot's international expansion strategy included phased currency rollout, correlating local currency availability with 30% higher win rates in those markets, according to their investor presentations.
Pricing Strategy
Currency choice affects perceived value:
Price Localization: Setting prices in local currency allows psychological price points (€99 vs. $107.82 equivalent)
Currency Arbitrage: Customers may exploit rate differences if you're slow to update pricing across currencies
Competitive Benchmarking: Competitors' currency offerings influence buyer expectations
Customer Segmentation
Different customer segments have different currency needs:
SMB: Often prefer simplicity; local currency reduces friction
Mid-Market: May have preferences but generally flexible
Enterprise: Frequently require specific currency terms as part of procurement requirements
Tailoring your currency approach by segment optimizes both customer experience and operational efficiency.
Building Your Currency Management Playbook
To implement effective dual-currency invoicing, develop a comprehensive playbook that includes:
Policy Documentation
- Supported contract currencies and criteria for adding new ones
- Acceptable settlement currencies
- Default FX rate methodology and approved sources
- Rate lock policies and approval requirements
- Exception handling procedures
Process Maps
- Quote-to-cash workflow with currency decision points
- Invoice generation checklist
- Payment application procedures
- Month-end close and reconciliation process
- Customer inquiry response protocols
Roles and Responsibilities
- Who approves non-standard currency terms (typically Finance VP)
- Who configures rates in billing system (Revenue Operations)
- Who monitors FX exposure (Treasury or CFO)
- Who handles customer currency questions (Customer Success with Finance escalation)
Training Requirements
- Sales team training on currency offerings and customer conversations
- Finance team training on dual-currency accounting
- Customer success training on common currency-related inquiries
- New hire onboarding curriculum
Measuring Success
Track these metrics to evaluate your currency management effectiveness:
Operational Efficiency
- Time to generate and send invoice (target: <24 hours from billing trigger)
- Invoice error rate (target: <0.5%)
- Payment processing time by currency (identify problem currencies)
- Manual intervention rate (should decrease as automation improves)
Financial Impact
- FX gains/losses as percentage of revenue (benchmark: 0.5-2% for most SaaS companies)
- Days sales outstanding (DSO) by currency (local currency often reduces DSO)
- Revenue leakage from currency errors (target: <0.1% of recognized revenue)
Customer Experience
- Payment success rate by currency
- Currency-related support ticket volume
- Customer satisfaction scores for international customers vs. domestic
Strategic Outcomes
- International revenue growth rate
- Win rate in markets with local currency vs. USD-only
- Average contract value by currency offering
Looking Forward: Emerging Trends
The landscape of international invoicing continues to evolve:
Real-Time Payments
Services like SWIFT gpi and instant payment networks (UK's Faster Payments, EU's SEPA Instant) are reducing settlement times, making real-time FX conversion more practical.
Blockchain and Stablecoins
Some companies are exploring cryptocurrency settlement options to reduce FX fees and settlement time. USD Coin (USDC) and other stablecoins are gaining traction for B2B payments, though regulatory uncertainty remains.
AI-Powered FX Optimization
Machine learning models can predict optimal timing for currency conversion, automated hedging, and even dynamic pricing adjustments based on volatility forecasts.
Embedded Finance
Banking-as-a-service providers are enabling SaaS companies to offer multi-currency accounts directly to customers, blurring the line between product and payment experience.
Conclusion
Mastering dual-currency invoicing—managing both contract currency and settlement currency—is no longer optional for SaaS companies with global ambitions. While the operational complexity is real, the strategic benefits are substantial: improved win rates in international markets, enhanced customer experience, and competitive differentiation.
The key is building a structured approach that balances flexibility for customers with operational efficiency and risk management for your business. This requires clear policies, robust technology, cross-functional collaboration, and ongoing refinement based on data and customer feedback.
Start by documenting your current state, identifying the highest-priority markets for currency support, and implementing the foundational elements: clear contract language, reliable FX rate sources, and proper accounting controls. As your international business scales, invest in automation and advanced treasury management to maintain efficiency.
For SaaS executives navigating this complexity, remember that currency management is ultimately about removing friction from the buying process while protecting your business from unnecessary risk. Done well, it becomes an invisible enabler of global growth rather than an operational burden.
Next Steps
- Audit your current approach: Review existing contracts and invoicing practices for currency handling consistency
- Assess technology gaps: Evaluate whether your billing system adequately supports multi-currency requirements
- Develop your policy: Create or refine your currency management playbook with input from Finance, Sales, and Legal
- Train your team: Ensure all customer-facing roles understand currency options and can articulate the value proposition
- Measure and iterate: Establish baseline metrics and review quarterly to identify improvement opportunities
The companies that master this capability will find themselves with a significant advantage in the increasingly global SaaS marketplace.