These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
Integrations
Connect the deal from your CRM through signature, delivery and accounting.
Connect CPQ around clear ownership of accounts, commercial documents, delivery and finance. The specification describes the required exchange; provider support, interfaces and access need to be configured and verified for the deployed application.
- CRM
- Accounts and contactsAccounts, Contacts · in and out
- Opportunities and productsOpportunities, Products · in
- Commercial updatesin and out
- E-signature
- Documents outout
- Evidence inin
- Provider setupin
- Fulfillment and provisioning
- Released ordersProducts · in
- Delivery evidencein and out
- Accounting and payments
- Invoices and creditsInvoices · in and out
- Cash and correctionsPayments · in
- Tax ownershipout
- Customer communications
- EmailInvoices · in and out
- Agents
- Your agentWorks within the permissions you assign
CRM
- Accounts and contacts. Keep stable source identifiers and define which team may change billing, ownership and credit details. Resolve contact and account references before using them on live documents.
- Opportunities and products. Bring the proposal context and source product lines into quoting. Unmapped SKUs stay in a review queue until a valid catalog match is made.
- Commercial updates. Return the primary quote’s agreed amount and outcome with its revision context. A delayed event from an older proposal must not overwrite a newer accepted result.
E-signature
- Documents out. Send the approved revision with its parties, selected options, commercial values and operative terms. Preserve the original document and the executed copy separately.
- Evidence in. Retain provider event identity, timestamps and payload context. Validate the envelope and revision before applying a signature, decline or void; repeated and stale callbacks cannot accept a different offer.
- Provider setup. Assess the selected signature provider, signer routing and document requirements during implementation. Naming a provider in the model is not a verified connector commitment.
Fulfillment and provisioning
- Released orders. Carry accepted line values, products, configured options, bundle references, addresses, purchase order and service dates into the receiving system. Retain the destination’s reference with the delivery outcome.
- Delivery evidence. Record shipment or provisioning quantities separately from customer acceptance. A billing milestone uses the specific event and extent of completion agreed for it.
Accounting and payments
- Invoices and credits. Preserve source line, product, revenue category, service period and tax provenance. Keep local preparation separate from confirmed external posting and retain the accounting reference.
- Cash and corrections. Import payments with stable source references, and exchange applications, returns, refunds and credit effects without applying the same money twice. Finance owns matching exceptions and reconciliation.
- Tax ownership. Agree whether configured supported cases are calculated locally or accounting supplies the final tax. Missing tax is unresolved, and accounting-owned totals must return before an invoice is sent or settled.
Customer communications
- Email. Use the company’s configured sending identity for quote links, invoices, reminders and notices. Preserve delivery status and suppress historical messages during migration.
Approval conditions
Visible to: Deal Desk. Visibility does not establish approval authority.
Draft
- SO-20115 ACC-31122 4 d
- SO-76815 ACC-54036 10 d
- SO-20787 ACC-36208 14 d
- SO-15359 ACC-54206 8 d
- SO-23801 ACC-82164 14 d
SO-20115
- Account
- ACC-31122
- Quote
- QTS-35640
- Contract
- CNT-63783
- OrderDate
- 13 Sep
Approval conditions.
How connections are governed
service accounts, audit, pausingGive each connection a scoped identity, an owner and an explicit set of actions. Retain event keys, payload digests and per-destination delivery outcomes. Repeated delivery should reuse the prior result; conflicting content or an uncertain remote outcome needs reconciliation before a retry could create another signature request, order or financial posting. Pausing a connection must leave its unfinished work visible.
The API is one more client of the same interface. AI agents →
# Example work after configuration
$ curl -fsSL erpai.studio/skill.md
› Find quotes waiting on a terms decision and summarize the requested changes.
› Compare this proposal with the version that was sent to the buyer.
› List released orders whose billing schedule still needs review.
› Show unmatched payments with possible invoices from the same account.
› Find renewal decisions that are approaching their notice deadline.