Small and Medium-Sized Enterprises (SMEs) have received a tremendous fillip of late, with the Government pitching in to give a hands up to this very vital business sector. SMEs engaged in businesses ranging from electronics to ad services, or from engineering to textile to handicrafts routinely face a cash crunch that handicaps their everyday operations, as well as hampers plans for expansion.
SMES and the short-term loan
It takes immense courage to begin your business, and taking risks of establishing, sustaining, and expanding it can be prohibitive for many. Financing is the fundamental issue here, and many businesses are compelled to shut shop or to approach banks in order to raise short-term business loans.
Finances are the lifeblood for any enterprise, and any business plan worth its salt must include sound planning for fund sources as well. Short-term business loans and short-term finance are available in plenty and offer SMEs a chance to overcome their temporary financial problems as also provide an opportunity to expand their business. However, these loans are not without pitfalls. Here are some tips that will help an SME to take a well-considered decision when it comes to applying for short-term business loans:
1. Do your homework
SMEs are recommended to do adequate research to identify the option that are most suitable to them. Occasionally, and especially if the borrower has a good credit score, a simple overdraft or line of credit can help the SME to tide over their cash flow problems. Bank loans carry low-interest rates, but the paperwork involved and time taken to sanction can be burdensome. Crowdfunding, inventory financing, and credit card financing are options that can be explored. Promoters also help to finance a large chunk of working capital requirements. But if a short-term loan is a final option, a careful look at the costs involved can help to tip the scales over.
2. Try online loans
Short-term online loans are meant to be repaid anywhere between 90 days to three years. They are quick, convenient and flexible. A good deal of the paperwork process is cut off and friendly financiers also help eliminate the traditional application method of back-and-forth conversation. The huge advantage lies in not necessarily having to offer collateral. Provided an SME finds the right fintech lender, they can benefit from the speed of digital processing. Additionally, preclosure penalties and hidden charges are also avoided. Genuine financiers will also provide the convenience of flexible loan tenures.
3. Measure business liquidity
There is always a possibility that even a profitable SME can run into cash-flow problems, regardless of the numbers reflected on the cash-book records. Delays in receivables have hurt many a lucrative business, and are in fact a common cause for cash-flow mismatches. In such cases, measuring the liquidity of the business can be very useful for an SME in order to find an alternative way to mitigate problems of a cash crunch. The proper evaluation of liquidity can be extremely beneficial, and can be measured in two ways:
Quick Ratio It shows the capability of business in covering current liabilities with current assets, and utilises the formula:
Quick Ratio= (Current Assets – Inventory)/ Current Liabilities
It is measured by calculating the difference between the current assets and current liabilities, with the formula:
Working Capital = Current Assets – Current Liabilities
Getting these figures in hand can help measure business solvency, and thus available funds can be duly channelised and prioritised.
4. Capitalise on credit score
It pays to maintain a good credit score history, in more ways than one. A good credit ranking can help you bargain for lower interest rates on short term business loans. Also, it opens up room for tapping into other means of raising money, such as getting into partnerships or seeking non-traditional lenders for funding.
On occasion, the lender may analyze both your business and your personal debt load, in addition to your credit score. If any of these is already high, the lender may hesitate to extend or provide fresh credit for your business. So, it is important to keep a tight rein over your credit utilisation, so that the services offered by the lender are not affected by your credit score.
5. Check APR
While comparing and selecting the best short-term business loan and finance service, one must always keep in mind the number of applications they are filing for apply for the term loan. After receiving multiple loan offers, one must select the most suitable loan offer by comparing the Annual Percentage Rate (APR) of every term loan lender. This is perhaps the most important calculation to estimate how expensive a loan is. Once you understand the logic of short-term business loans, it is easy to decide whether or not getting a particular loan is a right choice in terms of its actual cost.
6. Be ready for lender’s queries
Things don’t end here. There are chances that the lending party can contact the SME for verifying their documents that they submitted while applying for term loan. Thus, the SME owner must always be ready for answering any query regarding their documentation or regarding their future goals for the company. A small preparation toward this can prove to be very beneficial in getting a loan finalised. Ergo, shortfalls of cash may be inevitable, but not insuperable. A little bit of math and careful consideration of the choices can help you get the cash you need—hopefully at the price you can afford— without having to fall into a debt cycle.
More Related Posts
As we work in startup, we are under time pressure to release a lot of new features on time, features which do not have well defined requirements and the complexity of those features is often underestimated and we end up taking a lot of shortcuts / adding hacks to release such time sensitive features.
This may work for a short time, but over the period of time we realize that the same shortcuts that you took to release features quickly are now slowing you down. You can not scale and add new features on top of it, even if you do, they become quite unstable. In this situation you might want to take a step back and revamp/refactor you base system.
One of the easiest things that you can do to avoid this situation is follow coding guidelines.
Well, what according to you is a good code? The simple definition could be: if it can’t be understood, maintained and extended by other developers then its definitely not a good code. The computer doesn’t care whether your code is readable. It’s better at reading binary machine instructions than it is at reading high-level-language statements. You write readable code because it helps other developers to read your code.
As the name suggests, it is a simple concept where you follow a specific naming conventions across teams. This becomes important when your team is growing and are solving problems on daily basis and pushing a lot of code every day.
This helps a lot when your team becomes big and a lot of developers are working on the same code-base. If you follow some fixed patterns while defining classes/functions/variables names, it becomes really easy for fellow colleagues to understand your code. This directly impacts delivery time taken by a developer to build/modify a feature on top of existing code. For example, let us suppose you want to define a time-stamp field in a database table, how would you name it ? If you have a fixed pattern like a “action_ts” or “action_at” for giving names then you can easily guess what could be the field name in the schema. If its a created time-stamp then it could be either “created_at” or “created_ts”. You do not have to go and check every-time you writing any logic over different database tables.
Function/Module/API writing (Size and Purpose)
Simplicity and readability counts. It’s always better to write to concise code than a messier one so that if any other developer is also looking at it who has no idea, should get what exactly it is doing. Not more than max 10–15 lines. Jenkins is considered as one of the greatest implementations, and has average function length of 2 lines.
A function/module should only do ONE thing and should do it NICELY. By following this, code becomes modular and it helps a lot in debugging. You can solve the problem better and debug faster when you know where exactly it’s coming.
When you are developing features over an established products, more than 50% times, new requirements are of the nature which you can build on top of existing code. In such cases, you can ship those requirements really faster and stable if existing code-base is modular and stable. Writing library functions a savior. There are countless advantages of writing a library code. It avoids code repetition, no surprises when it comes to response formats and of-course code re-usability.
Unknown errors are real pain in developers life. It’s always better if you know probable exceptions and errors in code in advance. But that is not the case always. Irrespective of all this, you definitely do not want your end-users to see unexpected errors on their screens.
When you have different micro-services and bigger development teams, if you follow standard response formats for across APIs and standard exceptions then there will not be any surprises in production. You can agree upon one format across all the services. Every API can have certain ‘response_data’ and standard set of error-codes. Every Exception will have an error-code and a message. Message could have variation viz, tech specific message and user facing message.
Writing test cases:
If you want to have a good night sleep, then you better have thorough test cases covering almost all aspects of your code. The best way forward with building test cases is at requirement stage only. Whenever a requirement comes, products managers discuss it with developers as well as QA. Both teams start preparing for possible use-cases and test-cases.
A testing unit should focus on one tiny bit of functionality and prove it correct. Each test unit must be fully independent. Each test must be able to run alone, and also within the test suite, regardless of the order that they are called. The implication of this rule is that each test must be loaded with a fresh data-set and may have to do some cleanup afterwards.
Automation plays an important role here. What else is needed for stable product where you have all test cases covered and running at intervals automatically, giving you a report of the all functionalities. Also, whenever you are adding/modifying code, you make sure either you write new test cases or modify existing ones.
This one thing save lives, trust me! Every team can benefit from code reviews regardless of development methodology. Initially it takes time if you do not have a procedure setup of doing code reviews, but eventually it becomes a habit. Code review should be one of the core development steps.
Code review generally is about:
- Does the new code conform to existing style guidelines?
- Does the written piece of code covers all the use-cases specified in the requirements and has relevant test cases written ?
- Are the new automated tests sufficient for the new code? Do existing automated tests need to be rewritten to account for changes in the code?
There are several advantages of this process such as –
Code reviews make for better estimates: Estimation is a team exercise, and the team makes better estimates as product knowledge is spread across the team. As new features are added to the existing code, the original developer can provide good feedback and estimation. In addition, any code reviewer is also exposed to the complexity, known issues, and concerns of that area of the code base. The code reviewer, then, shares in the knowledge of the original developer of that part of the code base.
Code reviews mentor new joiners: Code reviews help facilitate conversations about the code base between team members. During these conversations, team members share their views and new alternatives of doing things.
Code reviews take time: It’s an incremental process, where it takes time initially but as your code-base grows, it ensures, you are always pushing verified and tested code.
Hidden truth about code reviews: When developers know their code will be reviewed by a teammate, they make an extra effort to ensure that all tests are passing and the code is as well-designed as they can make it so the review will go smoothly. That mindfulness also tends to make the coding process itself go smoother and, ultimately, faster.
As a fast growing company our self, these set of guidelines have helped us a lot in shipping stable features on time and helping to increase a healthy learning environment.
Source:- Capital Float’s Medium Blog
Oct 24, 2018
The new Goods and Services Tax (GST) is a unified tax structure that was implemented by the Government of India on 1 July 2017. The new regime has ushered a significant change in taxation levels and rules associated with it. On an average, we see the tax slab increasing from 15% to 18% for most of the services. While this may translate to higher cost of services to the end consumer, GST also presents a whole lot of opportunities, pushing ease of business.
Services Sector in India: An Overview
India is a strong services-led economy with the sector generating a significant chunk of employment opportunities and contributing to the GDP. It contributed around 66.1% of India’s Gross Value Added (GVA) growth in 2015-16, is the biggest magnet for Foreign Direct Investment (FDI), and an important net foreign exchange earner. Some of the core areas of service are IT and ITES, banking and financial services, outsourcing, research and development, transportation, telecommunications, real estate and professional services.
Some of the positive impacts of GST on service providers are:
Clear distinction between goods and services: The old regime does not clearly distinguish between goods and services, leading to many instances of double taxation. For example, software is often treated as a good and as a service. The new regime clearly distinguishes goods from services, and also defines principal supply, composite supply, and mixed supply separately. For example, when an individual books a Rajdhani train ticket which includes meals, it involves a composite supply wherein the ticket and the meals cannot be sold separately. Since the transportation of the passenger is the principal supply, the rate of tax will only be charged on the ticket. Alternatively, for items that can be sold separately, but are sold together, like a hamper of snacks and aerated drinks, the rate of tax applicable on the higher product will be levied on the composite supply. There are also separate definitions for supply of software, works contracts, and leasing transactions to bring in more clarity and transparency on their taxation rules.
Streamlining of taxation for intra-state service providers: Due to the state level taxes being subsumed, it will become easier for service providers that operate within the state to know their tax obligations better. Such companies can move away from multiple tax calculations. For example, a CD with software incurs Excise, Service Tax, and VAT under the old regime; this is simplified to one unified rate under GST, making tax calculations and administration easier for intra-state service providers.
Input credit facility: VAT payment under the old regime was not eligible for setting off against output liabilities. The input credit facility is now made available to service providers as well, wherein tax paid on any inputs can be claimed and adjusted against tax paid on output. This will result in direct cost savings for service providers and may even offset the expected rise in end pricing. For example, an AC fitter who paid tax on the raw material for AC fittings (pipe, tape, solder etc.) will be able to claim that tax, and end up spending less on the cost of fitting the AC. This cost advantage can spill over to the customer as well.
Regularised return filing: The old service tax system required two half-yearly returns for services businesses. Under GST, this has been replaced by a number of returns provisions, depending on the type of taxpayer and the type of business:
|Return||Type of tax payer||Timeline of filing return|
|GSTR 1||For outward supplies of sale (for registered taxable person)||By 10th of the next month|
|GSTR 2||For inward supplies received by a taxpayer (for registered taxable person)||By 15th of the next month|
|GSTR 3||Monthly return for registered taxable person (except for Compounding Taxpayer)||By 20th of the next month|
|GSTR 4||Quarterly return for Compounding Taxpayer/Composition Supplier||By 18th of the next month|
|GSTR 5||Periodic return by Non-Resident Foreign Taxpayer||By 20th of the next month|
|GSTR 6||Return for Input Service Distributor (ISD)||By 13th of the month succeeding the quarter|
|GSTR 7||Return for Tax Deducted at Source (TDS)||By 10th of the next month|
|GSTR 8||Annual Return for e-commerce operator||By 10th of the next month|
While a shorter timeline for filing returns might seem overwhelming, regularisation in return filing will result in better streamlining of taxes. Since all these returns are required to be submitted online through a common portal provided by GSTN, the process is simplified and will help the government weed out regular defaulters. This in turn will result in a major boost in the contribution of the Service sector to the GDP.
Service providers, however, are concerned about the following aspects:
- State-wise registration will be required: In the old regime, a service provider could operate with a single place of registration, since services were taxed only by the Central government. For example, if an IT services provider was present across states, they could carry out tax and delivery transactions from the main location. However, now a service provider that is offering services across states must register each place of business separately in each state. This is because the new GST regime entails taxation of services at “location of service recipient”, which will differ for different states. This means service providers will need to register afresh in new states and then carry out tax transactions separately in each state. For example, an IT company like TCS that has a widespread presence across states will need to decentralise service delivery.
- Decentralised reporting will add to costs: Under GST, the “location of service recipient” is the key criterion for how a service will be taxed. Tax considerations will be related to the place the service is being delivered, and even a pan-India service provider with several “locations of service” will need to maintain state-wise records of input credit, audits, service consumption, etc. For example, earlier a service provider like TCS would enter into a single contract with the client, based on its main location, and then would discharge service tax based on the single-service tax registration model. GST will decentralise service delivery models, ensuring various TCS units adopt their own tax reporting and tax management. While this need for decentralised tax tracking and processing is an immediate cost to service providers, it presents a very real opportunity to streamline reporting and compliance measures for the future.
GST offers clear benefits to the services sector, and while some of these measures entail additional cost and effort in the short term, businesses can look forward to simpler operations with the new taxation laws.
All in all, services industries must gear up for better ways to manage business. Now is the time for them to equip themselves with the right people, processes and technologies, and emerge as service providers of the future.
[maxbutton id=”4″ url=”https://safe.capitalfloat.com/cf/default/register?utm_source=blog&utm_medium=button&utm_campaign=blog-content-button&utm_content=implications-gst-services” text=”I want Business Loan” ]
Oct 24, 2018