How the As Charged Revenue Rule Works
In a charge-based project, NetSuite creates charges from qualifying project activity according to charge rules. When the As Charged revenue rule is used, the amount of revenue recognized for a period is driven by those generated charges. As new charges are created, the related project revenue can be recognized according to the configured accounting setup.
CRM ERP Integration is relevant when project contracts, customer terms, pricing, or opportunity information originates outside NetSuite because consistent commercial data helps ensure project charges and downstream revenue accounting reflect the agreed customer arrangement.
The Hyperbots Platform illustrates how finance AI agents can combine precise document processing with ERP integration for connected accounting activities. The Best CRM for Government Contractors: 2026 Comparison Guide provides broader context for AI architecture and technology-led finance transformation linking customer contracts with downstream project and finance operations.
Charge Types That Can Drive Revenue
The exact project setup determines which activities generate charges, but common charge-based inputs include:
- Time charges: Billable employee or resource time recorded against project tasks.
- Expense charges: Reimbursable or billable project costs that create customer charges.
- Milestone charges: Amounts generated when defined project milestones are reached.
- Fixed charges: Scheduled or rule-based amounts associated with project delivery.
- Other project charges: Additional charge types defined through the project's billing configuration.
Because the resulting revenue affects accounting operations, controls, auditability, and the general ledger, Optimizing COA Revenue Heads for Any Industry is relevant when finance teams design project revenue accounts and reporting structures that align with accounting standards.
Recognition Example
Assume a consulting project generates $18,000 of billable time charges and $4,000 of reimbursable expense charges during March. If those qualifying charges drive recognition under the As Charged rule, the project-related revenue for the period would be based on the total eligible charge activity: $18,000 + $4,000 = $22,000.
If April generates only $12,500 of qualifying charges, recognized revenue for that period would correspondingly reflect the lower charge activity. This means revenue patterns can vary between periods as project work, milestones, or billable expenses change.
Relationship With Billing and Accounts Receivable
The As Charged revenue rule determines how project revenue follows charge activity, while billing and accounts receivable manage customer invoices and open balances. AR Automation Software can automate manual collection follow-ups and payment-to-invoice matching to reduce DSO by 40% and reconciliation cost by 80%, while collections can automate prioritized follow-ups, promises to pay, and dunning with ERP write-back to accelerate cash collection.
Once customers pay project invoices, cash application can match bank files and remittances to invoices, post receipts into the ERP, and route exceptions so unapplied balances are cleared promptly. An Accounts Receivable Cash Application Workflow describes how those receipts move through identification, matching, application, posting, and exception resolution.
Cash Application Automation applies automated matching and posting capabilities to these activities. When finance teams are matching customer payments, interpreting remittances, resolving deductions or unapplied cash, and posting receipts, How Hyperbots AI Agents 10x NetSuite Finance Operations provides relevant context for connected NetSuite finance operations.
Multi-Entity and Financial Reporting Considerations
Organizations delivering projects through multiple subsidiaries should align charge rules, projects, accounting books, and revenue accounts with the correct entity. Multi Entity Support For Sales Tax Verification illustrates the broader value of centralized visibility when accounting actions span several entities or ERP environments and require consistent financial control.
The rule should also be distinguished from treasury decisions. Supplier approvals, payment methods, discounts, fraud controls, and payment timing influence cash outflows and cash flow, whereas the As Charged revenue rule determines how charge-generating project activity translates into recognized customer revenue.
Best Practices
Finance teams should validate that charge rules accurately reflect contract terms before projects begin and confirm which charge types are intended to drive revenue. Time entry, expense treatment, milestone configuration, and fixed-charge schedules should be tested with representative projects so the recognition result matches the accounting policy.
Organizations should also reconcile generated charges to recognized revenue during close, investigate unusual period-to-period changes, and maintain traceability from project activity through charge creation and general ledger posting. Clear ownership of project and accounting configurations helps ensure recognized revenue remains aligned with actual chargeable activity.
Summary
NetSuite As Charged Revenue Rule recognizes project revenue based on eligible charges generated from project activity. Time, expenses, milestones, and other configured charges can drive the amount recognized in each accounting period, allowing revenue to follow actual billable project activity. Proper configuration supports accurate project reporting, clear audit trails, controlled accounting, and reliable financial statements.