Unique identifier assigned to each contract record. This ID is used as the primary key for referencing the contract within the system.

Specifies the type of contract object, such as distribution agreement, service-level agreement, or consulting agreement, based on the system-defined classification.

System-wide unique identifier that distinguishes this contract across multiple Vault environments or integration layers.

System-generated hyperlink that provides direct access to the full contract record in the Vault interface.

Descriptive name assigned to the contract, typically used for display purposes in user interfaces and reports.

Current state of the contract in its lifecycle, such as Draft, Active, Expired, or Archived, depending on business workflow.

Username or identifier of the Vault user who originally created the contract record.

Timestamp indicating when the contract record was initially created in the system.

Username or identifier of the user who most recently updated the contract record.

Timestamp of the last modification made to the contract record.

Indicates whether the contract is based on a template that is specific to a particular account or customer entity.

Boolean flag that identifies whether the record represents a formal agreement, as opposed to an internal or placeholder document.

Specifies whether this contract supports batch processing, which is useful for automating data imports, exports, or synchronization activities.

Indicates whether this contract serves as the default contract type or template within a specific context or process.

Detailed description of the contract's purpose, scope, or key terms. This is typically used for internal reference and understanding.

Type of device or platform relevant to the contract, such as tablet, mobile, or desktop, used for deployment or compliance tracking.

Custom legal or informational disclaimer text associated with the contract, often shown in summaries or on acceptance screens.

Commercial or regulatory tier assigned to the contract, reflecting pricing levels, partner classification, or access rights.

Date on which the contract's terms officially expire or terminate. May trigger downstream compliance or renewal actions.

Identifier used to reference this contract in external systems such as ERP or CRM platforms. Supports data synchronization and audit traceability.

Specifies the approach or methodology for tracking inventory under this contract, such as manual, automatic, or real-time monitoring.

Timestamp of the most recent batch operation performed on the contract record, such as data import, sync, or workflow execution.

Indicates whether the contract is currently locked from editing, typically due to workflow state, compliance, or review restrictions.

Timestamp marking when the contract was created using a mobile interface or offline application.

Unique identifier associated with the contract in the mobile or offline Vault application. This is used for reconciliation and syncing.

Timestamp of the last update to the contract record made via a mobile interface or offline mode.

Flag that allows administrative users to override a locked state on the contract for emergency or exception handling.

Indicates whether this contract is tied to a specific product or product family, influencing applicability or reporting.

Date on which the contract becomes effective and its terms are enforceable. This is used for timeline and compliance tracking.

Indicates the current state of the contract, such as Draft, Active, Expired, or Terminated. This status reflects the contract's lifecycle and is used for workflow processing and filtering.

Stores the name of the document template associated with this contract. This is typically used to generate contract documents from predefined formats.

Indicates whether this record serves as a reusable contract template. If true, the contract can be cloned or referenced when creating new contracts.

Defines the unit of time used to express contract duration, such as Monthly, Quarterly, or Annually. This value determines how the system interprets contract length.

Specifies the minimum duration required for the contract to remain valid, based on the period type. This is often used to enforce contract compliance thresholds.

Represents the total length of the contract using the specified period type. This field helps calculate expiration dates and manage renewals.

The earliest date on which the contract is scheduled to expire based on its defined duration. This is used for expiration tracking and renewal reminders.

Indicates whether the contract is designated as a corporate-level agreement rather than a local or regional one. Corporate contracts often apply across multiple geographies or entities.

Defines the minimum number of programs that must be executed under this contract for it to be considered valid or fulfilled. Often used in performance-based agreements.

Specifies the upper limit on the number of programs that can be executed under the contract. Helps prevent overspending or overuse of contract scope.

Captures the number of programs that have been successfully completed under the current contract. This helps track execution progress and assess fulfillment.

Describes the primary purpose or goal of field representative calls conducted under this contract. This can relate to educational, promotional, or compliance objectives.

References the document or catalog template used when printing contract-related materials. This is typically linked to predefined EM (Event Management) templates.

Identifies the wholesale distributor or intermediary associated with the contract. This field supports supply chain coordination and financial tracking.

References the speaker or key opinion leader (KOL) who is contracted to participate in events or programs under this agreement. This is important for event planning and speaker management.

Specifies the type of event covered by the contract, such as Speaker Program, Advisory Board, or Webinar. This categorization is used for reporting and compliance purposes.

Lists the product or group of products included in the contract terms. Helps ensure alignment between contracted services and marketed assets.

Indicates the healthcare institution or facility associated with the contract, such as a hospital, clinic, or research center. Important for event logistics and regulatory compliance.

Identifies the user or system account responsible for managing the contract record. Often corresponds to the field representative, contract administrator, or system integration user.

Represents the total amount of payment defined in the contract for services rendered or products promoted. This is used for budgeting and financial reconciliation.

Captures the corporate-level total payment associated with the contract. This is typically used in roll-up calculations across business units or geographies.

Specifies the currency in which the contract values, such as total payment, are expressed. Supports global financial reporting in region-specific currencies.

Indicates whether the contract has reached or passed its expiration date. Helps with filtering out inactive or historical contracts in reports and workflows.

Holds the identifier from the legacy Customer Relationship Management (CRM) system for backward compatibility and migration tracking.

Specifies the language in which the contract content is written. This is useful for localization, document generation, and multilingual compliance reviews.

Indicates whether the contract document is pending finalization or official rendering. This status helps monitor document readiness for execution.