Guides · Epicor job cost report export

How to export job costs from Epicor Kinetic

Get a clean, one-row-per-job Epicor Kinetic export with estimated and actual costs, ready for margin analysis in Excel or MarginGuard, in about ten minutes.

By the MarginGuard team · FactoryEdgeAI · Last reviewed

The problem

Epicor Kinetic already records what each job was estimated to cost and what it actually cost. Getting that into a form you can analyze across all jobs is where shops lose time: picking the right report, getting one row per job instead of one row per operation, and making sure revenue, estimated cost, and actual cost all come through. Multi-assembly jobs are the trap: JobAsmbl returns one row per assembly, so an unsummarized BAQ repeats JobNum. Either group by JobNum in the BAQ or export only the top assembly (AssemblySeq 0) if your costs roll up there.

Ready to measure this on your jobs?

What to measure

A usable export has one row per job with at minimum: job number, customer, revenue, and estimated and actual cost (totals or by category). With those, you can calculate margin erosion per job (estimated margin minus actual margin) and see which cost categories drove it. The table below shows exactly which Epicor Kinetic columns to include.

How MarginGuard helps

Upload the export to MarginGuard and pick Epicor Kinetic as the source. The Epicor Kinetic preset recognizes the column names below, shows a readiness score before anything is saved, and blocks unsafe multi-row files instead of guessing. No API, ERP credentials, or IT project is needed.

Next step: sign up, load the demo, or compare plans.

How to get started

  1. Step 1
    Create or open a job-level BAQ

    In BAQ Designer, start from JobHead and join Customer and Part. Add the JobAsmbl TLE* (estimated) and TLA* (actual) cost fields. If you don't have BAQ access, a Job Costing dashboard grid works too.

  2. Step 2
    Summarize to one row per JobNum

    Group by JobNum and sum the assembly-level TLE*/TLA* fields so multi-assembly jobs don't repeat. Operation- or material-level rows will be blocked as unsafe to sum.

  3. Step 3
    Export to Excel

    Run the BAQ, then right-click the grid (or use Actions) → Export to Excel. Save as XLSX or CSV.

  4. Step 4
    Upload to MarginGuard

    Integrations → Import → Epicor → upload. JobNum, PartNum, and the TLE*/TLA* field names are recognized automatically.

Common mistakes

Multi-assembly jobs are the trap: JobAsmbl returns one row per assembly, so an unsummarized BAQ repeats JobNum. Either group by JobNum in the BAQ or export only the top assembly (AssemblySeq 0) if your costs roll up there.

Other ERP export guides

Using a different system? See the JobBOSS² and E2 Shop System guides, or the general CSV import guide for any ERP or spreadsheet.

Epicor Kinetic columns to include
Epicor Kinetic columnJob-cost fieldNotes
JobNumJob NumberRequired. Summarize the BAQ to one row per JobNum.
CustID / Customer NameCustomerRequired.
ExtPrice (or DocUnitPrice × ProdQty)Quoted revenue—
TLELaborCost · TLESetupCost · TLEBurdenCost · TLEMaterialCost · TLESubcontractCostEstimated cost by categoryTLE = this level estimated.
TLALaborCost · TLASetupCost · TLABurdenCost · TLAMaterialCost · TLASubcontractCostActual cost by categoryTLA = this level actual.
TLEProdHours · TLAProdHoursLabor hoursOptional.
ReqDueDate · CloseDate · JobClosedDates · statusOptional.
Worked example: JobNum 10421 from the Epicor BAQ sample
LineEstimatedActualVariance
Labor$2,800$3,100$300
Setup$600$650$50
Machine / burden$1,900$2,100$200
Material$3,200$3,350$150
Outside processing$400$420$20
Total cost$8,900$9,620$720
Margin$3,600 (28.8%)$2,880 (23.0%)−$720 erosion

Revenue $12,500. Positive variance = cost overrun. Margin erosion = estimated margin − actual margin.

Downloads

FAQ

What do TLE and TLA mean in Epicor?
TLE fields are “this level estimated” costs and TLA fields are “this level actual” costs on JobAsmbl. Together they give estimate vs actual by labor, setup, burden, material, and subcontract.
Do I need BAQ Designer access?
It's the cleanest path. Without it, export a Job Costing dashboard grid that has one row per job, or ask your Epicor admin for a job-level BAQ.
Does this work with Epicor Kinetic cloud and on-prem?
Yes. Both support Export to Excel from a BAQ or dashboard grid, and that's all MarginGuard needs.
Can I include multi-level assemblies?
Yes, as long as the export is summarized to one row per JobNum, or limited to the top assembly where costs roll up.

Still deciding? Start with a CSV import or the demo shop.

Related MarginGuard pages

Related FactoryEdgeAI products

MarginGuard is the profitability layer. Pair it with the rest of the FactoryEdgeAI family when you need alarms or machine monitoring too.

  • MarginGuard

    Job-level profitability intelligence: estimate vs actual, margin alerts, and opportunity tracking beside your ERP.

  • FactoryEdgeAI

    CNC alarm lookup, troubleshooting guides, and shop-floor knowledge for machinists and programmers.

  • Machine Monitor

    MTConnect machine monitoring for utilization and status — pair with MarginGuard when you want contribution, not just busy spindles.

Have your Epicor Kinetic export? See every job's margin in minutes.

Create a free account and upload the file. Nothing is saved until you confirm the readiness check.

Keep your ERP. CSV import today. Create an account or sign in.

Ready to find margin leaks?

Sign up free, explore the demo, or compare plans — keep your ERP either way.