Contracts, templates and signatures

Upload a purchase-contract attachment

Attach a file to a contract.

Audience: Purchasing staffPermission: purchase_contracts capabilityModule v1.7.9

Exact navigationAdmin Area → Purchase → Contracts → open contract → Files → Upload

Before you begin

Use an account with purchase_contracts capability and confirm the intended record or setting before making a change.
Follow the exact route above. If the screen or action is absent, check module activation, ownership and permissions rather than using another person’s account.
Use controlled test data for configuration, integration, email, AI, payment, portal or automation changes before production-wide use.

What this guide covers

Attach a file to a contract. The instructions reflect the supplied module’s registered menus, controller actions, views, settings and code-backed validation flow.

Exact step-by-step process

Open Admin Area → Purchase → Contracts → open contract → Files → Upload.
Download or inspect the supported template/field requirements before preparing the file.
Choose the Import or Upload action and select the intended file only.
Run validation and correct rejected rows, file types or required values.
Complete the import/upload and review the created records, attachments and any error file.

Fields, choices and supported possibilities

Contract headerContract name, vendor, purchase order, project, department and service category.

Commercial termsPayment terms, payment amount, payment cycle, contract value, notes and description/content.

SigningSigner, email, signed status, drawn/uploaded signature, send recipients, attach-PDF choice and SMS option where enabled.

Code-backed validations and workflow rules

Contract actions are governed by purchase_contracts capabilities.
Signature/send flows depend on the stored signer/email and configured email/SMS services.

Expected result and verification

The supported upload a purchase-contract attachment flow completes without bypassing permission or validation checks.
The resulting record, setting, status, file, delivery event or external response is visible from the relevant workspace.
Unexpected validation, provider or linked-record errors are investigated before retrying.

Security, privacy and operational checks

Apply least privilege to purchasing, vendor, invoice, payment, return, contract and report permissions.
Verify vendor identity, bank/payment details, tax, currency, totals and approvals before creating financial commitments.
Treat public links, signatures, portal files, attachments and exported reports as controlled business records.
Test settings and automated jobs with controlled records before production-wide use.