Aug <var data-var='date'>24</var>, <var data-var='time'>16:46</var> BST Resolved - The incident has now been resolved, ongoing monitoring has shown the platform has returned to normal stability. All users previously affected should be able to use affected services without disruption. If you are still affected by this issue, please contact support@codat.io Aug <var data-var='date'>24</var>, <var data-var='time'>15:36</var> BST Monitoring - We have implemented a fix. Affected users should now notice that they are again able to use the affected services as normal. Queued syncs will resume automatically. Our teams continue to monitor the platform to ensure continued stability. If you experience any issues please contact support@codat.io for further assistance. Aug <var data-var='date'>24</var>, <var data-var='time'>14:49</var> BST Identified - We're aware of an issue affecting a number of our integrations and sync services and are currently implementing a fix to remediate the issue. Requests to these services are currently returning errors. Retrying will return the same error until we've fixed the issue, so no action is needed from you. Queued syncs will resume automatically once service is restored. All other integrations and services are operating normally. We'll update this page as soon as we have more to share. This incident will be updated as soon as we have successfully tested and rolled out a fix, and no later than 4:00PM GMT.

Intermittent API errors

Aug <var data-var='date'>11</var>, <var data-var='time'>16:32</var> BST Resolved - The incident has now been resolved, ongoing monitoring has shown the platform has returned to normal stability. All users previously affected should be able to load the reports page. If you are still affected by this issue, please contact support@codat.io Aug <var data-var='date'>11</var>, <var data-var='time'>16:09</var> BST Monitoring - We have implemented a fix. Affected users should now notice that they are now able to access the reports page without an error. You may need to perform a hard refresh of your browser. Our teams continue to monitor the platform to ensure continued stability. If you experience any issues please contact support@codat.io for further assistance. Aug <var data-var='date'>11</var>, <var data-var='time'>16:00</var> BST Investigating - We are actively investigating an issue preventing users from accessing the Company reports page. Affected users will notice that when attempting to navigate to the Lending > Reports page for a given company, the web page will show a generic 'Oh no! Something went wrong' error. This incident will be updated as soon as we have identified the issue, and no later than 17:00

Portal: Company Reports Page Failing To Load.

Aug <var data-var='date'> 5</var>, <var data-var='time'>16:47</var> BST Resolved - The incident has now been resolved, ongoing monitoring has shown the platform has returned to normal stability. All users previously affected should be able to generate reports and sync expenses without unexpected latencies. If you are still affected by this issue, please contact support@codat.io Aug <var data-var='date'> 5</var>, <var data-var='time'>10:18</var> BST Monitoring - Affected users should now notice that reports generation and sync for expenses transactions pushes run much more quickly. Our teams continue to monitor the platform to ensure continued stability. If you experience any issues please contact support@codat.io for further assistance. Aug <var data-var='date'> 5</var>, <var data-var='time'>10:01</var> BST Investigating - We are actively investigating an issue which will be causing our reports generation and sync for expenses transactions pushes to take longer than normal. Affected users will notice that when they attempt to generate a report, it may take several minutes longer than usual.

Reports Generation and Expenses Latency

Jul <var data-var='date'>29</var>, <var data-var='time'>23:20</var> BST Resolved - The incident has now been resolved, ongoing monitoring has shown the platform has returned to normal stability. All users previously affected should be able to push and pull data from and to Xero as expected. If you are still affected by this issue, please contact support@codat.io Jul <var data-var='date'>28</var>, <var data-var='time'>10:55</var> BST Update - We are continuing to work with our partner Xero, and a resolution has been identified. Both parties are looking to assuage the problem asap and a resolution should be implemented as soon as possible. As per our observations, the failures are intermittent, so any push or pull operations which don't succeed as expected can be retried. As soon as we are confident that a fix has been deployed, we will update the status page to reflect this. Jul <var data-var='date'>28</var>, <var data-var='time'>09:13</var> BST Identified - We are continuing to work with our partners at Xero in an attempt to mitigate this issue. As per our observations, the failures are intermittent, so any push or pull operations which don't succeed as expected can be retried. As soon as we are confident that a fix has been deployed, we will update the status page to reflect this. Jul <var data-var='date'>24</var>, <var data-var='time'>12:25</var> BST Update - We have identified the cause of the incident and are currently implementing a fix to remediate the issue. This incident will be updated as soon as we have successfully tested and rolled out the fix, which will be no later than 13:25 Jul <var data-var='date'>24</var>, <var data-var='time'>11:48</var> BST Update - We have identified the cause of the incident and are currently implementing a fix to remediate the issue. This incident will be updated as soon as we have successfully tested and rolled out a fix and no later than 12:48 UK Time Jul <var data-var='date'>22</var>, <var data-var='time'>14:57</var> BST Investigating - Following on from Incident https://status.codat.io/incidents/92vdwfbdrw97, we are still observing some Xero failures. Affected users will notice that their push or pull operations to Xero are failing with an Auth - related error. The errors appear to be transient, so our users are advised to retry any failed operations.

Intermittent Xero Integration Outage

Jul <var data-var='date'>27</var>, <var data-var='time'>19:33</var> BST Resolved - The incident has now been resolved, as ongoing monitoring has shown the platform has returned to normal stability. You may have noticed errors with the Codat API or the Codat Portal from 14:54-15:06 UTC If you are still affected by this issue, please contact support@codat.io Jul <var data-var='date'>27</var>, <var data-var='time'>16:09</var> BST Monitoring - We have implemented a fix to the complete outage. Affected users should now notice that they are again able to use the Codat portal and Api as normal. Our teams continue to monitor the platform to ensure continued stability. If you experience any issues please contact support@codat.io for further assistance. Jul <var data-var='date'>27</var>, <var data-var='time'>16:08</var> BST Investigating - We are actively investigating an issue preventing users from both using the Codat portal and calling our public facing APIs. Affected users will notice that they are unable to call the Codat Api without an error or login to the Codat portal. This incident will be updated as soon as we have identified the issue, and no later than 17:07

Complete Outage of Codat Portal and all Codat API services

Jul <var data-var='date'>24</var>, <var data-var='time'>13:57</var> BST Resolved - The incident has now been resolved, ongoing monitoring has shown the platform has returned to normal stability. If you are still affected by this issue, please contact support@codat.io Jul <var data-var='date'>24</var>, <var data-var='time'>13:48</var> BST Monitoring - We have implemented a fix for the outage. Codat's services and Portal should now be accessible again. Our teams continue to monitor the platform to ensure continued stability. If you experience any issues please contact support@codat.io for further assistance. Jul <var data-var='date'>24</var>, <var data-var='time'>13:43</var> BST Investigating - We are actively investigating an issue preventing users from logging into the Codat Portal and making API calls to our Public API. Affected users will notice that they are unable to log into the Codat web portal and make API calls. There would be a 500 category error surfaced in both cases. This incident will be updated as soon as we have identified the issue, and no later than 14:40

Major outage across all Codat Platform.

Jul <var data-var='date'>17</var>, <var data-var='time'>16:01</var> BST Resolved - The incident has now been resolved, ongoing monitoring has shown the platform has returned to normal stability. All users previously affected should now again be able to connect their Xero Companies to Codat. If you are still affected by this issue, please contact support@codat.io Jul <var data-var='date'>17</var>, <var data-var='time'>13:07</var> BST Identified - We have identified a mitigation whilst we continue to investigate the root cause. Users should now be able to link Xero companies to Codat. This incident will be updated as soon as we have successfully tested and rolled out a permanent fix. Jul <var data-var='date'>17</var>, <var data-var='time'>13:07</var> BST Update - We have identified a mitigation whilst we continue to investigate the root cause. Users should now be able to link Xero companies to Codat. This incident will be updated as soon as we have successfully tested and rolled out a permanent fix. Jul <var data-var='date'>17</var>, <var data-var='time'>13:06</var> BST Investigating - We are actively investigating an issue preventing a subset of users from linking their Xero companies to Codat. Affected users will notice that upon being redirected to Xero during the link flow, a Xero error page will show, with a 500 error code. This incident will be updated as soon as we have identified the issue, and no later than 14:05

Intermittent Xero Link Failures

Jun <var data-var='date'>22</var>, <var data-var='time'>19:25</var> BST Resolved - The incident has now been resolved, as ongoing monitoring has shown the platform has returned to normal stability. If you are still affected by this issue, please contact support@codat.io Jun <var data-var='date'>22</var>, <var data-var='time'>16:43</var> BST Monitoring - We have implemented a fix. Affected users should notice that API queries have returned to normal, and they can now login to the Portal. Our teams continue to monitor the platform to ensure continued stability. If you experience any issues, please contact support@codat.io for further assistance. Jun <var data-var='date'>22</var>, <var data-var='time'>16:22</var> BST Investigating - Our monitoring has flagged a higher than usual volume of errors. Affected users may notice that API calls are erroring, and they may be unable to login to the Codat Portal. This could have been noticed between 15:03UTC - 15:30UTC This incident will be updated as soon as we have identified the issue.

Jun <var data-var='date'> 2</var>, <var data-var='time'>15:45</var> BST Resolved - The incident has now been resolved, ongoing monitoring has shown the platform has returned to normal stability. All users previously affected should be able to create companies with tags as normal. If you are still affected by this issue, please contact support@codat.io Jun <var data-var='date'> 2</var>, <var data-var='time'>15:07</var> BST Monitoring - We have implemented a fix in production. Affected users should now notice that they're now able to create companies with tags as normal. Our teams continue to monitor the platform to ensure continued stability. If you experience any issues please contact support@codat.io for further assistance. Jun <var data-var='date'> 2</var>, <var data-var='time'>15:01</var> BST Identified - We are currently investigating an issue preventing users from creating companies with tags. This incident will be updated as soon as we have successfully tested and rolled out a fix in production.

Users unable to create companies with Tags

May <var data-var='date'>29</var>, <var data-var='time'>15:50</var> BST Resolved - This incident has been resolved. Pushing to QBD is now working as expected. May <var data-var='date'>29</var>, <var data-var='time'>15:07</var> BST Monitoring - We have implemented a fix. Affected users should now notice that their QBD push operations now no longer fail with an error message referencing a Third Party Gateway. Our teams continue to monitor the platform to ensure continued stability. If you experience any issues please contact support@codat.io for further assistance. May <var data-var='date'>29</var>, <var data-var='time'>15:03</var> BST Investigating - We are actively investigating an issue preventing users from push items to QuickBooks Desktop Affected users will notice that their push operations are failing with 'Third-party gateway responded with an erorr status but did not return a valid error body' This incident will be updated as soon as we have identified the issue, and no later than 16:03

QuickBooks Desktop Push Operation Outage

May <var data-var='date'>29</var>, <var data-var='time'>12:17</var> BST Resolved - End-users attempting to link to TrueLayer would've experienced an issue for an approximately 40 min period this morning, where the callbacks to the Codat system, after authenticating on the banking-provider side were failing with an error page which read "Unknown Destination". Affected users would have noticed that after they entered their credentials in their banking-provider's app, when they would ordinarily get directed back to the Codat system, they would've instead seen an "Unknown Destination" error in their browser. We have resolved the incident now. End-users will be able to link to TrueLayer successfully and be directed back to Codat's application.

TrueLayer call backs routing to "Unknown Destination" error page.

May <var data-var='date'>28</var>, <var data-var='time'>16:30</var> BST Resolved - Our monitoring flagged that a higher than normal number of Plaid banking-transaction fetches were failing between 29th May 16:19 GMT and 1st June 16:30 GMT. Affected users would have noticed that for Plaid connected companies, banking-transaction datasets were failing with a FetchError, when it was their first ever attempt to fetch this particular dataset. The cause of the issue has been identified as a DNS change preventing us from receiving webhooks from Plaid's service. The DNS change has now been rectified and we are again able to receive messages from the Plaid system. We have improved our testing around these types of changes to our system. If you are still affected by this issue, please contact support@codat.io for further assistance.

Plaid banking-transaction fetches failing intermittently.

Apr <var data-var='date'>22</var>, <var data-var='time'>13:24</var> BST Resolved - The incident has now been resolved, ongoing monitoring has shown the platform has returned to normal stability. All users previously affected should be able to successfully complete push operations to QuickBooks Desktop without disruption. If you are still affected by this issue, please contact support@codat.io Apr <var data-var='date'>21</var>, <var data-var='time'>19:51</var> BST Monitoring - We have implemented a fix in Production. Affected users should now notice that all Quickbooks Desktop push operations are completing successfully. Please keep in mind that some Push Operations may remain in a Pending status if the end user's computer is offline. These Pending Push operations will resume when they are back online. Our teams continue to monitor the platform to ensure continued stability. If you experience any issues please contact support@codat.io for further assistance. Apr <var data-var='date'>21</var>, <var data-var='time'>18:41</var> BST Identified - The issue has been identified and a fix is being implemented. Apr <var data-var='date'>21</var>, <var data-var='time'>17:02</var> BST Update - We are continuing to investigate this issue. Apr <var data-var='date'>21</var>, <var data-var='time'>16:59</var> BST Investigating - We are actively investigating an issue preventing QuickBooks Desktop Push Operations from completing as quickly as expected. Affected users will notice that a small subset of their QuickBooks Desktop push Operations may take a lot longer than usual to complete, and will appear as though stuck in pending for a long time. This incident will be updated as soon as we have identified the issue, and no later than 18:00

QuickBooks Desktop Push Operations not moving beyond Pending

Mar <var data-var='date'>26</var>, <var data-var='time'>15:23</var> GMT Resolved - The incident has now been resolved, ongoing monitoring has shown the platform has returned to normal stability. All users previously affected should be able to sync datasets without disruption. If you are still affected by this issue, please contact support@codat.io Mar <var data-var='date'>26</var>, <var data-var='time'>11:21</var> GMT Monitoring - We have implemented a fix in production. Affected users should now notice that datasets are processing normally. Our teams continue to monitor the platform to ensure continued stability. If you experience any issues please contact support@codat.io for further assistance. Mar <var data-var='date'>26</var>, <var data-var='time'>10:47</var> GMT Investigating - We are actively investigating an issue causing a delay in datasets moving from the processing stage. This incident will be updated as soon as we have identified the issue.

Dataset delay in processing stage

Mar <var data-var='date'>19</var>, <var data-var='time'>13:22</var> GMT Resolved - The incident has now been resolved, ongoing monitoring has shown the platform has returned to normal stability. All users previously affected should be able to create Bank Accounts on behalf of Xero connected companies. If you are still affected by this issue, please contact support@codat.io Mar <var data-var='date'>19</var>, <var data-var='time'>13:09</var> GMT Monitoring - We have implemented a fix. Affected users should now notice that they are again able to push Bank Accounts on behalf of Xero connected companies. Our teams continue to monitor the platform to ensure continued stability. If you experience any issues please contact support@codat.io for further assistance. Mar <var data-var='date'>19</var>, <var data-var='time'>12:49</var> GMT Investigating - We are actively investigating an issue preventing users from Creating Bank Accounts through Codat's API for Xero connected companies. Affected users may notice that their Bank Account Push Operations Fail with a 524 error. This incident will be updated as soon as we have identified the issue, and no later than 13:48

Push Bank Accounts Intermittently Failing for Xero Connections

Mar <var data-var='date'>13</var>, <var data-var='time'>13:30</var> GMT Resolved - Our monitoring flagged that datasets were failing with an InternalError between 13.20 GMT and 13.25 GMT when a fix was released. This resolved the issue for the majority however some integrations would have still seen this until 13.35 GMT. The cause of the issue has been identified as an issue with a release causing failures. Service has now been restored. If you are still affected by this issue, please contact support@codat.io for further assistance.

Datasets failing with InternalErrors

Mar <var data-var='date'>11</var>, <var data-var='time'>12:00</var> GMT Resolved - During this incident, a small subset of our users may have noticed that they were unable to connect their Oracle NetSuite instances to Codat. After having given permission in the NetSuite system, upon being redirected back to Codat they would've immediately been shown a screen stating "There has been an error connecting to Oracle NetSuite". This was as a result of a backend configuration change, which has subsequently been reverted. End Users will now be able to connect their Oracle NetSuite instances to Codat as expected.

Oracle NetSuite intermittent linking errors

Mar <var data-var='date'> 6</var>, <var data-var='time'>14:53</var> GMT Resolved - The incident has now been resolved, ongoing monitoring has shown the platform has returned to normal stability. All users previously affected should be able to push attachments to QBO Sandbox without disruption. If you are still affected by this issue, please contact support@codat.io Mar <var data-var='date'> 6</var>, <var data-var='time'>10:38</var> GMT Monitoring - We have implemented a fix in production. Affected users should now notice that they're able to push attachments to QBO Sandbox. Our teams continue to monitor the platform to ensure continued stability. If you experience any issues please contact support@codat.io for further assistance. Mar <var data-var='date'> 6</var>, <var data-var='time'>10:26</var> GMT Investigating - We are actively investigating an issue preventing users from pushing attachments to Quickbooks Online Sandbox. Affected users will notice that they receive a 400 error response when attempting to push attachments to Quickbooks Online Sandbox. This incident will be updated as soon as we have identified the issue, and no later than 11.30AM GMT.

Unable to push attachments to QBO Sandbox

Feb <var data-var='date'>24</var>, <var data-var='time'>14:59</var> GMT Resolved - The incident has now been resolved, ongoing monitoring has shown the platform has returned to normal stability. All users previously affected should be able to generate Credit Model and Categorized Bank Statements reports in Production without disruption. If you are still affected by this issue, please contact support@codat.io Feb <var data-var='date'>24</var>, <var data-var='time'>11:10</var> GMT Monitoring - We have implemented a fix in Production. Affected users should now notice that Credit Model and Categorized Bank Statements reports complete successfully. If you were affected, please queue the report in the Codat portal or via the API. Our teams continue to monitor the platform to ensure continued stability. If you experience any issues please contact support@codat.io for further assistance. Feb <var data-var='date'>24</var>, <var data-var='time'>10:38</var> GMT Update - We are continuing to investigate this issue. Feb <var data-var='date'>24</var>, <var data-var='time'>10:34</var> GMT Investigating - We are actively investigating an issue preventing users from generating reports for the Credit Model and the Categorized Bank Statements. Affected users will notice that the Credit Model Report and the Categorized Bank Statements reports are currently timing out and failing to generate. This incident will be updated as soon as we have identified the issue, and no later than 11:30am UK time.

Credit Model and Categorized Bank Statements reports generation unavailable in Production

Feb <var data-var='date'>24</var>, <var data-var='time'>11:12</var> GMT Resolved - The incident has now been resolved, ongoing monitoring has shown the platform has returned to normal stability. All users previously affected should be able to push transactions to QuickBooks Online without disruption. If you are still affected by this issue, please contact support@codat.io. Feb <var data-var='date'>24</var>, <var data-var='time'>02:30</var> GMT Monitoring - We have implemented a fix in Production. Affected users should now notice that they are able to push data to QBO successfully. Our teams continue to monitor the platform to ensure continued stability. If you experience any issues please contact support@codat.io for further assistance. Feb <var data-var='date'>23</var>, <var data-var='time'>23:47</var> GMT Investigating - We are actively investigating an issue where a number of QBO Push Operations are failing with an "invalid_grant" or "Poisoned" response. This incident will be updated as soon as we have identified the issue.

QBO Push Operations may fail

Feb <var data-var='date'>20</var>, <var data-var='time'>09:20</var> GMT Resolved - The incident has now been resolved, ongoing monitoring has shown the platform has returned to normal stability. All users previously affected should be able to retrieve reports via the Codat portal without disruption. If you are still affected by this issue, please contact support@codat.io Feb <var data-var='date'>19</var>, <var data-var='time'>14:17</var> GMT Monitoring - We have implemented a fix in Production. Affected users should now notice that they are able to run the reports successfully in Production. Our teams continue to monitor the platform to ensure continued stability. If you experience any issues please contact support@codat.io for further assistance. Feb <var data-var='date'>19</var>, <var data-var='time'>13:25</var> GMT Identified - We are actively investigating an issue preventing users from generating Spend Insight, Categorized Bank Statement reports. Affected users will notice that reports are much slower to complete and upon completion, return a 'Failed' status. This incident will be updated as soon as we have identified the issue, and no later than 15:00 UK time.

Report generation unavailable in Production

Feb <var data-var='date'>16</var>, <var data-var='time'>14:30</var> GMT Resolved - Between 12:30 UK time and 15:45 UK time on 16th February 2026, some Categorized Bank Statement and Credit Model reports experienced unexpected latencies to complete. The incident has now been resolved, ongoing monitoring has shown the platform has returned to normal stability. All users previously affected should be able to generate reports, including the Credit Model and the Categorized Bank Statement reports, without disruption. If you are still affected by this issue, please contact support@codat.io.

Categorized Bank Statement and Credit Model report generation temporarily unavailable

Feb <var data-var='date'> 4</var>, <var data-var='time'>15:34</var> GMT Resolved - We have released a fix for this issue. Data connections can now be created to Shopify, for clients using custom apps. Please see our docs for updated linking instructions: https://docs.codat.io/integrations/commerce/shopify/commerce-shopify-custom-apps If you are still affected by this issue, please contact support@codat.io Feb <var data-var='date'> 3</var>, <var data-var='time'>09:35</var> GMT Identified - We have identified the issue and are in the process of implementing a fix. This incident will be updated as soon as we have successfully tested and rolled out a fix in production Feb <var data-var='date'> 2</var>, <var data-var='time'>10:56</var> GMT Investigating - We are currently investigating an issue where no new data connections can be linked to Shopify, for clients using custom apps. Existing connections are not affected. Affected users will notice that they are unable to generate a Shopify access token from their custom app during the linking process. This incident will be updated as soon as we have identified the issue.

Shopify - unable to create new connections

Jan <var data-var='date'>16</var>, <var data-var='time'>13:05</var> GMT Resolved - We have now successfully deployed a fix for this issue. Users of our system should now notice that for Xero connected companies, any bankTransactions datasets which had been failing with a Validation Error are now completing successfully. Jan <var data-var='date'>16</var>, <var data-var='time'>13:01</var> GMT Update - We are in the process of releasing a fix to this issue currently. This incident will be updated as soon as we have identified the issue, and no later than 14:05 Jan <var data-var='date'>16</var>, <var data-var='time'>11:55</var> GMT Identified - We have identified the root cause of the issue and are currently working on a fix. We hope to be able to release a fix to production in the very near future. This incident will be updated as soon as we have identified the issue, and no later than 13:05 Jan <var data-var='date'>16</var>, <var data-var='time'>11:03</var> GMT Investigating - We are actively investigating an issue whereby for Xero connected Companies, we are seeing a higher than expected number of validation errors on the BankTransactions dataset. Affected users will notice that companies who are synching BankTransactions datasets may have datasets fail with a Validation Error. This incident will be updated as soon as we have identified the issue, and no later than 12:05

Xero BankTransactions: High Number of Validation Errors

Dec <var data-var='date'>18</var>, <var data-var='time'>14:43</var> GMT Resolved - The incident has now been resolved, ongoing monitoring has shown the platform has returned to normal stability. All users previously affected should be able to link to bank feeds without disruption. If you are still affected by this issue, please contact support@codat.io Dec <var data-var='date'>18</var>, <var data-var='time'>13:59</var> GMT Update - We have identified the cause of the incident and are currently implementing a fix to remediate the issue. This incident will be updated as soon as we have successfully tested and rolled out a fix, and no later than 14:58 GMT Dec <var data-var='date'>18</var>, <var data-var='time'>13:48</var> GMT Investigating - We are actively investigating an issue preventing users from progressing in the bank feeds link flow, when consumers of our service are leveraging our bank feeds link SDK. Affected users will notice that the calls to generate the OTP are failing with a CORS error, and that their end users are unable to progress beyond the 'configure your accounts' screen. This incident will be updated as soon as we have identified the issue, and no later than 14:47

Bank Feeds Link SDK: calls to generate OTP failing with a CORS error

API Connectivity

Portal

Link

Webhooks & Alerts

General Connectivity & Portal

Bank Feeds Connectivity

QuickBooks Online Bank Feeds

Sage Bank Feeds

FreeAgent Bank Feeds

Xero Bank Feeds

Exact Bank Feeds

Bank Feeds

Lending Connectivity

Dynamics 365 Business Central

Exact Online

FreeAgent

FreshBooks

MYOB Business

Oracle NetSuite

QuickBooks Desktop

QuickBooks Online

Sage 50

Sage 200 Cloud

Sage Business Cloud Accounting

Sage Intacct

Wave

Xero

Zoho Books

Plaid

TrueLayer

Amazon Seller Central

BigCommerce

Clover

Lightspeed Restaurant K-Series

Mollie

PayPal

PrestaShop

Shopify

Square

Stripe

SumUp

WooCommerce

Zettle

Chargebee

Enhanced Cashflow Report Generation and Download

Enhanced Financials Report Generation and Download

Enhanced Invoices Report Generation and Download

Audit Report Generation and Download

Aged Debtors Report Generation and Download

Aged Creditors Report Generation and Download

Liabilities Report Generation and Download

Credit Model Report Generation and Download

Lending

Spend Insights Connectivity

MS Dynamics 365 BC

Spend Analysis Report Generation and Download

Spend Summary Report Generation and Download

Spend Insights

Sync For Commerce Connectivity

Sync For Commerce

Sync For Expenses Connectivity

Expenses

Bill Pay (Sync) Connectivity

Bill Pay (sync)

Bill Pay (async) Connectivity

Bill Pay (async)

Sync For Payroll Connectivity

Sync For Payroll

Xero - Accounting API (External)

QuickBooks Online - Intuit Developer Group Services

QuickBooks Online - Accounting API (External)

Shopify API & Mobile

Stripe API

BigCommerce API & Webhooks

Plaid API - Production

Svix - Webhooks

Email Alerts Message Delivery (External)

Mailgun (Email notifications & alerts)

npm Package installation

GitHub Packages

Python Infrastructure pypi.org - General

Auth0 User Authentication

Auth0 Machine to Machine Authentication

Auth0 Management API

Auth0 Email Delivery

Third-party integrations and infrastructures

Exact

Freshbooks

MYOB

Sage 200cloud

Legacy - Accounting API

Legacy - Banking API

Big Commerce

Lightspeed Restaurant (Series K)

Legacy - Commerce API

Schedule

NetSuite

Custom Product 91D68E9E-9C28-4C9A-9803-73A92AC3F748

Custom Product CF3A11B4-ACC3-4BC2-B498-64A9F638311C

OneUp

Custom Product C9ECB109-8C62-4595-9130-849B710CFE14

Sage 200

Custom Product F74BC050-CE30-4CF3-A1F6-7D5F3B5F7BD9

Custom Product 12BCD5ED-1A48-46E6-BD71-2D638FE5B7BF

Custom Product 55B5F014-36F3-4EC4-84B2-6B6DAF2960B8

Codat

Is Codat down?

Codat status is UP

Lastest published events

Intermittent API errors

Portal: Company Reports Page Failing To Load.

Reports Generation and Expenses Latency

Codat Services, Components and Regions

Recent Codat events

Intermittent API errors

Portal: Company Reports Page Failing To Load.

Reports Generation and Expenses Latency

Intermittent Xero Integration Outage

Complete Outage of Codat Portal and all Codat API services

Major outage across all Codat Platform.