How a Small IT Services Company Digitized Payment Planning, Collection Tracking, and Financial Reporting Without ERP Complexity
Financial operations are among the most critical processes in any organization. Despite this importance, many small and medium-sized businesses still manage payment planning, supplier obligations, collection tracking, and financial reporting through spreadsheets exchanged via email.
For years, our organization followed a similar approach. Weekly payment plans were prepared in Microsoft Excel, distributed to relevant stakeholders by email, and manually updated throughout the week. While the process was functional, it gradually became more difficult to manage as the business grew.
Historical payment records were scattered across multiple spreadsheets and email threads. Obtaining a consolidated view of previous payments required significant manual effort. More importantly, there was limited visibility into the relationship between supplier payments and customer collections. In many cases, determining whether a customer invoice had already been collected before authorizing a supplier payment required additional investigation.
As a result, operational efficiency decreased while financial visibility became increasingly limited.
The objective was not to replace Excel simply for the sake of modernization. The objective was to create a process that was visible, traceable, reportable, and manageable from a single platform while maintaining a simple user experience for the employees involved.
Our first attempt focused on enhancing the existing spreadsheet-based process through VBA-powered forms and automation. While this approach provided some improvements, it did not solve one of the most important challenges: collaboration. Simultaneous access by multiple users continued to create operational difficulties, version control remained problematic, and the process still depended heavily on individual spreadsheet files.
At this stage, it became clear that the problem was not the spreadsheet itself. The real challenge was process visibility.
To address this issue, we redesigned the workflow using Google Sheets, Google AppSheet, and Google Apps Script. The goal was to preserve the simplicity employees were accustomed to while creating a centralized and real-time operational platform capable of supporting payment planning, collection tracking, financial reporting, and management visibility.
Designing the New Process
Once the limitations of the spreadsheet-based approach became clear, the next step was to redesign the process rather than simply replacing the existing toolset.
One of the most important objectives was maintaining simplicity for the employees involved in the process. The goal was not to introduce a complex financial management platform or force users to learn an entirely new way of working. Instead, the objective was to create a centralized workflow that would improve visibility and traceability while requiring minimal changes to daily operations.
The first step was standardizing how payment requests were entered into the system.
Historically, payment information was collected through spreadsheets, emails, verbal communication, and various ad-hoc methods. This often resulted in inconsistent data structures and increased the risk of errors during payment planning activities.
To address this challenge, a single payment entry form was designed. Every payment request would now be entered through a standardized interface, ensuring that all required information was captured in a consistent format.
The form includes key financial information such as:
- Payment date
- Supplier information
- Purchase invoice details
- Customer information
- Sales invoice details
- Collection amounts
- Currency information
This approach established a single source of truth for payment planning activities and eliminated the need to manage multiple spreadsheet versions distributed across different users.
More importantly, the process became independent of individual employees and email chains. Every payment request entered into the system immediately became available to authorized users, creating a centralized and collaborative environment for financial operations.
Figure 1. Standardized Payment Entry Form
The accounting team enters payment requests through a simple and structured interface, ensuring consistency and reducing manual processing effort.
Creating a Single Source of Financial Truth
While standardizing data entry improved consistency, the real business value emerged when payment planning became connected to collection status.
In many organizations, supplier payments and customer collections are managed as separate activities. As a result, payments may be approved without a clear understanding of whether the corresponding customer invoice has already been collected.
This creates unnecessary financial exposure and can negatively impact cash flow management.
To address this challenge, the new platform introduced a simple but highly effective business rule.
Every payment request is evaluated against the collection status of the related customer invoice.
If the corresponding collection has been completed, the payment is automatically categorized as eligible for payment.
If the collection has not yet been received, the payment remains visible but is classified separately until the financial condition is satisfied.
This approach provides finance personnel with immediate visibility into payment priorities without requiring additional analysis or manual verification.
Instead of reviewing multiple spreadsheets, emails, and accounting records, users can instantly identify which payments are ready to be processed and which items require further attention.
The result is a more disciplined payment planning process that helps preserve cash flow while reducing operational complexity.
From a management perspective, this also creates a significant improvement in financial visibility. Decision-makers can quickly understand not only what needs to be paid, but also why certain payments remain pending.
The platform effectively transforms payment planning from a simple tracking exercise into a decision-support process.
Figure 2. Collection-Aware Payment Planning
Payment requests are automatically categorized according to collection status, helping finance teams prioritize cash outflows and improve financial control.
Simplifying Daily Financial Operations
One of the most important lessons learned during this project was that process visibility alone is not enough. If employees are required to perform excessive manual work to maintain the system, adoption rates decline and the expected benefits of digital transformation become difficult to achieve.
For this reason, operational simplicity became a core design principle throughout the project.
Once payment requests enter the system and are categorized according to collection status, finance personnel can manage their daily activities directly from a single operational screen.
Rather than navigating through multiple spreadsheets, email conversations, and accounting records, users can view all pending items in a centralized interface and execute the necessary actions with minimal effort.
Several operational functions were incorporated directly into the platform, including:
- Payment confirmation
- Partial payment processing
- Bulk payment updates
- Payment status tracking
- Operational note management
- Reporting actions
As payments are completed, users can update records individually or process multiple records simultaneously. This significantly reduces the administrative effort associated with maintaining payment records and improves the accuracy of operational data.
The platform also provides a direct communication channel between finance operations and accounting teams.
At the end of the payment cycle, completed transactions can be reported automatically, eliminating the need to prepare separate summary spreadsheets or manually compile payment information for distribution.
This seemingly simple capability produced a measurable operational improvement.
Tasks that previously required multiple files, email exchanges, and manual reconciliation efforts can now be completed from a single interface with only a few clicks.
Most importantly, employees were not forced to abandon familiar workflows entirely. The new process preserved the simplicity of the previous approach while adding visibility, consistency, and traceability.
This balance between operational efficiency and user adoption proved to be one of the key success factors of the project.
Figure 3. One-Click Financial Operations
Payment confirmation, status updates, partial payment processing, and reporting activities can be performed directly from a centralized operational interface.
Management Visibility Through Real-Time Dashboards
While operational efficiency was one of the primary objectives of the project, management visibility ultimately became one of its most valuable outcomes.
Prior to the transformation initiative, obtaining a comprehensive view of payment obligations, completed transactions, outstanding collections, and supplier commitments required reviewing multiple spreadsheets, email conversations, and accounting records.
Although the necessary information existed, it was fragmented across different sources and often required manual effort to consolidate.
The new platform introduced a centralized dashboard that provides real-time visibility into the organization’s financial operations.
Management can now monitor:
- Total payment obligations
- Completed payments
- Pending payments
- Outstanding collections
- Supplier exposure
- Currency-based financial distribution
- Weekly and monthly payment trends
All information is presented through a combination of summary metrics, operational lists, and graphical dashboards.
This level of visibility significantly improves decision-making capabilities.
Instead of reacting to issues after they occur, managers can proactively identify payment bottlenecks, collection delays, or cash flow risks before they become operational problems.
The dashboard also provides a historical record of financial activities, making it possible to analyze trends over time and evaluate operational performance using real business data rather than assumptions.
Most importantly, financial information is no longer trapped inside spreadsheets.
It is available in real time, accessible to authorized users, and continuously updated as business activities occur.
Figure 4. Real-Time Financial Visibility Dashboard
Management can monitor payment activities, collection status, supplier obligations, and financial performance through a centralized dashboard designed for operational visibility and decision support.
Conclusion
This project reinforced one of the core principles discussed in Part 1 of this series.
Digital transformation is not about replacing existing tools with newer technologies. It is about improving business processes, increasing visibility, and creating measurable operational outcomes.
The original payment planning process was functional. Payments were being tracked, suppliers were being paid, and financial operations continued successfully. However, the organization lacked the visibility, traceability, and reporting capabilities required to support growth and informed decision-making.
By redesigning the process and leveraging no-code technologies such as Google Sheets, Google AppSheet, and Google Apps Script, it became possible to transform a collection of spreadsheets into a centralized financial operations platform.
The result was not merely automation.
The result was operational transparency.
Employees continued to work through simple and familiar interfaces. Finance teams gained better control over payment planning. Management gained real-time visibility into financial activities. Historical data became accessible and reportable.
Most importantly, the organization achieved these outcomes without introducing ERP-level complexity or forcing users to adopt disruptive new workflows.
For many SMBs, this may be one of the most important lessons of digital transformation.
The objective is not to implement the most sophisticated technology available.
The objective is to create better processes, provide better visibility, and enable better decisions.
Technology simply makes those objectives achievable.
Continuing the Journey
This article is part of an ongoing series exploring practical digital transformation initiatives within a small IT services organization.
Part 1
Digital Transformation in SMBs: A Process-First Approach
Part 2
Building a No-Code ITSM Platform for SMBs: Operational Visibility Without the Heavyweight Overhead
Future articles will explore additional transformation projects, including license lifecycle management, CRM processes, task management, and other operational workflows implemented using low-code and no-code technologies.