Skip to content

Ask Your ERP for Epicor Kinetic

Plain-English questions over Kinetic’s own data, answered to the penny with a governed read-only query, every figure tied to the rows behind it, every question logged with a name.

Finance & reportingUpdated Oct 202620 ERPs

See it work on Kinetic.

Click through the steps. Fictional data, in Kinetic’s terms; the real thing runs on Kinetic.

Ask · Sam Okafor, 6:02 am
Illustrative

Which accounts are more than 90 days beyond their terms, by salesman?

Five accounts, $76,792.50 in total. Three belong to Rick Alder.

SalesmanCustomerBeyond termsBalance
R. AlderBayview Decks118 days$31,240.15
R. AlderOak Hill Builders104 days$9,870.00
R. AlderFerry St Renovations97 days$12,402.35
T. NguyenShoreline Electric101 days$12,980.00
T. NguyenGranite Peak Builders95 days$10,300.00

5 rows from Kinetic’s open items, aged on each account’s terms · read at 6:02 am · query shown below

A governed, read-only query over the open items, aged on each account’s own terms. The rows come back with the answer.

1 / 4

The problem, as it happens in Kinetic.

The number exists in Kinetic. Getting it means knowing which screen, which report, which filter, or asking the one person who does and waiting until they’re free.

So people keep their own spreadsheets, and three versions of last month’s sales circulate on Monday.

How it works.

  1. 1

    Ask in English

    Open accounts over ninety days by salesman. Drywall sales this month against last. What we paid a vendor in the third quarter.

  2. 2

    A governed, read-only query

    Written against curated knowledge of Kinetic’s tables and terms codes, checked by a governor: select only, single statement, row-capped.

  3. 3

    The answer, cited

    The figure, the table behind it, and the query, so anyone can check it. Validated against Kinetic’s own screens during setup.

  4. 4

    Export or automate

    Excel or PDF in one click. Save the question as an automation and have it in your inbox every Monday.

How it connects to Kinetic.

Lunica reads Kinetic through Kinetic’s REST services or a read-only database login: the customer master, open items, invoice history, purchase orders and receipts, the part master, whatever the question needs. Each query is written against curated knowledge of Kinetic’s tables and terms codes, so an account on Net 30 ages from end of month, and runs as a single select capped at a row count. The model sees the question, the schema context and the rows behind the answer, never the whole database.

Nothing is written to Kinetic by Ask, and nothing is sent on its own. The governor allows one read-only select per question and refuses everything else. An export is a file a person downloads; a saved question goes only to the inbox of the people you named. If an answer leads to a change, a credit limit, a price, a count, that change is keyed by your team in Kinetic, never by a query.

What a week looks like.

  • The number comes from the system of record, not a spreadsheet.
  • Every answer shows its work.
  • Every question is logged with the user’s name.
  • Monday’s report writes itself.

Questions

Can it change anything in Kinetic?

No. Every query passes a governor that allows a single read-only select and nothing else.

Is it accurate?

Answers are validated against Kinetic’s own screen values during setup, and every figure links to its rows so you can check.

Who can use it?

Anyone you give an account. Read-only accounts can ask; only named users can send or act.

Which Kinetic data can it see?

Whatever the read-only account is granted: the customer master, open items, sales history, purchasing, inventory. The scope is set at onboarding and can be narrowed per user.

Does it run on our server?

Yes. Lunica runs on one server inside your network, whether Kinetic is in Epicor’s cloud or on your own server, and every query runs there against Kinetic’s REST services or a read-only database login.

Does our data train anything?

No. The model sees the question and the schema context it needs, and nothing is used for training.

Does it need a server?

Lunica runs on one server inside your network, whether Kinetic is in Epicor’s cloud or on your own server, set up and maintained by Lunica. It reads Epicor Kinetic through Kinetic’s REST services or a read-only database login. There is no inbound connection from outside your network.

What does Lunica read in Kinetic?

The customer master, open items and terms, purchase orders and receipts, the part master, quotes and order history, as each workflow needs them. Read-only, and only the rows a task is about.

Can it post to Kinetic?

Nothing lands in Kinetic without a person. What belongs in Kinetic goes back as a Kinetic REST call or DMT import where one exists, or keyed by your team from what Lunica prepared.

What about our documents?

Invoice copies and scans keep living in Epicor ECM. Lunica reads them when a workflow needs one and never writes to them.

The same workflow, on another ERP.

Ask Your ERP is written for every system on the list. You’re reading the Kinetic version.

See it on your Kinetic data.

Thirty minutes. We walk the workflow on Kinetic data, then map it to yours.