2-min scorecardSee what your manual month-end close is actually costing you
← All Integrations
Epicor Logo

Epicor + Go Fig

ERP Premium

Connect Epicor ERP to Go Fig for manufacturing analytics and operational intelligence.

Epicor Kinetic (formerly Epicor ERP 10) and Prophet 21 run the core operations of thousands of manufacturers and distributors, but getting data out for analysis is notoriously painful. BAQs, SSRS reports, and Data Discovery each solve a slice of the problem and leave gaps. Go Fig does not replace Epicor. It connects to the REST API v2 (Kinetic) or the P21 middleware endpoints, syncs every job, part transaction, sales order, and GL journal, reconciles it against your other systems, and loads fresh, traceable numbers into the Excel your finance team already uses, automatically, every day, without the manual pull. Celeste, Go Fig's AI analyst, can run segmentation, cost-to-produce, and working-capital analysis on top, working only on your data, with a full audit trail back to the source transaction. You keep Epicor as the system of record and stop fighting its reporting layer for the questions finance actually needs to answer. Your financial data is never pasted into a public chatbot and is never used to train an outside model.

Key facts

Supported editions
Kinetic, ERP 10.2, Prophet 21
Sync grain
PartTran and job-operation level
Multi-company
All companies and plants in one tenant
Historical backfill
Up to 7 years of closed jobs
BAQ support
Direct object sync plus optional BAQ passthrough

SOC 2 Type II ยท All integrations

What you can do with Epicor data in Go Fig

Job-level gross margin

Roll up job cost (material, labor, burden, subcontract) against invoiced revenue and map back to product line, customer, and order type. Surfaces the margin patterns Epicor's standard job-closing report hides.

Inventory and working-capital diagnostics

Analyze part transaction history, slow-moving stock, excess and obsolete reserves, and PO price variance so finance can size working-capital headroom and inform purchasing policy.

Multi-plant and multi-company consolidation

Roll up financial and operational data across Epicor companies and plants with consistent dimensions, eliminating the BAQ gymnastics required for cross-company reporting.

Data available from Epicor

Go Fig extracts and normalizes the following data from your Epicor account:

Jobs and job operations
Part transactions (PartTran)
BOMs and routings
Purchase orders and receipts
Sales orders
Invoice headers and lines
Customer and vendor masters
GL journal detail
Chart of accounts and segments
AR and AP aging
Inventory on-hand and WIP
Shipments and RMAs

How to connect Epicor

1

Provision a Go Fig service account in Epicor

Create a dedicated user (commonly 'GOFIG_API') with read access to the business objects you want exposed. Keep the account separate from human users so token rotation and audit trails stay clean. For Kinetic SaaS, confirm your deployment region (US, EU, APAC) to pick the right base URL.

2

Generate the API key and test REST v2

In Epicor Admin Console, generate an API key tied to the service account. Go Fig validates connectivity against the Ice.BO.UserFileSvc and Erp.BO.JobEntrySvc endpoints before storing the credential, which catches permission gaps early.

3

Pick companies, plants, and time window

Most Epicor installs have multiple companies and plants. Select the entities to sync and how far back to backfill. Three to seven years of closed jobs is typical for manufacturers rebuilding historical margin trends, and the entity dimension flows through every downstream table.

4

Wire up the close-week dashboards

Celeste ships starter workflows for WIP-to-GL reconciliation, job margin by customer, and inventory aging. Point them at your accounting books (Epicor GL directly, or a separate system if you run Epicor ops with QuickBooks or NetSuite for accounting) and the controller has a working close pack on day one.

Authentication: Epicor Kinetic uses the REST v2 endpoint with an API key plus a dedicated service account (basic or token auth, depending on deployment). On-premise and dedicated-tenant customers authenticate through their own base URL; Epicor SaaS customers authenticate through the regional ERP endpoint. Prophet 21 uses a service-account login against the P21 middleware.

Common Questions About Epicor Integration

Which Epicor deployments are supported?

Epicor Kinetic (cloud and on-premise), Epicor ERP 10.2, and Prophet 21 are all supported through their respective REST endpoints. On-premise customers need to expose the REST v2 endpoint through a firewall-allowlisted hostname; most IT teams set up a static outbound IP allowlist for Go Fig. Classic E9 is possible via BAQ export but is not a first-class connector.

How does Go Fig handle Epicor's BAQ layer?

Most reporting needs are met by syncing the underlying business objects directly (JobHead, PartTran, InvcHead, etc.), which is faster and more maintainable than BAQ extracts. For edge cases where a BAQ encodes business logic you want to preserve, Go Fig can call the BAQ REST endpoint and materialize the result as a table, though we usually recommend rebuilding the logic in a Go Fig workflow so it is versioned and auditable.

Can Go Fig reconcile Epicor WIP to the general ledger?

Yes. Go Fig aggregates open job cost (material issued, labor applied, burden applied, subcontract posted) and stages it against the WIP GL balance on a daily snapshot. Variances are broken down by job so the controller can drill to the specific posting, which is typically a miscoded labor transaction or an uncosted receipt that has not hit PartTran yet.

What about Epicor's multi-company structure?

Go Fig tags every row with the Epicor Company ID and Plant, and handles intercompany transactions explicitly. You can build a single consolidated P&L, an entity-specific view, or a plant-level contribution report without rewriting the source query. Consolidation eliminations are handled as a Go Fig workflow rather than baked into the connector.

How current is the Epicor data inside Go Fig?

Hourly incremental sync is the default, anchored on Epicor's ChangeLog table where available and on object timestamps otherwise. High-velocity tables like PartTran can be dialed down to 15-minute sync if operations need near-real-time inventory visibility. Full reindex runs nightly and close-week on-demand sync is available for the controller.

Industries running Epicor with Go Fig

Finance teams in these industries commonly connect Epicor so Go Fig can reconcile it and load fresh data into Excel automatically.

Ready to connect Epicor?

See how your Epicor data looks in Go Fig with a personalized demo.

Book a Demo