Small PowerShell Update — Filename Parser (Optional Numeric Suffix)

PROJECT BACKGROUND We run a PowerShell script on a Windows VM that watches an inbound folder for new files. Filenames follow a fixed short-code convention: [8-character ClientCode][1-character Type Letter][Period] — e.g. SMIT1234I2025.pdf = Client SMIT1234, Individual return, tax year 2025. The script parses the ClientCode, Type Letter, and Period out of the filename, looks up the client name via an API call to a CRM system, and uploads the file to a SharePoint document library with those three values applied as metadata. The script is live in production and currently handles all of the firm's document intake this way. CURRENT BEHAVIOR The script rejects any filename with characters after the Period segment. For example, ACME5678U2025_01.xlsx is flagged as a PARSE-ERROR and the file is renamed with a warning prefix instead of being processed. REQUIRED CHANGE Update the filename parser to accept an optional two-digit numeric suffix after the Period, in the format _NN (underscore followed by exactly two digits, 01 through 99). This must work across all file types the script currently processes (.xlsx, .pdf, .docx, .txt, and any others). Valid — must be accepted: • ACME5678U2025_01.xlsx • ACME5678U2025_02.pdf • ACME5678U2025_03.docx • ACME5678X2025_01.pdf Invalid — must still be rejected: • ACME5678U2025_1.xlsx (single digit — invalid) • ACME5678U2025_100.xlsx (three digits — invalid) • ACME5678U20251.xlsx (no underscore — invalid) The suffix is for file differentiation only — it must be ignored during tag/metadata parsing. Files sharing the same base shortcode are tagged identically. Filenames without a suffix must continue to work exactly as before — the suffix is optional and fully backward compatible. SCOPE In scope: filename parsing/validation logic only. Out of scope: upload logic, tagging logic, CRM lookup, alert emails, scheduled task configuration. None of these should change. DELIVERABLES 1. Revised script, submitted for review before any deployment. 2. A short written note describing exactly what parsing logic changed (e.g. the regex pattern used). 3. Confirmation that you've tested both the valid and invalid suffix cases listed above. We will test the revised script ourselves on our own VM before it goes live — no remote access to our environment is needed for this task. TIMELINE Target turnaround: 3–5 business days from award. Please confirm a firm delivery date in your proposal — this is a fixed deadline, not an estimate. BUDGET — FIXED PRICE ONLY This is a fixed-price engagement — we are not considering hourly bids. Please submit a single fixed-price quote in your proposal covering the complete scope above, payable via Upwork milestone on delivery and successful review. Do not submit an hourly rate or an open-ended estimate. REQUIREMENTS PowerShell scripting experience required. Familiarity with REST API integrations (Microsoft Graph or similar) is a plus. Please describe your proposed regex/parsing approach briefly in your proposal — this helps us evaluate technical fit before award. Note: We're reviewing fixed-price proposals from multiple candidates for this task.