Zoho Sheet BESSELK Function: Orders, Controls and Numerical Checks

Zoho’s official BESSELK entry was retrieved on October 15, 2026. The entry documents the rolling web service; it does not establish the first introduction release or last functioning version. Both historical endpoints are unknown, and mobile/offline parity is unverified. The calculated expectations here are independent reference values, not captured native Zoho results.

BESSELK(x; n)

Both arguments are required. x is the evaluation point and n is the order. Zoho’s argument description asks for n greater than zero, while its error list specifically names n below zero. The zero-order boundary is therefore not fully resolved by this reference. Use positive integer orders in this guide; no truncation rule for arbitrary fractional n is assumed.

Zoho also asks for x greater than zero. Its error list names negative x, leaving the exact native zero-input error unspecified. All working examples below keep x strictly positive. A mathematical continuation to other arguments is not evidence that this worksheet function supports it.

“Modified” refers to the Bessel family, not to a setting that changes the entered argument into a text complex number. Zoho’s own examples use ordinary numeric x. Do not pass a string such as “2i” merely because the help relates this family to imaginary arguments.

Zoho additionally prints BESSELK(5;1.1) as 0.004044613. That agrees with mathematical order 1, approximately 0.004044613, rather than genuine order 1.1, approximately 0.004122838. This is a documented example, not proof of a general fractional-order algorithm. The reproducible worksheet deliberately uses integers so that distinction cannot change its intended meaning.

These are the vendor’s explicit argument pairs, evaluated independently. Some final displayed digits differ slightly from the help’s approximations; the table gives the independent values rather than treating the vendor’s last digit as an exact numerical contract. More displayed digits here do not certify Zoho’s accuracy over every input range.

Create BesselValues with x in A1, Order in B1 and Result in C1. Enter the six rows below and fill C2 =BESSELK(A2;B2) through C7. The table changes x and n explicitly; do not confuse an increase in order with an increase in the evaluation point.

In a copy change A4 from 2 to 2.5, leaving B4 equal to 1. C4 becomes approximately 0.073890816. The other rows do not change. Display at least nine decimal places for these controls; a coarse number format can hide a meaningful difference.

At x=2 and central order n=2, evaluate orders 1,2,3. The modified-family recurrence uses a difference, whose direction matters. Use this direct formula:

=BESSELK(2;3)-BESSELK(2;1)-2*BESSELK(2;2)

The mathematical residual is zero, from K₃(2)−K₁(2)=2K₂(2). In a spreadsheet, inspect a small numerical residual rather than demanding exact floating-point equality. The identity is supported by the NIST recurrence reference; it does not verify Zoho’s implementation or establish a universal tolerance.

For a supplied model proportional to K₁(2r), normalize the profile at r=1. Put 0.5,1,1.5,2 in F2:F5 and fill G2 =BESSELK(2*F2;1)/BESSELK(2;1) through G5.

The independent ratios are 4.303460017, 1.000000000, 0.287106695, 0.089253353. The r=1 row equals one by construction. The profile decays over these sample points. This is an explicitly chosen mathematical model; BESSELK does not determine whether it fits a physical system, which boundary condition is appropriate, or whether r and the scale factor use compatible units.

Zoho documents #NUM! for negative n, and for negative x. The zero-order ambiguity noted above is kept separate from those explicit error rules. The shared glossary also mentions invalid type, name and reference errors without specifying all blank, text or array coercions.

If the sign, magnitude or scale seems wrong, check x versus n, the selected family, and whether a displayed zero is only rounding. Modified functions can become very large or very small as x grows; no overflow or underflow threshold was verified. Mathematical reference calculations do not establish platform parity or a guaranteed number of significant digits in Zoho.