Can I Spreadsheet?
← All functions

SUMX2MY2

Quirk found

Category: Math and trigonometry · Last tested 2026-09-01

Real compatibility results for the SUMX2MY2 function: executed in Excel for the web, Google Sheets and LibreOffice Calc, with desktop Excel behavior from Microsoft’s official documentation (we do not run desktop Excel — Excel for the web is a different application and is executed separately). Syntax and links to that documentation are below.

Support matrix

EngineDocumentedLive-testedVerdict
Excel (desktop)Yes No — documented only n/a
Excel for the web— Yes (recalc, 2026-09-01) Supported, behaves as documented
Google SheetsYes Yes (Drive import, 2026-08-31) Supported, behaves as documented
LibreOffice CalcYes Yes (25.8.7.3, 2026-08-31) Quirk found

LibreOffice version history

We executed the same test cases under each LibreOffice release to show exactly when SUMX2MY2’s support changed — not documentation claims, real results.

LibreOffice versionVerdictTested
24.2.0.3 Quirk found 2026-08-31
24.8.7.2 Quirk found 2026-08-31
25.2.0.3 Quirk found 2026-08-31
25.8.7.3 Quirk found 2026-08-31

Why isn't SUMX2MY2 working in LibreOffice?

SUMX2MY2 exists in LibreOffice 25.8.7.3, but it is not a drop-in match for Excel — our executed tests found real behavioral differences (detailed in the test results on this page). If a formula that works in Excel or Google Sheets misbehaves in LibreOffice, compare your usage against the failing cases above before assuming your data is wrong.

Discovered quirks

Executed test cases

Excel for the web (executed 2026-09-01 via OneDrive recalculation)

These values come from Excel for the web, not from desktop Excel. They are two different implementations of the calculation engine, and this run measured only the web one: the corpus was uploaded to OneDrive as .xlsx, recalculated by Excel for the web on open, and downloaded again for readback. Excel for the web is a rolling service with no pinnable version, so the run is identified by its date. Where a value here disagrees with the Expected column — which is Microsoft’s documentation of the desktop product — we cannot tell you whether the web engine diverges from the desktop one or the documentation is wrong about both, because we do not run desktop Excel.

FormulaDescriptionResultExpectedVerdict
=SUMX2MY2({2,3,9,1,8,7,5},{6,5,11,7,5,4,4}) Microsoft's second documented row, which passes the data as array constants -55 -55
Provenance

Microsoft publishes =SUMX2MY2({2, 3, 9, 1, 8, 7, 5}, {6, 5, 11, 7, 5, 4, 4}) = -55. DERIVATION in exact integer arithmetic: sum of x^2 = 4+9+81+1+64+49+25 = 233; sum of y^2 = 36+25+121+49+25+16+16 = 288; 233 - 288 = -55. THIS ROW, NOT THE RANGE ROW ABOVE IT, IS THE ONE THAT REPRODUCES THE PUBLISHED ANSWER -- see SUMX2MY2_published_range_is_off_by_one_row. Microsoft's page was read live on 2026-08-31 at https://support.microsoft.com/en-us/excel/functions/sumx2my2-function. FETCH NOTE FOR THIS BATCH: batch F recorded every /en-us/office/<name>-function-<guid> URL returning Microsoft's 'Sorry, the page you're looking for can't be found' body; today BOTH paths serve the article again -- the GUID form redirects to /en-us/excel/functions/<slug>-function -- and every page cited in this batch came back complete (217-223 KB) in one or two attempts, with no 87 KB stub responses. Nothing here is sourced from a search snippet or a mirror.

 Matched
=SUMX2MY2(A3:A9,B3:B9) Microsoft's first documented row over the range where its own data actually sits -55 -55
Provenance

Microsoft's first example row publishes =SUMX2MY2(A2:A8,B2:B8) = -55, but its data table puts the seven pairs in ROWS 3 THROUGH 9 (row 1 is the word "Data", row 2 is the column headers "First array" and "Second array"). The corrected range A3:A9/B3:B9 -- which is exactly the range the SUMX2PY2 and SUMXMY2 pages publish over an IDENTICAL data table -- gives the published -55. Asserted here in the corrected form so that a failure means the engine is wrong rather than the citation.

 Matched
=SUMX2MY2(A2:A8,B2:B8) Microsoft's published range verbatim, which does NOT produce Microsoft's published result -64 -64
Provenance

A WRONG PUBLISHED FIGURE, RECORDED RATHER THAN QUIETLY CORRECTED. Microsoft publishes =SUMX2MY2(A2:A8,B2:B8) = -55 on a data table whose numbers start in row 3, so the published range takes in the text header row and only the FIRST SIX numeric pairs. Text is ignored per the page's own Remarks ("If an array or reference argument contains text, logical values, or empty cells, those values are ignored"), leaving x = 2,3,9,1,8,7 and y = 6,5,11,7,5,4: sum x^2 = 4+9+81+1+64+49 = 208, sum y^2 = 36+25+121+49+25+16 = 272, difference -64. So the page's own formula returns -64, not the -55 it prints beside it. The error is a one-row citation slip and nothing more -- its two sibling pages, SUMX2PY2 and SUMXMY2, publish A3:A9/B3:B9 over a byte-identical data table, and the array-constant row on this same page returns the correct -55. This case asserts what the published formula actually computes, and would catch an engine that silently included the header text as a zero (which would give 208+0 vs 272+0, the same -64 here, so the case is a citation record rather than a discriminator).

 Matched
=SUMX2MY2({1,2,3},{1,2}) Arrays of different lengths, which the page assigns an error code #N/A #N/A
Provenance

The Remarks publish: "If array_x and array_y have a different number of values, the SUMX2MY2 function returns the #N/A error value."

 Matched
=SUMX2MY2({2,3,9},{6,5,11})-(SUMSQ(2,3,9)-SUMSQ(6,5,11)) The definition checked against the engine's own SUMSQ, with no constant from us 0 0
Provenance

SUMX2MY2(x,y) = SUMSQ(x) - SUMSQ(y) by definition. Asserting the difference is zero makes the engine check the function against its own sum-of-squares, which is sharper than the published integer: it fails for an engine that squared the difference instead of differencing the squares (that is SUMXMY2, and would give 16+4+4 = 24 here, not -88).

 Matched

Google Sheets (executed 2026-08-31 via Drive import)

Google Sheets is a rolling service with no pinnable version, so this run is identified by its date. The corpus was imported to Drive as .xlsx, recalculated by Sheets, and exported back for readback.

FormulaDescriptionResultExpectedVerdict
=SUMX2MY2({2,3,9,1,8,7,5},{6,5,11,7,5,4,4}) Microsoft's second documented row, which passes the data as array constants -55 -55
Provenance

Microsoft publishes =SUMX2MY2({2, 3, 9, 1, 8, 7, 5}, {6, 5, 11, 7, 5, 4, 4}) = -55. DERIVATION in exact integer arithmetic: sum of x^2 = 4+9+81+1+64+49+25 = 233; sum of y^2 = 36+25+121+49+25+16+16 = 288; 233 - 288 = -55. THIS ROW, NOT THE RANGE ROW ABOVE IT, IS THE ONE THAT REPRODUCES THE PUBLISHED ANSWER -- see SUMX2MY2_published_range_is_off_by_one_row. Microsoft's page was read live on 2026-08-31 at https://support.microsoft.com/en-us/excel/functions/sumx2my2-function. FETCH NOTE FOR THIS BATCH: batch F recorded every /en-us/office/<name>-function-<guid> URL returning Microsoft's 'Sorry, the page you're looking for can't be found' body; today BOTH paths serve the article again -- the GUID form redirects to /en-us/excel/functions/<slug>-function -- and every page cited in this batch came back complete (217-223 KB) in one or two attempts, with no 87 KB stub responses. Nothing here is sourced from a search snippet or a mirror.

 Matched
=SUMX2MY2(A3:A9,B3:B9) Microsoft's first documented row over the range where its own data actually sits -55 -55
Provenance

Microsoft's first example row publishes =SUMX2MY2(A2:A8,B2:B8) = -55, but its data table puts the seven pairs in ROWS 3 THROUGH 9 (row 1 is the word "Data", row 2 is the column headers "First array" and "Second array"). The corrected range A3:A9/B3:B9 -- which is exactly the range the SUMX2PY2 and SUMXMY2 pages publish over an IDENTICAL data table -- gives the published -55. Asserted here in the corrected form so that a failure means the engine is wrong rather than the citation.

 Matched
=SUMX2MY2(A2:A8,B2:B8) Microsoft's published range verbatim, which does NOT produce Microsoft's published result -64 -64
Provenance

A WRONG PUBLISHED FIGURE, RECORDED RATHER THAN QUIETLY CORRECTED. Microsoft publishes =SUMX2MY2(A2:A8,B2:B8) = -55 on a data table whose numbers start in row 3, so the published range takes in the text header row and only the FIRST SIX numeric pairs. Text is ignored per the page's own Remarks ("If an array or reference argument contains text, logical values, or empty cells, those values are ignored"), leaving x = 2,3,9,1,8,7 and y = 6,5,11,7,5,4: sum x^2 = 4+9+81+1+64+49 = 208, sum y^2 = 36+25+121+49+25+16 = 272, difference -64. So the page's own formula returns -64, not the -55 it prints beside it. The error is a one-row citation slip and nothing more -- its two sibling pages, SUMX2PY2 and SUMXMY2, publish A3:A9/B3:B9 over a byte-identical data table, and the array-constant row on this same page returns the correct -55. This case asserts what the published formula actually computes, and would catch an engine that silently included the header text as a zero (which would give 208+0 vs 272+0, the same -64 here, so the case is a citation record rather than a discriminator).

 Matched
=SUMX2MY2({1,2,3},{1,2}) Arrays of different lengths, which the page assigns an error code #N/A #N/A
Provenance

The Remarks publish: "If array_x and array_y have a different number of values, the SUMX2MY2 function returns the #N/A error value."

 Matched
=SUMX2MY2({2,3,9},{6,5,11})-(SUMSQ(2,3,9)-SUMSQ(6,5,11)) The definition checked against the engine's own SUMSQ, with no constant from us 0 0
Provenance

SUMX2MY2(x,y) = SUMSQ(x) - SUMSQ(y) by definition. Asserting the difference is zero makes the engine check the function against its own sum-of-squares, which is sharper than the published integer: it fails for an engine that squared the difference instead of differencing the squares (that is SUMXMY2, and would give 16+4+4 = 24 here, not -88).

 Matched

LibreOffice Calc 25.8.7.3 (tested 2026-08-31)

FormulaDescriptionResultExpectedVerdict
=SUMX2MY2({2,3,9,1,8,7,5},{6,5,11,7,5,4,4}) Microsoft's second documented row, which passes the data as array constants -55 -55
Provenance

Microsoft publishes =SUMX2MY2({2, 3, 9, 1, 8, 7, 5}, {6, 5, 11, 7, 5, 4, 4}) = -55. DERIVATION in exact integer arithmetic: sum of x^2 = 4+9+81+1+64+49+25 = 233; sum of y^2 = 36+25+121+49+25+16+16 = 288; 233 - 288 = -55. THIS ROW, NOT THE RANGE ROW ABOVE IT, IS THE ONE THAT REPRODUCES THE PUBLISHED ANSWER -- see SUMX2MY2_published_range_is_off_by_one_row. Microsoft's page was read live on 2026-08-31 at https://support.microsoft.com/en-us/excel/functions/sumx2my2-function. FETCH NOTE FOR THIS BATCH: batch F recorded every /en-us/office/<name>-function-<guid> URL returning Microsoft's 'Sorry, the page you're looking for can't be found' body; today BOTH paths serve the article again -- the GUID form redirects to /en-us/excel/functions/<slug>-function -- and every page cited in this batch came back complete (217-223 KB) in one or two attempts, with no 87 KB stub responses. Nothing here is sourced from a search snippet or a mirror.

 Matched
=SUMX2MY2(A3:A9,B3:B9) Microsoft's first documented row over the range where its own data actually sits -55 -55
Provenance

Microsoft's first example row publishes =SUMX2MY2(A2:A8,B2:B8) = -55, but its data table puts the seven pairs in ROWS 3 THROUGH 9 (row 1 is the word "Data", row 2 is the column headers "First array" and "Second array"). The corrected range A3:A9/B3:B9 -- which is exactly the range the SUMX2PY2 and SUMXMY2 pages publish over an IDENTICAL data table -- gives the published -55. Asserted here in the corrected form so that a failure means the engine is wrong rather than the citation.

 Matched
=SUMX2MY2(A2:A8,B2:B8) Microsoft's published range verbatim, which does NOT produce Microsoft's published result -64 -64
Provenance

A WRONG PUBLISHED FIGURE, RECORDED RATHER THAN QUIETLY CORRECTED. Microsoft publishes =SUMX2MY2(A2:A8,B2:B8) = -55 on a data table whose numbers start in row 3, so the published range takes in the text header row and only the FIRST SIX numeric pairs. Text is ignored per the page's own Remarks ("If an array or reference argument contains text, logical values, or empty cells, those values are ignored"), leaving x = 2,3,9,1,8,7 and y = 6,5,11,7,5,4: sum x^2 = 4+9+81+1+64+49 = 208, sum y^2 = 36+25+121+49+25+16 = 272, difference -64. So the page's own formula returns -64, not the -55 it prints beside it. The error is a one-row citation slip and nothing more -- its two sibling pages, SUMX2PY2 and SUMXMY2, publish A3:A9/B3:B9 over a byte-identical data table, and the array-constant row on this same page returns the correct -55. This case asserts what the published formula actually computes, and would catch an engine that silently included the header text as a zero (which would give 208+0 vs 272+0, the same -64 here, so the case is a citation record rather than a discriminator).

 Matched
=SUMX2MY2({1,2,3},{1,2}) Arrays of different lengths, which the page assigns an error code #VALUE! #N/A
Provenance

The Remarks publish: "If array_x and array_y have a different number of values, the SUMX2MY2 function returns the #N/A error value."

 Mismatch
=SUMX2MY2({2,3,9},{6,5,11})-(SUMSQ(2,3,9)-SUMSQ(6,5,11)) The definition checked against the engine's own SUMSQ, with no constant from us 0 0
Provenance

SUMX2MY2(x,y) = SUMSQ(x) - SUMSQ(y) by definition. Asserting the difference is zero makes the engine check the function against its own sum-of-squares, which is sharper than the published integer: it fails for an engine that squared the difference instead of differencing the squares (that is SUMXMY2, and would give 16+4+4 = 24 here, not -88).

 Matched

Docs & syntax

Where SUMX2MY2 behaves differently