William KimFinance × Engineering
Quick view

Work

Kept like a ledger: what it is, what it does, what it runs on, and what changed because of it. Two books: production work at Ortho, and products I have shipped on my own. Experiments now live in the Lab.

Ortho Molecular Products, Barrington, IL. Staff Accountant working across technical solutions and financial systems, March 2026 to present. The three production systems below keep accountant review and posting authority, write audit logs, and ship with written procedures. The Fast Close item is a fix to an existing report, and the consolidation is specification work. Each name opens its case study. The automations run as Azure Functions written in C#/.NET.

  1. Concur Automation Production · LLM system

    Classifies corporate card transactions, about 1,900 per cycle, built in C#/.NET on Azure Functions, calling the OpenAI API inside deterministic rule guardrails. Benchmarked against the human reviewers. Humans still post.

    Stack C#/.NET · Azure Functions · OpenAI API · SAP Concur · rule engine

    Outcome 36 h → 10 min per month. 95 to 97% exact match to human reviewers, zero misclassifications.

  2. Royalty Calculation Pipeline Production

    Rule-based C#/.NET pipeline running as an Azure Function that applies per-family rate logic to monthly activity data with automated validation checks, replacing a manual Excel and pivot-table workflow for a critical month-end report.

    Stack C#/.NET · Azure Functions · validation checks

    Outcome Monthly royalty check cut from about 30 to 10 min.

  3. Fast Close Report Fix Financial systems

    The SQL-based Fast Close report had produced wrong data for months. I wrote the SQL myself to isolate the defect, gave BI the exact fix, and followed through until it held.

    Stack T-SQL · BI partnership

    Outcome The August close ran clean, after four months of follow-through.

  4. Accounting Time Tracker Production

    Timekeeping tool for the accounting building, built as an Azure Function: hours captured across roles and activities, approval workflow, full audit trail. Piloted, rebuilt after IT review, now in production.

    Stack Azure Functions · C#/.NET · approval workflow

    Outcome In production, after a pilot and a rebuild for IT review.

  5. Practitioner Website Consolidation Cross-functional · in progress, launch Dec 31, 2026

    Selected as the cross-functional bridge between IT, Accounting, and Marketing for consolidating three practitioner platforms into one. I author the specification layer: a workflows document, a decisions sheet, and a clickable HTML prototype.

    Stack Specification · HTML prototype · ERP field design

    Outcome Surfaced a tax compliance requirement missing from all project documentation (W-9/TIN and verified banking before proceeds accrue) and drove it into the ERP design.