Given that a battery works by moving ions between the electrodes and back again, then clearly it can only have two terminals, used for both charging and discharging, if the ions are to make it back to where they started (you could truly separate the functions with an all-liquid flow battery, but it would remain pointless).
As trainbike46 points out, even in the online architecture, a good chunk of the energy never gets converted from electrical to chemical and back again (and there is no need).
I suspect what is behind the briefing Logger79 has received is that the units are capable of operating in a mode with the battery isolated, so that the OHL must meet the instantaneous traction demand, but this isn't authorised for use. There are various possible reasons for this, but the obvious one is that the OHL draw will fluctuate more when run like this and the network as a whole may not like that.
I would be surprised to find a fully online architecture with separate battery charger and traction converter in this application, because of the use of Lithium chemistry batteries. Unlike most older chemistries with fairly constant terminal voltages, the terminal voltage of a lithium cell changes a lot with state of charge. This means a lithium charger has to be a continuously variable voltage charger, which varies the voltage depending on the state of charge of the battery, which is inferred from how much charge current the battery takes. Add a continuously variable load in parallel with the battery and the normal charging algorithms won't work.
Obviously with the correct measurement points the relevant currents can be measured, but it is getting very complex, and requires the "battery charger" and "traction controller" to be integrated into a single system - which is why there won't be a block schematic which shows this, and the full board diagram will be very complex.