An AFE (Authorization for Expenditure) is the moment a capital decision becomes real — the point where a proposed investment gets a number, a funding source, and a signature. But approval isn’t the finish line. The real test of capital project management software is what happens after: does that approved number actually govern what gets spent, or does it become a static PDF while the real spending happens somewhere else, tracked by a different team, in a different tool?
Most organizations can answer “was this AFE approved?” They struggle to answer “is this project still spending within what was approved, and what physical asset did that money actually produce?” That gap — between a funding decision and the executed, physical result of it — is where capital programs quietly lose control of their own numbers.
This guide covers the seven capabilities that keep an AFE connected all the way through to the asset it funds, what it actually costs an organization when that connection breaks, and the questions worth asking before choosing a platform to manage it.
In This Guide:
→ Why AFE Approval and Execution Usually Live in Different Systems → 7 Capabilities That Connect AFE to Asset → What a Disconnected Funding-to-Asset Process Actually Costs → Questions to Ask During a Capital Project Management Software Evaluation → How PACE Approaches This, End to End → Frequently Asked Questions (FAQs)
Why AFE Approval and Execution Usually Live in Different Systems
An AFE typically gets built and approved in one place — a finance system, a board deck, a standalone approval tool — because that’s where the governance and the signatures need to happen. Execution, meanwhile, happens in project management software, spreadsheets, or an ERP module that has no idea an AFE ever existed.
The handoff between the two is usually manual: someone re-keys the approved amount into a new project record, sets up a budget that resembles the AFE but isn’t formally tied to it, and moves on. From that point forward, the AFE is a historical document. Nobody’s system automatically checks whether actual spending is tracking against what was authorized, whether the funding source it drew on still has capacity, or whether the physical asset the project was supposed to produce has actually shown up.
That disconnect isn’t a discipline failure — it’s what happens by default when authorization and execution are architecturally separate systems. Fixing it requires more than a report that compares two numbers once a quarter. It requires the AFE, the funding, the project, and the resulting asset to be the same continuous data thread.
7 Capabilities That Connect AFE to Asset
These are the capabilities that keep a capital decision governed from the moment it’s requested to the moment it becomes a usable asset.
1. A Single AFE That Captures the Full Ask
An AFE needs to hold everything a funding decision actually depends on: Capex and Opex split by category, effort by discipline, expected benefits, and a year-by-year planning spread — not just a single lump-sum number that hides what it’s actually made of.
- Can the AFE break spend down into labor and non-labor categories (Contingency, Equipment, Material, ODC, Subs)?
- Does it validate that the components actually add up to the total being requested?
- Can the same AFE spread its request across multiple planning years?
Inside PACE: PACE structures every AFE around Capex and Opex captured by category, resource type, and planning year — and enforces a hard validation rule: Capex plus Opex must equal the total cost of the request. An AFE that doesn’t add up can’t be submitted for approval in the first place.
2. Automatic AFE Generation From What’s Already Approved
A recurring or follow-on capital request shouldn’t start from a blank form. If a project already has an approved, baselined forecast, the next funding cycle’s AFE should be able to start from that reality instead of a fresh guess.
- Can a new AFE be generated directly from an existing project’s baselined forecast?
- Does that generation start from a specific planning year forward, rather than forcing a full re-entry?
Inside PACE: PACE’s Generate AFE function populates a new AFE automatically from the last baselined forecast, starting from whichever planning year is selected forward — connecting what a project actually costs today to the next round of funding, instead of starting the request from scratch.
3. Funding Sources Defined Before Money Gets Committed
An AFE requesting money is only as credible as the funding source behind it. Reserves, grants, and debt aren’t interchangeable, and a capital planning system should know the difference before it lets anyone commit against them.
- Are funding sources (reserves, grants, debt) defined explicitly, by planning year and business line?
- Can funding rules be enforced at the organization level as well as by business unit?
Inside PACE: PACE’s Organization Budget defines funding sources by planning year and by business line or SBU, with business rules enforced at whichever level the organization operates — so a request is only ever competing for money that’s actually been documented and set aside.
4. A Portfolio That Prioritizes, Not Just Lists
When there are more eligible projects than available funds — which is the normal state, not the exception — a spreadsheet listing every AFE doesn’t help anyone make a decision. What’s needed is a working portfolio that lets a team model different combinations before committing.
- Can eligible AFEs be pulled into a single portfolio for prioritization, rather than reviewed one at a time?
- Can specific projects be included or excluded from a funding scenario before anything is finalized?
- Once decided, does publishing the portfolio formally allocate funds, not just record a decision?
Inside PACE: PACE’s Planning Portfolio pulls in every AFE marked Submitted for Funding Approval into one container, lets a team include or exclude candidates and propose amounts, and then publishes a final funding allocation — turning portfolio prioritization into a governed step, not a spreadsheet exercise that happens before the real system gets updated.
5. Funding Lines That Can’t Drift From What’s Actually Left
Once a project is funded, the number that matters day to day isn’t the original approval — it’s how much of that funding is actually still available. That number has to update as spending happens, and the system should refuse to let anyone commit past it.
- Is remaining funding tracked continuously against consumed funding, not just checked at approval time?
- Does the system prevent a new allocation from exceeding what’s actually left?
- Does it prevent funding from being reduced below what’s already been spent?
Inside PACE: PACE tracks Consumed Funds against Remaining Funds on every funding line, with alerts as a project approaches its threshold — and enforces two rules at the data level: a proposed allocation can never exceed remaining funds, and funding can never be reduced below what’s already been consumed. The number a Controller sees is never one a spreadsheet formula could quietly get wrong.
6. Programs That Consolidate Without Double-Counting
Large capital portfolios group related projects into programs for shared governance and reporting. That consolidation only works if a project’s spend can’t accidentally get counted under more than one program, and if the program’s budget model — top-down or bottom-up — actually matches how the organization wants to fund it.
- Can a program’s budget be managed top-down (allocated from the program level) or bottom-up (managed at the project level and consolidated up)?
- Does the system prevent a project from being tied to more than one active program at a time?
Inside PACE: PACE’s Capital Program supports both Top-down and Bottom-up budget models, and enforces a hard rule that a capital project can be associated with only one active capital program — preventing the kind of double-counted spend that quietly inflates a program’s real financial exposure.
7. A Closed Loop From Capital Spend to the Asset It Created
The entire point of a capital AFE is that it produces something — a piece of equipment, a facility, an upgraded system. If the connection between what was spent and what physically exists now has to be reconstructed by asking around, the capital planning system has failed at its actual job.
- Can specific physical assets be registered and linked directly to the project that created them?
- Does the asset record carry in-service date, location, and the task or cost that produced it?
Inside PACE: PACE’s Project Assets registry captures each asset’s name, type, in-service date, book, units, location, the task it’s tied to, and any additional estimated cost — creating a direct, traceable link between what was authorized in the AFE and the physical asset that request ultimately produced.
What a Disconnected Funding-to-Asset Process Actually Costs
Consider an organization with $50M in annual capital reserves and a Planning Portfolio holding $68M in eligible, submitted AFEs — a normal, not extreme, funding gap. Without a governed portfolio, prioritization happens informally: whoever escalates loudest, or whoever asks first, tends to get funded first, regardless of strategic priority.
With a working portfolio, the same $50M gets allocated deliberately: $41M across the highest-priority projects, $9M conditionally approved pending a mid-year funding review, and $18M in eligible requests explicitly deferred rather than silently ignored. Every stakeholder can see not just what got funded, but what didn’t, and why.
Now follow one $6M project through execution. Without connected funding lines, a $900K change order gets approved locally by a project manager without anyone checking whether $900K of headroom actually still exists on that funding line — because nobody’s system tracks remaining funds in real time. In a connected system, that same change order gets checked automatically against actual remaining funds before approval, and gets rejected or escalated if it would push the project past what’s authorized.
This is an illustrative scenario, not a specific customer figure — but the mechanism is exactly what disconnected AFE tracking produces at scale: funding decisions made on stale numbers, and overruns that surface only once the money is already spent.
Questions to Ask During a Capital Project Management Software Evaluation
- Can an AFE capture Capex and Opex separately, and does the platform validate that they reconcile to the total request?
- Can a new AFE be generated automatically from an already-approved, baselined project forecast?
- Are funding sources (reserves, grants, debt) defined explicitly by planning year and business line?
- Can a portfolio of eligible AFEs be modeled — including and excluding candidates — before funds are finalized?
- Does the system track consumed vs. remaining funds continuously, and prevent allocations from exceeding what’s left?
- Can capital programs be modeled top-down or bottom-up, and does the platform prevent a project from belonging to more than one active program?
- Is there a direct link between an approved AFE and the physical asset it ultimately produces?
- Does the vendor distinguish between capital funding data (which may stay internal) and approved project budgets that need to reach the corporate ERP?
How PACE Approaches This, End to End
The pattern underneath all seven capabilities is the same: PACE treats an AFE not as a document that gets approved and archived, but as the first link in a data chain that runs through the funding source, the portfolio decision, the project’s execution, and the asset it produces. Funding rules — remaining funds, consumed funds, program association — are enforced automatically at every step, so the numbers a Controller relies on can’t drift from what the system actually allows.
One distinction worth being direct about: capital funding references and funding lines in PACE are maintained locally and are not, in this flow, sent to the corporate ERP — that integration happens separately, when a project’s detailed budget is approved during Planning. The two are related but distinct steps, and knowing which one applies where is part of evaluating any capital planning platform honestly.
That’s the standard PACE was built to meet: not a system that approves capital requests and hopes execution stays aligned, but one where alignment is enforced by the data model itself, from AFE to asset.
Frequently Asked Questions (FAQs)
What is an AFE in capital project management software?
An AFE (Authorization for Expenditure) is a formal request to fund a capital investment, capturing the cost breakdown (Capex/Opex), funding source, and expected benefits. In PACE, it’s the entry point to a governed workflow that carries through funding approval, execution tracking, and asset registration.
Does PACE’s AFE and funding data integrate with our ERP?
Capital funding references and funding lines are maintained within PACE and are not sent to the ERP in this flow. Once a project’s detailed budget is approved during Planning, that approved budget structure is what integrates automatically with the connected corporate ERP — a separate, later step in the lifecycle.
What’s the difference between an AFE and a capital program?
An AFE is a funding request for a single project. A Capital Program groups multiple related projects under shared governance, with a budget managed either top-down (allocated from the program level) or bottom-up (consolidated from individual project budgets). A project can only belong to one active capital program at a time.
Can funding be adjusted after a project starts?
Funding lines can be adjusted, but PACE enforces two rules regardless: a proposed allocation can never exceed remaining available funds, and funding can never be reduced below what’s already been consumed — protecting both the organization’s budget and the project’s already-incurred cost.
What happens if a portfolio doesn’t have enough funds for all requested AFEs?
The Planning Portfolio lets a team model different combinations of eligible AFEs, including or excluding candidates and proposing specific amounts, before publishing a final funding allocation — turning a limited-funds scenario into a deliberate prioritization decision rather than a first-come, first-served outcome.
How does PACE keep spending connected to the asset a project produces?
PACE’s Project Assets registry links each physical asset directly to the project that created it, capturing its type, in-service date, location, and the task or cost tied to it — so the connection between what was authorized and what actually exists is documented from the start, not reconstructed after the fact.
Can an AFE be partially funded?
Yes — PACE tracks this explicitly as “Conditionally Approved,” which occurs when the funding actually published for an AFE is less than what was originally requested, giving finance teams a clear status distinct from full approval or rejection.
