Read back after every save
Fluent checks what Prophet 21 actually committed. An order that comes back missing a line is cancelled and reported, never left half-written.
Connect Fluent to the Prophet 21 you already run
Fluent works through Prophet 21's own APIs, against your own tenant. It reads your live customers, vendors, items and receipts, drafts vouchers and orders in the windows your team already uses, and installs nothing inside P21.
Coverage
Reach the P21 windows your back office keys by hand
Fluent drafts into the same windows your team uses, so a voucher or an order it creates is one Prophet 21 validated.
- Voucher Entry
- Supplier invoices vouched against PO receipts in Convert PO to Voucher, expense invoices in Voucher Entry By Amount, and vendor credits as debit memos.
- Order Entry
- Customer purchase orders drafted as sales orders, converted from the open quote when the order answers one, with the customer's job contract applied.
- Your live P21 data
- Customers, ship-tos, vendors, items, units and open receipts, read from your tenant as each document is checked rather than from a copy.
Agents
Automate Voucher Entry and Order Entry
Two agents for Prophet 21, built and running today: supplier invoices for accounts payable, and customer purchase orders for inside sales.
Epicor Prophet 21
Voucher Entry
Supplier invoices vouched against PO receipts, plus expense invoices and vendor credits, for AP to release.
Epicor Prophet 21
Order Entry
Customer purchase orders drafted as P21 orders, from the ship-to down to the contract price.
Connectivity
Set up four things your team already controls
Everything below is created and held in Prophet 21 by your own administrators, and can be taken back without calling us.
- 01
An integration user
A dedicated P21 user for Fluent rather than an employee's login, so every voucher and order it writes is attributed to it.
- 02
Read access you grant
Your P21 administrator lets that user read the tables the agents look up, in User Maintenance and Role Maintenance, and can narrow it there at any time.
- 03
A path to your tenant
Fluent calls out from fixed egress IPs, so a tenant behind a firewall needs those addresses allowlisted and nothing opened inward.
- 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.
The write
Let Prophet 21 validate every write before it lands
Fluent has no side door into your database. It writes through P21's own interfaces, so your required fields, your duplicate checks and your totals apply exactly as they do to a person in the window.
Duplicates caught twice
Fluent looks for a voucher on the same invoice number and an order on the same customer PO before drafting, and Prophet 21 refuses a duplicate voucher on its own.
A person approves the draft
Every run ends in a draft carrying what it could not settle. Vouchers are created unapproved by default, so AP releases them in P21 before a check run.
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
A document over an amount or outside a price tolerance goes to the approvers who own it.
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.
Prophet 21 validation
Transactions are validated by Prophet 21 before they post.
Human review
Exceptions escalate to your team with the agent's reasoning attached.
Permissions
Agents only touch the documents and companies you allow.
Frequently Asked Questions
No. Fluent calls Prophet 21's own APIs from outside, the way any integration does. There is no customization to deploy and no import file to schedule. If you disconnect Fluent, nothing has to be uninstalled.
Yes. Fluent calls out from fixed egress IPs, so a restricted network needs those addresses allowlisted on the P21 API endpoint and nothing opened inward.
What the integration user is allowed to read. Your administrator grants it read access to the tables the agents look up, in User Maintenance and Role Maintenance, and can narrow or revoke it there. Fluent writes only the vouchers and orders its agents draft, once a person approves them.
Supplier invoices and vendor credits into Voucher Entry, and customer purchase orders into Order Entry. Both agents are built and running. If your team keys another P21 window by hand, tell us which: that is how the next agent gets chosen.
Yes. User-defined fields on the order header and its lines can be filled from the document, with rules your team writes in the agent's settings rather than a customization inside P21.
What would you hand an agent in Prophet 21 first?
Send us a batch of the documents your team keys into Prophet 21 today. We will show you what an agent can match and post, and what still needs your judgment.
