OpportuNation
User Guide

Set up and run your organisation on OpportuNation

OpportuNation is an all-in-one platform for HR, payroll, finance, and procurement β€” built for NGOs, SMEs, and growing teams across Africa. This guide is built around the order things should be done in: each part of the system depends on the one before it, so setting up in sequence means every module has what it needs to work.

πŸ‘€ Admins set up & run the organisation πŸ§‘β€πŸ’Ό Employees manage their own work life 🚚 Vendors track orders & payments

The four portals

OpportuNation is one platform with separate front doors for different users. You only need the one that matches your role β€” and a single account can hold more than one. Each opens at its own address.

PortalWho signs in hereWeb address
Marketing siteAnyone β€” learn about OpportuNation and start a free trialopportunation.io
Organisation Admin AdminFounders, HR, finance, and procurement leaders who run the workspaceerp-portal.opportunation.io
Employee portal EmployeeStaff β€” payslips, leave, timesheets, expenses, and moreemployee.opportunation.io
Vendor portal VendorSuppliers β€” purchase orders, deliveries, payments, and RFQsvendor-erp.opportunation.io

Signing in

Go to the address for your portal and enter your email and password. If an organisation invited you, use the exact email the invitation was sent to.

  • Invited to an organisation? Open the invitation link from your email and follow accepting an invitation. Your email is already filled in β€” you just set a password.
  • Starting a new organisation? Go to the marketing site, choose Start free trial, and follow the steps below.
  • Forgot your password? Choose Forgot password on any sign-in screen; we email a single-use reset link.

Creating a new organisation

This takes a few minutes and starts on a free trial β€” no payment card needed to begin. Whoever creates it becomes the first administrator, the super admin.

  1. Verify your email. Enter your work email; type the 6-digit code we send to confirm it's you.
  2. Add your details. Your name and a password (at least 12 characters).
  3. Name your organisation. Legal name, a shorter display name, and a workspace handle. We check the name isn't already taken as you type β€” if a similar organisation exists, ask an existing admin there to invite you rather than creating a duplicate.
  4. Choose your modules and plan. HR, Finance, Procurement β€” you can change these later in Billing.
  5. Set your team size and start. Enter your staff count, accept the terms, and your workspace opens.
Now do it in orderYour workspace is empty. The next section is the most important part of this guide: set things up in the sequence shown so each module has what it needs.

Admin The setup sequence

Everything in OpportuNation builds on what came before it. Departments hold employees; compensation feeds payroll; access rights make approvals possible. Follow this ladder from the top β€” each rung unlocks the next.

  1. Foundation β€” the structures everything attaches to
  2. Departments & job titles

    The organisational skeleton. Every employee is slotted into a department and a job title, so these must exist before you add people. Do this first, always.

    HRIS β†’ Dept/Job
  3. Compensation structure

    Your pay grades and components. Payroll reads pay from here β€” without an active compensation record for a staff member, a payroll run has nothing to calculate. Build this before adding people so you can assign each person a grade as you go.

    HRIS β†’ Compensation
  4. People β€” added from the top of the hierarchy down
  5. Add employees, senior-first

    Add your CEO / executives first, then managers, then their teams. Each person can report to a manager β€” and you can only pick a manager who already exists, so building top-down means every reporting line and approval chain connects correctly. Assign each employee a compensation grade as you create them.

    HRIS β†’ Employees
  6. Access β€” who can do and approve what
  7. Team & Access

    Give the people who help run the workspace a role or specific permissions β€” including the Approve permission for anything they'll sign off. This is the gate: without it, the next step has no effect.

    System β†’ Team & Access
  8. Approval Authority

    Now shape what each approver can approve, for whom, and up to what limit. This only works once the person already has the Approve permission from the step above β€” the two settings work hand in hand, access first.

    System β†’ Approval Authority
  9. Go live β€” let people in, then operate
  10. Invite employees to the portal

    An employee record doesn't give the person access. Invite them so they can log in to see payslips, book leave, and submit timesheets. Now you're ready to run operations β€” payroll, finance, and procurement.

    HRIS β†’ Employees β†’ Invite to portal
1 Foundation

Departments & job titles

Needs firstNothing β€” this is the starting point.

Open HRIS β†’ Dept/Job and create the departments your organisation is structured around (Finance, Programmes, Operations…) and the job titles people hold. Departments can be nested under a parent to mirror your real structure.

Why first: when you add an employee, you place them into a department and give them a job title. Having these ready means every staff record lands in the right place β€” and it's what later scoping (like “approve leave for my department only”) is built on.

2 Foundation

Compensation structure

Needs firstDepartments & job titles help, but the key thing is to build this before adding staff or running payroll.

Open HRIS β†’ Compensation and define your pay grades and the components that make up pay. This structure is the single source your payroll calculates from.

This gates payrollA payroll run needs an active compensation record for each employee in the period. If compensation isn't set up and assigned, the run reports that it has no compensation records to process. Build the structure here, then assign each employee a grade β€” either as you create them (step 3) or straight after a bulk import.
3 People

Add employees β€” from the top down

Needs firstDepartments & job titles (step 1), and ideally your compensation structure (step 2) so you can assign a grade.

Open HRIS β†’ Employees and add people starting with the most senior β€” CEO and executives, then managers, then their teams.

Why senior-first matters

Each employee can be given a manager, and you can only choose a manager who already exists in the system. Adding people top-down means every reporting line connects the first time, which is what drives “my direct reports” approval scopes and manager-based routing. If you add junior staff first, you'll have to go back and set their managers later.

Adding one person

Choose Add employee. The form is tabbed β€” Identity, Work, Compensation, Personal contact, Sensitive. Only a few fields are required: employee code, first and last name, and hire date. Set their department, job title, manager, and compensation grade here too.

Emails must be validIf you enter a work or personal email it has to be a real address (like name@company.com). If something's wrong, the form tells you which tab to fix before it will save.

Adding many people at once

Use Bulk import: download the CSV template, one row per employee, and upload (CSV or Excel). Every row is previewed and problems flagged before anything saves.

Compensation first, then importBulk import doesn't set pay, department, job title, or manager β€” imported staff arrive without compensation. Set up your compensation structure (step 2) first, then assign each imported person a grade afterwards.
4 Access

Team & Access

Needs firstThe people involved should already exist as employees (step 3).

Open System β†’ Team & Access to control who can do what. There are three role levels:

RoleWhat it can do
Super adminThe organisation owner β€” full control, including billing and other admins. There's always at least one.
AdminBroad control of the workspace and its modules.
MemberA staff member with a precise set of permissions you grant β€” nothing more.

For members you grant permission per area and per action β€” view, create, update, delete, approve. So a line manager can be allowed to approve their team's leave and timesheets without touching payroll or finance.

Approve permission is the keyTo let someone approve a request type, grant them the Approve permission for that area here β€” before you set up their Approval Authority in the next step. Authority without the Approve permission does nothing.
5 Access

Approval Authority

Needs firstThe person must already have the Approve permission for that area (step 4).

Open System β†’ Approval Authority to fine-tune, for each person and each request type (leave, purchase requests, travel, expenses, timesheets…):

  • Whether they can approve that request type at all.
  • Whose requests β€” direct reports only, their department, specific departments, or everyone.
  • Up to what limit β€” e.g. approve purchases up to an amount, above which it escalates.
  • Delegation β€” whether they can hand approvals to someone else while away.
Two switches, working togetherTeam & Access gives the ability to approve at all; Approval Authority shapes the scope and limits. If an approver can't action something they should, it's almost always the Approve permission in Team & Access that's missing β€” check there first.
6 Go live

Invite employees to the portal

Needs firstThe employee record exists (step 3) and has a work or personal email on file.

An employee record alone doesn't let the person log in. To give them access to payslips, leave, and timesheets, send an invitation: open the employee and choose Invite to portal (or Resend invite if they were invited before). The Portal access column on the employee list shows who is Linked, Invited, or Not invited.

The invite email is fixedAn invitation is tied to the exact address you sent it to. When the employee accepts, that email is already filled in and can't be changed β€” so their account always matches your record. If the email is wrong, correct it on the employee record and resend.

What the employee does

  1. Opens the invitation link from their email.
  2. Chooses I have an account (if they already use OpportuNation) or Create account.
  3. Their email is already set β€” they just enter or create a password.

Admin Running payroll

Before a runEmployees are active with a compensation grade assigned, and staff being paid out have bank details on their record (needed for the payment export).

Open HRIS β†’ Payroll to prepare, review, and finalise a pay run. The flow:

  1. Create the run for the period. It pulls each employee's active compensation.
  2. Review per employee. Check the calculated pay; approve an entry or send it back for correction.
  3. Finalise. Once finalised the run locks, and each employee's payslip becomes available in their portal. Payroll also posts through to the finance ledger.
If a run won't calculateThe usual cause is a staff member with no active compensation record for the period β€” go back to Compensation and make sure everyone being paid has a grade assigned. For the bank payment export, missing bank details will also be flagged.

Where enabled, Salary Advance lets you record staff loans and advances that are recovered automatically through future payroll.

Admin Finance & the ledger

Set up firstYour chart of accounts β€” journals and postings have nowhere to go without it. Then make sure the accounting period you're posting into is open.

Finance keeps your books. Set it up in this order so each piece has what it needs:

  1. Chart of accounts. Create your accounts (each with a unique code). Everything posts to an account, so this comes first. Some system accounts are provided and can't be changed.
  2. Accounting periods. Postings land in an open period; a closed period won't accept new entries. Keep the current period open as you work.
  3. Budgets & budget holders. Set budget lines and assign who owns each, so you can track budget-versus-actual and burn rate.
  4. Then day-to-day. Post journal entries (which must balance), review the expense claims staff submit from their portal, and run reports and exports. Finalised payroll posts here automatically.
Why this orderA journal entry names the accounts it debits and credits and must fall in an open period β€” so the chart of accounts and an open period have to exist before anything can be posted.

Admin Procurement & vendors

Before a POThe vendor must be registered and verified β€” a purchase order is blocked while a vendor's compliance is incomplete.

Procurement runs from a request through approval to a purchase order and delivery. Vendors come first, because you can't issue a PO to a supplier who isn't verified.

  1. Add the vendor. In Procurement β†’ Vendor Registry, register the supplier or invite them to register themselves.
  2. Verify them. The vendor sets their registration type and uploads the required compliance documents (PDFs). Verification confirms these before you transact.
  3. Raise a purchase request and route it through its approvers (this is where Approval Authority thresholds apply).
  4. Issue the purchase order to the verified vendor, then record delivery / goods received.
Verify before you sendIf a purchase order is blocked, it's almost always because the vendor's compliance documents aren't complete or verified yet. Finish vendor verification first, then issue the PO. You can also send verified vendors requests for quotes (RFQs) to compare pricing.

Admin Recruitment

Needs firstDepartments & job titles (step 1) to post roles against, and approvers set up (steps 4–5) to sign off requisitions.

Where enabled, HRIS β†’ Recruitment helps you hire: create a job requisition, get it approved, post the role, track applicants through your stages, and β€” when someone is hired β€” turn them straight into an employee record without re-typing everything.

Employee Your employee workspace

The employee portal (employee.opportunation.io) is your personal home for work life. Sign in and you land on your Overview; the sidebar groups things into Personal, Work, and Your data.

Payslips

View and download every payslip once payroll is finalised β€” across all your employers.

Timesheets

Log your weekly hours and submit them for approval.

Leave

Check your balance, request time off, and see where a request stands.

Expenses

Submit expense claims and track reimbursement.

Loans

See salary advances and how repayment is progressing.

Requests

Raise procurement and other requests where your organisation allows it.

Performance

View your probation and performance reviews.

Documents

Your employment documents, kept in one place.

Employee Everyday tasks

Book leave

Open Leave, check your balance, and submit a request with the dates and type. It goes to your approver; the status updates once they respond.

Submit a timesheet

Open Timesheets, add your hours for the week, and submit. You can edit it until it's approved.

Claim an expense

Open Expenses, enter the details and amount, attach a receipt where needed, and submit for approval.

Get your payslip

Open Payslips to view or download any payslip. New ones appear automatically once your employer finalises that month's payroll.

Your data, your control

Under Your data you can export a copy of your information and request account deletion.

Employee Working with more than one employer

A single personal account can work with several organisations β€” useful for consultants and contractors. Your records stay separated per employer.

  1. Sign in to the employee portal with your personal account.
  2. Open Organizations to see every organisation you belong to.
  3. Switch into a workspace to access that employer's records β€” you confirm with your password when entering.
Added but don't see the organisation?Ask that organisation's admin to send or resend your invitation, and accept it from the emailed link.

Vendor The vendor portal β€” for suppliers

If you supply an organisation using OpportuNation, they can invite you to the vendor portal (vendor-erp.opportunation.io) β€” one place to work with every buyer connected to you.

Get transactingComplete your vendor profile and upload your compliance documents β€” buyers can only issue you purchase orders once your details are verified.

Purchase Orders

View POs from your buyers β€” quantities, amounts, and delivery dates in one place.

Delivery Confirmations

See when goods are accepted, partially accepted, or flagged for inspection.

Payment Status

Follow payment status from buyers who've enabled it.

Vendor Profile

Keep your registration, tax, and banking details current.

Compliance Documents

Upload and manage certificates. Verified documents build buyer trust.

RFQ Pipeline

Receive requests for quotes and respond on price and delivery.

To get started: register or accept your invitation, complete your Vendor Profile, set your registration type, and upload the required compliance documents. Keeping these current means buyers can onboard and transact with you without delay.

Account & security

Your data's safety is built into the platform. A few things worth knowing:

  • Each organisation's data is fully separated. One organisation can never see another's records.
  • Passwords are protected. Stored only in a scrambled form that can't be reversed β€” not even by us β€” and must be at least 12 characters.
  • Sensitive details are encrypted. Bank account and tax numbers are encrypted, and only the last few digits are ever shown.
  • Signing out ends the session immediately. Once you log out, that session can't be used again, even from the same device.
  • Documents are private. Files you upload are accessible only to the people and organisation they belong to.
Good habitsUse a strong, unique password, sign out on shared computers, and keep the email on your account current β€” it's how you recover access and receive important notices.

Getting help

Stuck, or something not behaving as this guide describes? We're here to help.

When you write in, tell us which portal you were using and what you were trying to do β€” it helps us help you faster.