How Trintech works

Requirement evaluated: Recurring and templated entries (accruals, depreciation, amortization) generated each period with calculated amounts

For a manufacturing group running 6 entities on NetSuite with recurring accruals, depreciation, and amortization entries to generate each period, Trintech addresses this through two complementary layers. In Cadency (the enterprise product), users can proactively define recurring journal entries on a set schedule, with automatic posting capability for accrual, depreciation, amortization, and allocation journals, managed through a dedicated recurring journal entry dashboard. Accrual entries specifically are handled with standardized templates, automated calculations, and configurable approval workflows, so amounts are computed by the system rather than re-keyed each period. …

Limitations: The Adra (mid-market) product currently supports cloning and reversing recurring entries but had fully automated rule-based recurring JE generation listed as a roadmap item as of early 2025; buyers targeting that product line should confirm current availability in a demo. …

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, 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

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 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 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 …