No staging, no import file
Nothing is installed in Epicor and nothing waits in a table for a job to pick it up. A record either exists in Epicor or it does not.
Connect Fluent to the Epicor you already run
Native Epicor v2 REST, against your own instance. Nothing is installed inside Epicor, nothing lands in a staging table, and the ceiling on what Fluent can call is a file your team holds.
Coverage
Reach ten Kinetic screens and the data behind them
Fluent posts through the same screens your team uses, so a transaction it creates is a transaction Epicor validated.
- Ten Kinetic screens
- Quote Entry, Order Entry, Customer Shipment, AR Invoice Entry, Cash Receipts Entry, PO Entry, Receipt Entry, AP Invoice Entry, Time Entry and Issue Material.
- BAQs and dynamic queries
- Questions answered from your own queries, run through Epicor's engine rather than a copy of your data.
- Your OpenAPI definitions
- Agents read the live definitions off your instance, so they work from your customizations and not a generic schema.
Connectivity
Set up four things your team already controls
Most Epicor instances are not on the public internet, and the people who have to approve this are the ones who keep it that way. Everything below is theirs to create, hold and revoke.
- 01
An integration account
A dedicated user in User Account Maintenance, not an employee's login, with a password set never to expire.
- 02
An API key you hold
Generated in API Key Maintenance and stored wherever you keep secrets. It authenticates v2 REST, and you can revoke it without calling us.
- 03
A path to your instance
Fluent calls out from fixed egress IPs, so an on-premise instance needs those addresses allowlisted and nothing else. Epicor-hosted usually needs no change at all.
- 04
A connection that proves itself
Before Fluent accepts a connection it resolves the hostname, opens the port and reads the certificate. A check it cannot complete is reported, not assumed.
Least privilege
Grant exactly the methods each agent needs
Every agent generates an Epicor access scope from the tools it actually calls. You import that file in Security Management and bind it to the API key.
Erp.BO.VendorSvcGetRows
Erp.BO.RcvDtlSearchSvcGetRows
Erp.BO.POSvcGetByID · GetRows
Erp.BO.APInvoiceSvcGetNewInvcHead · ChangeVendorID · UpdateExt
- Derived, not drafted
- The scope is traced from the agent's own tools, so it lists what that agent calls and stops there. An agent that never touches receipts never asks for them.
- Changes arrive as a diff
- Change what an agent does and its scope changes with it. Your administrators get a digest naming every permission added and every one removed, before anything needs re-importing.
- The ceiling is yours
- Epicor enforces the scope, not Fluent. Narrow it, revoke the key, or unassign the account and the agent stops at your boundary rather than ours.
The write
Let Epicor validate every write before it lands
Fluent has no privileged path into your database. It calls the same business objects the Kinetic screens call, which means your own rules, your own BPMs and your own required fields apply exactly as they do to a person typing.
Committed as one transaction
Where Epicor offers it, the header and its lines commit together, so a line that fails validation rolls the whole document back instead of leaving an orphan.
A person presses process
Every run ends in a draft carrying what it could not settle. You choose which agents may post on their own, and the rest wait.
Governance
Autonomy you can hand to an auditor
Every agent operates inside boundaries you define. Every action it takes is recorded, explainable, and reversible before it posts.
Approval thresholds
Low-risk orders post automatically; high-value or unusual ones wait for a person.
Audit logs
Every field the agent read, every decision it made, on the record.
Data retention
Your documents and data stay under retention policies you control.
Epicor validation
Transactions are validated by Epicor’s own business logic before they post.
Human review
Exceptions escalate to your team with the agent’s reasoning attached.
Permissions
Agents only touch the business objects and companies you allow.
Next
Run more on the same connection
Document automation
Order to cash, procure to pay and the shop floor, automated end to end across ten Kinetic screens.
Learn moreAnalytics
Ask your Epicor data a question, answered from your own queries with the query available to read.
Learn moreData syncing
Scheduled movement between Epicor and the systems around it, on your own transformation rules.
Learn moreEpicor ECM
Turn any ECM document type into a working agent, using templates your team already defined.
Learn moreFrequently Asked Questions
Ready to Save Hours Every Week?
Send us a batch of sample documents. Our Epicor specialists will show you what an agent can automate, and what still needs your judgment.
