Close
Workflows - Single Item Lock
Admins can now enable Single Item Lock at the entity level through Settings > Entities > Manage Entities. When activated, individual Checklist and Reconciliation items automatically lock once the final reviewer signs off, without waiting for a full Folder Lock. Admins can choose from three locking options:
- Lock item and documents - Once all sign-offs are complete, the item is fully locked. Sign-offs, documents, and item details can no longer be edited.
- Lock documents only - Only document uploads and removals are restricted. Other actions on the item remain available.
- Locking disabled - Single Item Lock is off for this entity.
Admins and Managers can also manually lock or unlock items from the kebab menu at any time, with a confirmation step before each action. Locked items cannot be reassigned, signed off on, or have documents added or removed, and they are excluded from bulk actions. If a reconciliation enters a redo state due to a general ledger or trial balance change, or falls out of balance with Strict Tie-Out mode enabled, the item automatically unlocks so the preparer can rework it. Checklist template uploads also cannot remove or modify locked items. Once a Folder is locked, individual items within it cannot be unlocked until the Folder itself is unlocked.
Workflows - Separate Strict Sign-Off
Strict Sign-Off Mode is now broken up into three independent settings (Settings > Entities > Manage Entities), giving you granular control over which sign-off rules apply to each entity. The three options are:
- Restricting sign-off to assigned users and Admins/Managers only
- Preventing the same user from signing off as both preparer and reviewer
- Requiring preparers to sign off before reviewers
Each option can be enabled or disabled individually, so you are no longer required to adopt all Strict Sign-Off rules as a single package.
If you previously had Strict Sign-Off enabled, your existing configuration is automatically mapped to the new individual settings with no action required. A badge next to the setting title indicates how many of the three options are currently active, providing a quick view of your entity's sign-off configuration.
Incremental Journal Entries for Amortization & Depreciation
When new amortization or depreciation items are added after an expense journal entry has already been posted, you can generate an incremental journal entry directly in FloQast instead of posting manually in your ERP.
FloQast automatically detects newly added items and prompts you to create an incremental entry, pre-populated with only those items. This keeps your journal entry workflow and audit trail in one place and ensures all monthly expense entries are captured in the correct period.
Additional improvements in this release:
- When connected via a direct ERP integration (NetSuite, Sage Intacct, or QuickBooks Online), account selection dropdowns pull directly from your general ledger, eliminating manual entry for new items and disposals.
- For monthly expense journal entries, you can apply any journal entry field and value to the offset side of an expense entry.
Reporting
Show margins, ratios, and unit counts without exporting to Excel
Margin rates, headcount metrics, and ratio-based subtotals are standard line items in management reporting. Report Builder calculation rows now support percentage and whole-number formats: define a numerator and denominator from any available row or group (for example, Gross Margin ÷ Revenue) and the result renders inline.
Presentation controls ship alongside the format work, including a distinct calculation-row icon, bold and color formatting, adjustable indentation for hierarchy, and tooltips on Amount Type selectors.
Drill into transaction-level detail without removing your pivot
Reviewing transaction-level activity on grouped report data usually forces a choice: keep the pivot for context, or break it apart to inspect the underlying detail. Report Builder now renders transactions in a nested sub-table beneath each pivoted row, so the column structure stays intact while the activity underneath becomes visible. The detail table shows Subsidiary, Account Number, Account, Entry Date, Transaction Line Memo, and Amount by default, with a column selector for adjusting the visible fields.
Available to: All Report Builder customers
Manage variance collection structure from one place
Responsibilities shift mid-quarter. A new controller joins, a department restructures, a rule belongs in a different cadence. Reorganizing variance reviews has typically meant working through one rule at a time.
AI Variance Analysis now includes a Collections Management page, a centralized workspace where administrators and Power Users can edit Collection-level metadata (assignees, business start days, cadence) and move individual rules between Collections using bulk actions. Changes to Collection structures and assignments are auditable.
Reference prior period explanations without leaving Focus Mode
When drafting a variance explanation, accountants refer to how the same account or department was explained in prior periods. That check grounds the current narrative in consistent reasoning.
Focus Mode now surfaces prior-period AI variance explanations inline, pulled from the Trends View time span (defaulting to the prior 12 months), so multiple historical periods remain visible during analysis. An in-app setting controls whether AI Variance Analysis uses the prior period explanation as a drafting example for the current period; when enabled, the AI produces drafts more consistent with how similar variances have been explained, with your team reviewing each output before it's saved.
Trace every FDM rule back to its author
When a mapping rule produces an unexpected result, the first question is who built it and when. FDM rulesets often grow across multiple admins and many close cycles, which makes that question harder to answer than it should be. FDM mapping rules and primary dimension rules now display authorship metadata inline: created-by, last-edited-by, and the corresponding timestamps.
Rules created after this release have populated creator metadata; rules that existed prior show blank values. Each rule also carries a "Manual" or "AI" badge to indicate how it was created. The "AI" value is reserved for a future release that introduces AI-generated mapping rules.
Permanently remove FDM rules instead of stockpiling them
Active FDM rulesets accumulate stale, deactivated rules over time. Experimental rules, mistakes, and rules that have run their course all stay in the interface. FDM now supports permanent deletion of individual mapping rules and primary dimension rules through a trashcan icon on each rule card. A confirmation dialog appears before deletion, stating that the action is permanent and cannot be undone; when the rule being deleted is currently active rather than already deactivated, an additional warning surfaces.
Deactivation remains an available, softer alternative for rules you may want to retain in an inactive state.
Collapse list-based mapping logic into a single rule
Expressing a list-based condition in FDM, such as "department is one of: Engineering, Marketing, Sales," typically requires one rule per value, which inflates the ruleset size and adds maintenance overhead. FDM mapping rules and primary dimension rules now support three additional operators:
- Includes: lets you select multiple values in a single rule.
- Does Not Include: applies the same multi-select interface to exclusion rules.
- Include All: creates catch-all rules that match every value for a given dimension.
The Includes and Does Not Include dropdowns support Select All and Clear All, display a count of selected values, and offer in-line search for large value sets.
Allow Users to Copy Rules from Existing Rules
Variance analysis rule creation now includes a copy function, allowing you to duplicate an existing rule and adjust specific elements like scope filters or assignees without rebuilding shared conditions from scratch. This is useful when maintaining large sets of parallel rules that differ in only one dimension, where the previous workflow required building each rule independently.
Copying a rule keeps shared logic consistent across your library and reduces the manual effort involved in expanding or refining your ruleset.
NetSuite Transaction Linking
For customers using NetSuite, transaction IDs displayed in Report Builder and Variance Analysis are now clickable links that open the corresponding source record directly in NetSuite. The link dynamically resolves to the correct record based on the transaction's attributes, so you can move from analysis to source documentation in a single click.
This removes the need to switch systems and search manually when validating figures or investigating exceptions, keeping your review workflow anchored in FloQast.
Compliance
Author & Upload Date on Control Documents
Documents uploaded to the Controls module now display additional metadata, including the name of the user who uploaded the document and the date it was uploaded. This information appears alongside each document in the list, giving you visibility into who contributed each file without needing to track that detail separately. The display follows the same pattern used in the Risks and Tests tabs.
Key Reports & Key Systems - Copy and Rollforward of Compliance Programs
When you clone an audit project, key systems and key reports are now included alongside tests and PBCs that are linked to key reports. Statuses for cloned items are reset to "Not Started," giving you a clean starting point for the new audit period without manually resetting each artifact. Issues are not cloned as part of this process.
This expands the previous roll forward behavior, which left key systems and key reports out of the cloned project, and brings the feature closer to a complete year-over-year setup so you spend less time rebuilding your program at the start of each audit cycle.
Certifications - Ability to copy a certification (FT)
You can now copy an existing certification to use as the starting point for a new one, eliminating the need to rebuild the structure from scratch. From the Certifications landing page, select Copy Certification and choose which audit project the new certification should live in. You can only copy certifications into audit projects where you have Admin or Manager access.
If you copy a Control Review certification into a different audit project, processes are reset since available processes can differ between projects. If any round due dates have passed, you will need to update them before the certification can be activated.
Cross-program Linking
You can now create relationships between compliance items across different programs and projects, eliminating the need to duplicate documentation when the same risk, control, key system, or key report applies in multiple places. Establish links between risks and controls, key systems and controls, key systems and key reports, key reports and controls, or scoping line items and their related processes, risks, and controls. A single record serves as the source of truth and stays in sync wherever it's linked.
Supported relationships span the full program hierarchy, so an enterprise SOX program with separate IT, business process, and entity-level projects can share a common set of systems, reports, and risks rather than recreating them in each location. Links can be created through the interface or through bulk imports.
Platform
Icon Color Update
The action icons in your checklist Actions column have a refreshed look. The icons themselves now appear in a darker, neutral tone, with notification badges retaining their red color to keep pending items visually distinct.
Admin Settings Header-Nav Update
The Admin Settings navigation has moved to the top of the page, replacing the previous stacked header layout. Tabs like Workflows, Entities, Team Members, Roles, Groups, Checklist, Reconciliations, API Keys, Reports, AI, Connections, Financial Data Model, and File Upload now sit on a single row, freeing up vertical space for the content below.
You'll see more of your workflows, entities, and other configuration tables without scrolling.