What Should Philippine CFOs Measure at Month-End Close?

What should a CFO measure in the monthly close first?

A CFO should measure whether the close produces dependable numbers on schedule, not speed alone. Start with close-cycle time, late critical tasks, reopened periods, unresolved reconciliations, post-close journals, and missing evidence. Those measures show where finance is waiting, correcting, or accepting risk before an SAP change hides the baseline.

Key takeaways

• Close speed is useful only when the final numbers stay closed and supporting evidence is complete.
• Critical-path delay should be separated from the total number of late tasks.
• Reopened periods and post-close journals expose quality problems that a faster calendar can conceal.
• Every close measure needs an owner, calculation rule, evidence source, and escalation threshold.
• Capture at least three comparable closes before using an ERP change as the explanation for improvement.

APQC’s October 2019 analysis of its General Accounting and Financial Reporting benchmarking data found that slightly fewer than 20% of respondents used shared services for general accounting. A little more than half had extensively achieved common finance-data definitions, about two-thirds had extensively implemented a standard chart of accounts, and about 44% extensively followed strict finance-process ownership. APQC also reported that 58% used cloud delivery for general accounting and reporting.

APQC associated standard data, processes, and ownership with better cycle-time and error measures. The public article does not disclose the sample size, sector mix, geography, or percentile values, so none of these percentages is a Philippine target. They point to the operating conditions a CFO should test locally. Appcentric’s article on real-time finance with GROW provides the system context. The decision still needs a pre-change baseline from the company’s own close.

Which close measures separate speed from control?

Use a scorecard that makes speed, quality, workload, and evidence visible at the same time. A single “days to close” number can improve while teams post more late journals, leave reconciliations unresolved, or reopen the period. The scorecard should prevent that trade from disappearing.

The following is an original close-control card for a Philippine finance team:

The APQC analysis above uses cycle time and journal-entry errors to distinguish speed from quality. The BIR’s official site maintains a live tax reminder with filing, payment, and submission dates. Because obligations vary by taxpayer and period, finance should load the entity’s approved calendar rather than copy a deadline from a static article.

Do not copy targets from another company. Define the calculation once, record the source system, and keep the rule unchanged across the baseline and post-change periods. Mark the tasks that can delay external or management reporting. A late low-risk checklist item should not carry the same weight as an unresolved bank reconciliation or consolidation entry.

The scorecard also needs an exception note. A typhoon-related office closure, acquisition entry, or mandated tax change may extend the close without indicating a broken process. Record the cause rather than changing the formula. That discipline lets finance compare three ordinary months, a quarter-end, and a disrupted period without pretending they are identical.

What evidence should survive each monthly close?

Every reported measure should point to evidence another reviewer can inspect. Keep the approved calendar, task ownership, preparer and reviewer sign-offs, reconciliation support, journal approvals, period-lock history, exception records, and the final management reporting pack. A dashboard without those records shows status; it does not establish why the number should be trusted.

The Philippine reporting anchor sits in Section 177 of the Revised Corporation Code of 2019. It says that “every corporation, domestic or foreign, doing business in the Philippines shall submit to the Commission” annual financial statements, subject to the Code and SEC rules. The section requires an independent CPA audit, while corporations with total assets or liabilities below ₱600,000 may submit statements certified under oath by the treasurer or chief financial officer. It also permits delinquent status after reportorial failures three times within five years.

A monthly close scorecard does not itself satisfy that annual obligation. It can make the annual evidence trail less dependent on reconstruction. For each material balance, finance should be able to identify the preparer, reviewer, source report, reconciling items, adjustment approvals, and final sign-off. For every post-close journal, retain the reason, amount, affected entities, and approval path.

Treat missing evidence as a measured defect, not an administrative footnote. A task marked complete without its required support should reduce the evidence-completeness rate. That rule discourages teams from improving the calendar by closing tasks before their proof is ready. It also gives the CFO a concrete basis for deciding whether a process change, additional training, or system control deserves funding.

How should an SAP change affect the close scorecard?

An SAP change should alter the close scorecard only when it changes how work is performed or evidenced. Preserve the baseline definitions through design, testing, cutover, and stabilization. Otherwise, finance can report an improvement that came from a new measurement rule rather than a better close.

Map each scorecard measure to a process step and system record before configuration. Close-cycle time needs one agreed start event and one final approval event. Reconciliation aging needs a policy date and a source for open items. Evidence completeness needs an explicit attachment requirement. Post-close journals need a period-lock event and an approved exception route. These decisions belong to finance, even when technical teams implement them.

Use process work to locate the waits and corrections before choosing automation. Appcentric’s SAP Signavio service and its guide to process mining in the Philippines provide one route for examining process behavior. For a cloud ERP program, the GROW with SAP service is a relevant implementation path. An ECC transition should also preserve the financial controls described in the existing Philippine CFO migration case.

Run the scorecard through user acceptance testing with realistic late tasks, rejected journals, missing attachments, reopened periods, and old reconciling items. Retain one reconciliation and one post-close journal as traced test cases from source report to approval, posting, and final scorecard value. Then hold the definitions steady for at least three post-change closes. The decision gate is not whether every measure improves immediately. It is whether finance can explain each movement from retained evidence and distinguish a configuration issue from a process, data, or staffing issue.

What else should a CFO ask about close measures?

Is days to close enough for a CFO dashboard?

No. Days to close measures elapsed time but can hide reopened periods, late journals, old reconciling items, and missing support. Pair it with critical-task delay, reopen rate, post-close journal count and value, reconciliation aging, and evidence completeness. The measures should retain the same definitions before and after an SAP change.

How many baseline closes should finance capture?

Capture at least three ordinary monthly closes and include a quarter-end if the timetable and workload differ materially. This is a recommended operating baseline, not an external benchmark. Record unusual events separately so a typhoon, acquisition entry, tax change, or one-time audit request does not silently change the comparison.

Should every late close task receive the same weight?

No. Mark tasks that can delay reporting, period lock, consolidation, tax work, or management approval as critical. Measure their delay separately from lower-risk checklist items. Keep the full late-task count for workload analysis, but use critical-path delay when the CFO needs to understand reporting risk.

What should finance retain for a post-close journal?

Retain the journal amount, currency, affected accounts and entities, business reason, preparer, approver, submission time, posting time, and linked evidence. The record should also show whether the period had already received final approval. That package lets reviewers distinguish a valid exception from a control or data-quality failure.

Can external benchmark results set our close target?

No. External data can identify useful measures, but it cannot establish a target for a Philippine entity with different systems, staffing, controls, and reporting duties. APQC’s 2019 public analysis does not disclose its sample size, sector mix, geography, or percentile values. Use the company’s own comparable closes.