Floemdata
ERP & SAP B1

SAP B1 Multi-Currency and Exchange Difference Reports

A euro invoice is paid in lira and the reports show two different amounts. What to watch in SAP B1 when reporting rates, foreign amounts and exchange differences.

Floemdata · · 5 min read
Two rulers marked with a circle coin and a rounded-square coin; their ticks drift apart toward one end

You invoiced a customer in euro. The invoice's lira equivalent was computed at that day's rate; the payment arrived weeks later at a different rate. The sales report shows one amount, the collections report another. Both can be correct. The problem is that the report does not say which amount it shows at which rate.

One document, three amounts

The SAP Business One developer documentation defines the rate and amount of a sales document in separate fields. The document's rate is DocRate (in SAP's words, the exchange rate with local currency for the document), the total in foreign currency is DocTotalFC, and the total in system currency is DocTotalSy; the document's currency sits in DocCur. Sources: SAP Business One SDK Help, DocRate and DocTotalFc.

For reporting this means one document carries both a foreign amount and a local amount, and they answer different questions. How much does the customer owe me? is answered with the foreign amount; what did this sale add to my lira revenue? with the local amount.

Rule 1: do not add different currencies

A report that adds 100 euro and 100 lira and writes '200' is wrong even with a currency column. Give totals per currency, or convert to one local currency and state the rate you used.

Rule 2: which date's rate?

  • Document-date rate: shows the value at the moment of sale; the natural choice for revenue reports.
  • Report-date rate: shows what a receivable is worth in lira today; meaningful for receivable and payable balances.
  • Holidays and weekends: the rate table may have no entry for the day. Set an explicit rule (for example, the previous working day's rate) and use the same one in every report.

What an exchange difference is

It is the gap between the lira equivalent at invoice time and at payment time. Fictional example: a 10,000 euro invoice at 35.00 on the invoice date is 350,000 lira. At payment the rate is 36.00, so 360,000 lira. The realised exchange difference is +10,000 lira. The difference that arises when foreign-currency balances still unpaid at period end are revalued is a separate concept. Do not mix the two in one report.

The bookkeeping and tax treatment of exchange differences is a matter for your accountant; this article covers only the reporting side.

Where Floemdata stands

In sales and payment documents from SAP B1, Floemdata carries the document currency and document rate into the Silver layer; sales lines also hold the line's foreign amount. SAP's dated rate table (ORTT) is loaded as a separate Silver table. In batch and serial tracking, amounts are computed in TRY, USD and EUR: if the document is already in that currency its own rate is used, otherwise the latest dated rate on or before the document date (the previous rate for a weekend).

We did not find a report that computes exchange differences, whether realised or from revaluation, and we did not verify that sales and receivable reports give a combined total converted to one currency. These behaviours were tested against mock SAP data; they were not separately verified on real customer data.

To begin, pick one customer's foreign-currency invoice and its payment and set the two lira amounts side by side: does the gap come from the rate, or from something else? Questions are welcome at info@floemdata.com or via Floemdata.

← All guides