Tax Management India. Com
Law and Practice  :  Digital eBook
Research is most exciting & rewarding
  TMI - Tax Management India. Com
Follow us:
  Facebook   Twitter   Linkedin   Telegram

Home Case Index All Cases Customs Customs + AT Customs - 2009 (10) TMI AT This

  • Login
  • Referred In
  • Summary

Forgot password       New User/ Regiser

⇒ Register to get Live Demo



 

2009 (10) TMI 261 - AT - Customs


Issues Involved:
1. Whether the imported software qualifies as "customized software" under Central Excise Notification No. 6/2006.
2. Interpretation of "customized software" versus "packaged software" in the context of the notification.
3. The role of expert opinions and other documentary evidence in determining the nature of the software.
4. The applicability of exemption under the Central Excise Notification No. 6/2006 to the imported software.

Issue-wise Detailed Analysis:

1. Whether the imported software qualifies as "customized software" under Central Excise Notification No. 6/2006:
The appellant argued that the imported software, PADO and BPOS, was customized specifically for each power plant of BHEL and thus should qualify for exemption under Notification No. 6/2006-C.E. The appellant provided evidence that the software was developed in Germany based on the specific parameters of each plant and referred to the Factory Acceptance Test (FAT) and System Design Documents to support this claim. However, the respondent contended that the software was not custom-designed but rather a standard software modified to suit the specific requirements of BHEL, thus not qualifying for the exemption.

2. Interpretation of "customized software" versus "packaged software" in the context of the notification:
The notification grants exemption to "customized software" defined as "custom designed software, developed for a specific user or client," excluding "packaged software or canned software." The appellant relied on the dictionary meaning of "customized" and previous tribunal decisions to argue that modification of existing software qualifies as customization. The respondent, however, emphasized that the notification explicitly restricts the exemption to "custom designed software," which should be developed from scratch, not merely modified.

3. The role of expert opinions and other documentary evidence in determining the nature of the software:
The appellant presented an expert opinion from BHEL stating that the software was customized. However, the respondent argued that BHEL, being an interested party due to the duty liability, could not provide an unbiased opinion. The tribunal agreed with the respondent, citing Supreme Court judgments that opinions from interested parties should not be considered reliable. The tribunal also considered various documents, including purchase orders, meeting minutes, and website printouts, which indicated that the software was pre-existing and only modified for BHEL's requirements.

4. The applicability of exemption under the Central Excise Notification No. 6/2006 to the imported software:
The tribunal concluded that the imported software packages were modified versions of pre-existing software and not custom designed from scratch. The tribunal emphasized that exemption notifications must be interpreted strictly, and any ambiguity should be resolved in favor of the state. The tribunal held that only software developed entirely from basic building blocks for a specific client qualifies as "custom designed software" eligible for exemption. Consequently, the tribunal upheld the order of the Commissioner of Customs (Appeals) and denied the exemption to the imported software.

Conclusion:
The tribunal concluded that the imported PADO and BPOS software packages are modified packaged software and do not qualify for exemption under Central Excise Notification No. 6/2006, which is reserved for custom designed software. The appeal was rejected, and the order of the Commissioner of Customs (Appeals) was upheld.

 

 

 

 

Quick Updates:Latest Updates