Reporting
One source, two audiences
Your board wants a portfolio view. Your regulator wants an extract. When those come from different systems they eventually disagree, and explaining the difference is nobody’s idea of a good week.
Provenance
Every figure traceable to an audited event
Reports are derived from the append-only audit trail rather than from a separately maintained reporting table. A number in a report can always be followed back to the events that produced it.
- No parallel reporting store to fall out of step
- Each figure traceable to immutable underlying events
- The regulatory ruleset version in force is recorded on every record
- Recomputable — a report can be regenerated for a past date and match
Management reporting
What your team sees
Portfolio position
Outstanding principal, active loan count and exposure by product, live rather than monthly.
Origination funnel
Applications by state, conversion at each stage, and where borrowers drop out.
Ageing
Days-past-due buckets with exposure, so provisioning discussions start from evidence.
Officer throughput
Decisions per officer and time in queue — a workload view, not a surveillance tool.
Cohort performance
How each origination month behaves as it seasons.
Disbursement volume
Instructed against confirmed, with reconciliation gaps visible.
Regulatory reporting
Extracts your compliance team can produce alone
A compliance extract that requires a developer is a compliance risk, because it will be late whenever the developer is busy. Khepee’s extracts are produced from the console by the people responsible for them.
- Generated from the console, without engineering involvement
- Every export recorded in the audit trail with the actor and purpose
- Consistent period boundaries, so successive returns are comparable
- Field mapping documented for your compliance team to verify
Export discipline
An export is a data event, and is treated as one
Bulk data leaving the platform is precisely when personal information is most exposed. Exports are permissioned, purpose-bound and logged, and personal fields are excluded unless the purpose requires them.
- Export requires an explicit permission, not merely a login
- A declared purpose is mandatory and is stored with the export record
- Personal fields excluded by default; included only where the purpose demands
- Every export attributable to a named person
The trail itself
An examiner can be walked through it unprepared
The audit view is designed to be shown to someone external without a rehearsal. Filter by borrower, application, officer or date, and read what happened in sequence.
- Filter by entity, actor, action or period
- Personal data appears as a hash, so the trail can be shown without exposing borrowers
- Reasons displayed alongside adverse decisions
- One request id links a support ticket to the exact events behind it
Retention
Kept as long as required, and no longer
5 yrs
Borrower records
Retained after loan closure, consistent with AML expectations.Full
Audit history
Retained for the life of the relationship and the statutory period after it.Never
Audit deletions
The trail is append-only; corrections are new entries.Bounded
Personal data
Retention is defined and documented, not indefinite by default.
Coming soon
Show us the return you have to file
Bring the extract your compliance team assembles today and we will map it field by field.