Actions478
- Account Actions
- Account Details For Period Inquiry Actions
- Account Group Actions
- Account Summary Inquiry Actions
- Activity Actions
- Amazon Store Actions
- Appointment Actions
- Attribute Definition Actions
- Big Commerce Stores Actions
- Bill Actions
- Budget Actions
- Business Account Actions
- Carrier Actions
- Case Actions
- Cash Sale Actions
- Cash Transaction Actions
- Change Order Actions
- Change Order Class Actions
- Check Actions
- Companies Structure Actions
- Company Financial Period Actions
- Contact Actions
- Contract Usage Actions
- Cost Code Actions
- Currency Actions
- Customer Actions
- Customer Class Actions
- Customer Location Actions
- Customer Payment Method Actions
- Customer Price Class Actions
- Deduction Benefit Code Actions
- Discount Actions
- Discount Code Actions
- Earning Type Code Actions
- Email Actions
- Email Processing Actions
- Employee Actions
- Employee Payroll Class Actions
- Employee Payroll Settings Actions
- Event Actions
- Expense Claim Actions
- Expense Receipt Actions
- External Commitment Actions
- Financial Period Actions
- Financial Year Actions
- F O B Point Actions
- Inventory Adjustment Actions
- Inventory Allocation Inquiry Actions
- Inventory Issue Actions
- Inventory Quantity Available Actions
- Inventory Receipt Actions
- Inventory Summary Inquiry Actions
- Invoice Actions
- Item Class Actions
- Item Sales Category Actions
- Item Warehouse Actions
- Journal Transaction Actions
- Kit Assembly Actions
- Kit Specification Actions
- Labor Cost Rate Actions
- Lead Actions
- Ledger Actions
- Lot Serial Class Actions
- Non Stock Item Actions
- Opportunity Actions
- Pay Group Actions
- Payment Actions
- Payment Method Actions
- Pay Period Actions
- Payroll Batch Actions
- Payroll Union Local Actions
- Payroll W C C Code Actions
- Physical Inventory Count Actions
- Physical Inventory Review Actions
- Pro Forma Invoice Actions
- Project Actions
- Project Budget Actions
- Project Task Actions
- Project Template Actions
- Project Template Task Actions
- Project Transaction Actions
- P T O Bank Actions
- Purchase Order Actions
- Purchase Receipt Actions
- Sales Invoice Actions
- Sales Order Actions
- Salesperson Actions
- Sales Prices Inquiry Actions
- Sales Price Worksheet Actions
- Service Order Actions
- Shipment Actions
- Shipping Box Actions
- Shipping Term Actions
- Shipping Zones Actions
- Ship Via Actions
- Shopify Store Actions
- Stock Item Actions
- Storage Details By Location Inquiry Actions
- Storage Details Inquiry Actions
- Subaccount Actions
- Subcontract Actions
- Task Actions
- Tax Actions
- Tax Category Actions
- Tax Reporting Settings Actions
- Tax Zone Actions
- Template Items Actions
- Time Entry Actions
- Transfer Order Actions
- Union Local Actions
- Units Of Measure Actions
- Vendor Actions
- Vendor Class Actions
- Vendor Prices Inquiry Actions
- Vendor Price Worksheet Actions
- Warehouse Actions
- Work Calendar Actions
- Work Class Compensation Code Actions
- Work Location Actions
Contract Usage → Insert/Update
AI-generatedSummary
Insert or update contract usage data in the Acumatica ERP system by specifying billed and unbilled transactions along with optional contract metadata.
Inputs
- Billed Transactions — A collection of billed transaction entries each containing details such as billing date, branch, case ID, inventory ID, quantity, reference number, transaction ID, type, unit of measure, description, start date, and end date.
- Unbilled Transactions — A collection of unbilled transaction entries with similar details as billed transactions including billing date, branch, case ID, inventory ID, quantity, reference number, transaction ID, type, unit of measure, description, start date, and end date.
- Additional Fields — Optional additional fields such as Contract ID and Post Period that provide metadata about the contract usage record.
Output shape
a single object containing the response from Acumatica after the insert or update operation, likely reflecting the upserted contract usage record or an operation status message
The output structure depends on the Acumatica API response to the upsert operation for Contract Usage and may vary; errors or failure details are returned in the standard node error handling mechanism.
Examples
Example 1: Create a new contract usage record with several billed and unbilled transactions specified, providing all necessary transaction details.
Input arrays for Billed Transactions and Unbilled Transactions populated with transaction details such as dates, IDs, quantities, types, and descriptions, and optionally include Contract ID in Additional Fields.