ANTE User Manual

Approval Configuration

Approval Configuration decides who approves what, in what order, and who steps in when an approver is away. It covers three modules: Filings (leave, overtime, official business, certificate of attendance, schedule adjustment, rest day work and schedule swap), Employee changes and the Payroll approval of a cutoff. For filings, instead of one person signing off, you can build a chain of stages — for example the immediate superior recommends, then the department manager gives the final approval.

Open it from Manpower → Settings → Approval Configuration. Changing a chain only affects filings submitted afterwards; a filing already in progress keeps the stages it was submitted with.

Everything about approvers lives on this one page, in five tabs. There is one idea to remember: an override is an approval chain that names specific employees. Overrides always come before the department and company approval flows. A flow can cover a whole department or an employee group you describe by rules, such as everyone tagged drivers.

The same page also holds the approval chains for employee changes and for the payroll cutoff approval. Pick the module from the Approval module list on the left of the page (Filings, Employee changes, Payroll approval); see Approval Modules.

The Five Tabs

TabWhat it is for
Approval flowThe department, company and employee-group approval flows in one priority list (drag to reorder; the first match wins): stages, who the flow applies to (a department or an employee group), filing types, plus Level backups on each stage. A line reminds you how many overrides always come first.
OverridesApproval steps for specific employees, with Excel import and export.
Backup approversPersonal backups for an approver: "Juan's backups are Maria and Pedro".
Who approves?A check: pick an employee and a filing type and see who would approve, who is away, and which backups are active today.
Filing types & rulesWhich filing types are switched on, and the rules about who may file and how often.
Info

Anyone with Filing Approval access can view the page. Changing flows, overrides and backups needs the Filing Approval update permission. An employee's record also shows their overrides to anyone with HRIS access.

Approval Modules

Filings, employee changes and the payroll cutoff approval all follow the same kind of chain: stages that recommend or approve, approvers, backups, later-stage override and one shared inbox (the header Approvals panel). The Approval module list on the left of this page chooses which set of chains you are editing. Each module shows a short description and how many chains it has (No chains when none). On a narrow screen the list sits above the tabs, and the module's own tabs (Approval flow, Overrides and the rest) are in the bar to the right of it. The choice is kept in the address (?module=), so a link can open the page on the right module.

ModuleWhat the chain approvesChain fields that differ
FilingsLeave, overtime, official business, certificate of attendance, schedule adjustment, rest day work and schedule swap.Filing types narrows a chain to some types; empty means all.
Employee changesA change to an employee record held for approval: personal information, government IDs, bank account, compensation, employment status, department and assignment, family, education, separation, each employee custom field, and a new employee registration.Change types narrows a chain to some change types; empty means all. The chain is chosen from the employee the change is about. For a new employee it is chosen from the department and role being created, and the preparer's superior.
Payroll approvalThe payroll run of a cutoff, from For Approval to Approved.One request type, Payroll cutoff. Chains cover the whole company; the person who submitted the run counts as the "employee" for picking a chain.

Which chain applies works as described under Which Chain Applies: an override for the employee first, then the flows from top to bottom, then the default (the superior approves; for payroll, a Director of your Human Resources department).

Info

With no chains, Employee changes save directly until a chain covers them, and a submitted payroll run is held until a payroll chain exists.

Approvers you can pick

Besides the approver types listed under Stage Fields, employee changes and payroll offer:

  • Anyone with a user level: any one person whose role holds the chosen user level can act. This is how the former Employee Change Approvals workflows were converted, one stage per step.
  • Anyone at a position rank, optionally in a chosen Department. Pick Human Resources and the rank Director to mean "a Director of Human Resources". Leave the department empty to mean the employee's own department.

Who can never decide

  • Filings: the employee the filing is for never approves it.
  • Employee changes: neither the person who prepared the change nor the employee it is about.
  • Payroll approval: not the person who submitted the run. The exception is a user with full access or a top-level role, who may decide outside the chain; that is disclosed before they confirm, recorded, and the approver being replaced is notified (see Payroll Approvers).

Backups and later-stage override per module

A later stage may act for this stage works the same in every module: the later approver sees the request under On behalf of others, can decide the earlier stage (Approve on behalf, Recommend on behalf, or Send back on behalf for payroll), and still signs their own stage. Personal backups on the Backup approvers tab have a Modules filter: leave it empty for every module, or choose the modules where the backup may act. The Filing types narrowing still applies inside Filings.

Info

A chain change affects requests submitted afterwards. A request already in progress keeps the stages it started with; a payroll run waiting for approval is re-routed to the new chain from its first undecided stage.

What Happens Without a Chain

Until you add a chain, every filing follows the default flow: the employee's immediate superior (the person in their Reports To field) approves, in one stage. A filing whose employee has no superior recorded is never approved automatically — it is held for HR. See Filings on hold (Needs attention).

Which Chain Applies

There are two tiers, and the first one that covers the employee and the filing type wins.

  1. Overrides first. If an override names the employee, its steps are used. An override for one filing type (say, Overtime) beats an all-types override.
  2. Then the approval flows, which are the department, company and employee-group flows on the Approval flow tab. They are checked from top to bottom in the list, and the first one that covers the employee and the filing type wins: a department flow covers the employee's department (or a parent department, or the whole company), and an employee-group flow covers the employee when they match its rules today. Drag a flow to change its priority.
  3. No match: the default flow above, where the immediate superior approves.

Under the Approval chains heading the Approval flow tab shows the same order as a numbered strip, How a chain is chosen: (1) overrides always come first, (2) flows are checked top to bottom (department or employee group), (3) the first matching flow wins, and with no match the immediate superior approves. A Learn more link opens this section.

Each employee and filing type is in at most one override. Two all-types overrides, or two overrides that share a filing type, cannot name the same employee: saving is refused with a message naming the other override.

Adding a Chain

  1. Open Approval Configuration

    Go to Manpower → Settings → Approval Configuration, stay on the Approval flow tab and click Add chain. Department and company flows are listed under Approval chains in priority order, with who they apply to (a department, or the rule summary and number of employees for an employee group), the filing types they cover, and their stages in order. Specific employees are handled on the Overrides tab instead.

  2. Name the chain and set its scope

    Under Who it applies to choose A department or An employee group (see Employee Group Flows). For a department, choose the Department (leave it empty for the company-wide default); for an employee group, describe the group with rules. Enter the Chain name, pick the Filing types it covers (leave empty for all) and keep Active on.

  3. Define the stages

    Click Add stage for each step. Stage 1 acts first; use the arrows to reorder or Remove stage to delete one. A chain can have at most 10 stages.

  4. Save

    Click Save chain. You are asked to fix anything missing — a chain name, a stage name, an approver on every stage, and an Approve stage as the last stage.

Tip

The dialog guides you as you build. How approval chains work opens a short walkthrough with an example. When adding a chain, Start from a template (Single approver, Supervisor then manager, Supervisor, manager, director) fills in the stages for you. The Flow preview at the top updates as you edit, showing who acts at each stage and what happens if they are away, and flags problems such as a last stage that only recommends (with a Make it Approve shortcut). Each field has a plain-language note underneath. New chains start with Active on.

On the list, each chain has an Active switch (turn a chain off without deleting it), Edit, and Delete. Inactive chains are labelled Inactive and are ignored when filings are submitted.

Employee Group Flows

A flow does not have to follow the org chart. Choose An employee group under Who it applies to and describe the people it covers by their attributes instead of a department. An employee-group flow has the same stages, backups and away-handling as any other flow; only the question "who does it cover?" is answered by rules.

UseWhen
A department flowEveryone in a department (and its sub-departments) follows the same approvers.
An employee-group flowThe people share something that cuts across departments: a tag such as drivers, a position rank, a branch, probationary status, a payroll group.
An overrideYou are naming particular people, one by one, and they must beat every flow.

Describing the Group

The rules use the same builder as Auto-Assign Rules. Each line reads WHERE a field, an operator and one or more values. Add Condition adds another line to the same group, and all of its lines must be true (AND). Add Group adds another group (OR): matching any one group is enough. You can build conditions on the employee tag, position, position rank, grade, branch, department (with sub-departments), employment status, payroll group, schedule, gender, civil status, age, tenure, hire date and your own employee custom fields.

Who it applies to*
A department or An employee group. With an employee group the hint reads "Who this flow covers, e.g. Tag is #drivers and Employment status is Probationary."
Conditions*
One or more WHERE lines. The dialog shows N employees match today. as you build the group, so you can see at once whether the rules catch the people you expect.
Chain name
Left empty, the name is filled in for you as Group: <rule summary> · <filing types>, for example "Group: Employee tag is drivers · Overtime".
Filing types, stages, Active
The same as for a department flow.

Below the rules the dialog shows the priority line (for example "Priority #1 of 4: chains above it win where they overlap") and Takes over: which employees and filing types this flow would take from the flows or the default that cover them today. If a flow above it already covers all of them, the dialog warns that it would never be used and suggests moving it up after saving.

Where an Employee-Group Flow Sits

Employee-group flows live in the same drag-to-reorder list as department flows, so the first match wins across both kinds. A new employee-group flow is added at the top of the flows, because a rule-based flow is usually the more specific one; drag it down if a department flow should win in some overlap. Overrides still beat all of them.

On the list, an employee-group card shows the rule summary and N employees. The coverage strip above the list adds a line such as "M employees follow employee-group flows".

Example: Drivers

Overtime for drivers should go to the Fleet supervisor and then the Operations manager, wherever the drivers sit in the org chart.

  1. Tag the drivers

    Give each driver the drivers tag in Employee Tags.

  2. Add the flow

    On Approval flow click Add chain, choose An employee group, and set WHERE Employee tag is drivers. The dialog shows how many employees match today. Pick Overtime as the filing type.

  3. Add the two stages

    Stage 1: Recommend, approver A named person (the Fleet supervisor). Stage 2: Approve, approver A named person (the Operations manager). Save the chain. The name is filled in as "Group: Employee tag is drivers · Overtime".

Who approves an overtime filing
EmployeeWhyApprovers
Ramon (tagged drivers, Warehouse department)Matches the group; no overrideFleet supervisor, then Operations manager
Ramon, with an override for OvertimeOverrides always come firstThe override's steps
Ramon, tag removed todayNo longer matches the group; the Warehouse department flow appliesThe department flow's approvers
Ana (not tagged, no flow covers her)No matchHer immediate superior
Overtime filings only; the same group has no effect on Leave unless you add that filing type.

Matching Is Live

Membership is checked each time a filing is submitted, not when the flow is saved. Tag an employee as a driver (or change their branch, employment status, payroll group and so on) and their next filings follow the matching flow, with no edit to the flow. Filings already submitted keep the approvers they were submitted with.

Info

On an employee's record (Approvers section) and in the Who approves? tab, the source reads Employee group ("An employee-group flow they belong to"), next to the flow's priority, so you can tell why a flow was chosen.

Stage Fields

Stage name*
What approvers and employees see, for example "Manager approval".
Stage type*
Recommend passes the filing upward; Approve signs it off. The last stage must be Approve.
Approver*
Who acts at this stage: Immediate superior, Anyone with a role, Anyone at a position rank (Executive, Director, Manager, Senior, or Staff), or A named person. Employee changes and payroll also offer Anyone with a user level and a position rank in a chosen department (see Approvers you can pick). To give specific employees their own approvers, use an override.
Levels up
For Immediate superior: 1 is the employee's direct superior, 2 is that person's superior, and so on.
Role / Position rank / Person
Appears for the matching approver type and is required for it.
Only people from the employee's own department
For role and position-rank approvers: limits approvers to the filer's own department.
Allow this stage to reject the filing
Recommend stages only. When on, the approver can Reject and end the chain. When off, they can only Decline to recommend: the filing still moves on to the next stage, flagged as not recommended.
If no one is available
What to do when every approver of the level is away and no backup can act (approved leave, or the stage waited too long): Escalate up the reporting line skips a recommend stage, or hands a final stage to the absent approver's own superior; Hold for HR keeps waiting and flags the filing. The old single "Delegate" option no longer exists: wherever a chain used it, it was converted automatically into an "Only while on leave" level backup with Hold, which behaves the same.
Level backups
Up to five people who may approve this level in place of its approvers. See Level Backups.
Also allow each approver's personal backups
On by default. When on, the personal backups set on the Backup approvers tab for each approver of this level can also act. Turn it off for a level that only the named people may decide.
Escalate after (hours)
Optional time limit. If a stage sits untouched this long, the away-handling is applied.
Warning

A stage with nobody to act — an employee with no superior, an empty role or rank, a departed approver — is never skipped or escalated. The filing is held for HR instead. Away-handling only applies when a person exists but cannot act.

Stage typeApprover seesEffect
RecommendRecommend, and Reject or Decline to recommendMoves the filing to the next stage; nothing reaches payroll yet
Approve (final)Approve and RejectApproves the filing; only now does it reach payroll and timekeeping

Later-Stage Override

Every stage has the option A later stage may act for this stage. When it is on, anyone who approves a later stage of the same chain (for example the director) may also approve or reject this stage without waiting for its own approver. The filing then moves on normally: only this stage is decided, the later approver still signs their own stage. The trail reads "Approved by ... on behalf of stage N" and the stage's own approver is notified. The last stage has no later stage, so the option is not offered there.

Info

Changing a chain or an override does not rewrite decisions already taken. A filing already in progress keeps the steps it was submitted with.

Level Backups

Every level of a chain can have Level backups: up to five people who may approve (or reject) that level in place of its approvers. They are set in the chain dialog, under the stage, and apply to everyone the chain governs.

Person*
An active employee. Someone who has left the company is refused.
When*
Anytime: always allowed to act, alongside the approvers. Only while on leave: allowed only while every approver of the level is away on approved leave. Between dates: allowed only from a start date to an end date.
Tip

Use a level backup for a standing arrangement, such as "the HR manager can always approve the director level". Use a personal backup (next sections) for "Juan has two people who cover for him everywhere he approves".

Overrides

An override gives specific employees their own approval steps, for example "the finance team is approved by Ana, then by the CFO". It is the same kind of chain as a department flow, with the same stages, but it names the employees it covers. It always comes before the approval flows: the people it names follow its steps, and everyone else follows the Approval flow tab. The immediate superior is still the default approver wherever no override or flow applies, and an Immediate superior stage still points at the person in Reports To.

The Overrides tab shows the overrides with their name, the filing types they cover (or all types), their steps and the employees in them. Use Find the override a person is in (type an employee or override name) and the Filing type filter to locate one. New override, Edit and Delete work like chains; deleting an override sends its employees back to the approval flows, and filings already in progress keep their current steps.

Employees
The people the override covers. An employee can be in several overrides as long as they do not overlap on a filing type.
Filing types
Leave empty for every type. A filing-type override beats an all-types override for the same employee.
Stages
The same stages, approvers, backups and away-handling as a department flow.
Warning

One employee and filing type can only be in one override. If an override would clash with another (two all-types overrides, or two that share a filing type, naming the same employee), saving is refused and the message names the other override.

  1. Create an override

    On the Overrides tab click New override, pick the employees, the filing types (or leave empty for all), and add the stages. Save.

  2. Import or export in bulk

    Export and Import overrides sit at the right end of the tab bar while the Overrides tab is open, and use an Excel file. Columns: Employee Code, Filing Type (blank = every type), and 1st to 5th Approver Code. Employees with the same approvers share one override. On import, each listed employee and filing type is moved into the override for its approvers (created if none exists) and out of any other override for that type; overrides left with nobody are deleted, and blank approver cells are skipped. The review screen shows, for every row, the override it lands in or New override, and nothing is saved until you confirm. Download current overrides gives you the file to edit.

Info

Export only writes overrides made of named people. Overrides that use a role, a position rank or the immediate superior go on a Not exported sheet, because those cannot be expressed as approver codes.

On the employee record

The Approvers section of an employee record (Employment tab) shows their Immediate superior (read-only here; change it under Edit employee, Reports to), the employee's override(s) with Set up, Edit and Remove, and a who-approves preview for each filing type. When you add an employee, the 1st to 4th approvers chosen in Leave & approvers become their all-types override: they join the override with exactly those steps, or a new one is created.

Tip

Employees who used to have assigned approvers were converted automatically into overrides with the same approvers (people with the same approvers share one). Nothing needs to be redone.

Backup Approvers

A personal backup follows the approver, not the chain. On the Backup approvers tab you say, for example, "Juan's backups are Maria and Pedro". From then on, wherever Juan is the approver (as someone's immediate superior, a named person in an override or a chain, a role holder, or in the default flow when no chain applies), any active backup may approve or reject in his place.

Approver*
The person who is being covered.
Backup*
Up to five per approver.
When*
Anytime; Only while Juan is on leave (an approved leave covering today, so it switches on the moment the leave is approved); or Between dates.
Filing types
All filing types, or only the ones you select.
Status
Covering now when the backup can act today, Standing by when the condition (leave, dates) is not met yet.
Warning

Backups are alternates ("or"): any one of them can act, and the first decision settles the level. They do not chain: a backup's own backups are not used. A backup who is on leave or has left the company is skipped. Nobody approves their own filing, and an employee's own backups never approve that employee's filings.

How a Level Is Resolved

For each level, the system looks for someone who can act in this order:

  1. The level's own approvers.
  2. Plus each approver's personal backups, if the level allows them (Also allow each approver's personal backups, on by default).
  3. Plus the level's Level backups.
  4. If nobody is available: Escalate up the reporting line or Hold for HR, as the level says.

A configuration gap, such as an employee with no superior or a level with no approver, is still held for HR, unless a level backup can act. Approvers who are acting as a backup see an As backup for badge on the filing, and the approval trail reads, for example, Approved by Maria (backup for Juan). The mobile app shows the same badge and wording; setting backups up is done on the web only.

Example: Juan is on leave 10 to 14 November
Who tries to approveSetupResult
JuanOn approved leaveAway: cannot act
MariaJuan's backup, Only while Juan is on leaveCovering now: can approve
PedroJuan's backup, AnytimeCan approve (also before the leave)
Maria, on 20 NovemberSame setup, Juan is backStanding by: cannot act
Any one of Maria or Pedro can settle the level; the first decision wins.

Testing an Employee

The Who approves? tab checks your setup before anyone files. Choose an Employee and a Filing type, then click Preview. For each level it lists the approvers, who is on leave today, and every backup with whether it is active today and, if not, why not (for example "standing by until Juan is on leave"). It shows Governed by chain: …, marked as an Override when one applies (or that no chain matches and the default flow applies) and, for each stage, who would approve it today. A stage can read Nobody resolved, Skipped for this employee, or Would be held — a sign to fix the employee's Reports To or the stage's approver before filings get stuck.

Tip

Typical gap: an Immediate superior stage for an employee with an empty Reports To. Record the superior in HRIS and preview again.

How Approvers and Employees See It

Approvers act from the Manpower Dashboard — see How multi-stage approval works. Employees see the current stage, who it is waiting on, and the approval trail on their filing, on the web and in the mobile app.

For Overtime filings, approvers also see the employee's Actual Punches (first in to last out, with "+1 day" for overnight shifts, or No punches recorded) next to the requested window, in the approval dialog, on the filing detail, and in the submitted, approved and rejected emails. This lets the approver judge the request against what really happened.

A Certificate of Attendance or Official Business form whose time runs beyond the employee's shift also asks for overtime, and the approvers of that chain approve both in one go. The approval dialog shows a warning block with the breakdown (time within the shift, overtime before and after the shift, of which night differential) and the approver confirms they are also approving overtime. If the shift changed since the form was filed, the approver sees the new figures and is asked again. When approvers select several requests and use bulk approve, ANTE tells them how many of the selected requests include overtime. If the company switched off the Overtime filing type, or an Overtime eligibility rule excludes the employee, the form still files but its overtime part is not credited, and the form and the approver say why. See Time beyond your shift.

Filing Types in Use

On the Filing types & rules tab, switch off the filing types your company does not use. A switched-off type disappears from the dashboard Add menu, the attendance Resolve choices, the Filings menus and the lists on this page, and the system refuses new filings of that type. Filings already made stay visible and can still be approved or rejected. Everything is on by default. Only people with the filing configuration permission can change it.

Renaming a Filing Type

If your company calls a filing type something else (for example Time Off instead of Leave, or Field Work instead of Official Business), give it your own name. The new name replaces the built-in one everywhere the filing type is named: the dashboard Add menu, the filing forms, the Filings pages and menus, the Request Panel, approvals, notifications, emails and Excel exports, on the web and on mobile.

  1. Open the Filing types & rules tab

    Go to Manpower → Settings → Approval Configuration and open Filing types & rules.

  2. Click Rename on the filing type

    Each filing type row has a Rename button next to its switch.

  3. Enter the names and save
    Name (English)*
    The name everyone sees. Up to 40 characters, and it must differ from the other filing types' names.
    Name (Japanese)
    Optional. Shown to people using Ante in Japanese. Left empty, they see the English name.
    Name (Thai)
    Optional. Shown to people using Ante in Thai. Left empty, they see the English name.

    Click Save name.

Example: Leave renamed to Time Off, no Japanese name
WhereEnglish userJapanese user
Dashboard Add menuTime OffTime Off
Form titleTime Off FilingTime Off申請
Overtime (not renamed)Overtime残業
This tabTime Off · Default name: LeaveTime Off · 標準の名称:休暇
Info

Renaming changes only the name. How the filing works, its approval flows, its rules and the filings already made stay the same. Notifications already sent keep the name they were sent with. To go back, open Rename and click Reset to default.

Filing Rules

Approval chains decide who approves; Filing rules decide who may file a request type in the first place and how often. Without a rule, every employee can file any request type as often as needed. The Filing rules panel on this page lists your rules.

  1. Click Add rule

    The Add filing rule dialog opens.

  2. Choose the request type and name the rule

    Pick the Request type and enter a Rule name.

  3. Limit how often (optional)

    Turn on Limit how often an employee may file, set the Maximum requests (a whole number of 1 or more) and the period: Cutoff period, Calendar month or Calendar year. The list then reads, for example, "At most 2 per month".

  4. Restrict who may file (optional)

    Fill any of Departments (sections), Payroll groups, Branches and Employee tags. Leave a list empty for no restriction; when several lists are filled, an employee must match each of them. The rule then shows Restricted to selected groups instead of Open to everyone.

  5. Add a message and save

    Optionally write the Message shown when blocked (blank uses the standard wording), keep Active on, and save. You can edit or remove a rule at any time; removing it means employees are no longer held to it.

For how a filing moves through these rules once it is submitted, see Filings → Approving a filing.

Schedule Swap Filings

A Schedule Swap lets an employee give up a scheduled workday and work a rest day instead, at no premium: the day worked is paid as the plain hours of the day given up. It is a filing type like the others, so it follows an approval chain and can be given a filing rule (for example a limit of swaps per month).

Employees file it from Manpower → Filing → Schedule Swap (File Swap), from the request panel on their dashboard, or on the mobile app. The form asks for the Day you will not work (a scheduled workday), the Day you will work instead (a day they would normally rest) and a Reason. Approvers can also file on behalf of an employee and auto-approve. Once approved, timekeeping treats the two days accordingly.

Tip

Approving a swap needs the Schedule Swap approval permission. Add Schedule Swap to a chain's Filing types like any other type.

The employee side of a swap is described in Schedule Swap Filing.

How It Connects

Set up first

  • Employee Records — the employees and their reporting line (immediate superior) must exist; the superior is the default approver when no chain applies.
  • Leave — approved leave is what switches an approver's backups on.
  • Roles — levels can point at anyone holding a role.
  • Departments — an employee's department (from their role) decides which chain applies to a filing.
  • Payroll Group — filing rules can limit a request type to chosen payroll groups.
  • Employee Tags — filing rules can limit a request type to employees carrying chosen tags, and an employee-group flow can pick its people by tag.
  • Employee custom fields — an employee-group flow can also pick its people by your own custom fields.

Gets its data from

  • Approved leaves — an approved leave makes an approver 'on leave', which activates their 'Only while on leave' backups the moment it is approved.

Feeds into

  • Approver inbox and dashboards — approvers and their backups see pending filings (with the 'As backup for' badge) here, and the mobile app shows the same.
  • Employee Change Approvals — the Employee changes module decides who approves each held change; that page keeps the on/off switches.
  • Payroll Approvers — the Payroll approval module decides who signs off a payroll run; that page shows the chain and who matches each stage.
  • Filings — every filing type, from leave and overtime to schedule swap, is routed through the chain that applies.
  • Manpower Dashboard — filings whose employee has no superior are held for HR and flagged there.
  • Payroll Time Keeping — approved filings change the timesheet that payroll is computed from.