Well. the svn(or any other source control for that matter) is designed for a programming atmosphere where multiple programmers (or just one) are working on a project and same files are being edited by multiple people. so a source control is used to track changes of code and by whom. So you gotta ask yourself 1- is there a semantic relations between my reports so that I need to track the changes between them? 2- do I care who made that change? if the answer to both questions is a no then svn is just an overkill and adds an unnecessary level of complexity.
Another thing, are these reports in a binary file format? if yes then this is one more disadvantage of using svn, since it can't keep track of what has changed. it will just commit the whole file as it is. If the file is ascii (text) format, then do you need to track changes? if yes, then svn can do it, but also a bunch of other tools can do it without the complexity of depending on svnkit library.
If you just need to store different reports with different "upload time" why dont you just use a database, with the following fields: (id, report, timestamp, some foreign key).
Hope this helps