Approval authority and delegation policy
Approval authority must follow documented limits for role, value, department, project, and transaction type. Approvers should act independently and disclose conflicts of interest. Delegation must be time-bound, approved, and assigned to a user with equivalent authority. Delegates must not share credentials or authentication codes. Administrators should review active delegates and privileged approvers regularly, remove expired delegations promptly, and preserve the approval history for audit.
Related Articles
Request approval workflow: illustrated guide
A typical request moves from creation and supporting evidence to manager review, finance review, and final processing. Your organization’s approval path may vary by amount, department, location, project, or request type. Approvers should review the ...
Using approval in principle
Audience: Budget owners, procurement administrators, approvers, and requesters using an approved AIP An Approval in Principle (AIP) pre-approves a spending budget, so that purchasing against it later can move faster and stay inside agreed limits. ...
Administering a Spendive organization
Audience: System administrators and implementation owners Setting up departments Departments group your people, and are used across the application to route approvals and report on spend. Where to find them Administration → Departments. The page ...
Record retention and deletion policy
Retain requests, approvals, documents, procurement records, payments, accounting entries, and audit history for the period required by law and organizational policy. Do not delete records to conceal errors or bypass workflow. When deletion is ...
Procurement competition and quotation policy
Purchases should follow the organization’s quotation and competition thresholds. RFQs must describe the same scope to each invited vendor and allow a reasonable response period. Evaluation must consider price, quality, delivery, capacity, risk, and ...