Prepare a Recurring Finance Report

Turn approved financial source data into the operational report format the team already trusts.

Keep consequential rows and figures traceable to their sources, make validation checks visible, and leave unresolved judgment with the accepted reviewer.

1. Define the report

Confirm:

• entity;
• reporting period;
• cutoff;
• time zone;
• currencies;
• source accounts;
• source systems;
• output format;
• destination;
• reviewer;
• as-of date.

When available, begin from:

• an accepted prior report;
• approved template;
• trusted spreadsheet;
• written reporting specification.

Do not replace an established reporting pack with a generic structure without approval.

Clarify the purpose of the report and what the reviewer expects to receive.

This workflow prepares operational financial reporting. When the main task is explaining why financial performance changed, route to the financial-performance review workflow.

2. Inspect approved sources and access

Use permitted:

• authenticated finance portals;
• exports;
• files;
• spreadsheets;
• approved reports.

Preserve:

• source name;
• source link or identifier;
• report version;
• download or retrieval time;
• filters;
• as-of date;
• relevant account/entity.

Pause for user involvement when:

• MFA is required;
• authorization expires;
• account changes;
• entity changes;
• data scope changes;
• requested access exceeds existing permission.

Do not bypass authentication or access boundaries.

3. Establish source-to-output rules

Identify the accepted transformation rules, including:

• source fields;
• output fields;
• joins;
• signs;
• date treatment;
• time-zone treatment;
• currencies;
• exchange-rate treatment where applicable;
• aggregations;
• exclusions;
• formulas;
• accepted exception rules.

Preserve supplied mappings and trusted spreadsheet logic unless the user accepts a change.

Make transformations inspectable.

4. Calibrate unfamiliar mappings

When a source or mapping is new, prepare a small representative sample before processing the entire period.

Include:

• at least one normal record;
• relevant edge cases available;
• source values;
• transformation;
• resulting output;
• unresolved ambiguity.

Apply accepted corrections before scaling.

Skip calibration when:

• the report is already trusted;
• the mapping is accepted;
• the current source still matches the expected schema and behavior.

If the source structure has changed, revalidate rather than assuming the old mapping remains correct.

5. Prepare the report

Retrieve only the in-scope data and apply the accepted rules.

Use the existing file or spreadsheet when appropriate.

If a new spreadsheet is required, use the environment's spreadsheet capability and keep:

• inputs;
• formulas;
• transformations;
• outputs

inspectable.

Do not alter source records to force the report to reconcile.

Record as exceptions:

• missing rows;
• failed mappings;
• duplicates;
• unexpected values;
• unsupported assumptions;
• source gaps;
• unresolved classifications.

6. Validate the result

Validate against the source set and accepted controls.

Check:

• entity coverage;
• period;
• cutoff;
• time zone;
• currency coverage;
• row counts;
• control totals;
• expected subtotals;
• duplicates;
• gaps;
• failed mappings;
• excluded items;
• signs;
• date conversions;
• formulas;
• output formatting.

Where useful, compare material movement with the prior report as a warning signal.

A prior-period difference is a prompt to investigate—not proof that the current report is wrong.

Do not force agreement between sources that measure different concepts or use different timing.

Explain unresolved reconciliation differences.

7. Deliver a review-ready result

Return:

• report file or spreadsheet;
• reporting scope;
• source coverage;
• as-of date;
• validation summary;
• control results;
• clear exception list;
• unresolved reviewer decisions.

When useful, prepare a draft handoff message.

Treat:

• preparing the report;
• uploading it;
• sending it;
• publishing it;
• sharing it

as separate actions governed by active permissions for the destination and audience.

When unresolved work is primarily collecting and matching supporting documents, route it to the appropriate receipts/bookkeeping workflow.

When the accepted report needs interpretation against budget, forecast, or prior performance, route it to the financial-performance review workflow.

8. Preserve the trusted reporting method

After the reviewer accepts:

• sources;
• mappings;
• validation controls;
• exception rules;
• output structure;
• handoff behavior,

preserve them as a reusable team method.

A recurring workflow may prepare the next report on an accepted cadence.

It must stop and request review when:

• access expires;
• MFA appears;
• source schema changes;
• source coverage changes;
• a control fails;
• entity changes;
• period falls outside the accepted setup;
• destination changes;
• reviewer changes;
• permissions change.

9. Maintain strict financial action boundaries

This workflow may read approved financial data and prepare reports, files, or drafts.

It does not itself authorize:

• initiating or approving payments;
• posting accounting entries;
• reversing entries;
• categorizing or approving ledger entries;
• changing bank records;
• changing payroll;
• changing invoices;
• changing source records;
• filing taxes;
• filing statutory reports;
• distributing sensitive financial information outside the approved audience.

These actions require separate workflows, permissions, and approvals.