Bank Forward, Price Buffer or Embedded Hedging: Which One Fits Your Business?

In short
Businesses that sell or buy in other currencies usually handle FX risk in one of four ways: absorb it, add a currency buffer to their prices, use bank forward contracts, or use embedded hedging through an API.
A price buffer is simple, but it makes prices less competitive and still doesn’t protect the margin when the market moves further than expected.
Bank forwards work well for a few large, predictable payments. They are harder to use for thousands of small transactions or for plans that change.
Embedded hedging, like Grain, gives every booking, order or invoice its own guaranteed rate through an API, and handles changes and cancellations automatically.
What problem are all these options trying to solve?
Every option on this list tries to solve the same problem: the gap between the day a price is set and the day the money moves. In that gap, the exchange rate keeps moving, and so does the margin. This is foreign exchange risk, also called FX risk or currency risk. For a full explanation of the gap and how Grain closes it, see How Grain works.
The right way to handle FX risk depends on three things: how many transactions a business has, how often its prices change, and how much its plans change after a price is set.
What happens if a business does nothing about FX risk?
If a business does nothing, it absorbs every currency move. That can sound like a fair bet, because the market can move either way. But the two sides are not equal. When the market moves in the business’s favor, it earns a little extra margin, by luck. When the market moves against it, it can lose the whole margin on every deal it has already priced. For a business with thin margins, a few bad months can put the business itself at risk.
Here is a simple example. A business that keeps a 3% margin on each sale faces a 5% currency move against it. It now loses money on every sale it priced before the move, and it can’t raise prices on deals that are already done. (Illustrative example.)
Doing nothing costs nothing up front, which is why many businesses start here. The cost shows up later, as profit that is hard to predict and hard to explain, or as a loss that arrives all at once.
Doing nothing can make sense when FX is a very small part of the business, or when money comes in and goes out in the same currency at the same time. When income and costs match like this, it is called natural hedging.
Is adding a currency buffer to prices a good way to handle FX risk?
A currency buffer means adding a few percent to prices, just in case the exchange rate moves. It is the easiest option to set up, and many businesses use it because they don’t know the true cost of FX on each deal.
But a buffer has two problems. First, it makes prices higher than they need to be, which can cost sales to a competitor who prices closer. Second, it is a guess. If the market moves more than the buffer, the margin is still lost. And when the market moves less, the business has charged its customers for a risk that never came. This is sometimes called FX revenue leakage: money that leaks out of every sale without showing up in any report.
Are bank forward contracts the best way for a mid-size company to manage currency risk?
A bank forward contract locks an exchange rate today for a fixed amount on a fixed date in the future. For a business with a few large payments that are known well in advance, a forward with a bank can work well. The rate is certain, and the budget is protected.
Forwards get harder to use when the business looks different. Each contract is usually booked separately, often by phone or through a bank portal. When an amount or a date changes, the contract may need to be changed or closed early, which can take time and cost money. Small transactions are often too small to hedge one by one, so they are grouped together and hedged on a forecast. And when an order is cancelled, the forward behind it no longer matches a real payment. Banks can also offer FX options, which protect against bad moves for an upfront cost, but they add complexity of their own.
What is embedded hedging?
Embedded hedging means FX hedging is built into the systems where deals happen: the booking engine, the checkout, the ERP or the invoicing system. Instead of booking hedges by hand, every transaction gets a guaranteed rate automatically, through an API, the moment it exists.
With Grain, the rate a business quotes at is the rate it hedges at and the rate it settles at. Changes are handled through the same API: a payment that comes early, a payment in parts, or an order that is cancelled. When an order cancels, Grain takes the impact, with no swap, no amendment, and nothing in the business’s P&L. Grain works on any transaction size, even micro-transactions, so ten transactions a month and ten thousand are handled the same way.
How do the four options compare?
Do nothing | Price buffer | Bank forward | Embedded hedging (Grain) | |
|---|---|---|---|---|
Setup effort | None | Low | Medium to high, often manual | An API or a file upload, then automatic |
Forecast needed? | No | No | Usually yes | No, each transaction is covered as it happens |
Protects the margin? | No | Only up to the size of the buffer | Yes, for the amount and date booked | Yes, on every transaction |
Effect on prices | None | Higher prices | None | None, prices can stay close |
Small transactions | Not covered | Covered by the buffer | Usually grouped, not hedged one by one | Each one covered, even micro-transactions |
Changes and cancellations | Not relevant | Not relevant | May need a change or an early close | Handled automatically. Grain takes the impact of cancellations |
Visibility | Low | Low | Per contract | Every position, live, in one dashboard |
Which option fits which business?
FX is a very small part of the business: doing nothing, or relying on natural hedging, may be enough.
A few large payments, known well in advance: a bank forward can do the job.
Prices that change often, many transactions, thin margins: this is where embedded hedging fits best. A buffer costs sales, and booking a forward for every deal by hand doesn’t scale.
Plans that change after the price is set: look for a setup that handles early payments, partial payments and cancellations automatically.
Many businesses combine options. For example, they cover part of a season’s forecast up front, and every new order as it comes in. See How Grain works for the three hedging approaches and how they fit together.
Frequently asked questions
What are the alternatives to using my bank for FX hedging?
The main alternatives are adding a currency buffer to prices, matching income and costs in the same currency (natural hedging), and embedded hedging through an API, like Grain. Embedded hedging gives every transaction its own guaranteed rate, without booking each hedge by hand.
Is a currency buffer cheaper than hedging?
A buffer has no upfront cost, but it is not free. It makes prices higher, which can cost sales, and it doesn’t protect the margin when the market moves more than the buffer. The real cost is the sales and margin it loses over time.
Can I hedge small transactions?
With traditional bank forwards, small transactions are usually grouped and hedged on a forecast. With embedded hedging through an API, each transaction can be covered on its own. Grain works on any transaction size, even micro-transactions.
What happens to a hedge if an order is cancelled?
With a bank forward, the contract may need to be changed or closed early. With Grain, cancellations and reduced amounts are handled automatically, and Grain takes the impact: no swap, no amendment, and nothing in the business’s P&L.
Do I need a treasury team to use embedded hedging?
No. Because hedging runs automatically through the API, nobody has to place a trade. The finance team sets the rules once, like which currencies to cover and how much, and sees every position in one dashboard. ________
Related reading: How Grain works
Talk to our team to see which option fits your business, on your own numbers.



Comments