Koora alongside your HRIS
How Koora complements an HRIS: your HR system stores documents and expiry dates, while Koora adds register checks, ban register screening and expiry tracking.
On this page
Most care providers already run a human resources information system, or HRIS. It holds employee records, payroll, leave, position descriptions and a folder of uploaded documents. Many also offer expiry reminders that nudge you when a certificate is due to lapse. So a fair question is: if our HRIS already stores credentials and reminds us about expiry dates, why add a compliance platform like Koora?
The short answer is that storing a document and confirming a credential are two different things. An HRIS is excellent at the first job and was never built for the second. This guide explains where the line sits, why a stored certificate is not a verified credential, and how Koora fits alongside an HRIS rather than replacing it.
What an HRIS does well
An HRIS is the backbone of your people operations. For workforce compliance, it typically gives you:
- A central place to upload and store credential documents: National Police Checks (Nationally Coordinated Criminal History Checks), NDIS Worker Screening Clearances, Working With Children Checks, qualifications and first aid.
- Expiry dates recorded against each document, with reminder emails before they lapse.
- Employment records: contracts, position, start date, leave and payroll.
- Org structure, reporting lines and basic role assignments.
That is genuinely useful. If your HRIS does these things, keep using it. The gap is not in storage or reminders. The gap is in knowing whether the thing you stored is actually true and still current right now.
Why a stored certificate is not a verified credential
When someone uploads a certificate to an HRIS, the system records that a file exists and trusts the expiry date a person typed in. It does not, on its own, confirm any of the following:
- That the credential is genuine and was issued by the body it claims.
- That the registration or clearance is still current at the source today, not just on the date it was uploaded.
- That a clearance has not been suspended, restricted or subject to a banning order since it was filed.
- That the person on the document is the person in your roster.
A document folder is a snapshot of what was handed in. Compliance is about the live state of a credential, which can change after the file is stored. A nurse can have conditions placed on their AHPRA registration. A worker screening clearance can be suspended. A banning order can be issued. None of that updates a PDF sitting in a folder.
A reminder is not a check
An expiry reminder tells you a date is approaching. It does not tell you whether the credential is valid, restricted or revoked between now and that date. Treat HRIS reminders as diary prompts, not as confirmation of compliance status.
What Koora adds on top
Koora is built specifically for care-sector workforce compliance, so it picks up where document storage stops. It adds two things an HRIS does not: source verification, and ban register screening with expiry tracking.
Source verification, where an authoritative source exists. Koora verifies certain credentials at source rather than trusting an uploaded file:
- AHPRA registration is verified against the national register of practitioners.
- Working With Children Checks are verified by Koora against the public state lookup in Victoria, Queensland, WA, Tasmania and the NT. NSW and SA checks are reviewed from the document.
- Government ban registers are checked so banning orders surface.
For checks that have no queryable authoritative source, Koora does not claim source verification. The compliance engine checks the evidence against the role's requirements: that includes National Police Checks, qualifications and training records, and NDIS Worker Screening Clearances, with source verification for NDIS clearances on the Koora roadmap. Where you want a person across the documents themselves, your own team can assess them in-app, or the Crew service adds Koora's reviewers. The language matters: "verified by Koora" means a register confirmed it, while "reviewed" means a person assessed the document.
Remember that AHPRA registration is never a substitute for worker screening. For Aged Care, worker screening means a National Police Check issued in the last three years or an NDIS Worker Screening Clearance, and only those two options. Police history is already bundled into the NDIS Worker Screening Check and into state Working With Children Checks, so it is not a separate line item in disability or childcare contexts.
Ban screening and expiry tracking. Rather than a one-off check at hire, Koora re-screens every Career Passport holder against the ban registers each night and tracks expiry across every credential, so the current state is what you see when you run a report. If a banning order lands or a credential lapses, the compliance picture updates. A clearance suspended part-way through its term is a different case: that notice comes from the scheme to you as the linked employer. Koora shows status as at the moment the report runs. It does not reconstruct a history of what the status was on some past date.
Koora checks credentials against the role so your team starts from a clearer position. The legal responsibility for who you engage stays with you as the provider. Koora does not handle or replace that decision, and it does not make compliance effortless. It removes manual chasing where it safely can, while you keep the rigour and the accountability.
How the two systems fit together
Think of it as a division of labour:
- HRIS: employment system of record. Holds people, pay, contracts and document files. Sends diary reminders.
- Koora: compliance layer. Verifies what it can against the register, checks the rest against each role's requirements, and keeps status current for the care sector specifically.
You do not have to choose one or the other. The cleanest setup keeps your HRIS as the source of truth for employment and lets Koora own the credential checks, ban screening and expiry tracking, with data flowing between them.
Connecting Koora to your HR stack
Koora integrates via API and webhooks today, so credential and compliance status can flow into your HRIS, data warehouse or internal dashboards without manual re-keying. Webhooks mean your other systems can react when a status changes, rather than waiting for someone to check.
If you run a system that needs a deeper link, Koora can build a direct integration for it on request. Tools like Employment Hero and ELMO Software are examples Koora can integrate with via API and webhooks, or build a direct integration for when there is demand. To be clear, these are not pre-built native connectors or partnerships, they are integration paths Koora can support.
Where Koora fits
If you already have an HRIS, you have solved storage and reminders. What remains is the harder part: knowing that each credential is genuine, current and unrestricted right now, and being ready to evidence that at audit. That is the job Koora is built for. It sits alongside your HRIS, verifies what a register can confirm, checks the rest against each role's requirements, keeps status current, and connects through API and webhooks so your systems stay in step. You keep your HRIS and your compliance accountability. Koora makes the credential side faster and easier to stand behind.
For more on connecting systems, see Koora integrations via API and webhooks. To understand the provider view, read worker compliance tracking for providers. And if you are weighing up tools, see choosing care-sector compliance software.
Frequently asked questions
Does Koora replace our HRIS?
No. Your HRIS stays the system of record for employment, payroll, leave and document storage. Koora sits alongside it, adding register checks for the credentials it can verify, nightly ban register screening and expiry tracking. The two systems do different jobs and work best together.
Can Koora share data with our HR system?
Yes. Koora integrates via API and webhooks today, so credential status can flow into your HRIS or other tools. If you use a system that needs a deeper link, Koora can build a direct integration on request. There are no pre-built native connectors being claimed.
Why is a stored certificate not a verified credential?
A stored file shows a document existed when uploaded. It does not confirm the credential is current, genuine or unrestricted at the issuing source. Koora verifies certain checks at source, such as AHPRA registration and Working With Children Checks in Victoria, Queensland, WA, Tasmania and the NT, and checks documents that have no authoritative source to query against the role's requirements, with human review available through the Crew service.
This is general information, not compliance advice. Always confirm requirements with the relevant regulator, and remember that providers keep the legal responsibility to sight credentials and decide who can work.
We work hard to keep everything accurate, and our compliance engine keeps up with the rules as they change. Even so, we might get a detail slightly wrong or miss something. No one's perfect. If you think something here needs updating, email us at resources@koora.care. We would genuinely rather know, because we all do better when we help each other get it right.
See where your team stands.
Run the free workforce audit on the records you already hold, or find your service on Koora and claim it. Your first five workers are free of passport-access charges.