July 2026. General Accounting Research Area

Panelists: Sr. Director, General Accounting & Payroll, Company A (national nonprofit organization) · Sr. Director, Americas GBS, Company B (global medical device company) · Group Manager, Company C (global consumer products company) · Sr. Director, Financial Services & Solutions, Company D (media company service center)

Overview

A peer panel of finance/accounting leaders discussed how their organizations are shortening and de-stressing the month-end close process. The conversation covered current close timelines, structural challenges (multiple ERPs, third-party dependencies, upstream data delays), recent process improvements, and forward-looking plans — especially around automation and AI.

Note that this document is a summary. Peeriosity-100 members have full visibility to company names, presenters, Peercast attendees, and a recording of the Peercast discussion.

Current Close Performance (Benchmark vs. Panel)

• Industry benchmark cited: ~10% of large enterprises have a fully mature continuous close; 18% close in 1–3 days; ~50% take 6+ days; over 25% take more than 7 days.
• Company A: 4-day close, CEO report morning of day 5.
• Company C: Books close in 3 days (within the top 18%), plus 2 additional days for proofing/adjustments — done by workday 5 globally.
• Company D: ~6-day close, handoff to corporate consolidation team; runs entirely on Oracle Fusion ERP; intercompany is the biggest holdup.
• Company B: Local entities close by workday 5; holding company close follows in a “domino” sequence, landing around workday 8.
• Year-end close is generally only 2 days longer than a normal month for most panelists, driven mainly by tax provision work; several noted that heavy upfront-year preparation has made year-end progressively less painful.

Common Structural Challenges

• Multiple/fragmented ERP environments (notably Company B, managing well over 30 ERPs across legal entities) slow consolidation and standardization.
• Third-party/vendor dependencies: a recent ADP payroll outage (linked to a data center issue in France) and a prior transport-management-system vendor outage both threatened close timelines, underscoring reliance on external system uptime and the need for tested business continuity plans.
• Upstream data delays from non-finance departments, and unpredictable volume spikes (Company A cited donation surges after major disasters, e.g., hurricanes, which can push their close out 1–2 days).
• Manual, non-integrated sub-ledger processes: Coupa Inventory lacking an automatic interface into Oracle was flagged by multiple panelists as a top bottleneck, requiring extensive manual journal entries (Company A uses ~17 major macros to manage this).
• Complex revenue recognition (e.g., rebate structures, life sciences business lines at Company B) and cost accounting complexity (Company C’s plant-level costing) add close-cycle friction.

Notable Process Improvements Already Made

• Company A: Implemented an Apex journal-entry workflow tool on top of Oracle R12, replacing an error-prone email-based JE submission process; fully adopted over 18 months and expected to shave a day off close once fully rolled out.
• Company C: Leveraging BlackLine’s Smart Close and AI-driven proofing, which has significantly reduced excess/late hours — the team no longer measures close quality by “pizza nights” (late-night work sessions), a stark contrast to a few years ago. Strict cutoff times for proofing entries (by a set hour on a specific workday) have reduced downstream rework.
• Company B: Uses FloQast to map and monitor close tasks globally, providing visibility into bottlenecks; shifting toward materiality-based estimates rather than high-precision entries for immaterial items, and moving more activity into the pre-close period to smooth workload.
• All panelists reported moving away from historic “hard close/soft close” distinctions toward a more consistent monthly process.

Mid-Month Activity

Common theme: reconciliations (excluding largest accounts) and follow-up on outstanding items happen after month-end close rather than during it; daily automated control checks catch errors as they occur; remaining time goes to audit support and continuous improvement work. Company B begins next month’s pre-close activities around day 18.

AI & Automation — Current Focus Areas

• Company C: AI-driven proofing (established success); continuing to expand Smart Close; piloting Microsoft Dynamics for some legacy forms.
• Company B: Early-stage conversations with BlackLine on AI for intercompany reconciliation; evaluating S-Curb-type tools for cash application; working with RoboIO on bot/AI opportunities for company-specific processes; expanding use of Copilot/ChatGPT-style tools within Microsoft Office workflows; exploring “Gapfile” as a cross-ERP tool to centralize PO data and automate accrual booking.
• Company D: Evaluating AI for balance sheet and intercompany reconciliation, particularly open-item management/clearing; running a parallel build-vs-buy evaluation (internal development vs. a BlackLine proof of value) — no decision made yet.
• Company A: Early-stage evaluation of Trintec’s AI capabilities for balance sheet and credit-card donation reconciliations.

12-Month Roadmap Highlights by Organization

• Company A: Unify onto a single closing calendar (chapters vs. HQ/biomedical currently run separately) — targeted for end of FY27, expected to cut close time by a day.
• Company C: Continue Smart Close expansion; complete migration of capital/fixed-asset sub-ledger to S/4HANA; pursue “zero defects, zero excess hours” methodology; continue AI proofs of concept.
• Company B: Consolidate onto a single ERP (long-term, multi-year effort); automate the rebates process to speed revenue recognition; expand FlowCast-driven task mapping; pursue accrual automation via tools like Gapfile.

Consistency Across Global/Regional Centers

• Company C operates as one unified global organization rather than autonomous regional centers, enabling a “follow-the-sun” handoff model (Asia → Europe → Americas) built on standardized KPIs, documentation, and close processes.
• Company B, despite multiple ERPs, drives consistency through a single global chart of accounts and centralized use of Hyperion for consolidation/reporting standardization.

Key Takeaways for Organizations Still Facing a “Fire Drill” Close

Panelists converged on a two-step recommendation:

1. Map the process first — understand the sequence and timing of close activities to identify where work can be shifted earlier (pre-close) and where volume concentrates.
2. Standardize before automating — automating one standard process is far easier than automating many disparate ones; standardization should precede any large automation or AI investment.