Borrowers by requirements, one grid.
Green is approved, teal is submitted and under review, amber is pending and on time, coral is overdue. Sort by overdue count to triage this morning's work in ten seconds.
Submission tracking software replaces the multi-tab spreadsheet fund operations teams use to chase compliance. One live matrix puts every counterparty on a row, every reporting requirement on a column, and every cell shows the current submission status.
Every counterparty, every requirement, one screen.
A full 191-by-27 matrix at production scale. Sticky first column, cells colored by status, drill-down to any submission. The tracker is how fund operations triage in the morning and close out at end of day.
Three inputs, one matrix.
Counterparties, imported once
Pull from your deal book, your CRM, or a CSV. Every counterparty becomes a row, grouped by fund, sector, and subsector, so you can filter the matrix without renaming anything.
Requirements, cascaded down
Assign 27 seeded requirement types (AFS, QMA, CC, SEMR, ESAP, PAR30, PAR90 and more) or your own custom types at the fund, sector, subsector, or counterparty level. Cascading rules mean one assignment covers many cells.
Status, live
Every cell picks up its status from the shared submission workflow. A borrower submits and the cell flips from amber to teal. A manager approves and it flips to green. A due date passes without activity and it flips to coral, automatically.
Same matrix, asked instead of scrolled
| Counterparty | Requirement | |
|---|---|---|
| Sahel Agri-Co | QMA · Q2 | 4 days overdue |
| Northstar Energy | ESAP | 9 days overdue |
| Lakeview Microbank | Compliance cert | Submitted |
The same cells, filtered to what's actionable
Sort the 191-by-27 matrix by overdue count and this morning's queue is the whole screen: no scrolling past green cells to find the ones that need a nudge.
Who's overdue on ESAP this week?
One counterparty overdue on ESAP:
Illustrative figures. Same shared submission workflow the matrix reads from, so the answer and the grid can never disagree.
A column filter you can just ask for
The MCP layer reads the same status the tracker cells do, read-only and logged to the user who asked, for the morning nobody wants to open the full grid.
What does a submission tracker do in fund compliance?+
A submission tracker gives fund operations one grid that shows every counterparty as a row and every reporting requirement as a column. Each cell is colored by the submission's current status (Approved, Submitted, Pending, Overdue, or Not Applicable). Instead of reconciling multiple spreadsheets or email threads, the team sees the full compliance posture on one screen and can drill into any cell to reach the underlying submission.
How is this different from a compliance calendar?+
The compliance calendar shows what is due when, ordered by date. The submission tracker shows where every obligation currently stands, ordered by counterparty and requirement. Most fund teams use both together: the calendar for forward-looking scheduling, the tracker for operational triage.
Can the tracker scale to 300 counterparties?+
Yes. The tracker is designed for 30 to 300 counterparties by 10 to 40 reporting requirements. Row and column headers are sticky, cells render as small colored tiles, and virtualization keeps scroll smooth even at the largest portfolio sizes. Filters reduce the visible matrix when you need to focus on a subset.
What happens when a submission status changes?+
The cell color updates on the next page load. All status transitions flow through the shared submission workflow (Pending to Submitted to Approved, Rejected, or ReworkRequired). The audit trail captures every transition with timestamp and actor, so a cell that changed from amber to green always has a traceable reason.