Skip to main content

Error codes

Most validation errors in Insurance Broker Core end with a code in parentheses, for example the text of the message followed by the code. This page lists those codes with the message text from the product, grouped by area. Placeholders in message texts are written in capital letters. It is generated from the source files, so it changes only when they change.

Codes that appear only as a field in a contract and are never raised are not listed. For the Tender workflow, see Tender states and commands.

Messages shown with a code​

These codes and texts come from the message table in insurance_broker_core/user_errors.py. The text is shown to the user, followed by the code in parentheses.

Approval proofs​

CodeMessage
IBC-APPROVAL-BINDING-001The approval no longer matches the current reconciliation.
IBC-APPROVAL-BINDING-HASH-001The approval integrity check failed.
IBC-APPROVAL-BREAK-GLASS-001Break-glass access cannot approve commission accounting.
IBC-APPROVAL-CLAIMS-001The approval proof is incomplete.
IBC-APPROVAL-EXPIRED-001This approval has expired. Start the approval again.
IBC-APPROVAL-REPLAYThis approval proof has already been used.
IBC-APPROVAL-REPLAY-001This approval proof has already been consumed.
IBC-APPROVAL-REVOKED-001This approval was revoked.
IBC-APPROVAL-TYPE-001This approval proof type has no admitted local verifier.

Capability admission​

CodeMessage
IBC-CAP-BLOCKED-001This product class is blocked or model-only for this process.
IBC-CAP-NOT-ADMITTED-001No valid capability admission exists for this company, product class and process.
IBC-CAP-UNRESOLVED-001The company, product class or country could not be determined for this record.

Carrier participation​

CodeMessage
IBC-CARRIER-SHARE-EMPTY-001Add at least one carrier participation.
IBC-CARRIER-SHARE-TOTAL-001Written and signed carrier shares must each total 100 percent.

Commission approval​

CodeMessage
IBC-COM-APPROVAL-PROOF-001Use the Approve action to create a bound approval proof.
IBC-COM-APPROVER-PRINCIPAL-001The approval must belong to the signed-in user.
IBC-COM-APPROVER-ROLE-001The Insurance Broker Accounting Approver role is required.
IBC-COM-SELF-APPROVALThe person who matched a commission line cannot approve the same line.

Commission command​

CodeMessage
IBC-COMMAND-CAPABILITY-001A submitted and validated commission capability is required.

Commission statements​

CodeMessage
IBC-STATEMENT-LINES-001Add at least one commission line.
IBC-STATEMENT-REQ-001Complete the required commission-statement details before saving.

Common record checks​

CodeMessage
IBC-CONTROLLER-COMPANY-001Select a company before saving this record.
IBC-CONTROLLER-CURRENCY-001Select a currency for this monetary record.
IBC-CONTROLLER-DATE-001The end date cannot be before the start date.

Desk actions​

CodeMessage
IBC-DESK-RECONCILIATION-001This statement has no lines that can be reconciled.
IBC-DESK-STATEMENT-STATE-001Reconciliations can only be created for an imported or matching statement.

Documents​

CodeMessage
IBC-DOCUMENT-REFERENCE-STATUS-001An archived document reference cannot be reactivated.
IBC-DOCUMENT-VERSION-IMMUTABLE-001Document versions are immutable once created.

Liability evidence​

CodeMessage
IBC-LIABILITY-ASOF-001The authoritative as-of date cannot be supplied or changed by the caller.
IBC-LIABILITY-COMPANY-001The liability evidence must belong to the same company.
IBC-LIABILITY-CURRENCY-001The liability posting plan currency must match the liability currency.
IBC-LIABILITY-DATE-001Liability dates do not define a valid elapsed-month period.
IBC-LIABILITY-ELAPSED-001Elapsed months are server-derived and cannot be supplied or changed by the caller.
IBC-LIABILITY-EVIDENCE-001An active Agreement with approved Finance and Legal evidence is required.
IBC-LIABILITY-EVIDENCE-BINDING-001Finance and Legal evidence must bind to the same Agreement.
IBC-LIABILITY-ROUNDING-001Agreement and Posting Plan rounding contracts must match.

Mandates​

CodeMessage
IBC-MANDATE-COLLECTION-001Only direct collection by the carrier is supported in this release.
IBC-MANDATE-DATE-001The mandate end date cannot be before its start date.
IBC-MANDATE-EVIDENCE-001An active mandate requires signature and power-of-attorney evidence.
IBC-MANDATE-LOB-SCHEMA-001Use either an explicit non-empty LOB include list or all=true.
IBC-MANDATE-LOB-UNRESOLVED-001The mandate LOB scope does not resolve to an enabled product class.
IBC-MANDATE-REQ-001Complete the required mandate details before saving.
IBC-MANDATE-SCOPE-EXPLICIT-001Mandate activation requires an explicit include list of servicing-eligible LOB classes; all=true is valid only for display and import.
IBC-MANDATE-VERSION-IMMUTABLE-001Create a new mandate version instead of changing the version number.

Parties​

CodeMessage
IBC-PARTY-MINOR-001Add a legal representative for a minor.
IBC-PARTY-SOURCE-001Select the ERPNext document type when a source record is linked.

Policies and policy terms​

CodeMessage
IBC-POLICY-COLLECTION-001Only direct collection by the carrier is supported in this release.
IBC-POLICY-TERM-DATE-001The policy term end date cannot be before its start date.
IBC-POLICY-TERM-IMMUTABLE-001Create a new policy term instead of changing a submitted term.
IBC-POLICY-TERM-LINEAGE-001A policy term after version 1 must reference its previous term.
IBC-POLICY-TERM-LINEAGE-002The previous term must be submitted and belong to the same policy.
IBC-POLICY-TERM-LINEAGE-003The term version must be exactly one higher than the previous term.
IBC-POLICY-TERM-OVERLAP-001This period overlaps another active term for the same policy.
IBC-POLICY-TERM-RECORDED-001The recorded time cannot be before the previous term was known.
IBC-POLICY-TERM-REQ-001Complete the required policy-term details before saving.
IBC-POLICY-TERM-REVIEW-REQUIRED-001A policy term must be approved before submission.

Provider receipts​

CodeMessage
IBC-PROVIDER-RECEIPT-IMMUTABLE-001Provider receipts are immutable once created.

Reserve release​

CodeMessage
IBC-RESERVE-RELEASE-ROUNDING-001The reserve release amount does not match the approved currency rounding contract.

Tender commands​

CodeMessage
IBC-TENDER-COMMAND-COUNTRY-001The Tender company has no country configuration.
IBC-TENDER-COMMAND-PAYLOAD-001Tender command payload must be a JSON object.
IBC-TENDER-COMMAND-PAYLOAD-002Tender command payload is missing a required field.
IBC-TENDER-COMMAND-PAYLOAD-003Tender command payload contains an invalid field.
IBC-TENDER-COMMAND-ROLE-001The signed-in user lacks the Tender command role.
IBC-TENDER-COMMAND-SCOPE-001Tender command company scope is missing or unauthorized.
IBC-TENDER-COMMAND-TRANSITION-001The Tender command is not allowed from the current state.
IBC-TENDER-COMMAND-UNKNOWN-001The requested Tender command is not allowed.

Uninstall guard​

CodeMessage
IBC-UNINSTALL-001Deactivate all Insurance Broker companies before uninstall.
IBC-UNINSTALL-002Cancel, let lapse or let expire all active/suspended policies before uninstall.
IBC-UNINSTALL-003Release all active Legal Holds before uninstall.
IBC-UNINSTALL-004Resolve all open Data Subject Request Cases before uninstall.
IBC-UNINSTALL-005Revoke all active accounting party mappings before uninstall.
IBC-UNINSTALL-006Drain the Outbox Delivery backlog before uninstall.
IBC-UNINSTALL-007Release or reject all queued documents before uninstall.
IBC-UNINSTALL-008Complete or reject all running retention disposition cases before uninstall.
IBC-UNINSTALL-009Export and seal disposition evidence bundles before uninstall.

Tender domain codes​

These codes are raised by the Tender checks in insurance_broker_core/foundation/tender.py. They appear in the form of the code, a colon and a short English text. The numbering is not continuous with the command codes above.

CodeCheckWhen it appears
IBC-TENDER-001Mandate check on the TenderThe linked Insurance Broker Mandate is missing, is not active on today's date, or its scope does not match the Tender.
IBC-TENDER-002Advisor eligibility check on the TenderThe advisor eligibility snapshot is missing, does not show an eligible responsible advisor, or does not cover the line of business.
IBC-TENDER-003Response deadlineA quote was recorded after the response deadline of the invitation.
IBC-TENDER-004Decision evidence on the TenderThe customer decision or remuneration disclosure is missing, does not belong to the Tender advice case, or the disclosure is not confirmed with a customer confirmation reference. Raised when a Tender is saved or commanded to decided.
IBC-TENDER-005Tender Invitation rulesThe linked Tender is missing, the company differs from the Tender, the carrier is invited twice on one Tender, the invitation deadline exceeds the Tender deadline, a decline reason is missing, a quoted invitation has no submission, or the submission context differs from the Tender or invitation.
IBC-TENDER-006Advice case on the TenderThe advice case is missing, does not match the Tender, or its pinned mandate version or regulatory context differs from the Tender.
IBC-TENDER-007Reason for an abort stateA Tender in cancelled, no_result or legal_review_required, or a command that leads there, has no cancellation reason.
IBC-TENDER-008Quote comparisonThe comparison cannot be built because no received quote exists, or the start_comparison or recommend command runs while the Tender has no quote comparison.
IBC-TENDER-009Not-considered markingThe not-considered reason is missing, or the invitation, Tender, customer decision or selected quote is missing or does not share the company and advice case of the Tender.
IBC-TENDER-010Selected carrierThe carrier of the selected quote cannot be marked as not considered.
IBC-TENDER-011Not-considered reason conflictThe invitation is already not considered with a different reason.

Tender status guard​

CodeWhen it appears
IBC-TENDER-STATUS-COMMAND-001A saved change of the Tender status without a transition command. Status changes go through the Tender commands.

State machine codes​

These codes are raised by the shared state machine in insurance_broker_core/foundation/state_machine.py when a command is run against a contract. A combination of state and command that the contract declares as forbidden is rejected with the error code stored for that combination in the contract.

CodeWhen it appears
IBC-STATE-VERSION-001The expected aggregate version differs from the stored version (stale write).
IBC-STATE-TRANSITION-001The state and command pair is not declared in the state machine.
IBC-STATE-ROLE-001The role required for the transition is missing.
IBC-STATE-CAPABILITY-001The transition needs a validated capability admission and none is given.
IBC-STATE-EVIDENCE-001The transition requires evidence and none is given.
IBC-STATE-APPROVAL-001The transition requires an approval and none is given.

Contract validation codes​

The same module validates a contract before it runs a transition. These codes point to a defect in a contract file, not to a user action.

CodeWhen it appears
IBC-STATE-MANIFEST-001Unsupported manifest schema version.
IBC-STATE-MANIFEST-002States, commands or transition matrices are missing.
IBC-STATE-MANIFEST-003The initial or a terminal state is not declared in the state list.
IBC-STATE-MANIFEST-004States or commands are not unique.
IBC-STATE-MANIFEST-005An allowed transition is incomplete or not marked allowed.
IBC-STATE-MANIFEST-006A transition refers to an undeclared state or command.
IBC-STATE-MANIFEST-007A forbidden transition is incomplete or marked allowed.
IBC-STATE-MANIFEST-008The state and command matrix is incomplete or has duplicates.
IBC-STATE-MANIFEST-009A terminal state has an allowed outgoing transition.
IBC-STATE-MANIFEST-010Approval policy and proof type do not agree.