Retrieve online currency rates and review logs
Fetch available exchange rates from the configured online source and audit the retrieval results before use.
What this feature does
Fetch available exchange rates from the configured online source and audit the retrieval results before use. It forms part of Britixo Enterprise CRM's Accounting & Bookkeeping module and uses the module's permission-aware controller, status and mapping flow rather than a generic spreadsheet process.
How the module flow works
The controller has get_all_currency_rate_online, get_currency_rate_online and currency_rate_logs_table actions. Online retrieval is therefore a deliberate settings workflow, not an invisible guarantee.
A successful technical response can still be inappropriate for the organisation's accounting policy.
Logs are useful for diagnosing timing and provider issues but should not expose secret credentials.
Step-by-step workflow
- Open Currency Rates.
- Choose Get All Online or retrieve an individual rate.
- Review the returned values before saving or relying on them.
- Open Currency Rate Logs.
- Investigate failed or unusual retrievals.
- Apply an approved manual rate if the online result is unsuitable.
- Retest the affected transaction or report.
Important fields and decisions
What happens after completion
After the action is saved, Britixo keeps the Accounting record connected to its source and updates the visible status or ledger data supported by this workflow. Review the saved result rather than relying only on a success message. Where the action posts accounting data, total debits and credits must balance and the accounts must match the approved mapping or manual selection.
- Open the saved record and confirm its final status.
- Review the source reference and every debit and credit line where ledger data was created.
- Use the relevant register, ageing, reconciliation or report to verify the wider effect.
Controls, checks and common mistakes
- External rates can be delayed or unavailable.
- Do not accept an implausible rate automatically.
- Protect API credentials if the provider requires them.
- Record manual override reasoning.
- Use the least destructive correction available and record the reason for material changes.
- Do not bypass a permission, approval or closed-period control by changing unrelated data.