A report is a definition plus a query
Most recurring reports fail not because the query is wrong but because the definition was never written down. Two people can produce different totals from the same system while both believe they are reporting the same thing. Before the next refresh, write the population, the inclusion rule, the exclusion rule, the time window, the currency or unit, and the event that counts as a record. If those fields are missing, the report is a snapshot of whoever built it last. A Philippines-based reporting administrator can maintain the definition register, run the approved query, reconcile the output, and flag discrepancies. The administrator should not change a definition to make a number look better, silently drop an inconvenient category, or present a working estimate as an approved result. Definition changes belong to the report owner and should carry an effective date.
Freeze the source extracts
Record the source system, the extract time, the reporting period, and the filter used. Keep the extract or a reproducible query reference with the report version. If the source system changes continuously, note that the report reflects a declared cutoff rather than a live state. This is especially important when a dashboard, a finance ledger, and a CRM all describe the same activity in different ways. Do not overwrite last month's extract when this month's arrives. Keep versions separate and label them. If a late correction changes a prior period, show the restated value and the reason instead of quietly replacing the old number. A reader should be able to compare the report they approved with the report that now exists and understand why they differ.
Reconcile totals before publishing
Reconciliation is a set of explicit checks, not a feeling that the numbers look reasonable. Compare the report total with the source total, the detail count with the summary count, the opening balance plus movements with the closing balance, and the prior period with the current period after known changes. Record each check, the result, and the person who performed it. A failed check should stop publication until the owner decides. Common causes of a reconciliation gap include duplicate records, timing differences, currency conversion, excluded test accounts, and a filter applied in one system but not another. Classify the cause before adjusting anything. An unexplained residual should remain visible rather than being pushed into an 'other' bucket. The report owner needs to see the size and direction of the gap to decide whether the report is fit for its purpose.
Handle late changes without rewriting history
Late changes are normal. A source system may post a correction after the extract, a business owner may clarify a category, or a legal entity may be reclassified. The administrator should record the change request, the effective period, the reason, and the approver. Then produce a new version with a change note rather than editing the published file in place. Version control is not bureaucracy when a report supports a decision. A board pack, a regulatory filing, or a customer invoice may depend on the exact version that was reviewed. Keep the approved version, the working version, and the superseded version distinguishable. If a correction affects a previously distributed number, tell the recipients through the approved channel and record that the correction was communicated.
Work a realistic refresh
A monthly operations report shows 1,240 completed items. The source detail contains 1,268 rows. The administrator checks the filters and finds 18 duplicate rows from a re-imported file and 10 rows outside the reporting period. The remaining 1,240 match. Instead of adjusting the source, the administrator records the duplicate import, the date range, and the reconciliation result, then publishes the report with the explanation. The next month, a category owner asks to move one service line into a different group. The administrator does not edit the historical series. A new definition version is created with the effective date, the old series is retained, and the report shows the change. The owner can then compare like with like and decide whether the new grouping is useful. The evidence trail explains both the old and the new view.
Review the definition register quarterly
A definition can become stale when a product changes, a system is replaced, a contract is amended, or a team reorganizes. Review the register on a fixed cadence and after any material change. For each report, confirm the owner, the purpose, the population, the source, the refresh time, the distribution list, and the review date. Retire reports that no longer support a decision rather than keeping them alive by habit. Sample a published report each quarter and ask an independent reviewer to reproduce the headline number from the saved extract and the written definition. If the reviewer cannot reproduce it, the report is not yet controlled. The fix may be a clearer definition, a saved query, a better extract, or a note about the source limitation. Record the correction and re-test after the change.
Sources and limits
The U.S. Government Accountability Office's Standards for Internal Control, the COSO Internal Control framework, the AICPA, and NIST provide general context for reliable information, control activities, and evidence. They do not prescribe the definition for a specific report or replace the client's finance and accounting judgment. Sources: https://www.gao.gov/products/gao-14-704g https://www.coso.org/internal-control https://www.aicpa-cima.com/ https://www.nist.gov/cyberframework