A Coupa requisition asks a yes-or-no question of the business: do we trust this vendor enough to spend money with them. The requisition itself is a transactional record. The judgment that releases it is not. When a procurement agent does the diligence, the brief it writes, the risk flags it raises, and the human who signed off all need to live somewhere durable, attributed, and re-openable. That somewhere is Dock. The Coupa PO stays canonical for spend. Dock stays canonical for why the spend was approved.
Coupa and SAP Ariba stay the system of record for the raw requisition, supplier master, and PO state. Dock is the system of record for what the agent interpreted from that data. Each Dock row carries a pointer back to the Coupa record (coupa_requisition_id, coupa_supplier_id), the agent identity that drafted the diligence, the reviewer who countersigned, and the timestamp of every state change. The agent re-fetches Coupa data via fresh API reads whenever it needs current requisition state, never trusting a stale cache.
The Dock surface: Vendor Diligence Briefs
| coupa_requisition_id | vendor | agent_recommendation | risk_flags | drafted_by | first_approver | second_approver | status |
|---|---|---|---|---|---|---|---|
| REQ-44219 | Northwind Analytics | Approve at $84K | None material | agent.procurement.v3 | priya.s (Procurement) | jordan.m (Finance) | PO released |
| REQ-44231 | Bramble Logistics | Hold | OFAC adverse media; insurance lapsed | agent.procurement.v3 | priya.s (Procurement) | (awaiting) | On hold |
| REQ-44247 | Cobalt Print Co | Approve at $12K with NDA | New vendor, no SOC 2 | agent.procurement.v3 | priya.s (Procurement) | counsel.r (Legal) | NDA pending |
The workflow
A buyer files REQ-44231 in Coupa for $310K with Bramble Logistics. Coupa pushes the requisition event to Dock. The procurement agent opens a new diligence row, re-fetches Coupa supplier history, runs sanctions screens, pulls insurance certificates from the supplier portal, and writes a 400-word brief into the row. It flags OFAC adverse media and a lapsed insurance cert. Priya, the procurement reviewer, reads the brief, agrees with the hold, and countersigns the recommendation. Because the recommendation is "hold," no second key is needed and Coupa receives a hold callback that freezes the PO. If Priya had approved, the row would route to a second approver in Finance, and only the two-key handshake would release the PO back to Coupa. The brief, both signatures, and the underlying Coupa pointers are now permanent audit evidence.
Why this matters
Procurement audits do not ask whether a PO existed. They ask who decided, on what evidence, and whether that decision was countersigned. Storing the agent's reasoning inside the PO record is the wrong shape: POs are mutable and built for spend, not provenance. A separate diligence ledger with stable agent identity and a dual-key cascade is what auditors actually want to see.
Deloitte's CPO research found high-performing procurement teams are roughly eighteen times more likely than peers to have deployed AI capabilities, and that only eighteen percent of teams formally track tier-one supplier risk. The bottleneck is not the model. It is the workspace where the model's work becomes reviewable.
Coupa remains excellent at transactions. Dock makes the agent's judgment around those transactions auditable, attributable, and revocable.
See the procurement pillar for the full pattern, the accounting pillar for how the PO ties to AP, the legal pillar for NDA gating, the audit and compliance guide for evidence shape, the two-key handshake reference for the release gate, and the agent identity primer for why the drafter must be named.
Try Dock with your Coupa tenant. Point the procurement agent at one open requisition and see the brief in your workspace within an hour.
FAQ
Does Dock replace Coupa? No. Coupa stays the requisition and PO system of record. Dock holds the agent-drafted diligence and the attributed approval that releases the Coupa PO.
What about SAP Ariba shops? The same pattern applies. The Dock row carries ariba_requisition_id instead, and the release callback targets the Ariba API. Per CIPS, governance standards apply equally across procurement platforms.
Can the agent release a PO on its own? No. The two-key cascade is enforced at the Dock layer. The agent drafts, a human countersigns, and only then does Dock call the Coupa release endpoint.
Where does the audit trail live? Inside the Dock row. Every state change is timestamped, attributed to a named agent or human, and re-openable for years after the Coupa PO is closed, matching the evidence shape Deloitte's CPO survey describes as table stakes for top-quartile teams.
