Get your first answer

Connect your AI client, sign in with Epicor, and make Cutova available in the conversation. Your administrator must first install a pack or publish tools for the business question you want to ask.

Working with an AI assistant

Treat the examples as starting points, not exact scripts. The same prompt can produce different questions, approaches and results, even with the same assistant. Each video shows one session.

Describe your goal and constraints. State important assumptions if the assistant does not ask. Build the result together through iteration. If the first answer or query is not what you expected, explain what you want changed and ask the assistant to revise it. Keep what works and refine the rest. You can narrow the scope, add detail, change the presentation or adjust a requirement. You do not need a perfect opening prompt. Seeing an initial result often helps you decide what you need next.

For example, ask: “Keep the customer totals, but show them by month,” or “Add the request date so I can check the calculation.” Continue the conversation until the result meets your needs. Iteration is part of the process, even when nothing is broken.

Check each revision against your requirements and the Epicor data. Stop if you cannot verify the result. Success means meeting your requirements and checking the result, not matching the video’s conversation.

With Executive Insights

Use the Executive Insights video as an example of exploring open receivables. Choose the follow-up questions that help you understand your results. You do not need to ask them in the recorded order. The recording uses Claude and a demo database. Your balances, customers and dates will differ.

Before you start

• Install Executive Insights and its skill on the instance you want to query.
• Connect and authorize your assistant. Reuse an existing connection to that instance.
• Enable the skill and code execution as described in the installation guide.
• Use an Epicor account that can read the required data.

Executive Insights is included with every tier, including Free. This example reads Epicor data. It does not apply cash, change invoices or send email.

Ask for a briefing

The recording starts with a broad business question. This prompt follows that request, with spelling and punctuation corrected:

How is my business doing today? Can I get some insights from my ERP?

Confirm the company, currency and reporting date before using the answer. If the assistant does not ask, state them yourself. If its briefing is too broad, narrow the request to one customer, period or business question. The recording shows tool permission, a briefing, receivables charts and suggested priorities. A general explanation without a tool call does not confirm the connection.

Inspect one customer’s invoices

Replace [customer] with a customer from your results. This prompt adapts the recording’s aging question and makes the required output explicit:

Break down [customer]'s open receivables by month and aging bucket.
Show invoice number, invoice date, due date, terms, balance and days past due.
Keep the same company, currency and as-of date. State the bucket boundaries.

Check whether the answer includes the invoice detail and aging breakdown you requested. If columns or rows are missing, ask the assistant to explain the omission and revise the result. The video shows one possible table after a receivables tool call. Ask for a table if your client cannot display interactive charts.

Separate invoices from unapplied cash

The video shows customer charts before and after accounting for unapplied cash. If this distinction is useful for your results, adapt this follow-up:

Show open receivables by customer, with gross invoice balances, credit memos
and unapplied cash shown separately. Explain how you calculate net exposure.
Do not treat unapplied cash as an invoice payment or change any Epicor records.

A net exposure calculation does not apply a receipt in Epicor.

Check the result in Epicor

1. Open the customer’s invoice details in Epicor.
2. Match invoice numbers, due dates, terms and remaining balances.
3. Compare the aging total using the same company, currency, date and bucket boundaries.
4. Check credit memos and unapplied receipts separately. Confirm their signs and avoid counting them twice.
5. If totals differ, give the assistant the specific discrepancy and ask it to inspect its filters and calculations.
6. Check the revised answer against Epicor again before using it.

The recording shows assistant output. These checks are instructions for your own run, not evidence of a filmed reconciliation.

Optional: draft a collections email

The recording ends with a draft email. After checking the balances, try:

Draft a collections email for [customer] using the invoice details I checked.
Ask for remittance details where cash remains unapplied.
Leave the recipient and signature as placeholders. Do not send it.

Review the wording, amounts and recipient before sending through your normal email process.

About the recording

This is an approximately 46-second edited demonstration, not a setup-time estimate. It starts with an assistant connection already available. Use the linked installation and authorization guides for those steps.

The exact Epicor release and Cutova tier used for the recording are not shown. The written follow-ups above are adapted instructions, not a new independently tested run.

With BAQ Builder

Use the BAQ Builder video as an example of building an on-time delivery query by customer. Your assistant may ask different questions or use a different approach. Agree on the requirements and test the resulting query.

Before you start

• Install BAQ Builder and its skill.
• Connect your assistant to a development or Pilot instance with demo data.
• Use an Epicor account that can create and test BAQs.
• Choose a new BAQ ID so the example does not replace an existing query.

BAQ Builder is included with paid plans and their 14-day trial. This example creates a BAQ in Epicor. Review and test it before using it outside your sandbox.

Describe the query

The recording asks for 2023 and 2024. Replace the years with periods that contain data in your demo instance. This prompt adapts the recorded request:

Create a BAQ showing on-time performance by customer for [first year]
and [second year]. Exclude customers without orders.
Use the new BAQ ID [new query ID] in my development company.
Ask me to clarify the date rules before building it.

Define “on time”

Agree on the date rules before the assistant builds the query. In the recording, the user chooses:

• On time means shipped by the customer’s request date.
• The request date determines the reporting year.

Use those choices if they match your requirements. If the assistant does not ask, state your rules explicitly. Different date rules answer different business questions.

Ask the assistant to explain how it handles partial shipments and unshipped releases. Confirm whether customers with orders but no shipments should appear.

Build and review

Ask the assistant to inspect the Epicor schema and explain its proposed query. Review its tables, joins, company filters and calculations. Clarify assumptions before it creates the BAQ.

The video shows one example of iteration: generated template header and detail rows used different company codes. The assistant corrected those values before the result appeared in Epicor. Your session may encounter different problems or none. This correction is not a step you must reproduce. Use your development company’s code, not the code from the video.

If creation or testing fails, provide the actual error or incorrect result and ask for an explanation and proposed correction. Review the change and test again. A query can run successfully and still answer the wrong business question.

Test in Epicor

1. Open the new query in BAQ Designer.
2. Select Test in the query test area.
3. Confirm the company and reporting years.
4. Check one customer’s shipment and request dates against the underlying Epicor records.
5. Confirm that joins do not count a release more than once because it has multiple shipments.
6. Check the on-time percentage against the counts used in its calculation.
7. Confirm how early shipments affect average days late. Do not assume negative values are errors.

The recording shows customer ID, name, year, shipped releases, on-time count, late count, on-time percentage and average days late.

For example, one displayed row has 74 shipped releases: 43 on time and 31 late. Its displayed on-time percentage is 58.11%, consistent with 43 divided by 74. This checks the displayed arithmetic. It does not independently verify the underlying shipment records.

About the recording

The approximately 35-second edit shows Claude and a query running in Epicor. It includes a correction and is not an end-to-end timing claim. The exact Epicor release and Cutova tier used for the recording are not shown.

The prompts and checks help you work toward the recorded goal. They do not guarantee the same conversation or generated query. A fresh installation and an independent reproduction of this written example remain unverified.

With your own tools

Choose a question your published tool supports. For a purchase-order lookup that supports sorting and limiting results, try:

List the five most recent purchase orders. Include the order number, supplier, and order date.

For a customer lookup, ask for a customer instead. A tool’s description explains its purpose and available inputs. Start with a read-only query and verify the result before using tools that change records.

Company and plant

On an instance configured for multiple companies or plants, ask:

Which Epicor companies and plants can I use?

The built-in company tool lists your available choices. Your selection applies to later calls until you change it. A single-company, single-plant instance does not offer this tool because there is nothing to select.

If the expected tool is missing

1. Complete authorization in your client’s connector settings.
2. Confirm you used the MCP URL for the intended instance.
3. Ask your administrator to check that the relevant pack tools or custom tools are installed and enabled.
4. Refresh the client’s tool list or reconnect after tools change. Make Cutova available in the conversation.

For an access-denied response, have your administrator check Epicor permissions and the connection’s API key scope. See Troubleshooting for specific errors.

Confirm setup in the console

If you are using the console’s setup guide, select I got my first result after a successful call. This is your confirmation. Cutova does not inspect your assistant conversation to detect success.

What you can add next

• More pack tools for other business questions.
• Your own BAQs, Epicor Functions, and Business Object operations.
• Built-in tools for charts, record displays, and user prompts, where your client supports them.

Ask your administrator to publish the tools you need. Installing Cutova does not expose every Epicor operation automatically.