Audit Date Systems Before Transferring Calendar Values in ONLYOFFICE

A date’s calendar meaning, its numeric storage and its visible format are separate checks. When dates move between workbooks, do not repair an apparent shift by randomly changing the date system or adding a fixed number to every value.

This workflow audits a transfer with explicit year/month/day inputs. It complements the DATE function reference and CSV date import guide; it is not another text-parsing recipe.

Preserve the original and record settings

Work on copies containing only synthetic data until the cause is clear. Record the source and destination editor builds, file formats and their current date-system setting. In the documented interface, open File → Advanced Settings and inspect Use 1904 date system in the calculation settings. Record its state without changing it in the original.

The advanced-settings reference describes the optional January 1, 1904 starting point and separately documents Region and formula-language settings. A display convention and a date-system selection are not interchangeable. This article does not establish whether a particular build preserves a setting across every save format or changes other open workbooks.

For a controlled comparison, close unrelated workbooks and use two disposable local files. Keep each file’s recorded setting unchanged for the main test. If you deliberately test a different setting, do so only in an empty disposable file, apply it there, and inspect its state again after reopening. Restore your original working configuration when finished.

Build a calendar control table

In the source copy, enter numeric components rather than ambiguous strings such as 01/02/2026:

Row	A: Year	B: Month	C: Day	Expected calendar date
2	2026	10	21	October 21, 2026
3	2028	2	28	February 28, 2028
4	2028	3	1	March 1, 2028

Enter =DATE(A2,B2,C2) in D2 and fill through D4. The official DATE syntax uses year, month and day arguments. Format D2:D4 as a date.

Use E2 =YEAR(D2), F2 =MONTH(D2) and G2 =DAY(D2), then fill down. Those numeric components should reproduce columns A:C. In D6 enter =D4-D3 and format D6 as Number. The independently calculated interval is 2 days, because 2028 includes February 29. These are expected calendar checks, not observed ONLYOFFICE output.

Set H2 to =D2 and fill to H4. Apply Number with zero decimal places to H2:H4 so you can record the underlying date values actually returned by this file. The number-format help explains how to choose a display format. Keep D2:D4 date-formatted alongside the numeric view. Do not replace D’s formulas or infer that H’s integers have universal calendar meanings.

Transfer components and audit a literal separately

In the destination copy, enter the same A:C control table and recreate the DATE/component/interval formulas. Compare the resulting calendar components with the expected table before importing any production data. Both the source and destination should represent the intended dates, even if their recorded serials differ.

For a separate diagnostic, copy down the source’s displayed H2 integer as a written number, then manually type that integer into an empty destination J2. This deliberate literal test avoids making assumptions about a clipboard operation that might convert dates. Apply a date format to J2 and use K2 =YEAR(J2), L2 =MONTH(J2) and M2 =DAY(J2).

Compare K2:M2 with 2026, 10, 21. A mismatch means that transferring that raw number did not preserve the intended calendar date under these settings. A match is only this one control, not proof that every original date, time, historical date or export behaves identically. Record both outcomes rather than changing the destination settings until the example happens to look right.

The safer controlled transfer in this exercise is the explicit calendar components plus DATE reconstruction. Whether that is appropriate for a real dataset depends on its meaning: a date-time with a fractional day, text timestamp or historical date needs its own specification. This fixture contains dates only and does not validate time zones.

Mutate, reset and reopen

Change source C2 from 21 to 22. Source D2 and E2:G2 should now represent October 22, 2026. The separately reconstructed destination remains October 21 because this is not a live link. That difference confirms that the files are independent rather than proving a conversion defect.

Restore source C2 to 21. Verify both original component tables, the 2-day interval and the recorded settings. Save each copy under distinct names, close and reopen them, and repeat the checks before trusting a production transfer. No persistence or transfer behavior was natively executed for this guide.

Troubleshooting boundaries

If D shows an unexpected day/month order but E:G are correct, investigate display formatting or region. If E:G themselves are wrong, investigate the input values, formula, stored number and date system. If a cell is text rather than a numeric date, date-system changes are not a text-import repair.

Do not bulk-add a guessed offset: that can corrupt dates already correct, formulas, mixed date systems and time components. Preserve the original, identify a consistent affected subset and validate any approved correction against independent known dates. A correct-looking date on one row is not sufficient.

Version and verification scope

Checked October 21, 2026 against rolling official help, using free ONLYOFFICE Desktop Editors 10.0.0 as the English Windows/Linux local-file documentation baseline. See the desktop product overview and 10.0.0 release history. Expected calendar components and leap-day arithmetic were independently checked; they are not a native application transcript. No screenshot, universal serial offset, automatic conversion, setting-persistence, mobile, hosted or receiving-program parity is claimed.