ERP & Enterprise

ERP Roundup: LKQ Puts $95 Million of Lost Revenue on an ERP Disruption, and BC29 Deletes a Page Microsoft's Docs Still Describe

Sharif George7 min read

A listed company putting a dollar figure on an ERP disruption, a Business Central page that no longer exists while its documentation still calls it merely obsolete, an AL change that makes interfaces safer to extend and harder to reason about, and a referral clock cut to five days. Four stories from the past seven days.

1. LKQ puts a number on an ERP disruption: $95 million of revenue

LKQ Corporation, the vehicle parts distributor, published preliminary third-quarter results on 23 October that it said primarily reflected Europe segment underperformance, including — in the company's own words — "operational disruptions associated with the ERP implementation in Germany". Europe parts and services organic revenue was down 9.8% and the segment EBITDA margin was given as 4.1% to 5.1% against 10.0%. LKQ withdrew its full-year guidance, said its chief executive and the president of LKQ Europe had both departed that day, and engaged Alvarez & Marsal to advise on European operations.

The quantification came six days later. On the 29 October earnings call, CFO Rick Galloway said "revenue loss in the region due to the ERP was approximately $95 million" and that the disruption in Germany "reduced EBITDA by approximately $43 million in the quarter".

What LKQ has not said is which software, which integrator, or what specifically went wrong, and no published reporting we could find establishes any of it. What is on the record is narrow and still unusual: a listed company has attributed a quarter of revenue and margin damage in one country to ERP-related disruption, and put a number on it.

What it means for testing

The useful thing here is not a diagnosis, it is the unit. "Operational disruption" in a distribution business means order capture, picking, despatch and invoicing not working at the rate the business runs at — a failure mode a feature-by-feature acceptance pass is poor at finding, because every function passes on its own. What finds it is volume: the same processes at realistic daily quantities, run by the people who will run them, with a measured throughput number rather than a tick. Exit criteria with no figure for orders per hour cannot distinguish software that works from software that works slowly enough to cost a quarter. Birmingham made the point from the public sector: the go-live decision sets the cost, the number lands years later.

2. BC29 removed the Custom Report Layouts page. The docs still call it "being phased out".

Yun Zhu reported on 30 October that the Custom Report Layouts page — the legacy Word and RDLC mechanism inherited from Dynamics NAV, which survived as far as BC 28.5 — is gone in BC29. His instruction is unambiguous: migrate everything to Report Layouts before upgrading.

The Microsoft Learn page gives the softer version. Titled "(Obsolete) Create and modify custom report layouts", it says the feature "is being phased out" and points at user-defined layouts, naming no version, no deprecation date and no removal date; its last-updated stamp predates BC29. Obsolete and absent are not the same word, and only one requires action this month — the same documentation lag Monday's post found in the Fabric mirroring preview, where two Microsoft pages gave two different dates.

What it means for testing

Reports are the part of an ERP nobody owns and everybody uses, so they are chronically under-tested — and this is a pre-upgrade task, not a post-upgrade defect. The deliverable is an inventory before the upgrade window: every custom layout, who uses it, whether an equivalent exists, and one comparison of old output against new on real data for each that matters. A layout that renders is not a layout that is correct — totals, grouping and page breaks are where they diverge. Like any BC29 change with no screen to click, the test is a comparison, and someone signs it.

3. AL interfaces get default method bodies, and a new way to break dependents

Zhu also documented on 26 October that AL interfaces in BC29 can carry method bodies acting as default implementations, against roadmap item 573352 and requiring runtime 18.0 or later; BC 28.5 rejected this outright with compiler error AL0413. An implementing codeunit can inherit a default or override it, and a new [RequiredPending] attribute marks a default that becomes mandatory in a stated future version. Two AppSourceCop rules police the lifecycle: AS0148 flags a default body removed without that step, and AS0149 warns when a change alters the runtime identifier, which can break dependent extensions until recompiled. The upgrade story is better for it — a publisher can extend an interface without forcing every implementor to ship a change — with one documented edge: a default is reached through an interface variable, and Zhu reports that calling one on a codeunit variable fails.

What it means for testing

An inherited default is behaviour nobody on your project wrote or reviewed, arriving in a build that compiles clean. Two things belong in the BC29 regression pass. First, for every interface you implement, establish which methods are yours and which are inherited, because an inherited one changes when the publisher changes it — AS0149 is the warning that it has. Second, if your test codeunits implement production interfaces, check how defaults resolve rather than assuming: Zhu is explicit that the two variable types behave differently, and does not cover test code.

4. The SMB referral window drops from fourteen days to five

A Partner Center announcement dated 28 October states that from 2 November 2026, partners have five calendar days to accept or reject SMB referrals from Microsoft, down from up to fourteen, "to increase referral velocity". A referral not actioned in time expires, and Microsoft says "expired referrals can be rerouted and shared with another partner". Corporate and Enterprise referrals keep the fourteen-day window.

Five calendar days, not working days: a referral arriving on a Wednesday afternoon expires on Monday. In a practice where whoever qualifies an inbound lead is usually also billing on a project, that is a staffing question dressed as a process change.

What it means for testing

Indirectly but reliably: faster qualification in front of unchanged delivery capacity pushes the compression to the back of the project, and the back of the project is acceptance. The cycle that gives way is always the one whose stakeholders are part-time and whose deliverable is a signature. The protection is structural — acceptance scope fixed to the contracted requirements at the start, so what gets cut is a signed decision rather than coverage that quietly did not happen.

The through-line: the number arrives long after the decision

LKQ's $95 million is a Q3 figure for decisions taken well before Q3. The report layouts page was marked obsolete years ago and became a blocking migration this month. An inherited interface default is a publisher's choice your build absorbs silently. A five-day referral clock lands on an acceptance phase eighteen months out. The cost is realised at a distance from the decision that caused it, and closing that distance is what structured acceptance is for: a dated record of who accepted what, on what evidence — most of what structured UAT on Business Central buys you, and why sign-off is a dated decision, not an email.

→LKQ: about $95m of revenue and $43m of EBITDA in one quarter. Put a throughput number in your UAT exit criteria.
→Custom Report Layouts is gone in BC29. Migrate before the upgrade and compare old output to new on real data.
→AL interfaces can carry default bodies. Know which methods you implement and which you inherit; watch AS0149.
→SMB referrals expire after five calendar days from 2 November. Name an owner before one lapses over a weekend.

Free ERP UAT checklist (Excel)

A structured workbook covering the full UAT cycle: pre-UAT preparation tasks, test execution tracking, an issue log with severity guide, and post-UAT wrap-up. Built from real ERP implementations.

No spam. We will occasionally send UAT and ERP implementation resources. Unsubscribe any time.

Sources and further reading

Free Plan Available

A Quarter's Damage Starts As A Sign-Off Nobody Can Produce

LogicHive keeps the acceptance layer where the pressure cannot quietly remove it: structured test cases tied to requirements, named business owners, linked defect tracking, and sign-off built from real execution data rather than a screenshot of a passing build. When a layout migration, an inherited interface default or a go-live decision turns into a number months later, the record of who accepted what, on what evidence, is already there. The free plan runs a real project end to end.

Start FreeView Pricing

Written by Sharif George

LogicHive Frontman

Sharif is the frontman for LogicHive. He writes the ERP news roundups and the Business Central release coverage, following each Microsoft, SAP and Oracle change through to what it means for regression scope and acceptance testing on live implementation projects.

View all articles by Sharif George

Related reading

  • ERP & Enterprise

    Business Central's Fabric Mirror Is a Second Set of Numbers. Someone Has to Sign Off Both.

    Microsoft is building continuous replication of Business Central tables into Microsoft Fabric. The documentation says production-ready preview in October 2026; roadmap entry RM574126, published on 20 October, says preview in November and general availability in April 2027. The limitations link points at the Azure SQL mirroring path rather than the open mirroring one Business Central actually uses, so which columns arrive is still an open question. What that means for reporting UAT: a read-only copy cannot corrupt the ledger, but it can disagree with it, and stale data renders exactly like current data.

    26 October 2026 · 5 min read

  • ERP & Enterprise

    ERP Roundup: The BC30 Preview Environment Deletes Itself, and Microsoft Stops Selling AI Builder Capacity in Nine Days

    The Business Central 2027 release wave 1 early access preview is open, and Microsoft documents a sandbox that force-updates every Sunday, deletes itself if that update fails, and cannot be recovered. Alongside it: a cancel action for scheduled PTE installs that no Microsoft documentation describes, an AI Builder capacity add-on end of sale nine days out, and a 28% larger SAP cloud backlog that is really a 2027 delivery queue. Four stories, four calendars, none of them yours.

    23 October 2026 · 7 min read

  • ERP & Enterprise

    AI Found the Defects Faster Than Anyone Could Fix Them. PostgreSQL Cut the Features. ERP Projects Cut the Testing.

    PostgreSQL 19 reached RC1 on 15 October with about 8 to 10 significant features reverted, because LLM-assisted review produced defect reports faster than committers could close them. The widely repeated "forty bugs" figure was an illustration of workload, not a count. The transferable point for ERP delivery: detection capacity now scales with compute, disposition capacity does not, and when a cycle runs out of calendar it is usually the testing that gets cut rather than the scope or the date.

    19 October 2026 · 6 min read