[ Salesforce / Quote to cash ]

Salesforce quote to cash, finished in the ERP

When an opportunity closes or a quote is accepted, engini picks it up in real time, has an AI agent check the deal, and creates the customer, the order and, where you want it, the invoice in NetSuite, SAP S/4HANA or QuickBooks. The signed quote goes with it, and order, invoice and payment status come back to the opportunity.

SalesforceNetSuiteSAP S/4HANAQuickBooksSlack
Read the Salesforce guide →
A quote is accepted
  1. Salesforce logo
    Quote accepted, opportunity wonreal-time outbound message
  2. Agent checks the deallines, discounts, terms, bill-to
  3. NetSuite logo
    Order created in the ERPNetSuite, SAP S/4HANA or QuickBooks
  4. Signed quote attacheddownloaded from Salesforce, stored with the order
  5. Salesforce logo
    Status back on the opportunityorder no., invoice no., paid
Illustration of the flow on this page, not a product screen.
What it does
Won deals become ERP orders and invoices; status returns to Salesforce
Systems
Salesforce, NetSuite, SAP S/4HANA or QuickBooks, Slack or Teams
Built with
A workflow on a real-time Salesforce trigger, with an AI agent check
Your control
Which stages qualify, what the agent checks, which ERP fields it writes
[ 01 / The problem ]

The quote is signed. The order is typed again.

Salesforce is where the deal is shaped: the opportunity, its products, the quote the customer signs. Then the process leaves Salesforce. Someone re-keys the order into the ERP, attaches the signed PDF, raises the invoice, and later copies the invoice number back so the account team knows where things stand. Integrators such as delaware describe exactly this break between CRM and ERP.

The break is costly in small ways that add up: an order entered with the old discount, a bill-to address that was updated in Salesforce but not in the ERP, a customer who is invoiced a week late because the order sat in a queue.

Where quote to cash leaks

  • Manual order entry after every closed deal.
  • Signed quotes stored in one place and orders in another.
  • Products, prices or terms that do not exist in the ERP.
  • No invoice or payment status in Salesforce, so reps ask finance.

An agent between the CRM and the ERP

engini catches the change the moment it happens, through Salesforce’s real-time outbound messages. An AI agent step reads the opportunity, its products, the quote lines and the account, and checks them against the ERP before anything is written. A clean deal becomes a customer and an order in NetSuite, a business partner and sales order in SAP S/4HANA, or an invoice in QuickBooks. A deal with a problem becomes a note to the owner instead of a broken order.

engini downloads the signed quote from Salesforce and stores it with the order or in your document folder. On the way back, order numbers, invoice numbers and payment status are written to the opportunity or a custom object. Every engini integration runs both ways, so this is one setup.

[ 02 / How it works ]

From accepted quote to paid invoice

01 / Trigger

Real time from Salesforce

An outbound message starts the workflow when the opportunity is marked Closed Won or the quote is accepted. Record triggers checked as often as every 15 minutes work too.

02 / Check

The agent reviews the deal

An AI agent step reads the opportunity, quote lines and account, and checks items, prices and terms against the ERP. Problems go to Slack or Teams.

03 / Create

Order in your ERP

It creates or updates the customer and creates the order in NetSuite, SAP S/4HANA or QuickBooks, and stores the signed quote with it.

04 / Return

Status back to the rep

Order numbers, invoice numbers and payment status are written to the opportunity or a custom object, and the owner is told in Slack or Teams.

[ 03 / What the agent reads and writes ]

What the agent reads and writes

SystemRecordsAccess
SalesforceOpportunity, Opportunity Products, Quote, Quote Line Items, AccountRead
SalesforceSigned quote documents and attachmentsDownload
SalesforceERP order, invoice and payment fields on the opportunityUpdate
NetSuite, SAP S/4HANA or QuickBooksCustomer, sales order or invoiceReadCreate
Slack or TeamsNotes to the ownerWrite
[ 04 / Build it with the engini skill ]

Describe it in plain words. The engini skill builds the workflow.

engini skills is engini’s plugin for Claude Code and Codex. Its workflow agent, Flo, turns a plain-language request into an engini workflow: it designs the steps, dry-runs them against your own engini account, shows you a proposal, and creates the workflow only after you approve it, always turned off. You check it in the engini designer and turn it on.

Blurred landscape photo with the Salesforce logo, the engini mark and the NetSuite logo joined by a thin line, labeled quote accepted: quote, check, ERP order

Editorial image: quote, order, invoice, paid.

Claude Code: install once
/plugin marketplace add engini/skills
/plugin install skills@engini
Then ask for this solution
Build a workflow in my engini account: when a Salesforce opportunity is marked Closed Won, read its quote lines and account, upsert the customer in NetSuite using the Salesforce account id, create a NetSuite sales order with the quote lines, and write the sales order number back to a field on the opportunity. Post a message to the opportunity owner in Slack with the order number.
  1. You need an engini account, the engini CLI (npm i -g @engini/cli) and a workspace-scoped API key, ideally a dedicated least-privilege one.
  2. Connect the systems this flow uses in engini first. Flo never creates or changes a connection and never handles your key; it tells you which command to run.
  3. Flo checks your login and workspace, searches the tool catalog, compiles the plan and shows a proposal table with every step. It creates the workflow only when you approve that proposal, and it creates it turned off.
  4. Open it in the engini designer, fill anything it left for you, and turn it on.
engini skills for Claude Code and Codex →
What the skill will never do on its own →
[ 05 / Agent Policy ]

The agent does only what you allow. Every run is on the record.

Agent Policy is how you govern agents in engini: the tools each agent may call, the account each tool uses, and a record of every call.

Toolsets

Scope every call

Hand the agent a toolset: only the tools it needs, each on the connection you choose, for example read only. engini enforces it on the server for CLI, SDK and REST API calls; a call outside the toolset is refused. An MCP server exposes only the connections and tools chosen when you set it up.

Identity

Acts with the account you connect

engini acts with the permissions of the connected account. Connect a person’s own account and it acts as that person; use a shared integration account and it acts as that account. Every run is recorded under the user who triggered it.

Audit

History and audit log

Each tool call and workflow run is recorded in History and the audit log, which supports export and streaming to your SIEM. Your agent never needs your credentials: engini stores them and adds them when it runs each call.

SOC 2 Type IIISO 27001GDPRHIPAA compliant
[ 06 / Try it now ]

Build it on your own data today

Start free, connect Salesforce, and build this flow with the engini skill, in Workflow Studio, or from your own agent.

  • 01Workflow Studio. Build the flow on a visual canvas, with an AI agent step where judgment is needed. Start free →
  • 02Your own agent. Give Claude, ChatGPT or Cursor an engini MCP server with only these tools. MCP client setup →
  • 03The engini skill. Ask Flo in Claude Code or Codex and review its proposal. Install the skill →
[ 07 / Questions ]

Questions buyers ask before they start

How do closed-won opportunities turn into ERP orders automatically?

A Salesforce outbound message starts an engini workflow the moment the opportunity closes. An AI agent checks the deal, then the workflow creates the customer and the order in your ERP and writes the result back to the opportunity.

Which ERPs does it work with?

NetSuite, SAP S/4HANA and QuickBooks are common, and the same pattern works for other systems engini connects to, including databases and systems behind your firewall through the on-prem agent.

Can reps see invoice and payment status in Salesforce?

Yes. A return flow writes order numbers, invoice numbers and payment status to the opportunity or a custom object, from a NetSuite trigger checked as often as every 15 minutes or a scheduled read for SAP and QuickBooks.

Does it need Salesforce CPQ?

No. It reads standard opportunities, opportunity products, quotes and quote lines, and works with custom objects and fields too, since engini reads each org’s own setup.

How does engini sign in to Salesforce?

By default through engini’s managed package installed in your org, with OAuth and no keys to create or copy. You can also use your own Salesforce app.

How is this different from Agentforce or MuleSoft?

Agentforce works inside Salesforce. MuleSoft is an integration project. engini runs the flow across Salesforce and your ERP with an AI agent check in the middle, built in Workflow Studio or with the engini skill, and the same connections serve your own agents.