When reviewing invoices, payments, or customer interactions, you may notice different date formats across the platform. Understanding how each behaves ensures accurate reporting and consistency across your data.
Type | Example | Affected by Timezone? |
Date | 01 Oct 2025 | No |
DateTime | 01 Oct 2025 10:15 | Yes |
Company Timezone | Workflow Execution, System level usage | System-Level |
1. Date Values - 01 Oct 2025
Example: (DD MMM YYYY)
These are static calendar dates and do not change based on your local timezone.
They are typically pulled from your integrations such as ERP & PSP system.
The date value remains exactly as stored in your ERP.
It does not adjust based on device or company timezone settings.
Examples of such fields: Invoice Due Date, Invoice Date, Payment Date.
2. DateTime Values - 01 Oct 2025 10:15
Example: (DD MMM YYYY HH:mm)
These fields include both a date and a specific time, and do change based on your timezone.
These fields include both a date and a specific time.
The system then converts them based on your computer’s local timezone settings.
This ensures timestamps like “Last Action” or “Activity Modified” reflect your local time accurately.
3. Company Timezone Settings
Your Company Timezone (found under Settings → Company Info) is not the same as your local or device timezone.
It’s primarily used for workflow executions, automated actions, and system tasks for example, sending reminders or triggering automation workflows.
It does not affect how static or local DateTime values appear in the user interface.
