ACCRINT Function in ONLYOFFICE Spreadsheet Editor
Calculate periodic-security accrued interest in ONLYOFFICE with explicit par, coupon-period fractions and documented method limitations.
Verification status: See the evidence and test scope described in this guide. How formula examples are checked
Quick answer: =ACCRINT(DATE(2025,1,1),DATE(2025,7,1),DATE(2025,4,1),0.06,1000,2,0,TRUE) is independently expected to return 15.
Availability and evidence scope
- Introduction: The original introduction release is not established by the sources checked.
- Current documentation: Listed in ONLYOFFICE’s unversioned official function help, checked October 18, 2026.
- Source scope: Inspected in official SDKJS tag v10.0.0.169, commit
3679e0375a758d7dc59d31337a45461be3525ed8. This is source inspection, not proof that every deployed editor contains identical code. - Retired or deprecated: Neither status is established; the function is documented and implemented in the inspected source.
- Testing: Examples are independently calculated or explicitly source-derived. They have not been tested in the ONLYOFFICE application or calculation engine. No native screenshot or workbook-import compatibility is claimed.
Formulas use commas and English names. If your regional settings use semicolons, replace argument separators outside quoted text. Use DATE to create financial dates rather than ambiguous text dates.
Purpose and syntax
ACCRINT calculates accrued coupon interest for a security that pays periodically. Its result is a currency amount on the supplied face value, not an annual yield or the full price of the security.
=ACCRINT(issue, first_interest, settlement, rate, par, frequency, [basis], [calc_method])
| Argument | Meaning and implementation default |
|---|---|
| issue | Security’s issue date |
| first_interest | First coupon date, anchoring the coupon schedule |
| settlement | Date through which interest is accrued |
| rate | Positive annual coupon rate, e.g. 0.06 for 6% |
| par | Positive face value; supply it explicitly |
| frequency | Coupon payments per year: 1, 2 or 4 |
| basis | Optional day-count code; default 0 |
| calc_method | Optional logical selector; default TRUE |
The registered interface requires six through eight argument positions. Official help describes par as optional with value 1000, and the implementation supplies 1000 for an empty par slot. That does not mean a five-argument formula can safely omit the position and shift frequency left. Use an explicit 1000 or your actual face value, as all examples do.
| Code | Day-count convention |
|---|---|
| 0 | US/NASD 30/360; default when basis is omitted |
| 1 | Actual/actual |
| 2 | Actual/360 |
| 3 | Actual/365 |
| 4 | European 30/360 |
Step-by-step: interest before the first coupon
On a fresh sheet enter the following values:
| Cell | Entry |
|---|---|
| A2 | =DATE(2025,1,1) |
| B2 | =DATE(2025,7,1) |
| C2 | =DATE(2025,4,1) |
| D2 | 0.06 |
| E2 | 1000 |
| F2 | 2 |
In G2 enter =ACCRINT(A2,B2,C2,D2,E2,F2,0,TRUE). Format G2 as a number or currency. The expected result is 15, not 15%.
The annual coupon is 1000 × 0.06 = 60. With two payments per year, a coupon is 30. Under 30/360, January 1 to April 1 is 90 days of a 180-day coupon period. The accrued amount is therefore 30 × 90/180 = 15. Both the coupon size and the fraction of its period are visible in this calculation.
For a holding with face value 25,000, keep the dates and rates unchanged and use par 25000. Interest scales to 375. This scaling does not incorporate fees or a purchase-price premium: par is the contractual face amount, not automatically the amount paid.
Advanced comparison: actual-day bases
For the same dates, actual elapsed days are 90 and the full January-to-July coupon interval contains 181 days. With basis 1, the independent expectation is 30 × 90/181, or 14.9171270718. With basis 3, the coupon-period denominator is 365/2 = 182.5, giving 30 × 90/182.5 = 14.7945205479.
These are different questions about the same dates. Replacing every denominator with 180 or every year with 365 would erase the contract’s day-count convention. Around leap days and month ends, validate the relevant coupon boundaries rather than assuming a simple elapsed-days formula always reproduces ACCRINT.
calc_method: documentation and source disagree in a later-period case
Official help says TRUE accrues from issue, while FALSE accrues from first_interest when settlement is later than that first coupon. However, the inspected source can produce a different result from that stated FALSE rule.
For issue January 1, first interest July 1 and settlement October 1, 2025, at 6%, par 1000, frequency 2 and basis 0, an independent trace of the FALSE branch starts from the previous January coupon boundary and gives 45. The help’s first-interest-to-settlement interpretation would give 15. The TRUE branch also traces to 45 for this example.
This is a source/help discrepancy, not a native result or a validated alternative convention. Do not rely on FALSE for post-first-coupon accrual without verifying the exact editor build and reconciling the contractual schedule. The main worked examples stay before the first coupon, where that disputed branch is not needed. A plausible output is not evidence that the requested accrual interval was used.
Errors and input checks
The source rejects nonpositive rate or par, issue on or after settlement, unsupported frequency and basis outside 0–4 with its numeric-error category, conventionally #NUM!. The comparison table’s frequency 3 is such a source-predicted error. Boolean values in several date/numeric positions are explicitly rejected as value-type errors; do not use TRUE as a substitute for a numeric date or frequency.
Dates, frequency and basis are floored during processing. Enter whole dates and supported integer selectors deliberately rather than relying on fractional-input coercion. The default calc_method is TRUE, but specify it explicitly in models where the accrual interpretation matters. General blank/text/range coercions and extreme date schedules are outside the examples verified here.
Reproducible checks
The following are expected values, not application observations. Numeric examples use independent arithmetic; implementation-specific outputs and errors are source predictions. Keep enough displayed precision to distinguish rounding from a changed formula.
| Formula | Expected result |
|---|---|
=ACCRINT(DATE(2025,1,1),DATE(2025,7,1),DATE(2025,4,1),0.06,1000,2,0,TRUE) |
15 |
=ACCRINT(DATE(2025,1,1),DATE(2025,7,1),DATE(2025,4,1),0.06,1000,2,3,TRUE) |
14.794520547945206 |
=ACCRINT(DATE(2025,1,1),DATE(2025,7,1),DATE(2025,4,1),0.06,1000,2,1,TRUE) |
14.917127071823204 |
=ACCRINT(DATE(2025,1,1),DATE(2025,7,1),DATE(2025,4,1),0.06,1000,3,0,TRUE) |
#NUM! |
Compatibility and related functions
Use the exact argument order above when moving a workbook between products. Similar function names do not establish identical date calculations, validation, rounding or optional-argument handling. This guide does not certify older ONLYOFFICE releases, mobile editors or file-format round trips. The inspected definition uses the canonical name ACCRINT; no alternate user-facing name is established here.
DATE builds the input dates. YEARFRAC helps inspect annual fractions, while ROUND controls presentation rounding when your reporting policy requires it.
First-party references
- ONLYOFFICE ACCRINT help, current unversioned function reference, checked October 18, 2026.
- Official SDKJS v10.0.0.169 implementation, pinned source for argument defaults, validation and implementation details discussed above.
These formulas calculate supplied assumptions. They do not determine a security’s contractual terms, appropriate investment choice or permitted accounting/tax treatment.