Enterprise platforms · Banking
Collateral and guarantee management system
We build custom collateral and guarantee management systems for banks and lenders: a register of every security and guarantee, valuations and loan-to-value tracking, charge and registration status, insurance, and the link from each item to the facilities it supports. The register feeds credit decisions, capital and provisioning calculations and the release of security at the end of a loan. You own the code.
RFP template · Banking
SME lending platform RFP template
Requirements to put in an RFP for an SME loan management system, from application intake to regulatory reporting, plus the questions to ask every vendor.- 01Eight requirement areas, each as a checklist you can paste into an RFP.
- 02Integration and data points your core banking and IT teams need to answer.
- 03Security, resilience and regulatory items that are easy to miss.
- 04Seven questions to put to any vendor or development partner.
Free download
Get it on screen in a few seconds.
What the system does, module by module.
- 01
Security register
Every collateral item, from property and deposits to receivables, vehicles, equipment and shares, held once and linked to every facility it secures. - 02
Valuation tracking
Valuation history by item, valuer and method, with due dates, reminders and a flag when a valuation is stale or the value has fallen. - 03
Loan-to-value and cover
Cover calculated per facility and per customer group after haircuts, prior charges and shared security, recalculated whenever a value or balance moves. - 04
Charge and perfection tracking
A checklist per asset type for charges, registrations and filings, with status, dates and the documents that evidence each step. - 05
Insurance monitoring
Policies, insured values, beneficiaries and expiry dates, with renewal reminders and a list of items that are uninsured. - 06
Guarantors and guarantees
Personal, corporate and third-party guarantees, their limits, expiry and enforceability checks, and coverage under government-backed guarantee schemes where the bank takes part. - 07
Collateral eligibility
Rules that decide whether an item qualifies as credit risk mitigation, with the reason recorded, so capital calculations use consistent inputs. - 08
Release and substitution
Release of security once a loan is repaid, partial release and substitution, each with an approval and a record of the documents returned. - 09
Custody and documents
Location and movement of original documents, with a log of who took what and when.
Reference architecture.
Standards and interfaces
What we design against.
- Basel credit risk mitigation
- Eligibility, haircut and cover rules that decide how collateral reduces exposure for capital purposes.
- IFRS 9
- Collateral values and cover supplied to the expected credit loss model, with the valuation date recorded.
- Registry and filing interfaces
- Company, land and security registries, accessed through the interfaces or files each jurisdiction offers.
- OpenAPI
- Interfaces for origination, servicing, valuation providers and the data warehouse.
- Market data feeds
- Prices for listed shares, funds and commodities, so margin and cover are calculated from current values.
- Data protection law
- Personal data of guarantors and asset owners kept for a defined purpose and period.
Data model
The core entities.
- Collateral item
- Type, description, owner, location, identifiers, current value and the valuation behind it.
- Valuation
- Date, valuer, method, basis (market or forced sale), amount and the report document.
- Charge and registration
- Ranking, prior charges, filing dates and references, status and the evidence for each step.
- Security link
- Which facilities an item secures, the share allocated and any cross-collateral conditions.
- Guarantee
- Guarantor, guaranteed obligation, limit, expiry, scheme coverage and legal opinion status.
- Insurance policy
- Insurer, insured value, beneficiary, period and renewal status.
- Release event
- Item, reason, approver, documents returned and date.
When custom development is the right call.
Controls designed in, not added later.
Approval on value changes
Manual valuation overrides and release of security require approval from a second person, with the reason recorded.Document custody log
Movement of original documents is logged to a named person, with reminders for items out of the vault.Access by role and portfolio
Credit, legal, operations and valuers see only the fields and customers their role needs.Audit trail
Every change to an item, link or valuation keeps the earlier value, the user and the time.Resilience
Recovery objectives agreed with the bank, with valuation feeds and registry interfaces that retry without duplicating entries.
From discovery to a system you run.
- 01
Inventory of security types
We list every collateral and guarantee type the bank takes, where each is recorded today and what the credit and legal teams need to know about it. - 02
Register and rules design
The item model, cover calculations and eligibility rules are agreed with credit, legal and risk, together with the registry and valuation interfaces. - 03
Build and migrate
The register is built by asset type, starting with the largest portfolio, and existing items are loaded and reconciled to the lending systems. - 04
Run alongside
Cover figures from the register are compared with the old process until the differences are explained. - 05
Switch over and extend
Lending systems read cover from the register; new asset types, feeds and reports are added as needed.
Relevant work
Where to see our work.
Common questions.
- Does the register replace our lending systems?
- No. Lending systems keep the loan. The register holds the security and guarantees and publishes cover and status back to them.
- Can one item secure several facilities?
- Yes. The link between item and facility records the allocated share and any cross-collateral terms, so cover is not counted twice.
- How are stale valuations handled?
- Each item has a valuation due date. Items past due appear in a worklist and are flagged on the facilities they secure, and credit decisions show the age of the value used.
- Can it track government-backed guarantee schemes?
- Yes, where the bank takes part. Scheme coverage, claims windows and reporting needs are modelled per scheme, using the rules the scheme publishes.
- Who owns the code and the data?
- You do. The code, the data and any models stay yours.