task-gdpval-1

PHASE 1: Reference file survey, compilation and cleaning Purpose: Establish the full breadth of available data and prevent incomplete data compilation from contaminating revenue, inventory, or controls conclusions. Rationale: We complete compilation before any calculation because several key accounting conclusions depend on judgmental evidence that sits outside the main xl files shared, and missing that evidence would silently bias the numbers. Steps: 1.1 We open the full Meridian Health folder and inventory every file, separating transactional extracts, invoices, email evidence, the SOP operations manual, and access-control logs, so that no judgmental source is overlooked once we begin calculating. 1.2 We load Order_Log, Shipping Log, Inventory_Master, and Vendor Access Log into our working file, keeping the raw extracts untouched on their own tabs and doing all of our work on controlled working tabs. [output: Meridian_Q4_Workings.xlsx] 1.3 We remove the 4 exact-duplicate inventory-master rows and carry forward the resulting 600 unique lots as our gross warehouse population. [rubric 1.1] 1.4 We screen the order and shipment data for orphan shipments, fully unshipped Q4 orders, multi-line shipments, and over-shipments before recognizing any revenue, so these exceptions are handled deliberately rather than by accident. 1.5 We read all 13 email images and the Inventory Operations Manual in full, because the cut-off overrides, valuation evidence, and reserve policy we will rely on later are only found there. [rubric 1.7] PHASE 2: Revenue recognition and cut-off Purpose: Calculate Q4 2025 recognized revenue and revenue deferred to Q1 2026 using shipment-line evidence and shipping-term cut-off rules. Rationale: We recognize revenue on transfer of control, not on invoice date or order value. We work at shipment-line level because a single order can have multiple shipments with different delivery dates and therefore different recognition outcomes, and we let specific contrary evidence override general conventions. Steps: 2.1 We join the order and shipment logs at shipment-line level rather than at order-header level, since recognizing a whole order at once would misstate orders that ship in parts across the cut-off. 2.2 We compute line revenue as quantity shipped times unit price, never order value, and we recognize FOB Shipping Point lines at the ship date because control passes to the customer at shipment. 2.3 We recognize FOB Destination lines only at the delivery date, because under those terms control does not pass until the goods are delivered. 2.4 Where a delivery date is not stated, we impute it using the company's 30-day delivery-window convention; this lets us recognize the October invoice-only FOB Destination items within Q4, but we treat the Dec-30 logistics email as more specific evidence that overrides the convention for Dec-29 shipments. [rubric 2.10] 2.5 We act on the Dec-30 logistics breakdown email by moving the Dec-29 FOB Destination deliveries into January, including SHP-70069, which we defer to Q1 even though the system shows a 31-Dec delivery. [rubric 2.6, 2.7] 2.6 We split ORD-2025-20142 by shipment rather than treating it as wholly recognized or wholly deferred: the shipment delivered before year-end is Q4 (1,329 units = $246,130.80) and the Jan-1 shipment is deferred (506 units = $93,711.20). [rubric 2.3, 2.4] 2.7 We do not drop transactions that have invoice or shipment support but no order-log value; instead we capture them in a separate invoice-only exception layer, recognizing the four supported sales INV-S-1001 to INV-S-1004 as Q4 revenue ($542,283.74) and excluding the unsupported orphan shipment ORD-2025-20503. [rubric 2.8, 1.2] 2.8 We foot our final Q4 recognized revenue to $120,047,883.16 and revenue deferred to Q1 2026 to $4,492,129.21, confirming each total agrees with the sum of its tagged lines. [rubric 2.11-2.14] [output: Meridian_Q4_Workings.xlsx] PHASE 3: Inventory valuation and cut-off Purpose: Determine Meridian-owned inventory at Dec. 31, 2025 and apply lower-of-cost/NRV, expiry, recall, and ownership adjustments. Rationale: We let ownership, not physical location, govern what is included, so we keep revenue cut-off and inventory ownership aligned (a Dec-29 FOB Destination unit deferred for revenue is still our inventory at year-end). We are careful not to over-correct lot overlaps, and we do not lean on a single post-merger extract that we know is incomplete. Steps: 3.1 We start from the post-deduplication inventory-master gross warehouse value of $313,494,104.52. [rubric 3.1] 3.2 We match inventory against the order and shipment logs and remove only the 3 full-lot sold-but-unrelieved errors where control has passed (LOT-10076/10365/10450 = -$767,576.31); we deliberately leave partially shipped lots in place, because their remaining quantity is still valid inventory. [rubric 3.17] 3.3 We add back the 12 in-transit FOB Destination lines at cost (+$2,432,598.30) and SHP-70069 (+$28,797.00, overriding its 31-Dec date) where they are not already in the master, because goods whose revenue we deferred under FOB Destination remain our inventory at year-end. [rubric 3.13, 3.14] 3.4 Where a lot has no printed expiry, we impute one from manufacture date plus the category shelf life given in the operations manual, and we treat packaging as non-expiring. [rubric 3.3, 3.12] 3.5 We apply the SOP reserve tiers (expired 100% / <=90d 50% / 91-180d 25%) for an expiry-reserve total of $13,783,218.29, taking care not to reserve again on lots we have already written down to nil. [rubric 3.4, 3.5] 3.6 We work through the recall, quarantine, and short-dated evidence: we write off the 3 recalled lots in full (-$677,448.18) and reserve the 2025 short-dated lots LOT-10277/10524 at 50% (-$458,944.53); we do not treat the stale 2023 alert (LOT-10139) as a current short-dated item, but we prudently reserve it 100% (-$881,540.88) and flag the judgment. [rubric 3.2, 3.6, 3.7, 3.8] 3.7 We write inventory down to NRV only where NRV is below cost (LOT-10252 to $51.62, LOT-10322 to $131.81), and we leave LOT-10506 at cost because its NRV of $355.28 exceeds its cost of $310.57 and we never write inventory up. [rubric 3.9, 3.10, 3.11] 3.8 We add the 4 off-extract owned lots from Email 13 (third-party, consignment, and in-transit) at gross cost (+$1,500,600.00) and reserve LOT-13004 at 50% (-$48,400.00), so our position does not depend solely on the incomplete post-merger warehouse extract. [rubric 3.15, 3.16] 3.9 We assemble the inventory bridge (gross post-dedup, less shipped lots wrongly retained, plus FOB Destination goods still owned and off-master inventory, less expiry/SOP/recall/NRV write-downs) and foot it to net inventory of $299,953,175.23, tying to the workbook summary. [rubric 3.18, 3.19] [output: Meridian_Q4_Workings.xlsx] PHASE 4: Controls and segregation-of-duties review Purpose: Evaluate merger-related access-control weaknesses and identify priority control remediation items. Rationale: System consolidation tends to merge entitlements, so we look for conflicts even when they are spread across fragmented provisioning records, and we report a clean test result explicitly rather than leaving it unstated. Steps: 4.1 We load the vendor-access records and normalize them by employee and permission type, so each person's full set of entitlements is visible in one place. 4.2 We identify the 19 employees who can both initiate and approve payments. [rubric 4.2] 4.3 We identify the 2 employees who can both onboard a vendor and initiate payment. [rubric 4.3] 4.4 We trace fragmented provisioning records and find that they collectively give EMP-1042 all three rights across 3 separate records; in total, 20 of 58 distinct employees hold at least one segregation-of-duties conflict. [rubric 4.1, 4.4] 4.5 We run the ghost-employee / shared-bank-account test and state its clean negative result explicitly rather than omitting it. [rubric 4.5, 4.6] 4.6 We rank the conflicts into priority remediation recommendations for the partner deck. [output: Meridian_Q4_Partner_Deck.pptx] PHASE 5: Deliverable production and presentation Purpose: Produce the client-ready artifacts and present the audit conclusions in a partner-ready format. Rationale: We build both deliverables so a reviewer can trace every number, deriving headline figures from explicit reconciliation bridges and reconciling the deck exactly to the workbook. We write the deck as an audit conclusion ("we concluded," "key judgment," "audit consideration," "control gap"), not as a spreadsheet walkthrough. Steps: 5.1 We build the consolidated live-formula workbook with source mapping, the revenue workings and revenue bridge (order/shipment population less deferred FOB Destination shipments, plus valid invoice-only revenue, reflecting the Dec-29 override), deferred revenue, the inventory bridge, controls testing, and the traps avoided, so every headline number can be traced to its source. [output: Meridian_Q4_Workings.xlsx] 5.2 We build the deck with a cover, exactly five core slides, and an appendix, the core slides covering the headline numbers, revenue methodology, deferred cut-off judgments, the inventory bridge, and controls and traps. [output: Meridian_Q4_Partner_Deck.pptx] 5.3 We tie every figure on the deck back to the workbook summary and bridges, so the two artifacts cannot disagree. 5.4 We summarize the reconciliations we made and the traps we avoided across revenue, inventory, and controls in both artifacts. 5.5 We run a final check that the workbook recalculates with no formula errors and that all three headline numbers foot correctly before release.