What Is Epicor Edge Agent? Features, Uses & Limits
Epicor AP Automation vs. Hyperbots: Features, Capabilities & Key Differences
Epicor now uses the word "agent" for three very different things: the Prism AI agents, the On-Prem Agent inside Automation Studio, and the Epicor Edge Agent. As our guide to Epicor AI, Prism, Edge Agent and Automation Studio explains, only Prism is AI in the sense most buyers mean.
That matters when a finance or IT team sees "Edge Agent" in a Kinetic setup screen and wonders whether it can automate work, a question that often comes up while teams are comparing Epicor AP automation with Hyperbots. This article explains what Epicor Edge Agent is, what it does in Kinetic, where its scope ends, and how it relates to finance-specific AI agents.
What Is Epicor Edge Agent?
Epicor Edge Agent is a small Epicor application, installed on a user's computer or on a server in the company network, that lets browser-based Epicor Kinetic reach local resources a web browser cannot reach on its own. Despite the name, it is not an AI agent. It does not read documents, make decisions or automate a business process.
The problem it solves is a browser security limit. Web browsers isolate the pages they run, so a page cannot see the printers, files or devices attached to a person's machine. Browser Kinetic hits that wall whenever a user prints or attaches a local file. Edge Agent acts as the trusted bridge between the browser session and the machine.
Epicor's own explanation, posted on the EpiUsers community forum during a 2023 certificate update, describes Edge Agent as an Epicor component for Kinetic browser users on cloud and on-premises deployments. It provides services that browser security otherwise blocks, plus network printing for Kinetic cloud customers. The same post notes that Edge Agent includes QZ Tray, a third-party component Epicor licenses.
In plain terms, the agent runs a small local web service (port 6071 by default). When Kinetic needs a printer list or a local file, it sends a request to that service, and origin rules set during setup accept requests only from the customer's configured Epicor app server (EpiUsers Experts' Corner).
Edge Agent should not be confused with two other Epicor "agents":
Epicor Prism agents are AI agents embedded in Kinetic that answer questions and carry out supported ERP tasks.
Automation Studio's On-Prem Agent lets the cloud-based Epicor Automation Studio integration platform reach approved on-premises systems.
Edge Agent sits below both: it is plumbing for the browser, not intelligence or integration.
Epicor Edge Agent Features and Capabilities
Edge Agent's capabilities fall into five groups. Epicor's 2023 forum explanation lists the first four; the fifth is described in Epicor's Kinetic setup documentation and community guides.
Capability | What it does | Problem it addresses | Dependencies |
Client (local) printing | Sends Kinetic reports from the browser straight to a printer on the user's machine | Browsers otherwise force a print preview first | Local-mode agent on each user's PC |
Network printing | Lets Kinetic cloud customers print to shared network printers | Cloud Kinetic cannot see printers inside the customer's network | Network-mode agent running as a service on a print server; printers set up in Kinetic Printer Maintenance |
Local file access | Lets users attach and open files from local drives and file shares | Browsers cannot read local files on a page's behalf | Local agent; not needed for files stored in ECM, SharePoint or other web sources |
Scale access | Reads serial and USB scales from browser-based Kinetic | Weighing devices are invisible to a browser | Supported scale hardware and agent configuration |
Classic screens from the browser | Opens Classic (desktop) screens from a Kinetic browser session, part of Epicor's Browser First approach | Not every screen had a browser version | A local Kinetic client install; Windows only |
Local mode runs as a tray application on the user's PC, and network mode runs as a background service (EpiUsers). Both include a diagnostics page and logs for troubleshooting.
The Classic-screen feature is changing. Community discussion of Kinetic 2026.1 indicates that, with the desktop smart client retired, Edge Agent remains available but loses the ability to launch it, while printing and file access continue (EpiUsers). Buyers should confirm the current feature set for their release with Epicor.
What Can You Use Epicor Edge Agent For?
Edge Agent is useful wherever people work in Kinetic through a browser and still need something on their desk or local network. The examples below are labelled by how well they are supported.
Documented uses
Printing reports directly. A user runs a report in browser Kinetic and sends it to the printer beside them, without opening a preview and printing again.
Printing to shared printers from Kinetic cloud. A warehouse or office prints labels and documents to network printers that the cloud application cannot reach directly.
Attaching local files. A user attaches a document saved on a local drive or file share to a Kinetic record.
Reading scales. Shipping or receiving staff capture weights from serial or USB scales in a browser session.
Reasonable implications for finance teams
Finance users who move to browser Kinetic benefit in the same everyday ways: printing reports at their desks and attaching supporting documents stored on a shared drive. These follow from the documented printing and file features; they are not separate finance capabilities.
Not supported
No Epicor source reviewed describes Edge Agent reading invoices, extracting data, matching documents, coding transactions or posting entries. Attaching a supplier invoice PDF to a record is file handling; interpreting that invoice is a different job, handled elsewhere in the stack.
Epicor Edge Agent Limitations: What Should Buyers Know?
Edge Agent's main boundary is its scope: it lets the application talk to the local environment, and it leaves the business process to other tools. Beyond that, most practical limits depend on release and setup, so treat the points below as questions to settle with Epicor or your partner.
Which environments are supported? Epicor's Kinetic 2024.1 setup guidance states that Mac users get report printing only, while launching Classic screens requires Windows. Community users report no native Linux version. Confirm the current list for your release.
What setup does it need? An administrator enables the download in Company Maintenance, and installation may need local admin rights. Larger rollouts typically use a silent installer.
Will the versions match? Agent versions are tied to Kinetic versions. Forum users report that a 2025.1 agent could not print directly against a 2024.1 environment, so align agent updates with ERP upgrades.
What security controls apply? Requests are limited to configured app-server origins. Network mode uses a service account whose permissions may need Epicor support to enable. Ask how certificates, updates and access are managed.
What happens if it is unavailable? Users can still print from the browser's print preview, network printers remain reachable through a network-mode agent, and attachments stored in ECM, SharePoint or other web sources do not need it. Some community users report intermittent preview-instead-of-print behaviour, so test with your own printers and report types.
What does it not cover? Report design, printer setup, document management and any finance workflow sit in other Epicor products or configuration. Edge Agent only delivers the result to the local device.
Epicor Edge Agent vs. Finance-Specific AI Agents
Edge Agent and a finance-specific AI agent work at different layers of a Kinetic environment, so they are not substitutes. Edge Agent connects the browser to the desk. A finance AI agent carries a finance task, such as processing a supplier invoice, from document to posted record.
Dimension | Epicor Edge Agent | Finance-specific AI agent |
Primary purpose | Give browser-based Kinetic access to local printers, files and scales | Automate supported finance tasks such as invoice processing |
Where it runs | User PC (local mode) or network print server (network mode) | Alongside the ERP, connected through the ERP's integration interfaces |
Interaction with documents | Prints them and attaches files; does not read their content | Reads invoices and extracts header and line data, where supported |
Accounting decisions | None | Matching against POs and receipts, and GL coding suggestions, where supported |
Human oversight | User actions in Kinetic, plus admin setup | Configurable review, approvals and exception routing |
Dependencies | Installation, version alignment, printer and permission setup | ERP connector, field mapping, matching and coding rules |
The useful question is not which agent is better. It is whether the buyer needs an environment-level utility, finance-process automation, or both. A team moving AP clerks to browser Kinetic may need Edge Agent for printing and attachments and still spend most of its hours keying and matching invoices.
How Hyperbots Complements Epicor Kinetic (with a Persimmon Technology Case Study)
Hyperbots adds finance-specific automation to Kinetic for supported AP workflows, while Kinetic stays the ERP and system of record. It does not replace Edge Agent and has no direct integration with it: Edge Agent serves the browser session, and Hyperbots connects to Epicor through its Epicor connector.
How the integration works
Reads from Epicor. The connector reads vendors, items, GL accounts, companies, payment terms, purchase orders and receipts, synchronizing only records that changed.
Prepares the invoice. The Invoice Processing HyperAGENT extracts header and line fields, checks that essential information is present, applies GL coding to non-PO lines, and runs 3-way matching of PO lines against goods receipts.
Posts through Epicor. Invoices go through Epicor's own validation and posting, and success is reported only after Epicor confirms the posting.
Handles failures. If a step fails, records created in that attempt are rolled back, and Epicor's own error message is surfaced.
Keeps people in charge of exceptions. Unresolved cases and approvals route to finance staff through human-in-the-loop controls.
One naming note: for on-premises Epicor, Hyperbots installs a lightweight connector agent on the Epicor app server. That agent is Hyperbots' integration component, not Epicor Edge Agent.
Case study: Persimmon Technology on Epicor
Persimmon Technology runs Epicor on-premises. In a recorded interview with Hyperbots, Dave Sackett, VP of Finance, explained that the Invoice Processing HyperAGENT reads PDFs from the AP Outlook mailbox, matches them three ways against the PO and receipt, generates GL codes and tax, and posts the AP invoice in Epicor, with about 80% going straight through. Persimmon reports cutting AP data entry by 80%.
Controls were built in. After every write, the connector reads the record back and compares amount, currency, company and posting date. Errors such as a closed fiscal period trigger three automatic retries, then land in an Integration Exceptions queue with a Teams alert to finance. On new installations, a person validates the work before final submission. The on-premises agent opens an outbound HTTPS tunnel, so no inbound firewall changes were needed.
Persimmon went live in three to five weeks, faster than usual. For ERPs where Hyperbots already has API connectors, including Epicor, implementation typically takes six to eight weeks.
How to Choose the Right AI Agent for Your Epicor Workflow
Start from the requirement, then pick the tool:
Browser Kinetic needs to reach printers, local files or scales. Evaluate Edge Agent against Epicor's documentation for your release, operating systems and printing mode.
AP needs invoices read, matched, coded, posted or triaged. Evaluate finance-specific automation on your own invoice mix, including PO and non-PO invoices, partial receipts, price variances and unusual layouts.
Both needs exist. Scope them separately. They have different owners, usually IT for Edge Agent and finance with IT for AP automation, and different success measures.
Whichever path applies, test six things before committing:
The exact business problem, stated as a task and a measure, such as "print pick lists at the packing bench" or "post PO invoices without re-keying".
Integrations and permissions the tool needs, and who grants them.
Human effort that remains, counted in touches per invoice or per print job.
Failure handling: what users see when a write, print or connection fails, and how it is retried.
Security and audit requirements, including certificates, access scopes and audit trails.
Deployment and upkeep: installers, version alignment with Kinetic upgrades, and who maintains the configuration.
Epicor Edge Agent or Finance AI: Choosing the Right Agent for Kinetic
What is Epicor Edge Agent? A local utility that lets browser-based Kinetic print directly, reach local files and read scales. It removes real friction from moving to the browser, but it is not an AI agent, and it does not interpret documents or automate finance work. The product choice should follow the business problem, not the word "agent" in the name.
When the bottleneck is AP work itself, finance-specific AI addresses a different need. Hyperbots is worth evaluating when a team wants supported invoices extracted, matched, coded and posted in Kinetic, with exceptions routed to people and Kinetic kept as the system of record. Book a Hyperbots demo to see how the Invoice Processing HyperAGENT handles a sample of your own Epicor invoices.
Frequently Asked Questions
Is Epicor Edge Agent an AI agent?
No. Edge Agent is a local application that gives browser-based Kinetic access to printers, local files and scales that browser security would otherwise block. It does not analyze data, reason about documents or make decisions. Epicor's AI agents are part of Prism, a separate product.
Do I need Edge Agent to use Kinetic in a browser?
Not for everything. Users can print through the browser's print preview, and attachments stored in ECM, SharePoint or other web sources open without it. Edge Agent is needed for direct printing to a local printer, local file access, scales and, for cloud customers, network printing through a network-mode agent.
What is the difference between Epicor Edge Agent and Epicor Prism?
Prism is a portfolio of AI agents embedded in Kinetic that answer natural-language questions and carry out supported ERP tasks. Edge Agent is infrastructure that connects the browser to local devices. They solve different problems, are deployed separately and can be used independently of each other.
Will Edge Agent still work after Kinetic 2026.1?
Community discussion indicates Edge Agent remains available for 2026 releases, but it can no longer launch the retired desktop smart client. Printing and file access are expected to continue. Because agent versions are tied to Kinetic versions, check Epicor's release notes for your exact release before upgrading.
Can Epicor Edge Agent automate AP invoice processing?
No. Edge Agent can print AP reports and let users attach invoice files from local drives, but no Epicor source describes it extracting, matching, coding or posting invoices. Those tasks come from Kinetic's AP functionality, add-ons such as Epicor ECM and IDC, Prism's document-capture agent, or third-party finance AI.
How does Hyperbots work with Epicor Kinetic, and how long does setup take?
Hyperbots connects through its Epicor connector, reads master data, POs and receipts, and posts invoices through Epicor's own validation, confirming each posting. It does not interact with Edge Agent. For ERPs with existing Hyperbots API connectors, including Epicor, implementation typically takes six to eight weeks; Persimmon Technology's rollout took three to five.
