Attendance and Vacation Document Terms

Vacation and attendance documents rarely post anything by themselves — a vacation does not move money, it moves a balance, and the money follows later on a salary document. So the terms on this family are mostly about what else gets created when the document is saved, and only occasionally about accounts.

The shared mechanics — what a term is, why most aggregated terms only name a book and a term, and the three differently-named accounting switches — are on Salary and Dues Document Terms.

The Vacation Document term

The vacation document's term is a small set of side effects.

Option	Field	What it does
Generate Delegation	termConfig.generateDelegation	Saving the vacation also creates a delegation document, so somebody is formally covering the absentee's responsibilities while they are away.
Generated Delegation Book	termConfig.generatedDelegationBook	The book that delegation is filed in. Setting the switch without the book leaves the delegation nowhere to go.
Change Employee State only If vacation Start Date Match Today	termConfig.changeEmpStateIfDateMatchToday	The employee's state changes to "on vacation" only when the vacation actually starts, rather than the moment the document is saved. Leave it off and a vacation entered three weeks ahead moves the employee's state today.
Generated Loan Reschedule Book / Term	termConfig.generatedLoanRescheduleBook, …Term	A vacation can push a loan instalment out, which is done by creating a loan reschedule document. These two name its book and term.

The last pair is easy to overlook and produces a good support puzzle: a customer reports that going on unpaid leave did not postpone the loan instalment, and the cause is an empty book on the vacation term.

The aggregated vacation terms

Three aggregated documents cover a batch of employees, and their terms do what aggregated terms usually do — name the book and term of what they create.

Term	Fields	What it creates
Aggregated Vacation Document	termConfig.generatedAggVacationDocTerm, …Book, plus its own Generated Loan Reschedule Book / Term	One vacation document per employee, and any loan reschedules those produce.
Multi-Employee Vacation	termConfig.generatedAggVacationDocTerm, …Book	The same, for the multi-employee vacation screen.
Aggregated Vacation Starting Document	termConfig.generatedWorkStartingDocBook	The work-starting documents that record a batch of employees coming back. Note it names only a book — there is no term field here.

The Vacation Compensation term

Paying an employee for vacation they did not take is one of the few attendance-family documents that does post, so its term carries account sides — Debit and Credit, plus a second pair Debit 2termConfig.debit2 and Credit 2 termConfig.credit2 for implementations that split the compensation across two entries.

The field that matters most is Compensation Value Calculation FormulatermConfig.compensationCalcFormula: the component calculation formula that decides what a day of untaken vacation is actually worth. Is it basic salary only, or basic plus allowances? That question is answered here, not on the document, which is why two compensation terms with different formulas are a normal arrangement.

The aggregated compensation term is the usual short one: Vacation Compensation Book and Vacation Compensation Term (termConfig.compensationBook, termConfig.compensationTerm).

See Vacation Compensation and Transfer.

The Holidays and Rest Balance term

This document compensates employees for public holidays and weekly rest days they worked, by adding to a vacation balance rather than by paying cash. Its term says which balance:

Option	Field	What it does
Rest Days Compensation Vacation Type	termConfig.restDaysCompensationVacationType	The vacation type that a worked weekly rest day is credited to.
Holidays Compensation Vacation Type	termConfig.holidaysCompensationVacationType	The vacation type that a worked public holiday is credited to.
Recalculate Employee Attendance Lines	termConfig.reCalculateEmpAttendanceLines	Saving the document re-runs the employee's system attendance calculation, so the days it compensates are re-read rather than taken from what was calculated before.

Pointing both types at the same vacation type is legitimate and common; keeping them apart lets a customer give rest-day work and holiday work different expiry or carry-over rules, since those live on the vacation type.

Compensating in balance, not in cash

Because this document credits a vacation balance, nothing appears on a payslip. If a customer expects money, the tool is a salary component driven by the rest-day and holiday overtime indicators, not this document. See Overtime and Lateness.

The aggregated leave permission and mission terms

Both are the pure two-field shape:

• Aggregated Leave Permission — Leave Permission Term termConfig.leavePermissionTerm and Leave Permission Book termConfig.leavePermissionBook.
• Aggregated Mission Document — Mission Document Term termConfig.missionDocTerm and Mission Document Book termConfig.missionDocBook.

The individual leave permission and mission documents have no term configuration of their own — everything that governs them is on HR Configuration (the permission ceilings, the overlap priorities, whether either adds to overtime) or on the document itself. So if you are hunting for a setting that changes how a mission behaves, the term is the wrong place to look.

Related pages

• Salary and Dues Document Terms — the shared mechanics and the money documents.
• Vacation Documents — the documents themselves.
• Vacation Types and Balances — what the compensated balances are.
• Leave Permissions and Missions
• HR Configuration — where the attendance rules actually live.