Rupid · Rupid · 46 documents in dependency order
These documents describe the Rupid platform as it is to be built. They are ordered by dependency: nothing appears before the things it needs in order to work. An employer is set up, the programme is configured, the workforce is loaded, employees use the app, and the money machinery and platform layers sit underneath all of it.
Each document covers one working area completely — the screens, the rules, the fields, the edge cases and the messages. Where two things were previously described separately but are really one thing, they have been written as one document.
A strict sequence — each step unlocks the next. Verification has the longest lead time, so it starts on day one.
| # | Document |
|---|---|
| 001 | Employer Account Setup and Admin Invitation |
| 002 | Company Verification and Financial Review |
| 003 | Agreements and Digital Signing |
| 004 | Portal Users, Roles and Access |
| 005 | Onboarding Workbench |
Branches first, because calendars, pay cycles and eligibility rules all attach to them.
| # | Document |
|---|---|
| 006 | Branches and Locations |
| 007 | Working Week and Holiday Calendar |
| 008 | Pay Cycles and Payday |
| 009 | Eligibility and Lending Rules |
Loading employees by file or connection, keeping the list current, and getting people registered.
| # | Document |
|---|---|
| 010 | Employee List Upload |
| 011 | Payroll and HR System Connections |
| 012 | Employee Lifecycle Management |
| 013 | Employee Invitations and Activation |
| 014 | HR Verification Queue |
| 015 | Employee View for HR |
What happens at cut-off, on payday, and afterwards.
| # | Document |
|---|---|
| 016 | Deduction File and Settlement |
| 017 | Reconciliation and Differences |
| 018 | Exit and Final Settlement Recovery |
What the employer sees, keeps and controls.
| # | Document |
|---|---|
| 019 | Employer Dashboard |
| 020 | Employer Reports and Invoices |
| 021 | Document Vault and Audit Trail |
| 022 | Programme Pause, Freeze and Offboarding |
From first opening the app to being able to receive money.
| # | Document |
|---|---|
| 023 | Employee Registration and Login |
| 024 | Employee Verification |
| 025 | Account Linking |
| 026 | App Home and Products |
The user journey in the order a worker actually meets it.
| # | Document |
|---|---|
| 027 | Earned Wages and Salary Timeline |
| 028 | Withdrawal |
| 029 | Salary Advance |
| 030 | Auto-Repayment Mandate |
| 031 | Loan Details and Repayments |
The engines the app and portal screens read from.
| # | Document |
|---|---|
| 032 | Earned Wage Calculation and Limits |
| 033 | Disbursement and Payment Rails |
| 034 | Ledger and Money Movement |
| 035 | Recovery and Collections |
The lending partner’s view and Rupid’s own working screens.
| # | Document |
|---|---|
| 036 | Lending Partner Portal |
| 037 | Operations Console |
| 038 | Support and Help |
| 039 | Fraud and Suspicious Activity |
Rupid-maintained layers that every other document depends on. No employer configures anything here.
| # | Document |
|---|---|
| 040 | Multi-Tenant Setup and Master Data |
| 041 | Identity and Access Services |
| 042 | Product Catalogue and Charges |
| 043 | Approvals and Change Control |
| 044 | Notifications |
| 045 | Consent and Data Governance |
| 046 | Reports and Regulatory Filing |
Within the employer journey the order is a genuine sequence of gates. The account must exist before papers can be uploaded; verification must be approved before agreements are issued; agreements must be in force before configuration begins. Verification sits second rather than later because it carries the longest lead time — Rupid’s credit review takes several days — so it starts while the employer does everything else.
Branches lead the configuration block because working-week patterns, holiday calendars, pay cycles and eligibility rules all attach to a branch, and the employee upload validates against branch codes. Configuring anything else first means going back.
Product Catalogue and Charges sits in the platform block rather than the employer block, because employers cannot see or change it. Prices and products are Rupid’s, and an employer only chooses which of them to switch on for their own people.
An earlier set of 135 documents has been reduced to these 46. Overlapping features were written as single documents rather than repeated: access control across five documents became one; eligibility rules, product settings and the rules engine became one; all settlement features became two; all notification features became one; all audit and document features became one.
Five features were removed rather than merged — pay runs, payroll validation, payroll exceptions, payroll preview and pay groups. Rupid does not execute payroll. It produces a deduction file which the employer’s own payroll applies, so these described work the platform never does.