The ticket barriers only read the information on the ticket barcode and dont alter the tickets.
If the final destination on the return ticket was the same as the station containing the origin barrier and it was placed into the exit side it will swallow the ticket unless it contains the word stations on the ticket, eg "Liverpool stations". In this case the ticket will be returned.
Also if the same ticket is used twice in the last 60mins the barrier will remember the information and refuse to accept it. This is supposed to elimate more than one person using the same ticket.
Hope the above helps.
As I consider myself to be somewhat of a "pro" in ATGs, (I create the data for them to implement), I can assure you that the ATGs will write to the ticket.
A code 07 for a ticket is a Write Failure code, for when the ATG is unable to write, but can read.
The "passback" time is set by each TOC, 60mins is a little too long IMO. I have set it at a fraction of that. Passbacks only occur generally within seconds of each other, a mate passing his ticket back. 60 mins is excessive. The error code for a passback is typically 133, but can be customised to something different, which I have set to 555 on Merseyrail ATGs.
As for what it writes on the ticket:
1) NLC where the ATGs are
2) Whether the gates were operating normally or in emergency
3) The time & date
If you then put a "used" ticket into a STAR Machine to read the data, it would tell you the above, as well as other things that the ATGs don't write.