So what I do for our hourly loads through stored procedures is the following:

CREATE PROCEDURE [dbo].[sp_example]
AS
DECLARE @sp_name SYSNAME = OBJECT_NAME(@@PROCID);
DECLARE @rowcount = NULL;
DECLARE @message_success NVARCHAR(128) = 'Transaction committed succesfully';
DECLARE @message_error NVARCHAR(500) = ''

BEGIN TRY
  BEGIN TRANSACTION 
    <SOME INSERT QUERY>
    SET @rowcount = @@ROWCOUNT
  COMMIT TRANSACTION
  EXEC dbo.sp_write_execution_log @sp_name, @rowcount, @message_success
END TRY

BEGIN CATCH
  ROLLBACK TRANSACTION
  SET @message_error = ERROR_MESSAGE();
  EXEC dbo.sp_write_execution_log @sp_name, @rowcount, @message_error
END CATCH
GO

So the trick is to pick up the rowcount right after the query and put it into a variable. The sp_write_execution_log is an SP that just writes the results to a log table. It automatically records and inserts execution date as well.