CPDERP system for agency operations

An agency needs to know more than whether a task is complete. It must connect that work to the person who delivered it, the amount owed, the correct payment route and the project that carries the cost. CPD brings those records into one operational chain while keeping the spreadsheet-based workflows the team already used.

The important architectural choice was to connect the existing working environment instead of forcing every operational record into a new interface at once. The spreadsheets remain practical entry and review surfaces, while CPD supplies the rules that relate their data. That keeps the process familiar for the team but gives calculations and status changes a shared system behind them.

The goal was to connect completed work with the amounts owed to each contributor and show how those costs affect a project's result. The system also had to support payment preparation, keep operational and financial records consistent and combine individual project calculations into one portfolio overview.

• Separated records

  Work entries, accruals and payment details came from different spreadsheet areas and needed reliable matching.

• Manual preparation

  Before a payout, the team had to understand what an amount related to and whether it had already been processed.

• Fragmented finances

  Project figures had to roll up into agency totals without assembling separate reports by hand.

The workflow separates new records from existing ones before writing the result. That distinction is essential for repeatable processing: running a synchronization again should update the right entry instead of creating a second payment or losing a correction. Acknowledgement steps also make the result available to the next stage of the data flow.

Because the payment register, project calculation and portfolio overview use connected records, a cost can be reviewed at the level where the team needs it. Operations sees the payout status, a project lead sees its effect on margin, and management sees the combined result across reporting periods without maintaining three unrelated versions of the same figure.

We implemented the processing and calculation logic with Next.js and TypeScript and connected it to the spreadsheet workflows shown in the case. Development covered work records, payout preparation, synchronization and financial reporting. Testing focused on accuracy and on the relationships between the outputs rather than treating each table as an isolated screen.

CPD connects work tracking with payout preparation and financial reporting. The agency can maintain records for internal and external contributors, calculate what is owed and review the resulting costs at project and portfolio level. Connected data flows and shared business logic make the operation repeatable without replacing every spreadsheet the team already knows.