Settings execution
Read the exact action guide for prerequisites, identifier discovery, supported input, effects, captured successful and refused responses, verification and recovery. Synthetic fixture results do not authorize a live mutation or establish a provider outcome.
- Get invoice email settings: Read the effective invoice From and Reply-To, the workspace sender and organization sending domains.
- Set invoice email sender: Create or update the invoice sending profile for this Books workspace on a verified organization domain. Requires organization email-management permission as well as Books settings permission.
- Remove workspace invoice sender: Deactivate only this Books workspace sender profiles and resume inherited organization or platform sender resolution.
- Connect invoice sending domain: Register an organization-owned domain through Nexus and return the authentication DNS records to publish. Requires organization email-management permission.
- Verify invoice sending domain: Ask Nexus to verify the authentication DNS records for an organization sending domain. Does not send an email.
- Get workspace settings: Read the workspace accounting, invoice identity and invoice approval-automation settings.
- List invoice automation payment options: List the Topolo Pay merchants enabled for automatic payment-link creation in this Books workspace.
- Get invoice Brand connection: List invoice-compatible Brand kits in this organization and the kit connected to this exact Books workspace.
- Connect invoice Brand kit: Connect one published, invoice-compatible Brand kit to this exact Books workspace.
- Disconnect invoice Brand kit: Remove this Books workspace invoice Brand connection.
- Update workspace settings: Set accounting, invoice identity and invoice approval-automation settings. Automatic payment links require automatic customer pages and a workspace-authorised Topolo Pay merchant.
Evidence
Actual Books route handlers and the exported Worker were exercised against five local SQLite D1 concern databases with all committed migrations, the real posting Durable Object and local R2. Route captures use synthetic verified Auth; Worker captures use synthetic Auth transports. Nexus, Brand, Notify, Pay, Mercury and Xero responses are explicitly simulated at the provider transport boundary. Captures prove local request/response behavior and canonical SDK projection, not live bank access, payment movement, email delivery, provider eligibility, tax compliance, encrypted custody, scheduled execution, deployment or production completion. Fixture identities, credentials, addresses and records authorize no live operation.