The hardest part of this build was not parsing the files. It was the nuances.
Brokerage compensation is full of small, specific rules that interact in ways a generic payroll system cannot anticipate. A representative might have a different rate for one period because of a temporary arrangement. A partnership might split revenue three ways with unequal shares before each member's individual rate applies. A manager's override income depends on the final gross revenue of every representative they supervise, which means it cannot be calculated until the first pass is complete.
Ticket charges follow tiered logic that behaves differently for small-gross and zero-gross cases. Cancellations and negative amounts need to flow through correctly without breaking downstream totals.
None of these rules are individually complex. But they all have to work together, correctly, for every representative, every period, without exception. The challenge was building a calculation engine flexible enough to absorb all of these adjustments while producing output the firm trusts enough to send to payroll.
This is exactly why the legacy system cost $4,500 a month and still required a specialist: the domain complexity is real, and generic tools cannot handle it without extensive manual intervention.