> For the complete documentation index, see [llms.txt](https://docs.kick.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kick.co/workflows/transaction-dates.md).

# Transaction Dates

Understand why a transaction's date in Kick can differ from your bank, how Pacific Time affects your reports, and which dates stay as entered.

Kick uses Pacific Time for your workspace. You can't select a different timezone during setup or change it afterward.

### How Kick dates your transactions

When a connected account sends an exact timestamp for a transaction, Kick converts it to Pacific Time and uses the day it falls on in your books and reports.

For example, a payment timestamped January 1 at 6:00 AM UTC is December 31 at 10:00 PM Pacific Time. It falls on December 31 in Kick, so it appears in the prior year's reports.

Pacific Time follows daylight saving time automatically. You don't need to adjust it yourself.

***

### Dates that stay as entered

When a source sends only a calendar date, Kick keeps that date. This includes:

* Bank and card transactions sent with only a date.
* Dates you select in Kick, such as when you create or update a manual transaction, check, or deposit.
* Calendar dates in files you import with the [Universal Importer](https://docs.kick.co/getting-started/universal-importer.md).
* Bill and invoice issue dates, payment dates, and due dates sent as calendar dates.
* Task due dates.

For example, a bank transaction sent with a January 1 date stays on January 1. It doesn't move to December 31.

Report dates work the same way. A report for December 1 to December 31 includes every transaction dated in that range in Kick.

***

### Activity times

[Activity](https://docs.kick.co/collaboration/activity.md) times appear in each person's local time. They don't change the dates in your books, and neither does changing your computer's timezone.

### If a transaction date looks wrong

Compare the date in Kick with the date and time from your bank or connected account. A transaction near midnight can fall on a different day in Pacific Time.

If the date still doesn't match what you expect, [contact support](https://docs.kick.co/troubleshooting/contact-us.md) with the transaction and its source date. The workspace timezone can't be changed.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.kick.co/workflows/transaction-dates.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
