Transaction Timestamps

Overview

Transaction timestamps determine how dates and times of transactions are recorded, displayed, and sorted within various components of Crassula, including the user interface, administrative panel, and generated transaction statements (PDF and XLS formats).

Display and Sorting

• Timestamp Field: transaction.createdAt

• Display Logic: Adjusted to the user's timezone

• Sorting Logic: Transactions displayed on the front-end are sorted based on the createdAt timestamp. Sorting is adapted dynamically to reflect the user's local timezone, providing an intuitive user experience.

Example

If a user in London (UTC+0) and another in New York (UTC-5) view the same transaction history, each will see the timestamp displayed according to their respective local time zones.

Transaction Statements (PDF & XLS)

For statements generated from both the administrative and client interfaces, the following logic applies:

• Timestamp Field: transaction.updatedAt

• Timezone Logic: Timezones are excluded to reflect raw data from the database (UTC).

• Sorting Logic: Transactions are sorted using the updatedAt timestamp, providing standard and predictable sorting behavior.

• Column Merge: Date and Time columns are combined into a single column labeled Date (UTC) to simplify the presentation of timestamps in transaction statements.

Example

A transaction updated on April 20, 2025, at 14:30 UTC will appear as follows in statements:

Summary of Standards

Important Notes

• This standard applies specifically to transaction timestamp handling within Crassula interfaces and statements.

• These guidelines will remain consistent, minimizing unexpected changes and ensuring reliability for users and administrators.

For additional questions or clarification regarding timestamp handling, please contact Crassula Support.