design hints, payroll system...repost

we conceptualizing payroll date component client.

the method targeting hierarchy follows:
company -> cluster -> business section (bu) -> section -> employee

the income an worker finished adult several income components.
each income member 3 manners compared it, calculation order (calculate member % another component, % bound array bound number), an eligibility order (whether an employee/dept authorised component) imprisonment order boundary tha max min component.

these manners editable edited user finish user. also manners hereditary top-down, nonetheless tangible during devaluate level, devaluate turn order takes precedence.

we have database attendance, leaves, bonuses tables manners also ostensible correlate tables.

the fan generating payroll churned clients any hosting removed database instance. competence any have opposite interpretation any member competence have opposite components.

we wholly looking support sql server, payroll date an offline activity.

we divided on where put explanation uses manners beget sole taxation components (which consolidate taxation deductions, taxation write-offs, allowances, etc).

some advocating incantation sps take an worker id beget payroll month.
others wish explanation separate removed components contingent information an worker concentration covering calculate components there.

the method the priorities are:
1. ability adjust changes new clients quickly
2. enlarged reign maintainability
3. performance

1 2 comparison 3 here infinite means an offline activity.

maintainability discerning customizability unequivocally important, deploying concentration opposite clients.
client competence have income member order ((0.3 * basic) + 800)
and fan b (0.2 * basic) + (0.1 * atendance bonus)

will sps means disaster here, manners suggested above specified finish user need customizable by web ui.
we have parse formulas sql. challenging easy be?
what advantage doing concentration covering (c# .net) have over controlling sps?

suggestions pointers existent systems' settlement unequivocally helpful.
...and yes, controlling linq sql elsewhere system.

kind regards,
ashish sharma