Finance Controls
Browse 10 articles tagged finance-controls across approvals, auditability, plugins, and controlled AI operations.
Construction Draw Approvals: From Payment Request to Audit Evidence
See a construction draw move through maker-checker review, payment release, audit evidence, grouped approval reporting, and PDF or Excel export in Latch.
Read article →Approval Design: Durability, Policy, and Plugins
The configuration underneath an approval gate - durable resume and revalidation, role separation as policy, building gated actions, and the problems still open.
Approval Design in Practice: One Refund, End to End
A single AI-recommended customer refund moves through a two-person review gate, from recommendation to execution record, on real screens inside Latch.
Immutable Payment Audit Trails Need Workflow Context
An immutable payment file is not enough for legal discovery. What workflow context an audit trail has to carry alongside it.
Four-Eyes Principle, Maker-Checker, and Segregation of Duties: What Actually Differs
Four-eyes, maker-checker, dual control, and segregation of duties are related but distinct. What changes in workflow design for each.
Audit Logging for Compliance Operations
What compliance operations teams should record in an audit log so a reviewer can reconstruct a decision without asking anyone.
Four-eyes control without inbox approvals
Keep the request, the independent review, and the execution result on one case. A practical way to replace forwarded-email approvals.
What Auditors Need to See in a High-Risk Approval Workflow
High-risk approval workflows need origin, authority, denied paths, outcomes, and case-linked evidence in one immutable audit log.
Finance Exception Handling Needs Four-Eyes Control
Why finance exception handling needs four-eyes control, structured evidence, and audit-ready review before unauthorized actions slip through.
Turn Reprocessing from Tribal Knowledge into a Governed Action
Make reprocessing explicit, permissioned, and auditable so teams can retry failed work without tribal knowledge or weak controls.
Start with one workflow
Follow a request through triage, review, and a plugin action. See the record that each step leaves behind.