NETWORKDAYS.INTL in ONLYOFFICE: Custom Weekend Workday Counts

=NETWORKDAYS.INTL(start_date, end_date, [weekend], [holidays])

The ONLYOFFICE function help supports dates made with DATE and a cell range containing holiday dates. Its reference is unversioned. It does not provide an edition-specific execution matrix, so this guide does not claim native results for all Desktop/online releases.

Numeric weekend choices

A seven-character mask runs Monday through Sunday, left to right. A 1 means nonworking; a 0 means working: "0000011" means Saturday/Sunday; "0000110" means Friday/Saturday; and "1000001" means Monday/Sunday. The official ONLYOFFICE article expressly calls "1111111" invalid. Treat a mask with the wrong length or nonbinary characters as a configuration error; the precise ONLYOFFICE error value still needs native confirmation.

Use the following exact cells, entering each date via the DATE function to avoid regional text-date ambiguity:

Format A2, B2 and D2:D3 as dates. The closure days are example inputs, not a claim about a particular country’s statutory calendar. Type the following formulas into other empty cells; do not paste formula strings into A2/B2/D2/D3 because those cells provide inputs.

Sanity-check the arithmetic: From Friday October 9 through Tuesday October 20 inclusive there are 12 calendar dates and four Saturday/Sunday dates, giving 8 default weekdays. Two additional Monday closures leave 6. In the Friday/Saturday-weekend case, Sunday becomes an ordinary workday; with both Monday closures excluded, the independent total is also 6. In a Monday/Sunday mask, both Monday closure dates were already nonworking, so adding them to the holiday list changes nothing.

Validation classification: the table values are outputs of a separately written Python datetime weekday model , not native ONLYOFFICE observations. Counting both endpoints is an independently modelled spreadsheet convention; the concise ONLYOFFICE reference does not separately describe every endpoint case. Confirm the one-day examples before relying on them.

Place a valid weekend code in E2 (e.g., 7) and all company closures in D2:D3. The parameterized formula is:

=NETWORKDAYS.INTL(A2,B2,$E$2,$D$2:$D$3)

Expected with E2=7: 6. This allows a single worksheet to serve different departments. A different business with only Sunday off could set E2 to 11 and would get an independently expected 8 with the same two Monday closures. Confirm dates in D2:D3 are genuine spreadsheet dates, not text strings that merely look like dates. If you fill the formula down, $ fixes the closure list; adjust the absolute references when your closure table grows.

To calculate the fraction of active days in the complete 12-day reporting interval, use:

=NETWORKDAYS.INTL(A2,B2,7,$D$2:$D$3)/(B2-A2+1)

The independent ratio is 6/12 = 0.5, so a percentage-formatted result would show 50%. This is an operations-planning ratio, not a payroll or legal entitlement calculation. Avoid using a holiday list that includes duplicate dates to imply that the same day should be excluded twice; the official reference does not describe duplicates explicitly, so test before relying on that edge case.

• Dates appear as strings or unexpected integers: Enter dates with DATE and set a Date number format. DATEVALUE and regional text-date parsing may differ by locale; a visible 10/12/2026 is ambiguous in different regions.
• The holiday list has no effect: Check if the excluded date is already a weekend under your chosen mask. Check whether D2:D3 contain date values and whether your range was entered as the fourth argument.
• Holiday dates shift while copying: Lock the range $D$2:$D$3; maintain a verified list for the relevant calendar year.
• You counted calendar days instead of workdays: DAYS calculates a date difference; NETWORKDAYS.INTL skips selected nonworking days. In a custom schedule a Saturday may be working, so counting generic weekdays is wrong.
• Unrecognized weekend code or malformed mask: Use exactly one of the documented codes or a seven-character Monday-first bitmask. The specific native error type for all invalid inputs is untested.
• End date precedes start date: Microsoft’s Excel guide documents a negative count, but the checked ONLYOFFICE page does not specify this behaviour. Native ONLYOFFICE reverse-range output remains unverified; it is intentionally omitted from the expected-results fixtures.
• Every day marked nonworking: ONLYOFFICE explicitly says "1111111" is invalid. Microsoft’s documentation for Excel NETWORKDAYS.INTL describes it as returning zero; this is a documentation-level divergence, not proof of an implementation difference.
• Filtered rows, blank holiday entries, invalid dates and 1904-date-system workbooks: These cases are not resolved by the concise official function reference. Test the target edition and its date-system setting before using this calculation for production deadlines.

The ONLYOFFICE NETWORKDAYS reference accepts start_date, end_date and optional holidays, without a custom weekend selector. NETWORKDAYS.INTL adds the selector and therefore moves holidays to the fourth position. The ONLYOFFICE WORKDAY.INTL reference instead moves a date by a workday offset; it does not report the number of included workdays in a date interval. These functions perform different calculations.

The Microsoft Excel NETWORKDAYS.INTL documentation lists the same argument order and weekend-code mapping. That establishes documented syntax compatibility, not full evaluation parity for imported workbooks. The all-days-weekend mask, reverse intervals, edge cases, locale behaviour and Desktop-vs-online releases require native ONLYOFFICE comparison.

The ONLYOFFICE Spreadsheet Editor function catalogue includes NETWORKDAYS.INTL. The Formula tab documentation illustrates the online and Desktop interfaces. Neither source is a definitive version-by-version feature matrix. As of 2026-10-13, the syntax above is reference-checked for the current English, unversioned documentation, not executed in ONLYOFFICE Desktop Editors or web Docs. Native Desktop/web execution, localized input, endpoint behavior and date-system boundaries remain untested. Verify these cases in the installed editor before relying on them.

Source trail (accessed 2026-10-13): function definition / weekend codes / seven-character mask; related workday function; function catalog and formula entry; Excel syntax comparator.