01
the user uploads input files from CRM and Optima
Case study
CRM and Optima reporting automation
The automation combined CRM and Optima data, organized client matching, and prepared reports without manual file assembly.
Key implementation elements
content-based file identification instead of filename matching
work time normalization to a safe format
client matching despite naming differences
automatic update of the settlement report
archiving input files when the process is finished
Problem before implementation
Problem before implementation
Monthly client settlement required combining data from two different sources. Client names were inconsistent, input files changed names, and importing long work times into Google Sheets caused formatting errors.
manual report assembly from CRM and Optima
different names for the same clients in two systems
input files hard to identify by filename alone
errors when importing work time and settling later
What we built
What we built
We built a Google Apps Script tool operating on Google Sheets. The system recognized files by content, converted data, normalized work time, matched clients, and updated the monthly settlement sheet.
content-based file identification instead of filename matching
work time normalization to a safe format
client matching despite naming differences
automatic update of the settlement report
archiving input files when the process is finished
Process after implementation
How the process works after implementation
From input data to a cleaner outcome. Below is a shortened view of the process after implementation.
02
the system recognizes each file type by its content
03
data is converted and cleaned into one shared format
04
the comparison mechanism matches clients across systems
05
the monthly report updates the settlement sheet
06
files are archived by month and year
Before / after
How the process changed
The table shows the main differences between manual work and the process after implementation.
| Before implementation | After implementation |
|---|---|
| manual combination of data from two systems | automated processing of CRM and Optima data |
| files recognized by changing filenames | file identification by headers and content |
| inconsistent client names | automatic name matching and normalization |
| time formatting errors after import | controlled time storage in a safe format |
Business outcome
shorter time needed for monthly settlements
less manual combining of data from different sources
lower reporting error risk
a more organized process for financial and operational data
Technologies
Google Apps ScriptGoogle SheetsGoogle DriveGoogle Sheets APICSV / XLSX
What can be implemented in a similar way
What can be implemented in a similar way
These are examples of processes that can be organized with a similar approach: start from one concrete problem and a clear data flow.
monthly operational reports from multiple sources
combining CRM, accounting, and settlement data
normalizing CSV and XLSX imports
automatic archiving of process files
Related services
This type of implementation can be connected with MorenaTech's core areas
If a similar process still runs manually or is scattered across files, it can be connected with automation services, Google Workspace, or further process development.
Final CTA
Want to organize reporting in a similar way in your company?
If your team still manually combines data from several files and systems, this can be turned into a process with far fewer manual steps.