Accounting System Change Records Request Checklist for Bookkeeping

An accounting system change request keeps legacy and new-system record sets, period coverage, excluded items, and client-provided cutover context visible as separate requested items for staff review.

View checklist

Browse the resources hub

Quick answer

Use this checklist after a client changes accounting systems or loses access to a former platform. It collects client-provided legacy exports, final reports, source documents, cutover context, and new-system opening records without connecting to, migrating, reconciling, or validating either system.

Copy-ready request checklist

Accounting System Change Records Request Checklist

Copy this list for one client, entity, legacy system, new system, cutover date, and defined period coverage.

1. Request setup

Set the systems and cutover boundaries before requesting reports or source records.

Client: [Client name]
Entity: [Entity name]
Legacy accounting system: [System]
New accounting system: [System]
Cutover date: [Date]
Final legacy period: [Period]
First new-system period: [Period]
Request owner: [Team member]
Review owner: [Team member]
Due date: [Date]

2. Legacy-system records

Request client-provided exports and final reports that apply to the defined transition.

General ledger or transaction export.
Final trial balance.
AR aging or open invoice report.
AP aging or unpaid bill report.
Reconciliation reports when maintained and requested.
Chart of accounts or account list when requested.
Fixed asset, loan, payroll, inventory, or deferred schedule only when maintained and relevant.
Audit trail or user activity export only when available and specifically requested.

3. Source-document archive

Keep client-provided source records separate from platform reports.

Bank and credit-card statements.
Vendor invoices and receipts.
Payroll provider reports.
Processor or sales reports.
Loan or lease statements.
Other client-provided source records required for the engagement.

4. New-system opening records

Request the reports and client context that describe the new-system starting point.

Opening trial balance or opening account balances.
Imported open invoices or unpaid bills report.
Opening bank and card account list.
Client-provided migration summary.
Account-mapping notes when maintained.
Known excluded, missing, or manually transferred items.
First available reports from the new system.

Legacy records vs new-system opening records

Keep record sets and coverage separate without claiming that either system is complete.

Record set

Legacy-system records

Possible requested support

Final reports, ledger or transaction export, open-item reports, maintained schedules, and requested account list.

Do not conclude

That the legacy data is complete, reconciled, or ready to migrate.

Record set

Source-document archive

Possible requested support

Statements, invoices, receipts, payroll, processor, loan, lease, and other client-provided source records.

Do not conclude

That source support maps automatically to either system.

Record set

New-system opening records

Possible requested support

Opening balances, open-item reports, account list, migration summary, maintained mapping notes, exclusions, and first reports.

Do not conclude

That migration is complete or opening balances are correct.

Record set	Possible requested support	Do not conclude
Legacy-system records	Final reports, ledger or transaction export, open-item reports, maintained schedules, and requested account list.	That the legacy data is complete, reconciled, or ready to migrate.
Source-document archive	Statements, invoices, receipts, payroll, processor, loan, lease, and other client-provided source records.	That source support maps automatically to either system.
New-system opening records	Opening balances, open-item reports, account list, migration summary, maintained mapping notes, exclusions, and first reports.	That migration is complete or opening balances are correct.

Item status and next action

Keep a missing client action distinct from staff review and a specific replacement request.

Situation

The requested support has not arrived

Status

Waiting on client

Next action

Ask for the named record or factual context for that item.

Situation

A file or response has arrived

Status

Uploaded / Pending review

Next action

Staff review the item, period, source, and readable context before resolving it.

Situation

Staff records evidence for the requested item

Status

Received

Next action

Keep other requested items open until they have their own review result.

Situation

The file is wrong, incomplete, unreadable, or for a different item

Status

Needs reupload

Next action

Request a replacement only for the affected requested item.

Situation	Status	Next action
The requested support has not arrived	Waiting on client	Ask for the named record or factual context for that item.
A file or response has arrived	Uploaded / Pending review	Staff review the item, period, source, and readable context before resolving it.
Staff records evidence for the requested item	Received	Keep other requested items open until they have their own review result.
The file is wrong, incomplete, unreadable, or for a different item	Needs reupload	Request a replacement only for the affected requested item.

Preserve cutover context without performing the migration

The checklist makes the client-provided records and coverage gaps visible for staff review; it does not transfer, map, repair, or reconcile data.

Client-facing request template

Subject: Records needed for [legacy system] to [new system] change for [entity].
Please upload the listed legacy reports, source documents, opening records, and client-provided cutover context by [due date].
Keep legacy reports, source-record archive, and new-system opening records in separate requested items.
Identify the final legacy period, first new-system period, and any known excluded or manually transferred items.
Do not send passwords, API keys, access tokens, MFA codes, or primary login credentials.

Synthetic illustrative scenario

Synthetic example: [Juniper Works] changes from [Legacy System A] to [New System B] on [June 1, 2026].
The request has separate items for the final legacy trial balance, open invoice report, bank statement archive, client-provided migration summary, and first new-system report.
The trial balance is Uploaded / Pending review. The migration summary is Waiting on client.
The scenario does not connect to either system, migrate data, verify completeness, map account codes, reconcile systems, or calculate opening balances.

Common mistakes

Asking for a broad system backup without naming the needed record or approved secure process.
Combining legacy reports and new-system opening records in one unclear upload item.
Assuming an export proves that a migration is complete.
Requesting passwords, API keys, tokens, MFA codes, or primary login credentials.
Using the request to give tax, accounting, audit, or data-retention instructions.

Product boundary

CollectCue organizes client-period requested items, uploads, staff review, reuploads, reminders, and follow-up.
It does not connect to or migrate accounting systems, verify a migration is complete, map chart-of-account codes, reconcile old and new systems, import data, repair files, or calculate opening balances.
It does not determine tax, accounting, audit, or data-retention requirements. Do not request passwords, API keys, access tokens, MFA codes, or primary login credentials.

How to use this checklist

Set the legacy and new-system periods first, then request legacy reports, source archive, and opening records as distinct item groups.

1Set the cutover contextRecord the client, entity, legacy system, new system, cutover date, final legacy period, first new-system period, owners, and due date.
2Request legacy recordsSelect the client-provided final reports, open-item reports, maintained schedules, and account list needed for the defined transition.
3Separate source archive and opening recordsKeep statements and source documents distinct from new-system opening reports, migration summary, and known exclusions.
4Review record contextStaff review each requested item and ask for a replacement without claiming a migration result.

Frequently asked questions

These answers explain client document collection and do not make an accounting, tax, legal, payroll, or compliance decision.

What legacy records may be requested after an accounting system change?+

A firm may request a general ledger or transaction export, final trial balance, open invoice or unpaid bill reports, maintained reconciliation reports and schedules, chart of accounts when requested, and available activity exports when specifically requested.

What new-system records may be requested?+

A firm may request opening balances, imported open-item reports, opening bank and card account list, client-provided migration summary, maintained mapping notes, known exclusions, and first available reports.

Can CollectCue migrate or reconcile accounting systems?+

No. CollectCue does not connect to, migrate, reconcile, import, repair, validate, or map accounting-system data.

Should passwords or access tokens be requested on this page?+

No. Do not request passwords, API keys, access tokens, MFA codes, or primary login credentials in a public request checklist.

Related resources

Use these pages for the next request, review, reupload, or follow-up action.

Client onboarding document checklist

Collect baseline entity, historical, and account records before the first bookkeeping cycle.

Open resource

Bookkeeping source documents and reports guide

Choose whether the next requested item needs source support or a system-generated report.

Open resource

Bookkeeping client document request form

Turn the cutover list into item-level client-period requests with review status.

Open resource

Keep system-change records organized for review

CollectCue helps firms organize the cutover context, requested records, uploads, review status, reupload actions, and follow-up. It does not migrate, reconcile, validate, or repair accounting-system data.

See how CollectCue works