If an XLSX workbook produces a different value in ONLYOFFICE Spreadsheet Editor than it does in Microsoft Excel, the useful goal is not simply to make the error disappear. The goal is to identify whether the difference comes from stale calculation results, workbook settings, regional interpretation, formula support, external data, or a genuine calculation-engine mismatch. A good fix should survive reopening the file, changing inputs, and recalculating the workbook—not merely make one cell look right once.
This guide was checked against the official ONLYOFFICE and Microsoft documentation available on October 6, 2026. The current ONLYOFFICE Docs changelog lists version 9.4.0, released May 20, 2026. Version 9.3.0, released February 25, 2026, added dynamic-array support and improved several spreadsheet behaviors, so an older ONLYOFFICE deployment can legitimately behave differently from a current one.
Before changing formulas, make a copy of the workbook and choose a small set of cells that represent the real problem: for example, a subtotal, a lookup result, a date calculation, and a final KPI. Record the formula text, the displayed result, and the underlying input values in both applications. If possible, compare the same XLSX file rather than two separately exported copies.
A useful troubleshooting result has three signs: the mismatch can be reproduced on demand, the cause can be explained without guessing, and the corrected workbook still produces the expected values after you change one or two source inputs and recalculate again.
Stale cached values can look like a formula incompatibility. In ONLYOFFICE, the Formula tab includes calculation controls that can recalculate the whole workbook or the current worksheet, according to the official Formula tab documentation. Recalculate first, save, reopen the file, and compare the critical cells again.
Excel also has Automatic and Manual workbook-calculation modes. Microsoft documents these under formula recalculation, iteration, and precision. That matters because a workbook last saved in Excel can contain values that were not freshly calculated. If a forced recalculation makes the two applications agree, the problem was likely calculation state rather than formula syntax.
A formula can be mathematically correct and still be parsed differently when regional settings do not match the workbook’s expectations. ONLYOFFICE separates formula language from regional formatting. Its Advanced Settings let you choose the formula language and region, and the editor can use decimal and thousands separators derived from the selected region or custom separators. See ONLYOFFICE Advanced Settings.
Pay special attention to numbers imported from CSV or pasted from another system. A value such as 1,234 can mean one thousand two hundred thirty-four in one convention and 1.234 in another. ONLYOFFICE’s text and CSV import documentation explicitly exposes decimal and thousands separators for imported data.
The test is simple: after aligning the region and separators, inspect a few suspect input cells. They should be recognized as numbers rather than text, dates should sort chronologically, and arithmetic should change when an input changes. If the cell content remains text-like, clean the data before rewriting the formula.
Date discrepancies of roughly four years are a strong clue that the workbook date system is mismatched. Excel supports both the 1900 and 1904 date systems. Microsoft states that the same date differs by 1,462 days between them. See Microsoft’s date-systems documentation.
ONLYOFFICE Advanced Settings include a Use 1904 date system option specifically for compatibility with older Excel for Mac workbooks. If formulas involving dates, age, tenure, or day counts disagree, compare this setting before touching the formulas themselves.
After changing the date system, recheck raw date serials as well as formatted dates. A visually plausible date is not enough; date subtraction and comparison formulas should also agree.
Circular-reference models are especially sensitive to settings. Both Excel and ONLYOFFICE support iterative calculation, where the workbook repeatedly recalculates until a threshold is reached. ONLYOFFICE documents Enable iterative calculation, Maximum iterations, and Maximum change in Advanced Settings. Excel exposes the same general concepts in its calculation options.
If a financial model, interest accrual model, or allocation sheet intentionally uses circular references, compare the maximum iteration count and acceptable change in both applications. A different stopping condition can produce a different final number even when the formulas themselves are identical.
Do not enable iteration merely to suppress a circular-reference problem you do not understand. If the workbook was not designed to iterate, locate the circular dependency instead.
ONLYOFFICE supports array formulas, including functions such as FILTER, UNIQUE, XLOOKUP, TEXTSPLIT, TAKE, DROP, HSTACK, and VSTACK, as documented in its array-formula guide. Current documentation also shows that version 9.3.0 added dynamic-array support.
If a workbook was created with newer Excel array behavior and fails on an older ONLYOFFICE installation, update ONLYOFFICE before redesigning the formula. If you cannot update, simplify the formula into helper ranges or a supported non-dynamic construction, then verify every returned row and column. This is a case where changing the approach can be safer than forcing a modern Excel pattern into an older engine.
A #NAME? result often leads people to immediately rewrite the workbook, but that can be premature. ONLYOFFICE maintains an official function list, and its current documentation includes many modern functions that older comparisons on the web may incorrectly describe as unsupported.
Use the current function list as the source of truth. If the function exists, compare its arguments, array behavior, and input types before replacing it. If the function is not documented for your installed version, then an alternative formula may be appropriate.
For lookups in particular, do not assume XLOOKUP is the problem: ONLYOFFICE documents XLOOKUP support, and recent releases have included lookup-related improvements.
Two cells can display the same characters while carrying different types internally. A numeric-looking value stored as text can affect comparisons, lookups, aggregation, and conditional formulas. This is important enough that ONLYOFFICE 9.1.0 explicitly listed improved formula logic for mixed data types in its changelog.
Check imported IDs, percentages, dates, and amounts. Remove accidental spaces, standardize decimal conventions, and convert text numbers to actual numbers where appropriate. Then recalculate. If the mismatch disappears, keep the data-cleaning step rather than embedding increasingly complicated coercion logic into every formula.
A formula may be correct while its linked source is stale. ONLYOFFICE supports references to cells in other workbooks and provides an External Links window where you can update values, change the source, or break links. The official external-links guide also notes that, in the online editor, inserting data through an external link must be supported by the integrator or document-management system.
If Excel has access to a source workbook that ONLYOFFICE cannot reach—or if the online integration does not implement the required external-link behavior—the two applications can show different values without either formula being mathematically wrong.
A strong test is to open the source workbook, confirm the referenced cells, update the link in ONLYOFFICE, and then change one source value. If the destination does not update as expected, address the link path or integration rather than the formula.
Excel can optionally calculate using displayed values instead of the full stored values. Microsoft warns that enabling Set precision as displayed permanently changes stored values to match their formatted precision. The current ONLYOFFICE Advanced Settings documentation describes date-system and iterative-calculation controls but does not document an equivalent option.
If an Excel workbook depends on that setting, do not assume another spreadsheet engine will reproduce the same result. For cross-application workbooks, explicit formulas such as ROUND, ROUNDUP, or ROUNDDOWN at the intended business rule boundary are easier to audit than relying on an application-level precision setting.
This is also a good example of a limit to “fixing” compatibility: if the workbook intentionally relies on an Excel-specific calculation option, keeping that calculation in Excel may be the safer choice.
| Symptom | Check first | Good sign after the fix | When to change approach |
|---|---|---|---|
| Values differ until the file is reopened | Force workbook recalculation and save | Results remain stable after reopen | If results still diverge after a full recalculation |
| #NAME? or formula not recognized | Current ONLYOFFICE function documentation and installed version | Function parses and changes correctly with inputs | If the required function is not supported in that version |
| Dates are about four years off | 1900 vs. 1904 date system | Date serials and date arithmetic agree | If the workbook mixes incompatible historical date assumptions |
| Results differ in circular models | Iteration count and maximum change | Both applications converge to the same tolerance | If the model depends on undocumented engine behavior |
| Lookups fail only for some rows | Mixed text/number types, spaces, and sort assumptions | Lookup results are correct across edge cases | If source data cannot be normalized reliably |
| Linked values are stale | External Links source and update status | Changing the source updates the destination | If the online integration cannot supply linked workbook data |
| Small rounding differences cascade | Excel precision settings and explicit rounding rules | Business-rule rounding is visible in formulas | If the model fundamentally depends on Excel-only workbook precision behavior |
Do not stop at “the error is gone.” Change a few representative inputs and confirm that the downstream results update in both applications. Include at least one boundary case: a zero value, a blank cell, a missing lookup key, a date near month-end, or a value that exercises rounding. If the workbook contains external links, test one linked value as well.
For business-critical workbooks, define a small reconciliation sheet with expected outputs. It can contain the source inputs, the formula under test, the expected result, and an allowed tolerance. This turns future ONLYOFFICE or Excel upgrades into a repeatable check rather than a manual visual inspection.
Compatibility has limits. If a workbook depends on an Excel-specific calculation option, unsupported automation, a proprietary external-data workflow, or a feature that behaves differently in the ONLYOFFICE version you are required to run, converting every formula may create more risk than it removes.
In that situation, use ONLYOFFICE for the parts it handles reliably and keep the critical calculation in Excel, or redesign the model around explicit, documented formulas and static data interfaces. The deciding factor should be repeatability: can you explain the result, reproduce it after reopening the file, and verify it after changing inputs? If not, the workaround is not yet robust enough.
The fastest route to a dependable fix is to diagnose in a strict order: recalculate, align locale and separators, verify the date system, match iteration settings, check version-sensitive array behavior, confirm function support, normalize data types, refresh external links, and investigate Excel precision settings. Each step removes a different class of error.
If the workbook agrees after those checks and remains stable under changed inputs, you have evidence that the fix is durable. If it still differs, reduce the problem to the smallest reproducible formula and workbook section before reporting it to ONLYOFFICE support or deciding that the calculation must remain in Excel.
Create an Outlook meeting invite, add required or optional attendees, choose a time, add Teams details, set recurrence, and check replies in new or classic Outlook.
Use Excel's Data Validation settings to set a maximum, minimum, exact length, or character range, then add clear prompts and error alerts.
Fix the Outlook “We can’t schedule the meeting” error by checking account support, refreshing Teams sign-in, and repairing the Classic Outlook add-in.
Change Office 365 menus, spelling and grammar settings, or keyboard input in desktop apps and Microsoft 365 for the web.
Learn how to auto-forward all or selected emails in Outlook 365 using Forwarding settings or Rules, plus how to stop forwarding and fix blocked external forwards.
Use Microsoft Editor in Word for Microsoft 365 to check spelling, grammar, clarity, and conciseness, review suggestions, and tune proofing settings.
Learn how to add an RSS feed to Outlook 365 in classic Outlook for Windows, find the correct feed URL, manage subscriptions, and fix common RSS issues.
Jump straight to any page in Word for Microsoft 365 with Ctrl+G or F5, relative page numbers, or the Navigation pane, with Windows and Mac shortcuts.
Learn how to add contacts to Outlook on the web, new Outlook, classic Outlook, and mobile, plus how contact syncing and CSV imports work.
Change a Word page color, add a picture background, remove either, and enable background printing on Windows or Mac with clear, current steps.
