Chapter 11 of 50
Chapter 11: The Phantom Expense
907 words
Coffee steamed in the dim glow of Elara's monitor. Midnight had long passed, but the financial reports Julian had handed her were a labyrinth she couldn't abandon.
Pages upon pages of numbers blurred before her eyes, an intricate web of expenditures across Vance Corp's various luxury properties. Julian's warning echoed in her mind: *"Expect deliberate obfuscation."*
He wasn't wrong. Data points were scattered, expenses categorized under vague headings like 'miscellaneous operational costs' or 'general vendor services.' It was like trying to find a specific grain of sand on a vast beach.
Hours melted away. Elara focused on the highest-value outliers, cross-referencing them against prior quarters. The discrepancies were glaring, not just minor fluctuations but significant spikes that defied logical explanation.
She marked each one, a growing list of anomalies. Her fingers flew across the keyboard, pulling up historical trends, looking for patterns that might justify the sudden increase.
Nothing. No major renovations reported. No new marketing campaigns that accounted for the figures. Just a sudden, inexplicable surge in spending.
Sending out initial queries, she targeted the relevant department heads. Her emails were polite, direct, requesting clarification on specific line items.
Replies trickled in. Some were boilerplate, citing 'increased operational demands.' Others were vague, promising to 'look into it' without ever following up.
A familiar knot tightened in her stomach. This wasn't just inefficiency. This felt deliberate, orchestrated.
Early morning light filtered through the blinds as Elara shifted her strategy. Direct confrontation was next. She began scheduling calls, starting with the property manager of the Miami Beach resort, which showed some of the most consistent overspending.
"Good morning, Mr. Davies," Elara began, her voice crisp despite the lack of sleep. "I'm calling about the Q3 expenditure report for your property."
Davies's tone was immediately defensive. "Everything is in order, Ms. Vance. We run a tight ship here."
"I'm sure you do," she countered smoothly. "However, I've noticed a significant uptick in your 'general maintenance' budget. Can you elaborate on what specific projects contributed to that surge?"
He stammered, citing 'routine wear and tear' and 'unexpected repairs.' He couldn't provide specific vendor names or project codes.
"I'll need a detailed breakdown, Mr. Davies, including all invoices for any expense over five thousand dollars," Elara stated, her voice firm. "Please send them to me by end of day."
Davies grumbled, promising to comply, but the evasiveness was palpable. This pattern repeated with the heads of several other departments across different properties: vague answers, promises of future documentation, and an underlying tone of annoyance.
One finance director even suggested Elara was 'overstepping,' implying her IT role didn't extend to financial audits. Elara simply thanked him for his 'feedback' and reiterated her request for documentation.
Ignoring the veiled resistance, Elara pressed on. She noticed a peculiar recurring theme. Many of the 'miscellaneous' charges, particularly those exceeding ten thousand dollars, referenced services that seemed almost generic.
'Consulting fees,' 'strategic planning,' 'infrastructure upgrades' – the descriptions were broad enough to cover almost anything, yet specific details were always missing.
She started isolating these generic expenses. A pattern emerged. Many of these payments, originating from different properties and seemingly unrelated departments, were routed through a single, unfamiliar vendor.
The name caught her eye: 'Apex Solutions Group.' She'd never heard of them. No official vendor code existed in Vance Corp's primary procurement system.
Pulling up the physical (or digitally scanned) invoices associated with 'Apex Solutions Group' was a challenge. They were filed haphazardly, sometimes under different property codes, sometimes buried deep within quarterly reports.
Finally, she pieced together a collection of them. Each invoice from Apex Solutions Group was remarkably similar in format, though the dates and amounts varied.
And the amounts. They were always rounded figures, often exactly $25,000, $50,000, or $100,000. For 'consulting' or 'system optimization' services that lacked any concrete deliverables.
Comparing the prices to industry standards, her jaw tightened. The figures were inflated by at least 30%, sometimes more. A $50,000 charge for a 'network review' that typically cost $30,000.
The company address listed on the invoices was a PO box in a nondescript business park, miles from any Vance Corp property. A quick online search for 'Apex Solutions Group' yielded nothing but a shell company registration, no website, no listed services.
This wasn't an obscure legitimate vendor. This was a phantom. A front.
Elara stared at the screen, the culmination of her exhaustive search laid bare. Hundreds of thousands of dollars, siphoned off through a single, fake entity, spread across multiple properties, cleverly disguised within legitimate-sounding categories.
Julian had suspected deliberate discrepancies. What Elara found was a sophisticated, systematic embezzlement scheme, hiding in plain sight.
The scale of it was staggering. And the precision of its execution suggested someone high up knew exactly what they were doing.
A shiver ran down her spine. She had just stumbled into a hornet's nest far more dangerous than a mere IT glitch. This was big. And whoever was behind it wouldn't want it exposed.
Her phone buzzed. Julian's name flashed on the screen. She took a deep breath, the weight of her discovery pressing down on her.
"Julian," she answered, her voice steady. "I think I found your phantom expense. And it's worse than we thought."