TAMS is a new software being developed and implemented by Indian Railways to integrate revenue accounting across different systems like FOIS, PRS, UTS. It aims to provide consolidated monthly revenue transaction status. TAMS modules include goods and coaching balance sheets, traffic book generation, earnings account, TIA inspections. It reduces manual work by automating processes and enabling online validation and reconciliation. Future goals include full integration with IPAS and automatic account current generation. TAMS development is ongoing with modules being added and improved over time to modernize railway revenue accounting.

1. TAMS
A way towards –
Transparency
Concurrency
Accuracy

2. Why TAMS
• FOIS caters RR generation and operational features.
• UTS/PRS caters generation of Tickets.
• There is no single software to collect and compile the Revenue
transactions.
• FOIS, UTS, PRS do not give the consolidated status of revenue
transactions on monthly basis.

4. The Traffic Book is
a compilation which collects and brings to account,
under the prescribed heads Coaching, Goods and Sundry Other Earnings,
the whole of the traffic earning of a railway,
both Local and Through,
whether accrued at stations or otherwise.
It records the progress of realization of these earnings,
the results of apportionment of traffic interchanged with Other Railways,
and
the progress in the settlement of the balances on these accounts.
Mechanism of Revenue Accounting

5. History of TAMS
• TAMS sanctioned in F.Y. 2016-2017
• MoU signed with Northern Railway in March 2017
• Western Railway (WR) and Northern Railway (NR) is nominated as nodal Railway for this
project
• User functional requirement coordinated by Western Railway
• Mapping of best practices on computerization processes in TA office
• Identification of Gaps
• Design, Development and Implementation of Traffic Account application
• Project was handed over to Central Rly for development and implementation in
March’20.
• Good Balance Sheet module of TAMS was formally launched by MF & M(O&BD) on 27th
September, 2021 and since have been implemented in CR and some of the railways.
Coaching Balance sheet module which was under development, has also been completed
recently and railway board guidelines in this regard will be shortly issued.

6. Objective of TAMS
• Integration of all Accounting Returns for different verticals of earnings of IR:
Passenger, Goods, Other Coaching and Sundries
• Collected Earnings to reconcile with cash book
• Originating Earnings : Transaction number + transaction value for statistical
statements
• Apportioned Earnings: 7C for Goods and 6A for Passenger
• Integration of Computerized Balance Sheets in TA office
• Generation of Traffic Book : Part A,B,C and D
• Linking of Balance-sheet with cash office module of IPAS
• Generation of Earnings Account

7. Conceptual Endeavour of TAMS
• Reduce manual intervention on basic data to minimal
• Internal check – completely online with smart checks and
validations
• Tweaking more on FOIS, UTS and PRS - ease of applicability
and integration
• Reduction of overall aberrations / modifications in the revenue
data – all correction through error sheet module.
• Reconciliation to be made part of the accountal and data flow
• MIS to support future decision making
• Almost all transactions to be part of station B/s
• TIA inspections – smarter and online
• Traffic finance and costing to be on IT platform
• Final JV and account current to be seamless.

8. Idea behind TAMS Development & implementation
• No re-invention of Wheel- TAMS utilises the features available in
FOIS, PRS/UTS/PMS, with necessary tweaking, minor modifications to
suit the requirement.
• All modifications in the data shall be routed through Error sheet
module only for accountal and traceability.
• All the entries will appear in Balance Sheet only after due
reconciliation in the system, thereby internal check is ensured.
• Balance Sheet will be the final outcome of the station transactions
duly considering the all activities without any manual adjustments in
the Balance Sheet.

9. • Apportioned revenue data available on line to Commercial Dept.
• Dispensing submission of Manual/ system generated Balance Sheet to
Traffic Accounts
• Availability of Station outstanding data directly to Divisions and Hqrs.
• Division wise earnings – category wise are available through Traffic
Book Part A.
• Availability of Zone wise inward and outward data
• Instant Accountal of Debits and settlement of debits online. Eliminates
lot of correspondence.
• Dispensing the preparation of manual CR/ TR notes and online
reconciliation & acknowledgement of Cash through IPAS module.
Establishing strong relation between Traffic Accounts and
Commercial Dept

10. 1. Apportionment of Passenger & Freight Revenue.
2. Statistical Statement of Passenger Traffic – 6A
3. Traffic Book -Part A, B, C & D
4. Accounts Office Balance Sheet (AOB)
5. TIA module.
6. Station Balance Sheet (Cog & Goods)
7. Error Sheet module.
Components of TAMS

12. TAMS Integrations with different CRIS Projects
TAMS
PROJECT
Apportionment
module
Goods Balance
sheet Module
Coaching Balance
sheet Module
Traffic Book
Module
Account Current
Module
RBS
PRS
UTS
FOIS
PMS
IPAS

13. TAMS Integration Details
PROJECTS Integration Details
PRS
Sharing of monthly Passenger earnings data in consolidated format for coaching earnings
apportionment.
Sharing of Military and paramilitary data for preparation of Account office balance sheet.
UTS
Sharing of monthly Passenger earnings data in consolidated format for coaching earnings
apportionment.
Sharing of Coaching Balance Sheet for Internal Check module.
Sharing of Military and paramilitary data for preparation of Account office balance sheet.
FOIS
Sharing details of Goods railway receipt data .
Sharing of Goods Balance sheet data for Internal check Module
Sharing of Goods Apportionment Matrix data for preparation of Traffic Book Part C.
Sharing of Military and paramilitary data for preparation of Account office balance sheet.
IPAS Sharing of Data from Cash & pay module for Balance sheets internal check module.
For Transfer of Zonal apportioned share through IPAS Journal Voucher.
PMS Sharing of Parcel Data for Generation of Traffic Book.
RBS Sharing of Route wise Apportioned Percentage for Coaching apportionment module

14. Different 6A Reports generated on TAMS portal
• Input statistics for apportionment (PRS ,UTS)
• Centralised apportionment matrix of passenger earnings for all zonal railways
(PRS,UTS)
• Summary of passenger earnings (for railway board statistics only) (PRS,UTS)
• Matrix of collected and originating earnings (PRS,UTS)
• Statement 6A Part- I Report (PRS,UTS,PCT,BPT ) Originating
• Statement 6A Part- II Report (PRS,UTS,PCT,BPT ) Carried
• Consolidated 6A Part-I (PRS,UTS,PCT,BPT) for IR
• Consolidated 6A Part-I I (PRS,UTS,PCT,BPT) for IR
• Prtn file report (PRS,UTS)
• Centralised apportionment matrix of catering charges for all indian railways
(PRS)

15. Traffic Book part ‘B’
•Present Procedure.
•Apportionment Matrix from CRIS.
•Manual Exchange of Net results.
•Manual feeding of JVs in IPAS.
•Requirements in TAMS Module.
•Creation of new file for net result
•Exporting the data to IPAS
•System Based generation of Railway wise Out ward
and In ward JVs for incorporation in Account Current.

16. Flow for generation of Balance Sheet & Error sheet
(Goods, Coaching)

17. GOODS B/S in TAMS

18. Error Sheet Module
B/S Internal
Check
CR Note not
received
D&W Siding &
Shunting
RRs check
& others
Error Sheet
issued
TA Office
CAN issued Goods B/S
Recovery or
Payment
On AFA’s Approval
Disagreed
NAD with remarks
Error sheet module in FOIS
Agreed
as
AD
Agreed
Debit Resolution Mechanism

19. Errorsheet Module in FOIS
BACK

20. AOB Module
TAMS
Voucher data
from PRS UTS
Voucher data
from IPAS
Automated
Reconciliation
Internal
Check
Auto bill
generation
IPAS Data checked &
matched manually
Matched
Unmatched

21. AOB – Dash Board

22. AOB - Reconciliation

23. AOB – Internal Check

24. Conceptual Framework of TIA module
• To have effective planning & Control over Inspection Process
• To have better monitoring on the due & Over due Inspections
• To include flexibility through built in mechanism for Special Check,
Assistance to TIAs, allotment of inspection.
• Paperless reporting System (except TA 6F)
• Online verification of reports and closure.

25. Structure of Module
Module is divided into 2 parts:
- Activities carried out by Hqrs Team.
- District Management
- Station Management
- Special Checks
- Assistance to TIAs
- Inspection of Vacant Districts
- Checking of Inspection Reports
- Activities carried out by Field Team.
- Inspection as per the District List (Beat)
- Submission of Reports

26. TIA Module
TAMS TIA Module
TA
Office
TIA
Mgmt
District
Mgmt
Forecast
&
Movement
TIA,
District &
Station
Mapping
TIA
Inspection
Reports
Debit resolution loop
starts
Raises Debit directly
in FOIS via 6F Report
in TAMS
FOIS

27. Additional Features
• Provision for downloading the individual reports & Consolidated report
in PDF format.
• Save and Submit facility.
• Android App for making entry of Forecast & Movements.
• Integrated Debit raising & Credit allowing facility.
Way forward –
Dash Board for smart inspection based on the activities of a station
- Station Outstanding.
- Irregularities reported in Last inspection

33. TIA Reports Screen in TAMS BACK

34. Integration with FOIS
• Integration with FOIS for taking the details of RRs.
• Integration with FOIS for taking GOODS Apportionment data for
preparation of Traffic Book part B & JV generation.
• Integration with PRS, UTS & FOIS for taking Military & Para Military
vouchers data for preparation of AOB and Traffic Book Part C.
• Integration with FOIS for computerised Goods Balance Sheet (GBS)

35. •Work In Progress
• Generation of Traffic book part C and traffic book part D
• Integration with IPAS for taking inputs (CR/ TR note) from Cash & Pay
Module and reflecting it in credit portion of the balance sheet
Work to be taken shortly
• Account Current Generation.
• Traffic Costing module

36. Way forward
• Auto reconciliation of TR data with Bank scrolls
• Auto generation of TC for JVs
• Generation of Abstract X & Y
• Generation of Account Current by 7th of next month- the ultimate
goal.

37. Thank You