The file had been registered. So why did no one know where it stood?

Case study · Internal control & digitization

The file had been registered. So why did no one know where it stood?

A payment file can be logged in a document management system and still stay stuck for weeks. This real-world case shows why tracking must cover the entire process, right through to the final decision.

Insights — Galaxy Conseils  ·  2 min read

The situation

A public institution receives a payment request along with all the supporting documents. The mail is logged in its document management system, then forwarded to the relevant department. Three weeks later, the supplier asks for payment. In the system, the file still shows as "forwarded."

To answer these questions, several staff members exchange emails and search for a paper copy. The file is eventually found on the desk of a manager who is out of office.

The internal control problem

The problem isn't with logging the mail — that first step was properly recorded. It's what happens afterward that escapes tracking. After the initial handover, approvals happen on paper, with no set deadline and no visibility into pending actions. Internal control can no longer catch the bottleneck in time.

This breakdown comes at a cost: time spent searching for the file, follow-up reminders, a delayed payment, and teams tied up reconstructing its history.

The institution's response

The institution decides to overhaul the entire workflow. Every file is now assigned to a specific owner, along with the required documents and a processing deadline. Checks and approvals are now logged in the system. Notifications flag pending tasks, while a dashboard highlights files that exceed the expected deadline. If a document is missing, the reason is recorded and stays visible to every authorized party.

Digitization doesn't replace accountability — it makes it visible throughout the process. Management can pinpoint the steps that slow things down, staff know exactly what action is theirs to take, and the supplier can get an answer based on the file's actual status.

This case is presented to illustrate a possible gap between digital logging and the actual processing of a file.