Certificates & Audit Trail
Six certificate types drawn from live ledger balances, and an event log that records every material action without allowing anyone to edit it afterwards.
Certificates in GoDravix are generated from current ledger balances rather than typed into a template, which means the figure on the document and the figure in the system cannot diverge. Issuance is itself a logged event in an append-only audit trail.
The trail is searchable and filterable, and includes interest runs and certificate issuance.
What is built today
- Outstanding Balance Certificate
Current principal, interest and penal position as at a stated date.
- Interest Repaid Certificate
Interest paid over a period, the document borrowers most often need for their own accounts.
- Loan Cancellation Certificate
Issued where a sanction is cancelled before or after partial disbursement.
- NOC Closure Certificate
No-objection certificate on full settlement of a loan.
- Part Payment Certificate
Acknowledgement of a partial settlement against an outstanding loan.
- Waiver Certificate
Records an approved waiver with its authority and order reference.
- Append-only audit trail
Every event attributed and timestamped. Once the book is live, entries are never edited or deleted, by any role.
- Searchable and filterable log
Filter the trail by actor, action type, entity and date range.
Generated,
never retyped.
Outstanding, Interest Repaid, Cancellation, NOC Closure, Part Payment and Waiver. Each is produced from live balances at the moment of issuance, and each issuance is itself an event in the trail.
See certificates and auditGenerated from balances, not typed into a template
The common failure mode with loan certificates is that somebody exports a balance, pastes it into a Word template, and issues a document that was accurate at the moment of the copy and drifted afterwards. Where the certificate later turns out to disagree with the ledger, nobody can say which one was wrong.
GoDravix generates each certificate from the live ledger at the moment of issuance, and records the issuance as an event. The document and the system agree because they are the same source. If a certificate is later questioned, the trail shows when it was issued, by whom, and what the balances were.
- One source of truth
The certificate reads the ledger; it does not receive a pasted number.
- Issuance is an audited event
Who issued which certificate for which loan, and when.
- Reissue leaves a trail
A second issuance does not overwrite the first in the log.
- Export to PDF
Certificates and the ledger behind them export for filing.
What append-only actually means here
Append-only is a claim many systems make while quietly offering an edit function to administrators. On a live GoDravix book there is no such function: a correction is a new event that references the original, and both remain visible in sequence with the resulting balance after each.
This is less convenient than editing. An operator who fat-fingers a repayment amount cannot simply fix the number; they record a correction, and the mistake stays on the record permanently. That inconvenience is the entire point. A ledger that can be tidied is a ledger that cannot be trusted, and the Auditor role exists precisely so that somebody outside the operations team can read the untidied version.
- No edit, no delete on a live book
Corrections are appended, referencing what they correct.
- Full attribution
Every entry carries the acting user and a timestamp.
- Interest runs logged
Accrual runs appear in the trail, not just loan transactions.
- Certificate issuance logged
Document generation is a recorded event.
- Independent Auditor role
Read-only portfolio-wide access, including the complete log.
- Filterable
By actor, action, entity and date range.
The role-based user manuals
Six role-based user manuals exist for the live deployment, one per role, written with screenshots of the actual system. They were produced for the board’s own onboarding and they are part of what we hand over.
Documentation is an unglamorous thing to mention on a product page. We mention it because in a government or cooperative deployment, the difference between software that gets used and software that gets abandoned is frequently whether the person in the accounts office was given something they can follow. The manuals are also the ready-made knowledge base for the in-app copilot, once it is built.
Where this module stops
These sit outside what this module does today. They are named here so a fit decision can be made now rather than during implementation.
- Certificate template editorThe six formats are fixed, so a different layout or a seventh certificate is a scoped development change rather than a settings screen.
- Digital signature and e-signCertificates are generated as documents and signed through your existing process. E-sign integration is roadmap.
- Custom fields on certificatesCertificate content is drawn from fixed fields. Additional data points cannot be added through configuration.
- Bulk issuanceCertificates are issued per loan today. Batch generation across a scheme or financial year is roadmap.
Some of it is built into an engagement, some is genuinely out of scope, and some is development we can quote against your requirement. Which one it is depends on your workflow, and that is a fifteen-minute conversation rather than a guess.
About this module
Six: Outstanding Balance, Interest Repaid, Loan Cancellation, NOC Closure, Part Payment and Waiver. Each is generated from live ledger balances at the moment of issuance, and each issuance is recorded in the audit trail. The six formats are fixed. There is no template editor, so a seventh certificate type or a modified layout is a development change rather than a configuration.
Not once the book is live. On a running deployment there is no edit function and no delete function, for any role including Admin. A correction is recorded as a new event that references the original, and both stay visible in sequence. The independent audit permission has read-only access across the whole portfolio including the complete log, deliberately outside the operations chain.
One exception, and we would rather you heard it here than found it in a demo. During migration, before cut-over, a reset tool lets a part-loaded book be cleared and re-run, because a migration that cannot be retried is a migration you only get one attempt at. It is withdrawn when the book goes live. Ask to see the state of that control on any deployment you are evaluating.
Every loan lifecycle transition, every interest accrual run, every repayment allocation, every waiver with its authorisation reference, and every certificate issued. Each entry carries the actor, the action and the timestamp, and the trail is filterable by all three plus borrower and date range.
The property that matters more than the contents: on a live book there is no edit function and no delete function, for any role including Admin. A correction is a new event that references the original, so the mistake and its fix are both permanently visible.
Not within the platform today. Certificates are generated from live balances as documents and go through whatever signing process your organisation already uses, which for most finance teams is the process their auditor already accepts. E-sign integration sits on the integrations roadmap.
Related modules
Loan Lifecycle Core
Sanction, maker–checker approval, single or multi-tranche disbursement, repayment, waiver, closure and NOC. Disbursement stays blocked until the approval actually happens.
Learn moreInterest & Accrual Engine
Simple and monthly-compound interest with a separate penal rate. Accrual runs on demand, and existing accruals can be recomputed when a back-dated entry changes the picture.
Learn moreRecovery & Repayment
Automatic waterfall allocation, penal, then interest, then principal. Monthly, half-yearly or yearly frequency. Grant deduction and cheque recovery methods.
Learn moreSee this module running on live data
We demo on the production deployment, not a sandbox with tidy numbers chosen to make the software look good.
45 minutes | On the live deployment | A straight answer on fit