remoteEaze

FX, fees, commissions, and rounding

How transaction values, overrides, charges, and rounding are determined.

remoteEaze stores the entered amount, the Account-currency amount, the company base-currency amount, the FX evidence used for each conversion, and the commission decision associated with each applicable batch.

System FX rates

When a line needs currency conversion, System is the default FX source. Select the required System Rate Type: Buy, Sell, or Mid. The server resolves the applicable configured rate against the Transaction Posting Date; users do not type a rate while System is selected.

The line preview shows the Account-currency and base-currency equivalents. A missing rate prevents a balanced, valid transaction from being saved.

Enter a non-system rate

You need Override FX Rate in addition to the permission used to create or edit the Transaction.

  1. On the posting line's FX Rate panel, change Source from System to Manual, Central Bank, or Third Party.
  2. Enter the positive Rate and Rate Date.
  3. Select an Override Reason: Customer Negotiated, Special Approval, or Other.
  4. For Central Bank or Third Party, enter the Source Name.
  5. Enter an Explanation or Source / Approval Reference. Both may be supplied when useful.
  6. Review the displayed Comparable System Mid and percentage deviation.

The Rate Date cannot be after the Posting Date. Changing FX evidence on one line synchronizes that evidence to lines in the same batch that use the same transaction currency.

On the saved record, expand Override details to review the source, reason, reference, explanation, rate date, comparable system Mid, and deviation.

Conversion and rounding evidence

A conversion can have two legs:

  1. transaction currency to Account currency;
  2. Account currency to company base currency.

remoteEaze rounds posted values to the target currency's configured decimal places using half-even rounding. The transaction detail keeps the exact source amount, exact converted amount, posted converted amount, and rounding delta for each conversion leg. These values explain why the posted value can differ from an unrounded manual calculation.

Balance is checked on the posted base-currency values for every batch. A user cannot rely on the combined transaction total to offset an imbalance in a different batch.

Commission Fee Review

When a batch's Transaction Code has active Authorized commission setup, Commission Fee Review appears before save or submission. Paying Accounts are derived from the commission's configured Debit or Credit payer side.

For each applicable commission:

  • choose Apply to retain the calculated charge;
  • choose Waive only when the commission is configured as waivable;
  • optionally record a Waive reason for the audit trail.

Every applicable fee requires an explicit decision. A commission can also show No charge when no configured band applies, the exact amount rounds to zero, or a required pricing rate is unavailable. All-GL batches do not produce transaction commissions.

Commission posting occurs after the main transaction posts. The saved record's Commission Decisions shows the batch, decision, payer side, paying Accounts, rate basis, and waiver note. Its Calculation audit preserves exact fee and tax calculations separately from the currency-rounded ledger values.

Commission and tax behavior is configured under Taxes and commissions; transaction users review the resolved result rather than changing those definitions here.

On this page