# Financial reporting automation acceptance worksheet

Use this with your controller, reporting owner and reviewer before deciding whether one monthly reporting workflow is ready for use. Fill the blank record with your own work, test a draft against approved sources, and record who accepts the result.

This worksheet covers report preparation and review. It does not authorize journal entries, payments, changes to source records or distribution of a final report.

Companion guide: [Automated financial reporting](https://www.cyndra.ai/blog/automated-financial-reporting). See [Cyndra's implementation services](https://www.cyndra.ai/services) for help choosing and building a first workflow.

## 1. Define one reporting scope

| Field | Fill in before the pilot |
| --- | --- |
| Report and decision it supports | [ ] |
| Reporting period, cutoff time and timezone | [ ] |
| Entity or project included | [ ] |
| Entities, accounts and workflows excluded | [ ] |
| Currency, units and sign convention | [ ] |
| Accounting basis and approved metric definition | [ ] |
| Report preparer and backup | [ ] |
| Finance reviewer and final approver | [ ] |
| Pilot owner and decision date | [ ] |
| Approved comparison period or budget version | [ ] |
| Permitted output and readers | [ ] |

For a developer, specify the legal entity or project rather than mixing project costs, corporate overhead and consolidated totals. Have finance approve any allocation or consolidation rules before testing them.

## 2. Map every source to an output

Keep source files unchanged. Give each test run a version or timestamp so a reviewer can reproduce the draft from the same inputs.

| Output line or metric | Approved source and version | Period, entity and units | Source owner | Mapping or calculation | Expected update time | Reviewer evidence location |
| --- | --- | --- | --- | --- | --- | --- |
| [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] |
| [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] |
| [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] |

- [ ] Record expected files, row counts and totals before preparing the draft.
- [ ] Specify a duplicate key, such as source document ID plus line ID, and how legitimate repeated amounts are distinguished from duplicates.
- [ ] Confirm that period, entity, currency, scaling and signs match the report definition.
- [ ] Document approved exclusions, adjustments and rounding rules. Name the person allowed to approve each.
- [ ] Set the source freshness deadline and the response to a late or incomplete input.
- [ ] Define the reconciliation tolerance and variance-review threshold before looking at the results. A threshold flags review; it does not explain a variance or approve it.

## 3. Record reconciliations and exceptions

Use a separate row for each report line or control total that must agree with its source. Do not net unrelated differences against one another.

| Check | Approved source value | Draft value | Difference and units | Agreed tolerance | Pass or hold | Evidence and reviewer |
| --- | --- | --- | --- | --- | --- | --- |
| [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] |
| [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] |

| Exception ID | What failed | Affected line and run version | Owner | Required correction or explanation | Due time | Retest evidence | Reviewer disposition |
| --- | --- | --- | --- | --- | --- | --- | --- |
| [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] |

If an override is permitted, record its reason, supporting source, authorizer and expiry. An override should remain visible in the review record rather than silently changing a result to pass.

## 4. Worked example: a correct total is not an explained variance

**Illustrative test data only.** These invented records demonstrate checks and arithmetic. They are not a Cyndra client, an observed result or an accounting recommendation.

Scope: one fictional entity, October 2026 monthly operating expenses, USD in whole dollars, expenses shown as positive amounts. The approved October ledger extract and September comparison use the same scope and definition. For this test, the agreed reconciliation tolerance is USD 0.

| Source record | Approved October expense | Treatment |
| --- | ---: | --- |
| EXP-001 payroll | 70,000 | Include once |
| EXP-002 occupancy | 25,000 | Include once |
| EXP-003 other operating expenses | 14,200 | Include once |
| EXP-004 office supplies | 800 | Include once |
| **Approved ledger total** | **110,000** | **70,000 + 25,000 + 14,200 + 800** |

The first draft includes EXP-004 twice. Its total is USD 110,800, so the reconciliation difference is 110,800 - 110,000 = **USD 800**. The duplicate-key check and zero-tolerance reconciliation both fail. Hold the draft and assign the duplicate to the preparer; do not alter the approved source ledger to make the report agree.

After correcting the draft's duplicate handling and rerunning the same input version:

- Corrected draft: 110,800 - 800 = **USD 110,000**.
- Residual difference against the approved October ledger: 110,000 - 110,000 = **USD 0**. This reconciliation check passes.
- Approved September expense: **USD 100,000**.
- October versus September change: 110,000 - 100,000 = **USD 10,000 increase**.
- Percentage change, using September as the denominator: 10,000 / 100,000 x 100 = **10% increase**.

Supported draft commentary: "October operating expenses increased by USD 10,000, or 10%, from the approved September total. The cause is pending the expense owner's review."

Unsupported commentary: "Hiring drove the increase." The totals alone do not establish hiring, seasonality or any other cause. A zero reconciliation difference does not resolve the business explanation.

| Decision | Result in this example |
| --- | --- |
| Does the initial draft reconcile? | Hold: duplicate USD 800 record |
| Does the corrected draft reconcile? | Pass: zero residual difference, subject to the other checks |
| Is the 10% movement explained? | No: request a source-backed explanation from the named expense owner |
| Can a draft be sent for internal review? | Only in the agreed draft state, with the unresolved explanation visible |
| Is the final report approved? | Hold until required explanations and checks are resolved and the named approver records sign-off |

## 5. Test the failure paths before accepting a pilot

Run each case on a copy of the inputs. Record the actual behavior and evidence; a planned check is not a passed test.

| Test | Deliberate input or state | Expected behavior | Actual result, evidence and reviewer |
| --- | --- | --- | --- |
| Missing source | Omit one required file or control total | Name the missing source; hold affected outputs; do not substitute an estimate silently | [ ] |
| Stale source | Supply a file from the wrong period or beyond the agreed freshness deadline | Flag the period or timestamp mismatch and hold the affected output | [ ] |
| Wrong units | Supply a value in USD thousands where the report expects whole USD | Detect or flag the mismatch before comparison; hold until an approved conversion and retest are recorded | [ ] |
| Duplicate | Repeat one source record with the same approved duplicate key | Flag it; prevent silent double counting; record correction and rerun evidence | [ ] |
| Unsupported variance cause | Supply a movement without evidence explaining it | State the movement accurately, mark the cause unresolved and route it to the owner; do not invent an explanation | [ ] |
| Approval missing | Leave final sign-off blank or use a reviewer who lacks the assigned approval role | Keep the output in draft or hold state; do not label or distribute it as approved | [ ] |
| Mapping changed | Change an account mapping after the reviewed run | Create a new run version; require the affected checks and approval again | [ ] |

When the prior comparison value is zero, the percentage-change formula is undefined. Test that the output reports the absolute movement and flags the percentage as not applicable rather than dividing by zero.

## 6. Agree stop rules and a fallback

- [ ] Hold affected outputs for missing, stale or incorrectly scoped sources, unresolved duplicates, unit mismatches or unexplained reconciliation differences outside the agreed tolerance.
- [ ] Hold final approval for unresolved required explanations, missing evidence or missing sign-off.
- [ ] Keep source values, calculations and owner explanations separate. Label AI commentary as a draft until reviewed.
- [ ] Identify who can stop the run, who fixes each failure and who can restart review.
- [ ] Preserve the last accepted run and the manual reporting method. Record which version finance will use if the pilot is stopped.
- [ ] Decide the number of representative parallel runs and the acceptance conditions before expanding scope. Do not accept a workflow solely because one clean sample passes.

Stop owner: [ ]  Fallback owner: [ ]  Escalation contact: [ ]

## 7. Compare the manual baseline with a reviewed pilot

Use matched scopes and record any differences in row counts, complexity, source readiness or staffing. Include preparation, checking, corrections and approval effort. Do not count a fast unapproved draft as a completed report.

| Measure and definition | Manual baseline period/run | Reviewed pilot period/run | Evidence and comparison notes |
| --- | --- | --- | --- |
| Source readiness to final approval, elapsed time | [ ] | [ ] | [ ] |
| Preparation effort, person-minutes | [ ] | [ ] | [ ] |
| Review and correction effort, person-minutes | [ ] | [ ] | [ ] |
| Reconciliation failures before approval, count | [ ] | [ ] | [ ] |
| Unsupported commentary statements found, count | [ ] | [ ] | [ ] |
| Corrections after approval, count | [ ] | [ ] | [ ] |
| Required evidence and approvals present, count out of required total | [ ] | [ ] | [ ] |

Keep the counts as well as any rate. Record whether a lower exception count reflects better inputs, different scope or a changed check. Released staff time is capacity for other work; it is not automatically a cash saving.

## 8. Record the decision

| Decision field | Fill in |
| --- | --- |
| Run ID, input versions and output version reviewed | [ ] |
| Required checks passed and evidence location | [ ] |
| Unresolved exceptions, owners and due dates | [ ] |
| Decision: hold, continue pilot, or accept the defined scope | [ ] |
| Conditions and limits of acceptance | [ ] |
| Final approver, date and recorded sign-off | [ ] |
| Next review date and trigger for retesting | [ ] |

## Bring one redacted reporting task to a free live build

Use a small example your organization permits you to share. Bring a blank report layout, a redacted or synthetic source sample, the approved calculation definitions and one exception you want the workflow to catch. Remove credentials, bank account details, personal data and confidential values; keep enough structure to show the task.

The first useful question is specific: "Can we assemble this draft, show where each number came from, and hold it when these checks fail?" A demonstration is a starting point for evaluation, not acceptance of a production reporting process.

[Book a free live build](https://www.cyndra.ai/contact) or [review Cyndra's services](https://www.cyndra.ai/services). Your finance team owns the definitions, exceptions and final approval.
