Browse 9 articles tagged finance-controls across approvals, auditability, plugins, and controlled AI operations.
The configuration underneath an approval gate - durable resume and revalidation, role separation as policy, building gated actions, and the problems still open.
Read Approval Design: Durability, Policy, and Plugins →A single AI-recommended customer refund moves through a two-person review gate, from recommendation to execution record, on real screens inside Latch.
Read Approval Design in Practice: One Refund, End to End →Immutable storage helps, but payments teams also need approval history, event context, and one case record when discovery asks how a decision was made.
Read Immutable Payment Audit Trails Need Workflow Context →Four-eyes principle, maker-checker, dual control, and segregation of duties are related but not identical. Here is what changes in workflow design and audita...
Read Four-Eyes Principle, Maker-Checker, and Segregation of Duties: What Actually Differs →Compliance audit logging works best when it captures origin, authority, blocked paths, exception handling, and action outcomes inside the operational case re...
Read Audit Logging for Compliance Operations →Replace forwarded-email approvals with case-centric four-eyes control that keeps role boundaries, denied attempts, and execution outcomes visible.
Read How to Run Four-Eyes Control Without Inbox Approvals →High-risk approval workflows need origin, authority, denied paths, outcomes, and case-linked evidence in one immutable audit log.
Read What Auditors Need to See in a High-Risk Approval Workflow →Why finance exception handling needs four-eyes control, structured evidence, and audit-ready review before unauthorized actions slip through.
Read Finance Exception Handling Needs Four-Eyes Control →Make reprocessing explicit, permissioned, and auditable so teams can retry failed work without tribal knowledge or weak controls.
Read Turn Reprocessing from Tribal Knowledge into a Governed Action →