Inspire glossary
The terms you will meet in the Inspire repos, in team conversation, and in the legacy systems being replaced. Industry terms are defined the way the industry uses them; system terms name the object behind them where one exists. The site-wide public glossary covers the other Nextera products.
Parties and roles
Section titled “Parties and roles”Party — Any person or organisation the system knows. Inspire GI keeps one
golden record per real-world entity (tparty) with roles attached, so the same
party can play different roles on different contracts.
Policyholder / customer — The party who buys the policy, is billed for it and holds the insurer’s promise. In group and credit life the policyholder is an employer or a creditor partner, not the covered person.
Insured — The person or thing actually covered. May differ from the
policyholder. GI types it (tpolicy_insured): PRIMARY, EMPLOYEE, SPOUSE,
CHILD, DEPENDANT.
Member — A person enrolled under a group contract; the group and pension flavour of insured. Members carry dependents.
Beneficiary — The party paid on a life claim — a credit-life certificate names the creditor as beneficiary of the outstanding loan.
Producer / agent — Sells and services business and earns commission
(tproducer, commission shares on the policy). The producer hierarchy feeds the
live nxo-dms distribution system.
Reinsurer — An insurer taking a share of another insurer’s risk, under a treaty or a facultative placement.
Provider — A hospital, clinic or repairer serving a claim. Central to group medical claims and the provider network with pre-authorisation and cashless treatment.
Creditor / partner — The bank, financing or leasing company whose loans a
credit-life scheme insures (tpartner in inspire-cl).
Debtor (debitur) — The loan holder insured by a credit-life certificate.
The Indonesian term survives in the legacy schema (DebiturNm).
Products and coverage
Section titled “Products and coverage”Line of business (LOB) — A class of insurance business — motor, fire, personal accident. Drives statutory class, reinsurance scope and reporting.
Component — A reusable product part in GI’s component library, the bottom layer of the product factory.
Technical product — The superset definition for a line of business, assembled from components. Never sold directly.
Market product — The sellable subset of a technical product, with fields, clauses, channels, rates and rules bound to it. What a quotation quotes.
Plan — A restricted, packaged variant of a market product. Group certificates and credit-life schemes sell plans.
Element / element tree — A node in the product or policy tree
(tproduct_element / tpolicy_element): ROOT, SECTION, RISK, INTEREST,
COVERAGE, BENEFIT, CLAUSE. “A product is a tree; a policy is that tree,
instantiated.”
Coverage — A specific promise within a policy — what peril, up to what limit, at what deductible.
Benefit — A payable amount under a coverage, the leaf where life and health premium accumulates.
Peril — The cause of loss insured against (fire, theft, windstorm). GI seeds 31 perils.
Sum insured (SI) — The maximum the insurer pays for a covered object. Rolls up from the interest level, where each distinct object counts once — fire 50bn and earthquake 50bn on one building is 50bn of exposure, not 100bn.
Rate table — The configured premium rates the rating engine reads
(trate_table), keyed by rating factors.
Rating / rating trace — Computing premium by walking the element tree
bottom-up. Every computation writes a trace (trating_trace) so any figure can be
explained.
Clause — Contract wording attached to a product; snapshotted onto the policy at issuance so later product edits never rewrite an in-force contract.
Data dictionary (DD) — The dynamic-field system: tdd_field defines a field,
tproduct_element_field binds it to a product level, tpolicy_element_value
stores the value. Adding a field is an INSERT, not DDL.
Product version — An immutable published state of a market product. In-force
policies stay bound to the version they were written on
(tpolicy.ProductVersionID).
Policy lifecycle
Section titled “Policy lifecycle”Quotation — A rated offer with no commitment; versions of a quotation can be compared. Becomes a proposal when accepted.
Proposal — The real risk with real parties and an allocated number; the object
underwriting decides on. GI allocates ProposalNo from tnumber and sets
PolicyStatus = PN.
New business (NB) — The first issuance of a policy; one of the three policy
transaction types (POLICY_TRANS_TYPE), with EN endorsement and RN renewal.
Issuance — Allocating the PolicyNo, writing policy version 1, snapshotting
clause wording and turning the contract in force. Fans out to billing,
reinsurance, documents and search after commit, from the outbox.
PolicyStatus — The contract lifecycle: PN pending, RD ready, TV
validated, IF in force, PE/PR pending endorsement/renewal, TX cancelled,
TM terminated (GI seeds; group uses its own strings).
Status (record status) — Whether a row is usable at all — active, draft,
pending, terminated, cleared (AC/DR/PN/TM/CL). Not the lifecycle; the
distinction is the schema contract (docs/04-naming-standards.md §3).
Endorsement (EN) — A mid-term change to an in-force policy: sum insured, rate,
covers, risks, period, or non-financial data. Versioned per element; bills the
delta, not the total. Seeded types include BIE, TSI, RATE, ADDCOV,
DELCOV, ADDRISK, DELRISK, POIEXT, POISHORT, POIMOVE, CAN,
REINSTATE, PC, UNDO, NP.
Out-of-sequence endorsement — An endorsement effective before one already
issued. Supported because element rows carry explicit version windows; later
premiums are rebuilt on the new basis (IsOutOfSequence).
Policy version / VersionSeq — The policy’s version counter; each endorsement
or renewal increments it and writes a new tpolicy_version row, flipping
IsCurrent.
ElementKey — The stable identity of a policy element for the life of the
policy, separate from the row that carries it. Endorsing closes a row and opens a
new one under the same key, so versioning a parent never orphans children.
fn_policy_element_at_version() reconstructs any past state.
Renewal (RN) — Continuing cover for a new period. A new policy with its
own number and claims, linked both ways (RenewedFromPolicyID /
RenewedToPolicyID) so continuous cover and NCD entitlement are provable.
No-claim discount (NCD) — A premium reduction earned by claim-free years;
NcdLevel steps at renewal.
Cancellation — Ending the policy early: FROMINCEPTION (full refund, only
without claims) or MIDTERM (short-rate or pro-rata refund). Sets
ExpiryDate to the effective date so period and premium agree; status TX.
Reinstatement — Restoring a cancelled policy from a date: cover back, reinstatement premium billed, cessions re-established.
Lapse — A policy that ended by non-payment rather than by decision
(RENEWAL_STATUS = LP on the renewal side).
Short-rate / pro-rata — Refund bases for the unexpired period: pro-rata is exact time-share; short-rate penalises early exit.
Coinsurance — Several insurers sharing one policy’s risk directly (not via reinsurance); each share’s premium and claim follow.
Installment — One of several scheduled premium payments; billing creates one AR row per installment.
Certificate — An individual contract issued under a master policy — the
credit-life unit of business (loan fields live on tcertificate) and the
micro-insurance unit (PolicyType = CERTIFICATE).
Master policy — The umbrella contract under which certificates or member coverages are issued — a group scheme or a creditor’s policy scheme.
Underwriting
Section titled “Underwriting”Underwriting (UW) — Deciding whether to accept a risk and on what terms.
UwType distinguishes the automatic pass (AUTO) from the human decision
(MANUAL).
STP (straight-through processing) — Cases that pass all underwriting rules without referral and issue automatically.
Referral — A case sent to a human underwriter by rule, with an SLA clock
(tunderwriting_referral).
Loading — A premium surcharge applied for extra risk; a term an underwriter may attach on acceptance.
Excess / deductible — The amount the insured bears of each loss before cover responds.
Authority matrix — Who may approve what amount, up a chain
(tmatrix, tentity_approval). Claims and settlements climb the same matrix.
Blocklist / sanctions screening — Checking parties against internal and
sanctions lists at proposal and claim time (tclient_blocklist).
Decision — The underwriter’s outcome: accept, decline, or accept with terms.
Claims
Section titled “Claims”FNOL (first notice of loss) — The initial loss report, any channel. The
notification row (tclaim_notification) is written before anything is verified, so
a loss is never lost.
Claim registration — Matching a notification to the policy version in force
at the loss date and snapshotting it immutably (tclaim_policy).
Claim item — One covered policy element’s slice of a claim
(tclaim_item).
Reserve — Money set aside for the expected cost of an open claim
(tclaim_reserve holds the position).
Reserve movement — The immutable history of every reserve change — OPEN,
INCREASE, DECREASE, PAYMENT, RECOVERY (tclaim_reserve_movement).
Actuarial triangles are built from movements, so they are exact.
Adjudication — Deciding what is payable: coverage checks, edits, calculation.
Deductible — See excess; deducted in claim calculation.
Depreciation — The age/value reduction applied to damaged property in claim calculation.
Salvage — The value of damaged property the insurer takes over — both a claim calculation and a recovery type.
Subrogation — Recovering from the third party at fault, after paying the insured.
Recovery — Any money coming back after a payment: subrogation, salvage,
reinsurance, recoverable deductible (tclaim_recovery, movement RECOVERY).
Underinsurance — Sum insured below the true value; the claim scales down in proportion.
Settlement — The approved claim outcome (tclaim_settlement).
EOB (explanation of benefits) — The member-facing claim statement letter, central in group medical.
Catastrophe — A declared event (tcatastrophe) grouping claims, with an
hours clause (e.g. 72 hours of windstorm) defining the event window for
accumulation and catastrophe reinsurance.
Premium, billing and money
Section titled “Premium, billing and money”Premium — The price of the insurance promise. Gross before reinsurance; ceded the reinsurers’ share; net what remains.
Bill — The financial document a business event produces; immutable once
created (tbill).
Fee — One money component of a bill — net premium, tax, commission, stamp
duty (tbill_fee); each routed to AR/AP or the ledger.
AR / AP — Accounts receivable / payable (tarap): what a counterparty owes
us, or we owe them, per installment.
Collection — Money in: parked in suspense (tsuspense), then allocated to
AR by offset (toffset). Personal lines can collect-and-offset in one step.
Suspense — Money received but not yet allocated to a debt.
Offset — Allocating suspense (RefType 2) or another AR/AP (RefType 3) against an AR balance. Tolerance offset (OffsetType 3) clears small residuals; write-off (OffsetType 4) clears uncollectibles — both authority-controlled.
Payment / disbursement — Money out — claims, refunds, commission, RI premium. Clears its payable directly; no offset step. Confusing collection and payment flows is the classic newcomer error.
Statement settlement — Netting a counterparty’s many debits and credits for a
period into one collection or payment (tstatement).
Commission — The producer’s share of premium, per the producer’s scale; brokerage is the reinsurer-facing equivalent in RI accounting.
Dunning — The batch that chases unpaid bills and reconciles lost payment callbacks.
Ledger and finance
Section titled “Ledger and finance”GL (general ledger) — The books of account. Inspire keeps a full internal
ledger and can mirror to an external one (Oracle): INTERNAL, EXTERNAL or
BOTH (GL_INTERFACE_MODE, ADR 0001).
Chart of accounts — The account structure posted against.
Dimension — One of 12 analysis axes on a posting (branch, LOB, product…) resolved from literals or expressions.
Posting template / event type — The rule matching a business transaction and
fee type to its debit and credit legs (tevent_type, tevent_type_detail).
Voucher — The staged, reviewable precursor of a journal entry
(tgl_voucher); a posting run can be corrected and re-run before it posts.
Journal — The immutable posted entry (tjournal), with references back to
the policy, claim, bill or treaty it came from.
Trial balance — Debits equal credits, per period (ttrial_balance).
Period close — End-of-period: post everything, revalue currencies, generate
bordereaux and statements, reconcile ageing, then close (tperiod.IsClosed = 1)
— by reversal, never by edit.
IFRS 17 — The insurance-contracts accounting standard; Inspire supplies its data from the same movements the ledger uses.
OJK — Otoritas Jasa Keuangan, Indonesia’s financial-services regulator; statutory reporting extracts are a first-class output.
Reinsurance
Section titled “Reinsurance”Retention — The share of risk the insurer keeps for itself
(tretention, by LOB / object type / SI band).
Treaty — A standing reinsurance contract. Quota share (QS) cedes a fixed percentage; surplus cedes above a retention in lines; XOL (excess of loss) pays loss above an attachment point; catastrophe XOL covers event accumulation; stop loss caps a portfolio’s loss ratio. GI seeds eight types.
Layer — A band of non-proportional cover: attachment point plus limit
(ttreaty_layer).
Attachment point — The loss amount at which a layer starts paying.
Limit — The most a layer pays.
Reinstatement — A layer’s capacity restored after it is exhausted by a loss, usually for a reinstatement premium.
Facultative — A one-off placement of a single risk that exceeds treaty
capacity (tfacultative).
Cession — The act or record of passing risk to reinsurers (tcession).
CessionBasis distinguishes proportional (cedes at issuance) from
non-proportional (attaches at claim).
Treaty participant — A reinsurer’s share of a treaty; participants’ shares
total 100% (ttreaty_participant).
RI premium — The premium ceded to reinsurers, net of RI commission and
brokerage (tri_premium).
RI recovery — The reinsurers’ share of a settled claim (tri_claim_recovery).
Bordereaux — The periodic schedule of ceded premiums, claims or risks sent to
reinsurers (tbordereaux).
RI statement / account — The net position and running balance with one
reinsurer (tri_statement, tri_account).
Group insurance terms
Section titled “Group insurance terms”GMD — Group medical/dental, the core group claims line in Compass.
HSD — Health Services Division, Compass’s VB6 provider-network / managed-care subsystem.
ASO — Administrative services only: the insurer administers a scheme without insuring its risk.
LTD — Long-term disability cover, a Compass group line.
Sponsor — The employer or client holding the master policy and receiving the bills.
Bill mode — The sponsor billing frequency: monthly, quarterly, semi-annual or annual.
Draft / official bill — Group bills are produced as drafts for review, then made official, before receivables arise.
Sub-office — A branch of the group client used for reporting and billing splits.
GMPS / EBPS — Compass’s Hong Kong group proposal / new-business system and its quotation subsystem.
DBR / MBR — Daily / monthly batch run cycles in Compass.
MAPA — Compass’s management-accounting profitability report family.
Enrollment / un-enrolled — Adding (or failing to add) members to coverage for a period; the upload orchestrator runs passes for both.
Credit life terms
Section titled “Credit life terms”Policy scheme — The creditor partner’s master setup: product package,
premium rate, standard limits (tproduct_package, tpremium_rate).
Agreement number — The loan agreement a certificate insures
(AgreementNmbr).
Monthly installment / loan duration / loan maturity — The loan facts a
certificate carries (MonthlyInstallment, LoanDuration, LoanMaturityDate).
Bulk certificate upload — The disbursement-file-driven issuance path
(tCertUpload / tCertUploadInvalid, one row per loan, per-row validation).
EXIM file — The export/import interface file format exchanged with partners
(texim_file, texim_file_detail).
Pre-policy / pre-claim staging — Tables that stage data before a certificate
or claim is formally created (tcertificate_pre_policy, tcertificate_pre_claim).
Surrender (credit life) — Closing a certificate because the loan was paid off
early; refunds the unearned premium (tsurrender).
Standard limit / underwriter level limit — The cover ceilings per scheme and
per underwriter authority (tstandard_limit, tunderwriter_level_limit).
Medical type / BMI loading — Health-questionnaire-driven premium loadings
(tmedical_type*, tbmi_rate).
Pension terms
Section titled “Pension terms”Plan — A pension arrangement’s rules: investment options, vesting scale, fees.
Investment option / fund — A fund a plan’s money can be invested in
(investopt_tbl, tmfplinvestopt).
Contribution — A remittance into a member’s account.
Fund allocation — How a member’s money splits across investment options
(tmffnalloc).
Fund price / unit pricing — The daily price applied to allocations; balances
are units times price (fund_price).
Fund balance / movement — A member account’s position and its immutable
change history (tmfphfnbal, tmffnmovement).
Vesting / vesting scale — The rules deciding what share of the account the
member is entitled to, typically by years of service (tmfvestnrec,
tmfvestscalemstr).
Withdrawal — Taking money out: full or partial, each with its own factors and interface files.
Switch — Moving money between investment options without leaving the plan.
Premium holiday — A suspended-contribution period on a policy.
IVR — Interactive voice response; RPAS fed an IVR system with balance data.
Platform and code terms
Section titled “Platform and code terms”tcode / tcode_type — The code-table system: every dropdown and enum is
rows, not code. GI seeds 194 code types verbatim from nxo-dms.
tnumber — The autonumbering engine assembling document numbers from tokens
like [YYMM] and [NEXT].
tobject / tproperty — Object registry and property storage in the shared
platform.
LOV / LOM — List of values (single-select) / list of multi-select. Two mechanisms share the name on some screens — check which one a page means.
Entity lifecycle — The shared status/approval/queue/history framework keyed
on (EntityType, EntityReference).
Outbox — Post-commit fan-out through a durable queue (tentity_queue),
at-least-once: issuance never blocks on billing, documents or search.
ReturnCode — The API envelope’s numeric verdict: 0 success, -1 failure,
-2 a reconfirmable warning the client may override with byPassValidation.
ccs — The gitignored connection-string file next to the API binary; carries
the database password. Ask a teammate for it.
@nextera/ui — The shared Angular component library (nxe- prefix), built
from the local projects/nxe-ui. Distinct from the nextera-library npm package
(types and constants only) — the two are not interchangeable.
Gauntlet — The spec-then-code loop discipline used by the group and credit-life migrations, gated on builds passing.
t-prefix tables — The house table-naming convention (tpolicy,
tclaim), inherited from the legacy systems’ T-prefix.
nxo-dms / nxo-link — Nextera’s live distribution-management and
life-e-submission systems. GI sends policy events to nxo-dms; an individual-life
core would sit behind nxo-link.
Legacy system terms
Section titled “Legacy system terms”Compass 2000 — AIA’s group core (1996–2009, v5.37; COBOL parts to 1993),
across nine countries. Centura UI, VB6, 1.15M lines of T-SQL, 958K lines of COBOL
batch, no foreign keys, soft delete, char(26) timestamps.
iCLIPS — The legacy credit-life system: VB.NET / ASP.NET WebForms + SQL Server.
RPAS — Avrist’s legacy pension administration system: VB6 client, SQL Server, 862 tables in the dump.
Centura / Gupta Team Developer — The 1990s Windows tool Compass’s UI was written in; 274 of its files are binary and unreadable without the tool.
RCDSTS — Compass’s soft-delete record-status column.
TMSGTBL — Compass’s message catalog (codes like E0553, W3004) —
effectively part of the code, preserved by translation-only porting.
TSYSPARM — Compass’s config-as-data parameter table.
Translation-only — The migration rule that ported rules keep the legacy system’s exact messages, statuses, money precision and flagged bugs.
nxgi — GI’s database and response-code prefix (NXGI-####), kept from
before the suite was branded Inspire (ADR 0007).
ADR — Architecture decision record. GI’s docs/adr/ holds the load-bearing
ones: no legacy migration (0003), GL mode BOTH (0001), single-tenant on-premise
(0002), the rename (0007).