PlanMaker TIMEVALUE Function: Convert Time Text into Numbers

Use it when a CSV or text export contains times such as 10:30:00 am, but the values are stored as text rather than numbers. Numeric time values allow durations to be calculated, differences to be checked and times to be formatted consistently. Do not assume that every string that visually resembles a clock time is already numeric. Keep a copy of the original import while checking conversions.

SoftMaker notes that TIMEVALUE is primarily retained for compatibility because modern PlanMaker can often convert recognized time text automatically. Writing the conversion explicitly can still be useful in a cleanup worksheet and makes the intention easy to audit. SoftMaker description.

=TIMEVALUE(Text)

There is one required argument. In a formula, quoted literal text is "10:30:00 am", while a cell reference is written A2, without extra quotation marks. The current SoftMaker help labels the argument Text and documents the clock-time sample. Its prose says a string “representing a date” even though the heading, formula, worked time example and see-also links concern time; treat that wording as a documentation ambiguity rather than expanding the supported parser contract. 2026 vendor page.

The formula contains no commas or semicolons inside TIMEVALUE because there is only one argument. Accepted clock notation and AM/PM labels can vary by region, however. Prefer the app’s recognized local time format and compare a known input before bulk conversion. PlanMaker data-entry notes.

Format A2:A4 as Text before entering these inputs; otherwise PlanMaker may convert them automatically. For the English-language AM/PM form used in SoftMaker examples, enter the following:

Calculation behind row 2: (10 hours × 60 + 30 minutes) ÷ 1,440 minutes per day = 0.4375. The return value is numeric, not the literal text "10:30". If B2 displays 10:30 instead of 0.4375, switch the number format to an ordinary numeric display; to show a clock, apply a time display such as h:mm. TIMEVALUE · number formats.

Create a time from numeric parts instead

PlanMaker’s TIME function takes three arguments in this order:

=TIME(10,30,0)

It constructs the corresponding numeric time from hours, minutes and seconds, rather than parsing a text string. Its return is expected to correspond to 0.4375 for 10:30:00. The vendor’s distinct official example, TIME(0,20,0), returns approximately 0.01389 because 20 minutes is 1/72 of a day. This reference verifies the formula structure; TIME(10,30,0) was not tested natively.

Suppose the text in A2 is 10:30:00 am and A3 is 6:45:00 pm. With numeric B2/B3 converted by TIMEVALUE, enter in C2:

=(B3-B2)*24

Independently calculated expected output: 8.25 hours. The difference in stored fractions is 0.78125 - 0.4375 = 0.34375 days; multiplying by 24 yields 8.25. This is suitable for same-day elapsed clock hours, not proof of a payroll timecard calculation: it ignores breaks, daylight-saving transitions, time zones and cross-midnight dates.

For an overnight shift, simple subtraction of fractions such as 02:00 minus 22:00 yields a negative number even when four actual hours elapsed. To handle overnight work correctly, use complete date-plus-time values (or a separately verified rollover rule), not a bare time fraction. Ensure an imported date/time column is not silently stripped of its date information. Microsoft documents how Excel ignores dates supplied within TIMEVALUE strings, but PlanMaker’s TIMEVALUE page does not explicitly guarantee that same rule. Microsoft Excel TIMEVALUE · PlanMaker data entry.

SoftMaker’s data-entry chapter explicitly documents accepted examples such as 9:30, 09:30:00 and 09:30:00 AM; this supports general time entry, not a promise that every text parsing edge case works in TIMEVALUE. For an import from another country, validate five known rows before replacing the originals. Vendor data-entry guidance.

SoftMaker’s 2021, 2024, and 2026/NX English manuals all document TIMEVALUE(Text) and the same vendor example: TIMEVALUE("10:30:00 am") → 0.4375. That is evidence of documentation in all three versions, not evidence of exact parser behavior on every OS, localized edition or mobile app. The official 2026 help covers system requirements for Windows, macOS, Linux, Android and iOS; platform-specific execution is still unverified. 2021 · 2024 · 2026 · system requirements.

Microsoft’s Excel TIMEVALUE likewise converts a recognized time string into a fraction of one day. Excel additionally documents that date information in its text argument is ignored; do not attribute that promise to PlanMaker without a SoftMaker reference or a native test. In round-trip .xlsx workbooks, verify recognized locale strings, date/time fields, displayed times and actual numeric results separately. Excel’s supported range or error messages must not be copied as PlanMaker limits without verification.

• PlanMaker TIME — build a time from numeric components
• PlanMaker DATEVALUE — convert date text instead
• PlanMaker number formatting — show a fractional day as a clock
• PlanMaker entering data — time notation and combined dates/times

Browse the PlanMaker function directory · Compare spreadsheet functions.

Evidence and validation: Accessed official vendor and Microsoft sources 2026-10-11 UTC. Only 0.4375 from the literal vendor example is specifically documented as a PlanMaker result; other expected values were independently calculated from clock fractions and require runtime parsing verification. Native PlanMaker execution was not performed.