Configure currencies and base currency
Follow this guide to add supported currencies and understand the restrictions around the system base currency. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.
Where to goSetup → Finance → Currencies
Before you startThe screen or action may be hidden when your role lacks permission, the related module is inactive, or a required setting has not been configured. Ask an administrator to review access rather than using another person’s account.
What you’ll accomplish
Add supported currencies and understand the restrictions around the system base currency. Britixo CRM keeps the result connected to the relevant customer, staff member and operational history where the feature supports those relationships. That connection is important for search, reporting, client portal visibility and future automation.
Follow these steps
- Go to Setup → Finance → Currencies using an administrator or appropriately permitted account.
- Check the current value and understand which users, records or automated processes it affects.
- Enter or select the new configuration values. Keep labels concise and use the approved business terminology.
- Where credentials, email, webhooks or cron are involved, begin with a test or sandbox configuration.
- Save the change and confirm that Britixo CRM reports success.
- Test the affected workflow with a non-critical record and with a restricted user where permissions are relevant.
- Document the operational change and use the available reset or rollback option if the result is not correct.
Fields and decisions to review
Name or referenceCheck this value against the source record before saving. If the field is optional and no verified value is available, leave it blank rather than entering placeholder data.
Date or effective periodCheck this value against the source record before saving. If the field is optional and no verified value is available, leave it blank rather than entering placeholder data.
Amount or rateCheck this value against the source record before saving. If the field is optional and no verified value is available, leave it blank rather than entering placeholder data.
Tax or currencyCheck this value against the source record before saving. If the field is optional and no verified value is available, leave it blank rather than entering placeholder data.
Status or visibilityCheck this value against the source record before saving. If the field is optional and no verified value is available, leave it blank rather than entering placeholder data.
NotesCheck this value against the source record before saving. If the field is optional and no verified value is available, leave it blank rather than entering placeholder data.
Checks before you finish
- Use consistent naming.
- Check downstream reporting impact.
- Test new finance settings on a draft transaction.
- Check whether the result should be visible to a customer contact or only to staff.
- Confirm the final status, activity entry, generated document or notification before leaving the record.
Permission and data safetyDeletion, refunds, signature clearing, module changes, payment configuration and privacy actions can affect linked records or legal history. Use the least destructive action available and follow your organisation’s approval process.
Browse connected topics:paymentexpensecheckreporttaxcurrencyapprovalinvoiceserviceclient portalnotificationsemailcustomerscustom fields
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.