No IT Required: FloQast's New Tool Reverse-Engineers Finished Closes to Automate Future Month-End Workflows
1. Introduction: The Month End Documentation Trap
For controllers, CFOs, and accounting managers, the month end close is still an exhausting process full of structural problems. Important operational knowledge stays stuck inside multi tab workbooks, complex spreadsheet formulas, and the memories of senior accountants. Up to date standard operating procedures (SOPs) rarely exist. When documentation does get written, it goes stale the moment a chart of accounts changes or a key team member leaves. Teams are left depending on manual tie outs and knowledge passed along by word of mouth.
Traditional workflow automation has struggled with this documentation trap. Automating a complex accounting task usually meant writing detailed procedural manuals or waiting in IT queues for custom code. Accounting teams rarely have time to draft software specifications during the close, so many automation projects stall at the pilot stage.
At its TakeControl 2026 conference in September, FloQast introduced a different approach: automation built from work the accounting team has already approved. Instead of asking accountants to spell out every step and edge case in advance, FloQast Transform reverse engineers completed close work into auditable AI agents.
2. Skip the Blank Page: AI That Builds From Last Month's Close
FloQast Transform shifts automation from writing specifications to learning from finished work. Instead of asking busy controllers to map out their routines, Transform takes the prior period's source files and the reviewed, signed off output from a completed close. It then works backward, capturing the logic, spreadsheet steps, and judgment calls buried deep in workbooks, and turns them into deployable AI agents.
Legacy Workflow Automation vs. FloQast Transform
Legacy Workflow Automation
Starting point: Blank page, procedural specs, or custom coding
Logic capture: Manual rule definition and IT development queues
Verification gate: Simulated testing or post deployment monitoring
SOP generation: Manuals written by hand and rarely updated
Ownership: IT or external consultants
FloQast Transform
Starting point: Finished, human reviewed prior period close files
Logic capture: Reconstruction of the logic inside existing workbooks
Verification gate: Column by column tie out against approved prior period data
SOP generation: Living playbooks generated with every agent
Ownership: The accounting team that runs the process
Teams can start building an agent in several ways:
Reconstruct from finished work: Hand Transform last month's source files and approved output, or an existing SOP, and it builds the agent.
Describe it in plain language: Explain a multi step workflow in conversation, without writing code.
Start from a prebuilt agent: Use a ready made agent for common close tasks, or build one step by step.
Transform also includes safeguards built for accounting:
Column by Column Verification: Before any agent goes live, it runs against prior period data and ties out its output, entity by entity, against numbers the team has already approved. If the output does not match, the agent cannot be saved.
Living SOPs: Every agent generates its own plain language playbook covering every input, step, and check, with version history, segregation of duties, and approval controls.
Accountant Ownership: Accounting team members build, test, and maintain workflows themselves. When an allocation method or entity structure changes, the owner describes the change in plain language and the workflow updates, with no IT ticket.
The approach reflects how close work actually happens. Real expertise lives in refined workbooks and past judgment calls, not in binders. FloQast reports more than 400 agents live across 125+ accounting teams.
3. The 85/10 Execution Gap: AI Maturity Linked to Closes 2 Days Faster
FloQast's State of Accounting AI 2026 report, based on research across finance and accounting professionals in the US and UK, shows a wide gap between AI ambition and day to day reality:
The Execution Paradox: 85% of accounting teams have made AI a strategic priority, but only 10% use it extensively (Level 5 maturity).
The Manual Burden: Six in ten accountants spend 40% or more of their time on manual tasks such as data entry and reconciliations. Nearly one in five spend more than 60% of their week on manual work, about three full days. 57% of close cycles take seven days or more.
The Performance Gap: Level 1 teams (manual and spreadsheet heavy) spend 63% of their time on manual tasks and average an 8.7 day close. Level 5 AI native teams spend 34% of their time on manual tasks and average a 6.7 day close, two full days faster.
Top Automation Targets: 55% of respondents name account reconciliations as the top automation opportunity, yet only 5% report a high degree of automation there today. Financial reporting ranks second at 53%.
"The accounting profession doesn't have an AI ambition problem, it has an execution problem. What this research makes clear is that, in accounting, the real test of AI is whether a human can confidently sign off on that work and defend it to an auditor."
Mike Whitmire, CPA (inactive), FCA, Co-Founder and CEO of FloQast
The lesson for controllers who have been burned by past automation promises is that layering AI over weak controls does not work. According to the survey, 51% of organizations operate with controls that are informal or inconsistently applied across the close. Automating an unstructured process only speeds up its errors. Lasting gains require documented controls and clear human review gates before agentic tools are scaled.
4. Governance Isn't Overhead, It's the Engine of Auditability
General purpose AI tools struggle in accounting because their outputs are hard to trace and defend. That concern shows up clearly in the data:
Adoption Barriers: In FloQast's survey, 39% of professionals cite data security and privacy as their top obstacle, and 31% say their teams lack the AI skills and training to use new tools. Respondents also named the lack of traceability of AI outputs as a key barrier.
Disclosed Risk: The Conference Board and ESGAUGE found that 72% of S&P 500 companies disclosed at least one material AI risk in their 2025 Form 10-K filings, up from 12% in 2023.
The Governance Gap: Figures cited at TakeControl 2026 put AI deployment at 88% of organizations in at least one business function, while only 38% have a governance policy in place.
FloQast is building governance into the platform itself:
Governance Leadership: FloQast hired COSO Board Chair Lucia Wind as Senior Vice President of Risk & Audit Advisory. Wind oversaw COSO's publication of its generative AI governance framework earlier in 2026.
COSO GenAI Governance Module (coming soon): FloQast has announced a module that will bring COSO's generative AI governance framework into the platform. It will map agent capabilities to risk assessments, control activities, and ongoing monitoring, with audit evidence captured as agents run.
ISO 42001 Certification: FloQast has held ISO 42001 certification for its AI management system since 2025, following an external audit of its AI systems, governance policies, and risk management practices.
For CFOs, AI that arrives with governance built in may shorten compliance reviews and procurement cycles that would otherwise stall. When every output can be traced and defended, finance teams spend less time justifying their numbers and more time using them.
5. From Post Close Corrections to Continuous GL Anomaly Detection
Traditional close management relies on review after period end, when controllers hunt for misclassifications and errors under deadline pressure. FloQast's newer tools move that work into the open period:
Traditional Post Close Review vs. Continuous Detection
Traditional Post Close Review
Review window: After period end, during close week
Error discovery: Reactive troubleshooting during final reconciliation
Review mechanics: Manual spot checks and spreadsheet tie outs
Audit trail: Scattered emails, review notes, and offline workbooks
Continuous Detection
Review window: Throughout the period, as transactions are recorded
Error discovery: Anomalies flagged before the books close
Review mechanics: AI risk scoring, structural checks, and user defined rules
Audit trail: Logged review and sign off for every flag
Three tools support this approach:
FloQast Detect: Learns normal transaction patterns for each subsidiary and account, and flags anomalies before the books close. Each flagged item is assessed for GL impact, routed for review, and signed off with a full audit trail. Team defined rules apply the team's own review criteria to every transaction.
AI Assistant (Journal Entry Management): Acts as a first pass reviewer inside journal entry workflows. When a reviewer requests it, the Assistant flags errors and anomalies, scores audit risk, explains its reasoning, and recommends a fix. The human makes every final call.
FloQast Operational Audits: Expands internal audit tools to cover the full audit plan, including SOX testing, other compliance audits, and operational audits. AI drafts the audit plan, executes testing, and generates an executive report from live audit data.
Catching anomalies during the period prevents month end logjams and lets the team shift from error hunting to oversight.
6. Real World Results: From 15 Day Closes to 25 Second Allocations
Customers presenting at TakeControl 2026 shared measurable results:
Gong: Cut its month end close from 15 days to 8 days.
Chickasaw Nation Industries: Cut its close from 15 days to 5 days and shaved a full month off its audit season.
Blue Owl Capital: Reduced an overhead allocation process that once took a week of back and forth with an offshore team to 25 seconds.
Hazeldenes: Built five AI agents, each with a designated human owner and a separate reviewer, including one that automated a seven step layered intercompany allocation. The team saved approximately 600 hours per year and absorbed natural attrition without backfilling headcount.
These results come from FloQast's own customer presentations and materials. They show how agentic workflows remove routine friction when automation runs under clear human oversight, freeing accounting teams to act as strategic partners to the business.
7. Conclusion: The Rise of the Forward Deployed Accountant
The accounting profession is going through a structural change. The traditional mandate of preparing workbooks, hunting errors, and defending the numbers is giving way to a role FloQast calls the Forward Deployed Accountant: an accountant who uses the numbers to guide business decisions.
Agentic automation does not replace the accountant. It raises the ceiling on the job by removing mechanical work. When routine matching, entry review, and multi entity allocations run on governed, auditable automation, finance professionals gain time for judgment, risk evaluation, and planning.
As finance leaders assess readiness for the coming fiscal year, one question remains: Is your close built on fragile, undocumented spreadsheets, or on a governed, auditable control foundation ready for agentic automation?
Sources
FloQast Maintains Lead: Tops G2's Summer Grid Report for Financial Close Management
FloQast adds auditable AI agents to accounting workflow platform - Disrupts Media
FloQast vs Numeric: Which Close Platform Wins in 2026? | CFO Shortlist
M&A Integration: Why the Office of the CFO is the Key to Deal Success | FloQast
Skip the Blank Page. Transform Builds From Last Month's Close. | FloQast
TakeControl 2026 Recap: FloQast's AI Accounting Announcements, Data, and Key Takeaways
The 3 Things Finance Teams Get Wrong Before AI Can Accelerate the Close | FloQast