A template that materialises a posted journal on a schedule — rent, accrual, amortisation and standing provision entries. A scheduled evaluator finds active templates whose next run date has arrived and emits one job per template; the processor clones the template lines into a new balanced journal dated for the run, posts it through the normal posting pipeline, and advances the next run date by the frequency. The generated journal is stamped with this template as its source document, and the template flips to Completed once the advanced date passes its end date.
Fields
| Field | Label | Type | Required | What it does |
|---|
BranchId | Branch | Lookup → Branch | | Stamped onto the generated journal header and onto every generated line, since template lines carry no branch of their own. Anything the branch cannot supply is then filled during posting from the GL account's defaults. |
CreatedById | Created By | Lookup → UserAccount | Yes | |
CreatedDateTime | Created On | DateAndTime | Yes | |
EndDate | End Date | DateAndTime | | The last date a run may be scheduled for: the scheduler skips a template whose next run date has passed it, and the run that advances beyond it marks the template Completed. Leaving it empty means the template runs indefinitely. |
Frequency | Frequency | Text | | Monthly, Quarterly, HalfYearly or Yearly, and it is what the next run date is advanced by after each run — monthly adds one month, quarterly three, half-yearly six, yearly one year. Anything unrecognised, including a blank value, is treated as monthly rather than rejected. |
Id | Id | Guid | Yes | |
IsActive | Is Active | Boolean | | A second enable switch alongside the status. The service-level due lookup treats an unset value as enabled and skips templates explicitly turned off, so a template needs both an Active status and a non-false value here to run reliably. |
Label | Label | Text | | |
ModifiedById | Modified By | Lookup → UserAccount | Yes | |
Name | Name | Text | Yes | |
Narration | Narration | Text | | |
NextRunDate | Next Run Date | DateAndTime | | The single field that decides whether a template runs: the scheduler picks up active templates whose next run date is on or before today, and the run advances it by the frequency. |
OwnerId | Owner | Lookup → UserAccount | Yes | |
PartnerAccountId | Partner Account | Lookup → Account | | |
RecordTypeId | Record Type | Guid, hidden | | |
StartDate | Start Date | DateAndTime | | Records when the schedule is meant to begin, but the scheduler does not read it — due-template selection is driven purely by the next run date. Set the next run date to the first intended run or the template will not fire when expected. |
Status | Status | Text | | Active, Paused or Completed. Only Active templates are picked up by the scheduler, Paused suspends runs without losing the schedule, and Completed is set automatically once advancing the next run date takes it past the end date. |
UIProps | UI Props | Text | | |
UpdatedDateTime | Updated On | 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 | DeleteRow |
EditEntity | Edit | Edit | EditEntity |
EditInLine | Edit | EditInline | EditInLine |
EditRow | Edit | Edit | EditRow |
New | New | New | New |
