If you have a transaction surrounding 5 stored procedure calls, and each call should result in a single row in each table that you can track to - then you should not see only a single row in just one table.

This tells me that something is happening to commit the transaction for the first SP and the rest of the code is getting rolled back.

Do you have explicit BEGIN TRANSACTION and COMMITs in each stored procedure?

Is it possible that somewhere after the first stored procedure runs, you get an explicit commit - and later in the process you are getting an implicit rollback because the connection is terminated? Or, is it possible that an error is occurring that isn't trapped?

Like I said before, start a profiler trace and capture the actual calls to the database.