A rental starts before midnight, ends after midnight and is charged later. Which day should receive the rental count? A Dutch operator can obtain three different answers from otherwise correct records. Before comparing venue performance, define the event behind each metric and the timezone used to group it.
The useful deliverable is a timestamp dictionary attached to the reporting workbook. It explains what each row counts, where its time comes from and how late or corrected events are handled. It is an operating workpaper, not a promise of a new native analytics module.
Keep the rental and payment clocks distinct
For the matched CoreCharge WisePad 3 route, the native Android rental application and Terminal SDK run inside the cabinet through the agreed USB data and power arrangement. CoreCharge connects payments, orders, release, returns and rent calculation. Stripe processes payments into the operator’s own account.
Stripe’s Netherlands guidance specifies EUR and matching Dutch account and Location requirements, with WisePad 3 listed. The operator buys and registers the eligible local reader. Confirm the actual staffed or unattended installation scenario separately from reporting design.
| Metric label | Proposed event basis | Question before using it |
|---|---|---|
| Successful borrowing | Confirmed physical release | Is this a release result or only a command acknowledgement? |
| Returned rentals | Matched return event | Which original order and power bank does it close? |
| Rental duration | Validated release-to-return elapsed time | Are both timestamps expressed as unambiguous instants? |
| Captured rent | Actual payment capture | Does its date differ from the rental’s start or return? |
| Customer correction | Verified adjustment result | Is the correction counted now without erasing the original event? |
Confirm which fields are available in the actual CoreCharge Excel export and Stripe records. Document unavailable fields rather than creating a precise-looking metric from an unsupported proxy. Keep a payment-attempt count separate from a count of distinct successful rentals.
Choose the reporting day deliberately
State whether the workbook uses UTC or local Dutch business days. Stripe’s report configuration guidance explains that its timezone choice affects both date filtering and displayed times. Match that setting to the workpaper before investigating a midnight difference as missing revenue.
For an illustrative rental released at 23:50 and returned at 00:20 the next day, the borrowing belongs to the first release day and the return to the second return day under those definitions. A later capture belongs to its own payment period. None of those choices requires inventing three rentals.
Preserve offsets around daylight-saving changes
Use a named timezone such as Europe/Amsterdam and retain an unambiguous underlying timestamp or UTC offset. IANA’s Time Zone Database maintains the rules used by software to translate instants into local time. A fixed summer offset should not be treated as a permanent Dutch timezone.
When clocks move back, two records can display the same local hour while representing different instants. When clocks move forward, a wall-clock hour is skipped. Calculate elapsed duration from validated instants rather than subtracting ambiguous text labels. Ask the integration team to demonstrate the chosen calculation; do not assume every export already exposes the required offset.
Test the dictionary with a small exception set
Include a rental crossing midnight, a late-arriving return record and a synthetic clock-change example in the workbook review. Preserve source times alongside converted reporting times. Give corrections a note and reviewer so a later rerun can explain changed totals.
Name an owner for the dictionary and retain its version. Comparing two weeks should use consistent definitions or explain explicitly which reporting rule changed.
The full-journey acceptance guide supplies the physical-event foundation. The weekly financial close guide explains why operational periods and bank payouts differ.
Review CoreCharge reader-equipped stations or request a Dutch reporting-field walkthrough with your proposed metric definitions and reporting timezone.
References and project scope
Technical references checked on 17 October 2026. The operating procedures above are planning guidance; hardware, account access and payment settings are confirmed for each deployment.