Month-End Close: Why Finance Transformation Still Depends on Faster Decisions

Bring close-related decisions, approvals and exception follow-ups into Teams to reduce delays without weakening control

Finance transformation is high on the CFO agenda.

Organisations are investing in modern ERP platforms, analytics, automation, artificial intelligence and better reporting. The goal is clear: finance teams need to work faster, provide better insight and spend less time on manual administration.

Month-end close is often one of the first areas to come under scrutiny.

That is understandable. A slow close delays reporting, limits visibility and puts pressure on finance teams at precisely the point in the month when accuracy matters most. If the close process takes too long, management information arrives late. If issues are only resolved after repeated chasing, finance teams lose time that should be spent on analysis, forecasting and business support.

But month-end close is not delayed only by system processing or accounting complexity.

In many organisations, the close process slows down because finance is waiting for people to respond.

A journal may need approval. A cost centre manager may need to explain an unusual posting. A budget owner may need to confirm an accrual. An intercompany difference may need investigation. A blocked posting may need a decision. A missing explanation may need to be provided before finance can complete its review.

The finance system may be working correctly. The month-end timetable may be defined. The close checklist may be clear. But the process still depends on timely input from people across the business.

That is why finance transformation needs to address the human decision points around the close, not just the system steps inside the finance function.

The close process is full of dependency points

Month-end close is often described as a finance process.

In one sense, that is true. Finance owns the timetable, controls the accounting treatment, validates the numbers and produces the outputs. The finance team is accountable for making sure the close is accurate, complete and compliant.

But the information needed to complete the close is not always held within finance.

A project manager may know whether work has been completed. A cost centre owner may understand why spend has increased. A budget holder may know whether a supplier invoice relates to the current period. A business manager may need to confirm whether an accrual is required. An operational team may need to explain a variance or provide evidence for a late adjustment.

These are not always complex accounting questions. Often, they are straightforward business confirmations.

However, they still create dependency points.

The close cannot always move forward until the right person has reviewed the issue, provided an explanation, confirmed a value or approved an adjustment. If that person is busy, misses the request, does not understand what is required or postpones the task until later, the finance team is left waiting.

This creates a familiar pattern.

The close timetable says that the task should be complete. The finance team checks the status. The item is still outstanding. Someone sends a reminder. The business owner cannot find the original email. Another message is sent. A separate Teams chat follows. The response eventually arrives, but the process has lost time and visibility.

The issue is not that finance lacks a process. The issue is that the process depends on people who are not always working inside the finance system.

Why email follow-up slows finance teams down

Email remains the default communication channel for many close-related follow-ups.

It is easy to understand why. Email is universal. It can reach anyone. It provides a written record. It can be used quickly when something needs to be chased.

But email is not always a good way to manage actionable finance tasks.

An email can be missed, forwarded, misunderstood or left unread. It may not contain enough context for the recipient to make a decision. It may require the user to open another system, locate a transaction, review supporting information and then reply informally. It may be copied to several people, creating confusion about who actually needs to act.

Email also creates control problems.

If a manager replies with “approved” in an email thread, is that approval captured in the finance process? If a cost centre owner provides an explanation in a separate message, is that explanation linked to the relevant journal, accrual or close task? If a query is resolved in a chat, will finance be able to find the evidence later?

These questions matter because month-end close is not just about speed.

Finance teams need control, traceability and accountability. They need to know what is outstanding, who owns each action, what decision was made, when it was made and whether the supporting information is complete.

Email follow-up can help move an issue forward, but it often sits outside the controlled process. It creates extra work for finance teams, who then have to interpret responses, update trackers, record comments and chase again if the response is incomplete.

The result is a close process that is technically structured but operationally fragmented.

Examples of close-related tasks that need business input

Close delays are often caused by small unresolved items rather than one large accounting problem.

A finance team may be waiting for a journal to be approved. A budget owner may need to sign off a late adjustment. A cost centre manager may need to explain a variance. A business user may need to confirm whether a cost should be accrued. A project manager may need to confirm whether activity has been completed. An intercompany team may need a response from another entity before a difference can be cleared.

The same pattern appears across many close activities, including:

• journal approvals;
• accrual confirmations;
• cost centre queries;
• budget owner sign-offs;
• intercompany queries;
• blocked postings;
• missing explanations;
• late adjustment approvals;
• supporting document requests; and
• variance explanations.

Each item may appear minor on its own.

But across a finance team, across multiple business units, entities, cost centres and reporting deadlines, these small dependencies become significant. Every outstanding action creates uncertainty. Every manual reminder adds work. Every delayed response increases pressure on the close timetable.

This is where finance transformation needs to become practical.

It is not enough to digitise the accounting transaction if the related decision still depends on a manager finding an email, logging into a separate system, working out what is being asked and then replying manually.

The decision point needs to become easier to complete.

Using Teams to reduce friction in close activities

For many organisations, Microsoft Teams has become a central part of daily work.

Managers use Teams for meetings, messages, collaboration and day-to-day communication. They may not be regular users of SAP or other finance applications, but they are likely to be active in Teams throughout the working day.

That creates an opportunity.

Instead of relying on email notifications and manual follow-up, close-related tasks can be brought into Teams as actionable requests. The business user receives a clear task, the relevant context and the available action in the same environment they already use for work.

This is where Looply can help.

Looply enables SAP business processes to be extended into Microsoft Teams. A close-related task, approval or exception can trigger an Adaptive Card in Teams. The card can show the information the user needs, such as the journal details, cost centre, amount, period, reason, supporting explanation and requested action.

The user can then respond directly from Teams.

For a journal approval, the approver may be able to review the journal summary, check the reason for posting, add a comment and approve or reject the request. For an accrual confirmation, the business owner may be asked to confirm whether the accrual is still required. For a cost centre query, the manager may be asked to provide an explanation or confirm the correct coding. For a blocked posting, the recipient may be asked to review the issue and provide the missing information.

The key point is not that every finance transaction should be rebuilt inside Teams.

SAP remains the system of record. The finance process remains controlled. The approval, confirmation or comment is returned to the underlying process.

Teams becomes the engagement layer: the place where the business user can see the task, understand the context and respond quickly.