Open the exact missing PO, receipt or invoice source.
CONTROLLER CONTROL TOWER
Know what is blocking AP—and who can unblock it.
Prioritise blocked value, close risk, approval aging and recurring exceptions across entities—then drill into the evidence and owner behind each item.
See the exposure.
Find the next action.
Portfolio viewRequest evidence · keep the item open
See open exposure across entities, owners and deadlines.
Prioritize the receipt gap ahead of lower-impact coding work.
Open the invoice, failed control and missing evidence behind the amount.
Assign the warehouse request. The item stays open until the evidence changes.
ACTIONABLE EXPOSURE
Start with the blocker. Open the transaction causing it.
Each category answers how much is affected, who owns it and what must happen next.
See the required authority and time waiting.
Inspect the accounting-system response and retry owner.
Review demand, client responses, material blockers and close exposure across books.
Blocked value, approval aging, evidence gaps and ERP failures across entities.
SLA aging, touch rate, exception load, throughput and service dependencies.
What should an AP control tower show?
It should rank material exposure and allow the controller to trace every aggregate number to the entity, transaction, failed control, source evidence and current owner behind it.
WORKSPACES BY ROLE
Do not give every finance role the same invoice inbox.
Each role sees the same transaction state through the decisions they own.
Portfolio risk
Blocked value, aging, close impact and recurrence across entities.
Material judgment
Exceptions requiring accounting treatment or control review.
Standard work
Evidence collection, routine corrections and assigned actions.
CONTROL SURFACE
Move from aggregate exposure to the work causing it.
The controller model connects material exposure, ownership and source-level transaction state.
Prioritize the blocker, not just the amount.
- 01Portfolio status
- 02Vendor-level transaction state
- 03Operational total and action
QUEUE SIZE IS NOT RISK
Exposure earns the order.
Rank work by financial value, close impact, time waiting, control severity, recurrence and external dependency.
Financial exposure
How much value is blocked or uncertain?
Close impact
Could the item delay a reporting deadline?
Control severity
Which policy or evidence requirement failed?
Recurrence
Is the same cause consuming the operation repeatedly?
EVERY METRIC RETURNS TO A SOURCE
Portfolio metric → entity → transaction → failed control → evidence → owner.
A controller should never receive a number that cannot be opened and explained.
Portfolio
₹6.3L blocked across two entities.
Priority
₹4.2L receipt gap due today.
Transaction
INV-2048 has 200 unsupported units.
Evidence
Second GRN is missing.
Owner
Warehouse operations receives the request.
CONTROL HEALTH
Measure whether automation remains safe.
Straight-through rate
Eligible transactions completed without manual rescue.
Exception recurrence
Repeated causes by vendor, entity and owner.
Approval aging
Time waiting on required authority.
Failed handoffs
Accounting submissions still unresolved.
See the risks inside your AP population.
Start with blocked value, close exposure and the transactions behind them.

BY NUMBER7 AI