REDA Setup (CMDT)
A handful of settings in REDA apply to your whole organisation rather than to any one company — the kind of thing that's either on or off for everyone. These live in REDA Setup. It's deliberately small, and that's by design: REDA keeps only true "infrastructure" here, and pushes every setting that's a business choice down to the company or region where it belongs. Understanding that split is the real point of this article.
Access you'll need. Changing these settings requires the Accounting Admin v2 or Accounting Controller v2 permission set (and, because they're org-wide, are best tested in a sandbox first). The Accounts Payable v2, Accounts Receivable v2, and Read Only v2 sets don't configure them.
The rule that keeps it small
Why does this matter to you? Because it tells you where to go to change something. Want to turn on withholding tax for one subsidiary? That's a business policy — it's on the entity, not here. Want to switch the whole org into multi-currency mode? That's infrastructure — it's here. The split means you never have to wonder whether a setting affects one company or all of them.
Here's the split in practice, using settings covered elsewhere in this Help Center:
| You want to… | Scope | Where it lives |
|---|---|---|
| Run the org in multi-currency mode | Everyone | REDA Setup — this article |
| Withhold tax on one company's purchases | One company | Entity — WHT Enabled (Purchase), see Policy Settings |
| Enforce budgets on purchase orders for one company | One company | Entity — Enforce Budget Controls |
| Auto-generate a PDF when invoices post | One company | Entity — the Auto-Gen PDF switches |
| Post AR/AP documents as summarised ledger entries | One region | Territory — Grouped Posting Enabled, see Grouped vs Line-Level Posting |
What a setting looks like
Each REDA Setup record is a single named switch with a few descriptive fields:
| Field | Purpose |
|---|---|
| Value | The setting's value (e.g. true / false). |
| Category | Groups related settings in the setup screen. |
| Data Type | How the value is interpreted and displayed. |
| Description | A plain explanation of what the setting controls. |
| Is Active | Whether the setting is currently in effect. |
| Sort Order | Where it appears in the list. |
What actually lives here
The headline setting — and the one you're most likely to touch:
| Setting | Shipped as | What it does |
|---|---|---|
| Multi Currency Enabled | OFF | Tells REDA to run in multi-currency mode. It's here, and not on a company, precisely because you can't have one company in multi-currency mode and another not — it's all-or-nothing for the org. (Turning it on has prerequisites — see Enabling Multi-Currency.) |
That "all-or-nothing for the org" test is exactly what qualifies a setting for REDA Setup. If the honest answer to "could two of my companies want this differently?" is no, it belongs here.
Where it lives, and how to change a setting
You don't hunt through Salesforce Setup for these — REDA surfaces them in its own admin screen:
Open the Financial Admin Console
From the App Launcher, open the Financial Admin Console tab — REDA's home for administration.
Go to Financial Setup → REDA Application Settings
Expand the REDA Application Settings section. Each setting is listed with its category and data-type badges, a plain-English description, and its current value.
Flip the toggle and Save
Boolean settings show a toggle. Change it and click Save — you'll briefly see "Deploying via Metadata API…" while Salesforce applies the configuration, and the change reaches the whole org within a few seconds.
That deployment step is the visible clue that these records are metadata rather than ordinary data — configuration that behaves like part of the app. Because they're org-wide and read on important paths (such as deciding currency mode), change them deliberately, and test in a sandbox first where you can.
Frequently asked questions
Almost certainly not. Anything that can vary by company is a business policy and lives on the entity (or territory). REDA Setup is only for settings that are the same for the entire org. See Entity-Level Policy Settings.
That's intentional. Keeping org-wide settings to a minimum — and putting business policy where it can vary by company — means fewer surprises and clearer control. A short global-settings list is a feature, not a gap.
No — it's configuration metadata, managed through the Financial Admin Console → Financial Setup → REDA Application Settings screen. Your administrator changes it, and because it's org-wide, it's worth testing in a sandbox before applying in production.
No — the switch is one of three prerequisites. Your Salesforce org itself must have multi-currency (with Advanced Currency Management) enabled, and every entity needs its functional currency and an FX Gain/Loss account. The whole checklist, in order, is in Enabling Multi-Currency.
Where to go next
- Enabling Multi-Currency — the full walkthrough for the one setting that lives here.
- Entity-Level Policy Settings — the per-company switches that deliberately don't live here.
- Administration — the rest of the Financial Admin Console.
Was this article helpful?