Your Setup Roadmap
This is your map for setting up REDA Financials after installation — the whole journey, in the order that works, with a link to the detailed guide for every step. You are configuring an enterprise-grade accounting platform that runs natively on Salesforce, with AI, automations and your CRM built into the same system — so the sequence below is less about wiring software together and more about making a series of accounting decisions in the right order. Follow it top to bottom and each step builds on the last. Tick each item off as you complete it — your progress is saved on this page.
Access you'll need. Working through the roadmap requires the Accounting Admin v2 permission set — the Financial Admin Console is visible to Accounting Admins (Accounting Controller v2 and Read Only v2 can reach it; Accounts Payable v2 and Accounts Receivable v2 cannot). Installing the package and assigning licences also needs a Salesforce System Administrator.
1. Switch it on
- Install the package. Install REDA Financials (a sandbox first, then production). — Installation & Upgrades
- Activate your subscription. Paste your licence key on the Subscription tab. — Subscription & Plans
- Assign user licences. Licence each user who will post transactions. — License Assignment
- Assign permission sets. Give each user the role they need, keeping duties separated. — Permission Set Assignment · Segregation of Duties
2. Lay the accounting foundation
- Set your currency mode. Choose single- or multi-currency before any transactions. — Financial Setup
- Seed your chart of accounts & tax. Seed the global chart (it auto-creates your accounting defaults) and each country’s tax pack. — CoA & Tax Seeding
- Review your accounting defaults. Confirm each default GL account is right for your policy. — Global Accounting Defaults
- Define your territories. Create at least one — every entity belongs to a territory. — Territory Management
- Create your entities. Set up each legal company with its currency, defaults, basis, and fiscal-year start. — Post-Installation Setup
- Configure document sequences. Set the numbering for each entity and document type before issuing the first document. — Post-Installation Setup
- Generate accounting periods. Create a year of periods for each territory and fiscal year. — Accounting Periods
3. Add your master data
- Set up your bank accounts. Cash GL account, currency, and reconciliation defaults — plus check stock if you print checks. — Creating a Bank Account · Check Stock & Check Printing
- Set up your products and services. Build your catalogue and tax profiles so tax resolves on lines. — Creating Products
- Set up your customers and vendors. Create the Accounts and attach their tax profiles. — Setting Up a Customer · Setting Up a Vendor
- Configure payment terms. Define due-day terms and early-payment discounts. — Payment Terms
4. Documents & automation
- (Multi-currency) Set up exchange rates. Configure your rate source and daily sync. — Financial Setup
- Configure PDF templates & branding. Set up per-entity templates, logos, and payment details. — Post-Installation Setup
- Schedule your operations. Turn on the batch jobs you rely on — recurring, depreciation, auto-reversal, FX sync, aging, and more. — Operations
- Wire your approval processes (optional). Purchase Orders, Purchase and Sales Invoices, and Budgets carry an Approval Status that gates posting — connect it to Salesforce approval processes that mirror your sign-off policy. — Approval Processes
- Automate your busywork (optional). Explore what the platform can take off your team’s plate — OCR invoice capture, recurring documents, auto-matching, and Salesforce Flows on any REDA object. — The REDA AI Platform · Automating with Flows
Why this order matters
A few of these steps genuinely lock each other in — the sequence isn't a style preference. The dependencies worth knowing before you start:
| Do this first… | …because |
|---|---|
| Currency mode before any transaction | An entity's currency is locked once accounting transactions have posted for it. Deciding single- vs multi-currency later means unwinding real postings. |
| Territories before entities | Every entity belongs to a territory, and the territory on an active entity can't be changed. Territory codes themselves are also permanent once saved — name them carefully. |
| Accounting defaults before entities | Defaults are copied onto an entity once, at creation. Entities created before the defaults exist get blank GL settings you'll have to fill by hand. |
| Entities before periods | The period generator builds a fiscal calendar per top-level territory using the fiscal-year pattern you chose — and an entity's fiscal year start locks once its territory has periods. |
| Sequences before the first document | Document numbering picks up from the sequence at the moment a document is created — numbers already issued can't be renumbered retroactively. |
| Chart of accounts & tax before master data | Products point at GL accounts; customers and vendors point at tax jurisdictions and party tax profiles. Create the targets first and every lookup just works. |
5. Test & go live
- Validate in a sandbox. Run every cycle end to end and confirm the accounting before production. — Sandbox Testing Guide
- Load opening balances and go live. Reconcile your opening trial balance, then cut over. — Go-Live Checklist
Where to go next
- Creating an Entity — set up your first company.
- Creating GL Accounts — build your chart of accounts.
- Customer Setup — add the customers you invoice.
- Creating a Sales Invoice — your first receivable transaction.
- Go-Live Checklist — the final steps before going live.
Frequently asked questions
Mostly. A few things are order-sensitive — set your currency mode before any transactions, seed the chart of accounts before reviewing defaults, and create territories before entities (every entity belongs to a territory). The rest can flex to suit your team, but this sequence avoids rework.
Yes — ticking a step off is saved in your browser for this page, so you can come back and pick up where you left off. (It’s local to your browser, not shared across your team.)
Absolutely. REDA’s team can guide your implementation end to end — from configuration to data migration to your first close. Contact support@reda.one or your REDA Account Executive.
Was this article helpful?