What has to be decided before you automate cross border orders

When a process involving foreign currency is up for automation, the first question is almost always aimed at technology. Which system, which rate source, which interface. That is the question with the least influence on price and outcome. The effort is driven by commercial decisions that, in many companies, are written down nowhere, because until now they lived in one person's head.

As long as a clerk writes the export invoices herself, she makes those decisions every day without ever discussing them. An automation cannot do that. It needs a rule, and if nobody gives it one, it takes whatever the system defaults to.

Four decisions that have to exist before anything is built

The first concerns the rate. There is no single correct exchange rate. There is the European Central Bank reference rate, the bank's own rate, the rate stored in the ERP, and the rate accounting is required to use for value added tax. Those figures differ, and each is correct for its purpose. What has to be settled is which source applies to which purpose.

The second concerns timing. A rate taken on the day of order confirmation, on the day of shipment, on the invoice date and on the date of payment produces four different amounts for the same transaction. More important than the source is the question of when the rate is frozen, and where that frozen value is stored. If it is not stored but recalculated every time somebody opens the record, the amount on an invoice you already sent changes after the fact.

The third concerns rounding. Do you round at line level and then add up, or add up and then round? Both are defensible, and they produce different results. On an invoice with many lines the gap is a few cents. Those few cents are exactly what stops an incoming payment from being matched automatically and sends a dunning letter to a customer who paid weeks ago.

The fourth concerns responsibility. Who carries the currency risk between order and payment, you or the customer? That is a commercial decision, not a technical one. It belongs in your pricing, and it has to be settled before anything is built, because it determines which amount is carried forward at all.

Why these points drive the price

A supplier who quotes for a foreign currency process without knowing those four points is pricing the normal case. The normal case is one invoice, in one currency, with two decimal places, no partial payment, no credit note, and no rate movement in between.

The effort sits in everything next to it. A partial payment that arrives at a different rate than the invoice. A credit note against an invoice from last quarter that has to use the rate of that time. A currency that does not use two decimal places. An amount that travels through an interface without a currency code and is silently read as euros at the other end.

Each of these is a commercial decision somebody inside your company has to make. No supplier can make them for you, and a fixed price only becomes sound once they exist in writing. Without that basis one of two things happens: the supplier prices in a buffer that you pay for, or prices tightly and invoices the rest as a change later.

What the automation genuinely takes off your desk

Once those four decisions exist, the benefit is substantial, and it does not lie in doing arithmetic.

A process can store every amount together with its currency code and the rate that was used, instead of passing on a bare number. It can freeze the rate at the agreed moment and keep that value attached to the transaction, so an invoice you already sent keeps its amount. It can match incoming payments that differ from the invoice by rounding differences or bank charges, and it can hold a tolerance threshold above which a person decides.

Above all it can stop rather than guess. When a currency code is missing, or no rate exists for the day required, stopping is the correct behaviour. A transaction parked for clarification costs ten minutes. A transaction that runs through on a silently assumed rate costs a search during the quarterly close.

How to produce the basis yourself

Take the export orders of the last three months and sort them into those that ran without a query and those where somebody had to step in. For every intervention, note the decision that was taken and the rule behind it. Add a list of the currencies that actually occur and the systems that see the same invoice.

That sheet of paper is the basis for comparable quotes. It costs you half a day and it replaces three rounds of meetings.

Sophera Consulting starts exactly there: first the review of the real transactions, then a written record of rate source, cut off date, rounding rule and intervention thresholds, then the build for a fixed price, with no subscription and with documentation at handover. The entry point is the free Automation Check.

The recommendation

For a process involving foreign currency, do not ask for a price first. Settle the four points instead: rate source per purpose, the moment the rate is frozen, the rounding rule, and who carries the currency risk.

Those four lines shape the effort more than any choice of platform. They make quotes comparable, they make a fixed price that holds possible, and they are the difference between a process that removes work and one that triggers a search every quarter.