SyteLine Multi-Currency Configuration: A Complete Setup Guide
Multi-currency in SyteLine lets each site transact with customers and vendors in foreign currencies while keeping the general ledger in the site's domestic currency, converting at defined exchange rates and posting realized and unrealized gains and losses automatically. Configuration spans the Currency Codes and Currency Rates forms, per-currency account assignments, and the periodic revaluation utilities that keep open AR, AP, and cash balances honest as rates move. Set it up correctly once and month-end currency work is routine; set it up wrong and you inherit unexplained FX variances that take controllers days to unwind. This guide covers the full configuration path and the pitfalls that generate audit findings.
Currency Codes, Rate Types, and the Rates Table
Setup starts on the Currency Codes form: define each transaction currency with its decimal precision and rounding rules, then assign per-currency GL accounts for realized gain, realized loss, unrealized gain, and unrealized loss. The Currency Rates form holds dated buying and selling rates per currency pair; SyteLine selects the rate effective on the transaction date. Rate handling per currency can be fixed or variable - variable currencies let users override the rate at order or voucher entry within tolerance, while fixed currencies lock to the table. Most controllers load rates monthly from a treasury source or daily via an integration; a stale rates table is the single most common source of phantom FX variance.
Transaction Flow: Orders, Invoices, and Payments in Foreign Currency
Once a customer or vendor is assigned a currency, every downstream document - quotes, orders, invoices, vouchers, payments - carries amounts in that currency alongside domestic equivalents converted at the effective rate. The GL always posts domestic values.
- Customer and vendor currency is set on their master records and flows to all new documents
- Invoice posting converts at the invoice-date rate; payment posting converts at the payment-date rate
- The difference between those two conversions posts automatically to realized gain or loss accounts
- Price lists can be maintained per currency so euro customers see clean euro pricing, not converted artifacts
Revaluation: Keeping Open Balances Honest
Open foreign-currency AR, AP, and bank balances are stated at historical rates until revalued. SyteLine's currency revaluation utilities recompute open items at the current rate and post the difference to unrealized gain and loss accounts, typically as a reversing entry at each month-end. Skipping revaluation is how balance sheets drift: a manufacturer holding 2 million euros of open receivables through a 5 percent currency move carries a 100,000 dollar misstatement until settlement. Run revaluation for AR, AP, and cash as a standard close task, verify the reversing entries posted in the new period, and reconcile the unrealized accounts to the open-item aging by currency every quarter.
Multi-Site and Reporting Pitfalls
Multi-currency gets genuinely hard when multiple sites have different domestic currencies and results must consolidate. These are the traps that surface during implementations and audits.
- Intercompany transactions between sites with different domestic currencies need agreed rate conventions or eliminations will not tie
- Consolidated reporting requires translation of each site's ledger, distinct from transaction-level conversion
- Historical-rate items like fixed assets and equity must not be swept up in period-end translation rates
- DFARS and government contract reporting is dollar-denominated; foreign-site cost data needs a documented, consistent translation method
How Netray Automates Multi-Currency Operations
Netray automates the currency chores that consume controller time: agents load daily rates from treasury feeds into the Currency Rates table, verify revaluation ran and reversed correctly each close, and reconcile realized and unrealized gain and loss accounts against open-item detail - flagging exceptions instead of requiring line-by-line review. A precision components group with sites in the US, UK, and Mexico cut currency-related close tasks from three days to four hours and eliminated a recurring audit comment about undocumented rate overrides, because Netray's agent now logs and reports every manual rate deviation. Everything runs on-prem against SyteLine's SQL Server, inside existing security boundaries.
Frequently Asked Questions
How do I set up multi-currency in SyteLine?
Define each currency on the Currency Codes form with decimal precision and assign the four gain and loss accounts (realized and unrealized). Load dated buying and selling rates on the Currency Rates form, then assign currencies to customers and vendors on their master records. From that point, orders, invoices, and payments carry foreign amounts with domestic conversions posted to the GL, and month-end revaluation utilities restate open balances at current rates.
How does SyteLine handle exchange rate gains and losses?
Realized gains and losses post automatically when a foreign-currency invoice is settled: SyteLine compares the domestic value at the invoice-date rate with the value at the payment-date rate and posts the difference to the realized gain or loss account assigned to that currency. Unrealized gains and losses come from the periodic revaluation utilities, which restate open AR, AP, and cash at current rates, normally as reversing month-end entries.
Why do my SyteLine currency balances not reconcile?
The usual causes are a stale currency rates table, revaluation skipped or run without its reversing entry, manual rate overrides at transaction entry that were never reviewed, and intercompany transactions converted at inconsistent rates between sites. Start by reconciling the unrealized gain and loss accounts against an open-item aging by currency, then audit rate override activity - undocumented overrides are the most common single finding.
Key Takeaways
- 1Currency Codes, Rate Types, and the Rates Table: Setup starts on the Currency Codes form: define each transaction currency with its decimal precision and rounding rules, then assign per-currency GL accounts for realized gain, realized loss, unrealized gain, and unrealized loss. The Currency Rates form holds dated buying and selling rates per currency pair; SyteLine selects the rate effective on the transaction date.
- 2Transaction Flow: Orders, Invoices, and Payments in Foreign Currency: Once a customer or vendor is assigned a currency, every downstream document - quotes, orders, invoices, vouchers, payments - carries amounts in that currency alongside domestic equivalents converted at the effective rate. The GL always posts domestic values..
- 3Revaluation: Keeping Open Balances Honest: Open foreign-currency AR, AP, and bank balances are stated at historical rates until revalued. SyteLine's currency revaluation utilities recompute open items at the current rate and post the difference to unrealized gain and loss accounts, typically as a reversing entry at each month-end.
Have Netray automate your SyteLine currency rate loads, revaluation checks, and FX reconciliations before your next month-end close.
Related Resources
SyteLine DataViews: Reporting Without a Developer
Build SyteLine DataViews reports without a developer: DataView setup, subcollections, publishing to users, filters, and Excel export in CloudSuite Industrial.
Infor SyteLineSyteLine APS: Advanced Planning & Scheduling Explained
How SyteLine APS advanced planning and scheduling works: CTP order promising, resource groups, APS vs MRP mode, and tuning tips for discrete manufacturers.
Infor SyteLineSyteLine REST API Development: IDO Endpoints in Practice
Practical SyteLine REST API development guide: calling IDO endpoints over REST, token authentication, JSON payloads, filter syntax, and error handling.