PCON: Purchase Contract
The PCON entity represents a purchase contract linking a vendor to a programme/portfolio with payment milestones, spend tracking, and document management.
PCON definition shipped with DemandFlow. Administrators can add, remove, rename, or re-type fields, change which ones are required, and alter the layout from the Definitions screen in Settings. Your tenant's current schema may differ from what is shown here. To read the current definition at any time, GET the DEFINITION object whose id matches PCON.Entity properties
| Property | Value |
|---|---|
| Entity code | PCON |
| Display name | Purchase Contract |
| Plural | Purchase Contracts |
| Level | 420 |
Use cases
PCON represents long-term purchase agreements or contracts with vendors, distinct from individual purchase orders (PO). It sits above PO in the procurement hierarchy, providing a contractual umbrella under which multiple POs may be raised. The entity links to PORT (Portfolio) and PROG (Programme) for strategic alignment, and to VEN (Vendor) for the supplier relationship. The payment milestones relatedlist (PMS entity, linked via SUB|PCON|PMS comboKey) breaks the contract value into scheduled payments, each with its own date, value, spend type, and monthly forecast. The contract type field distinguishes pre-purchase agreements from committed spend. The status field (Active/Inactive) controls whether the contract is in the current plan. Some field IDs use UUIDs (e.g. c4cf43b6 for Notes, 84950828 for Contract number) indicating fields added dynamically through the definition editor. The file attachment row supports contract document storage. Business owner and created-by fields provide governance accountability.
Fields
General
| Field | Type | Required | Notes |
|---|---|---|---|
ownerId | reference → user | Created by. Read-only. | |
name | text | Yes | Contract Name. |
description | text (multi-line) | Description. | |
portfolio | reference → PORT | Portfolio. | |
programme | reference → PROG | Programme. | |
status | enum | In plan. Valid ids: Active (Active), Inactive (Inactive). | |
programme | reference → PROG | Programme. | |
vendor | reference → VEN | Vendor. | |
busOwner | reference → user | Business owner. Read-only. | |
c4cf43b6-69c4-4160-989d-20ede6fb222b | text (multi-line) | Notes. | |
84950828-46dd-411c-9743-b10e319de9f2 | text | Contract number. | |
d5c79149-f420-40a2-8faf-01cd887c2520 | enum | Type. Valid ids: Pre-purchase (Pre-purchase), Committed spend (Committed spend). |
Additional panels
- Documents. Field
attachments.
Relationships
- Lookups:
portfoliopoints atPORTrecord;programmepoints atPROGrecord;programmepoints atPROGrecord;vendorpoints atVENrecord. - Related lists:
PMSvia formatSUB|PCON|PMS.
Creating a Purchase Contract via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "PCON",
"level": 420,
"comboKey": "SUB:<your-sub-id>|ENT:",
"name": "Example",
"description": "Long description text.",
"portfolio": "",
"programme": ""
} Listing PCON records
# All purchase contracts in your tenant
GET /v1/entities/PCON/SUB