Settlement exports and segregation of duties

Last reviewed: 2026-04-27 · Owner: Product & Engineering (finance review for mutations)

Goal

Understand how settlement and export surfaces are governed so partner admins do not bypass commercial controls (ADR-037).

Prerequisites

• Finance or platform role if you will download sensitive exports (SPEC-027).
• No expectation that partner admins can self-approve commercial policy changes.

Steps

1. Read commercial posture on partner detail responses—treat as read-only unless your role allows mutation APIs.
2. Request exports through approved finance workflows; avoid sharing CSV extracts in unsecured channels.
3. Link troubleshooting to Finance Sync when reconciliation requires adapter runs (SPEC-033).

Verify

• Attempts to mutate segregated fields without authority fail with explicit errors.
• Audit trails exist for approved changes (per deployment configuration).

If it fails

Stop before “workarounds” that bypass SoD. Escalate to finance operations with policy references, not ad hoc instructions.

Further reading

• SPEC-027 Revshare Settlement Export and Finance Access Contract.
• ADR-037 Tapestry Admin Console Commercial Policy Governance.
• Revshare exports — settlement vs engagement (console)
• Finance Sync overview