Skip to main content

User guide

This guide describes how to work with Insurance Broker Core in the ERPNext Desk, in the order of a broker's working day. It is a description of the product as it exists in the source repository, not a statement about any running installation.

Status of this guide​

ItemValue
Product versionVersion 1.0.0, repo-ready
What "repo-ready" meansThe source tree and its automated checks describe this behaviour. It says nothing about a running site.
Productive claimsNone. The guide describes forms, checks, and API calls. It does not assert that a process is productively validated.
LanguageEnglish only
ScreenshotsThe guide screenshot manifest contains 36 scene images; the public-doc asset gate selects five assets across two documents.

Where a page touches a business process, it contains a short Capability status section. The status values come from the overview: validated, supported, manual_only, model_only, blocked, and not_applicable. Only validated allows a productive claim.

Capability status at a glance​

The table below lists conditions, not claims. The binding rule is the capability matrix contract: claim_rule is only_validated_is_publicly_claimable, the default status is model_only, and the list validated_claims is empty. The capability claims document names the following conditions for a public assertion together with the verifier that would back each of them. No claim exists today.

CapabilityCondition that would have to be met before a claimEvidence script
Product classes51 classes validated (not met as a claim: validated_claims is empty)verify_product_scope_matrix.py
Special classes Fonds and Diversemodel_only, advice and placement blockedverify_fonds_diverse_boundary.py
Money and time contractBinary floats forbidden, UTCverify_money_time_contract.py
Approval proofsThree proof types, consume-onceverify_approval_proofs.py
AI capabilityBlocked by default, no domain mutation without admissionverify_ai_capability_admission.py
CRA baselinedraft_legal_review_requiredverify_cra_readiness.py

The matrix lists these processes: inventory, servicing, advice, quote comparison, placement, commission automation, and claims. Each defaults to model_only. For the special product class KVG the matrix sets inventory and servicing to supported and commission automation and claims to manual_only. On a concrete site, an Insurance Broker Capability Admission record per company, country, and product class decides which capability is admitted; a missing admission is rejected with an error.

How the guide is organised​

ChapterPageWhat you do there
OrientationGetting startedFind the workspace and the cockpit, choose a company
OrientationRoles and accessUnderstand roles and company permissions
Master dataPartiesRecord customers and other parties
Master dataMandatesRecord the authority to act for a party
Master dataProduct catalogRead the product classes and the capability report
ContractsPoliciesPolicies, terms, risk objects, coverages
AdviceAdvice and quotesAdvice cases, recommendations, quotes
TenderTender overviewWhat tender is and what it does not do
TenderTender states and commandsThe state machine and the command API
TenderPrepare and invitePrerequisites, tender record, invitations
TenderResponses and comparisonRecord answers, build the comparison
TenderRecommendation and decisionToday's limits at the end of a tender
Follow-upRenewals and deadlinesRenewal cases and deadline reports
Follow-upClaimsClaim assistance and complaint cases
MoneyCommissionsImport, reconcile, approve, draft postings
GovernancePrivacy, evidence, documentsPrivacy requests, evidence, document intake
DataMigration and importImport batches and migration contracts
HelpTroubleshootingCommon messages and next steps
HelpGlossaryTerms used in this guide

Generated lookup pages are in the reference section: Role matrix, State machines, and Error codes.

Before you start​

Installation, activation, and the first company setup are covered in First steps and activation. The data model is summarised in Core domains. Security and privacy controls are described in Security and privacy.