INSIGHTS · PRACTICAL GUIDE · UPDATED OCTOBER 8, 2026
Accounting Center Readiness: A Practical Source-Data Checklist
Before configuring a financial data flow, make sure the business event and its expected accounting result are understandable. This checklist helps finance and technology teams identify decisions that need owners.
1. Define the event and the record grain
Write one sentence describing what each source row represents: a transaction, a balance, a position or an adjustment. Record the business identifier, event date, accounting date, currency and amount fields. Two rows that look similar may represent a legitimate correction rather than a duplicate.
Working question: can a reviewer explain a representative row without relying on the developer who extracted it?
2. Make mappings explicit
List the source values that drive ledger accounts, worktags and other required attributes. Name an owner for every lookup and document how a new source value is introduced. Decide whether mapping changes are effective-dated and how historical reruns should behave.
3. Agree exception behavior
Decide what happens to missing identifiers, unmapped values, invalid dates and unsupported currencies. Do not silently convert an unknown value into a convenient default. Define which conditions reject a record, pause a batch or require finance review.
4. Design reconciliation before building
Identify the source totals and expected outputs for each stage. Counts, amounts and selected dimensions should be reviewable together. An equal grand total can still conceal a wrong account, duplicated positive and negative rows, or a missing business unit.
5. Plan corrections and reruns
Specify how a corrected source record is identified, who authorizes reprocessing and how previously processed events are distinguished. Include a test for duplicate delivery and a test for an interrupted load.
6. Establish operating ownership
Define the person or team responsible for source delivery, mapping approval, exception review and confirmation that the process is complete. Agree the expected delivery window and escalation path.
Readiness worksheet
| Decision | Evidence to prepare |
|---|---|
| Record grain | Field definitions and representative event examples |
| Mapping ownership | Approved lookup workbook and change owner |
| Control totals | Counts and amounts by meaningful dimensions |
| Exception workflow | Reject conditions, review owner and recovery steps |
| Go-live acceptance | Expected results and named business approver |
Use the checklist in discovery
Mark each area ready, unresolved or dependent on another team. The result should become a delivery backlog, not simply a score. Resolve high-impact accounting and source-definition questions before increasing implementation activity.
Product context: Workday Accounting Center overview. The checklist above is Forth Light’s practical planning guidance.
Put this guide to work
Download the editable planning worksheets and preview sample deliverables →
Use the template to record assumptions, owners and evidence before your project review.