Freight Invoice SQL Pipeline Rebuild

I’m moving our freight-invoice workflow off a Windows-only desktop utility and into a fully SQL Server–driven pipeline. All business rules live in clear documentation, every data source has been mapped, and I have a year’s worth of validated invoices to prove the expected outputs.

Here is the flow I need implemented: CSV files arrive from carriers, they are ingested into staging tables, T-SQL stored procedures match each line to the appropriate rate-card logic, the correct freight charges are calculated, and the results are surfaced through an API. The API’s main purpose is to let our client application migrate data and trigger the stored-procedure processing as needed.

To keep us aligned, these are the concrete deliverables:
• Schema for raw, staging, and final tables in SQL Server
• Robust import routine that accepts varying CSV layouts without manual tweaks
• Stored procedures encapsulating every documented rule, returning results identical to my 12-month reference set
• An authenticated REST endpoint (any lightweight framework is fine) that exposes processed invoices and key audit fields
• A repeatable deployment script so the whole stack can be rebuilt on another Windows server in one pass

I’ll provide sample CSVs, the rule handbook, rate cards, and the historical “golden” output for regression tests. Success means your pipeline reproduces those numbers exactly and the API feeds our front end with sub-second response times. If this matches your SQL Server and T-SQL expertise, let’s talk timelines and milestones.