- Industry
- Banking
- Department
- HR
- Team
- People Operations
- Kind
- Assistant
- Approver
- Head of HR
- Code
- HRS-09
It turns each accepted offer into a new-hire plan: identity and right-to-work checks, the background, credit and criminal-record vetting and references a bank role needs, regulatory approvals for senior managers, policy attestations (code of conduct, data secrecy, insider dealing), access requests by role and first-week tasks. It holds system access to payments and customer data until vetting has cleared.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the HRIS: the new hires' offers, vetting results and role access profiles..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 05Asks a person
Hands the work to Head of HR with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the HRIS: it creates the onboarding tasks and access requests for each new hire. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The onboarding standard for the bank: pre-employment vetting by role (identity, right to work, five-year references, credit and criminal-record checks, regulatory references), regulator approval for senior-manager roles, the role-based access model and segregation-of-duties rules, mandatory day-one attestations and first-week training.
Reads from
the HRIS: the new hires' offers, vetting results and role access profiles.
Acts in
the HRIS: it creates the onboarding tasks and access requests for each new hire.
Hands back
A list with one entry per new hire, each with employee_id, start_date, checks (a list with check and status), access (a list with system, profile and grant_after), attestations (a list with due date), buddy, first_week (a list) and blockers.
Asks a person when
A vetting check fails or is still pending within five working days of the start, the start must be moved, access beyond the role's default or a segregation-of-duties conflict is asked for, or the hire is a senior manager awaiting regulatory approval.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Start onboarding before start date (days) | 15 | Vetting and set-up begin this far ahead. |
| Vetting clears before access | On | When on, no access to payments, customer data or the core banking system until all checks pass. |
| Access beyond the role's default | needs the approver | How access outside the role profile is handled. |
| Assign a buddy | On | When on, each new hire gets a buddy in their team. |
| Day-one attestations due within (days) | 5 | Code of conduct, data secrecy and personal dealing attestations are signed within this. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Begin vetting 15 days before start; a senior-manager hire cannot start in role until the regulator's approval is recorded.
- When on is true, no access to payments, customer data or the core banking system until every check has passed.
- Grant only the role's default access; anything beyond it needs the approver, and never a combination that breaks segregation of duties (for example raising and approving payments).
- Code of conduct, data secrecy and personal dealing attestations are signed within 5 days.
- When on is true, assign a buddy from the team.
See the Employee Onboarding Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.