Accessing the Centralized Portal

• The primary platform for service tax payment tracking was the ACES (Automation of Central Excise and Service Tax) portal.
  
• Registered users could log in using their Service Tax or Central Excise registration credentials.
  
• The portal provided access to payment history, challan status, and filing records.
  
• It was integrated with NSDL and the Central Board of Excise and Customs.
  
• Only valid and active registrations could retrieve payment details through the portal.
  

Using Challan Identification Number (CIN)

• Each service tax payment generated a Challan Identification Number (CIN).
  
• CIN included the BSR code of the bank, date of deposit, and challan serial number.
  
• CIN had to be noted after making the payment through authorized banks.
  
• Tracking the CIN on the ACES or NSDL portal confirmed the status of payment.
  
• Matching CIN entries helped verify whether the payment was acknowledged by the system.
  

Tracking through NSDL OLTAS Portal

• The NSDL OLTAS (Online Tax Accounting System) portal allowed direct tracking of challan status.
  
• Taxpayers could enter PAN, CIN, or TAN details to search payments.
  
• It showed the date of deposit, name of the bank, and amount paid.
  
• The portal was available to all users and did not require login credentials.
  
• This method helped in confirming if the bank had uploaded the challan to the tax system.
  

Verifying in Filed Returns

• Paid challans were required to be mentioned in the half-yearly ST-3 returns.
  
• After submission, the return status reflected whether challan details matched with the system records.
  
• A successful match indicated correct payment and credit.
  
• Discrepancies in challan data could lead to mismatch notices or audits.
  
• Return acknowledgment served as an official record of accepted payment.
  

Resolving Discrepancies and Helpdesk Support

• In case of mismatch or missing challan, the taxpayer could approach the jurisdictional Range Office.
  
• Banks could also be contacted if the CIN was generated but not uploaded.
  
• Reconciliation of records and manual verification were sometimes necessary.
  
• ACES provided a helpdesk and contact numbers for technical issues.
  

Regular reconciliation ensured error-free tracking and compliance.