.gif?width=320&height=80&name=7-logo-30years%20(1).gif "7-logo-30years (1)"){kind=logo}
Our two most recent Insights posts looked at AI from the assurance side of finance. Autonomous Audits: Applying SAP AI to Continuous Assurance explored how continuous, population-level monitoring changes the audit, and Governing SAP AI Agents: Why the Control Plane Matters More Than the Model addressed how organizations keep AI agents accountable. In this post, we turn to the question that is on every controller's calendar right now: what can finance teams realistically do with SAP AI before the books close on December 31st?
The honest answer is more nuanced than most AI marketing suggests. With roughly eleven weeks left in the year, this is not the moment to launch a broad agentic transformation inside your most scrutinized close of the year. But it is exactly the right moment to remove manual effort from high-volume, rules-driven close tasks, to tighten the evidence your auditors will ask for, and to set up the foundation that will let 2027 look very different from 2026.
From a Bramasol perspective, the right framing is a two-speed approach: automate what is proven and low-risk now, and prepare deliberately for what comes next.
The Close Cycle Time Has Barely Moved in a Decade
The case for change is not new, but it remains compelling. According to APQC’s research on strategies for streamlining the annual closing process, top-performing organizations complete the annual close in 10 days or less, compared with a median of 18 days and 35 days for slower performers. APQC also reports that 31% of organizations actively use AI in record-to-report processes, while another 39% are still in the early stages of adoption.
For finance leaders, the message is clear: a faster close starts with better preparation, stronger coordination, and smarter tools. Year-end, with its additional reconciliations, true-ups, disclosures and audit requests, is the slowest and most stressful close of all.
At the same time, finance leadership intent has clearly shifted. According to Deloitte's Q4 2025 CFO Signals survey, 87% of North American CFOs consider AI very or extremely important to their operations, and 54% planned to integrate AI agents into the finance function during 2026.
The gap between that intent and a still-manual close is where the practical opportunities exist.
What SAP Now Brings to the Close
SAP's approach to the close has evolved from individual automation features into an orchestrated set of agents. The Financial Closing Assistant coordinates specialized agents for journal postings, clearing activities and analysis, and lets users control each agent's level of engagement. The agents SAP has included under that assistant are:
- Accounting Accruals Agent for audit-ready accruals preparation.
- Receivables and Payables Clearing Agent, using AI-based matching and aging-pattern analysis to recommend clearing.
- Intercompany Matching and Reconciliation Agent, which matches unstructured intercompany invoices.
- Journal Entry Verification Agent, which recommends actions on general ledger entries and provides an evidence trail.
- Journal Attachment Validation Agent, which validates and scores supporting documents for mass-uploaded journal entries.
- Asset Accounting Anomaly Detection Agent, which helps prevent inaccurate or invalid asset postings.
- Financial Consistency Analysis Agent, which surfaces hidden process inconsistencies and data errors.
SAP's Financial Closing Advisor Agent built in Joule Studio can read task status from the Financial Closing Cockpit, to map dependencies, flag tasks as actionable, blocked or at-risk, and recommend the next activities in sequence, with controller-confirmed status updates.
One important caveat. Not all of these capabilities are available to every SAP customer today. Depending on your current SAP configuration and whether you are using Public or Private cloud, some agents may not be available. If you'd like to get a quick, personalized assessment of how these agents map into your specific situation, contact Bramasol here.
What to Automate Before December 31
For most SAP customers, the highest-value, lowest-risk moves for this year-end fall into five areas.
- Cash application and receivables clearing. This is mature, high-volume work. SAP Cash Application uses embedded machine learning to automatically match incoming bank statement items to open receivables. Every unmatched payment cleared before December is one fewer reconciling item in January.
- GR/IR and open-item clearing. Aged open items are a perennial year-end headache and a common audit question. AI-assisted clearing proposals, which are then system-validated and reviewed before posting, can clear backlog that would otherwise be carried into the new year.
- Intercompany matching. For multi-entity organizations, intercompany differences are one of the most common causes of a late consolidation. Getting matching and dispute resolution under control in November pays off directly in the year-end close.
- Journal entry review and supporting documentation. Using AI to verify journal entries and score their supporting attachments creates the kind of evidence trail that shortens auditor walkthroughs, and it reinforces the continuous-assurance model we described in our autonomous audits post.
- Close orchestration and visibility. Even before any agent posts a single entry, a closing advisor that shows controllers which tasks are blocked, at risk or ready to execute can remove days of status chasing from the year-end calendar.
The common thread is that each of these keeps a human in the loop for approval while removing the manual matching, searching and chasing that consume most of the close.
Discipline matters as much as ambition here. As we discussed in our governance post, no agent should enter a production finance process without a named owner, a defined autonomy level, documented authorization boundaries and complete logging. Year-end is the close your external auditors examine most closely, which makes it the wrong place to introduce an unproven agent with unclear evidence.
Three areas deserve particular care:
- Judgment-heavy entries. Reserves, impairments, complex accruals and estimates should remain human-owned this year. AI can prepare and support them, but not decide them.
- Revenue recognition and lease accounting true-ups. Year-end is when performance obligation allocations, remaining performance obligation disclosures, contract modifications and lease remeasurements get the most scrutiny. As we noted in Is Your Revenue Recognition Process Ready for New AI-Enabled Offerings?, "almost right" is not good enough in these areas.
- Early adoption capabilities. Pilot test them in a monthly close or a sandbox first, then bring them into the year-end cycle once their results and evidence have held up.
The most valuable thing many finance teams can do this year-end is to treat the close itself as a discovery exercise. A few practical steps:
- Measure the baseline. Track days to close, number of manual journal entries, unmatched items, intercompany differences, late reconciliations and audit requests outstanding. Without a baseline, it is impossible to prove AI's value next year.
- Tag the friction. Have each close owner note where they waited for data, rekeyed information or chased someone for an answer. Those notes become your 2027 automation backlog.
- Clean the foundation. Master data, the chart of accounts, closing task lists in the Financial Closing Cockpit, and documented accounting policies are what AI agents rely on. SAP's accruals agent, for instance, works from historical data and accounting policy documents, so their quality directly determines its output.
- Plan the 2027 pilots. Select two or three close processes with clear volume, measurable cycle time and well-understood controls, and plan their rollout for the first quarter, when there is time to evaluate them before the next year-end.
Bramasol's Finance-First S/4HANA Transformation methodology is built on a simple principle: automation only accelerates the quality of the foundation underneath it. That principle has never mattered more than with AI in the close. When the chart of accounts, master data, revenue events, billing data and controls are sound, SAP's closing agents can remove days from the calendar. When they are not, agents simply surface exceptions faster than teams can clear them.
Our deep experience in SAP Finance, Revenue Accounting, Lease Accounting, Treasury and Quote-to-Cash means we see the close from the perspective of the subledgers that feed it, which is where many of the most stubborn year-end delays begin. Billing disputes that should have been resolved in October, revenue contracts with unprocessed modifications, and leases with missed remeasurements all land on the controller's desk in January.
The approach we recommend is practical: secure the proven automation now, protect the year-end from unnecessary risk, and use the close itself to build the evidence and the roadmap for a materially faster, AI-enabled close in 2027.
Year-end is not the time for AI experimentation in the most scrutinized parts of the close, but it is a real opportunity to apply proven SAP AI capabilities to the manual, high-volume work that slows every finance team down: cash application, open-item clearing, intercompany matching, journal entry review and close orchestration.
The organizations that will see the biggest gains in 2027 are the ones that use this year-end both to automate what is ready and to measure, document and clean up what is not. Bramasol combines deep expertise in SAP Finance solutions, along with practical AI and S/4HANA implementation experience, which enables us to help finance teams do both.