Tax Compliance for Startups and SaaS in Miami

Sales-tax nexus is the compliance issue that catches Miami SaaS founders most off guard, because a company based in a state that does not tax its software can still owe sales tax in many other states, and getting this wrong quietly builds up a liability that surfaces during diligence or an audit. The rules changed fundamentally with the Supreme Court’s Wayfair decision in 2018, which is the starting point for understanding why a Florida company has to think nationally rather than assume its home-state simplicity travels with it.

Before Wayfair, a state could require a business to collect its sales tax only if the business had a physical presence there, an office, employees, or inventory. Wayfair overturned that, allowing states to impose sales-tax collection on remote sellers based purely on economic activity in the state. Most states adopted an economic-nexus threshold, commonly around $100,000 of sales or 200 separate transactions into the state in a year, and once a seller crosses that line it is required to register, collect the state’s sales tax, and file returns, even with no physical presence whatsoever. For a SaaS company selling subscriptions nationwide, this means dozens of states can potentially require collection, and the exposure grows silently as sales scale.

The SaaS-specific complication is taxability. States do not agree on whether software-as-a-service is a taxable product. Some states tax SaaS outright, some exempt it, and some tax it only in certain configurations, and these rules change over time. So a Miami SaaS company faces two questions in every state, whether it has crossed the economic-nexus threshold, and whether SaaS is taxable there, and it must register and collect only where both are true. Florida itself does not tax most SaaS and has no state income tax, so the home state is simple, but that simplicity does not extend to the states the company sells into, and marketplace facilitator laws add yet another layer where a platform sometimes collects on the company’s behalf.

Here is a concrete example. Suppose a Miami SaaS company sells $120,000 of annual subscriptions to customers in a state that taxes SaaS and sets its economic-nexus threshold at $100,000. Having crossed the threshold, the company must register with that state, begin collecting the state’s sales tax on those subscriptions, and file sales-tax returns there, despite having no office or employee in the state. If the company had instead sold that same $120,000 into a state that exempts SaaS, it would owe nothing and might not even need to register. Multiply this analysis across every state the company sells into and the compliance map gets complex quickly. We track the company’s sales by state against each state’s threshold and taxability rules, register where collection is required, set up and file the returns, and monitor the thresholds as sales grow, coordinating the exposure with the planning in tax strategy consulting. The economic-nexus and sales-tax framework is summarized in the IRS sales and use tax overview, and Florida’s own rules are at the Florida Department of Revenue.

For most pure SaaS products a Miami startup owes no Florida sales tax on its core subscriptions, but the answer is not a flat no, because Florida sales and use tax reaches several things a startup does around its software, and the county surtax adds to the rate wherever the tax does apply. Understanding where the line falls is what keeps a company from either over-collecting from customers or missing a genuine obligation of its own.

Florida’s state sales and use tax is 6 percent, and each county levies a discretionary surtax on top, so in Miami-Dade the combined rate on taxable transactions sits above the 6 percent state figure. The key point for a SaaS company is that Florida generally does not treat software-as-a-service delivered remotely as a taxable sale, so the recurring subscription revenue from the company’s core product usually is not subject to Florida sales tax. That is a genuine advantage over states that do tax SaaS, and it means the company often has no Florida sales tax to collect from its customers on the software itself, which simplifies its home-state billing.

Where Florida tax does bite is around the edges. If the company sells anything tangible, branded merchandise, hardware, or a physical product, that sale can be taxable, and if it buys goods for resale it needs a Florida resale certificate to buy them tax-free and then collect tax when it sells them. More commonly for a startup, use tax applies to taxable items the company buys for its own use when the seller did not charge Florida tax. If the company sets up a Miami office and buys furniture, computers, and equipment from out-of-state vendors, or buys certain taxable software or services from a vendor that collected no Florida tax, the company owes Florida use tax on those purchases and must self-assess and remit it rather than wait to be billed. This is the piece companies most often overlook, because it requires the company to police its own purchases rather than simply collect from customers.

Here is a concrete example. Suppose a Miami SaaS startup furnishes a new office and buys $40,000 of desks, computers, and equipment from out-of-state vendors who charged no Florida sales tax. The company owes Florida use tax at 6 percent plus the Miami-Dade surtax on that $40,000, which it has to calculate and remit itself, so the tax is roughly $2,400 in state tax plus the county surtax amount, all self-assessed. Meanwhile, its core SaaS subscriptions sold to customers generally carry no Florida sales tax. We determine exactly where the company has a Florida collection duty or a use-tax liability, register it with the state if required, handle the use-tax self-assessment on out-of-state purchases, and keep the Florida filings current, tying the analysis to the records our bookkeeping team maintains. The Florida sales and use tax rules, including the discretionary surtax, are explained by the Florida Department of Revenue, and the broader framework is in the IRS sales and use tax overview.

The 1099 rules are a core part of tax compliance for a Miami startup because a young company pays many people who are not employees, and the federal information-reporting system requires the company to report much of that spending, with penalties for getting it wrong. The rules changed for 2026 in a way that helps, raising the main reporting threshold, but the obligation to collect the right information and file on time remains, and Florida’s lack of a state income tax does nothing to remove this federal duty.

The central form is the Form 1099-NEC, used to report payments for services to independent contractors and unincorporated service providers. For payments made in 2026, the reporting threshold rose from $600 to $2,000, so the company generally has to issue a 1099-NEC to any contractor or service provider it paid $2,000 or more during the year. The higher threshold means fewer small payments trigger a filing, but any meaningful contractor relationship will still cross it. Payments to corporations are generally exempt, with some exceptions such as legal fees, which is one reason knowing the payee’s entity type matters before the first payment goes out.

The information the company has to gather up front is what makes the filing possible. Before paying a contractor, the company should collect a Form W-9, which provides the payee’s legal name, entity type, and taxpayer identification number. Without a valid W-9, the company may be required to apply backup withholding to the payments and can face penalties for filing an information return with a missing or incorrect identification number. There is also a separate regime for payments made through third-party payment networks and card processors, reported on Form 1099-K, which for 2026 reverted to a threshold of $20,000 and 200 transactions, so payments the company makes through such a platform may be reported by the platform rather than by the company, and the company has to avoid double-reporting the same payment on both forms. Deadlines matter too, because the 1099-NEC is due to both the recipient and the IRS at the end of January, a tight window right after year end.

Here is a concrete example. Suppose a Miami SaaS startup engages a contract developer and pays that developer $60,000 over the course of the year by direct payment rather than through a card platform. The company should have collected a W-9 from the developer at the start, and after year end it issues the developer a Form 1099-NEC reporting the $60,000 and files a copy with the IRS. If instead it had paid the developer through a third-party platform, the platform might issue a 1099-K and the company would not duplicate it. Getting the names, identification numbers, and amounts right across all the company’s contractors is what keeps January’s filing clean and penalty-free. We collect the W-9s during the year, track reportable payments as they occur, prepare and file the 1099s, and coordinate the worker-classification question with our payroll compliance team so contractors and employees are correctly distinguished. The reporting rules are described in the IRS Form 1099-NEC guidance, and the worker-status framework is in the IRS worker classification guidance.

The tax compliance calendar for a Miami startup with a Delaware C corporation spans several jurisdictions, and keeping every date is what separates a clean company from one that collects penalty notices, so mapping the whole calendar up front is one of the most useful things compliance does. Because the company is a Delaware entity doing business in Florida and selling across the country, its filings come from the federal government, Delaware, Florida, and every state where it has crossed a sales-tax threshold, and the dates do not line up neatly with one another.

Start with Delaware. As a Delaware corporation, the company owes the Delaware annual franchise tax and report by March 1 each year, no matter where it actually operates. This deadline is separate from any income tax and catches founders who forget the company has an obligation to its state of incorporation. Then Florida. As a company doing business in Florida, it files the Florida corporate income tax return on a schedule generally tied to the federal due date, with a Florida extension available, and it files any Florida sales-and-use-tax returns on the frequency the state assigns, which can be monthly, quarterly, or annual depending on volume, with larger collectors filing more often.

Federally, the calendar has several recurring items. The Form 1120 corporate income tax return is generally due the fifteenth day of the fourth month after the close of the tax year, with a six-month extension available. If the company has employees, the quarterly payroll returns run on their own cycle throughout the year, and annual wage statements are due at the start of the year. The 1099s for contractors are due at the end of January. On top of all of this, every state where the company crossed an economic-nexus threshold for sales tax has its own registration and return schedule, so a company selling into many states can have many separate sales-tax return deadlines scattered through the year.

Here is a concrete picture of a single year. Suppose a Miami SaaS startup has employees, uses contractors, and has crossed the sales-tax threshold in four states that tax SaaS. Its calendar includes the 1099s and wage statements in January, the Florida and out-of-state sales-tax returns on their assigned frequencies through the year, the Delaware franchise report by March 1, the federal Form 1120 and the Florida corporate return by their spring deadlines or on extension, and the quarterly payroll returns each quarter. That is easily a dozen or more distinct filing obligations across five or more jurisdictions in one year, and missing even one, particularly a sales-tax return, can trigger penalties that exceed the tax owed. We build the company’s compliance calendar across the federal, Delaware, Florida, and multi-state obligations, prepare and file each return on time, and keep the registrations current as the company grows into new states, coordinating the income-tax filings with our corporate returns team. The Delaware franchise deadline is set by the Delaware Division of Corporations, and the Florida corporate return schedule is described by the Florida Department of Revenue.

Yes, a Miami SaaS startup can have income-tax obligations in states beyond Florida even though Florida itself imposes no personal income tax, because state corporate income tax nexus is a separate question from sales-tax nexus, and a growing company that sells and hires across the country can find itself filing corporate returns in several states. This is one of the less obvious pieces of tax compliance, and it grows in importance as the company scales and adds people and customers outside Florida.

The starting point is that nexus for corporate income tax is determined state by state and does not depend on Florida having no income tax. A company creates income-tax nexus in a state through physical presence, such as an office or an employee working there, and many states also assert economic nexus for income tax based on sales into the state above a threshold, similar in spirit to the Wayfair sales-tax rules but under each state’s own income-tax law. So a Miami company with a remote engineer in Georgia, or with heavy sales into California, may have created income-tax nexus in that state and be required to file a state corporate return and apportion a share of its income there, and public-law protections that once shielded mere solicitation of sales generally do not cover a SaaS company with employees or servers in a state.

Apportionment is what determines how much income each state can tax. A company with nexus in multiple states does not pay full income tax to each one, it apportions its total income among the states based on formulas that weigh where its sales, property, and payroll are, with most states weighting sales heavily. For a SaaS company, the sales factor, where its customers are, usually drives the result. The company files in each state where it has nexus and reports the apportioned share, so the same income is divided among the states rather than taxed in full by each, though the rules and rates differ and some states impose a minimum tax even in a loss year.

Here is a concrete example. Suppose a Miami SaaS startup becomes profitable, employs a developer in Georgia, and makes sizable sales into California and New York. Florida taxes the Florida-apportioned share of its corporate income at 5.5 percent, but the company may also have income-tax nexus in Georgia through the employee and in California and New York through sales, requiring it to file corporate returns in those states and apportion income to each. If 20 percent of its sales are into California, roughly that share of income might be apportioned and taxed at California’s corporate rate, and similar analysis applies to the other states. The company’s total state income tax is the sum of these apportioned pieces, and each requires a return. We determine where the company has income-tax nexus, handle the apportionment, prepare the multi-state corporate returns, and keep the whole footprint consistent, coordinating with our corporate returns team. The multi-state framework builds on the same nexus principles summarized in the IRS sales and use tax overview, and the Florida corporate apportionment rules are explained by the Florida Department of Revenue.