William KimFinance × Engineering
Quick view

Production

Royalty Calculation Pipeline

A rule-based pipeline that replaced a manual Excel and pivot table workflow for a monthly royalty report.

A month-end royalty report was built by hand in Excel and pivot tables. The rate logic differs by family, and checking the result each month took about 30 minutes.

I designed and shipped a rule-based system in C#/.NET on Azure Functions. It applies the per-family rate logic to the month's activity data, then runs automated validation checks before anyone reads the numbers.

There is no model in it. The rules are the whole system, and they are written down.

Royalty Calculation Pipeline: architectureMonthly activity data goes to an Azure Function written in C#/.NET, which applies the per-family rate logic. Automated validation checks run on every result. An accountant then checks the royalty report, and the output is the monthly royalty report that replaced the Excel and pivot table workflow.SourceMonthly activity dataProcessingAzure Function in C#/.NET applies theper-family rate logicGuardrailAutomated validation checks run onevery resultHuman reviewAn accountant checks the royaltyreportOutputMonthly royalty report, replacing theExcel and pivot table workflow
Monthly royalty check
~30 → ~10 min

Compare each month's output with the prior verified month before the report goes out, so a shift in the input data is caught by a check rather than by a reader.

  • C#/.NET
  • Azure Functions
  • Rule-based rate logic
  • Validation checks