CiviCRM Community Forums (archive)

I'm unclear about what you want Civi to do. It sounds like you don't want this commission to be charged to the end-user (like a credit-card surcharge), but it's more of an internal-tracking sort of thing where your accounting department needs to know what percentage of revenues to give to partner organizations.
In that case, why would Civi need to do anything? Civi is not really an accounting tool, and keeping track of internal finances is generally better left to specialty bookkeeping software.
Am I missing something?

The "soft credit" field might be good for indicating the organization. The "fee amount" field might be good for indicating the commission. Views ought to be able to display both.
Are you wanting the org and percentage to be entered by staff, or somehow calculated automatically?

A better approach might be to forget what I said in the last comment about storing the info inside the contribution. If you already have a view set up that that displays the contribution as well as the related org then you are 90% there. Just show that custom commission rate field in the view, and then you can either use jQuery or views_custom_field to do the math and display it.

It sounds like the problem you're having is displaying the related org. How is the relationship set up in CiviCRM?

If I could find a way (either in Civi or views) to pull in these Soft Credits per Organization and somehow combine them with the custom field "commission_rate" in a calculated field then I would be there.

Well that part's acutlly easy. In your view (of contributions), add a relationship: soft-credit -> contact id. That let's you pull up the contact record of the soft creditor including any custom fields, plug that into your custom field, and you're done.
The part I'm not sure about is how to get the soft credit to populate in the first place, aside from entering it all manually.
My hesitation about this whole approach is that you are now committing a rather big database sin, which is storing the same data in two places. That is, there is no "real" need to store the relationship info twice - once in the contact's relationships, and once in a soft credit field. The only reason you would actually want this is if the relationship might change over time and you wanted to be able to have some contributions for a contact attributed to different organizations. If that's the case, go ahead with this plan.
If that's not the case, then I think this approach is asking for trouble, for all the reasons you can probably think of (if your staff forgets to add the relationship and then adds it later, it ain't gonna automatically update all the soft credits for the contact).
A better solution would be to use views_custom_field to execute a little bit of php code that uses the civicrm api to pull up the related contact and display that custom field.

My point was that, depending on how exactly the soft-credit is being used, it may be straight-up duplication of data in your database.
Basically, if the soft credit always points to the same organization that the student already has a relationship with, then yes it is duplicate data. This should be a red flag for you, since storing the same thing in two places is almost always a terrible idea.
In that case, you should not be using soft credits at all. Change your view to use a custom php field and use the CiviCRM api to look up the related contact and get the custom data that way.