Recurring Depreciation — entity reference

A per-asset (or per-pool) depreciation schedule that posts one period's charge at a time under the Companies Act book: either a fixed straight-line amount or a written-down-value rate applied to the reducing balance, floored at the residual value. Each run posts a balanced Depreciation journal (Dr depreciation expense / Cr accumulated depreciation), reduces CurrentWdv, adds to AccumulatedDepreciation, stamps LastRunDate and advances NextRunDate by the configured frequency. That NextRunDate advance — not a timestamp check — is what makes the schedule safe to run repeatedly: a period is never depreciated twice. A background evaluator picks up Active schedules whose NextRunDate has arrived, and the same service backs the manual PostRecurringDepreciation action. The schedule flips itself to Completed when the carrying value reaches residual or the advanced next date passes EndDate.

Fields

Field	Label	Type	Required	What it does
`AccumulatedDepreciation`	Accumulated Depreciation	Currency		Running total of everything this schedule has charged, incremented by each posting so it mirrors the credit side of the journals.
`AccumulatedDepreciationGLAccountId`	Accumulated Depreciation GL Account	Lookup → GLAccount		The contra-asset account credited by every run, forming the other leg of the two-line Depreciation journal. Like the expense account it must be set before the schedule can post at all.
`AssetName`	Asset Name	Text		Descriptive name of the asset or pool being depreciated. It is not merely cosmetic: it is embedded in the generated journal's unique name and label alongside the run date, so it is how a posted depreciation journal is traced back to the asset it belongs to.
`BranchId`	Branch	Lookup → Branch
`Cost`	Cost	Currency		Acquisition cost of the asset. It is the starting point for the carrying value rather than an input to each run: CurrentWdv should be seeded from it at setup, and the run only falls back to reading this column when the carrying value has not been populated.
`CreatedById`	Created By	Lookup → UserAccount	Yes
`CreatedDateTime`	Created Date	DateAndTime	Yes
`CurrentWdv`	Current WDV	Currency		The live carrying (written-down) value, seeded from Cost at setup and reduced by every posting. It is the base the written-down-value rate is applied to, so it drives the size of each reducing-balance charge; once it reaches the residual value the schedule marks itself Completed and further runs post nothing.
`DepreciationExpenseGLAccountId`	Depreciation Expense GL Account	Lookup → GLAccount		The profit-and-loss account debited by every run. It is mandatory in practice: the engine refuses to run the schedule and raises a validation failure if either this or the accumulated-depreciation account is missing.
`EndDate`	End Date	DateAndTime		Optional hard stop for the schedule. It is applied twice: the scheduler skips a schedule whose next run would fall beyond it, and after a posting the engine marks the schedule Completed if the newly advanced next date has passed it. Leave it null to let the schedule run until the carrying value reaches residual.
`Frequency`	Frequency	PickList		How far NextRunDate is pushed forward after each posting — Monthly, Quarterly, HalfYearly or Yearly — which makes it the cadence of the whole schedule rather than a display setting. Only the Monthly option is currently seeded as a selectable value in the first-party metadata, so the other three have to be set through data or configuration. Values: Monthly, Yearly.
`Id`	Id	Guid	Yes
`LastRunDate`	Last Run Date	DateAndTime		Stamped with the effective date of the most recent successful posting. It is written for audit and reconciliation against the generated journals; the scheduler's due test looks at NextRunDate, not at this column.
`Method`	Method	Text		Selects the arithmetic for each run: StraightLine charges the fixed PeriodAmount, while WrittenDownValue (the default) charges the current carrying value multiplied by RatePerPeriod.
`ModifiedById`	Modified By	Lookup → UserAccount	Yes
`Name`	Document Number	Text	Yes
`NextRunDate`	Next Run Date	DateAndTime		The control column of the whole mechanism. The scheduler picks up Active schedules whose value here has arrived, the run uses it as the journal's posting date when no explicit date is passed, and after posting it is advanced by the frequency — which is precisely what prevents a period being depreciated twice, however often the job runs.
`OwnerId`	Owner	Lookup → UserAccount	Yes
`PartnerAccountId`	Partner Account	Lookup → Account
`PeriodAmount`	Period Amount	Currency		The fixed charge per run for a straight-line schedule. The engine clips it on the final period so the closing carrying value lands exactly on the residual rather than overshooting, and it is ignored when the method is written-down-value.
`RatePerPeriod`	Rate Per Period	Percent		The written-down-value rate as a fraction between zero and one, and applied per run rather than per annum — a schedule running monthly needs the monthly rate here, not the annual one. It is ignored entirely when the method is straight-line.
`RecordTypeId`	Record Type	Guid, hidden
`ResualValue`	Residual Value	Currency		Intended as the salvage floor below which the asset is not depreciated.
`StartDate`	Start Date	DateAndTime
`Status`	Status	Text		Lifecycle state with the vocabulary Active, Paused and Completed. The engine sets Completed itself once the asset is fully depreciated or the end date is passed, so Paused is the only value an operator sets to suspend a schedule.
`UIProps`	UI Props	Text
`UpdatedDateTime`	Modified Date	DateAndTime	Yes

Actions

Action	Label	Type	What it does
`Clone`	Clone	ServerAction (`Clone`)	Create a copy of this record
`Delete`	Delete	Delete	Delete
`DeleteEntity`	Delete	Delete	DeleteEntity
`DeleteRow`	Delete	Delete	Delete
`Edit`	Edit	Edit	Edit
`EditEntity`	Edit	Edit	Entity
`EditInLine`	EditInLine	EditInline	EditInLine
`New`	New	New	New
`PostRecurringDepreciation`	Post Recurring Depreciation	ServerAction (`PostRecurringDepreciation`)	Runs one period of the schedule immediately, using an optional runDate argument and otherwise the schedule's own next run date. It computes the period's charge, posts a balanced two-line Depreciation journal (debit depreciation expense, credit accumulated depreciation), reduces the carrying value, increases accumulated depreciation, stamps the last run date and advances the next run date by the frequency, returning whether it posted along with the journal id. It shares the same service the background scheduler uses, so manual and scheduled runs cannot double-post the same period; it refuses to run a schedule that is not Active or that lacks either GL account, and it returns without posting when the asset is already down to its residual value, marking the schedule Completed.

Account — looks up via PartnerAccountId
GLAccount — looks up via DepreciationExpenseGLAccountId
UserAccount — looks up via CreatedById
UserAccount — looks up via ModifiedById
UserAccount — looks up via OwnerId
Branch — looks up via BranchId
GLAccount — looks up via AccumulatedDepreciationGLAccountId
Journal — referenced by via SourceRecordId

Recurring Depreciation — entity reference

Fields

Actions

Related entities

Related topics