.png)
Trintech Cadency Integration Guide
Trintech Cadency integrates with enterprise finance landscapes through tenant-specific APIs, file exchanges, integration services, and approved callbacks that must be confirmed for each deployment.
Trintech Cadency integration options at a glance
Cadency provides enterprise integration options for financial close and accounting operations, but the publicly reviewed material does not confirm a general REST, GraphQL, SOAP, webhook, or bulk API specification. Tenant-specific deployments may support APIs, scheduled imports and exports, managed file transfer, vendor-provided integration services, or selected callbacks. Cadency handles reconciliation, journal, close, matching, compliance, and intercompany information, while the exact resource names and exchange formats require confirmation. Martini can orchestrate these channels through scheduled or event-driven workflows, secure environment secrets, mappings, validation, business rules, and error handling without assuming direct database access.
| Integration point | Supported by Trintech Cadency? | Common use cases | How Martini supports it |
|---|---|---|---|
| REST APIs | Not confirmed | A tenant-specific REST API could exchange account reconciliations, close tasks, journal entries, or status data if Trintech provisions and documents it. | Martini can consume a supplied Cadency REST specification, authenticate requests using the confirmed method, map payloads, orchestrate calls, and expose normalized APIs. |
| Webhooks and outbound callbacks | Not confirmed | Selected Cadency events may be delivered through callbacks, but public documentation does not confirm general event coverage or supported state transitions. | If enabled, Martini can expose an API endpoint and receive callback notifications, validate them, retrieve current data where possible, and route workflow processing. |
| Bulk, asynchronous, or batch APIs | Not confirmed | Accounting and close processes may use batch-oriented exchanges, but a public Cadency bulk or asynchronous API specification was not verified. | Martini can orchestrate batches, track export or submission identifiers, split records, validate results, and handle asynchronous status checks when the tenant interface supports them. |
| File and attachment exchange | Limited | Cadency handles supporting accounting documentation and financial close information. Imports, exports, document exchange, SFTP, and attachment APIs require tenant-specific confirmation. | Martini can process approved files, transform CSV, Excel, JSON, or XML data where applicable, coordinate managed file-transfer workflows, and retain batch and error metadata. |
| Scheduled synchronization | Yes | Scheduled imports, exports, and incremental synchronization are practical options when real-time events or APIs are unavailable or incomplete. | Martini can trigger workflows on a schedule, maintain watermarks and overlap windows, apply pagination or batch logic, and route results to Cadency or downstream systems. |
| Authentication | Not confirmed | Cadency-specific OAuth, API keys, Basic Authentication, mutual TLS, tenant-issued tokens, scopes, and credential lifecycle requirements were not publicly confirmed. | Martini stores confirmed credentials in environment-specific secrets and applies the authentication configuration required by the Cadency tenant or integration endpoint. |
| Database and analytics access | No | Direct access to Cadency's managed application database was not confirmed. Reporting or analytics exports may be available but require verification. | Martini should use supported APIs, exports, or file mechanisms rather than connecting directly to the Cadency database. |
How Trintech Cadency exposes data and business events
Trintech Cadency REST APIs
Trintech provides enterprise integration options for Cadency, but a publicly verifiable Cadency REST API specification and endpoint catalog were not confirmed. Resource names, permissions, pagination, and write behavior must be obtained for the target tenant.
Martini implementation pattern
Martini implementation pattern: when Trintech supplies a REST specification, Martini consumes the documented endpoints, stores tenant credentials as environment secrets, retrieves or submits Cadency objects, maps them to canonical finance models, and applies validation, idempotency, and error handling.
Implementation sequence
Cadency file and batch exchange
Cadency handles accounting support and close-process information, and customer-specific integrations may use imports, exports, scheduled files, managed file transfer, or vendor-provided integration services. Formats and processing status must be confirmed.
Martini implementation pattern
Martini implementation pattern: a scheduled workflow obtains an approved export or source file, validates its structure, transforms account and period values, submits or stages the target file through the approved exchange mechanism, and records batch outcomes.
Implementation sequence
Cadency webhook or callback notifications
Public documentation does not confirm general Cadency webhooks or outbound callbacks. If the tenant provides notifications for selected events, coverage must be verified for each object and state transition.
Martini implementation pattern
Martini implementation pattern: Martini exposes a secured API endpoint for the confirmed callback, validates the notification, prevents duplicate processing, retrieves current data when a supported read interface exists, and starts the appropriate workflow.
Implementation sequence
Cadency scheduled synchronization
Scheduled synchronization is a practical fallback when API, event, or callback coverage is incomplete. A watermark, export batch identifier, or modified timestamp should be used only when the Cadency interface documents it.
Martini implementation pattern
Martini implementation pattern: Martini starts a periodic workflow, retrieves the next page or export window, applies an overlap period to reduce missed updates, transforms records, and persists the checkpoint only after successful processing.
Implementation sequence
Common Trintech Cadency integration patterns
Pattern 1: Load ERP balances into Cadency reconciliations
When to use this pattern
Use this pattern when an ERP is the system of record for ledger balances and Cadency is used for account reconciliation and close activities. The exact Cadency API, import, or file channel must be confirmed before implementation.
Integration direction
Example Mapping
| Trintech Cadency Field | Canonical Field | Target Field |
|---|---|---|
| Company code | legalEntityCode | Cadency company or legal entity |
| G/L account | accountCode | Cadency account |
| Fiscal period | accountingPeriod | Cadency period |
| Balance amount | endingBalance | Cadency reconciliation balance |
Martini implementation pattern
A scheduled Martini workflow retrieves balances from the ERP, normalizes company, account, currency, and period values, validates period status and required identifiers, and submits or stages the data through the confirmed Cadency mechanism. Failed rows are separated from accepted records and retried only when safe.
Martini capabilities used
- workflows
- scheduling
- API consumption
- file processing
- data mapping
- business rules
- error handling
Pattern 2: Publish Cadency close status to reporting
When to use this pattern
Use this pattern when finance, operations, or leadership teams need normalized close-task, reconciliation, exception, or certification status outside Cadency. The Cadency read interface must be verified.
Integration direction
Example Mapping
| Trintech Cadency Field | Canonical Field | Target Field |
|---|---|---|
| Close task status | processStatus | reporting status |
| Due date | dueAt | reporting due timestamp |
| Assignee | owner | reporting owner |
| Reconciliation certification status | certificationStatus | close metric |
Martini implementation pattern
Martini periodically retrieves or processes an approved Cadency export, converts tenant-specific statuses into a canonical model, calculates overdue indicators using normalized time zones, and publishes the result through an API or downstream exchange. Watermarks and correlation IDs support repeatable processing.
Martini capabilities used
- scheduled workflows
- API consumption
- data mapping
- business rules
- API exposure
- monitoring
Pattern 3: Orchestrate approved journal entries
When to use this pattern
Use this pattern when a source application submits approved journal entries that must be validated and routed to Cadency, an ERP, or both. Financial writes require deterministic duplicate handling and confirmation of the target interface.
Integration direction
Example Mapping
| Trintech Cadency Field | Canonical Field | Target Field |
|---|---|---|
| Source journal ID | sourceJournalId | Cadency journal reference |
| Accounting period | accountingPeriod | Cadency period |
| Debit and credit lines | journalLines | Cadency journal lines |
| Approval state | approvalStatus | Cadency approval status |
Martini implementation pattern
A Martini API receives approved journal data, validates balancing, period status, currency precision, required references, and approval state, then transforms and routes the payload through the confirmed Cadency API or file process. Idempotency keys prevent duplicate writes, while uncertain transport outcomes are reconciled before retry.
Martini capabilities used
- API exposure
- workflows
- validation
- data mapping
- business rules
- idempotency
- error handling
Pattern 4: Synchronize transaction-matching exceptions
When to use this pattern
Use this pattern when unmatched transactions or reconciliation exceptions need operational follow-up in another application and resolution references may need to return to Cadency. It depends on confirmed Cadency read and write or export interfaces.
Integration direction
Example Mapping
| Trintech Cadency Field | Canonical Field | Target Field |
|---|---|---|
| Transaction match ID | exceptionId | ServiceNow correlation key |
| Exception status | exceptionStatus | ServiceNow state |
| Exception amount | amount | ServiceNow financial impact |
| Resolution reference | resolutionReference | Cadency resolution reference |
Martini implementation pattern
Martini retrieves or imports unmatched transaction exceptions, normalizes status and financial context, creates or updates ServiceNow work items, and applies duplicate detection using the Cadency exception identifier. Resolution updates are sent back only through a documented Cadency mechanism, with failed records routed for review.
Martini capabilities used
- workflows
- API consumption
- data mapping
- business rules
- duplicate detection
- error handling
Applications commonly integrated with Trintech Cadency
Cadency typically participates in an enterprise finance and control architecture. The applications below are practical integration targets based on their role in accounting, close, ERP, and operational exception management; the exact Cadency interface and supported object set should be confirmed for the customer tenant.
| Application | Scenario | Direction | Martini Pattern |
|---|---|---|---|
| SAP S/4HANA | Exchange general-ledger balances, journal entries, company codes, currencies, and accounting periods for reconciliation and close processes. | SAP S/4HANA → Martini → Trintech Cadency | Martini retrieves or receives approved SAP finance data, normalizes account and period values, validates balancing and required identifiers, and sends the result to Cadency through its confirmed API or file channel. Processing identifiers and failures are retained for reconciliation. |
| SAP ECC | Support close and reconciliation processes for organizations using SAP's earlier ERP platform. | SAP ECC → Martini → Trintech Cadency | A scheduled Martini workflow consumes an approved SAP export or endpoint, maps company, ledger, account, currency, and period fields, and stages the result through the Cadency integration mechanism confirmed by Trintech. |
| Oracle Fusion Cloud ERP | Synchronize ledger balances, journals, account structures, and close-related information between Oracle Financials and Cadency. | Oracle Fusion Cloud ERP → Martini → Trintech Cadency | Martini orchestrates retrieval of Oracle financial data, applies tenant-specific reference mappings and validation, and submits or exports Cadency-compatible data while routing rejected records separately. |
| Oracle E-Business Suite | Exchange accounting balances, journal data, and account-master information with Cadency. | Oracle E-Business Suite → Martini → Trintech Cadency | Martini consumes an approved Oracle API or file export, transforms legacy accounting structures into the Cadency exchange model, and records batch, source, and target identifiers for auditability. |
| NetSuite | Provide reconciliation inputs and financial data from NetSuite to Cadency, with selected status or journal flows in the reverse direction where supported. | NetSuite → Martini → Trintech Cadency | A scheduled workflow retrieves NetSuite balances or exports, maps subsidiaries, accounts, periods, currencies, and amounts, validates the data, and sends it to the Cadency-approved interface. Reverse updates are enabled only for confirmed objects. |
| Microsoft Dynamics 365 Finance | Synchronize ledger, journal, and period-close information for organizations using Microsoft's finance platform. | Microsoft Dynamics 365 Finance → Martini → Trintech Cadency | Martini coordinates API or file exchanges, applies accounting-period and balancing rules, transforms reference values, and manages retries without blindly repeating financial writes. |
| Workday | Exchange accounting or financial-management data where Workday participates in the organization's finance landscape. | Workday → Martini → Trintech Cadency | Martini retrieves approved Workday outputs, converts them into the tenant's Cadency import or API structure, validates company and period context, and preserves source identifiers for traceability. |
| ServiceNow | Create operational follow-up work for close exceptions or control issues and return selected resolution status. | Trintech Cadency → Martini → ServiceNow | Martini retrieves confirmed Cadency exception or control data, maps it to ServiceNow work items, applies duplicate detection using source identifiers, and optionally sends resolution updates back through a supported Cadency channel. |
How to build a Trintech Cadency integration in Martini
Objective
Confirm the Cadency tenant's actual integration channel, authentication model, permissions, endpoint or file details, and sandbox availability before designing the workflow.
Instructions in Martini
- Obtain tenant-specific Cadency API, callback, file, or integration-service documentation
- Confirm roles, scopes, IP restrictions, credential rotation, and environment differences
- Store credentials in Martini environment-specific secrets
- Avoid direct database access unless explicitly supported
Objective
Select a schedule, approved inbound API request, file arrival process, or confirmed Cadency callback based on the capabilities available in the tenant.
Instructions in Martini
- Use a scheduler for periodic exports or incremental synchronization
- Use an API trigger for source-system submissions
- Use a callback endpoint only for confirmed Cadency events
- Define the watermark, batch identifier, or overlap strategy
Objective
Acquire Cadency or source-system data while preserving source identifiers, batch metadata, timestamps, and the original processing context.
Instructions in Martini
- Retrieve pages or approved export files
- Validate file structure and batch metadata
- Preserve source object identifiers and timestamps
- Separate transport failures from business validation failures
Objective
Coordinate the end-to-end exchange in a Martini workflow so that retrieval, transformation, validation, target writes, and outcome handling remain maintainable.
Instructions in Martini
- Call the confirmed endpoint or process the approved file channel
- Use reusable workflow logic for common finance operations
- Route accepted, rejected, pending, and uncertain outcomes separately
- Apply controlled concurrency and retry limits
Objective
Convert Cadency functional objects and enterprise finance data into a canonical model while enforcing accounting and close-process rules.
Instructions in Martini
- Map companies, accounts, ledgers, currencies, and periods
- Validate required identifiers and configured reference values
- Check journal balancing, approval state, precision, and duplicate keys
- Normalize timestamps and preserve tenant-local context where needed
Objective
Deliver validated data to Cadency or downstream applications through their confirmed integration mechanisms and capture the resulting identifiers.
Instructions in Martini
- Submit or stage the approved API payload or file
- Write reporting, ERP, or ServiceNow results where required
- Store request, response, batch, and correlation identifiers
- Do not blindly retry uncertain financial writes
Common Trintech Cadency data objects used in integrations
| Object | Typical Use | Common target systems | Martini handling |
|---|---|---|---|
| Account reconciliations | Exchange balance-sheet reconciliation work, status, preparer, reviewer, balances, certifications, and supporting information. | SAP S/4HANA, Oracle Fusion Cloud ERP, Microsoft Dynamics 365 Finance, reporting platforms | Martini maps account, company, currency, period, balance, and status values, validates required fields, and synchronizes through a confirmed API or file channel. |
| Close tasks | Manage period-end activities, dependencies, assignees, due dates, and completion status. | Enterprise reporting platforms, ServiceNow, finance systems | Martini retrieves or imports task status, normalizes due dates and time zones, applies overdue or completion rules, and routes exceptions to downstream workflows. |
| Journal entries | Prepare, approve, post, and retain supporting information for accounting entries. | SAP S/4HANA, Oracle Fusion Cloud ERP, NetSuite, Microsoft Dynamics 365 Finance | Martini validates approval state, balancing, period, currency, and duplicate keys before routing entries through a confirmed Cadency endpoint or file process. |
| Transaction matches | Represent matching results and exceptions associated with transaction-matching processes. | Operational platforms, ERP systems, ServiceNow | Martini normalizes matched and unmatched results, creates or updates exception work items, and preserves source and correlation identifiers. |
| Compliance controls | Manage controls, evidence, certifications, ownership, and review activity associated with financial controls. | ServiceNow, reporting platforms, governance systems | Martini maps control status and evidence references, applies routing rules, and synchronizes approved status data without assuming a direct database connection. |
| Intercompany transactions | Coordinate intercompany balances, transactions, confirmations, and exception management. | SAP S/4HANA, Oracle Fusion Cloud ERP, Microsoft Dynamics 365 Finance | Martini validates legal entities, currencies, periods, and transaction identifiers, then orchestrates approved imports, exports, or API calls with controlled retries. |
Authentication and security considerations
Confirm the Cadency security model first
Public Cadency-specific authentication documentation was not located. Confirm whether the tenant uses OAuth 2.0, API keys, Basic Authentication, mutual TLS, tenant-issued tokens, or a Trintech-managed integration service, together with scopes, roles, IP restrictions, and credential lifecycle requirements.
Protect integration credentials
- Store credentials in Martini environment-specific secrets.
- Use separate credentials and permissions for development, testing, and production.
- Confirm whether credentials are provisioned per user, integration account, tenant, or application.
- Do not log tokens, passwords, or unnecessary financial data.
Operational considerations for Trintech Cadency integrations
Tenant-specific behavior
Cadency capabilities may vary by edition, enabled modules, regional deployment, contract, and integration package. Confirm endpoint catalogs, file formats, object coverage, sandbox access, pagination, quotas, and processing-status behavior.
Financial data controls
- Validate accounts, companies, currencies, periods, approvals, supporting documentation, and journal balancing before writes.
- Use deterministic identifiers and idempotency checks to prevent duplicate financial submissions.
- Separate transient transport failures from business validation failures.
- Use controlled concurrency, exponential backoff, retry limits, and exception routing after confirming Cadency throttling behavior.
- Preserve correlation IDs, source and target identifiers, timestamps, statuses, and permitted payload references for auditability.
Schema and synchronization changes
Treat account structures, legal entities, close templates, reconciliation types, approval workflows, custom fields, and fiscal calendars as configurable. Version mappings, test period and time-zone handling, and use a persisted watermark or batch checkpoint only when the Cadency interface documents the relevant field.
Why use Martini instead of scripts or point-to-point integrations?
Orchestrate more than a single exchange
Cadency integrations commonly involve ERP balances, journal controls, reconciliation status, close tasks, exceptions, and reporting. Martini provides a workflow layer for retrieving or receiving data, applying business rules, transforming models, writing targets, and handling uncertain outcomes.
Reduce point-to-point coupling
Martini can expose normalized APIs and reusable workflows so downstream applications do not each implement Cadency-specific mappings, authentication, pagination, file handling, and error rules.
Improve maintainability and control
- Keep environment-specific secrets outside workflows and mappings.
- Version mappings and configurable reference values.
- Use validation, idempotency, retry, and exception paths consistently.
- Retain correlation and processing information for operational review.
- Adapt the implementation when Trintech confirms tenant-specific capabilities without redesigning every connected application.
Frequently asked questions
Cadency can participate in enterprise integrations through tenant-specific APIs, scheduled imports and exports, managed file exchange, Trintech-provided integration services, and possibly selected callbacks. Public research did not confirm a general Cadency REST, GraphQL, SOAP, webhook, or bulk API specification, so the supported channel, objects, formats, and authentication model must be verified for the customer deployment.
Yes. Martini can integrate with Cadency using the tenant's confirmed APIs, callbacks, file interfaces, managed file-transfer mechanisms, or Trintech-provided integration endpoints. Martini can orchestrate workflows, transform finance data, apply validation and business rules, expose normalized APIs, and handle errors without assuming direct database access.
No. A dedicated Trintech Cadency connector is not required. Martini can use Cadency's confirmed native integration mechanisms, such as APIs, supported callbacks, imports, exports, files, or vendor-managed integration services. A native Martini Cadency connector was not documented in the supplied materials.
Lonti does not charge an additional per-connector or per-vendor fee to integrate Trintech Cadency. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from Trintech, infrastructure providers, managed file-transfer services, or other third-party systems depending on subscriptions, usage, and deployment model.
Use the current, tenant-documented API or integration service when available. If API coverage is unavailable or incomplete, scheduled imports, exports, managed file exchange, or vendor-provided integration services may be appropriate. REST, GraphQL, SOAP, bulk APIs, and general webhooks should not be assumed without documentation for the target deployment.
Public research did not confirm general Cadency webhooks or outbound callbacks. A deployment may support notifications for selected processes or state changes, but event coverage and authentication must be verified for each required object. If supported, Martini can receive the notification through an API endpoint and start a workflow.
Martini can use a documented modified timestamp, export watermark, event sequence, or batch identifier. It can schedule incremental workflows, paginate or process files, use a small overlap window, and persist checkpoints after successful processing. The chosen method depends on what the Cadency tenant exposes.
Martini maps Cadency functional objects to canonical and target models, validates accounts, companies, periods, currencies, approvals, and balancing rules, and routes failures separately from successful records. Stable journal, reconciliation, task, transaction-match, or batch identifiers can support idempotency. Financial writes should not be retried blindly when the original outcome is uncertain.
Related Martini documentation
Workflows
Data
Plan your Trintech Cadency integration
Confirm the Cadency tenant's APIs, files, callbacks, authentication, and object coverage, then use Martini to implement a governed workflow for finance data synchronization, validation, and operational monitoring.