SQLRNNR (1/17/2013)
There is a way, but while hashing that out I just want to bring up a preference. I prefer to have the date and time on the backup files myself. If the logs traverse a day, then they will still be listed in order by name. It's just easier imho.
My experience is that vendor supplied backup jobs are usually not very well done, and it looks like the case in your situation. I prefer to setup my own backups.
One day is really too short a time to retain the transaction logs. I recommend at least four days, and I would like to see longer. I also recommend you do a full backup daily and keep that for at least three days.
If you are on SQL Server 2008 Enterprise Edition or SQL Server 2008 R2 or later, you may also want to set the option to compress backups. They usually run faster, and they will take up less disk space.
You could do all this with SQL Server maintenance plans that can be setup in just a few minutes. It takes care of generating the date/timestamped backup file names, setting up jobs and schedules, and also takes care of deleting the old backup files on the retention that you decide.
There are also very good backup stored procedures posted on this site and elsewhere that can do all of this.