Enter dates, times and amounts
Use the units and date labels displayed by each form. The distinction between a date, a local timestamp and an exclusive boundary matters.

Local date and time inputs
Timestamp inputs such as sale Occurred at, campaign Starts and case Due at show device/browser local time. When submitted, timestamps are converted to an ISO timestamp for the service. Editing supported timestamp fields converts the stored value back to local time.
For example, 09:00 in Nairobi (UTC+3) corresponds to 06:00 UTC. Keep the device timezone correct. Do not manually subtract three hours before entering Nairobi time; the form already converts it.
Date fields show DD/MM/YYYY, for example 25/09/2026. Date-and-time fields add a 24-hour time. Open a field to type a date or choose it from the calendar. Records show day first with the month written out, for example 25 Sept 2026. Read any timezone or offset shown. If comparing an export or provider statement with a form, establish which timezone each uses before deciding the dates disagree.
Date ranges
Contract and suspension end times must be later than their start times. Campaign and other period forms also apply their stated range checks. A date-only control does not ask for a time of day.
In settlements, Period to (exclusive) means an earning exactly at the end boundary is excluded. Use the intended next boundary rather than assuming the final day is included automatically.
Live reports currently do not apply date filtering; see report scope.
Amounts in KES
A field labelled Amount (KES) or Unit price (KES) expects shillings. Enter 1250.50 for KES 1,250.50. Avoid currency symbols and thousands separators in inputs unless the control explicitly supports them. Money fields accept no more than two decimal places.
The client preserves integer-based monetary precision when calculating and displaying large amounts. Do not round an amount yourself to work around validation.
Advanced configuration units
Reward-rule Value can use minor units or basis points depending on calculation type. It is not always a KES field. Read reward plan guidance before changing those values.