Skip to content
  • There are no suggestions because the search field is empty.

Go-Live Readiness in Light: Minimum Viable Setup and Legacy Preparation

Checklist for Light go-live readiness, including system foundations, cards, master data, contracts, and legacy close requirements such as reconciliations, COA mapping, and accrual schedules.

Readiness in Light before Go-Live (minimum viable setup)

1. Foundations

  • Chart of Accounts + custom properties defined

  • Tax codes

  • Bank accounts created in Light

  • Bank feed integration activated (can be connected early)

  • Users, groups, approvals, workflows, guardrails

  • Slack integration (if used) for bill approvals and reimbursements

  • Reimbursement category → GL mapping

  • Invoice template

  • AI assistant rules (optional)

2. Cards readiness

  • Adyen GL Account setup in Light before Go-Live

  • Adyen account funding + spending limits configured

3. Master data readiness

  • Vendors + Customers created:

    • those present in Open AP/AR

    • those used in last years postings / selected history scope

  • Products/services (the ones that are present in the contracts)

Upload Open Contracts

Objective: Ensure recurring sales invoice works immediately.
Methods:

  • Individual upload by sending the contracts to the defined mail

  • Bulk CSV upload

Legacy preparation (what must be done in the last month end closing before cutoff)

These actions reduce migration issues more than anything else.

1. Reconcile subledgers to GL

  • Reconcile AP subledger ↔ AP control account from General Ledger

  • Reconcile AR subledger ↔ AR control account from General Ledger

  • Reconcile Fixed assets register ↔ FA / accumulated depreciation (GL) (if applicable)

Rule: If differences exist, correct them in the Legacy System. Do not attempt to "patch" the difference in Light.

2. Clean up open items

Allocate/offset as much as possible where payments have been made/received to ensure that prepayments, and open items are accurately presented.

  • apply vendor credit notes to invoices

  • apply customer credits to invoices

  • allocate prepayments where possible

Goal: Migrating clean and consistent data.

3. Confirm prior year close

Ensure previous year-end closing (e.g 2024) is completed in Legacy (especially important if importing 2025 journals only).

4. COA mapping readiness

Confirm COA mapping is complete:

  • any account used in 2025 (or agreed historical period) must be mapped to the Light account code.

Missing mappings are a common cause of migration delays.

5. Accruals schedule

Prepare a detailed schedule for ongoing accruals to carry operationally in 2026:

  • deferred revenue / prepaid expenses

  • start date, end date, frequency, remaining balance