Actions981
- Account Actions
- Accounting Period Actions
- Adv Intercompany Journal Entry Actions
- Assembly Build Actions
- Assembly Item Actions
- Assembly Unbuild Actions
- Billing Account Actions
- Billing Revenue Event Actions
- Billing Schedule Actions
- Bin Actions
- Bin Transfer Actions
- Blanket Purchase Order Actions
- Bom Actions
- Bom Revision Actions
- Calendar Event Actions
- Campaign Actions
- Campaign Response Actions
- Cash Refund Actions
- Cash Sale Actions
- Charge Actions
- Check Actions
- Classification Actions
- Commerce Category Actions
- Competitor Actions
- Consolidated Exchange Rate Actions
- Contact Actions
- Contact Category Actions
- Contact Role Actions
- Cost Category Actions
- Coupon Code Actions
- Credit Card Charge Actions
- Credit Card Refund Actions
- Credit Memo Actions
- Currency Actions
- Currency Rate Actions
- Customer Actions
- Customer Category Actions
- Customer Deposit Actions
- Customer Message Actions
- Customer Payment Actions
- Customer Refund Actions
- Customer Status Actions
- Customer Subsidiary Relationship Actions
- [Custom Record] Actions
- Department Actions
- Deposit Actions
- Deposit Application Actions
- Description Item Actions
- Discount Item Actions
- Download Item Actions
- Email Template Actions
- Employee Actions
- Estimate Actions
- Expense Category Actions
- Expense Report Actions
- Fair Value Price Actions
- Fulfillment Request Actions
- Gift Certificate Item Actions
- Inbound Shipment Actions
- Intercompany Journal Entry Actions
- Intercompany Transfer Order Actions
- Inventory Adjustment Actions
- Inventory Cost Revaluation Actions
- Inventory Count Actions
- Inventory Item Actions
- Inventory Number Actions
- Inventory Transfer Actions
- Invoice Actions
- Issue Actions
- Item Fulfillment Actions
- Item Group Actions
- Item Receipt Actions
- Item Revision Actions
- Job Actions
- Job Status Actions
- Job Type Actions
- Journal Entry Actions
- Kit Item Actions
- Location Actions
- Manufacturing Cost Template Actions
- Manufacturing Operation Task Actions
- Manufacturing Routing Actions
- Markup Item Actions
- Merchandise Hierarchy Level Actions
- Merchandise Hierarchy Node Actions
- Merchandise Hierarchy Version Actions
- Message Actions
- Nexus Actions
- Non Inventory Purchase Item Actions
- Non Inventory Resale Item Actions
- Non Inventory Sale Item Actions
- Note Type Actions
- Opportunity Actions
- Other Charge Purchase Item Actions
- Other Charge Resale Item Actions
- Other Charge Sale Item Actions
- Other Name Actions
- Other Name Category Actions
- Partner Actions
- Paycheck Actions
- Payment Item Actions
- Payment Method Actions
- Phone Call Actions
- Price Book Actions
- Price Level Actions
- Price Plan Actions
- Pricing Group Actions
- Project Task Actions
- Promotion Code Actions
- Purchase Contract Actions
- Purchase Order Actions
- Purchase Requisition Actions
- Resource Group Actions
- Return Authorization Actions
- Rev Rec Schedule Actions
- Rev Rec Template Actions
- Sales Order Actions
- Sales Role Actions
- Sales Tax Item Actions
- Service Purchase Item Actions
- Service Resale Item Actions
- Service Sale Item Actions
- Ship Item Actions
- Statistical Journal Entry Actions
- Subscription Actions
- Subscription Change Order Actions
- Subscription Line Actions
- Subscription Plan Actions
- Subscription Term Actions
- Subsidiary Actions
- Subtotal Item Actions
- [SuiteQL] Actions
- Support Case Actions
- Task Actions
- Tax Type Actions
- Term Actions
- Time Bill Actions
- Time Sheet Actions
- Topic Actions
- Transfer Order Actions
- Units Type Actions
- Usage Actions
- Vendor Actions
- Vendor Bill Actions
- Vendor Category Actions
- Vendor Credit Actions
- Vendor Payment Actions
- Vendor Prepayment Actions
- Vendor Prepayment Application Actions
- Vendor Return Authorization Actions
- Vendor Subsidiary Relationship Actions
- Web Site Actions
- Work Order Actions
- Work Order Close Actions
- Work Order Completion Actions
- Work Order Issue Actions
Billing Revenue Event → Insert or update record
AI-generatedSummary
Inserts or updates a NetSuite Billing Revenue Event record identified by the required 'Id' parameter using a PUT request to /billingRevenueEvent/{id}. The operation allows setting standard fields (amount, date, event purpose/type, quantity, etc.), custom fields, and optional controls for replace behavior, idempotency, asynchronous execution, and property validation. When debug mode is enabled, the full request and response details are included in the output.
Inputs
- Id (required) — External identifier of the billing revenue event to insert or update. Used as the {id} path parameter.
- Amount (Transaction Currency) — Total revenue amount included in this revenue recognition plan.
- Cumulative Percent Complete — Enter a value when the Amount Source for the associated revenue recognition rule is Event‑Percent Complete.
- Custom Form — Select a custom form for the record.
- Date — Date for the revenue recognition event.
- Event Purpose — Purpose of the event (e.g., FORECAST, ACTUAL).
- Event Type — Type of the event.
- External ID — External identifier for the record.
- Internal ID — Internal NetSuite identifier for the record.
- Quantity — Quantity when the Amount Source is Event‑Percent based on quantity.
- Transaction Line — Select a transaction line as the sales contract source.
- Replace — Comma‑delimited list of sublists whose lines should be replaced.
- Replace Selected Fields — If true, all fields to be deleted in the update must be included in the 'replace' query parameter.
- Prefer — Set to 'respond-async' to execute the request asynchronously.
- X-NetSuite-Idempotency-Key — User‑defined unique idempotency key for asynchronous requests (UUID format).
- X-NetSuite-PropertyNameValidation — Strictness of property name validation.
- X-NetSuite-PropertyValueValidation — Strictness of property value validation.
- Custom Fields — Collection of custom fields to set on the record. Each field requires a Field Name (selected via loadOptions), Field Type, and a Value matching the type.
Output shape
object
Returns the NetSuite API response body for the inserted/updated billing revenue event. If debug mode is true, the output also includes the full request and response details.
Examples
Example 1: Update an existing billing revenue event
Set Id to the external ID of the event, provide Amount, Date, Event Purpose, and any custom fields, then execute.