NETWORKDAYS_EXCEL2003 Function (LibreOffice Calc)

• Introduced: First calculation release not established. In the 5.1 source line, NETWORKDAYS_ADD became NETWORKDAYS_XCL, then NETWORKDAYS_EXCEL2003.
• Supported in: LibreOffice 26.8.1.1. No final supported release has been established.
• Scope: Desktop Calc; compatibility function, retained rather than retired.
• Checked: October 14, 2026. Pinned source and independent examples checked. This compatibility name was not natively executed; tests of other imported names are separate.

This spelling is retained for older Excel interoperability. The official function page recommends NETWORKDAYS or NETWORKDAYS.INTL for new documents because those entries provide more flexible conventions. The compatibility function has a fixed Saturday/Sunday weekend and an optional holiday argument. It does not take the fourth workweek argument supported by LibreOffice’s current NETWORKDAYS.

The result is a count of eligible calendar dates. It is not an elapsed-hours calculation, a timezone conversion, or a count of shifts worked. Supplying a holiday list does not make the function aware of any country’s official holiday calendar; the workbook author chooses the excluded dates.

=NETWORKDAYS_EXCEL2003(StartDate; EndDate [; Holidays])

StartDate and EndDate are required. Holidays is optional and can be a date or a range of dates to exclude. For a start date in A2, end date in B2 and holiday list in H2:H5, use:

=NETWORKDAYS_EXCEL2003(A2;B2;$H$2:$H$5)

The fixed holiday range stays in place when the formula is filled down. Put genuine numeric dates in H2:H5, not labels such as “Christmas.” Use DATE expressions when entering examples and format the result as a number. Formatting a number as a date does not change its underlying meaning.

For the last example, create an Inputs sheet with =DATE(2026;12;25) in A1 and =DATE(2027;1;1) in A2. The other rows are self-contained. These are independently counted reference results.

The same working start and end date returns 1. A Saturday or Sunday used as both endpoints returns 0. Reversing the dates makes the count negative; the source loop includes both endpoints in either direction. This sign is useful when auditing reversed input dates, but it should not silently stand in for a valid positive task duration.

A project runs from Monday 2026-10-12 through Friday 2026-10-16. Put those dates in A2 and B2. Without holidays the count is 5. If Wednesday 2026-10-14 is excluded, place that date in H2 and calculate =NETWORKDAYS_EXCEL2003(A2;B2;$H$2): the result is 4.

With 7.5 available hours per eligible day in D2, =C2*D2 gives 30 scheduled hours when C2 contains the four-day count. This is a simple capacity model, not a timesheet: partial days, different daily schedules, leave fractions and overnight work need additional inputs.

Inclusive endpoints matter when dividing a schedule into adjacent periods. For Monday through Wednesday and Wednesday through Friday, the two counts are 3 and 3, so adding them gives 6 even though the full Monday-to-Friday interval has only 5 workdays. Wednesday was counted twice.

For consecutive nonoverlapping windows, end the first period on Tuesday and start the second on Wednesday, or derive the next start date from the previous end plus one calendar day. Then count each window with the same holiday list. Do not add one workday blindly: the boundary adjustment is about date inclusion, while weekend/holiday filtering belongs to the function.

For the year-end example above, 2026-12-24 through 2027-01-04 contains eight weekdays before exclusions. Removing 2026-12-25 and 2027-01-01 leaves 6. A holiday already falling on a weekend does not subtract an extra working day. Repeated entries for the same holiday are de-duplicated by the sorted holiday collection in the release implementation.

Validate that both input cells hold the intended dates. Empty cells or text may be converted before the add-in receives them, and such conversions are not part of the worked examples. Use explicit numeric dates when diagnosing a discrepancy; a locale-formatted string can be interpreted differently on another installation.

The fixed Monday-Friday calendar is the main limitation. A Friday/Saturday weekend, rotating roster or six-day week requires a different model. Use the documented NETWORKDAYS.INTL or current NETWORKDAYS contract instead of appending an unsupported argument to this function.

Files may serialize this compatibility calculation under NETWORKDAYS. Inspect the importing application’s resolved function identity and test weekend, holiday and reversed-date examples after reopening. A successful result from the current core NETWORKDAYS is useful comparison evidence but does not by itself verify NETWORKDAYS_EXCEL2003.

• Function purpose and exact three-argument contract
• Pinned evaluator: inclusive endpoints, fixed weekend and holiday exclusion
• Rename to the compatibility suffix