Finance Executive Lists ‘Survived Three ERP Migrations’ Under Military Service

SATIRE — In an escalation of the résumé arms race, finance executive Randall Voss has listed “Survived Three ERP Migrations” directly below “Military Service,” explaining that the distinction had become largely administrative. “One was overseas,” Voss said, referring not to a deployment but to a Workday implementation that required a 6:00 a.m. status call with consultants in three time zones and one integration lead who existed only as a calendar placeholder.

The new section, titled Service Record, includes dates, operating theaters, systems involved, and a short description of decorations received. These include the Bronze PivotTable, the Distinguished Service Cross-Functional Alignment Medal, and a commendation for maintaining month-end close during a cutover in which accounts payable briefly ceased to recognize the existence of vendors.

A résumé format for the modern finance leader

Voss’s résumé now treats each ERP migration as a campaign. The first, Oracle E-Business Suite to NetSuite, is described as a “rapid extraction under incomplete master-data conditions.” The second, NetSuite to SAP S/4HANA, appears as “enterprise-scale stabilization activity amid legacy-reporting insurgency.” The third is simply marked “classified,” which sources close to the matter say means the final balance sheet still has a suspense account with a name nobody is permitted to change.

The executive summary begins: “Finance leader with 18 years of progressively responsible experience in controllership, planning, and post-traumatic chart-of-accounts reconstruction.” It then notes fluency in GAAP, board reporting, cash forecasting, and “calmly explaining to a chief executive why historical results cannot be compared to prior historical results until further notice.”

Hiring teams have welcomed the format because it eliminates the tedious work of interpreting ordinary language. “When a candidate says they led an ERP implementation, that could mean anything,” said a fictional vice president of talent at Meridian Spreadsheet & Defense Systems. “When they say they survived it, we know they personally watched a revenue-recognition workflow route invoices into an inactive legal entity for eleven business days.”

How the interview process has adapted

The interview screen has changed accordingly. Candidates are no longer asked merely whether they have ERP experience. They are asked to identify, from a list of mild physical symptoms, which were caused by conversion stress, which by an auditor’s PBC list, and which by discovering that the implementation partner had mapped “customer” to “employee” in one region.

At the panel stage, the hiring manager presents a case study: It is Day 2 after go-live. The controller cannot run a trial balance. The CFO has promised the board “real-time reporting.” Payroll is scheduled tomorrow. The procurement team has discovered that all purchase orders now require approval from a person named Test User 04. The candidate has 20 minutes to explain what they would prioritize and 40 minutes to avoid saying “we need to pause.”

• For staff and senior accountants: “Describe a reconciliation you rebuilt after a migration, without naming the spreadsheet tab after your feelings.”
• For accounting managers: “Which controls would you preserve, redesign, or quietly hide in a drawer until the auditors leave?”
• For FP&A candidates: “How would you forecast when the new planning system contains eight versions of actuals, all equally official?”
• For controllers: “At what point do you tell leadership that go-live is not a morale event?”
• For finance systems leaders: “Please walk us through a time you prevented a consulting workstream from creating a ninth approval hierarchy.”

The compensation question

Voss’s résumé also lists expected compensation in a new format: base salary, annual bonus, equity, and a modest hardship differential for every legacy subledger that must remain operational “for historical purposes.” He has requested one additional week of vacation for each major chart-of-accounts redesign and the contractual right to decline any meeting titled “quick question on the new system.”

The company has countered with a standard offer: market base, a target bonus contingent on metrics that will be redefined after the first planning cycle, and an equity grant valued using an internal methodology last updated when the company still had a fax machine. The offer also includes the phrase “high visibility,” which Voss correctly recognizes as a warning that any data issue will become visible to senior leadership before the finance team has located the source file.

Contract work earns a campaign ribbon

Recruiters say this framing is especially useful for interim and contract candidates. A six-month ERP stabilization engagement can otherwise sound like an awkward career gap to someone who has never spent four consecutive closes reconciling an opening balance conversion. Under the service-record model, it becomes a clearly bounded assignment: entered during active operational disruption, established control over key reporting terrain, departed before the organization reopened scope decisions from the prior fiscal year.

This is not merely branding. A permanent role after a migration may mean building the controls, team habits, reporting logic, and close calendar that were deferred while everyone focused on making the system technically capable of issuing an invoice. A contract role may mean fixing a defined portion of that work without agreeing to own every unresolved design choice for the next five years. The title alone will not tell you which one it is; the scope, decision rights, timeline, and who owns the backlog will.

A final distinction worth preserving

Voss has not actually equated ERP work with military service, despite the résumé layout, the campaign ribbons, and the request for a ceremonial flag to be folded at the end of UAT. The joke works because finance teams know the underlying truth: an ERP migration is not a software project that happens to touch accounting. It is an operating-model change, and the people hired around it are being hired to make that change usable after the launch presentation is over.