Plan a messaging budget when rates and payments use different currencies
Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.
A messaging budget approved in pounds can look overspent even when the underlying dollar-denominated usage barely changed. The opposite can happen too: a favourable conversion can conceal a real increase in messaging costs. Comparing the approved total with a bank debit tells you the size of the difference, but not what caused it.
The practical solution is to keep three views: the cost in its source currency, that cost translated at the original planning rate, and the amount actually paid in the budget currency. Show documented conversion fees separately. This creates a bridge from estimate to payment without treating every difference as a usage problem.
The worked example below uses a fictional dollar-denominated messaging charge and a pound-denominated budget. All amounts, exchange rates, fees and operating details in the example are hypothetical. The method is for operational budgeting and reporting, not exchange-rate forecasting or hedging decisions.
1. Define what the budget is actually comparing
Before selecting an exchange rate, identify the cost being measured. A rate-card currency, invoice currency, payment-account currency and reporting currency are not necessarily the same.
- Rate-card currency: the currency attached to the underlying messaging prices.
- Invoice currency: the currency in which the supplier requests payment.
- Settlement currency: the currency debited from the payment account.
- Budget currency: the currency used for approval and internal comparison.
If the invoice is already converted from the rate-card currency, record that conversion as its own stage where evidence is available. A later bank conversion is a different stage. Do not describe the entire difference as a bank fee.
Also define the cost boundary. Keep provider or platform subscriptions, Meta messaging charges and AI usage in separate lines. They may use different currencies, billing periods and charging methods. Combining them before conversion makes it difficult to determine whether a larger debit came from messaging activity or another service.
For WhatsApp, Meta pricing depends on delivered messages, message category and recipient market. Check the current official pricing information for exact rates and applicable exceptions. Do not treat every planned or sent message as a billable message.
A useful budget header therefore states the service period, included cost lines, budget currency and treatment of separately itemised taxes or adjustments. Keep those boundaries unchanged when comparing the estimate with actuals.
2. Write down the conversion basis before approval
An exchange-rate number without a direction is an avoidable source of error. Write the planning assumption as an equation, not just a currency pair.
Hypothetical planning convention: GBP 0.8000 per USD 1; multiply USD costs by 0.8000 to obtain GBP costs.
For each currency pair, retain these fields with the budget:
- The planning rate, its direction and the rounding rule.
- The date the assumption was adopted.
- The source or internal approval record supporting that assumption.
- The period for which the assumption will remain fixed.
- Whether conversion fees have a separate allowance.
- The owner authorised to approve a revised forecast.
The planning rate is a comparison tool, not a prediction of the eventual settlement rate. Keeping it fixed allows the team to ask a stable question: what would actual source-currency costs have been worth under the original budget assumptions?
If an updated forecast uses a new exchange assumption, preserve both versions. Label one as the original approved budget and the other as the latest forecast. Replacing the original rate silently makes a budget look more accurate without explaining what changed.
Round consistently. Retain enough precision for calculations, then round reported currency amounts according to the chosen reporting convention. Otherwise, repeated line-by-line rounding can produce a small unexplained remainder.
3. Build the source-currency estimate before translating it
Start with the messaging estimate in the currency in which its underlying charges are expressed. Retain the usage assumptions needed to rebuild that estimate: relevant billable quantities, category and recipient-market mix, applicable rates and any supported exceptions.
A single total is enough to translate a budget, but not enough to explain it later. If the underlying estimate is just “messaging: USD 1,000,” a higher invoice cannot reliably be attributed to more usage rather than a different category mix or changed rates.
For an operational variance analysis, use a consistent calculation order:
- Calculate the approved source-currency estimate.
- Recalculate using actual billable usage and mix, while retaining the planning messaging rates.
- Apply the actual applicable messaging rates to that actual usage.
- Reconcile the result to the invoice, showing credits or other adjustments separately.
This order assigns the interaction between usage and rate changes to the rate-change line. Another order could assign it differently. Neither convention should be hidden: document the chosen order and apply it consistently.
If detailed usage records are unavailable, stop at a combined source-cost variance. You can still distinguish source-cost changes from currency effects, but you cannot honestly claim that the source-cost increase was entirely caused by volume.
4. Use this filled hypothetical currency bridge
Fictional worked example: a team approves a messaging-only budget for a hypothetical April service period. Messaging charges are invoiced in USD and paid from a GBP account. Subscription charges, AI usage and taxes are outside this bridge and tracked separately.
The approved estimate is USD 1,000.00. The planning conversion is GBP 0.8000 per USD 1, with a separate GBP 12.00 conversion-fee allowance. The approved total is therefore GBP 812.00.
At close, actual usage and mix valued at the original messaging rates would cost USD 1,075.00. Applying the actual applicable messaging rates produces an invoice of USD 1,100.00. The invoice is paid in two parts, with separately documented conversion fees.
HYPOTHETICAL CURRENCY BRIDGE Service period: April, fictional example Scope: messaging charges only Budget and payment currency: GBP Source and invoice currency: USD Planning basis: GBP 0.8000 per USD 1 Variance sign: positive = above budget APPROVED ESTIMATE Source-currency messaging estimate USD 1,000.00 Converted at planning rate GBP 800.00 Separate conversion-fee allowance GBP 12.00 Approved total GBP 812.00 SOURCE-CURRENCY RECONCILIATION Original estimate USD 1,000.00 Actual usage/mix at planning rates USD 1,075.00 Usage/mix difference USD 75.00 Actual invoiced messaging charge USD 1,100.00 Messaging-rate difference USD 25.00 Unreconciled invoice adjustments USD 0.00 ACTUAL COST AT PLANNING EXCHANGE RATE USD 1,100.00 x 0.8000 GBP 880.00 DOCUMENTED SETTLEMENTS Payment A: USD 600.00 x 0.8100 GBP 486.00 Payment A: separate conversion fee GBP 8.00 Payment A: total debit GBP 494.00 Payment B: USD 500.00 x 0.8320 GBP 416.00 Payment B: separate conversion fee GBP 10.00 Payment B: total debit GBP 426.00 Converted principal, both payments GBP 902.00 Documented conversion fees GBP 18.00 Total paid GBP 920.00 BRIDGE FROM APPROVAL TO PAYMENT Approved total GBP 812.00 Usage/mix: USD 75.00 x 0.8000 GBP 60.00 Messaging rates: USD 25.00 x 0.8000 GBP 20.00 Currency effect: 902.00 - 880.00 GBP 22.00 Fee variance: 18.00 - 12.00 GBP 6.00 Total paid GBP 920.00 Total variance: 920.00 - 812.00 GBP 108.00 Unexplained residual GBP 0.00
The interpretation is specific: GBP 80.00 of the increase came from source-currency messaging costs, GBP 22.00 from settlement conversion relative to the planning basis, and GBP 6.00 from conversion fees above their allowance. Calling the whole GBP 108.00 a usage overrun would misdirect the next budget discussion.
The effective settlement conversion for principal is GBP 902.00 divided by USD 1,100.00, or GBP 0.8200 per USD 1. It is calculated from the actual amounts, not by taking a simple average of the two payment rates. Fees remain outside that calculation.
5. Choose a reporting convention that answers two questions
Most teams need both a performance view and a cash view. Trying to make one number answer both questions creates confusion.
Performance view: translate actual source-currency costs at the original planning rate. In the hypothetical example, that is GBP 880.00 compared with a GBP 800.00 messaging estimate. This isolates the change in messaging costs from settlement currency movement.
Cash view: report converted principal plus documented fees. In the example, that is GBP 920.00 against the GBP 812.00 total approval. This answers how much funding the payments consumed.
Show these side by side, connected by the bridge. The performance view deliberately does not equal the bank debit; the currency and fee lines explain why.
A service-period report and a payment-period report may also differ. An invoice can relate to one month while its payments occur later. Attach settlements to the relevant invoice rather than comparing one month's usage with unrelated bank debits from that month.
When an invoice remains unpaid, label its converted amount as provisional and state the conversion basis used. Do not present it as an actual settlement. When payment arrives, replace the provisional conversion in the settlement view and preserve the original planning-rate comparison.
6. Keep observable fees separate from unknown conversion costs
A payment record may show a separate fee, an applied exchange rate, only a total debit, or some combination. Report only the detail supported by the evidence.
If the source amount and converted principal are known, you can calculate an effective conversion rate. If the total debit also includes an unidentified charge, dividing that debit by the source amount produces an all-in conversion factor, not a clean exchange rate.
Do not invent a fee by comparing the payment with an unrelated reference rate. A difference may reflect the applied conversion basis, timing, embedded margin or another charge that your records do not identify.
- Separate fee documented: record it in the fee line and retain the payment evidence.
- Fee embedded but not quantified: label the difference as an unseparated conversion effect.
- Only a total debit available: show the combined settlement difference and request supporting detail.
- Invoice already converted: retain the original source amount if available; otherwise state where the observable bridge begins.
This makes a less detailed report more trustworthy than a precise-looking breakdown based on unsupported assumptions.
7. Recover when the bridge does not reconcile
A non-zero residual is a request for investigation, not a reason to force the currency line to balance.
First check scope and timing. Look for partial payments, an invoice paid twice, credits applied to another period, or subscription and AI charges accidentally included in the messaging debit. Then check conversion direction and whether a fee was counted both inside the debit and as a separate addition.
For multiple invoices or currencies, build one bridge per source currency and invoice group before consolidating into the budget currency. Adding USD and EUR amounts into one “foreign currency” total destroys the basis for a meaningful exchange calculation.
If a refund arrives later, link it to the original charge and record its actual conversion separately. Do not assume the refund reverses the original budget-currency amount exactly.
When evidence is missing at close, retain an explicitly labelled unresolved amount with an owner and follow-up date. The report should distinguish a known cost increase from an unexplained reconciliation difference. Once resolved, record the correction without rewriting the original approval.
8. Make the next close testable
For the next reporting cycle, select one completed messaging invoice and build this bridge before expanding the process. Have the messaging owner validate the source-cost calculation and the payment owner validate the settlement amounts.
- Record the approved source estimate, planning rate and fee allowance.
- Rebuild actual source costs, separating usage/mix from messaging-rate changes where evidence permits.
- Attach each payment and its documented conversion details to the invoice.
- Calculate the source-cost, currency and fee variances.
- Check that approval plus explained variances equals payment, subject only to the stated rounding convention.
The measurable outcome is a reconciled payment with no unexplained residual—or a clearly assigned unresolved item—not a more favourable headline variance. Once that is working, apply the same structure to the remaining currency and cost lines. Budget owners can then decide whether the next estimate needs different usage assumptions, a revised conversion basis or a more realistic fee allowance, without confusing those decisions.
Put the next conversation to work.
Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.
Explore Communications