How to Add a Supplier in Epicor (Step-by-Step + History)

If you have just joined an Epicor Kinetic team, one of the first questions you will hear is: how do I add a supplier in Epicor? The next one usually follows within a week: what have we actually bought from this supplier, and what did we pay them? 

Both answers live in Epicor, and neither is hard. Adding a supplier takes about ten minutes once you know which screens matter. The harder part is doing it well: with the right tax ID, the right bank details, the right payment terms and no duplicate record already in the system. Supplier setup errors don't fail at setup. They fail weeks later as a blocked invoice, a misdirected payment or a 1099 correction. 

This guide covers how to add a supplier in Epicor Kinetic step by step, how to look up supplier history in Epicor, and how to keep the vendor master clean as your supplier base grows. It also shows how one Epicor customer, Persimmon Technology, automated that work. 

Why Supplier Setup in Epicor Deserves More Care Than It Gets 

In Epicor, the supplier record is the root of the procure-to-pay chain. Every purchase order, receipt, AP invoice and payment inherits something from it: terms, currency, tax liability, payment method, bank details. Epicor treats procure-to-pay as a chain of linked records, so a bad supplier record surfaces downstream as an AP exception.  

Typical consequences of a sloppy supplier setup: 

• Wrong payment terms mean missed early-payment discounts or early payments that waste cash. 

  
  

• A missing or incorrect tax ID means 1099 and year-end reporting rework. 

  
  

• Two records for the same supplier split spend and history and make a duplicate payment possible. 

  
  

• Unverified bank details open the door to payment fraud. 

Keep these in mind as you go through the steps below. Most of the "optional" fields are the ones that cause trouble later. 

Before You Start: Gather the Supplier Information 

Collect these items before opening Epicor. Chasing them mid-entry is how incomplete records get saved. 

Search Epicor for the supplier first, by name, tax ID and address. It is the cheapest duplicate check you will ever run. 

How to Add a Supplier in Epicor Kinetic: Step by Step 

Step 1: Open Supplier Maintenance 

In Kinetic, go to Purchase Management → Setup → Supplier (the program is often called Supplier Maintenance). This is the master screen for supplier records. You can also use the menu search and type "Supplier." 

Step 2: Create a new supplier and assign a Supplier ID 

Click New, then enter a Supplier ID. This is the unique code every PO, receipt and invoice will reference, so use a consistent convention. Many teams use a short alphanumeric code derived from the legal name, or a sequential number. Agree on the convention first, because changing IDs later is painful. 

Then enter the Name exactly as it appears on the supplier's invoices and tax form. 

Step 3: Complete the Detail tab 

On the main detail view, work through the fields that control how the supplier behaves in transactions: 

• Address and country. Enter the supplier's main address. Country matters for tax and payment behavior. 

  
  

• Supplier group. Assign the group your reporting and defaults depend on. 

  
  

• Payment terms. Choose the terms code (for example Net 30 or 2/10 Net 30). If a terms code doesn't exist yet, set it up in the terms setup program first. This is why rationalizing payment terms across vendors and understanding variations in payment terms matter: terms entered once here govern cash decisions for years. 

  
  

• Currency. Set the supplier's transaction currency. For foreign suppliers, see our notes on handling multi-currency transactions. 

  
  

• Tax ID and tax liability. Enter the tax ID and the correct tax liability setting so sales and use tax and 1099 reporting behave correctly. Missing tax details are a common source of sales and use tax compliance problems. 

  
  

• Payment method. Choose check, EFT/ACH or another instrument, consistent with how you will pay. 

Step 4: Set up the purchase point 

A supplier generally can't be used on a purchase order without a purchase point, the address and contact details Epicor uses when you order from them. Add at least one primary purchase point with its address, contact name, phone and email. If the supplier ships from several locations or invoices from a different entity, add more. 

Step 5: Add contacts 

Add the people you actually deal with: a sales contact for POs and an AP contact for remittances and invoice queries. An AP contact on file saves time when an invoice is questioned. 

Step 6: Add bank and payment information 

For ACH/EFT suppliers, enter the bank account details in the supplier's bank or payment settings. Don't treat an emailed bank form as verification. Call back a known number on file, or use a verified onboarding process. Changed bank details on a supplier's letterhead are a common route into payment fraud. That is why vendor identity verification belongs before the record is created, not after. 

Step 7: Review defaults, flags and holds 

Check that the supplier is active, not on hold, and that any 1099 or reporting flags match what your tax team expects. Confirm any default GL or expense account behavior your company uses. 

Step 8: Save, then test the record 

Save the supplier. Then run a quick sanity test: start a new PO (without saving it) to confirm the purchase point, terms and currency flow through. A two-minute test is cheaper than discovering a broken terms code on the first invoice. 

How to Look Up Supplier History in Epicor 

Once a supplier is active, the next question is usually about history: open POs, what was received, which invoices were posted, what was paid and what is still owed. Epicor gives you several routes. 

Option 1: Supplier Tracker 

For most "tell me everything about this supplier" questions, start with Supplier Tracker (typically under Purchase Management → General Operations). Search by supplier ID or name, then use its views to move through purchase orders, receipts, invoices and payments. It answers "what did we order, what arrived, what was billed and what was paid?" in one place. 

Option 2: The transaction-specific trackers 

When you need to dig into one document type, use the dedicated tracker: 

• Purchase Order Tracker for open and closed POs, release dates and quantities still outstanding. 

  
  

• AP Invoice Tracker for posted and unposted invoices, balances and payment status. 

  
  

• Payment-related trackers for checks and EFTs, including voids and adjustments. 

Option 3: Aging and AP reports 

For a financial view of what you owe, use the AP aging reports and the Received but Not Invoiced report. The second is useful for supplier history because it shows goods received with no invoice yet. The AP clearing account acts as an early-warning system for invoices that are stuck or missing.

Option 4: Dashboards and BAQs 

If your team needs a recurring view, such as spend by supplier by quarter or price trends on key parts, build it once as a dashboard or Business Activity Query (BAQ) rather than rebuilding it in Excel each month. Ask your Epicor administrator or partner to set it up. 

Reading supplier history well 

Looking up history only helps if you know what to look for: 

• Spend concentration. Does one supplier take a disproportionate share of spend? 

  
  

• Price drift. Are unit costs creeping up against past POs or quotes? 

  
  

• Receipt-to-invoice lag. A supplier whose invoices arrive late creates accrual noise at month-end. 

  
  

• Discount behavior. If a supplier offers 2/10 Net 30 and you rarely capture it, that is cash left on the table. See how AI can capture missed early payment discounts. 

  
  

• Duplicate-looking records. If history looks oddly thin for a supplier you buy from constantly, some of it may sit on a second supplier ID. 

That last point leads to the real issue. 

Where Supplier Setup Goes Wrong in Epicor 

Epicor is a strong system of record, but it isn't built to chase documents, verify identities or detect near-duplicate suppliers. In practice, vendor-master problems cluster around five patterns: 

1. Duplicate suppliers. "Acme Industrial," "Acme Industrial Inc." and "ACME IND." become three IDs because the person adding the supplier didn't find the first one. Spend and history fragment, and the risk of a duplicate payment rises. 

   
   

2. Missing W-9s and tax IDs. Records get created "temporarily" without a tax ID and never get fixed, until year-end. 

   
   

3. Unverified banking details. Bank information arrives by email or PDF and is keyed in by hand, with no independent check. 

   
   

4. Inconsistent terms. The same supplier has different terms on different POs because the master was never aligned to the contract. Anomalies in payment terms are easy to miss when terms are keyed by hand. 

   
   

5. Manual, email-driven onboarding. AP chases suppliers for documents and corrections by email. We cover the broader problem in vendor onboarding challenges and the advantages of AI. 

None of these are Epicor bugs. They are what happens when a master-data process depends on people reading emails and typing. 

A Practical Vendor-Master Hygiene Checklist 

Whether or not you automate, these habits keep an Epicor supplier master healthy: 

• Search before you create. Check name variations, tax ID and address. 

  
  

• Standardize naming. Legal name, no abbreviations, consistent punctuation. 

  
  

• Require a tax form before activation. No W-9, no active supplier. 

  
  

• Verify bank details out of band. Never rely only on the form that came with the request. 

  
  

• Separate duties. The person who creates a supplier shouldn't also approve payments to them. 

  
  

• Review inactive and on-hold suppliers on a schedule and retire what you no longer use. 

  
  

• Audit changes. Keep a record of who changed bank details or terms, and when. 

The list is sound, but it depends on discipline at scale. If you add dozens of suppliers a month, it becomes a full-time job. 

How the Vendor Management HyperAGENT Automates Supplier Onboarding for Epicor

This is where Hyperbots fits. The Vendor Management HyperAGENT takes over the manual parts of supplier setup, so what reaches your Epicor supplier master is complete, verified and non-duplicated. It handles:

• Automated vendor onboarding. Workflows collect and validate the documents and details you need from a new supplier, such as tax forms, instead of AP chasing them by email. 

  
  

• Structured vendor information upload. Supplier master data is uploaded and validated in a structured format rather than keyed from PDFs. 

  
  

• Vendor identity verification. Tax IDs and bank details are checked before they are trusted, which reduces fraud risk. 

  
  

• Duplicate detection. Incoming suppliers are compared against your existing master so near-matches are flagged before a second record is created. 

  
  

• A self-service vendor portal. Suppliers submit information, check status and communicate in one place, with structured collaboration in place of scattered email threads. This is the same vendor visibility that cuts down on payment-status calls. 

  
  

• Automated remittance communication. Payment notifications reach suppliers without manual follow-up. 

Human-in-the-loop controls stay in place, so your team approves what matters, and every action is recorded in an audit trail. 

Clean suppliers pay off downstream. When the master is right, the Invoice Processing HyperAGENT matches invoices more reliably, and its duplicate invoice checks have a trustworthy baseline.

How Hyperbots Integrates with Epicor Kinetic 

A vendor-management layer only helps if it works with Epicor instead of around it. Hyperbots' Epicor Kinetic connector is built on Epicor's own service layer, not flat-file imports or generic middleware. It drives Epicor the way an Epicor user does, through the same business objects, validations and posting process. Nothing lands in Epicor that Epicor itself wouldn't have accepted. 

In practice: 

• Full-coverage sync. Vendors, items, GL accounts, payment terms and companies flow from Epicor into Hyperbots automatically, so Epicor stays the source of truth and your AP team never uploads vendor lists or chart-of-accounts extracts by hand. POs and receipts sync in, and AP invoices, accrual journals and POs created from requisitions are written back. 

  
  

• Native authentication and transport. Token-based authentication the way Kinetic expects it, scoped by company through configuration, with nothing hardcoded per customer. 

  
  

• Domain-smart invoice writes. Invoices are built the way Epicor structures them: pre-flight checks, an invoice group, header, lines, GL coding for non-PO lines and receipt matching for PO lines. The Epicor invoice number then appears on the Hyperbots record so your team can open it in Kinetic right away. 

  
  

• Clean rollback. If any step fails, the connector undoes what it created. Epicor ends up with a complete document or nothing, never a half-built invoice. 

  
  

• Posting that follows Epicor's own checks. An invoice is reported as posted only after Epicor confirms it, not merely when it is submitted. 

  
  

• Change-aware incremental sync. The connector tracks Epicor's own revision numbers, so re-runs read only what changed. Reads are paged and paced so a large initial sync doesn't flood a live system. 

  
  

• Source documents attached inside Epicor. The original invoice PDF is attached to the invoice header, so anyone opening it in Kinetic, including an auditor, sees the source next to the entry. 

  
  

• Plain-language errors. When Epicor rejects a request, its own message is shown to the user as-is, backed by Slack or Teams alerts and stable event codes for support. 

  
  

• Configuration, not code. Field mappings live in templates, so custom fields, company codes or GL structure are a configuration change, not a release. 

The same connector architecture powers Hyperbots' integrations with other ERPs, so improvements built for one platform tend to reach Epicor customers too.

The principle behind all of this is simple: Epicor remains your system of record, and AI handles the repetitive work around it. That is how AI complements ERP systems in practice, without replacing what your team already relies on.

Case Study: How Persimmon Technology Runs Hyperbots on On-Premise Epicor 

The best proof is a customer. Persimmon Technology runs on-premise Epicor, and Dave Sackett, VP of Finance, walked through their experience in a conversation moderated by Jace Kitchen of Hyperbots.  

Connecting an on-premise Epicor safely 

Hyperbots ships a plug-and-play connector for Epicor Kinetic, the cloud version. Persimmon uses on-premise Epicor, so the connector works through Epicor's REST v2 endpoints, or Service Connect on older builds. It gets secure read-write access to companies, sites, suppliers, parts, receipts, AP invoices, payments and any user-defined fields. 

For the on-premise setup, a lightweight agent is deployed on the Epicor app server. It opens a secure outbound HTTPS tunnel to Hyperbots, so no inbound firewall changes are needed, and it calls Epicor's APIs locally. Data never leaves the network unencrypted and stays under IT's control. 

Live in 3 to 5 weeks, with no custom code 

Sackett described a rollout of 3 to 5 weeks. Week one covers connecting to the Epicor company database, mapping fields and replaying known transactions to confirm the results match. User acceptance testing and the production cut-over follow, all without custom coding. 

How data stays in sync 

The standard cadence at Persimmon, which can be throttled in the Hyperbots dashboard by data volume: 

The daily supplier sync matters for the vendor master. A supplier added or corrected in Epicor is available to the HyperAGENTs by the next day's sync. 

What the HyperAGENTs do at Persimmon 

• Vendor master. The Vendor Management HyperAGENT validates tax IDs and bank details, automates onboarding and updates the supplier master with EFT data. 

  
  

• Invoices. The Invoice Processing HyperAGENT reads PDFs from the Outlook AP mailbox, performs a three-way match against the PO and receipt, generates GL codes and tax, and posts the AP invoice in Epicor. About 80% go straight through, and Persimmon cut AP data entry by 80%. 

  
  

• Month-end. The Accruals HyperAGENT finds PO receipts without invoices, books the journal entries and reverses them automatically when the invoice arrives. 

  
  

• Procurement. The Procurement HyperAGENT creates POs from contracts, checks budgets and rules, routes approvals in Teams and converts requisitions into POs. 

  
  

• Payments. The Payments HyperAGENT weighs early-pay discounts against the cost of capital, builds payment proposal batches, generates NACHA/SEPA files and reconciles against bank statements. 

  
  

• Tax. The Sales Tax Verification HyperAGENT checks ship-to and ship-from tax groups and part tax categories before posting. 

Accuracy, exceptions and security 

• Read-back verification. After posting an invoice, PO, journal entry or payment, the connector re-reads the record and compares every field, including amount, currency, company and posting date. Only a perfect match passes. 

  
  

• Retries and escalation. Errors such as closed fiscal periods or duplicate document numbers trigger three automatic retries. If the write still fails, the item goes to an Integration Exceptions queue and finance gets a Teams alert, so nothing fails silently. On new installations, a person validates the work before final submission. 

  
  

• Custom logic preserved. Hyperbots pulls Epicor metadata during onboarding, so custom fields and tables become mapping targets, and the AI learns from historical postings how to fill them. Business process workflows are triggered just as a human user would trigger them. 

  
  

• Security. SOC 2 Type II compliant and ISO 27001 certified, with encryption in transit and at rest. Access keys inherit Epicor's security groups with least-privilege access, and no passwords are stored. 

  
  

• Upgrades and migrations. Connectors are versioned, and dual-write mode posts to both systems until cut-over. 

Why agentic AI beat the OCR add-ons 

Sackett had used invoice OCR tools before and found them much simpler. In his words, most add-ons "just do OCR or basic workflows," while Hyperbots delivers "AI that acts": raising requisitions, posting journals, reversing accruals, reconciling payments, closing POs and verifying taxes, with an immutable audit trail for every action. His assessment is that finance-trained models can reach 99.8% accuracy and 80% productivity gains, against roughly 30% from traditional RPA and OCR tools.

For manufacturers and distributors with PO-heavy AP, Hyperbots for manufacturing shows how the same approach applies to your industry. 

Quick Reference: Supplier Tasks in Epicor 

A Clean Supplier Master Starts at Setup, Not at Cleanup

Knowing how to add a supplier in Epicor is the easy part. Open Supplier Maintenance, create the supplier ID, complete the detail, purchase point, contacts and bank information, then test the record. Looking up supplier history is just as straightforward once you use Supplier Tracker and the transaction trackers together. 

The hard part is keeping the vendor master clean as you scale: no duplicates, no missing W-9s, no unverified bank details, no inconsistent terms. Manual checklists help, but they depend on people catching every issue on every record. The Hyperbots Vendor Management HyperAGENT automates onboarding, document collection, identity checks, duplicate detection and the vendor portal, and it connects to Epicor through Epicor's own service layer. As Persimmon Technology's experience on on-premise Epicor shows, the payoff is less manual entry, a rollout measured in weeks, and a supplier master your auditors can trust. 

Ready to see it on your own Epicor data? Book a personalized Hyperbots demo and we'll show you how supplier onboarding, verification and duplicate detection work with your Epicor environment. 

Frequently Asked Questions (FAQs)

1. How do I add a supplier in Epicor Kinetic?

Open Supplier Maintenance (Purchase Management → Setup → Supplier) and click New. Enter a unique Supplier ID and the supplier's legal name. Complete the address, group, payment terms, currency, tax ID and payment method. Then add a purchase point and contacts, enter bank details for ACH/EFT, confirm the supplier is active and save. Search for existing records first to avoid creating a duplicate. 

2. How do I look up supplier history in Epicor? 
Use Supplier Tracker to see a supplier's purchase orders, receipts, invoices and payments in one place. For more detail, use the Purchase Order Tracker, AP Invoice Tracker and payment trackers. For a financial view, run AP aging and the Received but Not Invoiced report. For recurring analysis, build a dashboard or BAQ. 

3. What information do I need before creating a new supplier in Epicor?

At minimum: the legal name, remit-to and ordering addresses, a tax ID with a signed W-9 for US suppliers, payment terms, currency, bank details for electronic payments and the key contacts. Gathering it first prevents incomplete records. 

4. How do I avoid duplicate suppliers in Epicor?

Search by name variations, tax ID and address before creating a record. Standardize naming conventions and require a tax ID before activation. For higher volumes, an automated process such as the Hyperbots Vendor Management HyperAGENT compares new suppliers against your existing master and flags near-matches. 

5. Why do I need a purchase point for a supplier in Epicor?

The purchase point holds the address and contact details Epicor uses when you order from a supplier. A supplier generally can't be used on a purchase order without one, so set up at least one primary purchase point. 

6. Can Hyperbots automate supplier onboarding for Epicor?

Yes. The Vendor Management HyperAGENT automates onboarding workflows, structured vendor data upload, identity verification of tax IDs and bank details, and a self-service vendor portal. At Persimmon Technology, it validates tax IDs and bank details, automates onboarding and updates the supplier master with EFT data, while Epicor remains the system of record. 

7. Does Hyperbots work with on-premise Epicor as well as Kinetic?

Yes. Persimmon Technology runs Hyperbots on on-premise Epicor. A lightweight agent on the Epicor app server makes a secure outbound HTTPS connection to Hyperbots and calls Epicor's REST or Service Connect APIs locally, so no inbound firewall changes are required. 

8. How long does it take to implement Hyperbots with Epicor, and how are errors handled?

Persimmon's VP of Finance described a typical rollout of 3 to 5 weeks, with no custom coding: connect and map fields, replay known transactions, run user acceptance testing, then cut over. After every write, the connector re-reads the record to verify it. Failed writes retry three times, then land in an Integration Exceptions queue with a Teams alert to finance.