FloQast vs Trintech

Requirement evaluated: Complete audit trail of every edit to an entry before posting, including who changed what

For a SOX-controlled manufacturing group running six entities in NetSuite, FloQast's dedicated Journal Entry Management (JEM) module is the relevant mechanism. Within JEM, FloQast explicitly commits to audit readiness through automatic logs of changes, approvals, and updates that ensure every journal is fully traceable. The workflow enforces preparer/reviewer segregation of duties: approved entries are locked to secure financial integrity, and configurable approval workflows prevent unauthorized approvals and ensure preparers cannot review their own work. …

Limitations: The buyer's requirement is for a forensic-quality log of every edit, showing who changed which field and what the value was before and after, for the full pre-posting lifecycle. …

Requirement evaluated: Complete audit trail of every edit to an entry before posting, including who changed what

For a SOX-controlled manufacturing close like this buyer's, Trintech's journal entry capability sits across two platforms: Cadency (enterprise) and Adra (mid-market, with Adra Journal Entry launched April 2025). Both platforms route journal entries through configurable preparer, reviewer, and approval workflows before ERP posting. Trintech's product page documents that 'every action from preparation, review, and approval to posting is logged with timestamps and user attribution,' and that every journal includes metadata on 'who prepared, reviewed, and posted' with audit logs accessible directly from the journal entry. …

Limitations: The documented audit trail mechanism captures who acted at each workflow stage (prepare, review, approve, post) with timestamps, which exceeds the buyer's current spreadsheet baseline; but field-level before/after change capture on intermediate saves prior to workflow submission is not confirmed in available public doc …

Requirement evaluated: Supporting documentation attached to the reconciliation and retained with it across periods

For your 180 monthly balance sheet reconciliations across 6 entities, FloQast Account Reconciliations pulls each account's balance from the ERP and stores the support (bank statements, subledger detail, schedules or spreadsheets) with that reconciliation (FloQast Account Reconciliations page). Support, review notes and sign-offs stay attached to each reconciliation, and audit reports track changes, so the evidence sits with the account and period balance rather than only on a checklist task. FloQast Close's rollforward feature moves documents into the next close, with bulk roll forward for multiple folders at once (FloQademy). …

Limitations: I could not locate the help-center article that states exactly how attachments are retained per period after rollforward, or whether recurring support is carried forward automatically or by a manual rollforward step. …

Requirement evaluated: Supporting documentation attached to the reconciliation and retained with it across periods

For your 180 monthly balance sheet reconciliations across 6 entities, Cadency keeps supporting files on the reconciliation record itself, not on a checklist task. The Reconciliation Detail screen shows the files attached in support of the reconciliation, the notes, the account's reconciliation history, and any child accounts. To avoid re-attaching recurring support each month, a Carryover function brings forward items from the previous period, such as open reconciling items, notes, or files. Users can also compare the current reconciliation with one from a previous period. For audit, Trintech says supporting material is captured in an online, audit-ready eBinder. …

Limitations: The carry-forward behavior and the decertify rule come from the Cadency v11 help page. The help page says decertifying a reconciliation deletes that period's Reconciliation Details. Your SOX team should confirm how that affects attachments already reviewed. …

Requirement evaluated: Real-time close status dashboard by entity and by owner, without anyone reporting progress by email

For a manufacturing group running 6 legal entities across the US, Mexico, and the Netherlands with 140 close tasks currently tracked in a shared spreadsheet, FloQast's Close Checklist and Close Analytics modules directly replace that model. Each task is configured with an owner, due date, entity tag, dependencies, and duration; when a preparer completes or signs off on a task or linked reconciliation, FloQast automatically updates the master checklist, eliminating self-reported status emails entirely. Controllers access a live dashboard that surfaces task status by team member, business process, and entity simultaneously, including at-risk and overdue flagging. …

Limitations: Third-party reviewers note that organizations with very high entity counts can experience occasional reconciliation sync delays, and that highly entity-specific checklist exceptions may still require parallel workpaper management outside FloQast. …

Requirement evaluated: Real-time close status dashboard by entity and by owner, without anyone reporting progress by email

Your team currently coordinates 140 tasks across 6 entities through a shared spreadsheet and daily status calls. Cadency Close Management replaces that pattern with a persistent, dashboard-driven framework that updates task status in real time as each action is taken, with no self-reporting required from task owners. Controllers and staff can view the status of outstanding tasks and any potential bottlenecks or delays through real-time management dashboard views, eliminating the need for in-person status update meetings. …

Limitations: The documented customer evidence covers environments far larger than your 6-entity, 140-task structure (Trintech cites a customer with 225 entities and 40 countries achieving daily close visibility), so scale is not a constraint here. …

Requirement evaluated: SOX control framework held in the system, with each control linked to the close task or reconciliation that evidences it

For your 6-entity group, with about 140 close tasks, about 180 reconciliations, and an annual SOX review, FloQast Compliance Management holds the risk control matrix (RCM) inside the platform. Controls are linked to the close and workflows already tracked in FloQast, so evidence is captured at the source. Teams capture controls while performing daily tasks like the Close or account reconciliation, which gives visibility into control ownership and execution. FloQademy course titles also list a Quick View that shows all linked Compliance items, plus RCM snapshots, control testing, and external auditor access (FloQademy Risk & Compliance). …

Limitations: The vendor material I found is mostly launch announcements, product pages, and course titles. I did not find a help-center article showing exactly how a control is linked to a task or reconciliation, so confirm that link mapping and the evidence report in a demo. …

Requirement evaluated: SOX control framework held in the system, with each control linked to the close task or reconciliation that evidences it

For a six-entity NetSuite group running about 140 close tasks and 180 reconciliations on a spreadsheet, the relevant piece is Cadency's Governance, Risk and Compliance module. Trintech describes it as extended governance of financial close tasks related to close, reconciliations and journal entry efforts. Trintech says the module includes formal workflow, control testing and remediation management with attachments, and that controls, action plans, audit trails and eBinders can be viewed remotely by internal and external auditors. One third-party review says the compliance module produces audit-ready eBinders with controlled access for auditors. …

Limitations: The module is documented as Cadency-only; one independent review states Adra has no GRC module. A $210M buyer may be steered to Adra, so confirm Cadency is in scope and priced for six entities. …

Requirement evaluated: Transfer pricing documentation retained with the intercompany activity it supports

For a manufacturing group running intercompany flows across six legal entities in three jurisdictions, FloQast offers two attachment surfaces. First, its dedicated Intercompany module (part of the FloQast Reporting add-on, priced separately) provides a shared intercompany matrix where cross-entity teams can capture and store notes, documents, updates, and decisions alongside intercompany activity, creating an audit trail of all intercompany adjustments (FloQast Intercompany product page). …

Limitations: Document attachment lives at the reconciliation or intercompany matrix level, not at the individual transaction line. For this buyer, where a single intercompany reconciliation account may aggregate flows governed by different transfer pricing rates across the US, Mexico, and Netherlands entities, attaching one memo to …

Requirement evaluated: Transfer pricing documentation retained with the intercompany activity it supports

For a six-entity manufacturing and distribution group running NetSuite, Trintech's Cadency Intercompany module handles transfer pricing documentation retention at the individual transaction record level. When Subsidiary A proposes an intercompany transaction, Cadency's configurable workflow requires the initiating entity to attach relevant supporting documentation before the request is routed to the counterparty; the receiving entity cannot approve the transaction until those documents are present. Once both entities agree on the amount with supporting documentation attached, the system generates postings automatically for the payable and receivable sub-ledgers. …

Limitations: Trintech's blog and best-practice documentation describe the attachment mechanism in terms of intercompany invoices and general supporting materials; there is no published documentation explicitly naming transfer pricing agreements or pricing memos as a distinct document type with dedicated metadata fields, so labeling …