Portfolio Monitoring Review & Operations Manual
Analysed why portfolio monitoring was reactive, using COSO, BPM process mapping and interviews, and designed the fix.
Diagram
Context
My graduation project for the BBA in International Business, carried out inside Zintra Capital during my internship.
Problem
Invoices rejected after purchase, or payments that never arrived, were often noticed late. Checks depended on individual habits, and each of 30+ debtor portals used its own status names.
What I did
- Interviewed the team working on due diligence, collections and reporting.
- Mapped the process in BPM and assessed its controls against the COSO framework.
- Traced the problems to root causes and wrote both manuals.
Solution
- Operations Manual
- Procedures for pre-purchase due diligence, the daily workflow, bank reconciliation and a monthly portfolio control cycle.
- Debtor-status manual
- Maps the statuses of 30+ debtor portals to 7 internal codes, so everyone classifies invoices the same way.
The control cycle in the manual
- 1 · Due diligenceInvoice status checked on the debtor portal before purchase.
- 2 · Daily workflowPurchased invoices checked so rejections are flagged early.
- 3 · Bank reconciliationCollections matched to the bank statements.
- 4 · Monthly controlA fixed review of the whole portfolio closes the cycle.
Result
- The Operations Manual was adopted by the company.
- One shared status language: 30+ portals → 7 internal codes.
Evidence
The thesis and both manuals are internal company documents, so they are described here rather than published.
Tools
COSO · BPM · Interviews · Word · Excel