Skip to content

Conversation

@codatbot
Copy link
Collaborator

@codatbot codatbot commented Jan 23, 2026

Updated OAS at 2026-01-23T09:38:54Z


Note

Clarifies date handling for bank transactions and aligns examples accordingly.

  • In Codat-Bank-Feeds.json, replaces date field $ref with an explicit "Local date time" string schema, adding ISO 8601 examples and guidance that timezone offsets are ignored and values are treated as local (recommend omitting Z).
  • Updates example transaction payloads (Xero, QuickBooks Online Bank Feeds, FreeAgent, Sage) to remove the trailing Z from date values.

Written by Cursor Bugbot for commit 9de301c. This will update automatically on new commits. Configure here.

@vercel
Copy link

vercel bot commented Jan 23, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Review Updated (UTC)
codat-docs Ready Ready Preview, Comment Jan 23, 2026 9:42am

Request Review

Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.

This PR is being reviewed by Cursor Bugbot

Details

Your team is on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle for each member of your team.

To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.

"2023-08-22T10:21:00",
"2023-08-22"
],
"description": "In Codat's data model, dates and times are represented using the <a class=\"external\" href=\"https://en.wikipedia.org/wiki/ISO_8601\" target=\"_blank\">ISO 8601 standard</a>. Date and time fields are formatted as strings; for example:\n\n```\n2023-08-22T10:21:00\n2023-08-22\n```\n\nWhen pushing bank transaction data to Codat, the date is treated as a local date. This means:\n\n- The date/time is used exactly as provided, without any timezone conversion.\n- If a timezone offset is included (e.g., `2023-08-22T10:21:00-05:00`), the offset will be ignored and only the local date/time portion will be used.\n- We recommend providing dates without a timezone suffix for clarity (e.g., `2023-08-22T10:21:00` rather than `2023-08-22T10:21:00Z`)."
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Timezone offsets silently ignored in transaction dates

High Severity

The date field now silently ignores timezone offsets in ISO 8601 timestamps, treating 2023-08-22T10:21:00-05:00 and 2023-08-22T10:21:00+05:00 as identical times despite being 10 hours apart. This violates ISO 8601 semantics and can cause incorrect transaction ordering when clients submit transactions from different timezones, leading to data integrity issues in bank transaction records.

Additional Locations (1)

Fix in Cursor Fix in Web

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants