Regulatory Audit Evidence Packs for Utility Finance
An evidence pack should help a reviewer understand what happened without requiring a live demonstration from the original preparer. Organize it around the reporting assertion, the supporting records and the review performed.
Regulatory Audit Evidence Packs for Utility Finance
Distinguish evidence of preparation from evidence of approval. A completed workbook shows work was done; it does not by itself show that an independent reviewer checked the relevant assumptions.
Treat the reporting map as a controlled business record rather than a convenient lookup list. Keep the effective period, approving owner and explanation beside each rule. A reviewer should be able to reconstruct an earlier report without applying the rules used for a later one. Where a conclusion depends on regulatory interpretation, record the question for the responsible accountant instead of making the software team decide it silently.
Three useful steps
- Define the question each file supports.
- Include source selections and rule versions.
- Record review comments and their resolution.
Operational and regulatory views answer different questions. A field supervisor may need a project total while a reporting specialist needs a classification of the underlying costs. Design the handoff so the second view can be explained without destroying the first. Write down which attributes are inherited from source documents and which are added by an approved reporting rule; that distinction makes later investigations much easier.
Consider a small example
A mapping change pack could contain the old rule, the proposed rule, a sample comparison and the approval. A folder containing only the final export leaves the reason for the change unexplained.
Prepare a small challenge set as well as an ordinary sample. Include a reversal, a late adjustment, a shared-service charge and a record with incomplete attributes. Ask the reviewer to explain the intended treatment before the test is run. A successful total is useful, but it does not prove that each underlying line has reached an appropriate destination. Keep unresolved items visible rather than placing them in an unexplained balancing category.
Where the approach can go wrong
Avoid collecting every available screenshot. Excess material can hide the few records that actually support the conclusion.
A useful review meeting ends with decisions, not simply a cleaner spreadsheet. Give each open item an owner, an evidence request and a next review point. Where two interpretations remain possible, preserve both proposed treatments and identify the person authorized to decide. This is especially important when a small technical change could alter the way an expense is presented outside the organization.
Make the handoff easier
Separate preparation, review and resolution in the status record. A task can be prepared but not reviewed, or reviewed with open questions. Calling all of those states complete removes useful information. Define the evidence required for final acceptance and keep unresolved items assigned to someone who can actually make the next decision.
Preserve the ability to move from summary to evidence. A selected amount should lead to the relevant underlying records and the rules used to assemble them. This does not mean every viewer needs unrestricted detail; access can remain role-appropriate. The important point is that an authorized reviewer has a repeatable route to the explanation.
Use examples of acceptable and unacceptable entries in the guidance. Abstract definitions can leave users uncertain about a real request. Show a complete ordinary record, an ambiguous request and an exception that must be escalated. Review the examples with the people who actually submit and approve changes.
A usable result
Assemble an indexed evidence pack with a short narrative and a direct link from each conclusion to its support.
Related reading
FERC Form 1 Preparation: Organizing the Source Data; Regulatory Reporting Close Calendars for Utilities; Regulatory Reporting Data Lineage in SAP Utilities.