What's new?​

One or more owners can optionally be assigned to a companyCompany In Codat, a company represents your customer's business entity. Companies can have multiple connections to different data sources. when creating or editing it in the Portal.

We've also introduced a new companyCompany In Codat, a company represents your customer's business entity. Companies can have multiple connections to different data sources. permissions setting. When enabled for your organization, users with the Onboarding, Advisor, or Analyst role can only access companies they've been assigned to as an owner. Administrator and Developer users retain access to all companies.

Who is it relevant for?​

Clients who want to establish clear ownership of their companies, or need to control which of their users can access which companies' data - for example, banks that need to restrict client data visibility internally.

How to get started?​

Owner assignment is available to all clients today - simply assign owners when creating or editing a companyCompany In Codat, a company represents your customer's business entity. Companies can have multiple connections to different data sources. in the Portal.

To enable the companyCompany In Codat, a company represents your customer's business entity. Companies can have multiple connections to different data sources. permissions setting for your organization, contact your account manager or our support team.

What's changing​

The Shopify integration historically supported two ways for a merchant to connect their store:

• Custom apps — the merchant creates a custom app in their Shopify admin and provides the store name, client ID, and client secret during the Codat LinkLink The authorization flow that allows end users to connect their accounting, banking, or commerce platforms to your application via Codat. flow. This is the standard method.
• Public apps — the client builds a public Shopify app, submits it to Shopify for approval, hosts an authorization endpoint, and configures the app's credentials in Codat.

The public apps method is being deprecated and removed. It places a significant setup burden on clients, who must create and submit a public Shopify app for Shopify's review and approval, and develop and host an endpoint to authorize each merchant. Custom apps remove these requirements, so we are standardizing on the simpler custom apps approach for all Shopify connectionsConnection A link between a Codat company and a data source (like an accounting platform). Each connection represents authorized access to pull or push data from that platform..

Alternatives​

Use the custom apps connection method for all Shopify connectionsConnection A link between a Codat company and a data source (like an accounting platform). Each connection represents authorized access to pull or push data from that platform.. Compared with public apps, custom apps:

• Don't require you to build and submit your own public Shopify app.
• Don't require you to build and host a merchant authorization endpoint.
• Guide the merchant through creating the app and entering their credentials with an in-flow, step-by-step Find your Shopify credentials section.

Action required​

For the vast majority of clients, no action is required — Shopify connectionsConnection A link between a Codat company and a data source (like an accounting platform). Each connection represents authorized access to pull or push data from that platform. already use custom apps.

If you currently rely on the public apps connectionConnection A link between a Codat company and a data source (like an accounting platform). Each connection represents authorized access to pull or push data from that platform. method, switch to custom apps before connecting any new merchants.

If you have questions or need assistance, reach out to your dedicated Codat representative or contact our support team.

Expected impact if no action is taken​

The public apps connectionConnection A link between a Codat company and a data source (like an accounting platform). Each connection represents authorized access to pull or push data from that platform. method will stop working, and merchants will no longer be able to start new connectionsConnection A link between a Codat company and a data source (like an accounting platform). Each connection represents authorized access to pull or push data from that platform. through it. Existing, already-linked Shopify connectionsConnection A link between a Codat company and a data source (like an accounting platform). Each connection represents authorized access to pull or push data from that platform. are unaffected and continue to syncSync The process of fetching the latest data from a connected data source. Syncs can be triggered manually or run automatically on a schedule.. Any client still onboarding merchants through public apps must move to custom apps to continue connecting new stores.

Codat now supports a single, global companyCompany In Codat, a company represents your customer's business entity. Companies can have multiple connections to different data sources. access token that provides seamless access across multiple products. To improve efficiency and consistency, we are deprecating the older connectionConnection A link between a Codat company and a data source (like an accounting platform). Each connection represents authorized access to pull or push data from that platform.-management-specific endpoint in favour of this global token.

The following endpoint will be deprecated:

GET /companies/{companyId}/connectionManagement/accessToken

Action required​

If you are using the endpoint above, you will need to instead use the global companyCompany In Codat, a company represents your customer's business entity. Companies can have multiple connections to different data sources. access token endpoint:

GET /companies/{companyId}/accessToken

The access token is returned in the same accessToken field, so if you read that field you can switch to the new endpoint with no further changes. The replacement response additionally includes expiresIn (seconds until the token expires) and tokenType (for example, Bearer). Update your integration to call the new endpoint ahead of the deprecation date.

Expected impact if no action is taken​

After 2026-10-12, calls to the deprecated endpoint will return a 404 error.

{
  "statusCode": 404,
  "service": "PublicApi",
  "error": "NotFound",
  "correlationId": "2b60a2bafedd3238702c2186a2dc833f",
  "canBeRetried": "Unknown",
  "detailedErrorCode": 0
}

What's new?​

Today it's possible to create a duplicate mapping where the target Xero bank account is already connected to a different companyCompany In Codat, a company represents your customer's business entity. Companies can have multiple connections to different data sources. using the same Xero application. When that happens, multiple source accounts across different companies point to the same Xero bank feed, making it unclear which is the true source of data.

This update introduces two improvements:

• Validation: when a target Xero bank account is already connected under a different companyCompany In Codat, a company represents your customer's business entity. Companies can have multiple connections to different data sources., the mapping request now returns a clear 400 error with a suggested resolution, instead of silently creating a duplicate.
• Filtered options: target Xero bank accounts already connected to a bank feed under any companyCompany In Codat, a company represents your customer's business entity. Companies can have multiple connections to different data sources. using the same Xero app are excluded from the available mapping options.

If a source account is already mapped to a Xero target account, attempting to create the same mapping again still succeeds without errors. That behaviour is unchanged. Existing mappings are not modified.

When does this take effect?​

This update takes effect on 24 June 2026.

Xero APIAPI A set of rules and protocols that allows different software applications to communicate with each other. Codat provides APIs for accessing financial data from accounting, banking, and commerce platforms. limitation​

Xero's APIAPI A set of rules and protocols that allows different software applications to communicate with each other. Codat provides APIs for accessing financial data from accounting, banking, and commerce platforms. only shows feed connectionsConnection A link between a Codat company and a data source (like an accounting platform). Each connection represents authorized access to pull or push data from that platform. that share the same OAuth application. If a target account is already connected through a different Xero OAuth application, it still appears as available. The mapping attempt then fails with an error explaining that the account is already in use.

Who is this relevant for?​

This change is relevant for Xero bank feedsBank Feeds A Codat product that enables automatic synchronization of bank transaction data into a company's accounting software. clients whose setup meets all of the following:

1. Multiple companies share the same Xero OAuth application.
2. Those companies connect to the same Xero organization.
3. A user tries to map a source account to a Xero target account already used by a different companyCompany In Codat, a company represents your customer's business entity. Companies can have multiple connections to different data sources..

How to get started?​

No changes to your integration are required. Once the update is live, you will see:

• Target accounts already connected under another companyCompany In Codat, a company represents your customer's business entity. Companies can have multiple connections to different data sources. using the same Xero application no longer appear in the available mapping options.
• Target accounts connected through a different Xero application still appear, but attempts to map them return an error.

Remapping a Xero bank account​

If a customer needs to remap a Xero bank account:

1. Remove the existing bank feed connectionConnection A link between a Codat company and a data source (like an accounting platform). Each connection represents authorized access to pull or push data from that platform. that uses the account. This makes the target account available again.
2. Create a new mapping to the required companyCompany In Codat, a company represents your customer's business entity. Companies can have multiple connections to different data sources..

Contact Codat Support or your Account Manager if you'd like help with this change.

What's new?​

A new View timeline button on the Manage ConnectionsConnection A link between a Codat company and a data source (like an accounting platform). Each connection represents authorized access to pull or push data from that platform. page in the Codat Portal opens a right-anchored drawer with a per-connectionConnection A link between a Codat company and a data source (like an accounting platform). Each connection represents authorized access to pull or push data from that platform. diagnostic history. Until now, status pills told you the current state of a connectionConnection A link between a Codat company and a data source (like an accounting platform). Each connection represents authorized access to pull or push data from that platform. but not how it got there. The timeline closes that gap.

Chronological view of every status change​

The drawer renders a vertical timeline of status transitions for the selected connectionConnection A link between a Codat company and a data source (like an accounting platform). Each connection represents authorized access to pull or push data from that platform., oldest at the top and newest at the bottom. Each step shows the status, the date and time of the transition, and the reason where one is available for Deauthorized and Unlinked events.

Steps map onto the connectionConnection A link between a Codat company and a data source (like an accounting platform). Each connection represents authorized access to pull or push data from that platform. statuses you already see on the table:

• Started: when the linkLink The authorization flow that allows end users to connect their accounting, banking, or commerce platforms to your application via Codat. flow began
• Completed: when the connectionConnection A link between a Codat company and a data source (like an accounting platform). Each connection represents authorized access to pull or push data from that platform. became authorized and started syncing data
• Deauthorized: when access was revoked or expired
• Unlinked: when the connectionConnection A link between a Codat company and a data source (like an accounting platform). Each connection represents authorized access to pull or push data from that platform. was manually unlinked

Switch between a companyCompany In Codat, a company represents your customer's business entity. Companies can have multiple connections to different data sources.'s connectionsConnection A link between a Codat company and a data source (like an accounting platform). Each connection represents authorized access to pull or push data from that platform. without leaving the drawer​

A connectionConnection A link between a Codat company and a data source (like an accounting platform). Each connection represents authorized access to pull or push data from that platform. picker at the top of the drawer lists every connectionConnection A link between a Codat company and a data source (like an accounting platform). Each connection represents authorized access to pull or push data from that platform. on the companyCompany In Codat, a company represents your customer's business entity. Companies can have multiple connections to different data sources.. Selecting another platform replaces the timeline and status summary in place, so you don't need to close the drawer and reopen it from another row.

Current status and last syncSync The process of fetching the latest data from a connected data source. Syncs can be triggered manually or run automatically on a schedule., at a glance​

Above the timeline, the drawer surfaces the connectionConnection A link between a Codat company and a data source (like an accounting platform). Each connection represents authorized access to pull or push data from that platform.'s current status as a colored pill and the last successful syncSync The process of fetching the latest data from a connected data source. Syncs can be triggered manually or run automatically on a schedule. timestamp in your locale. These values come straight from the connectionConnection A link between a Codat company and a data source (like an accounting platform). Each connection represents authorized access to pull or push data from that platform. record, so they are always present even when the underlying transition history is not.

Older connectionsConnection A link between a Codat company and a data source (like an accounting platform). Each connection represents authorized access to pull or push data from that platform. fill in over time​

ConnectionConnection A link between a Codat company and a data source (like an accounting platform). Each connection represents authorized access to pull or push data from that platform. transitions are only recorded from the release of this feature forward, and there is no historical backfill. ConnectionsConnection A link between a Codat company and a data source (like an accounting platform). Each connection represents authorized access to pull or push data from that platform. that have not transitioned since the recording started show a "Timeline not available" banner alongside the current status and creation date. As soon as those connectionsConnection A link between a Codat company and a data source (like an accounting platform). Each connection represents authorized access to pull or push data from that platform. next change state (a relink, a deauthorization, an unlink), the timeline starts populating itself, so coverage self-heals over time.

Who is this relevant for?​

This update is most useful for bankers, implementation managers, and support engineers who need to answer "what's going on with this connectionConnection A link between a Codat company and a data source (like an accounting platform). Each connection represents authorized access to pull or push data from that platform.?", whether that's a client reporting data isn't flowing, a status pill showing Deauthorized, or an onboarding that has stalled. It also benefits any Portal user who wants a clear audit trail of how a connectionConnection A link between a Codat company and a data source (like an accounting platform). Each connection represents authorized access to pull or push data from that platform. has changed over time.

How to get started?​

No action is required to benefit from this update. Open the Companies page in the Codat Portal, pick a companyCompany In Codat, a company represents your customer's business entity. Companies can have multiple connections to different data sources., and click View timeline on any connectionConnection A link between a Codat company and a data source (like an accounting platform). Each connection represents authorized access to pull or push data from that platform. in the Manage ConnectionsConnection A link between a Codat company and a data source (like an accounting platform). Each connection represents authorized access to pull or push data from that platform. view to see its history.

What's new?​

On May 22, 2026, we are shipping a first-class Canadian French experience across LinkLink The authorization flow that allows end users to connect their accounting, banking, or commerce platforms to your application via Codat., the Codat Portal, Spend Reports, and payment method inference. This enables our clients operating in Canada to serve French-speaking Quebec commercial businesses in line with the Charter of the French Language (Bill 96), and lays the groundwork for any future language we ship.

What's included​

This release covers surfaces across LinkLink The authorization flow that allows end users to connect their accounting, banking, or commerce platforms to your application via Codat., Portal, Spend Reports and Help Hub. Canadian French is gated by a language toggle and the client's LinkLink The authorization flow that allows end users to connect their accounting, banking, or commerce platforms to your application via Codat. configuration — existing English-only deployments see no change.

LinkLink The authorization flow that allows end users to connect their accounting, banking, or commerce platforms to your application via Codat. journey​

Full Canadian French translation of the commercial business-facing connect flow, including:

• Platform selection
• OAuth handoff copy
• Error states
• In-modal language toggle (top-right, globe icon and locale code)

Supported integrations in this release:

• QuickBooks Online
• QuickBooks Desktop
• NetSuite
• Sage Intacct
• Dynamics 365 Business Central
• Dynamics 365 Finance & Operations
• Workday
• FreshBooks
• Xero
• All intelligent upload flows

Portal UI​

The Spend Insights, Companies, and Create CompanyCompany In Codat, a company represents your customer's business entity. Companies can have multiple connections to different data sources. surfaces are translated end-to-end, with locale-aware date and number formatting.

Spend Reports​

Spend Reports are localized — field names, labels, section headers, and static copy all render in Canadian French when the report is generated for a French locale client. The underlying data remains language-independent, and CSV exports stay locale-neutral for downstream pipelines.

Payment method inference​

Payment method mapping inference now handles Canadian French source data, so ERP exports with French account names, categories, and descriptions map correctly into Codat's canonical schema without manual cleanup.

Why it matters​

• Compliance, not just translation. Bill 96 requires that French experiences be available with comparable quality to English across customer-facing digital products. This release meets the customer-facing bar.
• Ready for Canadian FIs. Any client with Quebec operations now has a Canadian French-ready stack to launch against — no per-client translation effort.

Who is this relevant for?​

This update is relevant for any client operating in Canada, and especially for financial institutions onboarding commercial businesses in Quebec who need to meet Bill 96 requirements.

How to get started?​

Canadian French is opt-in per client at the configuration level. To enable it for your deployment, contact Codat support. We'll work with you to align on the pages and integrations in scope before enabling.

What's new?​

We have shipped a set of updates to the Companies table in the Codat Portal.

Platforms column​

A dedicated Platforms column now sits between the ConnectionConnection A link between a Codat company and a data source (like an accounting platform). Each connection represents authorized access to pull or push data from that platform. and Created columns on the Companies table, restoring the at-a-glance view of which integrations each companyCompany In Codat, a company represents your customer's business entity. Companies can have multiple connections to different data sources. has connected.

• Pill colours reflect the connectionConnection A link between a Codat company and a data source (like an accounting platform). Each connection represents authorized access to pull or push data from that platform. state for each platform: green for linked, amber for deauthorized, grey for unlinked, and neutral for pending authorization.
• When a companyCompany In Codat, a company represents your customer's business entity. Companies can have multiple connections to different data sources. has more platforms than fit in the column, a +N chip indicates how many additional integrations are connected.
• Hovering the cell opens a tooltip with the connectionConnection A link between a Codat company and a data source (like an accounting platform). Each connection represents authorized access to pull or push data from that platform. status, the full list of platforms with status indicators, and — for parent rows with subsidiaries — an X/Y companies counter showing how many subsidiaries are connected.
• Searching by a platform name in the table search input filters the rows, with matches highlighted in the pills.

ConnectionConnection A link between a Codat company and a data source (like an accounting platform). Each connection represents authorized access to pull or push data from that platform. details in one click​

Platform pills, the +N chip, and the connectionConnection A link between a Codat company and a data source (like an accounting platform). Each connection represents authorized access to pull or push data from that platform. status are now clickable. Selecting any of them opens a connectionsConnection A link between a Codat company and a data source (like an accounting platform). Each connection represents authorized access to pull or push data from that platform. panel for that companyCompany In Codat, a company represents your customer's business entity. Companies can have multiple connections to different data sources. — without leaving the table.

• Every connectionConnection A link between a Codat company and a data source (like an accounting platform). Each connection represents authorized access to pull or push data from that platform. for the companyCompany In Codat, a company represents your customer's business entity. Companies can have multiple connections to different data sources. is listed with its logo, platform name, connectionConnection A link between a Codat company and a data source (like an accounting platform). Each connection represents authorized access to pull or push data from that platform. ID, source type, and live status pill.
• When one or more connectionsConnection A link between a Codat company and a data source (like an accounting platform). Each connection represents authorized access to pull or push data from that platform. have errors, an info-style alert appears above the list showing a count of affected connectionsConnection A link between a Codat company and a data source (like an accounting platform). Each connection represents authorized access to pull or push data from that platform. and a quick linkLink The authorization flow that allows end users to connect their accounting, banking, or commerce platforms to your application via Codat. to manage them.
• A Manage connectionsConnection A link between a Codat company and a data source (like an accounting platform). Each connection represents authorized access to pull or push data from that platform. button takes you straight to that companyCompany In Codat, a company represents your customer's business entity. Companies can have multiple connections to different data sources.'s connectionsConnection A link between a Codat company and a data source (like an accounting platform). Each connection represents authorized access to pull or push data from that platform. page when you want to dig in further.

Customizable columns​

A new Columns dropdown lets you choose which columns appear on the Companies table, with your selection remembered the next time you open the page.

• Columns are split into two groups: Default (Created date, Last data syncSync The process of fetching the latest data from a connected data source. Syncs can be triggered manually or run automatically on a schedule., Platforms) and Additional (Products).
• A header checkbox toggles all optional columns at once, and a Default view footer button resets your selection back to the defaults.
• The dropdown trigger summarizes the current state — Default, All, or N/total — so you can see at a glance how your view is configured.
• The same dropdown appears on the Subsidiaries page, with your selection shared between the two views so your preference follows you.
• CompanyCompany In Codat, a company represents your customer's business entity. Companies can have multiple connections to different data sources. name and ConnectionConnection A link between a Codat company and a data source (like an accounting platform). Each connection represents authorized access to pull or push data from that platform. status stay locked on and are not listed in the dropdown.

Last data syncSync The process of fetching the latest data from a connected data source. Syncs can be triggered manually or run automatically on a schedule. column rename​

The previous Last Updated column has been renamed to Last data syncSync The process of fetching the latest data from a connected data source. Syncs can be triggered manually or run automatically on a schedule. to more accurately describe the value: the timestamp of the most recent successful data exchange across all of a companyCompany In Codat, a company represents your customer's business entity. Companies can have multiple connections to different data sources.'s connectionsConnection A link between a Codat company and a data source (like an accounting platform). Each connection represents authorized access to pull or push data from that platform..

• Companies with no successful syncSync The process of fetching the latest data from a connected data source. Syncs can be triggered manually or run automatically on a schedule. render an em dash (—) and sort to the bottom of the list in both directions.
• Date values render in your selected locale (English or Canadian French).

Who is this relevant for?​

These updates benefit all customers who use the Codat Portal to manage their companies, and are especially useful for implementation, support, and customer-facing teams who need to quickly identify which systems each companyCompany In Codat, a company represents your customer's business entity. Companies can have multiple connections to different data sources. is connected to, customize their view, and triage connectionConnection A link between a Codat company and a data source (like an accounting platform). Each connection represents authorized access to pull or push data from that platform. issues.

How to get started?​

No action is required to benefit from these updates. Open the Companies or Subsidiaries page in the Codat Portal to start using the improvements today.

What's new?​

On May 6, 2026, we are updating the Codat Portal so that the search input is always visible on the Companies and Subsidiaries pages, instead of being hidden behind a search icon. Search now lives in a dedicated table toolbar directly above the table, alongside the connectionConnection A link between a Codat company and a data source (like an accounting platform). Each connection represents authorized access to pull or push data from that platform. status filter.

We are introducing the following improvements:

• The search input is always visible in a new table toolbar on the Companies and Subsidiaries pages — no more clicking a search icon to reveal it.
• The toolbar groups search and the connectionConnection A link between a Codat company and a data source (like an accounting platform). Each connection represents authorized access to pull or push data from that platform.-status filter together below the page header, while the Invite and Create actions remain in the page header.
• Focusing the empty search input opens a popover that lists exactly which fields you can search by: CompanyCompany In Codat, a company represents your customer's business entity. Companies can have multiple connections to different data sources. ID, CompanyCompany In Codat, a company represents your customer's business entity. Companies can have multiple connections to different data sources. name, ConnectionConnection A link between a Codat company and a data source (like an accounting platform). Each connection represents authorized access to pull or push data from that platform. ID, Connected platform, and User who created it.
• An updated placeholder ("Search companyCompany In Codat, a company represents your customer's business entity. Companies can have multiple connections to different data sources., platform, ID...") makes the supported search terms clearer at a glance.

These improvements apply to the Companies and Subsidiaries pages and build on the multi-entity company table we shipped earlier this year.

Who is this relevant for?​

This update benefits all customers who use the Codat Portal to manage their companies, and is especially useful for implementation, support, and customer-facing teams who frequently search across large numbers of companies and connectionsConnection A link between a Codat company and a data source (like an accounting platform). Each connection represents authorized access to pull or push data from that platform..

How to get started?​

No action is required to benefit from this update. Open the Companies or Subsidiaries page in the Codat Portal from May 6, 2026 and start typing in the search input at the top of the table.

MYOB is currently the only integration where push operations return their final status synchronously. Migrating it to async brings MYOB in line with the restREST An architectural style for designing networked applications. Codat's APIs follow REST principles, using standard HTTP methods. of our integrations and simplifies our underlying push infrastructure, so we can continue to invest in reliability across the platform.

What's changing​

Today, when you push to MYOB, the APIAPI A set of rules and protocols that allows different software applications to communicate with each other. Codat provides APIs for accessing financial data from accounting, banking, and commerce platforms. returns a final Success or Failed status immediately on the initial request.

From May 11, 2026, push requests to MYOB will return a Pending status on submission, and resolve to Success or Failed once the operation completes — the same pattern as every other integration.

The change only affects how you confirm the outcome of a push. Pushes themselves will continue to work as before.

Action required​

To track the final status of a push operation to MYOB, use one of the following:

• Push webhooksWebhook An automated notification sent from Codat to your application when specific events occur, such as when data syncs complete or connections change status. (recommended) — subscribe to the {dataType}.write.successful and {dataType}.write.unsuccessful events. See Consume the data types write webhook.
• Status endpoints — poll the Get push operation endpoint using the pushOperationKey returned in the initial response.

If you already push to other Codat integrations, you'll likely already have this in place.

Expected impact if no action is taken​

If your integration relies on receiving a final Success or Failed status directly from the initial push response, that status will instead be Pending from May 11, 2026 — and you won't be able to confirm whether the operation ultimately succeeded or failed without consuming the webhookWebhook An automated notification sent from Codat to your application when specific events occur, such as when data syncs complete or connections change status. or polling the status endpoint.

Pushes to MYOB will continue to be processed.

If you have questions or need help migrating, reach out to your Codat representative or our support team.

What's new?​

On April 30, 2026, we are adding a new Subsidiaries view to parent companies in the Codat Portal. When you open a parent companyCompany In Codat, a company represents your customer's business entity. Companies can have multiple connections to different data sources., you will see a dedicated Subsidiaries page that lists all of its child companies in one place, with the same controls you already use on the top-level Companies page.

We are introducing the following improvements:

• New Subsidiaries sidebar item is added to any companyCompany In Codat, a company represents your customer's business entity. Companies can have multiple connections to different data sources. that has subsidiaries, with a count indicator showing how many child companies it has.
• Dedicated subsidiaries table reuses the familiar Companies table, including search, sort, connectionConnection A link between a Codat company and a data source (like an accounting platform). Each connection represents authorized access to pull or push data from that platform.-status filter, and infinite scroll.
• Edit, delete, and linkLink The authorization flow that allows end users to connect their accounting, banking, or commerce platforms to your application via Codat. actions are available directly from each subsidiary row, matching the behavior on the top-level Companies page.

These improvements apply to all parent companies in the Portal and complement the hierarchical company table we shipped earlier this year.

Who is this relevant for?​

This update benefits all customers who manage multi-entity companies, and is especially useful for enterprise clients working with deep parent–child hierarchies who need to drill into a specific parent and manage its subsidiaries without losing context.

How to get started?​

No action is required to benefit from this update. Open any parent companyCompany In Codat, a company represents your customer's business entity. Companies can have multiple connections to different data sources. in the Codat Portal from April 30, 2026 and select Subsidiaries in the sidebar to view its child companies.

What's new?​

We've made it simpler to embed our SDKs in apps that enforce strict browser security policies.

Our LinkLink The authorization flow that allows end users to connect their accounting, banking, or commerce platforms to your application via Codat. SDK now accept a nonce option that it applies to every <style> tag it injects into your page. This means your app can use a strict CSP style-src directive instead of allowing unsafe-inline, which previously was required to render the SDK's styles. This option is also available in the ConnectionsConnection A link between a Codat company and a data source (like an accounting platform). Each connection represents authorized access to pull or push data from that platform. and Bank FeedsBank Feeds A Codat product that enables automatic synchronization of bank transaction data into a company's accounting software. SDKs, so a single nonce-based CSP can cover all three.

This change results in the following benefits:

• Stronger browser security: strict CSPs help protect your customers from cross-site scripting (XSS) attacks. Removing unsafe-inline is one of the most impactful changes you can make to your CSP.
• Compliance-friendly: if your security or compliance team has previously flagged unsafe-inline in your CSP, this change gives you a clean path to remove it.
• No styling trade-offs: the SDK continues to render with the same look and feel you've configured in the Portal. The nonce only changes how the browser trusts the styles, not the styles themselves.

Who is this relevant for?​

This update is for clients who embed Codat's SDKs (LinkLink The authorization flow that allows end users to connect their accounting, banking, or commerce platforms to your application via Codat., ConnectionsConnection A link between a Codat company and a data source (like an accounting platform). Each connection represents authorized access to pull or push data from that platform., or Bank FeedsBank Feeds A Codat product that enables automatic synchronization of bank transaction data into a company's accounting software.) in an app that sets a Content Security Policy, especially those working to remove unsafe-inline from their style-src directive.

How to get started?​

The nonce option is available immediately. To start using it, follow these steps:

1. Configure your server to generate a unique cryptographically random nonce for each request.
2. Expose the nonce to the browser (for example, using a <meta> tag).
3. Pass the value to the SDK through options.nonce:

   <CodatLink companyId={companyId} options={{ nonce }} />
   

4. Update your CSP header to swap style-src 'unsafe-inline' for style-src 'nonce-<value>'.

   style-src 'self' 'nonce-r4nd0mB4se64Val==' *.codat.io;
   

The full migration guide and detailed configuration steps are available in CSP nonce in our SDK documentation.

What's new?​

The Codat Portal now has a new Advisor role. Advisors can add and linkLink The authorization flow that allows end users to connect their accounting, banking, or commerce platforms to your application via Codat. companies, view companyCompany In Codat, a company represents your customer's business entity. Companies can have multiple connections to different data sources. data, and view webhookWebhook An automated notification sent from Codat to your application when specific events occur, such as when data syncs complete or connections change status. consumers, but can't delete companies or change settings. This reduces operational risk and opens up access to insights to more people in your organization.

You can review the detailed permissions breakdown in the User roles summary.

Who is this relevant for?​

This update is relevant for anyone using the Codat Portal to view and manage data. It's especially beneficial for organizations that require their users to have visibility into insights and reporting without the ability to change companyCompany In Codat, a company represents your customer's business entity. Companies can have multiple connections to different data sources. configuration.

How to get started?​

The Advisor role is already available in the Codat Portal and you can start assigning it to relevant users immediately.

If you're using Enterprise SSO, you need to set up a group corresponding to the new role in your Identity Provider (IdP) first. Get in touch if you need further guidance.

Almost a decade ago, Codat started as the reliable, behind-the-scenes infrastructure layer that financial institutions use to connect and standardize business financial data. Hundreds of thousands of data connectionsConnection A link between a Codat company and a data source (like an accounting platform). Each connection represents authorized access to pull or push data from that platform. later, we've become a strategic partner to the world’s largest financial organizations.

Our support goes beyond data connectivity and basic analytics. We give commercial bankers clear, timely, forward-looking insight that helps them anticipate client needs and act with confidence. We call this advisory intelligence.

Our new brand is a way to re-introduce Codat and its simple conviction: banks should be able to understand what their clients need before the client has to ask.

What's new​

You'll see our new brand across every part of Codat: the website, the Portal, our documentation, and the Help Hub. At the heart of it is a new logo: an incomplete circle where the final piece clicks into place, representing the role Codat plays in completing the picture between data, insight, and action.

What's not changing​

RestREST An architectural style for designing networked applications. Codat's APIs follow REST principles, using standard HTTP methods. assured, the connectionsConnection A link between a Codat company and a data source (like an accounting platform). Each connection represents authorized access to pull or push data from that platform., integrations, and APIsAPI A set of rules and protocols that allows different software applications to communicate with each other. Codat provides APIs for accessing financial data from accounting, banking, and commerce platforms. your teams rely on are unaffected. Data flows, authentication flows, and existing implementations continue to work exactly as they did yesterday. If you ever have questions about continuity or compatibility, our Support team is here for you.

Welcome to the new Codat.

As part of our newly launched brand identity, we’ve updated interfaces of the Codat Portal and the LinkLink The authorization flow that allows end users to connect their accounting, banking, or commerce platforms to your application via Codat. connectionConnection A link between a Codat company and a data source (like an accounting platform). Each connection represents authorized access to pull or push data from that platform. flow to reflect a sharper, more modern visual identity.

What's new?​

From today, both Portal and LinkLink The authorization flow that allows end users to connect their accounting, banking, or commerce platforms to your application via Codat. reflect Codat's updated visual identity, boasting a new color palette and logo. These changes are subtle, and the Codat you know and rely on is still recognizable beneath them.

Custom LinkLink The authorization flow that allows end users to connect their accounting, banking, or commerce platforms to your application via Codat. settings​

If you’ve previously configured custom branding settings for LinkLink The authorization flow that allows end users to connect their accounting, banking, or commerce platforms to your application via Codat. (for example, your own colors and logo), they will remain unchanged. Your overrides take precedence, as before. If you want to learn more about setting your own color palette, refer to Branding in Portal.

If you have the Secured by Codat setting enabled in your LinkLink The authorization flow that allows end users to connect their accounting, banking, or commerce platforms to your application via Codat. settings, the Codat logo displayed in your LinkLink The authorization flow that allows end users to connect their accounting, banking, or commerce platforms to your application via Codat. flow will automatically update to the new logo.

Who is this relevant for?​

These changes are already live for all our clients, reflecting our commitment to our new visual identity, and don’t require any action on your part. If you have any questions about the visual changes, get in touch with our Support team.

What's new?​

When a user successfully connects a bank account in LinkLink The authorization flow that allows end users to connect their accounting, banking, or commerce platforms to your application via Codat., they are now prompted to connect another. The prompt appears in two places:

1. On the connectionConnection A link between a Codat company and a data source (like an accounting platform). Each connection represents authorized access to pull or push data from that platform. success screen, users see a We recommend adding more bank accounts message with a primary Connect another account button.

   A secondary Continue button on the screen skips additional account creation. A tooltip explains why connecting additional accounts is beneficial.

   

2. On the main LinkLink The authorization flow that allows end users to connect their accounting, banking, or commerce platforms to your application via Codat. screen, the Banking step displays an Add another button tagged Recommended and provides context on the value of connecting more accounts.

   

Previously, users completed the flow after connecting a single account and didn't receive a suggestion to add more. The update aims to change this common connectionConnection A link between a Codat company and a data source (like an accounting platform). Each connection represents authorized access to pull or push data from that platform. pattern. Merchants who connect multiple accounts give their lenders a fuller picture of their cash flow, which leads to better lending decisions and improves conversion rates.

The change applies to banking integrations connected via Plaid and TrueLayer.

Who is this relevant for?​

This change is relevant to all clients using LinkLink The authorization flow that allows end users to connect their accounting, banking, or commerce platforms to your application via Codat. with banking integrations enabled. This includes the Hosted Link flow and the Link SDK solutions.

How to get started?​

No action is required. The updated flow will be available to all customers using LinkLink The authorization flow that allows end users to connect their accounting, banking, or commerce platforms to your application via Codat. with banking integrations from April 24, 2026.

This change is part of our ongoing program of security enhancements across the Codat platform. It follows similar updates already applied to QuickBooks Online and Xero.

What's changing​

From July 10, 2026, clients using our out-of-the box Authentication UI for the Sage Bank Feeds connectionConnection A link between a Codat company and a data source (like an accounting platform). Each connection represents authorized access to pull or push data from that platform. flow will need their users to complete a one-time passcode verification step when connecting.

You must update your user journey to surface the verification code during authentication.

Action required​

Clients using Sage Bank Feeds must update their application to include the new OTP generation step before July 10, 2026. See how to Surface the one-time password (OTP) to the user for implementation instructions. To test this change in your test environment, please ask Codat Support to enable the feature for you.

You may also want to update your internal and client-facing documentation in line with this change. Contact Codat Support if you’d like any additional help with this update.

Expected impact if no action is taken​

After July 10, 2026, the existing out-of-the-box Sage Bank Feeds flow will always require a valid OTP to establish the connectionConnection A link between a Codat company and a data source (like an accounting platform). Each connection represents authorized access to pull or push data from that platform..

Clients who haven’t updated their integration won’t be able to establish new Sage Bank FeedsBank Feeds A Codat product that enables automatic synchronization of bank transaction data into a company's accounting software. connectionsConnection A link between a Codat company and a data source (like an accounting platform). Each connection represents authorized access to pull or push data from that platform. until the change is made.

To focus our efforts on the SDKs where we can deliver the most value, we are deprecating the Go client SDK across all Codat products. This will allow us to concentrate our resources on improving the developer experience for our more widely adopted TypeScript, Python, and C# SDKs.

What's changing​

All Go modules published under github.com/codatio/client-sdk-go will no longer be maintained:

After May 7, 2026:

• We will stop publishing new versions of these modules.
• We won't address bugs, security updates, or compatibility issues.
• The GitHub repository will be archived (read-only).
• Existing tagged versions will remain available via the Go module proxy and your current builds will continue to work.

Alternatives​

Codat's APIsAPI A set of rules and protocols that allows different software applications to communicate with each other. Codat provides APIs for accessing financial data from accounting, banking, and commerce platforms. remain fully available to Go applications. If you are currently using the Go SDK, you can:

• Call Codat's RESTREST An architectural style for designing networked applications. Codat's APIs follow REST principles, using standard HTTP methods. APIsAPI A set of rules and protocols that allows different software applications to communicate with each other. Codat provides APIs for accessing financial data from accounting, banking, and commerce platforms. directly using Go's standard net/http package or any HTTP client library. Our API reference documents all available endpoints.
• Switch to a supported SDK if your stack allows. Our TypeScript, Python, and C# SDKs are actively maintained and receive regular updates.

Action required​

If you don't use the Go SDK, no action is required on your part.

If you use the Go SDK, migrate to direct APIAPI A set of rules and protocols that allows different software applications to communicate with each other. Codat provides APIs for accessing financial data from accounting, banking, and commerce platforms. calls or a supported SDK before May 7, 2026.

If you have questions or need assistance, reach out to your dedicated Codat representative or contact our support team.

Expected impact if no action is taken​

Your existing builds will continue to work since published versions remain available via the Go module proxy. However, you will no longer receive bug fixes, security patches, or compatibility updates for these modules, and the SDK will fall increasingly out of date with Codat's APIsAPI A set of rules and protocols that allows different software applications to communicate with each other. Codat provides APIs for accessing financial data from accounting, banking, and commerce platforms. over time.

What's new?​

We've expanded our Bill Pay solution with the new Update suppliers endpoint.

With this update, your customers can edit suppliers in their accounting software, and we will automatically syncSync The process of fetching the latest data from a connected data source. Syncs can be triggered manually or run automatically on a schedule. these changes to your platform, keeping the records accurate and up-to-date.

The endpoint currently supports our FreeAgent, QuickBooks Online, and Xero integrations.

Who is this relevant for?​

This update is relevant for all clients using Codat's Bill Pay solution who want to give their customers a seamless bill and supplier management experience.

How to get started?​

You can start using the endpoint right now. Check out the Update suppliers endpoint in our APIAPI A set of rules and protocols that allows different software applications to communicate with each other. Codat provides APIs for accessing financial data from accounting, banking, and commerce platforms. reference, or explore Bill Pay's Update supplier documentation for a full walkthrough.

These changes will help us to:

• Focus ongoing investment on our latest and most capable product offerings.
• Provide clear timelines and migration paths for existing customers.
• Reduce long-term platform complexity while maintaining transparency.

What's changing​

On May 1st, 2026, we will move some legacy product versions into maintenance mode for a period of 12 months. After this, they will be retired and access to them will be removed.

Product lifecycle definitions​

We use the following lifecycle states across our products:

• Active product: Actively sold and maintained. These products receive new features, bug fixes, and ongoing improvements.
• Maintenance: No longer sold. These products receive no new features and no planned bug fixes or maintenance work. Customers may experience degradation over time as dependencies, platforms, or integrations evolve.
• Deprecated: No longer sold or maintained and scheduled for removal after a defined notice period.
• Retired: Access has been removed and the product is no longer available.

Affected products​

The following product versions will enter their maintenance period of 12 months on May 1st, 2026:

During the maintenance period, these versions will continue to operate, but we won't provide bug fixes, performance improvements, or compatibility updates.

Action required​

To continue benefiting from Bill Pay and Expenses functionality in an actively supported product, start your migration to the new versions as soon as possible. We'll send reminders every three months.

Expected impact if no action is taken​

From May 1st, 2027, at the end of the 12-month maintenance period:

• We will issue a deprecation notice outlining the retirement procedure of the affected product versions.
• All APIAPI A set of rules and protocols that allows different software applications to communicate with each other. Codat provides APIs for accessing financial data from accounting, banking, and commerce platforms. access to the products will be disabled.
• Requests to retired versions will no longer be supported.

Get help​

If you have questions about these changes or would like support with planning your migration, reach out to your Account Manager or Codat Support.

As part of our effort to simplify our technical estate, we are merging the type definitions from @codat/sdk-bank-feeds-types and @codat/sdk-connections into @codat/sdk-link-types using subpath exports. This reduces the number of packages you need to manage and aligns all SDK type definitions under a single package.

The existing versions of the deprecated packages will continue to work as thin re-exports, but no new versions will be published.

New import paths​

To use the new @codat/sdk-link-types package, replace your existing imports with the new subpath exports:

// Before
import { CodatConnectionsProps } from "@codat/sdk-connections";
import { CodatBankFeedsProps } from "@codat/sdk-bank-feeds-types";

// After
import { CodatConnectionsProps } from "@codat/sdk-link-types/connections";
import { CodatBankFeedsProps } from "@codat/sdk-link-types/bank-feeds";

Additionally, the initializeCodatBankFeeds function has been renamed to initCodatBankFeeds. The old function name is available as a deprecated alias.

Action required​

If you need to bump the package version or want to move to using @codat/sdk-link-types to take advantage of future feature releases, follow these steps:

1. Update your project to use @codat/sdk-link-types@1.11.0 or later.
2. Replace imports from @codat/sdk-connections with @codat/sdk-link-types/connections.
3. Replace imports from @codat/sdk-bank-feeds-types with @codat/sdk-link-types/bank-feeds.
4. If you use initializeCodatBankFeeds, rename it to initCodatBankFeeds.

Expected impact if no action is taken​

Your existing code will continue to work as the deprecated packages now re-export from @codat/sdk-link-types. However, the old packages won't receive updates and will eventually be removed. As a result, you may miss feature enhancements that will be published under @codat/sdk-link-types. You will also see deprecation warnings in your IDE for the old init functions.