Last updated: October 8, 2026

NetSuite Project Accounting · Contract seats

NetSuite Project Accounting and SuiteProjects Implementation Staffing

Contract functional leads and SuiteScript developers who stand up job costing, project budgets and a project P&L you can read before the month closes.

One charge, one job

Cost posted
Feb 14
Billed
Apr 1
Revenue recognized
May 31
In a spreadsheet
one date
Project accountant and a site superintendent reading a job cost summary on a laptop inside a half-finished retail store

Your finished jobs made money. Probably. You find out in six weeks.

NetSuite project accounting staffing puts a contract functional lead and a SuiteScript developer on your rollout to build job costing, project budgets and project P&L reporting. KORE1 places both, with an average IT fill of 17 days.

Last updated: October 8, 2026

Here’s the part nobody warns you about. One project charge carries three separate dates in NetSuite, and they rarely land in the same month. A cost posts when a timesheet or a vendor bill hits. Billing happens when the charge rule says. Revenue recognizes when the project revenue rule says, which, on a fixed-bid job running a percent-complete rule off task duration, can be two periods behind the invoice and three behind the cost.

A spreadsheet can’t hold three dates for one number, so somebody picks one. That’s the whole reason month-end profitability takes weeks and still gets argued about.

This desk
Contract NetSuite project accounting functional leads, SuiteScript developers and project-costing analysts for Projects, Charge-Based Billing and project revenue builds.
Routed elsewhere
A full first-time go-live goes to NetSuite implementation consultants, reporting and dashboard work to NetSuite financial reporting consultants, and daily upkeep to NetSuite administrator staffing.

This desk sits inside KORE1’s NetSuite consultant staffing practice, part of our wider IT staffing services. Across every KORE1 desk, 92% retention at twelve months is the number we get measured on.

Why the close is slow

The Same Charge, Three Dates

One retail build-out, six charges, six periods. Each row shows the same amount three times, on the period it posts, the period it bills and the period it recognizes. The run between the first mark and the last is the part a spreadsheet has to throw away.

Period register

Illustrative · one job, amounts invented for the example

  1. Crew time, week one 18,400 CostJan 9 BilledJan 31 RevenueJan 31 same period
  2. Fixture package, purchased 52,750 CostJan 22 BilledFeb 28 RevenueMar 31 two periods
  3. Electrical subcontract 31,200 CostFeb 14 BilledApr 1 RevenueMay 31 three periods
  4. Change order, exterior signage 9,860 CostFeb 26 BilledApr 15 RevenueApr 30 two periods
  5. Punch list labor 4,120 CostApr 18 BilledMay 15 RevenueMay 31 one period
  6. Retainage release 13,540 CostFeb 14 BilledJun 10 RevenueJun 30 four periods
Cost posted, Feb
54,260
Billed, Feb
52,750
Recognized, Feb
0
What one date would have shown for Feb
52,750

Three totals for one month, and none of them is wrong. Solid marks a cost date, dotted a billing date, double a revenue date. The underline carries the meaning, not the color.

Row three starts the arguments. February carries the electrical cost, April carries the invoice because the progress schedule says so, and May carries the revenue because that is when the project crossed its completion threshold, which means the same $31,200 is a cost, a receivable and a revenue entry in three different months without anybody doing anything wrong. Ask three people what February’s margin was. You get three honest answers.

NetSuite’s answer is to stop making anyone choose. Oracle’s documentation on project revenue recognition is blunt about the price of admission. Project Management, Charge-Based Billing and Advanced Revenue Management are all required, and it won’t run at all if Advanced Revenue Management is left in configuration mode. Three features, one dependency chain, and plenty of accounts have two of the three switched on.

That’s a staffing problem before it’s a software problem. Somebody decides, charge rule by charge rule, which clock governs. Then somebody builds it. Those are rarely the same person.

Two NetSuite consultants comparing two project setup documents side by side on a meeting room table
First fork in the road

SuiteProjects Inside NetSuite, or SuiteProjects Pro

Two products share most of a name and they are not the same purchase. The project features inside NetSuite ERP give you projects, project tasks, budgets, charge rules and project revenue in the same ledger as everything else. SuiteProjects Pro is the separate professional services platform, the one that spent years as OpenAir before Oracle renamed it in 2025. Its documentation lives in its own set, which tells you most of what you need to know about how separate it is.

Colin Boothe, CIO at Foretopia, eight years of NetSuite work

Pick the one your controller will actually close the month in.

The rough cut we use. If the project is how you deliver a product, like a build-out, an install or a job, stay inside NetSuite. If selling people’s time by the hour is the business, and you need utilization, resource forecasting and timesheet approvals as first-class features, Pro earns its line item.

Where it gets expensive is picking Pro and then wanting one ledger anyway, because now you own an integration between two Oracle products and somebody has to maintain it through two release cycles a year. We’ve staffed that repair more than once. It is not the fun kind of project.

Multi-subsidiary adds another wrinkle worth settling early, and our NetSuite OneWorld consolidation desk covers that side.

NetSuite functional consultant mapping charge rules and billing milestones on a whiteboard while a project controller takes notes
Where the hours go

Charge Rules First, Then Revenue Rules

Billing and revenue are two decisions, made in that order, and teams collapse them constantly. NetSuite documents four ways to bill a project, and they behave differently at close.

Time and materials
Bill actual resource time and expense as it posts
Fixed bid, interval
Fixed amounts on a set schedule, the simplest of the four
Fixed bid, milestone
Bill when a preset goal or percent of work completed is hit
Charge based
Charge rules plus billing rate cards, for anything the first three can’t express

Only then do you pick how revenue behaves, and Oracle gives you three project revenue rules. As charged recognizes from the actual charge dates and amounts. Percent complete recognizes at the rate the project progresses, so ten percent complete in January recognizes ten percent of charges, and fifteen percent by February adds the next five. Fixed amount recognizes on a schedule you calculate yourself, which is the honest option when the math genuinely lives outside NetSuite.

Percent complete is where the rework lives. By default it runs off task duration. Duration only stands in for progress while somebody maintains the task plan, and six weeks after kickoff nobody is maintaining the task plan. The revenue comes out precise to the cent and wrong, and the first anyone hears of it is a restatement.

We screen for the audit, not the setup. Ticking the box marked percent complete takes an afternoon. Ask a candidate instead how they would prove a task plan is current before letting it drive revenue, and you learn everything in about four minutes.

3

features NetSuite requires before project revenue recognition runs at all

4

documented ways to bill a NetSuite project, each closing differently

17 days

KORE1 average time to fill an IT role

92%

KORE1 twelve-month retention, all desks combined

Sources: Oracle NetSuite Help Center, Project Revenue Recognition and Project Billing. KORE1 placement data.

One we ran

A Retail Construction P&L That Stopped Being a Reconstruction

Controller reviewing project profitability by job on a dashboard during month end close

Accuserve builds and remodels retail sites. Working out whether one had made money meant archaeology. Labor out of one place, vendor bills out of another, invoices out of a third, reconciled by hand into a figure that landed weeks downstream of the decision it should have informed. By then the crew was two stores away.

The fix wasn’t a report. Job costing moved into the system already holding the costs. Once it did, those three dates stopped being a monthly reconciliation and turned into fields that post themselves. Nobody minds it now.

The same shape turns up across services firms and job shops, and Colin lays out the wider version in his NetSuite optimization playbook. Builds like this are rarely exotic. The decisions behind them are slow. Hiring somebody who has already made those decisions once is the entire shortcut.

Engagement detail published with the client’s agreement.

How it runs

Five Steps, and Only One of Them Is Configuration

The order matters more than the tooling. Every step below has to be settled before the next one can be built, which is why a build stalls at step two far more often than at step four.

  1. Write down how you actually billEvery habit, every exception, every handshake deal a project manager honors because it predates them. This is the long step and it is not a systems task.
  2. Settle the project and task structureWhat a project is, what a task is, how deep the tree goes. Get this wrong and percent complete is meaningless for the next three years.
  3. Build charge rules and rate cardsPick one of the four billing types per project type, then rate cards for the charge-based ones.
  4. Pick a revenue rule per charge ruleAs charged, percent complete or fixed amount. This is where the third date gets decided and where finance has to sign.
  5. Close a month in parallelRun the old way and the new way over the same period and reconcile the gap before anybody switches off the spreadsheet.

Step five is the one teams try to skip, and skipping it is how a controller ends up defending a number they cannot reproduce. One parallel close is cheap. Explaining a restatement to an audit committee is not.

Step one is where the hours actually go. A services firm with four project types and a decade of exceptions can spend three weeks just getting the exceptions written down, and about a third of them turn out to be things nobody has honored since 2021. Killing those is part of the work.

What it costs

Contract Rate Bands for NetSuite Project Accounting Seats

Hourly bill rates on a KORE1 W-2, United States, 2026. These sit on the same NetSuite contractor ladder our other desks publish, roughly $90 to $185 an hour depending on seat and metro.

Project accounting functional lead
$135 to $175Top of the functional band, because the seat owns revenue decisions and not just configuration
SuiteScript developer
$120 to $175Same band our developer desk places against, with project and billing experience at the upper end
Project costing analyst
$85 to $120Budgets, rate cards and task plans, the seat that keeps percent complete honest
Project accountant, NetSuite
$75 to $110Usually contract-to-hire, and usually the one who stays

For comparison, a specialist ERP consultancy bills around $215 an hour blended across delivery roles, per Foretopia’s 2026 benchmarks. That buys a bench, a methodology and somebody else’s project manager. It is the right call when you need all three and the wrong call when you need two seats for a quarter.

The honest version of the trade. Consultancies are faster to start and more expensive to keep. Contractors are slower to start and cheaper to keep, and they leave the knowledge inside your building instead of inside somebody’s deliverable template. Most mid-market project accounting builds we see want the second shape, which is why this desk exists.

Seats we fill

NetSuite Project Accounting Seats We Staff on Contract

Each card’s tag names the engagement that usually fits. A habit, not a rule.

  • Contract

    Project accounting functional lead

    Owns the charge rules, revenue rules and the project P&L design, and settles which clock governs each charge.

  • Contract

    SuiteScript developer

    Builds the costing logic, saved searches and record automation that charge rules alone can’t express.

  • Contract

    Project costing analyst

    Rebuilds budgets, rate cards and task plans so percent complete means something at close.

  • Contract-to-hire

    Project accountant, NetSuite

    Runs the close on the new design once the build team rolls off, and keeps the task plans honest.

Builds usually open with the first two seats on contract staffing terms and close with the fourth on a trial period that converts. Repairing somebody else’s project setup is fixed scope, which suits project staffing. Already stalled? That’s a rescue.

Heavier script work goes to our NetSuite developer staffing desk. If the people running the close are the gap rather than the system, that’s accounting and finance staffing instead. Budgeting first? Our implementation cost calculator gives you a range to argue with.

Questions

Common Questions

What does NetSuite project accounting actually give you?

Margin by job, while the job is still open. Cost, billing and revenue post against a project record and not only against the general ledger, which is what lets a controller read a job mid-flight rather than reconstruct it in arrears. Five moving parts hold it up. Projects, project tasks, project budgets, charge rules, project revenue rules.

Do we need SuiteProjects Pro, or is NetSuite enough?

Depends what you sell. Where projects are how a product gets delivered, a store build-out or an install or a job, stay inside NetSuite, because the costs already sit in that ledger and splitting them buys you an integration nobody wanted. SuiteProjects Pro is the separate platform Oracle renamed out of OpenAir in 2025. It earns a line item when selling time is the business itself.

Three features just to recognize project revenue. Really?

Really. Project Management, Charge-Based Billing and Advanced Revenue Management (Essentials), all three, and the whole thing stays dark while Advanced Revenue Management sits in configuration mode. Count what you own before anyone scopes the work. Two out of three is the usual finding, and the missing one is usually the expensive one.

Why does our project margin change after the month closes?

Three dates, one charge. Cost, billing and revenue can each land in a different period, so the month keeps moving as the later two show up. Nothing is broken there. What is broken, and wears the same costume, is a percent-complete rule running off a task plan that gets corrected twice a year, because every correction restates a margin somebody already reported.

How long does a project accounting build take?

A quarter, for a single-subsidiary services firm or job shop. Configuring it is quick. Deciding is not, because every charge rule is a finance and operations argument rather than a setting, and settling one means getting people who have never written their billing habits down to finally write them down. Add subsidiaries, currencies or an old revenue arrangement to unwind and a quarter stops being realistic.

Can one contractor cover the whole thing?

On a small build, sometimes. Settling which clock governs a charge and writing the script that enforces it are different skills, and the people who are genuinely good at both get hired away faster than we can present them. Waiting for that one person usually costs more than running two. Send the scope over and we’ll say which way yours leans.

Contractor or full-time hire for NetSuite project accounting?

Contract the build, hire the close. Design work wants deep project accounting judgment for a few months, then it stops wanting it. A monthly close wants an owner for as long as you keep taking on projects. Hence the split we usually place, build team on contract, project accountant on contract-to-hire.

Next build

Send Us One Finished Job

Pick one job you’ve closed out. Tell us how you worked out whether it made money, and a KORE1 recruiter will say which project accounting seats you need now and which can wait.

Staff a Project Accounting Build →