Yes. for example, if a row is updated on the source and then later that same row is deleted on the source, that order of transactions will be preserved when replicated to the target. (Reminds me of the time a colleague recounted the answer that an interviewee gave to the question "what is transactional replication"? and the answer came back "it's when transactions are replicated transactionally"! :-D)

Change Data Capture (CDC) has the ability to 'net' transactions so an INSERT followed by a DELETE would generate no change data. Not for the reason I just gave, but I wonder whether CDC is an option for you?

I think MisteryJimbo's suggestion to use Merge Replication is your best option if you don't want to create your own custom solution.

By the way, wouldn't it be better to validate the data as it is arrives in the source database rather than using a replication delay to QA it?

Regards

Lempster