Last updated: October 15, 2026
ERP Staffing in Detroit, Where Two Running Totals Have to Agree
Detroit suppliers ship against a cumulative count that the automaker keeps too, and the two counts drift apart one lost receipt at a time. KORE1 recruits the SAP, Oracle, Dynamics 365, Epicor and Sage people who keep them in step.
Talk to a Detroit ERP Recruiter
KORE1 handles ERP staffing in Detroit for SAP S/4HANA, Oracle, Dynamics 365, Epicor and Sage, placing the consultants who reconcile supplier shipments with automaker receipts, and 92% of our placements remain employed a year on.
Most companies ship an order and close it. A Detroit parts supplier rarely gets an order. It gets a release, an EDI 830 forecast for the coming months and an 862 shipping schedule for the next few days, and every truck it sends adds to a running total called the cum. Every truck counts.
The automaker keeps its own cum of what it received. Same part, same plant, same model year.
When the two numbers disagree, both sides are working from a different truth.
Next week’s requirement gets calculated from the customer’s number, not yours. Payment follows receipt. So one advance ship notice that never matched a receipt can sit inside the ERP for months, quietly bending every release that follows it, until somebody sits down with both counts and finds week seven. It happens a lot.
Since 2005 KORE1 has filled ERP seats, and a Detroit search draws on the full ERP consultant staffing bench and on ERP recruiters active in over 30 metros. Michigan has plenty of people who know automotive. Fewer can explain where a cum lives in their system and who may change it. Those are the people we find.
NetSuite roles are handled separately, on the NetSuite staffing in Detroit desk, which covers the Tier 2 and Tier 3 shops and EV startups on that platform. Different buyers. This page covers SAP S/4HANA, Dynamics 365, Oracle Cloud ERP and JD Edwards, Epicor and Sage.
Every tote that leaves the dock adds to a running count the customer keeps too.
Detroit ERP Releases Run on a Total That Starts at the Model-Year Reset
An automotive release isn’t a list of orders. It’s a target. The 862 says the customer needs its cumulative receipts of part 8471-L to reach 2,200 by Thursday, and the supplier’s ERP works out how many pieces that means by subtracting what it has already shipped since the last reset.
Simple arithmetic, kept in two places.
Each truck carries an X12 856 advance ship notice with the part number, quantity, packing slip and bill of lading. The assembly plant receives against that notice, and both sides add the quantity to their own running total. Lose one receipt, key it against the wrong ASN, or post a return to the wrong part, and the totals part ways until a person agrees a corrected figure with the customer, which on a busy 2026 program can take a quarter.
SAP’s documentation for scheduling agreements works through exactly that case, two recorded cums that differ by 20 pieces, settled by entering an agreed cumulative quantity from an agreed date. The same screen handles the year change, when cumulative received and scheduled quantities usually go back to zero or to some other figure both sides accept. At our illustrative $41.30 a piece, twenty pieces is $826 on one part at one plant.
Oracle’s JD Edwards EnterpriseOne demand scheduling stores CUM shipped, CUM received and firm and planned CUM required in table F40R42, edited through program P40R12. Its 9.1 implementation guide says that screen doesn’t display ahead or behind, so a planner subtracts by hand, and a positive number means behind. The year-end reset runs as a separate batch, R40R020.
On Dynamics 365, Epicor, Sage 100 and Sage X3 the answer varies by shop. Sometimes it’s native, sometimes an EDI add-on, sometimes a spreadsheet beside the ERP that one planner in Sterling Heights maintains. Ask which before you hire. It changes the search.
The customer computes your next release from its count, so its count is the one you have to fix.
What a Missing Tote Does to a Detroit Supplier’s Count
Here is one invented part shipped to one assembly plant for ten weeks, 200 pieces to a tote, one tote per advance ship notice. The left stack is what the supplier’s ERP says it shipped since the model-year reset, and the right stack is what the automaker’s receiving system says arrived. The orange outline is the week-seven tote, which reached the dock and never reached the customer’s books.
- Wk 11 · still due
- Wk 10 · ASN 4418
- Wk 9 · ASN 4417
- Wk 8 · ASN 4416
- Wk 7 · ASN 4415
- Wk 6 · ASN 4414
- Wk 5 · ASN 4413
- Wk 4 · ASN 4412
- Wk 3 · ASN 4411
- Wk 2 · ASN 4410
- Wk 1 · ASN 4409
- Wk 11 · still due
- Wk 10 · received
- Wk 9 · received
- Wk 8 · received
- Wk 7 · no receipt
- Wk 6 · received
- Wk 5 · received
- Wk 4 · received
- Wk 3 · received
- Wk 2 · received
- Wk 1 · received
Next shipment, by the supplier’s count2,200 − 2,000 = 200 pcs
Next shipment, by the automaker’s count2,200 − 1,800 = 400 pcs
Shipped, never received on their books200 pcs · $8,260 not yet payable
Ship 200, the supplier’s number, and the customer’s system shows the part 200 behind, which in a just-in-time plant means a phone call from a material planner and sometimes a premium freight bill. Ship 400, the customer’s number, and the supplier is 200 ahead forever, carrying parts it hasn’t been paid for. Neither is right. The fix is finding ASN 4415 and getting both sides to sign one agreed cum.
Who we’d hire to find week seven
The release analyst
This person reads 830s and 862s every morning and knows which customer resets its cum on January 1 and which waits for the model-year changeover. A material planner with SAP scheduling agreement or JD Edwards demand scheduling time usually fits. Ask them how they would prove an agreed cum before entering it. Most skip the proof.
The EDI map owner
Cums break at the translator as often as at the dock, usually after a customer changes a map or a plant code. A good map owner can trace one 856 from the warehouse scan to the acknowledgment. Few can. That’s an EDI analyst who has worked automotive trading partners, and our supply chain IT recruiters run those searches.
The receivables reconciler
Short payments show up in accounts receivable weeks before anyone looks at a cum. Somebody has to tie the remittance back to the receipt, the receipt to the notice, and the notice to the tote that left the dock. A credit analyst who reads EDI is rare. Pair one with an ERP data migration specialist from our bench whenever the history has to move to a new system.
The part, ASN numbers, piece price and totals above are invented. The mechanics come from the vendors’ documentation, and real reset dates, tolerances and dispute rules come from each automaker’s supplier requirements, which change by customer and by program.
A merger between two suppliers is also a merger between two sets of open schedules.
A Detroit Supplier Merger Moves Every Open Release to a New ERP
On January 26, 2026, American Axle & Manufacturing Holdings became Dauch Corporation. Eight days later, on February 3, it closed its purchase of Dowlais Group, the British parent of GKN Automotive and GKN Powder Metallurgy. The combined driveline maker runs more than 175 locations in 24 countries from One Dauch Drive in Detroit. New name, same plants.
Big deal. Bigger ERP job. Long one, too.
Dauch’s 2025 annual report lists “risks related to integrating enterprise resource planning systems” among the hazards of the deal, and describes its integration expenses as costs for information technology infrastructure, ERP systems and consultants. Acquisition and integration charges came to $61.6 million in 2025, before the deal had even closed. That was the warm-up.
Here’s the part a cum makes harder. Every open scheduling agreement carries its running totals, and a plant moving from one system to another has to arrive on the new side with the same cum shipped that the customer’s receiving system expects, on a cutover date both sides know about.
Miss it by one in-transit truck and the new system opens the year a tote out of step. Nobody notices until the first release lands. Then everybody does.
Supplier consolidation keeps that work coming in Michigan, merger or not. Steady demand. The hire that saves a cutover is a plant systems lead with manufacturing ERP time, someone who has moved open releases between systems and reconciled the first week afterward with the customer’s planners. Plant engineers working beside that lead are recruited by our automotive engineering staffing practice and the Detroit engineering staffing team, and the systems leads through manufacturing ERP staffing.
Detroit ERP Talent From Dearborn to Auburn Hills
Federal wage survey data for May 2025 show 7,150 computer systems analysts and 5,920 logisticians at work in the Detroit-Warren-Dearborn metro, most of them within a half-hour of an assembly plant. Districts marked with a tote keep their hardest records in pieces, not dollars. Each orange tag names our slowest search there.
Detroit plant managers seldom start an interview by listing modules. Not here. They ask something harder. When did your customer last reset the cum, and what did you check before you let the new year start at zero?
Detroit and Dearborn
Downtown · New Center · Dearborn · the Rouge
Ford runs its business from Dearborn, Dauch runs a 24-country driveline company from One Dauch Drive, and the warehouses, sequencing centers and logistics providers that feed the assembly plants pack in between the Lodge, the Southfield Freeway and I-94. Lots of trucks, lots of notices. Constant traffic. ERP and finance systems people for these offices mostly reach us through our Detroit IT staffing team.
Hardest recordsSequenced deliveries that ship by the vehicle, not by the tote
Warren and Sterling Heights
Warren · Sterling Heights · Mound Road · Van Dyke
GM’s Global Technical Center anchors Warren, Stellantis builds the Ram 1500 at Sterling Heights Assembly, and stampers, molders and tool shops line Mound Road and Van Dyke. Tier 2 country. Busy roads. Plant and manufacturing engineers here come through our Detroit staffing agency.
Hardest recordsCums for one part shipped to three customers on three reset dates
Troy and Auburn Hills
Auburn Hills · Troy · Rochester Hills · I-75
Stellantis runs North America from Auburn Hills, a few miles from the BorgWarner and PHINIA headquarters, and Troy fills the office parks along Big Beaver Road. Engineering-heavy. Tier 1 programs with dozens of customer plants. Cost and plant accountants in these towns usually arrive via our Detroit accounting staffing desk.
Hardest recordsProgram costs split across platforms that launch in different years
Novi, Northville and Livonia
Novi · Northville · Livonia · Plymouth
Stoneridge keeps its headquarters in Novi, Cooper-Standard keeps its headquarters in Northville, and its latest annual report names ERP standardization in its manufacturing plans. Lots of suppliers, lots of plants on lots of systems. Plenty of migrations. Reporting and analytics hires along I-275 come through our Detroit data staffing recruiters.
Hardest recordsThe same part number on two ERPs while plants migrate one at a time
Southfield and Birmingham
Southfield · Birmingham · Bloomfield Hills · Telegraph Road
Lear builds seats and wiring from a Southfield headquarters, and OneStream, whose finance software pulls data from ERP systems across a company, is based a short drive north in Birmingham. Consolidation runs through here. So do the people who close the month across six ledgers. Wider automotive systems hiring sits with our automotive IT staffing team.
Hardest recordsA month-end close across several ERPs in several currencies
Ann Arbor, Flint, Lansing, Monroe and Toledo are covered by this desk as well. One team, one phone list.
What the customer recorded as received is usually what gets paid.
For Detroit ERP Teams, the Receivable Clock Starts at the Customer’s Dock
Dauch’s annual report says most of its receivables are owed by automakers and are generally due within approximately 50 days of the date customers receive the product. Received, not shipped. In 2025 GM accounted for about 44% of its net sales, Ford 15% and Stellantis 13%, so three receiving systems decide when most of that cash arrives.
A tote the customer never received isn’t late revenue. It’s disputed revenue.
Finance sees it differently. On a $41.30 part, the week-seven tote in the drawing is an $8,260 short payment on an X12 820 remittance, an aging line nobody can explain, or a deduction coded to the wrong reason. Receivables spots it first.
The proof sits elsewhere, in the 856 the shipping office sent, the 824 application advice the customer may have returned, and the dock scan from week seven. That handoff, three departments and two systems, is where we see Detroit ERP teams lose the most time.
The strongest finance hires here can follow an 820 back through the receipt to the 856. Not many can. They know where SAP or Oracle stores the customer’s receipt reference, and how an agreed cum changes the next invoice.
The larger Tier 1 ledgers draw on our SAP FICO consultant staffing team, while our Dynamics 365 recruiters and the SAP recruiters on the desk begin searches before the year change rather than after. Smaller shops billing a handful of customer plants tend to run Business Central, and our Business Central consultants cover them.
Detroit ERP Engagements, From One Model Year to Permanent
Contract
A launch, a year change or a plant cutover with a hard end is a job for contract staffing, and the consultant stays on KORE1’s payroll.
Contract-to-hire
Bring in a release analyst for one model year, then hire them outright if the counts stay clean.
Direct hire
Cums, resets and customer disputes need an owner on staff, found by direct hire recruiting.
Statement of work
Reconciling a year of notices against receipts is finite work that suits a team paid per deliverable.
Dates first. Detroit calls usually arrive with a date attached, a program launch, a merger cutover or the model-year changeover. We work backward from it, and once the new system is running we cover the first weeks with go-live hypercare staffing.
Budgets come next. Our 2026 hourly rates for ERP consultants, along with the ERP implementation checklist with costs cover most of what a finance team asks for.
An agreed cum is a one-line edit that rewrites every release after it. Small edit, long reach. Colin Boothe’s firm, Foretopia, requires a second person, never the one who made a change, to review it before it goes in.
Hold a cum correction to that rule and a mistyped 2,000 gets caught before the next 862 arrives. Two people, one number. An ERP project manager who builds that check into the cutover plan earns the fee.
The same ERP desk recruits across the Great Lakes in Chicago and Minneapolis, and east and south in Philadelphia, New York and Atlanta. One desk. When a cutover needs extra hands inside an existing team, ERP staff augmentation adds them, and our ERP program team desk builds the full crew when there’s no team yet.
Common Questions
Apart from NetSuite, what ERP systems does your Detroit desk cover?
S/4HANA and ECC on SAP, Oracle Cloud ERP and JD Edwards, Dynamics 365 and Business Central, Epicor, and Sage 100, X3 and Intacct. NetSuite roles go to our Detroit NetSuite desk. Roles we fill include solution architects, functional and technical leads, EDI and release analysts, developers and project leads.
What is a cum in automotive EDI?
A running total. The cum is the cumulative quantity of a part shipped or received since the last agreed reset, and automotive releases such as the 830 and 862 are calculated against it. Supplier and customer each keep one, and they have to match. Both of them.
What do Detroit ERP consultants get paid?
$103,670 is the May 2025 median for the Detroit-Warren-Dearborn metro’s computer systems analysts in federal OEWS data, a little below the national $105,850. Contract rates sit well above that. Specialty pays. Automotive EDI and SAP sales scheduling experience push pay up faster than years do.
What happens to the cum at the model-year changeover?
It usually goes back to zero, or to another figure both sides agree. Some customers reset on January 1, others at the model-year changeover, and the supplier and customer need the same reset date. Open shipments in transit on that date are where most new-year mismatches start. Watch the trucks.
How quickly can you fill a Detroit ERP role?
Seventeen days. That’s the mean across our IT searches, measured from the day the req opens to the day an offer is signed. Many Detroit ERP roles close faster. Release analysts with automotive EDI and cutover leads who have moved open schedules between systems often take longer, since every supplier near the same launch is calling the same people.
Do you recruit outside the city, in Ann Arbor or Toledo?
Yes. Our Detroit searches run across Oakland, Macomb, Wayne and Washtenaw counties, north to Flint and Lansing and south to Monroe and Toledo. Plenty of plant and systems people already drive an hour each way, so one search usually reaches most of southeast Michigan.
Should a supplier hire its cum owner or contract one?
Hire, most of the time. A contractor is a good fit for a one-time reconciliation or a cutover. Releases, resets and customer disputes never stop, though, and the person who answers for them should still be around at the next changeover. Continuity matters here.
Put Both Counts Back in Step Before the Next 862
Send us the platform name and the part numbers whose counts keep drifting. Most of the time one conversation scopes the work, and you leave the call holding a written search plan, Detroit pay figures and a named recruiter responsible for the result. No slides.
Call the Detroit ERP Desk