How Can You Add Line Items to a Budget in Procore? (w/Examples) + FAQs

You add a budget line item in Procore by opening the Budget tool, clicking Create, and entering a cost code, cost type, quantity, and unit cost. Procore then does the math for you, and a single project budget can hold hundreds or thousands of items, so the method you pick matters.

Typing 400 rows by hand instead of importing them can cost you an afternoon, and one wrong cost code can quietly send spend to the wrong place for months. The right method depends on whether you are starting a budget from scratch, patching a gap mid-project, or pulling data from a finished estimate.

What a Procore Budget Line Item Represents

A budget line item is one row in Procore's Budget tool. Each row stands for one slice of a project's planned spending. Procore builds every row from a budget code, and that code always has two required parts.

The first part is the cost code, which names the type of work, like concrete or wiring. The second part is the cost type, such as labor, material, equipment, or subcontract. Together, these two parts show what the money pays for and how it gets spent.

Some companies add a third, optional part called the sub job. A sub job splits costs by building, phase, or site area on one project. A builder putting up three townhomes on one lot might give each building its own sub job, so the three budgets never mix.

This whole setup is called the Work Breakdown Structure, or WBS. Every line item must use one unique mix of cost code, cost type, and sub job. You cannot create two line items with the exact same mix, because Procore treats that mix as the row's ID.

Many new admins assume one line item stands for one task or one trade contract. That guess is a common wrong idea. One trade can span several line items, split across labor, material, and equipment, since a line item tracks a cost category, not a single task.

Getting this setup wrong rarely triggers an error on the spot. Procore still lets you post commitments and change orders against a mismatched line item with no warning. The real cost shows up months later, when a manager compares labor spend across two jobs and finds the cost categories do not line up at all.

Before you add a single line item, check your company's default WBS under company-level settings. A project-specific WBS should only stray from that default when the project truly needs a finer level of tracking. A clean, steady WBS also makes an audit faster, since anyone checking the budget later can trace a dollar back to its exact type of work.

Three Ways to Get Line Items Onto a Budget

Procore gives you three distinct paths onto a budget, and picking the wrong one for the moment is the top source of rework. The first path is manual entry, where you add one full line item at a time with its own quantity, unit cost, and calculation method. This path fits a small project, or a few late additions to an active budget.

The second path is a partial line item, a stripped-down row that carries only a budget code with no dollar value yet. Teams use this path when a cost lands on an invoice or a change order before anyone ever planned for it. It flags the gap right away, instead of hiding it inside a line item that was never meant to carry that cost.

The third path is bulk creation, either by loading a spreadsheet through the Import a Budget tool, or by sending a finished estimate straight into the budget. When an estimate is sent over, Procore builds one line item for every unique budget code it finds in that estimate. Bulk creation is the right call whenever you are setting up a whole project's budget at once, or loading fifty-plus rows that already sit in a clean file.

Typing that much data by hand invites typing mistakes that a bulk load simply skips. One mistyped cost code in row 340 of 400 is easy to miss on a screen, but a clean spreadsheet import applies the same codes every single time, with no drift. New budget codes get created on the fly during import, so matching codes do not need to exist before you load the file.

Step-by-Step: Adding a Full Line Item Manually

Before you add anything, check your permission level on the project first. Standard-level Budget tool access lets you create a new line item, and that part is usually simple. If your Standard access came from a company permission template, though, a second setting called Modify Original Budget Amount must also be turned on. Skip that step, and your new line items save with no dollar value at all.

Admin-level access is a separate need, used only when you want to edit the original budget amount on a line item someone else already made. A project manager with plain Standard access, plus that one extra setting, can still create fresh line items freely. Once both permission pieces check out, the manual path runs through the same six fields. This holds whether your company sees the classic Budget tool, or the newer product-manual interface some accounts moved to as of 2026.

1. Go to the project's Budget tool and open the Budget tab.
2. Click Create and choose Budget Line Item from the drop-down list.
3. Pick a Cost Code from the drop-down, standing for the type of work.
4. Pick a Cost Type, and a Sub Job if your company tracks by area or phase.
5. Choose Calculate Subtotal Automatically, or Override Subtotal Manually to type a fixed amount.
6. If calculating automatically, enter the Unit Quantity, Unit of Measure, and Unit Cost.
7. Save the line item and check that the Original Budget figure looks right.

A common misconception is that Override Subtotal Manually is a quick shortcut for speed. It removes Procore's built-in math check instead, so a typo in the dollar field ships with nothing to flag it as wrong. Save that override for a true lump-sum allowance, like a $5,000 owner's contingency line, where there is no unit quantity to multiply from in the first place.

The redesigned interface some Procore accounts now see keeps this same six-field flow underneath. The Create button may sit in a slightly different spot on the screen. But cost code, cost type, calculation method, quantity, unit of measure, and unit cost all work the same. If your team has people on both interface versions, tell them the logic underneath never changed, only the screen around it did.

Adding a Partial Line Item When Scope Was Missed

A partial line item exists for the moment a cost shows up that nobody planned for. A subcontractor might send a change order for demolition work that was never in scope, and the budget has no row ready to catch it. Procore calls this an unbudgeted, or missing, line item, since it carries only a budget code, with zero dollars, until someone later gives it a real value.

Creating one only needs Standard-level Budget tool access, the same baseline needed for a full manual entry. You can add a partial line item whether the project's budget is locked or open, which matters, since a locked budget otherwise blocks most other edits on the page. The steps mirror the full manual path closely. Open the Budget tool, click Create, pick the budget code parts that match the surprise cost, and save with no quantity or dollar figure yet.

Once the real cost is clear, usually from an invoice or a priced change order, someone goes back and edits that same row to add the quantity and unit cost. At that point, it acts exactly like a full line item planned from day one. The only difference is timing, since the code came first and the number came later.

The mistake teams make here is treating a partial line item as a paperwork step instead of a real check. Skipping it, and letting the cost post against a mismatched line item, hides the unplanned spend inside a code that still looks fine on a report. A project manager scanning cost-code variance never sees the real gap until the job is much further along, and by then, the fix means untangling months of mixed numbers.

Companies running an ERP link should also check that the partial line item exports right before the next sync runs. An unpriced row can act differently across systems, and some ERP links expect a dollar value before they pull a line item across at all. Check that behavior once with your link owner, rather than finding out during a live sync.

Sending Budget Codes From an Estimate Into the Budget

If your project began in Procore's Estimating tool, you do not have to re-key a single line item by hand. Budget codes set at the estimate level, on single items, assemblies, or groups, carry straight into the project's budget once the estimate is sent over. Procore then builds one line item for every distinct budget code it finds in that estimate.

How detailed your estimate is directly controls how many line items land in the final budget. Rolling every item in a group into one shared code produces a single, bigger line item once it reaches the budget. Giving different cost codes to items in that same group instead produces several smaller line items, split to match how the estimate was built.

Picture an assembly with twelve framing items inside it. Send that whole assembly over with one shared code, and the budget gets one combined line item worth the assembly's full price. Split the same assembly into labor and material cost types first, and the budget instead gets two separate line items, each carrying its own share.

An estimator who wants labor and material tracked apart for later cost review has to set that split at the estimate stage. Procore will not split a combined line item after the fact, once it already sits in the budget. This is where the biggest wrong idea shows up: teams often think they can split budget detail later. In practice, that means editing the original estimate and sending it again, not simply relabeling a row that already exists.

Getting this choice right the first time avoids reworking an estimate mid-project. Reworking it risks leaving commitments or actual costs unmatched against the old, bigger line item structure. If your estimate is genuinely rough, keep it broad at first. Then use partial or manual line items to add real detail once invoices and subcontracts show where the money lands.

Worked Example: Calculating a Line Item's Original Budget

Say a general contractor is budgeting the concrete slab for a small commercial build. The team wants Procore to add up the dollar figure instead of typing it in by hand. The cost code chosen is 03 30 00, Cast-in-Place Concrete, paired with the cost type Labor, since this line only covers crew time, not the material.

The project's estimator measured 480 square feet of slab, and agreed on a subcontractor labor rate of $14.75 per square foot. Those two numbers, quantity and unit cost, are exactly what Procore needs to calculate the line item on its own. Neither figure alone tells the full story, but the pair together sets the whole line item's value.

With Calculate Subtotal Automatically picked, Procore multiplies 480 by $14.75 and posts an Original Budget of $7,080, with no manual math needed. If the crew's real cost later lands at $15.50 per square foot instead, that $7,080 line item stays fixed as the approved baseline. The higher real cost then shows up as a variance the project team has to explain, rather than a number that quietly overwrites the original plan.

Now compare that to a lump-sum case. Say the same project also needs a $5,000 owner's contingency line, with no unit quantity behind it at all. Here, Override Subtotal Manually is the right choice, since there is nothing to multiply, and typing $5,000 straight in is both faster and correct. Using Override on the concrete line instead, by typing $7,080 with no math behind it, would have hidden a mis-typed digit that the calculated version would have caught.

That single difference is why the calculation method matters as much as the numbers themselves. Before you save any line item, glance at which option is selected, not only the dollar amount on screen. A quick second look catches the mistake before it becomes a permanent part of the budget.

Which Situation Applies to You?

Setting up a brand-new project's budget

If you are standing up a project with no budget yet, bulk import or an estimate push is almost always faster and cleaner than manual entry. Build a clean spreadsheet with every cost code, cost type, and starting dollar figure, then run Import a Budget instead of building rows one at a time. Typing a few hundred rows by hand invites the exact typing mistakes a clean import skips entirely.

This path also forces you to lock in your company's default WBS before the load happens. That one check catches a structure mistake before hundreds of line items make it bigger across the whole project. A five-minute review of your cost code list before importing saves a much longer cleanup later, once commitments and real costs already point at the wrong rows.

Catching a gap mid-project

Say you are a site-level project manager who has found a change order with no matching budget line. A partial line item is the right tool here, not a manual full entry. It flags the cost as truly unplanned, instead of quietly folding it into an existing row that was never meant to carry it. That split keeps your variance reports honest for whoever reviews cost codes above you later.

Check that your Standard-level Budget access covers this action before the change order's deadline passes. Creating the partial line item takes under a minute, and it costs nothing to do it early, even before you know the final dollar amount. Waiting until the price is set only delays the moment the gap becomes visible to your team.

Working inside an ERP-integrated company

If your company links Procore's Budget tool to an outside ERP system, check that link's export rules before you add anything by hand. Some ERP links expect line items built to a specific format, and a mismatch only shows up once the next sync runs and something fails to cross over cleanly. A quick check first is far cheaper than a failed sync found days later.

A line item added correctly inside Procore can still fail to export if its budget code does not match what the ERP side expects. Talk with whoever manages that link before running a large import, especially one that adds dozens of new codes at once. That one short talk stops a much longer troubleshooting session later.

Lessons From Three Common Budget Setups

The estimator who rolled everything into one code

Dana, a preconstruction estimator, built a whole drywall package under one combined budget code to save setup time. She planned to split labor and material apart later, once the project moved further along. Once the estimate pushed over to the budget, Procore built exactly one line item for the whole package, carrying one combined dollar figure.

By the time real invoices started arriving, there was no clean method to see labor cost apart from material cost inside that one row. Splitting it meant editing the original estimate and sending it over again, not simply relabeling the row that already existed. The lesson is simple: pick your reporting detail before the estimate is sent, not after, since Procore mirrors whatever split existed at that exact moment.

The admin who missed the granular permission

Marcus had Standard-level Budget access through a company permission template, so he assumed he could enter original budget amounts freely on any new row. Every line item he made instead saved with a zero dollar value, since his template never turned on the Modify Original Budget Amount setting under that Standard tier. He noticed the pattern only when a weekly cost report showed a budget total far lower than it should have been.

The fix took five minutes once his company's Procore admin turned on the missing setting for his template. By then, though, the project had already run two weeks with a budget that looked complete but was not. Nothing on the screen warned Marcus that his dollar values were quietly missing. That gap is exactly why this one setting deserves a check before any bulk entry session starts.

The PM who let an unbudgeted change order hide

Priya's team logged a $22,000 change order against the closest matching line item, instead of making a partial line item first, since it felt faster in the moment. Her monthly cost report then showed that cost code running fine on the surface, while it quietly carried scope it was never meant to hold. It took a full budget review, weeks later, to trace where the real cost had come from.

Making the partial line item first, even with zero dollars attached at that point, would have flagged the gap the same day it appeared. Instead, the mismatch sat hidden inside a line item that looked fine on every routine report her team ran. The lesson matches Marcus's case closely: one small setup step, skipped once, turns into a much bigger cleanup problem down the road.

How Line Items Connect to Commitments, Change Orders, and ERP Exports

A budget line item is not the end of the story inside Procore. It is the anchor that commitments, change orders, and direct costs all point back to once work starts. Once a subcontract or purchase order is made in Procore's Commitments tool, it draws against one specific line item's cost code. Every change order against that commitment then flows back into the same line item's committed and revised-budget columns.

This is why the cost code you pick at line-item creation ripples through every money tool on the project after that. A wrong pick at setup does not stay boxed inside the budget screen alone. It follows the money through commitments, change orders, and direct cost entries for the whole life of the job.

For companies running an ERP system alongside Procore, every line item added by hand or through a partial entry is a candidate for export the next time that sync runs. Export rules differ by which ERP link your company uses, so a setup that works fine for one company can act differently for another. Smaller companies often link Procore to plain accounting software instead of a full ERP. That setup faces a related but separate question, since QuickBooks integration runs through its own mapping rules.

The current state of this link, as of 2026, still needs a person to map Procore's cost codes to the other system's chart of accounts once, before line items export smoothly. Newer accounts on Procore's redesigned interface see the same budget code logic as the classic Budget tool underneath. Switching interface versions does not change how commitments or ERP exports read a line item. If you are still deciding whether the platform fits your company at all, how Procore's tools fit together is worth reading before you spend time building out a detailed WBS.

Mistakes to Avoid

• Using the same cost code twice with different sub jobs by accident. This creates duplicate tracking that inflates reported spend when reports roll up without sub job filters.
• Overriding the subtotal instead of calculating it. A typo in a manually entered dollar figure has no unit-quantity check to catch it, so errors ship silently.
• Skipping partial line items for unbudgeted costs. The cost still gets recorded somewhere, but it hides inside a code that no longer reflects reality.
• Assuming Standard permissions include dollar-value entry. Without the granular Modify Original Budget Amount setting, line items save with no value and look complete.
• Setting estimate detail too coarse for later reporting needs. Re-splitting a combined budget code after the estimate is sent means editing and resending the original estimate.
• Forgetting to check ERP export rules before a bulk import. A large batch of new line items can desync an integration if the codes do not match the ERP's expectations.
• Building a project-specific WBS that quietly drifts from the company default. This makes cross-project cost comparison unreliable for anyone reviewing more than one job at a time.
• Locking the budget before confirming every planned line item exists. A locked budget still allows partial line items, but full manual entries and edits become harder to add cleanly afterward.

Do's and Don'ts

Do

• Confirm your permission level, including the granular budget-amount setting, before you start entering line items.
• Use bulk import for any project where more than a handful of line items need to exist at once.
• Create a partial line item the moment an unbudgeted cost appears, even before you know its dollar value.
• Match your estimate's budget code detail to how granular you need your later cost reports to be.
• Confirm your company's default WBS before building a project-specific one that departs from it.

Don't

• Don't override a calculated subtotal unless the line item genuinely has no unit quantity to calculate from.
• Don't assume two similar-sounding cost codes are interchangeable; each one tracks separately in every report.
• Don't wait until a change order posts to decide whether it needed its own budget line item.
• Don't bulk-import into a project without checking whether an ERP integration expects specific code formatting first.
• Don't treat the redesigned product-manual interface as a different tool; the underlying budget code logic is the same one described here.

Pros and Cons of Procore's Line-Item Budget Structure

Pros

• Granular cost tracking by cost code, cost type, and sub job makes labor-versus-material reporting accurate.
• Partial line items give teams a clean method to flag unbudgeted costs instead of hiding them.
• Bulk import and estimate pushes make large or repeat project setups fast compared with manual entry.
• The automatic subtotal calculation catches obvious data-entry errors that a manual override would not.
• Commitments and change orders tie directly to the same line items, keeping the financial picture connected end to end.

Cons

• The unique budget code rule means you cannot quickly duplicate a line item without changing at least one segment.
• Re-splitting granularity after an estimate is sent requires editing and resending the estimate rather than a simple in-budget fix.
• Granular permissions are easy to misconfigure, letting Standard users create line items with no dollar value by mistake.
• ERP export behavior varies by connector, so a line item that syncs cleanly in one setup may need extra mapping in another.
• Two interface versions currently coexist, which can confuse a team where some members see the classic tool and others see the newer one.

You may still be weighing whether the platform is worth adopting company-wide. A broader look at whether Procore is worth it covers that call beyond the Budget tool alone. It walks through cost, setup effort, and the features teams lean on most once they are past the first setup. The Budget tool is usually one small piece of that bigger decision.

What to Do Next

1. Confirm your Budget tool permission level, and check whether the granular Modify Original Budget Amount setting is enabled.
2. Decide whether this project needs manual entry, partial line items, or a bulk import based on how many rows you are adding.
3. Verify your company's default Work Breakdown Structure before creating a project-specific one.
4. If costs are coming from an estimate, confirm the budget code detail matches your reporting needs before sending it.
5. If your company runs an ERP or accounting integration, check its export mapping rules before a large bulk import.
6. Bring in your Procore administrator or controller if permissions, integrations, or WBS defaults need company-level changes.

Frequently Asked Questions

Can you edit a budget line item after it is created?

Yes. You can edit quantity, unit cost, or the calculation method on an existing line item. This works as long as your permission level allows editing the original budget amount, and the budget is not locked against that type of change.

What happens if you enter the wrong cost code on a line item?

It sends spend to the wrong place. Commitments and actual costs recorded against the line item follow whichever code you picked, so reports split by cost type or cost code stay wrong until someone fixes the entry.

Do you need Admin access to add a new line item?

No. Standard-level Budget tool permissions are enough to create a new line item. Editing the original budget amount needs either Admin access, or a Standard template with the granular budget-amount permission turned on.

Can a locked budget still accept new line items?

It depends on the type. A locked budget still accepts partial line items, but most full manual additions and edits become restricted once the project budget is locked.

How many segments can a Procore budget code include?

Two required, one optional. Every budget code always includes a cost code and a cost type, plus an optional sub job segment for companies tracking costs by area, building, or phase.

Does importing a budget overwrite existing line items?

Not by default. Import a Budget is built to add new rows from a spreadsheet. Review the import mapping carefully before running it on a budget that already has line items you want to keep.

Can two line items share the same cost code?

Only if another segment differs. Two rows may share a cost code as long as the cost type or sub job is different, since the full mix is what Procore requires to stay unique.

What is the difference between a full line item and a partial one?

A partial line item has no dollar value yet. It carries only the budget code segments, used to flag an unplanned cost. A full line item, by contrast, includes a calculated or manually entered Original Budget amount.

Does sending an estimate to the budget always create separate line items per trade?

No, it depends on the estimate's detail. Procore creates one line item per unique budget code in the estimate. Items rolled into one shared code produce a single combined line item instead of several.

Can you tell whether a company is on the classic or redesigned Procore interface?

Check the web address, or ask your admin. The redesigned interface and the classic Budget tool share the same underlying budget code logic, so the click path differs slightly, but line item behavior stays the same.

Why would a line item save with a zero dollar value?

A missing granular permission is the top cause. Standard-level access assigned through a permission template needs the Modify Original Budget Amount setting turned on. Otherwise, new line items save with no value even when the code and quantity are correct.