Purchase requisitions (PRs) bypassed budgets; ServiceNow–Anaplan pre-checks with finance approvals kept spend to plan

Overview

A public sector agency routinely overspent budgets because purchase requisitions (PRs) were created without timely checks against the plan. Budget availability was reconciled after approvals, retro waivers piled up, and Finance had little visibility into why exceptions happened. Intelligex integrated PR creation in ServiceNow with Anaplan budgets, enforced guardrails at request time, and routed exceptions to a CFO approval workflow with full logging. PRs were evaluated against current budgets before commitment, fewer retro approvals were needed, spend tracked to plan, and Finance could see and manage exceptions in one place—while ServiceNow, Anaplan, and the ERP remained unchanged.

Client Profile

• Industry: Public sector agency (multi?department operations)
• Company size (range): Multi?entity, multi?fund structure with grants and capital projects
• Stage: ServiceNow used for PR intake; Anaplan for planning and budgets; ERP for POs and invoicing; budget checks performed after approval via spreadsheets
• Department owner: Finance & Accounting (Budget Office and Controllership)
• Other stakeholders: Procurement, Departmental Requesters, Grants Management, Program Managers, IT/Service Management, Internal Audit

The Challenge

PRs moved through approvals without a reliable pre?check against available budget. Department requesters submitted items in ServiceNow, approvers reviewed business need, and only after Procurement converted a PR to a PO did Finance validate budget availability. When a budget line lacked funds, exceptions were handled via email and spreadsheets. Retro waivers, reclassifications, or urgent budget transfers were common and consumed close time.

Budget lineage was opaque. The agency managed operating, grant, and capital budgets in Anaplan with fund, department, program, project, and object detail, but ServiceNow PRs carried free?text or partial coding. The mapping between PR coding and the budget structure lived in local files. Budget updates, reforecasts, and transfers didn’t reliably flow into the PR process, so requesters and approvers operated on stale numbers. Internal Audit noted that approvals for over?budget requisitions were inconsistently documented and difficult to trace.

Why It Was Happening

Root causes were fragmented tools and the absence of a governed budget check at PR intake. ServiceNow captured the request; Anaplan held the current plan and changes; the ERP recorded obligations and actuals. There was no shared layer to align PR coding to budget lines, check availability at the time of request, and route exceptions with a clear approval path. Budget guardrails and thresholds existed in policy documents, not in a rules engine. As a result, overspends surfaced late, and approvals became after?the?fact justifications.

Ownership and timing were misaligned. Departments owned requests, Procurement owned PR workflow, Finance owned budgets and policy, and IT owned systems. Without a pre?encumbrance check and CFO?level exception workflow, teams relied on manual transfers and email sign?offs to keep operations moving.

The Solution

Intelligex delivered a budget?aware PR workflow that connected ServiceNow to Anaplan and enforced finance?owned guardrails at request time. When a PR was created in ServiceNow, coding was validated and mapped to budget lines; the pipeline queried Anaplan for available balance, applied guardrails and tolerances, and returned a decision: proceed, proceed with conditions, or escalate. Exceptions routed to a CFO approval queue with required rationale and attachments. Approved outcomes and any budget adjustments were logged with effective dates and synced back to Anaplan and the ERP as needed. The approach leveraged ServiceNow workflow capabilities and Anaplan as the system of record for budgets; Procurement and ERP processes remained intact.

• Integrations: PR intake and approvals in ServiceNow; current budgets, reforecasts, and transfers from Anaplan; optional encumbrance and PO updates to the ERP; notifications to collaboration tools.
• Canonical budget schema: Standardized fields for fund, department, program, project, object, period, available balance, and owner; identity crosswalks to PR coding and ERP segments.
• Guardrails and tolerances: Finance?owned rules for hard stops, conditional approvals, and allowable variances by fund, grant, or project; effective?dated changes with rationale.
• Exception workflow: Escalation to CFO or delegate with required attachments (business justification, alternate funding, grant terms); maker?checker approvals and segregation of duties enforced.
• Mapping and validation: PR coding validated at entry; auto?suggested budget lines based on item and department context; low?confidence mappings routed for review.
• Sync and lineage: Approved decisions logged with links to PR, budget line, and rule version; optional pre?encumbrance updates to ERP pending PO creation; post?PO updates reconciled to approval.
• Dashboards: Budget check outcomes by department and fund, exception aging, top drivers of escalations, and rule changes; drill?downs to PRs and budget lines.
• Audit trail: Immutable logs of checks, approvals, transfers, and postings with attachments; exportable evidence packs per period and fund.

Implementation

• Discovery: Mapped current PR and approval paths in ServiceNow; cataloged budget structures, reforecast cadence, and transfer policies in Anaplan; inventoried ERP segments and encumbrance practices; gathered historical exception emails and audit findings.
• Design: Defined the canonical budget schema and coding crosswalks; authored guardrail and tolerance rules by fund, grant, and project with effective dating; designed exception reason codes, approval tiers, and required attachments; specified sync points to Anaplan and the ERP; planned dashboards and evidence exports.
• Build: Implemented ServiceNow integration for PR events and approval tasks; built the budget check service against Anaplan with caching and refresh logic; developed rules enforcement and escalation workflows; configured mapping validation and review queues; assembled dashboards and audit logging.
• Testing/QA: Ran in shadow mode: evaluated live PRs with draft checks while the legacy process continued; reconciled decisions against Finance policy; tuned mappings and guardrails; piloted CFO approvals and evidence capture for select departments.
• Rollout: Enabled budget checks for a subset of funds and departments first; retained manual exception handling as a controlled fallback; expanded coverage as rules stabilized; enforced mandatory CFO approvals for over?budget exceptions after training.
• Training/hand?off: Delivered sessions for requesters, approvers, Procurement, and Finance on coding validation, interpreting outcomes, and handling exceptions; updated SOPs for PR intake, budget transfers, and grant constraints; transferred ownership of rules, mappings, and dashboards to the Budget Office under change control.
• Human?in?the?loop review: Established periodic reviews to assess exception trends, rule thresholds, and mapping drift; decisions recorded with rationale and effective dates.

Results

Budget control shifted to the start of the process. PRs were checked against up?to?date Anaplan budgets before commitment, requesters saw clear outcomes, and approvers acted on consistent guardrails. Fewer retro waivers were needed because exceptions were routed and documented at request time with CFO sign?off where policy required. Procurement spent less time reconciling PRs to funding late in the cycle.

Finance gained visibility into exceptions and drivers. Dashboards showed where over?budget requests originated, which funds or grants drove escalations, and how rule changes affected outcomes. Audit support improved with logs tying each exception to policy and approvals. ServiceNow and Anaplan stayed in place; the change was a budget?aware orchestration layer that aligned policy and execution.

What Changed for the Team

• Before: Budget checks happened after approval. After: PRs were evaluated at creation against current Anaplan budgets.
• Before: Exceptions were handled via email. After: Over?budget requests routed to a CFO approval queue with required attachments and rationale.
• Before: PR coding was inconsistent. After: Coding was validated and mapped to budget lines with review for low?confidence cases.
• Before: Retro waivers and transfers consumed close time. After: Decisions and any adjustments were logged at request time with effective dates.
• Before: Finance lacked visibility into drivers. After: Dashboards surfaced exception trends by department, fund, and project.
• Before: Audit trails were reconstructed. After: Each decision carried citations to rules, approvals, and PR/PO lineage.

Key Takeaways

• Move budget control upstream; check availability and coding when the PR is created, not after approval.
• Encode guardrails; finance?owned rules and tolerances by fund and grant need effective dating and rationale.
• Make exceptions a workflow; route to CFO or delegate with required evidence and maker?checker approvals.
• Normalize coding; validate and map PR segments to budget lines to prevent drift.
• Preserve lineage; log checks, approvals, and adjustments with links to PRs, budget lines, and rule versions.
• Integrate, don’t replace; keep ServiceNow and Anaplan, and add a governed budget?aware layer between them and the ERP.

FAQ

What tools did this integrate with? PR intake and approvals remained in ServiceNow. Budgets, reforecasts, and transfers were read from and, where appropriate, updated in Anaplan. The ERP continued to manage POs, encumbrances, and actuals; the pipeline optionally posted pre?encumbrance markers and reconciled PO creation to approved PR decisions.

How did you handle quality control and governance? Guardrails and tolerances lived in a finance?owned rules registry with effective dating and rationale. Coding crosswalks were versioned under change control. Each over?budget PR required maker?checker approval up to the CFO or delegate with attachments. All checks, approvals, and adjustments were immutably logged with links to PRs, budget lines, and rule versions.

How did you roll this out without disruption? The budget check ran in shadow mode first, evaluating live PRs while teams followed existing steps. Outcomes were compared to policy, and mappings and thresholds were tuned. Rollout started with selected funds and departments, then expanded as stability grew. Manual exception handling remained as a controlled fallback during early cycles.

How were budget checks performed and updated? The service mapped PR coding to the canonical budget schema, queried Anaplan for current available balance by period, applied guardrails and tolerances, and returned a decision to ServiceNow. When Finance changed guardrails or thresholds, updates were effective?dated and applied prospectively, with prior versions preserved for historical reference.

How did you handle grants and multi?year funding? Guardrails accommodated fund source rules, including grant period restrictions and cost eligibility by object or project. The schema carried period and funding attributes so PRs were checked against the correct window. Exceptions required attachments and rationale referencing grant terms, and approvals were captured alongside the PR.

What happened when PR coding didn’t match budget structures? The mapping layer suggested likely budget lines based on department, item, and prior patterns. Low?confidence mappings entered a review queue for correction before checks proceeded. Confirmed mappings updated the crosswalk under change control.