Use case / SoD
Segregation of duties for collections
Separate who drafts/requests a chase from who approves Mark as sent — with workspace roles and a full approval history for auditors.
SoD without a GRC rollout
You do not need AuditBoard to enforce dual control on AR chase sends. Enable SoD in SOX reporting, invite a teammate, and every approval is logged.
Controls in product
- Workspace Admin vs Member
- Maker-checker on send (optional)
- Pending approvals queue in SOX reporting
- Request approval from the chase card
- Consumed after successful send
FAQ
Can one person approve their own send?
No — when SoD is on, the API rejects self-approval.