Deprecated: Return type of Requests_Cookie_Jar::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/gkmglobal/public_html/gkmtax.in/wp-includes/Requests/Cookie/Jar.php on line 63

Deprecated: Return type of Requests_Cookie_Jar::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/gkmglobal/public_html/gkmtax.in/wp-includes/Requests/Cookie/Jar.php on line 73

Deprecated: Return type of Requests_Cookie_Jar::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/gkmglobal/public_html/gkmtax.in/wp-includes/Requests/Cookie/Jar.php on line 89

Deprecated: Return type of Requests_Cookie_Jar::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/gkmglobal/public_html/gkmtax.in/wp-includes/Requests/Cookie/Jar.php on line 102

Deprecated: Return type of Requests_Cookie_Jar::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/gkmglobal/public_html/gkmtax.in/wp-includes/Requests/Cookie/Jar.php on line 111

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/gkmglobal/public_html/gkmtax.in/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 40

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/gkmglobal/public_html/gkmtax.in/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 51

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/gkmglobal/public_html/gkmtax.in/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 68

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/gkmglobal/public_html/gkmtax.in/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 82

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/gkmglobal/public_html/gkmtax.in/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 91
IND AS | GKMTax.in
Deprecated: preg_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated in /home/gkmglobal/public_html/gkmtax.in/wp-includes/formatting.php on line 5397

IND AS: GKM

GKM takes great care to ensure your business undergoes minimum disruption at the time of transition while training your internal team on continued compliance with key IND-AS requirements. With increasing global imprints, companies across the world are seeking out markets across emerging economies to fulfill their capital requirements, and drive growth.

In this scenario, the use of different accounting frameworks in different countries can lead to confusion, bringing about inefficiency in capital markets across the world. The increasing complexity of business transactions and globalization of capital markets call for a single set of high-quality accounting standards.

The new leasing standard, Ind AS 116 Leases, has replaced the existing standard (Ind AS 17) from accounting periods beginning 1 April 2019. This standard is the Indian equivalent of the global standard IFRS 16, which has become effective for annual periods beginning on or after 1 January 2019. The new standard is expected to bring about a substantial change in lease accounting for lessees by replacing existing dual finance vs operating lease model with a “single accounting model for all leases” which recognizes leases in the balance sheet on day one, in the form of a right-of-use asset and a lease liability.

While larger multi-national organizations can make this transition process with resources on their side, for many smaller and mid-sized organizations, this transition can pose difficult questions.

Indian entities of foreign corporates, all listed entities, and Indian corporates above specific net worth criteria require reporting as per International Financial Reporting Standards (IFRS) or New Indian Accounting Standards (Ind – AS).

Extensive review & assessment to gauge the impact on your business, with necessary review and advisory services are carried out to make sure requirements are met and effective measures are in place to implement conversion to IND-AS.

Reach out to us to discuss on your questions regarding NRI taxation, business setup in India / USA, GST returns filing, transfer pricing or any other questions.

Subscribe to our Newsletter:

Loading