Book a demo

Foreign-currency supplier invoices: checking the rate before you key

A foreign-currency invoice carries two numbers that decide what goes into your books: the amount in the supplier’s currency, and the exchange rate that turns it into ringgit. SQL Accounting keeps each currency’s rates in Tools > Maintain Currency, and each invoice carries its own rate. Agree one rule for which rate you use, check it before you save, and never change it later to match the payment.

Last checked against eStream’s SQL Accounting documentation (the Tools and Supplier usage guides and the Customer FAQ).

The two numbers on the paper

An invoice from a supplier abroad states its amounts in their currency: US dollars, Singapore dollars, Chinese yuan. Your books are in ringgit, so every foreign amount needs a rate. Some invoices print the rate, or a ringgit total beside the foreign one. Many print neither.

A wrong currency or a wrong rate does not look wrong on the screen. It looks like a normal invoice for the wrong amount of ringgit, and nobody notices until the payment does not match.

Where SQL Accounting’s rate comes from

  • The supplier’s currency is set on the supplier, in Maintain Supplier.
  • The rates are kept in Tools > Maintain Currency.
  • On the invoice, eStream’s Tools guide, using a customer’s invoice as its example, says the rate follows the Maintain Currency setting and can still be changed on the invoice. Its Customer FAQ shows a supplier invoice in US dollars with its own rate and a ringgit total: USD 100 at 3.00 is RM 300.

Pick one rule, and keep it

Which rate your books use is a decision for whoever looks after your accounts. Common rules are the rate on the invoice date from one named source, or one fixed rate for the month. What matters is that there is one rule, it is written down, and everyone who keys uses it. Mixing the supplier’s printed rate on one invoice with the bank’s rate on the next makes the books disagree with themselves.

Four checks before you save

  1. The currency. The code on the invoice matches the supplier’s currency in SQL Accounting. A supplier in China may print RMB; the currency code is CNY.
  2. A rate that looks like that currency’s. A misplaced decimal is the costly slip: a rate of 47.20 where 4.72 was meant makes the invoice ten times bigger in ringgit.
  3. The sums. If the invoice prints a ringgit total, the foreign total times the rate should come to it, give or take rounding.
  4. No rate printed. Use your rule’s rate, and write the rate and where it came from on the paper or in the file name, so the next person can see why it is there.

The rest of the supplier invoice checks apply as they do to a ringgit invoice.

When you pay

You pay later, at a different rate. When the payment is knocked off against the invoice, SQL Accounting posts the difference as a gain or loss on foreign exchange: eStream’s Tools guide lists the foreign exchange gain and loss accounts that customer and supplier payments post to, and its Customer FAQ works through a supplier invoice paid at a different rate.

So the invoice keeps its own rate. Do not change it afterwards to make the payment match: the gain or loss is the real difference between the two dates, and it belongs in the books.

At the end of the month

A month-end statement in the supplier’s currency is checked the same way as any other: see supplier statement reconciliation. Valuing what is still unpaid at a closing rate is part of preparing your accounts; ask whoever looks after them when they want it done. eStream’s Customer FAQ shows how it is done for customers, from the aging report with a closing rate.

Sources

  1. eStream, SQL Accounting documentation: Tools guide, opened
  2. eStream, SQL Accounting documentation: Supplier guide, opened
  3. eStream, SQL Accounting documentation: Customer FAQ, opened

See it on a real invoice

Book thirty minutes and watch IgnisArc Finance read, check and post a supplier invoice into SQL Accounting.

Book a demo