Bill in EUR, Collect in GBP,
Close the Books in USD.
LedgerUp invoices each customer in their contracted currency, matches payments across FX differences, and posts clean multi-currency records to your ledger.
Currency chaos vs currency discipline
International customers are a growth milestone that quietly becomes a reconciliation problem.
Without automation
- International customers invoiced in USD and left to handle conversion
- EUR payment arrives $312 short of the USD invoice — is that FX or a short-pay?
- Someone maintains an exchange-rate tab in the billing spreadsheet
- Wire fees deducted in transit break payment matching
- Month-end FX cleanup as a recurring ritual
With LedgerUp
- Each customer invoiced in their contracted currency at contracted pricing
- Payments matched across FX differences — genuine short-pays distinguished from rate movement
- Rates applied consistently from your configured source
- In-transit bank fees recognized and handled in matching tolerance
- Multi-currency records posted natively to your ledger, close-ready
How multi-currency billing works
From a EUR contract to a clean USD close.
Contract currency honored from signature
Ari reads the contract’s pricing currency and bills in it — EUR contracts invoice in EUR at the contracted amounts, not USD amounts converted at whatever rate the spreadsheet had.
Invoices carry the right details per currency
Currency-appropriate formatting, the right receiving bank details per currency, and payment methods your international customers actually use. Fewer excuses for late payment.
Payments matched with FX intelligence
When payments land, Ari matches them to invoices with tolerance for rate movement and known wire fees — and distinguishes an FX difference from a genuine short-pay, routing only real discrepancies as exceptions.
Ledger stays close-ready
Transactions post in their native currency to QuickBooks, NetSuite, Sage Intacct, or Xero with your functional-currency treatment applied per your accounting configuration — so month-end FX cleanup stops being a ritual.
Works with your existing stack
LedgerUp connects to the tools you already use — no migration required.
Multi-currency use cases
How international billing runs on LedgerUp.
First European Customers
The first EUR-denominated contract shouldn’t require new process. Ari bills it in EUR, tracks it alongside USD receivables, and reports it in your reporting currency.
A €50K annual contract bills €12.5K quarterly; consolidated AR shows it at the current rate with the EUR amount preserved on the record.
FX-Tolerant Payment Matching
A GBP payment that arrives slightly off the invoice amount due to rate movement matches automatically within tolerance — while a payment short by a suspicious round number flags as a potential dispute.
A £20,000 invoice settled at £19,972 after wire fees matches and closes; a payment short by exactly £2,000 flags as a short-pay for review.
Multi-Currency + Multi-Entity
Currency and entity usually arrive together. EUR billing from the EU entity, GBP from the UK entity, consolidated reporting in USD — one workflow handles the matrix.
A UK customer bills in GBP from the UK entity; group AR reporting shows the exposure in USD with drill-down to the native-currency record.
Currency is half of the international story
Multi-currency billing usually pairs with entity structure and reconciliation.
Multi-entity billing
The legal-entity half: routing contracts and keeping per-entity books clean.
See multi-entity billingPayment reconciliation
The matching engine that FX tolerance builds on.
See payment reconciliationMulti-currency FAQ
Common questions about multi-currency billing with LedgerUp.
Which currencies are supported?
Any currency your billing system and payment rails support — in practice, USD, EUR, GBP, CAD, AUD, and others are common. The contract’s currency drives invoicing; your ledger’s multi-currency configuration drives accounting treatment.
Where do exchange rates come from?
From your configured source — typically your accounting system’s rate table — applied consistently for reporting and matching tolerance. LedgerUp doesn’t invent its own rates; it enforces consistency with the rates your books already use.
How does matching handle wire fees deducted in transit?
Known fee patterns (correspondent bank deductions, typically $15-50) are recognized within matching tolerance, and the treatment — absorb as bank fee or bill back — follows your policy. Payments outside tolerance flag as exceptions with the gap quantified.
How do you tell an FX difference from a short-pay?
By pattern: rate movement between invoice date and payment date produces small percentage differences consistent with the rate delta; short-pays are typically round numbers or exact line-item amounts. Ari classifies accordingly and only routes genuine discrepancies for human review.
Does multi-currency require multiple entities?
No — a single US entity can bill customers in EUR or GBP if your billing system supports it. Entity structure becomes relevant for tax and legal reasons; when you add entities, currency handling composes with entity routing automatically.
What lands in the ledger?
Native-currency transaction records with your functional-currency treatment, posted to QuickBooks, NetSuite, Sage Intacct, or Xero per their multi-currency conventions — so revaluation and FX gain/loss run in your accounting system the way your accountants expect.