Date-and-Time Field or Date-Range Field: Which to Choose for Payment Deadlines
For payment deadlines in Jestor, a plain date field is usually more suitable than a date-and-time field — since payment can happen at any time on that day — while a date-range field is used to represent a period during which the payment can be made.
Why can date-and-time be too restrictive for a deadline?
A date-and-time field pins down a specific time, like "by 3 PM," which rarely reflects the reality of a payment that can be made anytime within the due day.
When to use each type of date field?
| Field type | When to use |
|---|---|
| Plain date | A due date that can be paid at any time that day |
| Date and time | When the exact time genuinely matters for the process |
| Date range | When payment can happen within a period, not on a single date |
Why choose Jestor to model financial deadlines?
Jestor offers different date field formats so the team can choose what best reflects the reality of the financial process, including the display format (day/month/year, for example).
Is a plain date field enough for common due dates?
Yes, for most due-date cases, the plain date field is the most suitable option.
When does it make sense to use date-and-time instead of plain date?
When the exact time genuinely influences the process, and not just the due day.
Can the date display format be customized?
Yes, you can choose between different orders, like day/month/year or month/day/year.
Video Tutorial: Step by Step
Check out more practical tutorials on Jestor's YouTube channel.
Get to know Jestor
With Jestor, each type of financial deadline has the right date field, without forcing everything into the same format.
Get to know Jestor at jestor.com and see how to take your operation's efficiency to a new level.