Multi-Currency Revaluation and FX Gain Loss

The problem with FX in SAP Business One

SAP Business One handles foreign currency transactions correctly at the document level: a Sales Order in EUR converts to local currency at the rate held in the Exchange Rates and Indexes table, and the A/R Invoice carries both the foreign amount and the local amount. What it does not do well is everything that happens after the document is posted.

At period end somebody in finance exports the open items from Business Partner ageing, builds a spreadsheet of foreign-currency balances, looks up the closing rate, calculates the difference against the historic rate on each open item, and then types a manual Journal Entry to move the difference into an unrealised gain or loss account. Next period, that entry has to be reversed before the new one is calculated, otherwise the same movement is counted twice. When a payment finally lands, the realised difference has to be split away from the unrealised amount that was accrued while the invoice was open.

Every step in that chain is manual, and every step is a place where a wrong rate, a missed open item, a forgotten reversal or a fat-fingered account code becomes an audit finding. Businesses running several currencies across multiple company databases repeat the whole exercise per database, per month.

What ECOSIRE builds

ECOSIRE builds a SAP Business One add-on that owns the full revaluation cycle: rate acquisition, exposure calculation, posting, reversal and reporting.

Exchange rate acquisition

A scheduled service pulls daily and period-closing rates from the rate source you nominate — a central bank publication, your bank's rate file, or a commercial rate API — and writes them into SAP Business One's own ORTT exchange rate store through the Service Layer, so every standard document, report and query in the system sees the same rate. Where you need a rate that SAP does not model natively, such as a separate month-end closing rate held alongside the daily transaction rate, the add-on stores it in a User-Defined Table and uses it only in the revaluation run.

Rates arrive with an audit trail: source, retrieval timestamp, and the value that was in place before the update. Manual overrides are permitted, captured against the user who made them, and can be routed through a SAP Business One approval procedure if you want a second pair of eyes on a rate change.

Revaluation run

The run reads open foreign-currency exposure directly from SAP Business One's transactional tables: open A/R and A/P Invoices, open credit memos, foreign-currency bank and cash accounts, and any G/L account you flag as revaluable. For each open item it compares the local-currency amount originally posted against the amount that the still-open balance would represent at the revaluation rate, and calculates the unrealised difference.

Results land in a preview screen before anything is posted. The preview shows the run per currency, per Business Partner, per account and per document, with drill-down to the underlying document so a reviewer can trace any number back to its source. Nothing reaches the ledger until the run is confirmed.

Posting and reversal

On confirmation the add-on posts a Journal Entry through the DI API or Service Layer into the accounts you configure — separate unrealised gain and unrealised loss accounts, split by currency if you want that granularity, with the correct Business Partner, project code, cost centre and dimension values carried through from the source documents. The reversal entry for the following period is created and dated automatically, so the accrual cannot be left stranded.

When the invoice is eventually settled, the add-on identifies the realised difference on the Incoming or Outgoing Payment, reverses the unrealised portion previously accrued against that document, and posts the realised gain or loss to its own account. Realised and unrealised movements are never conflated.

Reporting

Delivered reports cover the revaluation run itself, unrealised exposure by currency and Business Partner, realised gain and loss by period, and a rate history report showing which rate was used where. Reports are provided as Crystal Reports layouts inside SAP Business One so they run from the standard reports menu, plus a query-based view for anyone who prefers to pull the data into a spreadsheet.

Who this is for

Distributors and manufacturers buying in one currency and selling in another. Groups running several company databases with different local currencies. Service businesses invoicing overseas clients in the client's currency. Any SAP Business One site where the auditor has asked how the FX revaluation was calculated and the honest answer is "a spreadsheet".

Technical approach

The add-on is built against SAP Business One 10.0 on both SQL Server and SAP HANA, on-premise or cloud-hosted. Business logic runs through the Service Layer where REST is appropriate and the DI API where the object model requires it; reads use views and queries appropriate to your database platform. Extension points use User-Defined Fields, User-Defined Tables and User-Defined Objects so your data stays inside your company database and is visible to standard SAP Business One tools. No transaction is written outside SAP's own object layer, which means posted documents behave exactly like manually entered ones for audit, reconciliation and period-close purposes.

How delivery works

1. Scoping call. We walk your chart of accounts, the currencies you transact in, your rate source, your period-close calendar, and how you currently treat realised versus unrealised movements. We look at your actual company database structure, not a generic template. 2. Fixed quote. You receive a written scope with the accounts, currencies, reports and approval flows the build will cover, at a fixed price. Anything outside that scope is priced separately before work starts. 3. Build. ECOSIRE builds the add-on to that scope. Typical lead time is two to four weeks from sign-off, depending on how many currencies, accounts and rate sources are in scope. 4. Install into your test company. We install into your test or sandbox company database first, load a representative set of your own open items, and run a revaluation you can reconcile against your existing spreadsheet. You sign off on the numbers before production is touched. 5. Install into production. Once test sign-off is complete we install into the live company database, configure the accounts and the schedule, and stand by for the first live period-close run. 6. Support. A support window is included from production go-live, covering defect fixes, configuration questions and assistance with the first live close.

This is a build-to-order product. Nothing is downloaded and nothing is pre-built — the add-on is constructed for your chart of accounts, your currencies and your close process after the quote is accepted.