ANTE User Manual

Employee Records (HRIS)

The Employee Records screen is your central registry of employees. Each record links a person's account, their work assignment (branch, schedule, payroll group), their employment contract, government IDs, and bank details β€” the information payroll and timekeeping rely on. New to the screen? Follow Onboard an Employee for the full setup-to-first-payroll walkthrough.

Sensitive personal information: government ID numbers, biometric data (face and fingerprint) and health information are sensitive personal information under the Data Privacy Act (RA 10173). Your organisation handles it as the controller; ANTE processes it on your organisation's behalf.

Facial attendance consent: when an employee is enrolled, the enrol screen shows a notice and a required consent checkbox, and ANTE records the employee's consent. Admins can withdraw consent, which deletes the face template and the enrolment photo. Enrolments made before this change show "consent not recorded".

The Employee Records list
  1. 1Status tabs β€” Active, Inactive, Separated, Not Yet Set
  2. 2Search box with a search-by selector
  3. 3Create Employee β€” add a new employee record
Tip

New to how departments, user levels, roles, the Reports To line and employee records fit together? Start with the tutorial Understand Users, Roles and Employees.

Accessing Employee Records

  1. Open HR in the sidebar.
  2. Click Employees.
  3. Click Employee Records.

The page header reads Employee Management with the subtitle "View and manage employee records."

The Employee List

The list shows one row per employee with these columns:

Eleven of them are hidden until you turn them on β€” click Column Visibility at the top right of the list and check the ones you want. They're marked (hidden by default) below.

Beyond those, the picker has more optional detail columns, grouped into sections: Personal (Birthdate, Age, Sex, Civil Status, Nickname, Place of Birth, Nationality, Religion, Blood Type, Mother's Maiden Name, Height, Weight), Contact & address (Username, Personal Email, Alternate Mobile, Present Address, Permanent Address), Emergency contacts, Government IDs (TIN, SSS, PhilHealth, Pag-IBIG, MP2 Account), Bank (Bank Name, Bank Account Number), Employment (Contract Start, Regularization Date, Probation End Date, Biometrics Number, Custom Daily Rate, Separation Type, Date of Separation), Education (Highest Education, Course / Degree, School, Year Graduated) and Custom fields. All are hidden by default. An employee whose personal details you are not allowed to read shows Restricted in these columns, and pay columns such as Custom Daily Rate are masked without the View Compensation permission.

Avatar
Profile photo (or initials)
Employee Code
Full Name
Shown as Last, First M.
Department
Position
Tags
The employee's hashtag labels (e.g. #factory, #set-a), shown as colored chips β€” up to three, with a count for the rest. An employee can carry several, unlike Department or Branch. See Employee Tags to manage the tag vocabulary. (hidden by default)
Rank
Job-title rank derived from the employee's role β€” Executive, Director, Manager, Senior, or Staff. (hidden by default)
Level
The role's numeric authority rank, where 0 is the highest. (hidden by default)
Branch
Date Hired
The start date of the employee's first contract. A renewal or a new contract doesn't move it. (hidden by default)
Supervisor
Who the employee reports to. Reads Restricted when that supervisor outranks you. (hidden by default)
Schedule
The employee's assigned schedule code. (hidden by default)
Payroll Group
The employee's assigned payroll group code. (hidden by default)
Tenure
Length of service since the hire date, e.g. 2y 3m. (hidden by default)
Contract End
Blank for an open-ended (Regular) contract. (hidden by default)
Email
The employee's email address. (hidden by default)
Contact Number
(hidden by default)
Status
A colored badge: Regular, Probationary, Contractual, Project Based, Part Time, Intern, Consultant, or No Contract / Inactive / Separated
Account Status
A colored badge showing whether the employee's login is ready β€” one of three states: Activated (they can sign in β€” they set their own password, or simply logged in), Invitation sent (an activation email has gone out and the employee just hasn't used it yet), or Not invited (the account exists but no activation email has been sent β€” the common state right after Add Employee or bulk import, since both default to not emailing). See Account Activation below.

By default, the list loads sorted by Full Name (A–Z) β€” alphabetically by last name. Click any column header to sort by that column instead.

Click any row to open that employee's detail page. (When the Status filter is set to Not Yet Set, clicking a row opens the account setup page instead.)

Use the search box and pick what to search by:

  • First Name (default)
  • Last Name
  • Employee Code

Searching by First Name or Last Name will not turn up an employee whose identity is restricted from you β€” searching by their Employee Code still finds them.

Filters

  • Status β€” Active (default), Inactive, Separated, Not Yet Set
  • Employment Type β€” No Contract, Regular, Probationary
  • Branch β€” pick from the branch tree
  • Job Grade β€” optional filter: only the employees who hold the chosen job grade today, or No job grade for the employees who have none. Optional Job Grade (the grade name), Job Grade Code and Title Rank (the leader title of that job grade) columns can be turned on in Column Visibility.
  • Department
  • Tags β€” pick one or more tags. Once you've picked two or more, an Any tag / All tags choice appears next to it: Any tag (the default) shows an employee who carries at least one of the selected tags, All tags shows only an employee who carries every one of them.

With five filters now on this list, only the first three (Status, Employment Type, Branch) show directly on the bar. Department and Tags are tucked behind a More Filters button β€” click it to reveal them. If you (or a link someone shared with you) already have Department or Tags applied, the button shows a count badge and the extra filters open automatically so you can see what's narrowing the list. Any list in ANTE whose filter bar grows past four filters behaves the same way.

Your search, sort, and filter choices here are remembered between visits β€” leave Employee Records for another screen and come back, and the list reopens the same way you left it. A shared or bookmarked Employee Records link that already has its own filters is shown as-is instead.

Toolbar actions

At the top right of the list you see Tutorial, Change requests, a More menu and Add Employee. Change requests opens the Employee change requests dialog, with a count of pending requests beside it (shown to users who can view profile changes); see Profile Change Requests. The More menu holds:

  • Due for regularization β€” opens Regularization Due
  • Import β€” open the bulk employee import workflow
  • Approval overrides β€” opens the Overrides tab of Approval Configuration, where approvers for specific employees are set and imported from Excel (shown only to users who can open Approval Configuration)
  • Export β€” opens the Export employees dialog to download an .xlsx of the employees currently shown (this button is hidden while the Status filter is "Not Yet Set"). See Exporting Employees

Add Employee stays on the bar and opens the employee creation page.

Row menu (right-click or β‹―)

Right-click any employee in the list, or click the β‹― button at the end of the row, to act on that employee without opening their record first. The menu offers:

  • View employee information, Open in new tab and Edit employee
  • Shortcuts straight to a tab of the record: View pay & contracts, View leave balances and View documents
  • Assign Leave, Assign Allowance, Assign Deduction and New Contract
  • Copy employee code and Copy email
  • Send Email Invite (or Resend), Log in as this employee and Salary certificate
  • Separate, Cancel separation, Re-Hire, Restore and Delete

The menu shows only what you can do for that employee, using the same rules as the buttons on the employee's record. For example, it leaves out pay items if you cannot see pay, and it shows Cancel separation instead of Separate when a separation is already scheduled. It offers Re-Hire for a separated employee. On the "Not Yet Set" filter it offers View account, Activate Employee and Copy email.

Adding an Employee

Click Add Employee to open the Add Employee page. It is a guided flow of six steps shown across the top: Account & login, Position & organisation, Contract & pay, Leave & approvers, More details and Review & submit. Click Next to move on (the required fields of the step you are leaving are checked first) and Back to return. Nothing you typed is lost when you go back, and you can click a step you have already visited in the bar at the top. Required fields are marked with an asterisk.

The Add Employee flow, step 1 β€” six steps across the top, Next and Back at the bottom right
  1. 1The six steps β€” click a visited step to jump back to it
  2. 2Account type β€” create a new account or link an existing one
  3. 3Employee ID β€” required, and unique within the company
  4. 4Next β€” checks this step, then opens the following one
What you can see depends on your permissions

Pay fields (Monthly Rate, the contract file and the custom daily rate) need the View Compensation permission. Without it the contract step shows a notice instead of those fields, and you cannot finish on the last step: ask an administrator to add the employee, or to grant you access (see Who Can See Pay). Setting the filing approvers on step 4 needs the Filing Approver Update permission; without it that block explains that the employee's superior approves by default.

Step 1: Account & login

Account type*
Create new account registers a brand-new person and creates their login at the same time. Link existing account turns an account that already exists, but is not yet an employee, into an employee: pick it in the Account search field and its name, e-mail, role and superior are carried over.
Employee ID*
The company's own employee number. It must be unique within the company.
First Name / Middle Name / Last Name*
First and last name are required (new account only). Letters, spaces, hyphens, periods and apostrophes are accepted; digits are not. ANTE writes each name with a capital first letter.
Email Address*
Where the activation link is sent. Must be a valid e-mail address.
Contact Number*
10 to 13 digits. Spaces, dashes, brackets and a leading + are allowed.
Username*
The employee's login. It is suggested for you from the company's username convention as soon as the name, employee ID or e-mail is filled in; type your own to replace it. See How usernames are suggested.
Date of Birth*
Stored on the employee's personal record. You do not set a password: the employee chooses their own through the activation link.
Send activation email now
Off by default. Leave it off to create the account without e-mailing the employee yet (the Account Status then reads Not invited); tick it to e-mail the set-password link as soon as the employee is created. See Account Activation.

Step 2: Position & organisation

Role/Position*
The employee's job title, and the role that decides which screens they can use. You can only seat someone in a role below your own hierarchy level; a full-access user (Super Admin) is not bound by this (same rule as on Settings β†’ Users and Roles).
Job grade
Optional, and shown only when your company has job grades. The grade sets the employee's title allowance automatically from their start date, so you do not add it by hand. Grades linked to the chosen position are listed first and marked, but any grade can be picked. See Managing the Employee's Job Grade.
Department
Defaults to Same as role β€” <department path>. See Choosing an Employee's Department. Not shown when you are activating an existing account.
Reports To
The employee's immediate superior; the choices depend on the selected role. The superior is also the employee's default filing approver until you set approvers on step 4 (a hint under the field says so and, for users who can open Approval Configuration, links there).
Branch*
The branch the employee belongs to.
Tags
Optional hashtag labels. Pick existing ones, or type a new one and choose Create tag to add it on the spot. See Employee Tags.
Step 2 β€” the position is the job title; the department follows it unless you choose one

Choosing an Employee's Department

An employee's department normally follows their role. On the Add and Edit employee forms, the Department field lets HR place the employee in any department directly instead. Its first option, Same as role β€” <path> (the default), keeps the department of whichever role is picked in the same form; any other option sets the department directly, and that choice stays even if the role changes later. Choose Same as role again to go back to following the role.

Everywhere an employee's department is shown β€” the list's Department column, the detail page and its identity card, the team panel and the Excel export's Department column β€” Ante displays the full path, for example Plant 1 β€Ί Production β€Ί ICE Line, with the parent levels muted. In a table cell a long path is shortened (the middle folds into …); hover to see the whole path. Filing approvals, department pools and the other department-based rules use this effective department. A department that has employees assigned to it directly cannot be deleted.

Step 3: Contract & pay

Monthly Rate*
The monthly pay for the contract. Needs the View Compensation permission; without it the field is not shown.
Employment Status*
Defaults to Regular.
Start Date*
When the contract starts. The job grade's title allowance also starts on this date.
End Date*
Appears, and is required, when the status is anything other than Regular.
Regularization date / Monthly rate on regularization
Shown only when the status is Probationary. The date defaults to six months after the start date. See Regularization.
Use custom daily rate
Tick it to type a Custom Daily Rate instead of the rate derived from the monthly rate. Needs View Compensation.
Contract file
Optional. Upload the signed contract (PDF, DOC, PNG or JPG, up to 10 MB). It is attached to the new contract. Needs View Compensation.
Schedule*
The work schedule (shifts) the employee follows.
Payroll Group*
The payroll group that pays the employee. When the company has only one, it is chosen for you.
Step 3 β€” contract, pay, schedule and payroll group

Step 4: Leave & approvers

Leave plan
Optional, and shown only when the company has an active leave plan. It gives the employee their leave entitlements from the start. Leave it empty and the company's assignment rules may still assign a plan. When there is only one plan, it is chosen for you. See Assigning a Leave Plan.
1st / 2nd / 3rd / 4th approver
Up to four people who approve this employee's filings, in order, for every filing type. The next slot appears once the previous one is filled. Pick people other than the employee, and nobody twice. Leave all four empty to keep the default flow: the Reports To superior approves. The 1st to 4th approvers become this employee's all-types override. Per-type overrides, flows and backup approvers are set later in Approval Configuration.
Who approves a filing for the new employee
What you set on this stepWho approves the employee's filings
No approvers chosenThe Reports To superior (the default flow)
1st approver onlyThat person, for every filing type
1st, 2nd and 3rd approverThe three in that order, one after the other
After saving you can check the result on the employee's Employment tab, under Who approves this employee's filings.
Step 4 β€” an optional leave plan and up to four filing approvers

Step 5: More details

Everything here is optional and can be added later. For a linked account (an existing user) there is nothing more to add except any company custom fields.

  • Additional Information β€” your company's own custom fields, shown when any are active. Required ones must be filled before you can continue.
  • Additional Details tab β€” gender, civil status, address (street, city, state / province, country, postal and zip code) and the personal details, permanent address and emergency contacts. Height must be between 50 and 250 cm and weight between 20 and 300 kg.
  • Government tab β€” SSS, PhilHealth, Pag-IBIG, MP2 and TIN numbers, formatted as you type (SSS XX-XXXXXXX-X, PhilHealth XX-XXXXXXXXX-X, Pag-IBIG and MP2 XXXX-XXXX-XXXX, TIN XXX-XXX-XXX). MP2 is the separate, voluntary Pag-IBIG savings program, so it has its own number.
  • Bank tab β€” bank name and account number (needs the Bank Account update permission).

Step 6: Review & submit

The last step starts with a summary of the new employee: their name, position and department, the employee ID, start date, employment status and branch. Beside it, a box says what the button will do: Ready to create (the employee is created when you confirm), Goes for approval (it names the approval steps in order) or Cannot create yet (and why, for example a missing View Compensation permission).

Under the summary, Optional, but worth a look lists things that are not required but are easy to forget on a new hire: no contract file, no grade (so no title allowance yet), no filing approvers (the Reports to person then approves) and no leave plan. Add on each line jumps to the step that holds it. Then one card per step shows what you entered, with Edit to jump back. Pay figures appear only if you have View Compensation. The submit button's name depends on whether your company reviews new employees (next section).

If something is wrong, the page jumps to the step that holds the problem and highlights the field, for example a username or employee ID that is already taken.

Step 6 β€” check the summary and the outcome box, then Create Employee (or Submit for approval)

Create Employee or Submit for approval

The button on the last step is Create Employee (Activate Employee when you came here to activate an existing not-yet-set account) or Submit for approval. Which one you see depends on the company's approval route for New employee registration, set in Employee Change Approvals:

What the last step does for you
Your situationButtonWhat happens when you click it
No approval route for new employees, or your user level may save directlyCreate EmployeeThe employee and their login are created at once, and you open their record. A message confirms it.
A route is on and your user level is not a direct saverSubmit for approvalNothing is created yet. The registration is filed as a request and the registration waits in the Change requests list. A line above the button reads "Reviewed by:" followed by the steps.

A submitted registration appears in the Change requests list, described on Profile Change Requests as New employee: <name>, waiting on the first approver. No account, no username and no employee ID is taken until the last approver approves.

  • When it is approved by the last step, ANTE creates the account and the employee exactly as you entered them (including the grade, approvers, leave plan and contract file, and the activation e-mail if you ticked it), as if you had clicked Create Employee.
  • When it is rejected, nothing is created and the reviewer's note comes back to you. Start again from Add Employee with the corrections, or ask the reviewer what to change. You can also Withdraw your own request while it waits.
A registration can fail when it is approved

The details are checked again at approval time. If the username, employee ID or e-mail was taken by someone else in the meantime, the approval is refused with the reason and the request stays pending: withdraw it and submit a new one with a free value.

After a successful direct save, a message may add a note that a follow-up step did not apply (for example the job grade or an approver could not be saved). The employee still exists; open their record to finish it.

How usernames are suggested

Under HR Settings β†’ Employee records, the company chooses a Username convention. On step 1, the Username is filled in for you as soon as the name, employee ID or e-mail is known, following that convention; you can always type your own instead. A username is saved in lowercase, and login ignores capitalization.

The same person under each convention (Juan Dela Cruz, employee ID 2836, juan@example.com)
ConventionSuggested usernameIf it is taken, the next one
Typed by HR (default)nothing suggested; you type ityou are told it is taken
E-mail addressjuan@example.comjuan2@example.com
Employee code283628362
First name . surnamejuan.delacruzjuan.delacruz2
Surname + first initialdelacruzjdelacruzj2
Accents are removed (PeΓ±a becomes pena). A suggestion that is already taken gets the lowest free number added (2, then 3 ...); for an e-mail the number goes before the @.

A username you type yourself is used as typed. If someone already has it, saving is refused and you are told the next free one to use.

Account Activation

When you create a new employee (single add or bulk import), ANTE does not set their password for you. The account is created inactive with an activation invitation. Whether the activation email goes out right away depends on the Send activation email now checkbox β€” it's off by default for both single add and bulk import, so by default no email is sent at creation time. (Onboarding a hired applicant from the recruitment pipeline is the one flow that always emails the link immediately.) An administrator can send it later whenever ready, either from that employee's own record (Actions β†’ Send Email Invite) or from Settings β†’ User Invites. Once the email is sent β€” whether right away or later β€” here's what the employee sees:

  1. ANTE sends an email titled "Activate your [company] account on ANTE" to the Email Address you entered, with a Set My Password button (and a plain-text link as a fallback). The link expires after 7 days.
  2. The employee clicks the link and lands on a Welcome! Set Your Password page, greeted by name and company.
  3. They enter a New Password and Confirm Password β€” a live checklist confirms the password meets the company's password policy.
  4. They click Activate Account. They're taken to the login page with a confirmation banner, and can now sign in.

Until the employee activates their account, they cannot sign in, and the Account Status column on the Employee List shows Not invited if no activation email has gone out yet, or Invitation sent once one has. A row without a valid email address is still created as an employee and stays Not invited, since no activation email can ever be sent to it.

Clicking the emailed link isn't the only way an account becomes Activated β€” anything that proves the employee controls the account does it: logging in (for example, with a temporary password an administrator handed them directly), or setting their own password through Forgot Password on the login page. An administrator resetting the password on the employee's behalf does not, by itself, activate the account β€” only the employee's own subsequent login or password change does.

If the link is invalid or has expired, the employee sees an Invalid or Expired Link message asking them to contact their administrator.

Activating a "Not Yet Set" Account

Accounts that exist but were never set up as employees appear when you set the Status filter to Not Yet Set. Clicking one opens its setup page; from there you complete the same Add Employee form (pre-filled with the account's name, email, and role) to activate the person as an employee.

Viewing an Employee

Click an employee row to open the detail page. At the top is an identity card that stays visible on every tab: the photo, name, position Β· department, status badges, username, email and phone number, and a row of key facts (employee code, employment status, contract start date, branch, and supervisor β€” a link to the supervisor's record). Below it, the detail is split into seven tabs: Overview, Personal, Employment, Pay & Tax, Leave & Time, Documents and Training. The tab you are on is kept in the page address (?tab=), so a reload or the browser's Back button returns you to the same tab. The page shows:

An employee's detail page β€” every card that payroll and timekeeping read from, with the record's actions in the header
  1. 1Assign β€” allowances, deductions, and leave plans
  2. 2Edit β€” change the record
  3. 3Actions β€” send/resend the activation email, separate, or delete
  4. 4Identity card β€” photo, name, position Β· department, status badges and key facts, visible on every tab
  5. 5Tabs β€” Overview, Personal, Employment, Pay & Tax, Leave & Time, Documents, Training
  6. 6Work Assignment β€” branch, supervisor, schedule, payroll group
  7. 7Tags β€” this employee's hashtag labels ("No tags assigned" when empty)
  • Identity card (above the tabs) β€” photo, name, position and department, username, email, contact number, key facts, and status badges: an Account Status badge (Activated / Invitation sent / Not invited) plus an Inactive or Separated badge when the employee is one of those β€” an active employee is the default, so it isn't badged separately. When the employee holds a job grade today, the card also shows Job Grade (code and name) as a link to the Job Grade section on the Employment tab, and Title Rank (the job grade's leader title, such as Senior TL) when the job grade has one
  • Personal tab β€” three cards: Personal information (date of birth, gender, civil status and the other personal details, including Mother's Maiden Name, Height and Weight), Contact and address, and Emergency contact (name, number, relationship and address, plus a Second Emergency Contact block when one is set); the Overview tab repeats a short Personal summary, which also shows the employee's Highest Education (level Β· course Β· school) taken from their education records β€” the highest level first, then the latest year graduated
  • Work Assignment β€” Date Hired (the first contract's start date, with the length of service, e.g. March 24, 2026 Β· 6m), branch, department (full path), role/position, supervisor (a link to the supervisor's record), schedule, payroll group, and Job Grade (code, name and the date it started, or No job grade) and Title Rank (the title that goes with that job grade, such as Senior TL, or a dash when it has none)
  • Tags β€” its own section, separate from Profile, since an employee can carry several at once (unlike the single-valued Branch, Department, Payroll Group, or Schedule). Reads No tags assigned when the employee has none. See Tags above and Employee Tags to manage the vocabulary.
  • Contract Details β€” employment status, start date, end date, monthly rate. For a probationary employee it also shows the Regularization date, Probation ends, and the Monthly rate on regularization when one has been set
  • Government β€” SSS, PhilHealth, Pag-IBIG (and custom Pag-IBIG amount if set), MP2 Account Number, TIN, and Projected Bonus Tax Smoothing (months of salary, or Off)
  • Bank Accounts (Pay & Tax tab) β€” the full Bank Accounts section lists every account with its dates and change history. Only a viewer who has no access to bank accounts sees the older Bank Details card (bank name and account number) instead
  • Weekly Schedule β€” a day-by-day table (shift code, type, time, break, target hours)
  • Leave Balances β€” per leave plan, showing Available, Used, and Total credits (the Total is hidden when the plan has no yearly total)
  • Contract History
  • Allowances
  • Deductions & Loans
  • Fixed Withholding Tax
  • Employee Documents
  • Project & Engagement Assignments
  • Courses completed (Training tab) β€” every Academy course the employee has finished, newest first, with the completion date, length and certificate number. Click a certificate number to open its public verification page. A course still in progress is not listed.
  • Team training (Training tab) β€” trainings assigned through Workspace team management, with their status and completion date.
  • Enrolled Faces β€” the employee's enrolled facial-recognition reference photos, newest first, each with the enrollment date and a quality score. Only shown when the employee has at least one enrolled face.
  • Recent Successful Scans β€” the employee's last 10 successful (Match) face scans, newest first, with a photo, scan time, device, action (Time In / Time Out / Smart), and confidence. Click a row to open that scan's detail page in Face Scan Logs. Only shown when the employee has at least one successful scan.

Managing Allowances

The Allowances section lists every allowance currently assigned to the employee, with a summary of the total number of allowances and their combined monthly total. If your role has the allowance permissions, you can add, edit, and remove the employee's allowances directly from this section β€” you no longer have to leave Employee Records to do it. Adding, editing, and removing are each gated by their own permission, so depending on your role you may see only some of these actions (for example, edit but not remove). Without any of these permissions, the section is read-only: no Add Allowance button, and no edit or remove icons on the rows.

Adding an allowance

  1. Click Add Allowance in the section header.
  2. Allowance Type β€” search and select the allowance to assign.
  3. Once a type is selected, fill in:
    • Allowance Amount
    • Payment Period β€” when the allowance is given: Every Period, First Period, Last Period, or Not Given
    • Effectivity Date
  4. Click Add Allowance to save. The new allowance appears in the list immediately.

Editing an allowance

Click the pencil icon on an allowance row to open Edit Allowance:

  • Computation Mode β€” Fixed, Pro-Rated Ratio, Per Absent, or Banded by Absence. Banded by Absence pays the share of the allowance set by the allowance type's absence bands for the employee's absence in the calendar month (default: 0–49.9% absent pays 100%, 50–99.9% pays 50%, 100% pays nothing). Absence is judged for the whole month even with semi-monthly cutoffs: each cutoff pays the month-to-date entitlement minus what earlier cutoffs already paid, so the month-closing cutoff equals the monthly amount times the band. The percentage is rounded down to a tenth, and only days the employee's contract covers count (a partial month for joiners and leavers). Use Every Period or Last Period as the Payment Period β€” a banded plan set to First Period only sees the first half of the month.
  • Deduction Per Absent β€” only shown when Computation Mode is Per Absent
  • Allowance Amount
  • Payment Period
  • Effectivity Date

Click Save Changes to apply your edits.

Removing an allowance

Click the X icon on an allowance row, then confirm in the dialog that appears. Removing an allowance here permanently deletes that assignment β€” this cannot be undone.

Managing Deductions & Loans

The Deductions & Loans section lists every regular deduction and loan currently assigned to the employee, with running totals and, for loans, a balance and progress bar. If your role has the deduction permissions, you can add, edit, and remove the employee's deductions and loans directly from this section β€” you no longer have to leave Employee Records to do it. Adding, editing, and removing are each gated by their own permission, so depending on your role you may see only some of these actions. Without any of these permissions, the section is read-only: no Add Deduction button, and no edit, remove, or balance icons on the rows.

Adding a deduction or loan

  1. Click Add Deduction in the section header to open Add Deduction or Loan.
  2. Deduction Type β€” search and select the deduction (or loan) to assign.
  3. Once a type is selected, fill in:
    • Total Loan Amount β€” only shown when the selected type is a loan
    • Monthly Amortization
    • Deduction Period β€” Every Period, First Period, Last Period, or Not Deducted
    • Effectivity Date
  4. Click Add to save. The new deduction or loan appears in the list immediately.

Editing a deduction or loan

Click the pencil icon on a row to open Edit Deduction:

  • Total Loan Amount β€” for loans, shown read-only here; the loan principal is not edited on this dialog (use Add Balance / Pay Balance below instead)
  • Monthly Amortization
  • Deduction Period
  • Effectivity Date

Click Save Changes to apply your edits.

Removing a deduction or loan

Click the X icon on a row, then confirm in the dialog that appears. Removing here permanently deletes that deduction or loan assignment β€” this cannot be undone.

Managing a loan's balance

Loan rows have two additional icons, alongside Edit and Remove:

  • Add Balance β€” increases the loan's outstanding balance (for example, a top-up). Enter the Amount and a Remarks explaining why; both are required.
  • Pay Balance β€” records a payment against the loan. Enter the Payment Amount (capped at the remaining balance) and Remarks; both are required. This icon is hidden once the loan's balance reaches zero.

Managing Fixed Withholding Tax

The Fixed Withholding Tax section lets you set a flat peso amount of income tax to withhold from this employee every cutoff, instead of the amount the BIR semi-monthly table would produce β€” typically used for executives, expatriates, or staff with other income sources who ask for a higher withholding. It shows a summary line (the amount in force, its period, and its effective dates, or a note that the BIR table applies when no amount is set) plus a history of every setup ever recorded for the employee. If your role has the deduction configuration permissions (the same MANPOWER_CONFIGURATION_DEDUCTION_* scopes as Allowances and Deductions & Loans), you can add, edit, activate/deactivate, and remove setups directly from this section; without them the section is read-only β€” no Add Fixed Withholding button, and no edit, toggle, or remove icons on the rows. Viewing the section only needs the HRIS read permission.

The Fixed Withholding Tax section, with one active setup on file β€” the summary line above the history shows the amount in force, its period, and its effective date
  1. 1Add Fixed Withholding β€” opens the add dialog
  2. 2Summary line β€” the amount currently in force, or a note that the BIR table applies
  3. 3Status β€” Active, Inactive, or Ended
  4. 4Edit, activate/deactivate, and remove icons for this setup

Adding a fixed withholding setup

  1. Click Add Fixed Withholding in the section header.
  2. Fill in:
    • Amount per Cutoff β€” the flat peso amount to withhold
    • Withholding Period β€” Every period, First period, or Last period
    • Effective From
    • Until (optional) β€” leave blank for open-ended
    • Remarks (optional)
  3. Click Add Fixed Withholding to save.

Setting zero withholding β€” enter 0 as the amount to withhold no income tax for the period (for example, for a trainee dispatched abroad). A zero amount needs a reason, so extra fields appear:

  • Reason for zero withholding (required) β€” Dispatched abroad, No TIN yet, Client instruction, or Other
  • Reason details β€” free text for the reviewer, up to 500 characters; required when the reason is Other
  • Also skip the year-end true-up (optional) β€” leave it off unless the income is not subject to Philippine withholding. By default the December true-up still settles the annual tax, which can collect a full year of tax in one payslip.

The reason is recorded for audit, and cutoffs that use a zero setup are listed for review before payroll can advance. The same fields appear when you edit a setup and change its amount to 0.

Only one setup can be active for a given date. If the new setup's dates overlap an existing active one, the save is rejected and a checkbox appears offering to end the existing setup on the day before and create this one β€” check it and save again to resolve the overlap automatically, instead of having to go end or delete the old setup by hand first.

Period compatibility with the payroll group β€” a setup's period must be honorable under the employee's payroll group's own withholding-tax period. A group that withholds every period accepts any setup period. A group that withholds only on the First period or Last period only accepts a setup of Every period or that same single period β€” because a first/last-period group folds both periods' income into one table figure, so a mismatched setup would double up or skip the withholding. A mismatch is rejected when you try to save; if the payroll group's period changes later and an existing setup no longer fits, the section shows a warning banner instead, and payroll keeps the BIR table for that employee until the setup or the group is corrected.

Editing a fixed withholding setup

Click the pencil icon on a row to open Edit Fixed Withholding Tax and change the amount, period, effective dates, or remarks, then click Save Changes.

Activating or deactivating a setup

Click the play/pause icon on a row to activate or deactivate it without deleting it.

Removing a fixed withholding setup

Click the X icon on a row, then confirm in the dialog that appears. Removing here permanently deletes the setup β€” this cannot be undone.

How this shows on payroll β€” while a setup is in force it replaces only the tax line: gross taxable income and taxable income are computed and stored exactly as for a table cutoff, so the alphalist, BIR Form 2316, 1601-C, and the December annualization all keep the same basis, simply counting the fixed amounts as tax already withheld for the year. The fixed amount applies to a cutoff whose start date falls inside the setup's effective window β€” ending a setup mid-cutoff still covers that cutoff in full, with the table resuming from the next one. If the fixed amount would exceed the employee's net pay after every other deduction, only the available net is withheld and the cutoff is flagged for review; a cutoff with no taxable income withholds zero regardless of the setup. A declared minimum-wage earner stays exempt even with a setup on file β€” see Minimum Wage Compliance. On the Payroll Summary, cutoffs using a fixed amount show a Fixed chip in the Tax column, with a warning icon when the setup needs review. Changing or ending a setup does not automatically recompute cutoffs already processed under the old setup β€” recompute the payroll if you need the new setup reflected. Separating or re-hiring an employee does not change their fixed withholding setups.

Entering 0 as the amount reveals the zero-withholding warning and the required reason

Regularization

A Probationary employee becomes Regular automatically on their Regularization date. You don't have to open the record and change the status by hand.

Regularization datedate
The first day as a Regular employee. When you add a Probationary employee and leave it blank, it defaults to the start date plus 6 months. The detail page also shows Probation ends.
Monthly rate on regularizationnumber
Optional. If set, this monthly rate applies from the regularization date. Left blank, the employee keeps their current rate. Setting it needs the permission to update employee records.

Each night ANTE checks for employees whose regularization date has arrived. For each one it adds a new Regular contract starting on that date (at the regularization rate if you set one, otherwise at the current rate), records the change in the audit trail, and notifies your HR and admin users. Pay for the regularization date itself already uses the new contract, never the next pay period. Running the check twice never regularizes anyone twice.

HR is also warned ahead of time. A set number of days before the date, ANTE sends a notification that the employee will become regular (and reminds you if no regularization rate is set). To see everyone who is overdue or coming up, open Regularization Due.

To change the date or rate later, open the employee and click Edit; the regularization block appears on the Work tab while the employee is still Probationary and not yet regularized. Clearing a field removes it. Once the employee has been regularized, the block disappears.

Managing Employee Dispatch

The Dispatch / Assignment Abroad section records periods when an employee is posted away, for example a trainee sent to Japan. It shows whether the employee is On dispatch today (with the type, destination, and dates), or reads Not on dispatch, and lists the full history below it. Each dispatch is marked On dispatch, Upcoming (it starts later), History (it has ended) or Removed.

While a dispatch is in force, payroll applies the treatment you configured under Dispatch Treatment (for example, no withholding tax, no SSS, or a flat full period of pay). A Dispatch treatment settings link in the section takes you there.

Each running or upcoming dispatch shows the rules that apply to this employee under its dates: where they come from (Rules (payroll group …) when the employee's payroll group has its own treatment, otherwise Rules (company-wide)) and one chip per switch that is on, such as No withholding tax, No SSS or Full scheduled period paid. Anything without a chip carries on as normal. If no treatment is configured for the dispatch type, the row reads No treatment for this type: payroll is unchanged. Ended dispatches show no rules, since they were paid under the settings in force at the time.

  1. Add a dispatch

    Click Add dispatch in the section header and fill in Type (Trainee, Assignment, Secondment, or Other), Destination (for example, Japan), Start date, End date (leave empty if ongoing), Expected return date, and Remarks. Start date is required.

  2. Save

    Click Add dispatch. If the dates overlap another dispatch of the same employee, ANTE refuses and names the dispatch that already covers them (Another dispatch (…) already covers these dates. End it first or adjust the dates.). Change the dates, or end the earlier dispatch first.

  3. End a dispatch when the employee is back

    On a running or upcoming dispatch, click End dispatch (the plane landing icon) and enter the Return date, the last day of the dispatch. Only the end date changes; the type, destination and remarks stay as recorded. From the next day payroll treats the employee as back.

  4. Edit, remove, or restore

    Use the pencil on a row to edit it. Remove takes a dispatch out of use (it shows as Removed in the history) and Restore brings it back, so nothing is ever lost.

To load many dispatches at once, click Import in the section header: download the template, fill one row per dispatch (Employee Code, Type, Destination, Start Date, End Date, Expected Return Date, Remarks), upload it, and review the results. Rows with errors are skipped, and nothing is saved until you confirm the import. A row that overlaps another active dispatch of the same employee, in the system or earlier in the same file, is rejected.

Info

The section only appears if you have access to employee dispatch. Adding and editing are separate permissions, so some users see the section read-only.

Managing Bank Accounts

Bank accounts are kept as their own record, separate from salary and contract data, and each one has dates. The Bank Accounts section on the employee detail page shows the Payroll account in force today (or No payroll account in force today (paid in cash)) and a table of every account with Bank, Account number, Type, Effective, Ends, and Status. Payroll bank files always use the account that was in force on the cutoff date, so changing an account never alters the files of past periods.

  1. Add an account

    Click Add account. Fill in Bank, Account number (4 to 34 characters), Account name, Account type (Savings, Checking, Payroll, or Other), Effective from, and Ends on (leave empty if open-ended). Tick Use for payroll for the account salary should be paid into, and add Remarks if you want.

  2. Understand the payroll account rule

    Only one payroll account can be in force on any date. A new payroll account ends the previous one the day before it starts. If a later payroll account already exists, ANTE asks you to edit or end it first.

  3. Edit or end an account

    The pencil edits a row. The stop icon (End account) ends it from today, so payroll files for later dates no longer use it.

  4. Check the history

    Click Change history to see who changed what and when, with the Before and After values. Changes made from other places (for example an approved profile change, or an import) are labelled with where they came from.

Warning

Account numbers appear as the last four digits only unless you hold the View Full Account Numbers permission. When you edit a masked account, leave the number box empty to keep the stored number. Adding or editing needs the Bank Accounts edit permission, and the section does not appear at all without Bank Accounts access.

To work across all employees at once, use the Bank Accounts screen.

Who Approves This Employee's Filings

The Who approves this employee's filings section is a read-only summary of who would approve this employee's filings today. Pick a Filing type and it shows the approval chain that applies (or Default: immediate superior when none is set), then each level with its approvers. An approver who is away is marked on leave today, and the backups are listed with a Backup for <name> or Level backup badge and whether they are available today or not available today. It is shown to users with Employee Records access. At the top it lists the Immediate superior (read-only here: change it under Edit employee, Reports to) and the employee's Overrides. Users who hold the Filing Approver Update permission can Set up an override for the employee, Edit one or Remove the employee from it, without leaving the record (an employee added through Add Employee already has the approvers chosen on step 4 as their all-types override). Without that permission the section stays read-only; Manage in Approval Configuration opens the Overrides tab for users who can open that module. See Backup approvers.

Managing Leave Balances

The Leave Balances section lists every leave plan currently assigned to the employee, showing their Available, Used, and Total credits. Each card is titled with the leave plan's name, with the leave type shown underneath. Balances on an archived leave plan or archived leave type are not shown here (matching the Leave Balance report and the employee's My Leaves); nothing is deleted, and restoring the plan brings the balance back. If your role has the leave permission, you can assign a plan, adjust credits, and deactivate an assignment directly from this section β€” you no longer have to leave Employee Records to do it. All three actions share a single permission: without it, the section is read-only β€” no Assign Leave button, and no adjust or deactivate icons on the rows.

Assigning a leave plan

  1. Click Assign Leave in the section header to open Assign Leave Plan.
  2. Leave Plan β€” search and select the plan to assign. Only plans the employee doesn't have yet are listed. To add credits to a plan they already have, use Adjust Credits on that plan's card instead.
  3. Once a plan is selected, fill in its credit settings:
    • Total Annual Credits
    • Monthly Accrual Credits
    • Credits Given Upfront
    • Renewal Type β€” read-only; set by the leave plan and applied on the same schedule to every employee assigned to it (see Service Incentive Leaves to change it).
  4. Click Assign to save.

This is the same assignment used by Assign β†’ Assign Leave in the header menu (see Assigning a Leave Plan below) β€” use whichever is more convenient.

Adjusting credits

Click the tune icon on a leave plan row to open Adjust Leave Credits:

  • Transaction Type β€” Add or Deduct
  • Amount
  • Reason β€” required; every adjustment is recorded with this reason for audit purposes

The dialog previews the Current Balance and the resulting New Balance before you save. On a company that counts leave in days, credits accept up to two decimals (for example 0.67). On a company that counts leave in hours, the Amount is entered as hours and minutes.

Deactivating a leave plan assignment

Click the X icon on a leave plan row, then confirm in the dialog that appears. Deactivating removes the plan from the employee's active leave balances, but credits are retained β€” the assignment isn't deleted, and it can be reactivated later.

Deactivated plans are hidden by default. When the employee has any, a Show deactivated (n) button appears in the section header (it becomes Hide deactivated). Each deactivated plan shows a Deactivated badge with its Available and Used credits and, if you can manage leave, a Reactivate button that puts the plan back with its credits. A plan that an auto-assign rule manages has no button and reads "Switched on and off by its auto-assign rule".

Managing the Employee's Job Grade

The Job Grade section on the Employment tab shows the employee's current job grade and the full, dated history of job grades they have held. A job grade is a pay level (for example Engineer grade 1), separate from the role; the job grade list is kept on Job Grades. Grade-based allowances read the job grade held on the last day of each cutoff. A job grade may carry a Title Rank such as Senior TL; the employee's Title Rank is always the one of the job grade they hold today, so changing the job grade changes it too.

  1. Click Change Job Grade

    Choose the new job grade and the Effective From date, and add a remark if you wish. Job grades linked to the employee's role are listed first under For this role; choosing another one shows a warning but never blocks saving.

  2. Save

    The current job grade ends the day before the new one starts. A change dated before a later entry is refused: edit that history entry instead.

Each history entry shows its dates and a badge: Current, Upcoming or Past. The pencil edits an entry and the bin removes it (payroll is recomputed for the affected cutoffs). Without the permission to update employee records the section is read-only. To set many employees at once, use Import Job Grades on the Job Grades screen.

Managing Contract History

The Contract History section lists every employment contract ever recorded for the employee β€” Monthly Rate, Start Date, End Date, Status, Employment Type, and an attached Contract File if one was uploaded. Payroll always reads the employee's basic salary from these contracts, so keeping this history accurate (no duplicates, no gaps, no overlaps) is what keeps every cutoff's basic salary correct.

Cash portion on the contract

Some companies pay a fixed part of the net pay in cash and the rest to the bank account. There are two ways to set it up: on the Payroll Group (everyone in the group), or on the employee's contract. The contract is where pay terms are agreed, so a cash portion set there applies from the contract's start date and replaces the group's for that employee. The contract in effect on the last day of the cutoff (the pay-day contract) decides, so a new contract can change or drop the cash portion from its start date. On Add Contract and Edit Contract, the Cash portion section has:

Cash portion amountamount
The pesos of net pay paid in cash. Blank means the payroll group's cash portion applies. 0 means no cash on this contract, even if the group has one.
Paid inselect
Same as payroll group (default), Second period (the cutoff that pays on the 30th), First period or Both periods. A period set here wins over the group's.
All net pay to bank accountcheckbox
No cash for the life of this contract: the whole net pay goes to the bank. It applies even when the group has a cash portion.

A line under the fields shows what the payroll group sets (for example Payroll group sets: β‚±1,000.00 Β· Second period), so you can see what applies when the amount is left blank. Add Contract starts from the current contract's cash terms, so a new contract carries them forward unless you change or clear them. The employee's Contract Details and the Contract History table show the cash terms next to the monthly rate. Employees on an active dispatch, and employees whose net pay is below the cash amount, are paid entirely to the bank automatically. The cash portion is part of the pay terms, so it shows as a lock (masked) for anyone without the View Compensation permission, and a change to it follows the Compensation approval route, like a rate change. The Excel import and export carry it in the Cash Portion (Optional), Cash Paid In (Optional) and All Net Pay To Bank (Optional) columns (blank keeps the contract as it is).

Status column

Each contract row shows one of five statuses:

StatusMeaning
ActiveIn effect today.
ScheduledStarts on a future date.
In CutoffAlready ended, but its end date falls inside the payroll cutoff that is currently open β€” payroll still reads this contract while that cutoff is being processed.
EndedEnded, and its end date falls outside every currently open cutoff.
DeactivatedManually deactivated from this section.
Warning

A contract marked In Cutoff is still being used by payroll even though it has "ended" β€” this is the status to watch for when a duplicate contract is silently skewing an employee's Basic Salary (see Basic Salary β€” Prorated on Salary Detail).

Deactivating a duplicate or incorrect contract

Click the βœ• icon on any still-active contract row (not only the single current one) to deactivate it, then confirm in the dialog. This lets HR clear duplicate or incorrect contracts directly from this list.

The dialog reads "It is removed from the contract history and payroll stops using it." If adding this contract had ended an earlier one, the earlier contract gets its previous end date back, so deactivating a mistaken renewal undoes it. A deactivated contract leaves the list; when an employee has any, a Show deactivated (n) button in the section header (then Hide deactivated) brings them back into view.

Adding or editing a contract

Click Assign β†’ New Contract in the employee's action menu to add a contract, or the pencil icon on a contract row to edit one. Both forms share the same rules:

  • End Date is required for every Employment Status except Regular.
  • End Date must be a date after the Start Date.

ANTE also checks the new contract's dates against the employee's other contracts:

  • Same start date as an existing contract β€” rejected outright: "Another contract already starts on {date} ({status}). Edit or deactivate that contract first." Edit or deactivate the existing contract before trying again.
  • Backdated contract that overlaps a later contract β€” rejected outright: "This overlaps a later contract ({status}, starts {date}). Adjust the dates so the contracts do not overlap." Adjust the dates so the two contracts no longer overlap.
  • Overlaps an earlier contract β€” an Overlapping contract confirmation dialog appears instead of a hard rejection, since this case can be resolved automatically. It names the older contract and states that its end date will be set to the day before the new contract's start date. Click Confirm and the older contract is automatically end-dated as the new one saves, or Cancel to change the dates yourself instead.

Who Can See Pay (Compensation Permission)

Seeing what an employee is paid is a separate permission from managing employees. The View Compensation permission (User Levels β†’ Manpower β†’ Employee Records β†’ View Compensation) decides who sees pay on the employee record. A user level that has Employee Records access but not View Compensation can still open an employee and edit the name, contact details, department, shift and every other non-pay field.

Without View Compensation, every field, section and column stays where it is, but each amount shows as β‚± β€’β€’β€’β€’β€’β€’ with a lock. Hover the lock to see "You don't have permission to view compensation". Names, periods, dates and status are still shown, so you can see what exists without seeing how much:

  • On the detail page: the Monthly Rate, the contract cash-portion terms, the regularization rate, the custom Pag-IBIG amount and the projected bonus months show the lock. On the edit page the same fields show the lock and cannot be changed.
  • Contract History: dates, status and contract file stay; the amount columns show the lock, and the edit pencil and the New Contract action are hidden.
  • The Allowances, Deductions & Loans, Fixed Withholding Tax and Previous Employer sections list their rows (allowance and loan names, periods, effective dates, employer and period), with every amount, balance and total masked and the add / edit / delete actions hidden. The Salary Certificate action is hidden because the certificate states the salary.
  • The employee list has a Monthly Rate column (turn it on in Column Visibility); without the permission every cell shows the lock.
  • The Excel export keeps the Monthly Rate, Custom Daily Rate, Regularization Rate and cash-portion columns, but every cell reads Restricted. You can edit that file and import it again: a pay cell that still reads Restricted (or is blank) means "leave the pay as it is". Typing a real pay value in an existing employee's row still needs the permission. The Regularization Due list hides the rates.
Enforced by the system

The server never sends a real amount to these users: it sends an empty value plus a flag, and the screen draws the lock from the flag. Anything that reads the employee record for that user (the list, the detail page, the export, exports through integrations) gets the masked version, never a number that is merely covered up.

  • An employee always sees their own pay (payslip, My Employment Details).
  • Adding an employee needs it too. The Contract step of Add Employee holds the Monthly Rate and the contract file, so without View Compensation the step shows a notice instead of those fields and the last step cannot be submitted: ask an administrator to add the employee or to grant you access. When a new-employee registration is sent for approval, a reviewer without View Compensation sees the pay in the request masked, like any other pay change.
  • The seeded HR Administrator, HR Manager and Payroll Manager levels have it. Existing user levels that already had Employee Records access were given it automatically when the permission was introduced, so nothing changed on day one - remove it from the levels that must not see pay. Full-access roles always see pay.

Dispatch Status

An employee who is on an active dispatch today (see Managing Employee Dispatch) is marked on the list and on the profile.

  • The Dispatch column (turn it on in the column picker) shows a Dispatched badge with the destination.
  • The Dispatch filter narrows the list to Dispatched or Not dispatched, and the Excel export honours it.
  • The profile header shows the same Dispatched badge. It disappears the day the dispatch ends - the status is worked out from the dates, nothing to switch off.

Emergency Contact

Each employee has an Emergency contact (name, number, relationship and address) and, optionally, a Second Emergency Contact β€” a backup person to call if the first cannot be reached (name, relationship and number). HR edits both on the Personal tab of the edit page (the second one is its own group) and sees them under the Emergency Contact card on the employee page. Whether the employee may change it themselves is a company choice (Manpower β†’ HR Setup β†’ Employee Self-Service); until the company opens it, only HR can edit it.

Personal Details, Family and Background

Beyond the core record, HR keeps a fuller personal profile for each employee. Employees can maintain much of it themselves from My Profile; HR always sees and can edit all of it.

  • Personal details: Nickname, Place of birth, Nationality, Religion, Blood type, Mother's maiden name, Height (cm), Weight (kg), Personal email and Alternate mobile number. Height is accepted from 50 to 250 cm and weight from 20 to 300 kg. HR edits them on the Personal tab of the edit page and sees them under Personal Information on the employee page.
  • Permanent address: street, city, state / province, country and postal code, edited on the same Personal tab and shown as one line on the employee page.
  • Family and dependents, Education, Work history, Licenses and certifications: four sections on the employee page, each with an Add button and edit and remove buttons on every row. A family member can be marked Dependent or Beneficiary, only one spouse is allowed, and a license shows Expires soon (within 60 days) or Expired. The fields are the same as the employee sees on My Profile (see Family and Background Tab).

Editing the lists needs the same permission as editing the employee; without it the lists are read-only. When the Family and dependents or Education, work history and licenses change type needs approval (see Employee Change Approvals), an HR edit is submitted as a request instead of being saved, and the page tells you it was submitted for approval.

Info

Which of these items employees see on My Profile, and whether they change them right away or through approval, is set under Manpower β†’ HR Setup β†’Employee Self-Service. An item set to Hidden from My Profile disappears for the employee only: the data stays and HR still sees and edits it here.

Restricted Employees (Identity Masking)

Employee Records follows the same organization hierarchy used across Settings: if an employee's role outranks yours (they sit at a more senior level than you), their identity is hidden from you. The record is not removed from the list β€” it stays fully searchable and countable β€” only who they are is withheld.

  • On the employee list, the row's avatar becomes a generic person icon and the Full Name column reads Restricted instead of their name.
  • On the employee's detail page, the profile photo is replaced with the same generic icon and the name reads Restricted.
  • The Employee Code stays visible everywhere as the reference for a restricted record, and every other detail β€” department, position, branch, contract, schedule, and government IDs β€” remains visible as normal. Only the fields that reveal who the person is (name, username, email, contact number, photo) are withheld.
  • If this employee's own supervisor outranks you, the Supervisor column on the list (if shown) and the Supervisor link on the detail page both read Restricted β€” independently of whether the employee themselves is restricted from you.
  • Coworkers at your own level (peers) are never restricted β€” masking only applies to roles more senior than yours.
  • Searching by First Name or Last Name will not match a restricted employee; searching by Employee Code still works. See Search above.
  • The Excel export writes Restricted in the name, username, email, and contact number columns for a restricted row β€” the rest of that row's exported data is unchanged.
  • A full-access user (for example, a Super Admin) is never subject to this masking and always sees every employee's identity.

Actions on an Employee

The available buttons in the detail page header depend on the employee's state.

Reaching this page at all only takes view access to Employee Records. Edit and the Send Email Invite item need the Update permission for HRIS, and Delete needs the separate Delete permission β€” a role that only has view access (for example the seeded HR Viewer) opens an employee's record read-only, without either button.

When the employee is Active

  • Assign (dropdown):
    • Assign Leave
    • Assign Allowance
    • Assign Deduction
    • New Contract
  • Edit β€” open the edit form. Requires the HRIS Update permission; hidden without it.
  • Actions (dropdown):
    • Log in as this employee β€” open a session as this employee to see Ante exactly as they do. Shown only to Level 0 and Level 1 accounts, only for an employee who ranks below you, and only when the employee's Account Status is Activated (there is no account to sign in to before that). It works the same as on the Users page β€” the session is added to your account switcher, a banner offers Return to my account (which brings you back to this page), it ends after 8 hours, and everything is recorded in the audit trail. See Users β†’ Logging In as Another User.
    • Send Email Invite (reads Resend Email Invite once an invitation has already gone out once) β€” see Sending or Resending an Activation Email below. Requires the HRIS Update permission (same as Edit); hidden without it. Also hidden once the employee's Account Status is Activated; disabled when the employee has no email address.
    • Separate β€” start the separation process (see below). You cannot separate your own account: it is refused with You cannot separate your own account, even when the separation would go through an approval route.
    • Delete β€” deactivate the employee account (a confirmation dialog warns that this action will deactivate the account; the employee will appear as Inactive and can be restored). Requires the HRIS Delete permission; hidden without it.

Sending or Resending an Activation Email

From the employee's detail page, open Actions and click Send Email Invite (or Resend Email Invite, once one has already gone out) to email this employee their set-password activation link right away β€” the same link described in Account Activation above, freshly issued.

  • It's hidden once the employee's Account Status is Activated β€” there's nothing left to invite them to, and the action exists to set up a first login, not to reset a working account.
  • It's disabled when the employee has no email address on file, since there's nowhere to send it.
  • You only see a success message when the email actually went out. If delivery fails, you see an error instead, and the Account Status stays Not invited rather than being marked as sent.

Assigning a Leave Plan

Click Assign β†’ Assign Leave to open the Assign Leave Plan page for that employee.

  1. Select Leave Plan β€” search and choose the leave plan to assign. Only plans the employee doesn't have yet are listed; assigning a plan they already hold is rejected with "This employee is already assigned to this leave plan. Use Adjust Credits on the plan to add credits." Use Adjust Credits on the plan's card to add credits to an existing plan.
  2. Once a plan is selected, fill in its Credit Settings:
    • Total Annual Credits β€” total leave credits per year
    • Monthly Accrual Credits β€” added every month, on top of the renewal grant (leave 0 for none). This accrues every month regardless of the plan's Renewal Type β€” it is not limited to plans renewing monthly, and it stacks with whatever the plan's annual renewal grants.
    • Credits Given Upfront β€” credits given immediately upon assignment
    • Renewal Type β€” read-only, showing when the plan's annual credits renew (Hiring Anniversary, Start of Year, Monthly, or Custom Date). The renewal schedule β€” including the custom renewal date, when applicable β€” belongs to the leave plan and applies to every employee assigned to it; it is no longer set or edited per employee here. To change it, edit the leave plan itself (see Service Incentive Leaves).
  3. Click Assign Leave Plan to save.

See Service Incentive Leaves for how leave types and plans are configured, and how the Run renewals now action processes accruals and renewals company-wide.

When the employee is Separated

  • Re-Hire β€” restart employment; this takes you to the Add Contract page (in rehire mode) to record the new contract. The employee's prior separation is kept on record as history rather than erased β€” reports for the period it fell in (such as the BIR alphalist reason code) still reflect it correctly β€” and you can separate the employee again later if needed.
  • Cancel separation β€” use this instead when the separation was entered by mistake. The separation is removed as if it was never filed: the employee is active again and can sign in, the contract end date goes back (prefilled with the date it had before the separation; leave it empty for an open-ended contract), a draft final pay is voided, and the separation no longer appears in Separation Pay, payroll or BIR reports. Enter a reason; it is kept in the audit log. A separation with a released final pay can't be cancelled until that final pay is voided in Separation Pay.

A separation filed for a future date can be cancelled the same way before it takes effect β€” for example when the employee rescinds a resignation. Open the employee (still active, with the Separation on (date) badge) and choose Actions β†’ Cancel separation.

When the employee is Inactive (not separated)

  • Restore β€” reactivate the record (with a confirmation dialog).

Editing an Employee

  1. Open the employee, then click Edit.
  2. Update the fields you need.
  3. Save your changes.

Clicking Edit opens the edit tab that matches the detail tab you were on (for example, Edit from the Employment tab opens Work). Inside each tab the fields are arranged in aligned groups, each with its own heading β€” for example Personal information (with Mother's Maiden Name, Height and Weight), Present address, Permanent address, Emergency contact (with an Address field) and Second Emergency Contact on the Personal tab, and Government IDs and Contribution and tax settings on the Government tab. The present and permanent addresses are separate groups; the Permanent address header has a Copy from present address button that fills it in from the present address.

The edit form is organized into tabs. Tags lives on the Work tab, in the same place as Branch, Schedule, and Payroll Group β€” see Step 2: Position & organisation above for how the picker works. The tabs are Personal, Work, Government, Bank, and Documents.

The Bank tab is the Bank Accounts section: add, edit, and end accounts there. The employee form no longer has its own bank name and account number boxes, so saving the form never changes bank details. For a Probationary employee, the Work tab also holds the Regularization date and rate.

Profile photo

The first group on the Personal tab is Profile photo. The photo shows wherever the employee appears: the directory, approvals, chats and the org chart.

  • Upload photo (or Change photo when one exists) β€” pick a JPG, PNG, GIF or WebP image of up to 2 MB. The photo is saved immediately; you do not need to click Save Changes, and anything you have already typed in the form is kept.
  • Remove photo β€” asks you to confirm, then removes the photo immediately; the employee's initials show instead.

Payroll attribution: cost centre

On the Work tab, the Payroll attribution block holds the employee's cost centre. It is saved on its own (it has a Save button in the group's header and does not wait for the main form's Save Changes):

Cost centreselect
The employee's own cost centre from Treasury (active ones only). The payroll, disbursement and recharge journals group this employee's costs under it. Leave it blank to use the department's cost centre. The employee list can show it as a column and filter by it, and the Excel export and import carry a Cost Centre column (blank on import keeps the current value; an unknown code is rejected). The journal reads it when it is generated.

The employee detail page shows the cost centre. The cash portion of net pay is not set here: it is agreed on the employee's contract (see Cash portion on the contract).

Time Tracker β€” per-employee allowed IPs

On the Work tab you may see a Time Tracker β€” Allowed IPs section. It appears only when your company has Restrict to whitelisted IPs turned on (HR β†’ HR Setup β†’ Settings).

Use it to let this one employee clock in/out from a network that isn't on the company-wide whitelist β€” for example, a field employee's home or branch connection:

  • Add an IP: type a single IP (e.g. 203.0.113.5) or a range (e.g. 203.0.113.0/24) and click Add, or click Add my current IP.
  • Remove an IP: click the Γ— on any listed address.

An employee can clock in/out if the network matches either the company whitelist or their own list here. Changes save with the rest of the employee record.

Company-Paid Tax (Gross-Up) Override

On the Work tab, the Company-paid tax (gross-up) box lets you treat this one employee differently from their payroll group. By default an employee follows the group's company-paid tax setting β€” leave the box on Same as the payroll group and nothing changes. The note under the box reads "Use only when this employee is different from their payroll group." Pick one of these options:

Same as the payroll groupoption
The default. The employee follows whatever the payroll group is set to.
Employee pays (normal payroll)option
Tax and SSS/PhilHealth/Pag-IBIG are deducted from this employee's pay, even if the payroll group has the company pay them for everyone else.
Company pays the taxoption
The company pays this employee's withholding tax; the employee still pays their own SSS / PhilHealth / Pag-IBIG.
Company pays the tax and SSS/PhilHealth/Pag-IBIGoption
The company also pays this employee's SSS / PhilHealth / Pag-IBIG share.

An option other than Same as the payroll group wins over the payroll group for this employee only, and is saved with the rest of the employee record. Payroll applies it the next time it computes the employee's cutoff. The company-paid amount then shows as a Tax gross-up – pay (company-paid) line on Salary Detail and on the payslip; the options themselves are explained in full under Payroll Group.

Projected Bonus Tax Smoothing

On the Government tab, Projected Bonus Tax Smoothing lets you spread the income tax on an employee's expected 13th month pay and bonuses across the year instead of collecting it all at once in December.

13th month pay and bonuses are tax-free up to the other-benefits ceiling β€” β‚±90,000 a year by default, or your company's own override if it has set one β€” and anything above that is taxable. For an employee whose bonus will go over that ceiling, this setting has payroll withhold the tax on the excess a little on every payday, instead of taking it all at once in the year-end tax adjustment. The total tax for the year is exactly the same either way β€” only the timing changes. Most employees never cross the ceiling and don't need this: leave it blank to turn it off.

The Government tab β€” Projected Bonus Tax Smoothing sits above the Previous Employer (tax year) card
  1. Open the employee, click Edit, then the Government tab.
  2. Under Projected Bonus Tax Smoothing, enter Expected 13th month + bonus (months of salary) β€” for example, 1.85 means one month of 13th month pay plus 0.85 of a month in bonuses. The value must be greater than 0 and no more than 24.
  3. Save the employee.

As you type, a What this does for this employee block shows the live math using the employee's own monthly rate: the expected 13th month + bonus, less the tax-free ceiling, the taxable excess for the year, and the amount that gets added to the tax computation on each payday. If the expected amount stays within the ceiling, the block says so instead and nothing will be withheld in advance. If the employee has no monthly rate on an active contract yet, the block explains that an example can't be shown β€” and if the block doesn't appear on the Government tab at all, it's because ANTE couldn't work out this company's ceiling or withholding schedule for the current date; the setting is simply hidden rather than showing broken numbers, and no employee data is affected.

Warning

This setting only raises the tax withheld β€” it is not extra pay, and it never appears as income on the payslip, BIR Form 2316, or the alphalist. The December tax adjustment counts everything already withheld for the year, so nothing is taxed twice, and if the employee's actual bonus turns out different from this estimate, December settles the difference.

The employee's detail page shows the value as Projected bonus tax smoothing β€” N months of salary on the Government card, or as Off when it isn't set (see Viewing an Employee). When the setting changed a cutoff's tax, the Tax line on the Salary Detail Summary tab carries a matching note.

Non-Resident Alien (Fringe Benefit Tax)

An employee who is not engaged in trade or business in the Philippines is taxed at the non-resident alien fringe benefit rate (25%, with a 75% divisor) instead of 35%. Open the employee, click Edit, then the Government tab and switch Non-resident alien (FBT 25% / 75%) on. The employee's Pay & Tax tab shows the same flag as Yes or No. Both need the permission to see pay. See Fringe Benefit Tax.

Previous Employer (tax year)

On the Government tab, a Previous Employer (tax year) card lets HR record what a mid-year hire's prior employer's BIR Form 2316 shows β€” one consolidated record per tax year. ANTE folds this into the employee's annual tax computation everywhere it's used: the Alphalist Breakdown, the BIR 2316 certificate, and payroll's year-end tax true-up β€” so a mid-year hire isn't taxed as if they only earned what this company paid them. It sits further down the Government tab, below Projected Bonus Tax Smoothing β€” scroll down to reach it.

  1. Open the employee, click Edit, then the Government tab.
  2. Pick the Tax year the record belongs to β€” last year, this year, or next year.
  3. Fill in what the prior employer's certificate shows:
    Employer name
    Employer TIN
    Employer address
    ZIP code
    Period fromdate
    Period todate
    Taxable compensation
    Tax withheld
    Non-taxable compensation
    13th month & other benefits
    Notes
    No single field is required, but you must fill in at least one before you can save, and Period from cannot be after Period to.
  4. Click Save previous employer.

Once saved, a Delete button appears next to Save β€” click it (then confirm in the dialog) to remove the record for the selected tax year. This cannot be undone.

Warning

Recording a previous-employer income for the year does more than print Part III of the 2316 β€” it changes the employee's numbers: their prior 13th month and other benefits share the same annual β‚±90,000 (or configured) exemption pool as this company's, their prior taxable compensation joins the annual tax-due computation, their prior tax withheld is credited toward the year's total, and they are no longer eligible for substituted filing β€” they must file their own BIR Form 1700. Only enter a record when the employee genuinely had a previous employer within the same tax year.

Separating an Employee

  1. Open an active employee and click Separate.
  2. In the Separate Employee dialog:
    • Separation Type * β€” choose from the list (or use + Add new type to create one on the spot; the inline form also offers an optional BIR reason code β€” T (Terminated / Transferred out), R (Retirement), D (Death), or TR (Transferred) β€” used to fill the "reason of separation" column on the Alphalist; leave it unset and the type is reported as T)
    • Effectivity Date *
    • Attachment (optional)
    • Remarks (optional)
  3. Confirm with Separate Employee.

The separation takes effect on its Effectivity Date. The contract end date is set to that date right away, but until then the employee stays active, keeps working, and can still sign in; their profile shows a Separation on (date) badge. At 12:00 AM on the effectivity date, login is refused and the employee is deactivated and logged out of all devices. A separation dated today or earlier takes effect immediately. Once separated, the employee appears on Separation Pay's Process tab, where you compute and release their final pay. To set or change an existing separation type's BIR reason code later (not just for a brand-new type), use the Separation Pay Settings tab.

When the effectivity date falls inside a posted payroll

If the effectivity date you enter falls within an already-posted payroll period that includes this employee, a warning panel appears in the dialog:

"This effectivity date falls within an already-posted payroll period (date range shown). The posted payroll is locked and will not change. Click Confirm Separation to record the separation with this date anyway."

The button label changes from Separate Employee to Confirm Separation. Clicking it records the separation with the true effectivity date. The posted payroll itself is not affected β€” its employee list, on-hold section, totals, exports, and bank files remain exactly as they were at the time of posting. The correct resignation date is still recorded for 13th-month proration, final pay, and statutory calculations.

If you change the effectivity date, the warning panel clears and the standard check runs again.

Importing Employees in Bulk

Click Import on the list to open the Import Employees workflow. It runs in four steps shown as a stepper:

Step 1: Upload File

  1. Click Download Template to get the Excel template.
  2. Fill in the employee data.
  3. Drag and drop your file (or click to browse β€” .xlsx, .xls, .csv).
  4. Click Upload & Validate.

Write dates year-first. Birthdate, Start Date and End Date must read 2026-01-13 or 2026/01/13 β€” year, then month, then day. A real Excel date cell works too. What ANTE will not accept is a day-first or month-first date like 13/01/2026, because 03/02 and 02/03 are impossible to tell apart, and guessing would put the wrong date on the record. If a date can't be read, the upload stops and names the row and column so you can correct that cell β€” for example Row 7: Birthdate (yyyy/mm/dd) is not a date we can read ("N/A"). Nothing is imported until you fix it and upload again.

The template's Role/Position column is a dropdown that lists each role as Role - Department (for example General Manager - Market Support); a role with no department shows just its name. Pick the label so the employee lands in that department's role. You can still type a bare role name, but only when no other department has a role with that name β€” otherwise the row is flagged as ambiguous and the error lists the Role - Department choices to use. The employee export writes the same label in its Role/Position column, so an exported file can be re-imported as is.

The template's Tags column takes a comma-, semicolon-, or pipe-separated list of hashtags, e.g. #factory, #set-a (the leading # is optional). Names are stored lowercase and hyphenated, so Work From Home becomes #work-from-home. A tag that doesn't exist yet is created automatically β€” you don't have to set up the vocabulary in Employee Tags first. When the template already has existing tags in your company, it lists them near the top of the instructions sheet so you can copy the exact spelling instead of accidentally creating a near-duplicate.

The last two template columns are Regularization Date and Regularization Rate (Optional), used for Probationary employees (see Regularization). A new Probationary hire with no date defaults to the start date plus 6 months. The date must be after the start date, the rate must be above zero, and leaving either blank on an existing employee keeps what is stored. Values on a row that isn't Probationary are stored but never acted on. The Regularization Rate column needs the permission to update employee records.

After them come the contract's cash terms: Cash Portion (Optional), Cash Paid In (Optional) (First, Second, Both, or "Same as payroll group") and All Net Pay To Bank (Optional) (Yes or No). Blank keeps what the contract already has, text that cannot be read is refused at upload, and the columns need the View Compensation permission, like the Monthly Rate. In an export made by someone without it, these cells (and the Monthly Rate) read Restricted; importing that file back leaves the pay unchanged.

The Monthly Rate can be 0 or more. For a new employee a rate of 0 means they are not paid through ANTE, and the row is accepted with the warning Monthly Rate is 0: nothing will be computed or paid for this employee. A new employee row cannot leave it as Restricted. On an existing employee, 0 keeps the current rate, with the warning Monthly Rate 0 keeps this employee's current rate. Enter the new rate to change it. A negative rate is refused.

The Bank Name and Bank Account Number columns still work for the masterlist, and they land in the employee's Bank Accounts. A masked number (for example one exported without the View Full Account Numbers permission) is treated as unchanged. To load many accounts with dates, use the Bank Accounts import instead.

Leaving the Tags cell blank on a row that matches an existing employee (by Employee Code) leaves that employee's current tags exactly as they are β€” it does not clear them. Filling the cell always replaces the employee's whole tag set with what the cell says.

After the cash-term columns come 26 optional personal-profile columns: Nickname, Place of Birth, Nationality, Religion, Blood Type (a dropdown), Mother's Maiden Name, Height (cm), Weight (kg), Personal Email, Alternate Mobile, the permanent address (Permanent Street, Permanent City / Town, Permanent State / Province, Permanent Country, Permanent Postal Code), the emergency contact (Emergency Contact Name, Relationship, Number, Address), the second contact (Emergency Contact 2 Name, Relationship, Number) and the highest education (Highest Education Level (a dropdown), Course / Degree, School, Year Graduated).

Leaving one of these cells blank on an existing employee leaves the stored value alone β€” it never clears it. A bad value is an error on that row: a blood type that is not in the list, an invalid e-mail address, a height outside 50–250 cm or a weight outside 20–300 kg, an unknown education level, an education level without a school, or a year that cannot be read.

The education level accepts the codes, the labels and everyday wording such as College Graduate, College Undergraduate, Technical/Vocational or Senior High School Graduate; a blank, 0 or N/A means no education. A level plus a school creates or updates one education record: the same level and school updates the course and year, otherwise a new record is added. The employee's other education records are never touched, and an employee can hold at most 20 records.

Step 2: Validate

The system checks every row and reports Total Rows, Valid, Errors, and Warnings. Rows with errors are skipped; rows with warnings can be approved. Review the results, then continue.

If a row's Role/Position, Branch, Schedule Code, or Payroll Group Code matches more than one live record with that same name or code, the row is flagged as an error right here β€” for example Role 'General Manager' is ambiguous β€” 2 roles share that name. Pick the "Role - Department" entry from the template dropdown: 'General Manager - Market Support', 'General Manager - Sales'. For a role, pick the Role - Department label it lists. If two roles have the same name in the same department, the error asks you to rename one of them in Settings β†’ Roles instead. This is caught during validation, before anything is created, so a duplicated name elsewhere in the company can no longer let some rows in the batch import successfully while later ones fail partway through. Rename the duplicate (or make the reference unique) and re-upload.

A Tags cell is previewed as chips in the results table, so you see the parsed tags rather than the raw text. If any of them will be created (rather than reused), the row carries a warning like New tag(s) will be created: #factory β€” this doesn't block approval, it just tells you before you commit the batch. A row is rejected outright only if the cell contains no usable tag name, or names more than 20 tags.

Step 3: Process

Optionally check Send activation emails now β€” it's off by default. Leave it unchecked to create the employee accounts and their activation invitations without emailing anyone yet; check it if you want ANTE to email each imported employee their activation link immediately. Click Process Import to create the valid (and approved) employees.

Step 4: Complete

A summary shows Employees Created and Skipped counts. If you left Send activation emails now unchecked, a note tells you how many activation invitations were created without sending an email β€” those employees' Account Status reads Not invited until someone sends it. Use Import Another to run the workflow again.

Every imported employee is created inactive with an activation invitation, the same as adding one employee at a time β€” make sure every row has a valid email address. Whenever you're ready to send (or resend) an activation email, do it either from that employee's own record (Actions β†’ Send Email Invite) or from Settings β†’ User Invites, where each invitation's Resend button sends that employee the correct set-your-password activation link. A row without an email is still imported as an employee, but stays Not invited with no way to notify them until an administrator adds an email for that account.

Exporting Employees

Click Export on the list to download an .xlsx file. The export matches the employees currently shown β€” it honors your active Status filter, Employment Type, Branch, Department, Tags (including the Any tag / All tags choice), and search.

Clicking Export opens the Export employees dialog ("The filters and search applied to the list are applied to the file"), with two choices:

  • Complete details β€” every detail of each employee, in the import layout, so the file can be edited and imported back.
  • Selected columns β€” only the columns you tick, in your order. It starts with the columns currently shown in the list. Use it for reports; this file cannot be imported back.

The rest of this section describes the complete file.

The download respects the same identity masking as the list and detail page β€” a row for an employee who outranks you exports with Restricted in place of their name, username, email, and contact number, while every other column is unaffected.

Tags is included as its own column β€” the same position it holds in the import template, right after Bank Account Number β€” with an employee's tags written as #factory, #set-a. It isn't identity data, so it exports even for a Restricted row.

The export also includes the Regularization Date and Regularization Rate columns, and the bank account number is shown as the last four digits only unless you hold the View Full Account Numbers permission. Exporting needs the permission to update employee records.

The same 26 personal-profile columns (personal details, permanent address, both emergency contacts and the education columns) are exported before these last columns; the education columns carry the employee's highest education, so an exported file can be edited and imported again.

The file includes Job Grade and Title Rank columns with the employee's current job grade and its title rank, and it follows the Job Grade filter.

The file's last three columns are Rank, Level, and Tenure β€” the same fields as the list's opt-in columns of the same name. They're always included in the download, whether or not you've turned those columns on in Column Visibility.

Employees in Multibook

When the company is connected to Multibook, employees can become Multibook business partners in the employee category, so reimbursements and payments to them can be booked there. This is switched off by default and is turned on under Settings β†’ Multibook β†’ Employees. Only identity is sent: employee code, name, e-mail, phone and country. Government IDs, bank details and pay never leave ANTE. An employee who already exists in Multibook is linked, never duplicated.

The employee list gets a Multibook column and the employee page shows chips beside the account status:

ChipMeaning
Multibook partner E000045The employee is linked to that Multibook partner.
Partner being createdThe partner is queued and goes up with the next employee sync.
Possible Multibook matchAn existing Multibook employee looks like this person by e-mail or name only. Nothing is linked automatically: click the chip to open Multibook business partners, searched for this person, and link it there. The chip for a named problem (such as Code already used in Multibook) opens the same place.
Not in Multibook, or a reason such as No employee code or Code already used in MultibookThe employee has no partner yet, and why.
Has a Multibook ER login / No Multibook ER loginWhether the person can file reimbursements as themselves in Multibook. ER logins are only created when that option is on, and each uses one Multibook user licence.
Approving route: set in MultibookWho approves a person's claims is a Multibook administrator task; ANTE does not check it.

A separated employee's Multibook partner is kept by default, because a partner carries history there; a setting can delete it instead.

Tips

πŸ“Œ Set the Employment Status before the dates β€” non-Regular statuses require an End Date.

πŸ“Œ Use the Status filter set to Not Yet Set to find accounts that still need to be activated as employees.

πŸ“Œ Accurate employee records feed payroll and timekeeping directly β€” keep the contract, schedule, and payroll group up to date.

πŸ“Œ When ANTE adds new hidden-by-default columns to this list, they start out hidden for everyone β€” even if you'd already customized which columns show. Your view won't gain a new column without you choosing to reveal it from Column Visibility.

How It Connects

Set up first

  • Job Grades β€” the pay level you give an employee comes from the company job grade list; grade-based allowances then pay by it.
  • Payroll Group β€” every employee is assigned one, which sets the pay frequency and the cutoffs their salary follows.
  • Schedule Management β€” the weekly schedule you pick in the employee’s assignment comes from here.
  • Service Incentive Leaves β€” the leave plans you assign to an employee and their leave balances are built from these leave types.
  • Allowance β€” the allowance types and plans you can attach to an employee’s record.
  • Deduction β€” the deduction types and plans (including loans) you can attach to an employee’s record.
  • Employee Tags β€” the hashtags you can put on employees to group and filter them.
  • HR Settings β€” the username convention decides how Add Employee suggests a login.
  • Employee Change Approvals β€” decides whether Add Employee saves at once or files a New employee registration for approval.
  • Approval Configuration β€” the 1st to 4th approvers you pick for a new employee, and the backups and chains behind them.

Gets its data from

  • Applicants β€” an applicant who is hired becomes an employee account, and the hiring history stays linked to the record.
  • Profile Change Requests β€” HR-approved self-service edits are applied to the employee record, and an approved New employee registration creates the employee.

Feeds into

  • Individual Scheduling β€” shifts are assigned per day on top of the schedule set in the employee’s assignment.
  • Payroll Time Keeping β€” the timesheet is built per employee from their schedule, contract and leave.
  • Payroll Center β€” salaries are computed from each employee’s rate, allowances, deductions and bank account.
  • Government Contribution Reports β€” contributions are reported from each employee’s government numbers and pay.
  • Separation Pay β€” a separated employee’s final pay is computed from the separation you record on their record.
  • Team Management β€” employees on the list can be grouped into named teams.