Skip to main content

Advance Tax/Self Assesment Tax and Interest u/s 234B and 234C


Read more about Tax filing @ http://tips4ufromsony.blogspot.com/2011/07/income-tax-process-and-e-filing.html .

If you are a salaried person there is tax deduction at source (TDS), which takes care of the tax payments for your salary. At the same time, there will be additional liabilities for income like interest on deposits, bonds and even capital gains which might require you to pay Advance Tax. Advance tax has to be paid in several installments in September, December and March. Self-assessment tax is the difference between the tax paid and the tax payable.You can figure out the self-assessment tax amount when you make the final income tax calculation. There is no specific date for paying this tax but it has to be done before you file your income tax return so that no further amount of tax remains to be paid.

While computing advance tax, income-tax on the current income has to be first determined and the tax on such income has to be determined. As per section 208, advance tax shall be payable in every case where the amount of tax payable by the assessee during that year is in excess of Rs. 5,000. As per section 211, advance tax is payable by companies in four instalments and by non-corporate assessees in three instalments. In cases of corporate assessees, advance tax is payable as under:

Due date of instalment Amount payable
On or before 15/6 Not less than 15%
On or before 15/9 Not less than 45%
On or before 15/12 Not less than 75%
On or before 15/3 The whole amount or 100%

If an assessee fails to pay the amount as above or if the amount paid falls short of the amount payable as under, he would be liable to interest @ 1% p.m. for a period of 3 months with respect to the first three instalments and for one month for the fourth instalment.

In the case of a non-corporate assessees, advance tax is payable in three instalments as given below:

Due date of instalment Amount payable
On or before 15/9 Not less than 30%
On or before 15/12 Not less than 60%
On or before 15/3 The whole amount or 100%

If an assessee either fails to pay the whole of advance tax or where the advance tax paid by him is less than 90% of the assessed tax, he shall be liable to interest @ 1% per month (@ 1.25% up to 7-9-2003) or part of the month from the 1st April of the assessment year to the date of determination of total income u/s. 143(1) and where regular assessment is made, to the date of such regular assessment. No interest is payable if the advance tax paid is 90% or more of the assessed tax.

Find more @ http://www.vipca.net/interest-defaults-payement-advancetax-interest-payable.php
Labels:

Comments

Post a Comment

Popular posts from this blog

ATG Search troubleshooting tips

In this blog, I have listed some basic ATG Search troubleshooting tips in some general scenarios. 1. If the index did not deploy, consider the following possible causes : Is the DeployShare property configured @ /atg/search/routing/LaunchingService component ?  Is enough space available @ deployment share box for the index ?  Are the RMI ports configured correctly in the RoutingSystemService component ?  If the search engine application is running in a separate box, this application is invoked through a RemoteLauncher running in these boxes. Check whether these RemoteLaunchers are running in these boxes ? 2. If you have trouble in launching one or more search engines, try the following remedies: If the Search engine is standalone, set the /atg/search/routing/LaunchingService component’s engineDir property to the absolute path of the Search engine directory.  3. Search unavailable in the estore page, even when the SearchEngine is in "Running" st...
5 comments
Read more

Basic design decisions for a commerce search setup ( with an ATG Search view)

In this blog I would like to explain the basic set of configuration/design decisions needed to setup an ATG search project. Most of these design decisions are common for all Enterprise search applications. 1. Decide the searchable properties :   This means the properties that the business want the user to search in the ecommerce platform. In ATG search these are configured as the text properties in the product-catalog-output-config.xml ( the definitionFile of the \atg\commerce\search\ProductCatalogOutputConfig). Usually the displayName of product/sku, displayName of department/category/sub-category, skuId, brandName are the properties configured as searchable. 2. Decide the search refinement properties or the faceted properties :   After a user search for a keyword, search refinement is the next step done to filter his results. ATG supports the search refinement using the Faceted Search concept. Read more about facted search @...
6 comments
Read more

Search Facets - how to create a new search facets in ATG Search

A Facet is a search refinement element that corresponds to a property of a commerce item type. ATG supports the search result refinement using the Faceted Search concept. Read more about facted search @  http://en.wikipedia.org/wiki/Faceted_search . Facet can either be ranges or specific values. Each facet is stored in the RefinementRepository as a separate refineElement repository item. Facets are divided into Global and Local facets. Global facets apply to all the categories and local facets only to the category in which they are created. For example Price/Brand can be considered as the facets that are common for all skus and New Release/Coming Soon can be considered as the facets that are specific to Physical Media products like Vidoe/DVD/Blue-ray/Books. We can use the ATG BCC - Merchandising UI to create facets. The Faceting Property depends on the meta-properties defined in the \atg\commerce\search\product-catalog-output-config.xml ( the def...
4 comments
Read more

How to simulate Browser back button

When someone asks how to simulate a back button, they really mean to ask how to create a link that points to the previously visited page. Most browsers tend to keep a list of which websites the user has visited and in what order they have done so. The DOM window object provides access to the browser's history through the history object. Moving backward and forward through the user's history is done using the   back(), forward(), and go() methods of the  history  object. To move backward through history, just do window.history.back() ; This will act exactly like the user clicked on the Back button in their browser toolbar. Find below a sample html code: <html> <head> <script type="text/javascript"> function goBack(){  window.history.back() } </script> </head> <body>    <input type="button" value="Back" onclick="goBack()" /> </body> </html>
Post a Comment
Read more

ATG - how to prevent Cross-Site attacks using _dynSessConf parameter

Cross-site scripting attacks take advantage of a vulnerability that enables a malicious site to use your browser to submit form requests to another site. In order to protect forms from cross-site attacks in ATG, you can enable form submissions to automatically supply the request parameter _dynSessConf , which identifies the current session through a randomly generated long number. On submission of a form (using dsp:form tag) or activation of a property setting (using dsp:a tag), the request-handling pipeline ( DAFDropletEventServlet ) validates _dynSessConf  against its session confirmation identifier. If it detects a mismatch or missing number, it can block form processing and return an error. To disable this functionality, we could give the following properties (@ /atg/dynamo/Configuration to disable it globally) enforceSessionConfirmation  = false -->  specifies whether the request-handling pipeline requires session confirmation in order to proc...
1 comment
Read more