REDA One Help Center
EN
Language
English EN Español ES Português PT Italiano coming soon Français FR Deutsch coming soon العربية coming soon
reda.one ↗
Home / REDA Financials AI / Getting Started / Best Practices / Go-Live Checklist

Go-Live Checklist

Going live on a new accounting system is the one moment you only get to do once per set of books. This checklist takes you through it in order — from installing the package to cutting over to production — so nothing important is missed and your opening numbers are right from day one. It is written for the person leading the implementation: the administrator, controller, or implementation partner.

Getting there. Most of this work happens in the Admin Console: open the App Launcher (the grid icon at the top-left of any page) → REDA Financials Admin → the Financial Admin Console tab, which is where you activate the subscription, seed the chart of accounts and tax rules, define territories, and generate accounting periods. The very first steps (installing the package, assigning licences) happen in Salesforce Setup before the console is reachable.
Access you'll need. Running the implementation 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 additionally needs a Salesforce System Administrator.
How to use this checklist Work through it top to bottom — each phase builds on the one before it. Do the configuration in a sandbox first, prove every cycle works, and only then repeat it in production. Treat Phase 3 (opening balances) and Phase 4 (validation) as non-negotiable gates: do not cut over until your opening trial balance ties to your old system and your test transactions post to the right accounts.
The two decisions to lock before anything else Two choices are very expensive to change once transactions exist: your currency mode (single vs. multi-currency) and your fiscal-year structure per territory. Settle both before you configure anything — they shape everything downstream.

Before you begin — gather & decide

A smooth go-live is mostly preparation. Pull these together first:

  • Decide single- vs. multi-currency. If any entity will transact in a currency other than your home currency, you are multi-currency. Decide now — it is set once, up front.
  • Assemble your opening trial balance. Export the closing balances from your current system as of your planned cutover date. This is the backbone of Phase 3.
  • List your entities. Every legal company that owns a set of books — with its home currency, accounting basis (accrual or cash), and fiscal-year start month.
  • List your territories. The countries and regions you operate in. Every entity belongs to a territory, so you need at least one even for a single-country operation.
  • List your users and their roles. Who does receivables, who does payables, who owns the ledger, who only reviews. This drives licences and permission sets — and your segregation of duties.
  • Identify your countries of operation. These determine which tax and withholding packs you seed.
  • Name the owner of the books. Decide who has authority to close periods and who signs off the close.

Phase 1 · Install & activate

  • Install in a sandbox, then production. REDA never pushes the package to your production org — you install it, test it in a sandbox, and promote it when you are ready. See Installation & Upgrades.
  • Activate your subscription. In the Financial Admin Console → Subscription tab, paste your licence key and click Activate. See Subscription & Plans.
  • Assign user licences. Tick the REDA Financials AI box on each user who will post transactions. See License Assignment.
  • Assign role-based permission sets. Give each user the v2 permission set for their role — and keep duties separated. The v2 sets are the ones to assign from version 1.610; the originals cannot be assigned to users on a Salesforce Platform licence. See Permission Set Assignment and Segregation of Duties & Security.

Phase 2 · Configure the foundation

This is the bulk of the work, and almost all of it happens in the Financial Admin Console and your master-data tabs. The Post-Installation Setup guide walks through each of these in detail — here they are as a checklist, in the order that works.

Application & chart of accounts
  • Set your currency mode. Confirm single- or multi-currency in REDA Application Settings before entering any transactions.
  • Seed the Global chart of accounts. This builds a standards-based chart — and automatically creates your global accounting defaults.
  • Seed your country tax & withholding packs. Seed each country you operate in to load its tax jurisdictions, tax rules, and withholding (WHT/TDS) rules.
  • Review your accounting defaults. Open Global Accounting Defaults and confirm each default GL account is the right one under your policy. The package guarantees the mapping is structurally valid; choosing the right account is your professional judgment.
Structure & entities
  • Define your territories. Create at least one; add sub-regions if you need them. Set territory-level accounting defaults where a region needs different accounts.
  • Create your entities. For each legal company, set its territory, home currency, default GL accounts, accounting basis (accrual vs. cash), and fiscal-year start month.
  • Configure document sequences. Set the numbering for each entity and document type (invoices, bills, receipts, payments, journals) — prefix, suffix, starting number, and whether the year is included. Do this before you issue the first document, so numbering is clean and audit-friendly from the start.
Master data
  • Set up your products and services. Create your catalogue and attach fiscal profiles so tax resolves correctly on invoice and bill lines.
  • Set up your bank accounts. For each account, set the cash GL account, currency, owning entity, and reconciliation defaults.
  • Configure check stock & numbering. If you print checks, set the starting, ending, and next check number and the check-stock description on each bank account — the number then flows onto each disbursement automatically.
  • Set up your customers and vendors. Create the Accounts, attach their tax profiles, and set defaults such as payment terms.
  • Configure payment terms. Define your due-day terms and any early-payment discounts.
  • (Multi-currency) Configure exchange rates. Set up your rate source and the daily rate sync so conversions and FX gain/loss post correctly.
  • Configure PDF templates & branding. Set up per-entity templates, logos, and payment details for the documents you will send to customers and vendors.

Phase 3 · Periods & opening balances

This phase is a hard gate Your opening balances are the foundation every future report stands on. Do not begin transacting in production until the opening trial balance ties exactly to your prior system.
  • Generate your accounting periods. Create a year of periods for each territory, matching each territory’s fiscal-year start. Generate every fiscal year you intend to transact in.
  • Load your GL opening balances. Post your closing trial balance from the old system as an opening journal entry, dated to your cutover. Debits must equal credits.
  • Load open AR and AP items. Bring in unpaid customer invoices and unpaid vendor bills individually, so aging, statements, and applications are accurate from day one.
  • Migrate your fixed assets. Load mid-life assets with their migration date, original cost, and opening accumulated depreciation so the schedule continues correctly rather than restarting.
  • Reconcile the opening trial balance. Confirm every balance ties to your old system, account by account. Resolve any difference before moving on.
  • Set your book-closure dates. Lock the periods before your cutover so nothing can be posted into them by mistake.

Phase 4 · Validate in a sandbox

Prove the system end to end before production. Run a real transaction through every cycle you use and confirm the accounting is correct. See Sandbox Testing Guide for how to set this up.

  • Run a full receivables cycle. Sales invoice → post → cash receipt → apply, plus a credit memo. Confirm the customer balance and aging are right.
  • Run a full payables cycle. Purchase order → purchase invoice → match → post → cash disbursement → apply, plus a vendor memo.
  • Post journal entries, including an intercompany entry, and confirm the automatic offsets.
  • Run a bank reconciliation end to end against a sample statement.
  • Run a depreciation batch and confirm the entries post to the right accounts.
  • Capture a period-end aging snapshot for AR and AP.
  • Verify every posting hits the intended GL account. Spot-check the underlying accounting transactions and the GL Account Ledger.
  • Verify tax and withholding. Confirm the right rates and accounts for each country you seeded.
  • Verify multi-currency. Check conversions and FX gain/loss on a foreign-currency transaction.
  • Verify your financial statements. Trial Balance, Income Statement, Balance Sheet, and Cash Flow should be correct and balanced; aging reports should match.
  • Verify your documents. Generate invoices, checks, and statements as PDFs and confirm the branding and payment details.
  • Do a trial month-end close. Walk the full Month-End Close Checklist once in the sandbox so the real one holds no surprises.

Phase 5 · Controls & automation

  • Confirm segregation of duties. Make sure no one person can both record and conceal — separate receivables from payables, and keep whoever reconciles the bank distinct from whoever records cash. See Segregation of Duties & Security.
  • Schedule your automated operations. On the Operations tab, schedule the jobs you rely on — recurring transactions, journal auto-reversal, exchange- rate sync, depreciation posting, aging snapshots, auto-apply, and OCR. Leave the rest to run on demand.
  • Confirm audit logging and field history are capturing changes to the records and fields you need for compliance.
  • Document your close policy. Write down who closes the period, in what sequence, and on what timetable.

Phase 6 · Cutover & go live

  • Pick a cutover date — ideally the first day of a period, so your old and new systems split cleanly on a close boundary.
  • Do the final opening-balance reconciliation as of the cutover date and confirm it still ties.
  • Freeze the old system to new transactions so nothing is recorded in two places.
  • Confirm every user has the right licence and permission set, and can log in.
  • Brief and train your team on the workflows they will use day one.
  • Start transacting in production. You are live.

After go-live

  • Run your first real month-end close carefully, following the Month-End Close Checklist.
  • Review your batch-job outcomes on the Operations tab — watch for any partial or failed runs.
  • Reconcile your first month’s bank statements to confirm cash is clean.
  • Gather feedback from your team and fine-tune defaults, templates, and schedules.
You don’t have to do it alone REDA’s team can help you plan and run your go-live — from data migration to validation to the first close. Reach out to support@reda.one or your REDA Account Executive.

Where to go next

  1. Your Setup Roadmap — the full setup sequence behind go-live.
  2. Sandbox Testing Guide — validate everything before you cut over.
  3. Month-End Close Checklist — your first close after going live.
  4. Opening Balances Migration — load starting balances at go-live.
  5. Trial Balance — confirm the books balance on day one.

Frequently asked questions

Two, really: validating end to end in a sandbox (Phase 4) and reconciling your opening trial balance (Phase 3). Get those right and everything else is recoverable. Skip them and small errors compound across every future period.

No. You need accurate opening balances as of your cutover date — the GL trial balance, open AR/AP items, and any mid-life fixed assets. Loading full transaction history is optional and usually unnecessary; most organisations keep the old system available for historical lookups.

Yes. Many organisations go live with one entity, prove the process, then onboard the rest. Just remember every entity belongs to a territory, and each territory needs its own accounting periods generated.

Cut over at a period boundary — typically the first day of a month or fiscal year. A clean break means your old system holds everything up to the close, and REDA Financials holds everything from the opening balance forward, with no overlap.

It depends on how many entities, currencies, and countries you run, and how much master data you have. The gating factor is almost always sandbox testing and opening-balance reconciliation, not the configuration itself. Plan generously for those two phases.

Stop and resolve it before going live — do not “plug” the difference. A balance that doesn’t tie means an account is mismapped, a sub-ledger is incomplete, or an item was missed. Work account by account until debits equal credits and every balance matches your prior system.

Was this article helpful?