Tax Compliance for Startups and SaaS in Austin

Tax compliance for a startup in Austin covers a set of filings that is lighter on the state side than in most major startup cities, because Texas has no state or city income tax, but still includes a full slate of federal, Delaware, and information-return obligations that a founder cannot ignore. Understanding the scope is the first step, because the filings that get missed are usually the ones a founder did not know existed, especially the Delaware and 1099 pieces.

At the income-tax level, an Austin Delaware C corporation answers to three authorities rather than four. The IRS wants the federal Form 1120, which taxes corporate income at the flat 21 percent rate, though an early startup that spends more than it earns often owes nothing federally and files to bank the loss. Delaware, as the state of incorporation, requires an annual franchise tax payment and an annual report regardless of where the company operates. And Texas requires a franchise tax report, which owes nothing below roughly 2.47 million dollars in revenue, so a young company files a no-tax-due report. What is notably absent is any state or city income tax return, because Texas has neither, so unlike a New York company that files state and city corporate returns on top of the federal one, the Austin company has no such returns to prepare.

Beyond income tax sit the information and employment filings, which are the same everywhere. If the company has employees, it files quarterly and annual payroll returns and issues W-2s. If it pays contractors, it issues Form 1099-NEC to unincorporated payees above the reporting threshold, which rose to 2,000 dollars for 2026. Payments that flow through a card processor or payment app are reported on Form 1099-K under its own threshold. And depending on where the company sells its SaaS product, it may have to register for and collect sales tax in multiple states, including Texas, which taxes SaaS as a data-processing service in part.

Coordination across all of these is what keeps a company clean. The numbers on the corporate return have to agree with the financial statements, the payroll returns have to reconcile to the W-2s, and the 1099s have to match what the books show was paid to contractors, because the authorities cross-check the forms against each other and inconsistencies trigger notices.

Here is the scope in a single year for a small company. Suppose a pre-revenue Austin SaaS startup has a federal loss, three employees, and five contractors. It files a Form 1120 showing the loss and owing no federal tax, pays the Delaware franchise tax and files the Delaware report, files a Texas franchise report showing no tax due, files quarterly and annual payroll returns and issues three W-2s, and issues 1099-NEC forms to the contractors it paid more than 2,000 dollars. That is a full set of filings across three authorities, but with actual income tax owed nowhere in a loss year. We prepare and coordinate all of them and tie the entity treatment back to our entity formation and structuring team. The corporate return is described in the IRS Form 1120 guidance, and the Texas franchise obligation sits with the Texas Comptroller.

An Austin startup has fewer tax compliance filings than one in New York or California because Texas imposes no state personal income tax and no state corporate income tax, and no Texas city imposes an income tax either, so the entire layer of state and city income-tax returns that burdens companies in those states simply does not exist for an Austin company. This is one of the concrete compliance advantages of basing a startup in Texas, and it shows up clearly when you compare the filing lists side by side.

Consider what a New York City startup files. On top of the federal Form 1120 and the Delaware franchise report, a New York company files a New York State corporate franchise tax return and a separate New York City Business Corporation Tax return, and each of those carries a minimum tax that is owed even in a loss year, so the company writes checks to Albany and to the city regardless of profit. A California company similarly files a California corporate return and owes California’s 800 dollar minimum franchise tax every year. In both places, the state and local income-tax layer means more returns, more minimums, and more deadlines.

An Austin company skips that entire layer. Because Texas has no corporate or personal income tax, there is no Texas income-tax return for the company, and because no Texas city levies an income tax, there is no city return either. What remains on the Texas side is the franchise tax report, which owes nothing below the revenue threshold, so a young company files a single no-tax-due report rather than multiple income-tax returns with minimums attached. The result is a shorter filing list and, in the early years, no state-level tax actually owed.

The federal and Delaware obligations are unchanged, though, and that is worth being clear about. An Austin startup still files the same federal Form 1120, still owes and files the Delaware franchise tax and report, and still handles the same federal information returns and payroll filings as a company anywhere. So the Texas advantage is specifically the elimination of the state and city income-tax returns, not a reduction in the federal or Delaware compliance that every venture-backed startup shares.

Here is a concrete comparison. Suppose two identical pre-revenue SaaS startups, one in Austin and one in New York City, each a Delaware C-corp with a loss for the year. Both file the federal 1120 and the Delaware report. The Austin company then files only a Texas franchise report showing no tax due, and owes no state or city income tax. The New York company additionally files a New York State corporate return and a New York City Business Corporation Tax return, and pays the state and city minimum taxes even though it lost money, so it writes checks and files returns the Austin company never has to. Over the early years, that difference is real money and real administrative time. We handle whichever set applies and coordinate the filings through our corporate returns team. The federal return is described in the IRS Form 1120 guidance, and the absence of a Texas income tax is confirmed by the Texas Comptroller.

Contractor information returns are a routine but easily botched part of tax compliance for an Austin startup, and the rules shifted for 2026, so a company that ran its 1099 process on the old thresholds needs to update it. Startups lean heavily on freelancers and fractional talent, which means most SaaS companies have a meaningful stack of 1099s to issue, and the penalties for getting them wrong scale with the number of contractors.

The core obligation is that a business paying an unincorporated person for services during the year must report those payments to the IRS and to the contractor on Form 1099-NEC. For payments made in 2026, the reporting threshold rose from the long-standing 600 dollars up to 2,000 dollars under the new law. So a company that pays a freelance designer 1,500 dollars for a project no longer has to issue a 1099 for that payment, while a fractional developer paid 30,000 dollars over the year clearly must receive one. The higher threshold reduces the number of small 1099s but does not change the obligation for meaningful payments.

The step founders skip is collecting a Form W-9 from each contractor before paying them. The W-9 provides the contractor’s legal name and taxpayer identification number, which the company needs to file an accurate 1099. Without it, the company may be required to apply backup withholding to the contractor’s payments at a flat statutory rate, and it risks filing information returns with missing or incorrect identification numbers, which the IRS penalizes separately. Collecting the W-9 at onboarding, before the first payment goes out, is the simple fix, and it also settles whether the payee is incorporated, since payments to most corporations are exempt from 1099-NEC reporting.

Payment channel matters too, and it is a distinction founders routinely get wrong. Amounts a company pays contractors directly, by check, ACH, or bank transfer, are the company’s responsibility to report on 1099-NEC. Amounts paid through a third-party payment platform or a card processor are reported by that platform on Form 1099-K instead, whose threshold reverted to more than 20,000 dollars and more than 200 transactions. The company has to know which of its payments went through which channel, because a contractor paid partly directly and partly through a platform could otherwise be double-reported or missed entirely. For an Austin company, there is no state 1099 equivalent to layer on, because Texas has no income tax, so the whole information-return obligation is federal.

Here is what carelessness costs. Suppose a startup paid eight contractors more than 2,000 dollars each during 2026 but never collected W-9s and filed no 1099s. The IRS imposes penalties both for failing to file the returns with the government and for failing to furnish them to the recipients, and those per-form penalties, applied to eight contractors on both counts, can climb into the thousands of dollars, all for paperwork that a W-9 at onboarding and a January filing would have handled for almost nothing. We collect W-9s at the start, track each contractor’s payments against the 2,000 dollar threshold through the year, and file the 1099-NEC forms and reconcile any 1099-K by the deadlines, coordinating with the worker-classification review our payroll compliance team performs. The reporting rules are in the IRS Form 1099-NEC guidance, and the broader small-business filing duties are described in the IRS small business center.

Sales tax is the tax compliance area that most often blindsides a growing SaaS startup, because whether a software subscription is taxable depends on the state, and a company selling nationwide has to deal with many different answers at once, including a Texas rule that taxes SaaS in part. An Austin company that assumes its product is either taxable everywhere or nowhere is usually wrong on both counts, and the exposure builds quietly until a state sends an assessment.

The framework changed with the Supreme Court’s Wayfair decision, which let states require out-of-state sellers to collect sales tax once they cross an economic-nexus threshold in the state, typically a dollar amount of sales or a number of separate transactions during a year. Physical presence is no longer required, so an Austin SaaS company with customers spread across the country can trigger collection duties in many states purely by selling into them. The first job of compliance is therefore tracking sales by state and knowing where the company has crossed each threshold.

The second job is determining taxability, which varies sharply and includes a wrinkle right at home. Texas treats SaaS as a taxable data-processing service, but it taxes only a portion of the charge, applying the state sales tax rate of 6.25 percent plus local additions to part of the subscription value, so a Texas customer’s SaaS bill can carry some Texas sales tax. Chicago, by contrast, reaches software and SaaS through its Personal Property Lease Transaction Tax at roughly 9 percent, a different mechanism entirely, and many other states exempt SaaS from sales tax altogether. So the identical subscription can be partly taxable in Texas, taxed under a lease-transaction tax in Chicago, and completely exempt in a state like California, which means the company cannot apply one rule everywhere.

Once nexus and taxability are established for a state, the company has to register with that state’s tax authority, configure its billing to charge the correct tax to customers there, file periodic sales-tax returns, and remit what it collects. Setting this up before crossing thresholds is far cheaper than fixing it afterward, because sales tax not collected from a customer generally cannot be recovered from that customer later, so any uncollected liability comes out of the company’s own revenue.

Here is the exposure. Suppose an Austin SaaS company crosses another state’s economic-nexus threshold and continues billing its customers there without charging sales tax on the taxable portion of its subscriptions. A year later that state audits and assesses the uncollected tax. Because the company never charged its customers, it now owes that tax out of its own revenue, plus penalties and interest, and on a meaningful customer base that liability can reach tens of thousands of dollars that simply evaporate from the company’s cash. Had the company registered and charged correctly, the tax would have been the customers’ cost, not its own. We monitor sales against each state’s nexus threshold, determine where SaaS is taxable including the partial Texas treatment, handle the registrations, and configure billing to collect and remit correctly, coordinating the planning with our tax strategy consulting team. The Texas sales-tax treatment of SaaS is administered by the Texas Comptroller, and the broader small-business framework sits with the IRS small business center.

The tax compliance mistakes that create the biggest problems for Austin startups are usually failures of process rather than of arithmetic, the deadlines missed and registrations skipped because a founder was building a product and did not know an obligation existed. A few recur often enough to name, and because Texas removes the state income-tax layer, the ones that remain are concentrated on the federal, Delaware, and sales-tax sides.

The first is missing the Delaware franchise report, due March 1 every year. Founders who think of taxes as an April event are surprised by a Delaware deadline six weeks earlier, and missing it triggers a penalty plus interest and, worse, causes the company to lose good standing in Delaware. Loss of good standing can stall a financing or an acquisition, because investors and acquirers check it during diligence, so a forgotten report can hold up a deal until it is cured. The tax itself may be small, but the consequences of the lapse are not, and this is the single most common serious compliance slip for an Austin startup precisely because the tax is easy to dismiss.

The second is the sales-tax blind spot. A SaaS company grows its customer base across states, crosses economic-nexus thresholds without tracking them, and never registers or collects, building a liability for tax it should have charged customers but did not. When a state assesses that tax years later, the company pays it from its own pocket with penalties, and the amount can be large relative to a startup’s cash. This is easy to overlook in Austin because the founder may assume their home state does not tax SaaS, when in fact Texas taxes it in part and other states vary.

The third is the missed research-credit payroll election, which is less a penalty risk than a lost opportunity, but it costs real money. A pre-revenue startup that fails to compute its research credit and elect it against payroll taxes leaves cash on the table that could have extended its runway, and because the election is tied to the return filing, missing the return timing can forfeit the near-term benefit.

The fourth is inconsistency across filings. When the corporate return, the payroll returns, the W-2s, and the 1099s do not reconcile to each other and to the books, the mismatches invite notices, because the authorities cross-check the forms. A company that reports one payroll figure on its return and a different one across its W-2s is creating questions it will have to answer.

Here is what one lapse can cost. Suppose an Austin startup forgets its Delaware franchise report while raising a round. The direct penalty and interest might be a few hundred dollars, trivial on its own, but the company also shows as not in good standing in Delaware just as an investor runs diligence. The financing pauses while the company files back reports, pays the penalties, and restores good standing, a delay that can cost far more in momentum and legal fees than the tax ever would. We keep the full compliance calendar across the federal, Delaware, and Texas obligations, file every return and report on time, reconcile the filings to each other and to the books, and monitor sales-tax nexus so none of these gaps opens, coordinating the whole effort with our corporate returns team. The corporate filing rules are in the IRS Form 1120 guidance, and the Delaware franchise requirements sit with the Delaware Division of Corporations.