Enterprise finance and operations agents serve as core business functions for your customers including billing, invoicing, reconciliation. But the finance team needs to track the whole business across accounting, sales, and inventory. Your customers need your agent to stay in sync with their ERP as their internal source of truth, which may already be wired to customer-specific workflows you can’t afford to change.
The first ERP everyone hits: NetSuite. In a 2026 CFO technology survey of 1,364 finance leaders, NetSuite held 58–67% market share among companies with $50–$500M in revenue. But integrating is rarely as simple as calling a standard REST endpoint. To reach the full surface of a customer’s account, you navigate:
- Records: transactions, accounts, custom objects, fields, and record types unique to each instance
- SuiteScript: NetSuite’s server-side scripting language
- REST Web Services: NetSuite’s REST-based web-services API
- M2M auth: machine-to-machine (OAuth 2.0) authorization required to call the account
- RESTlets: SuiteScript endpoints your customer installs to expose native, custom API access
Ampersand now handles this entire surface for you: M2M auth handshake, REST Web Services + API interfaces, and schema introspection. Finally, the hardest last mile is writing the custom APIs needed for transactions specific to a customer’s system; Ampersand creates these custom APIs for your agents with NetSuite RESTlets.
Automate business-specific transactions with custom endpoints
Writing into your customers’ NetSuite with the standard REST API is not the same as writing a business-specific transaction. NetSuite is built so each customer can architect their ERP around their specific business, and those transactions may be more custom and powerful than the public REST API.
Since Oracle can’t ship an endpoint for every possible business need, RESTlets allow building custom endpoints. These can be tailored to the fields you need to add, such as your platform’s transaction ID, or to write a customer’s data in the specific way their existing workflows rely on.
One example is writing a tax workflow into a customer's NetSuite. Your customers may not have a choice in supporting only the modern workflows; they may be required to still run NetSuite Legacy Tax, which the standard REST API may have limitations.
A SuiteScript RESTlet can enable your platform to post tax across customers using both Legacy Tax and SuiteTax, introspecting their engine and selecting the workflows the system runs.
Ampersand packages this RESTlet as a NetSuite bundle that your customer installs into their account. From there, Ampersand manages and maintains the bundle for you. Your agents can introspect the account’s schemas and call its custom endpoints to post the transactions the business runs on across sales, inventory, tax, and your custom fields.
Now your agents can act inside your customers’ ERP, reliably writing data the way each customer’s business expects.