AMORLINC Function (Gnumeric)

=AMORLINC(cost,purchase_date,first_period,salvage,period,rate,basis)

All seven arguments are required in the inspected Gnumeric registration, including basis. Do not assume an optional basis solely because another spreadsheet permits omission.

• Cost is the initial asset value.
• Purchase_date is a real spreadsheet date, preferably constructed with DATE.
• First_period is the date ending the initial prorated period.
• Salvage is the residual value after depreciation.
• Period is the requested period number: 0 selects the initial prorated period; 1 selects the next full period. Use a nonnegative integer.
• Rate is the annual depreciation fraction; 0.2 means 20%.
• Basis chooses the day count: 0 US 30/360, 1 actual/actual, 2 actual/360, 3 actual/365, or 4 European 30/360.

Use positive cost and rate, a plausible salvage value between zero and cost, and ordered dates. The implementation does not comprehensively validate every economically meaningful relationship.

For cost 1000, purchase 1 July 2024, first period ending 1 January 2025, salvage 100, annual rate 20% and basis 0:

=AMORLINC(1000,DATE(2024,7,1),DATE(2025,1,1),100,0,0.2,0)

The result is 100. The 30/360 year fraction is 0.5, so first-period depreciation is 1000×0.2×0.5. Changing period from 0 to 1, 2, 3 or 4 returns 200 in each case. Period 5 returns 0. Total depreciation is 100+4×200 = 900, leaving the residual value 100.

This example deliberately uses dates away from month ends, making the day-count arithmetic easy to inspect. It does not establish that all bases give identical first-period fractions across leap years or irregular dates.

Put periods 0 through 5 in A1:A6. In B1 enter =AMORLINC(1000,DATE(2024,7,1),DATE(2025,1,1),100,A1,0.2,0) and fill down. In C1 enter =1000-SUM($B$1:B1) and fill down to show remaining book value: 900, 700, 500, 300, 100, 100.

The final depreciation payment may be a partial amount for other cost, salvage or rate combinations. Check the sum of the schedule against cost minus salvage rather than assuming an identical charge in every period. The prorated first period is distinct from the final residual adjustment.

Negative rate and basis 9 each returned #NUM! in the bounded native tests. The callback converts period to an integer; do not use fractional periods as a substitute for proration. Use DATE rather than a locale-sensitive text date or an expression such as 7/1/2024, which a formula may interpret as arithmetic.

Zero rate was deliberately not executed: the inspected helper divides by cost×rate when deriving the number of full periods. Model a no-depreciation case separately rather than relying on that boundary. Date order, salvage plausibility and accounting suitability require your own checks even when a formula returns a number.

Official NEWS lists AMORLINC among functions added in Gnumeric 1.1.6. Native tests and the retained financial implementation inspected here use 1.12.57. No retirement or last functioning release is established. Other spreadsheets can differ in optional arguments and boundary validation, so compare exact syntax and results before exchanging a depreciation model.

• Gnumeric function implementation and help
• Official function catalog
• Gnumeric release history
• Financial calculation helpers

On 17 October 2026, Gnumeric 1.12.57 ssconvert recalculated 8 bounded AMORLINC fixture records in C.UTF-8. Saved input formulas and output cells were independently read back and matched to the recorded evidence. Recorded results agree with the independent arithmetic or special-function reference calculations to the documented numerical tolerance. This is engine evidence, not a GUI test or screenshot. Derived worksheet checks are mathematical examples unless separately recorded in the fixture. No execution of 1.12.62 or untested extreme inputs is claimed.

• AMORDEGRC
• SLN
• DATE