NetSuite Project Billing Methods: Fixed Bid vs T&M vs Charges

Executive Summary

NetSuite project billing methods should be selected from the engagement's promise to the customer: payment for approved effort and reimbursables, payment at recurring dates, payment after accepted deliverables, or a mixture of these triggers. The native project choices are Time and Materials, Fixed Bid, Interval, Fixed Bid, Milestone, and Charge-Based Billing. For the first three, a project billing schedule governs the associated sales transaction. For charge-based projects, rules create charges and the rule governs billing frequency; the project schedule chiefly supports the sales forecast. Oracle documents Project Management and Advanced Billing as prerequisites and documents separate charge-based requirements. ^[1] This is a configuration decision, not a prediction that one contract form will earn a higher margin. Federal contract definitions distinguish fixed price from time and materials, while a professional-services benchmark found similar average 2024 project margins for both categories. ^{[2] [3] [4]}

Time and Materials is the clean fit when approved, billable hours and allowable costs set the invoice amount. Fixed Bid, Interval fits a fixed commercial amount billed at recurring intervals, with attention to how project duration and actual time influence scheduled amounts. Fixed Bid, Milestone fits payment after specified goals or tasks are completed. Charge-Based Billing fits blended agreements because fixed-fee, time, expense, and purchase rules can create separately reviewable charges. A missing approved time entry stops time billing, whereas a missing expense rule can leave a charge-based pass-through cost out of the charge queue. A charge in Hold stays out of billing until its stage is changed.

The decision should be tested with the same underlying labor, expense, and purchase economics across four contract designs. The worked examples below use fictional values so differences in invoice timing can be separated from differences in cost. A project accountant should tie contract value or approved billable charges to invoices, pending charges, recognized revenue, and project cost. ^[5] NetSuite's project profitability configuration can include actual and committed transactions, while charge-based revenue rules and Advanced Revenue Management (ARM) govern revenue separately from invoice creation. This distinction matters at close: invoice timing may differ from revenue timing, and retainage can have its own contract-balance classification. ^{[6] [5]}

The practical control set is a contract-to-record map, time and expense approval owners, charge review, invoice approval, rate versioning, and a month-end reconciliation. ^[7] Oracle states that project time must be approved before billing and that invoice approval is a separate workflow when its SuiteApp is installed. Houseblend, as a NetSuite implementation provider, describes process design, configuration, migration, and testing as parts of an implementation; those are relevant services for translating billing policy into configured records. ^{[8] [9]} The implementation partner is a service layer, not a fifth billing method.

Introduction and Background

A professional-services contract can fix the price while allowing an invoice every month, defer payment until acceptance of a deliverable, or price most work by hours while passing through travel and subcontractor purchases. The word “project” alone does not determine the billing object. The controller first needs the contractual trigger, the unit of charge, the evidence required before invoicing, and the treatment of changes. ^[7] U.S. federal procurement rules illustrate the economic distinction: a firm-fixed-price amount does not change with the contractor's actual costs, while a time-and-materials contract pays specified hourly rates and material costs. These are definitions for federal purchasing, not rules imposed on every private services contract. ^{[2] [3]}

NetSuite's native project billing makes the commercial distinction operational. Project Management and Advanced Billing are required for project billing. A chosen project schedule can flow to the estimate or sales order, where it determines billing dates and supports forecasting. Charge-based billing adds rules that turn project activity into charges. A charge is a separate record before invoicing and does not itself post to the general ledger. ^[10] That separation creates a useful review point, but it also means that a charge count, an invoice count, and revenue recognized are different measures. Standards-based revenue recognition follows transfer of goods or services, and a filed issuer disclosure explicitly notes that invoice and revenue dates can differ. ^{[6] [5]}

This report is for chief financial officers (CFOs), controllers, services operations leaders, project accountants, and NetSuite owners designing engagements in the United States. It compares the four native methods as of September 2026, then tests an identical fictional project under each method. It also distinguishes native SuiteProjects from SuiteProjects Pro, formerly OpenAir, only where migration affects billing records. Oracle describes approved SuiteProjects Pro invoices being exported to NetSuite through a separate integration workflow. A NetSuite implementation provider such as Houseblend can help map contracts, configuration, migrations, and controls, but the commercial terms and accounting policy remain the buyer's decisions.

Time and Materials

Capabilities

NetSuite time and materials project billing follows a schedule for billing dates and uses entered, billable, approved time to determine the work that can be invoiced. Oracle says the schedule bills in arrears. The amount can move with actual effort, so a sales order may hold estimated lines until invoicing replaces them with actual billable activity. ^[11] Materials and expenses need their own correct billable source records and treatment. The contract should specify labor categories, rates, reimbursable categories, any markup, invoice cadence, and who approves work. A federal time-and-materials definition uses fixed hourly rates plus material costs and, for that procurement context, a ceiling price. A private contract can use a cap too, but the cap must be defined in the agreement and tested in configuration. ^{[3] [12]}

Adoption

There is no public NetSuite metric showing the share of customers that use this method. A broader benchmark is informative but does not measure NetSuite adoption: SPI Research's 2025 Professional Services Maturity Benchmark surveyed 403 firms in fall 2024 and reported a 34.7% 2024 mean project margin for time-and-materials work. Its fixed-price result was 34.6%. Those category averages are nearly equal and do not establish causation or a target margin for a particular firm. ^[4] A buyer should therefore choose a billing method from enforceable terms and record quality, then manage delivery margin separately.

Strengths and Limitations

The method is transparent when the customer buys measured labor and eligible cost. The invoice can be traced to time entries, expense reports, and other billable records. ^[2] The weakness is timing sensitivity: time must be entered, marked billable, and approved before it is billed. A late entry is a late invoice candidate, not proof that the work lacked economic value. Oracle also warns that billing project time through Invoice Billable Customers can create an invoice that is not linked to its originating sales order; it recommends Bill Sales Order for order-associated project billing. A weekly approval cutoff and exception list should identify unsubmitted time, nonbillable flags, and missing rates before the billing run. This control reflects the general project-management requirement to keep approved scope and changes visible. ^{[7] [13]}

Fixed Bid, Interval

Capabilities

NetSuite fixed bid project billing can use an interval schedule when the customer owes a defined amount at recurring dates. Oracle describes interval billing as arrears-only and calculates its number of cycles from project duration and recurrence. Recording project time does not change the timing, but it can affect the amount billed under this schedule, so the label “fixed bid” should not be treated as a promise that every invoice is the same. ^[14] The agreement should state whether each month has a fixed amount, whether the price is spread over the planned project duration, and how extensions change invoices. If the buyer needs a strict installment amount independent of task time or project duration, it should confirm the exact schedule configuration in user acceptance testing (UAT) before launch. The fixed-price commercial principle is that actual delivery cost does not itself reprice the contract. ^[2]

Adoption

Oracle documents this as one of its native schedule types but does not publish customer adoption by schedule. The method suits a defined scope with calendar-based payment, such as a fixed-fee engineering design delivered over several months. The billing design and the delivery budget need distinct baselines: an approved scope change may change project work, a contract amendment may change price, and a revised duration may change schedule projections. PMI recommends an approved scope baseline and coordination of authorized changes before approval. ^{[7] [13]} The distinction is important because a monthly invoice is neither a measure of work complete nor a measure of earned revenue under all accounting policies. ^[6] IFRS 15 allows performance obligations to be satisfied over time or at a point in time. ^[15]

Strengths and Limitations

An interval schedule makes invoice timing predictable, helping the finance team plan billing windows. Its control risk is that the invoice can arise even when actual labor cost is late or incomplete, so a favorable apparent project margin may reflect missing cost input. NetSuite Job Costing calculates labor cost from tracked time; the project profit and loss (P&L) view depends on enabled features and configured cost mappings. Where a contract includes a holdback, it should be represented explicitly in contract and invoice procedures. AIA's payment application separates retainage, previous payments, and the current requested payment; the accounting classification of a holdback depends on whether payment is unconditional. ^{[16] [17]} The interval schedule should not be assumed to solve retainage, change-order, or revenue-recognition treatment without a documented test.

Fixed Bid, Milestone

Capabilities

NetSuite fixed bid milestone billing ties customer billing to completed project goals rather than the quantity of time or materials consumed. A milestone can be linked to a project task; when the linked task is completed, the milestone can be marked complete, and the amount becomes available to bill. Without a linked task, a responsible user must mark the milestone complete. Oracle describes each milestone schedule as private to its project. ^[18] In contract terms, the milestone should have an acceptance criterion, authorized approver, amount or percentage, and change-control rule. AIA's G703 continuation sheet illustrates the value of dividing a contract sum into portions of work, while PMI advises approval of the scope baseline. These sources provide control context; they do not dictate a NetSuite field design. ^{[19] [7]}

Adoption

No public source found a count of NetSuite milestone projects. AIA's 2024 firm survey included more than 1,200 architecture firms and reported $143,000 average net billings per employee for 2023. That measures firm economics rather than use of milestone billing, so it belongs only as context for why billings and capacity both matter to project-based firms. ^{[20] [21]} A fixed milestone arrangement is appropriate when the customer accepts discrete deliverables. A project can incur labor cost well before its next milestone is accepted, creating a timing gap between cost, invoice eligibility, and possibly recognized revenue. Standards distinguish a conditional contract asset from an unconditional receivable. ^[17]

Strengths and Limitations

The billing event is easy to explain to a customer if completion evidence is clear. It can be harder to administer when acceptance is ambiguous, the scope changes, or the project team closes tasks before the commercial approver has accepted the deliverable. The project manager should confirm completion; the contract owner should confirm acceptance where required; finance should then review the invoice. ^[16] AIA's construction payment workflow similarly separates the application from an architect's certification, although that is an analogy rather than a universal services requirement. ^[22] The schedule itself is not a substitute for a signed change order. The Internal Revenue Service (IRS) construction guide describes change orders as written revisions that increase or decrease contract price. ^[23] NetSuite can recalculate a project plan and invoice schedule after some project, task, or time changes. ^[24] Oracle says billing schedule changes do not trigger the same recalculation. ^[25] UAT should cover both paths.

Charge-Based Billing

Capabilities

NetSuite charge-based project billing uses rules to turn activity or events into charge records. Its four documented rule types are fixed fee, time, expense, and purchase. A fixed-fee rule can respond to a date, a completed task or milestone, or project progress; time rules apply selected rates to time; expense rules use expense report receipts; purchase rules can use purchase transactions. ^[26] A charge-based project may still have a billing schedule, but Oracle says charge-rule frequency determines billing and the schedule calculates sales forecast amounts. This is the central distinction in NetSuite project billing schedule vs charge rules. ^[27]

Adoption

Oracle does not publish method-level adoption or a public price for this feature. It does specify that Project Management and Advanced Billing precede Charge-Based Billing, and that Billing Rate Cards additionally depend on Per-Employee Billing Rates. Entitlement and account setup should be checked against the buyer's current subscription and sandbox because a general product description is not a license quote. NetSuite's SuiteProjects material says it supports project budgeting and comparison of timesheet and expense actuals with project figures; that describes a reporting capability, not a measured margin improvement. ^[28]

Strengths and Limitations

Charge rules are the best native fit when one engagement combines a fixed setup fee, hourly work, reimbursable travel, and purchased services. ^[2] The tradeoff is another review layer. Oracle states a generated charge must be Ready for Billing; a Hold-stage charge does not bill. Pending charges can be reviewed and zeroed, and Ready charges can flow to a project sales order or invoice path. ^[29] A missing rule leaves eligible activity outside the intended charge flow, while a broad rule risks charges that need a write-off or hold. Rate basis also matters: a time rule using service items gets rates from service items on time entries, while a resource-rate rule ignores project-task rates for charge calculation. There is no universal precedence across all bases; the configured rule decides the path. ^[30] Project and customer currency must agree for associated transactions, and rate-card versions can take effect on future dates. Oracle's public pages do not establish that changing a card retroactively reprices already generated charges, so that behavior should be tested before a rate amendment is applied.

Feature Comparison

The NetSuite fixed bid vs time and materials choice starts with the commercial trigger and reverse-maps it into NetSuite. For NetSuite project billing setup, the owner should specify the event that makes work invoice-eligible. The distinction between NetSuite project billing rules and charges is part of that map. Table 1 records the primary object, source evidence, and approval point. The final row identifies Houseblend's implementation service role because that provider can configure the choices; it is explicitly a service, not an additional billing method. The service page describes process mapping, configuration, migration, testing, and integrations, without publishing a list price. ^{[8] [9]}

The matrix shows why the customer's promise must be written first. ^[7] A recurring date and a completed deliverable are distinct events even if both contracts have the same total fee. A blended contract can need several charge rules and a review queue. A partner can configure the process, but cannot infer an acceptance criterion or cap from a project name. The distinction parallels PMI's recommendation to define scope and coordinate approved changes. ^{[7] [13]}

The next design issue is lineage. Table 2 follows records from commercial terms into billing and margin. It is also a compact rate-card precedence matrix: the rate source is selected by the time rule's basis, not by a single global ordering.

A single source record can influence several views without being the same accounting event. ^[5] NetSuite describes a charge as a non-general-ledger record before invoicing, and its profitability reports distinguish actual from committed transactions. Thus the project accountant should not sum all forecast charges, pending charges, and invoices as if they were additive revenue. ^[5] FASB staff guidance similarly distinguishes receivables, contract assets, and contract liabilities.

Performance and Benchmarks

A billing method's operational performance is the accuracy and timing of billable events, not a software vendor's claimed margin uplift. Public sources do not isolate native NetSuite invoice-error rates or days-to-bill by billing method. The strongest directly relevant external result found is SPI Research's professional-services benchmark: its 403-firm sample reported 34.7% average time-and-materials project margin and 34.6% fixed-price project margin in 2024. The 0.1 percentage point gap is a descriptive comparison, not evidence that a billing form causes that margin. The PDF reports the prior-year averages as 33.6% and 34.0%, respectively. ^[4]

A separate Deltek 2026 architecture and engineering study drew on 896 firms and reported utilization just under 60% and operating profit of 16.7%. The sponsor, population, definitions, and level of metric differ from SPI's project-margin measure, so the numbers should not be compared as if they had the same denominator. ^{[32] [33]} AIA's 2024 firm survey, with more than 1,200 firms, reported $143,000 net billings per employee for 2023, another different numerator and population. ^{[20] [21]} These observations underscore the need to define whether a dashboard measures billed revenue, recognized revenue, project gross margin, operating profit, or capacity use. NetSuite describes its analytics as including profit margin, utilization, and budget-versus-actual views, while Oracle's advanced profitability setup controls how actual and committed items are mapped. ^{[28] [34]}

For a method-level evaluation, test observable control outcomes: the number and value of approved time entries missing from the invoice candidate, expenses without an expense rule, charges held at cutoff, milestone amounts billable before acceptance, and invoice lines without a project link. A monthly work-in-progress (WIP) review should compare revised estimated costs, approved changes, billings, and margin. CFMA explicitly includes those items in a construction WIP process, and its underbilling/overbilling discussion supports using them as exception categories. ^{[35] [36]} The numerical tolerance for each check is a policy decision; no universal NetSuite target was found.

Data Analysis and Evidence

Consider four fictional engagements with identical delivery economics: a planned $120,000 client value, 600 hours of labor at $120 internal cost per hour, $12,000 of expenses, and $6,000 of supplier cost. The planned cost is $90,000, and the illustrative gross margin is $30,000, or 25% of client value. The four designs below change only the contractual billing trigger. The examples are analytical scenarios, not observed NetSuite customer outcomes. A real project must use its approved contract, labor-cost basis, expense policy, and revenue rules. Tracked time and expense actuals should be compared with the approved project budget. ^[28]

Table 3 shows the first two fictional billing periods. All amounts are illustrative and are deliberately not market rates. For charge-based billing, the rule mix is a contract design choice; Oracle documents its available rule types and Ready-stage requirement.

The comparison isolates timing, not total economics. The T&M contract could ultimately bill more or less than the modeled $120,000 if hours or eligible costs differ, unless a contract cap changes the commercial right. The interval and milestone designs keep the fixed fee but differ in when invoice eligibility arises. The charge-based mix can also reach the same planned value, yet each rule has a separate path to a charge. In that fictional contract, costs not passed through separately are included in fixed fees. Federal procurement's ceiling-price requirement is one example of a cap, but a private cap must be interpreted from its own terms. ^[12] Oracle's charge-rule documentation says caps are unavailable for fixed-fee and expense-based rules, so a blended agreement may require additional control outside those specific rule caps. ^[37]

For NetSuite project profitability by billing method, hold the cost basis constant while testing each invoice trigger. The blank project margin bridge for any of the four designs is: approved contract value or eligible billable charges; less discounts, write-offs, and credits; less labor cost from the chosen time-cost basis; less expense and purchase cost; equals project gross profit. Divide gross profit by the selected revenue denominator for gross margin. ^[35] Keep three adjacent reconciliations: billable candidate to invoiced, invoiced to recognized revenue, and recognized revenue to contract asset or liability. ^[5] NetSuite's charge records are non-posting until invoicing, its revenue rules can recognize separately from customer billing, and a public-company filing confirms that invoice and recognition timing can differ. ^[5] FASB staff guidance treats conditional payment rights as contract assets and unconditional rights as receivables. ^[17] The bridge should be filled with the firm's own mapped accounts and transactions, not these fictional amounts. ^[35]

Implications and Future Directions

The first implementation deliverable is a signed contract-to-record map. ^[7] It should list scope, price or rate basis, invoice trigger, acceptance authority, reimbursable rules, cap, holdback, currency, subsidiary, and amendment process. A change order should modify the commercial baseline before finance changes a billing rule or schedule. The IRS's construction guide calls change orders written price revisions; PMI likewise places approved changes against a controlled baseline. ^[13] The finance team should assign owners to time approvals, expense approvals, charge review, and invoice release. Oracle notes that a project time approver does not automatically have expense-approval authority, and its invoice approval workflow requires the NetSuite Approvals Workflow SuiteApp.

A focused UAT sequence should use the same project and sales order records across methods where practicable:

• Time cutoff: Enter approved, unapproved, nonbillable, and late time; confirm which entries appear in the invoice candidate.
• Expense and purchase lineage: Enter an expense receipt and vendor bill; confirm the intended charge rule captures each and the cost is mapped once.
• Milestone evidence: Complete a linked task and an unlinked milestone; confirm completion, acceptance, and billable status occur in the intended order.
• Rate amendment: Create a future-dated rate-card version, then compare an old charge, a new charge, and their invoice lines.
• Hold and invoice approval: Leave one charge in Hold and route a draft invoice through a configured approver.
• Currency and subsidiary: Test the customer project currency and sales order invoice currency, plus OneWorld resource eligibility.
• Close tie-out: Compare project billings, pending charges, posted costs, recognized revenue, and contract balances.

A spreadsheet migration should import master records before dependent project tasks, rates, and open transactions, then reconcile opening balances and unbilled work. ^[35] Oracle documents CSV import for projects and tasks, including a required subsidiary field in OneWorld project imports. A SuiteProjects Pro migration needs separate mapping: Oracle describes it as the former OpenAir product, and its integration exports approved invoices to NetSuite but does not update already integrated invoices. ^[38] That is a workflow boundary, not evidence that one platform is generally superior. Houseblend's own implementation description includes migration, configuration, and testing, so it can serve as the implementation provider if a buyer elects outside help. ^[8] The forward-looking control opportunity is a repeatable monthly exception pack that shows missing source activity and reconciles billing with margin before the period closes. ^[28] CFMA's WIP guidance and NetSuite's project profitability configuration support that discipline. ^[35]

Frequently Asked Questions (FAQs)

Is charge-based billing the same as a project billing schedule?

No. In charge-based billing, rules create charges and determine billing frequency; the schedule on the project supports forecast amounts. A native Time and Materials or Fixed Bid schedule instead governs the associated order's billing dates. ^[27]

Does fixed bid mean project time can be ignored?

No. Time may not be the milestone trigger, but it remains a cost and progress input. Oracle specifically says interval project time can affect billed amount while not changing timing, and its labor-cost tools derive cost from tracked time.

How are pending charges approved?

Charge-based projects can default new charges to Hold, use Manage Pending Charges for review, and move eligible charges to Ready for Billing. Invoice approval is a separate optional workflow with its own installation and routing.

Which rate wins on a charge-based time line?

The rule's selected rate basis determines the path. Oracle documents service-item rates from the service item on a time entry and resource rates that do not use project-task rates for the charge. Rate cards have effective-dated versions. Verify the configured basis and amended dates in a sandbox.

Does an invoice equal project revenue or profit?

No. A charge can exist without general-ledger impact, and ARM project revenue rules can recognize independently of billing. Project P&L depends on the chosen cost and revenue mapping. Under IFRS 15, revenue reflects transfer of promised goods or services, while FASB distinguishes conditional contract assets from unconditional receivables. ^{[6] [6]}

Conclusion

The practical choice among NetSuite project billing methods is the choice of billable event. Use Time and Materials for approved measured effort and eligible costs, Fixed Bid, Interval for a fixed commercial obligation paid at recurring dates, Fixed Bid, Milestone for acceptance-linked deliverables, and Charge-Based Billing for agreements that combine dates, deliverables, time, expenses, and purchases. Oracle's documented schedules and rule types support these distinct paths.

A reliable design goes beyond the billing type field. It assigns a source record and approver to every invoice line, states how caps and change orders are handled, tests rate and currency behavior, and reconciles invoices with project cost and recognized revenue. ^[5] Project gross margin is only as useful as the time, expenses, purchases, and account mappings beneath it. The measured industry averages in this report are context, not a promise of outcome; the fictional examples are a test design, not a benchmark. The controller should leave UAT with a documented contract-to-record map and a month-end exception report that makes missing activity, held charges, and billing-versus-revenue differences visible. ^[35] At sign-off, the buyer should trace a representative invoice from contract clause through source record, approval, schedule or charge, transaction, project report, and ledger. Repeating that trace for an amendment and a missing source record makes the operating process auditable. ^[35]