SchemeServe Glossary
Definitions for policy administration, scheme building, accounting and integrations.
How to use this glossary
Find the term shown in SchemeServe. Abbreviations are included beside their full term, with cross-references where terminology overlaps.
Find the term shown in SchemeServe. Abbreviations are included beside their full term, with cross-references where terminology overlaps.
Terminology note: The knowledge base sometimes uses policy, case and record interchangeably. This glossary distinguishes them by lifecycle context while preserving that documented usage.
| Term | Definition |
|---|---|
| A | |
| Access Group | A user grouping used to control access and permissions. The selected access group affects which areas and actions are available to a user. |
| Account Statement | A Digit accounting view of financial entries recorded against an account. It is used when reviewing, reconciling, merging, or investigating payments and transactions. |
| Activity Log | A timeline of actions on an individual policy or case. It can show events such as status changes, referral clearance, and other updates during the case lifecycle. See also: Audit Log. |
| Address No Postcode Question | A Question Set field for capturing an address without a postcode. |
| Address Question | A Question Set field for capturing a full address, including postcode. |
| Adjustment | A change made to a policy during its period of cover. SchemeServe usually records this as a Mid-Term Adjustment, or MTA. See: Mid-Term Adjustment (MTA). |
| Administrator | A user with administrative access to manage areas such as schemes, users, agents, Question Sets, rating files, rules, reports, and site configuration. |
| Agent | The SchemeServe term commonly used for a broker organisation or broker account on a site. Individual broker users can be created beneath the relevant agent account. See also: Broker and User. |
| Agent Statement | A financial statement showing transactions and balances associated with an Agent or broker account. |
| API | An application programming interface that lets external software exchange data with SchemeServe. SchemeServe Developer APIs can read platform data and, for supported operations, send data into SchemeServe. |
| API Authentication | The credentials or security method required to authorise an API request. The exact method depends on the API being called. |
| API Builder | A SchemeServe tool for configuring calls to third-party services within a workflow. Returned data can be stored in hidden questions and then used by rating, referrals, or other actions. |
| API Callback Question | A Question Set field that pulls data into SchemeServe through an API call. |
| API Endpoint | The URL to which an API request is sent. Different endpoints perform different supported operations. |
| API Key | A secret credential supplied with an API request to identify or authorise the calling application when the integration requires key-based authentication. |
| API Rate Limit | The maximum number of API requests permitted during a defined period. SchemeServe API limits should be considered when designing integrations. |
| API Request | The information SchemeServe or an external application sends to an API endpoint, including its method, headers, parameters, and any request body. |
| API Response | The status and data returned by an API after it processes a request. API Builder can store selected response values in hidden questions. |
| Audit Log | A site-wide record in the Admin area that helps administrators trace activity such as logins and changes to clients, policies, schemes, rules, and configuration. See also: Activity Log. |
| B | |
| BACS | A bank-transfer payment method. Payments received by BACS can be recorded and reconciled in Digit. |
| Batch Renewal | A process used to create or manage renewals for multiple eligible policies together, rather than renewing each policy manually. |
| Bearer Token | An API access token supplied in the Authorization header using the Bearer authentication scheme. |
| Bordereau | A structured insurance report or data export, commonly produced from SchemeServe reports for an insurer or another recipient. |
| Broker | A user or organisation that accesses a SchemeServe site to quote, place, and service policies made available by the site's administrator or MGA. SchemeServe setup screens may refer to the broker account as an Agent. See also: Agent. |
| Broker Commission | Commission payable to the broker or Agent. It can be set through rating and appears in the policy's Matrix and financial reporting. |
| C | |
| Calculation Question | A Question Set field used to hold a calculated value. In a SinglePage scheme, calculation questions can appear as rows on the Matrix and can be assigned to a risk group. |
| Cancel Policy | The SchemeServe function used to cancel an active policy. It creates the appropriate cancellation MTA record rather than changing the original On Cover record to Cancelled. |
| Cancellation | The process of ending cover. SchemeServe creates a cancellation MTA record; the original On Cover record should remain On Cover while the cancellation record carries the Cancelled status. |
| Cancellation MTA | The Mid-Term Adjustment record created to represent a policy cancellation. This record carries the Cancelled status. |
| Card Payment | A policy payment collected through a configured card-payment gateway. SchemeServe records the resulting transaction status. |
| Case | A policy-related item being managed in SchemeServe, covering the entire lifecycle. A policy lifecycle may contain linked records for New Business, MTAs, and renewals - all contained under one case. See also: Policy and Record. |
| Cases by Creation Date | A report type that selects cases according to the date the policy or case was created in SchemeServe. |
| Cases by Expiry | A report type that selects records according to their expiry date. It is commonly used for renewal reporting. |
| Cases by Inception | A report type that selects records according to inception date. It is commonly used for premium and bordereau reporting. |
| Checkbox Question | A Question Set field that allows multiple selections, with one question or stored answer for each option. |
| Child Site | A SchemeServe site connected beneath a parent or network-level site. Some configuration and API data access can depend on the parent-child structure. |
| Claim | An insured loss or incident recorded against a policy. Once a policy is On Cover, authorised users can add and manage claims from the policy's Claims tab. |
| Client | The person or organisation being quoted for or insured on a SchemeServe policy. |
| Client Address Field | A predefined Question Set field for storing the client's address. |
| Client Address No Postcode Field | A predefined client address field that excludes postcode. |
| Client Business Description | A predefined short-text Question Set field for the client's business activity or description. |
| Client Company Name | A predefined Question Set field for the client's company name. |
| Client Contact Name | A predefined Question Set field for the customer's or client's name. |
| Client Date of Birth | A predefined Question Set date field for the client's date of birth. |
| Client Deposit | Money held on a client's account in Digit that can be allocated or, where supported, transferred between policies. |
| Client Email | A predefined Question Set field for the client's email address. |
| Client Email and Password | A combined Question Set field used for client login-style email and password capture. |
| Client Mobile Phone | A predefined Question Set field for the client's mobile telephone number. |
| Client Phone | A predefined Question Set field for a landline or general telephone number. |
| Commission | An amount or percentage payable to a broker, agent, insurer, or other party. Commission can be configured in rating and is reflected on the Matrix. |
| Commission Override | A controlled replacement of the normal calculated commission. The override is usually stored in hidden fields and applied after rules and rating are rerun. |
| Copy Row on Export | A reporting option that repeats record-level fields on each exported MultiPage row, so every entity row contains the shared policy information. |
| CORS | Cross-Origin Resource Sharing. Browser-based API integrations may use CORS to control whether requests from a particular origin are permitted. |
| Cover | In policy administration, the protection provided by the policy. In SchemeServe rating, Cover can also mean the numeric amount stored in a calculation field and referenced with a _Cover suffix. |
| Cover Group | A grouping of related calculation questions on the Matrix. When calculation questions are marked as coverage, their values can contribute to the total shown for the group. See also: Risk Group. |
| Credit | A positive accounting entry that increases the amount available or reduces an amount owed, depending on the account and transaction context. |
| CSV | Comma-Separated Values, the file format used for SchemeServe rating files and many data imports or exports. |
| Custom Policy Number | A policy number supplied from an uploaded or configured sequence instead of relying on a standard generated number. |
| D | |
| Data Lookup Cascade | A Question Set field containing linked lookup lists where one selection controls the next, such as country, county, and city. |
| Data Migration | The process of importing existing policy or related data into SchemeServe. Migration structure and mappings must align with the target scheme. |
| Date Picker | A Question Set field that lets the user select a date from a date control. |
| Debit | An accounting entry that reduces the amount available or increases an amount owed, depending on the account and transaction context. |
| Declined | A policy status used when a quotation is declined automatically by scheme logic or underwriting rules. |
| Diary Task | A task assigned in SchemeServe with a status and deadline. Users receive daily email reminders until an outstanding task is completed. |
| Digit | SchemeServe's built-in accounting area. It supports tasks involving payments, transactions, statements, reconciliation, and financial reporting. |
| Direct Client | A customer accessing a SchemeServe quote journey directly rather than through an Agent user. |
| Discount | A negative modifier or adjustment that reduces a premium. SchemeServe rating commonly represents a discount with a negative value. |
| Document | A file or template generated from policy data, such as a quotation, schedule, certificate, or policy wording. Documents can be generated by rules at selected policy statuses. |
| Document Editor | The SchemeServe area used to build and format document templates with HTML, styling, system IDs, formulas, headers, and footers. |
| Document Formula | A formula embedded in a document template to calculate, format, show, or hide content when the document is generated. |
| Document Template | The reusable layout and content used to generate a policy document from SchemeServe data. |
| Download Document Question | A Question Set element that provides a document for the user to download during the quote journey. |
| Draft | A status indicating that quote submission failed but some data was retained. Draft records are incomplete and should not be treated as valid quotations. |
| Dropdown Question | A Question Set field that presents a single-choice dropdown list. |
| DVLA Lookup | A Question Set lookup used to retrieve supported UK driving-licence or vehicle information. |
| E | |
| Email Template | Reusable email content that can be managed in the Email Templates area or built into a rule. Rule-based templates can use a wider range of dynamic fields and formulas. |
| Employers Reference Number | A Question Set field for capturing an employer PAYE reference with the expected slash formatting. |
| Endorsement | A policy term, condition, exclusion, or amendment that can be applied to a record. Rules can apply endorsements automatically and documents can display them. |
| Expiry Date Question | A Question Set date field intended for an expiry date. |
| F | |
| Fee | A monetary amount added through rating or rules, such as a policy fee. In formulas it can be referenced with _Fee, which returns the same field value as _Result. |
| File Lookup Question | A Question Set field whose selectable options come from a lookup file uploaded to the site. |
| File Upload Question | A Question Set field that allows the user to upload a file. |
| First Premium (FP) | The SchemeServe record type used for the original New Business transaction. The abbreviation FP is commonly used in rating files, rules, and reports. See also: New Business and Record Type. |
| First Premium Rating File | The rating file used for the original New Business or First Premium record. Version selection logic is commonly set in this file. |
| Flat Fee | A fixed monetary rating result rather than an amount calculated from Cover multiplied by Rate. |
| Formula | An expression that calculates or returns a value. SchemeServe formulas are used across rating, rules, documents, reports, APIs, and email templates, although available syntax can vary by area. |
| Formula (No Format) | A report column type intended for raw calculations where report formatting should not alter the returned value. |
| Formula Tester | A development tool that evaluates SchemeServe formulas against a selected policy record without changing that policy. It is used to check syntax, system IDs, returned values, and errors. |
| G | |
| Generate Document | A rule action that creates a selected document when the rule's conditions and status criteria are met. |
| Get Answer | A rule condition that reads an answer from the scheme's Question Set. |
| Get Cover | A rule condition that reads the Cover value held against a calculation question. |
| Get Result | A rule condition that reads the calculated Result value held against a calculation question. |
| Gross Written Premium (GWP) | Premium written during a reporting period. SchemeServe guidance commonly uses Cases by Inception with On Cover or Cancelled status criteria for GWP reporting. |
| H | |
| Header and Footer | Reusable content displayed at the top or bottom of generated documents. Document settings and template source can affect how headers and footers render. |
| Hidden Question | A Question Set field that stores information without displaying it in the normal customer journey. Hidden questions are often used to hold API results, calculated values, flags, or data needed by rules. |
| Hidden Scheme | A scheme status that keeps a product unavailable for normal broker or client use. A scheme is changed from Hidden to Live when it is ready to be made available. |
| HTML Source | The source-code view used to edit the HTML and inline styling behind a SchemeServe document, endorsement, email template, or Helpjuice article. |
| I | |
| Inception Date Question | A Question Set date field for the date policy cover begins. |
| Index Linking | The process of increasing selected sums insured at renewal by an index or percentage. SchemeServe can calculate and store the revised amount through rating logic. |
| Insurer | The insurance carrier attached to a scheme or quotation. SchemeServe can run multiple insurers in a configured order and select an available result, subject to rating and referral outcomes. |
| Insurer Commission | Commission payable to or retained by an insurer, as configured in the scheme's rating and financial setup. |
| Invited | A Renewal status meaning the renewal has been approved and is ready to be placed On Cover. It can be set after underwriting review or automatically through Batch Renewals. |
| Invoice | A request for payment recorded as part of the policy payment process. Scheme settings include invoicing among the available payment options. |
| IPT | Insurance Premium Tax. Tax can be configured within a scheme and calculated through rating so it is reflected in the policy premium. |
| J | |
| JSON | JavaScript Object Notation, a structured data format commonly used for API request and response bodies. |
| JWT | JSON Web Token, a token format that may be used by an external API's authentication method where supported by that integration. |
| L | |
| Lapsed | A status used for a renewal record that was not taken up. The expiring live policy remains On Cover for its original period; only the unsuccessful renewal record should be marked Lapsed. |
| Live Scheme | A scheme status indicating that the insurance product is available to the brokers or clients who have permission to use it. See also: Hidden Scheme. |
| Load | A positive modifier or rating adjustment that increases premium in response to a risk factor or commercial rule. |
| Lock Rates | A scheme setting that preserves existing rated values. Where a selected fee or rate must still change, supported SetRate or SetFee actions can use an override. |
| Lookup File | A file uploaded in Admin that stores reusable data. Lookup files can supply dropdown answers and support Question Set triggers, rules, and rating logic. |
| M | |
| Manual Payment | A payment processed outside SchemeServe and then recorded manually against the relevant policy or account. |
| Manual Renewal | A renewal created and processed individually rather than through Batch Renewals. |
| Matrix | The policy tab where rating outputs are displayed. Rating files use answers from the Question Set to populate covers, rates, fees, premiums, commissions, and other calculated results on the Matrix. |
| Mid-Term Adjustment (MTA) | A record used to change an On Cover policy during its term. An MTA can update policy details and produce a premium adjustment while preserving the policy's history. |
| Minimum Premium | The lowest premium permitted by the scheme's rating logic for a cover, group, or record. |
| Modifier | A configured increase or decrease applied to premium calculations. Modifiers are built from Question Set fields and rating logic, then displayed on the Matrix as loads or discounts. |
| Money Question | A Question Set field for entering a currency value. |
| Money Tab | The policy area where payments, monetary transactions, schedules, and related financial activity are recorded or reviewed. |
| More Info | An operational status used when an underwriter needs additional information from an Agent user. It signals a workflow requirement rather than a final policy outcome. |
| MultiPage (MP) | A scheme setup used when one policy covers multiple entities, such as properties or vehicles. The same set of questions is repeated for each entity added to the policy. |
| N | |
| New Business | The first quotation and policy transaction for a new risk. In builder areas and reports, the corresponding record type may be called First Premium or FP. |
| Not Taken Up (NTU) | A status for a New Business quotation that did not proceed. It is distinct from Lapsed, which is used for an unsuccessful renewal record. |
| Notes | Messages stored within a policy to record information or communicate about a case. Notes can be shared with agents or clients and may trigger email notifications. |
| Number Question | A Question Set field that accepts numeric input. |
| O | |
| On Cover | The definitive status for an active policy record. Referrals generally need to be cleared before a broker can place a policy On Cover. |
| Opayo | A supported card-payment provider that can be configured for online policy payments. |
| Open Banking | A payment option that uses bank-account connectivity for supported payment and reconciliation workflows. |
| Origin Header | An HTTP header identifying the origin of a browser-based API request. It can be relevant to CORS validation. |
| P | |
| Page Break | A document-editor instruction that forces the following content to begin on a new page. |
| Parent Site | A network-level SchemeServe site connected to one or more child sites. Parent-child configuration can affect data access and shared structure. |
| Payment Gateway | The external service that authorises and processes an online payment, such as a configured card provider. |
| Payment Option Question | A Question Set field that lets the user choose between configured payment methods. |
| Payment Schedule | A structured plan for collecting policy payments over time. SchemeServe can store payment schedule information against a record and include it in reporting. |
| Payment Transaction | A monetary entry associated with a payment, refund, fee, or other financial event on a policy or account. |
| Pending | A New Business status meaning the quotation has been approved following underwriting review and is ready to be placed On Cover. |
| Percentage of Cover Question | A Question Set percentage field designed specifically for a cover value. |
| Percentage Question | A Question Set field for entering a percentage. |
| Permission Level | A user access setting that controls what a user can see and do in SchemeServe. Permission and referral levels can affect whether a user can process or approve a case. |
| Policy | The insurance contract and its ongoing lifecycle in SchemeServe. A policy can have related records for New Business, adjustments, cancellations, and renewals. See also: Case and Record. |
| Policy Fee | A fee added to a policy through scheme settings, rating, or rules. Rating logic can override the default value shown in settings. |
| Policy ID | The system identifier for a policy, commonly referenced through the [PolicyId] system ID. |
| Policy Status | The current lifecycle state of a record, such as Draft, Quotation, Referred, On Cover, Cancelled, Declined, Lapsed, or NTU. Statuses can trigger rules, documents, and workflow actions. |
| Postcode Lookups | Lookup functionality that enriches a quotation with data associated with a postcode, such as peril or risk information used in rating and referrals. |
| Postcode Perils Data | A Question Set lookup that returns supported peril information based on a postcode. |
| Postcode Question | A Question Set field designed for postcode entry. |
| Premium | The price charged for insurance cover before or after applicable taxes, fees, and adjustments, depending on the specific Matrix or report field being used. |
| Premium Finance | An arrangement where policy premium is paid through instalments or external finance. SchemeServe stores relevant payment details while the finance agreement may be managed externally. |
| Privacy Terms Conditions | A Question Set element used to capture acceptance or confirmation of privacy terms and conditions. |
| Pro Rata | A proportional premium calculation used when cover applies for only part of the full policy term, commonly during an MTA. |
| Q | |
| Question Set | The collection of questions used to capture the information needed for a quote or policy. It can include standard fields, calculations, validations, triggers, tables, and MultiPage questions. |
| Question Set Editor | The SchemeServe builder used to create and configure questions, pages, calculations, validations, triggers, tables, and MultiPage sections. |
| Question Type | The configured input or display style assigned to a Question Set item, such as Text, Money, Dropdown, Address, Table, or File Lookup. |
| Quotation | The standard status applied after a quote is successfully submitted. A quotation is not an active policy until the relevant record is placed On Cover. |
| Quote Journey | The screens and steps a user completes to enter risk information, obtain a quotation, handle referrals, and progress towards cover. |
| R | |
| Radio Question | A Question Set field that presents a single-choice set of radio buttons. |
| Rate | A numeric rating value used in premium calculations. In SchemeServe formulas, a calculation question's rate can be referenced using the _Rate suffix. |
| Rating File | A CSV file containing the scheme's calculation logic. It uses Question Set answers to calculate and populate values on the Matrix. Separate files can be used for different record types. |
| Reconciliation | The accounting process of matching a payment or transaction in Digit to the corresponding bank or policy entry. |
| Record | A specific transaction or stage within a policy lifecycle, such as First Premium, MTA, cancellation, or renewal. Related records preserve the history of the overall policy. See also: Policy and Record Type. |
| Record Created Date | The date and time a specific record was created in SchemeServe. It is distinct from inception, expiry, and status-change dates. |
| Record ID | The unique identifier for a specific policy record or transaction stage. It can be referenced with record-level system IDs. |
| Record Type | The transaction category assigned to a record. Common types include First Premium, Adjustment, and Renewal. |
| Referral | A workflow outcome that sends a case for internal review instead of allowing it to proceed automatically. Referral levels and permissions control who can clear or process it. |
| Referral Level | A setting that controls the level at which a user can process or clear referred cases. |
| Referral Reason | The message or recorded explanation showing why a case was referred. It can be included in referral emails and reports. |
| Refund | Money returned following a payment adjustment, cancellation, overpayment, or other approved financial correction. |
| Renewal (RNL) | A new record created to continue cover for a further term. RNL is a common builder abbreviation for the Renewal record type. |
| Renewal Date | The date on which the next policy term is due to begin or the current policy is due for renewal. |
| Renewal Invitation | The renewal offer or communication issued when a Renewal record is approved and ready for the customer or broker to act on. |
| Renewal Rating File | The rating file used when calculating a Renewal record. Version-selection logic can be set here for the new term. |
| Report | A configurable export or on-screen view of SchemeServe data. Reports can be built around dates, statuses, premiums, transactions, claims, referrals, and other policy information. |
| Report Column | A field added to a report to determine which value appears in the output. Columns can use standard fields or formulas. |
| Report Condition | A filter applied when a report runs, such as scheme, insurer, record status, date, Agent group, or client group. |
| Report Type | The report's underlying selection method, such as Cases by Inception, Cases by Expiry, claims, cancellations, or payment transactions. |
| Reporting Formula | A formula used in a report column. Reporting has its own formula behaviour, so syntax that works in rating or documents may need adjustment. |
| Request Body | The structured content sent with an API request, commonly formatted as JSON. |
| Requote | A new quotation created from an existing record with previously captured data prepopulated. Requoting does not overwrite the original record. |
| REST API | An HTTP-based API style used by SchemeServe Developer APIs to expose supported data and operations. |
| Result | A calculated monetary output associated with a calculation question. In formulas it is commonly referenced with the _Result suffix. |
| Risk Group | A Matrix grouping used to organise related calculation questions and rating outputs, such as a group of covers for one part of the risk. See also: Cover Group. |
| Row Charge | A charge configured against a calculation question or repeated row so its value contributes to rating and the Matrix. |
| Rule | Conditional SchemeServe logic built from IF conditions and THEN actions. Rules can trigger referrals, decline records, generate documents, apply endorsements, send emails, or set values. |
| Rule Action | The THEN part of a SchemeServe rule. Actions can refer or decline a case, set values, send emails, generate documents, or apply endorsements. |
| Rule Builder | The Admin tool used to create SchemeServe rules by combining IF conditions with THEN actions. |
| Rule Condition | The IF part of a SchemeServe rule. Conditions evaluate policy data, question answers, formulas, dates, tables, or other supported values. |
| S | |
| Scheme | A configurable insurance product built on SchemeServe. It defines the Question Set, rating logic, rules, documents, workflows, insurers, and distribution setup needed to quote and administer the product. |
| Scheme Settings | The configuration area for a scheme's status, payments, localisation, policy behaviour, renewals, MTAs, and other product-level options. |
| Send Email | A rule action that sends an email to a configured recipient using rule content or an email template. |
| Set Cover | A rating or rule action that writes a numeric Cover value to a calculation question. |
| Set Fee | A rating or rule action that writes a fee value. An override can be used where locked rates would otherwise prevent the change. |
| Set Rate | A rating or rule action that writes a Rate value. An override can be used where locked rates would otherwise prevent the change. |
| SFTP | Secure File Transfer Protocol. SchemeServe uses SFTP to exchange files securely with insurers, MGAs, and other external systems, including policy, bordereau, claims, and document data. |
| SinglePage | A scheme setup designed for one insured entity, with policy details captured without repeating the same section for multiple entities. See also: MultiPage (MP). |
| Site | A SchemeServe environment containing its own users, agents, schemes, settings, policies, and configuration. |
| Site ID | An identifier supplied with supported API requests to specify the SchemeServe site being accessed. |
| System ID | A stable field reference used to insert or retrieve SchemeServe data in formulas, rules, documents, reports, and integrations. Examples are enclosed in square brackets, such as [PolicyId]. |
| T | |
| Table Question | A Question Set field that captures repeated information in a table layout, such as multiple claims or items. |
| Tag | A label used to organise and search cases or claims and to support filtered reporting or internal workflows. |
| Term Choice | A Question Set field used to select the period of cover, such as six or twelve months. |
| Text Area Question | A Question Set field for entering multi-line text. |
| Text Capitalized Question | A Question Set text field that automatically capitalises the entered text. |
| Text Question | A Question Set field for entering a single line of text. |
| Text Validation From Lookup | A Question Set field that checks entered text against values held in a lookup list. |
| Ticket | A support request submitted to the SchemeServe Obsessive Support team. A ticket keeps the request, conversation, updates, and actions together until resolution. |
| Total Premium | The combined policy premium after the relevant rating outputs, tax, fees, and adjustments included by that field have been applied. |
| Transaction | A monetary entry recorded on the Money tab. In reporting, transaction refers to a financial transaction rather than an endorsement applied to a record. |
| Trial Balance | A Digit accounting report that summarises ledger balances for financial review and reconciliation. |
| Trigger | Question Set logic that shows additional questions when an answer meets a condition. Multiple triggers can be attached to a question. |
| U | |
| Underwriter | A user responsible for reviewing risk, handling referrals, approving quotations, and carrying out authorised policy actions. |
| URL Encoding | The conversion of text into a format that can be transmitted safely in a URL or query string. API Builder formulas can URL-encode system-ID values. |
| User | An individual login with assigned permissions and, where relevant, a referral level. Users may belong to an internal team, broker or agent account, or another access group. |
| User Permission | An individual access control that determines whether a user can view or carry out a specific action in SchemeServe. |
| User Saved | A status for a quote that has been saved for later but not formally submitted. It is a work in progress, not a live quotation. |
| V | |
| Validation | A Question Set check that displays a personalised warning when an answer meets a configured condition. It can help users review values that may cause a referral or require correction. |
| Value | The text or selected answer stored for a question. In formulas, text answers are commonly referenced with the _Value suffix. |
| Versioning | A method for preserving the rates or logic that applied when a record was created. A stored version value can ensure an older policy continues to use its original rating basis even after rates change. |
| W | |
| Write-Off | A Digit accounting adjustment used to clear an approved underpayment, overpayment, or balance that will not be collected or refunded. |
| Y | |
| Yes No Dropdown | A Question Set field that presents Yes and No as dropdown options. |
| Yes No Question | A Question Set field that presents a Yes or No choice as radio buttons. |
Builder shorthand
| Abbreviation | Meaning |
|---|---|
| API | Application Programming Interface |
| FP | First Premium |
| IPT | Insurance Premium Tax |
| MP | MultiPage |
| MTA | Mid-Term Adjustment |
| NTU | Not Taken Up |
| RNL | Renewal |
| SFTP | Secure File Transfer Protocol |
| System ID suffix | Returns |
|---|---|
| _Value | Text representation of an answer |
| _DateValue | Date representation of an answer |
| _Cover | Numeric representation of an answer |
| _CoverBefore | The previous record's Cover value |
| _Rate | The numeric percentage rate |
| _Result | The calculated result or flat fee |
| _ResultBefore | The previous record's Result value |
| _Fee | The same field value as Result |
.png)
