In a ledger centralisation programme, the “tactical” interfaces between the systems of entities still to migrate and the central ledger often decide the timeline.
Ledger centralisation programmes at international banking groups rarely happen in a single wave. For months, sometimes years, entities still on their legacy systems must feed the central ledger. The interfaces providing that link are called tactical: they are meant to disappear. That is exactly why they get underestimated.
Temporary does not mean approximate
A tactical interface produces real entries feeding real statements. It must give the same guarantees as a target interface: complete flows, traceability of every entry back to the original transaction, balancing controls, reject handling.
The business analyst’s role
The business analyst sits where three worlds meet: the entity, which knows its flows; the central-ledger team, which knows the target scheme; and IT, which builds. The job is to make explicit what each side takes for granted.
- a mapping dictionary from source data to the target accounting scheme;
- transformation rules written down with their edge cases;
- test cases written alongside the specification, not after it;
- a parallel-run plan stating in advance how breaks will be explained.
Plan the decommissioning from day one
A successful tactical interface is one that can be switched off cleanly. Documenting the rules it carries from the start means they can be reused in the target solution instead of being rediscovered at migration time.