Use case / SOX

Maker-checker for invoice chase sends

Require a second teammate before Mark as sent. The requester cannot approve their own chase — logged for auditors on Business.

Open SOX reporting AR SOX hub →

Why makers and checkers matter for AR

SOX ICFR expects dual control on actions that affect financial reporting evidence. Invoice chase sends are often informal — docstoc makes the approval chain explicit without auto-emailing customers.

What you get

  • SoD toggle — require approval before Mark as sent
  • Requester ≠ approver — enforced in the API
  • Email notify — teammates get a request to review
  • One-time consume — an approval cannot be reused after send
  • Audit log — every request and decision is attributable

FAQ

Does docstoc auto-send chase emails after approval?

No. You always send from your own inbox. Maker-checker gates Mark as sent / send-like events so the audit trail is dual-controlled.

Which plan includes maker-checker?

Business ($39.99/mo). Enable it under SOX reporting → Retention & SoD.

Related

SOX reporting →Dashboard readiness and auditor packs.Auditor packs →HTML + SHA-256 + OpenTimestamps.SOX compliance →Framework overview.Compare →Workiva, FloQast, AuditBoard, Hyperproof.vs Workiva →AR SOX without a reporting suite.vs FloQast →Collections ICFR next to close.