I would like to know if anyone has a suggestion for (or can point to) a sane way of mixing 'Bulk' SQL functionality with hibernate. What are the rules of engagement?

The functionality of my app can be broken into these major tasks:
1. User reserves records in db for a few weeks work. [BULK]
2. User uploads XML data files. [BULK]
3. User configures rules for automated processing [O/R]
4. User applies rules to reserved set [GRAY-AREA: iteration or BULK]
5. User iterates the items that fail the rules and takes some action, each item is a graph with multiple collections: history, pricing, details, etc [O/R]
6. User generates summaries [BULK]
7. User generates reports [BULK]
8. User finishes (records are unreserved/unlocked) [BULK].

So there's this intensive setup that consists of validating and uploading data and locking a large set of information, then theres a long process in which individual, complex items are reviewed (Hibernate rocks here) then there is
the finalizing steps, which involve reporting and summary calculations.

This isn't an uncommon set of tasks, so has someone worked out a way to have the best of both worlds? If this is really stupid, just flog me.