Well it depends on whether or not the report output versions satisfy your archive requirements.
You say initially you want to run them manually, print and archive those results. What I would do is go ahead and schedule them to run a minute from now so you can do a save as pdf and also print them (otherwise you'll have to run it to save it and then run it again to print it). To automate it, same thing only set the schedule to be recurring.
The real problem comes in the archive scheme. Do you understand what report output versions are? Try this: View properties on a report and set the "report output versions" to some number (say 5). Now run the report and click 'save' and select pdf as the type. Close it. Return to the portal and run the report again, only save and put html as the type. Now either click the icon that looks like pages or go to the more... link and select 'View report output versions'. Now you can select which version to view based on the time. If this is acceptable, then you are done. You just need to schedule the report on a recurring (repeating) basis, make sure to save enough versions to satisfy your archive requirements, and educate the users on how to see past data. You do need to be leery of users with write access as they could potentially wipe out your archive. This would also be a point of user education and teaching them how to view the latest output. It's also a means to justify some stricter security on this set of reports and limiting everyone to just read and execute. (and traverse). Just make sure no one can save the report back to that folder and you are good.
If you are unhappy with using the report output version feature, then you are stuck with manually saving a 'report view' with a different name. To automate this, you would need to schedule the report to run, saving as a report view with some 'default' name that reminds someone to change the name to the current month.
Hope that helps