Receivables & Collections for Startups and SaaS in Austin

Receivables and collections for a SaaS startup in Austin is a different job from managing receivables at a typical service business, because a subscription company collects money through two channels that behave nothing alike, and each one leaks cash in its own way. The first channel is self-serve, where customers pay by credit card on a recurring charge. Here the problem is not customers refusing to pay, it is cards that fail. A card expires, hits its limit, or gets declined by a bank, and the recurring charge bounces even though the customer had every intention of staying. This is called involuntary churn, and it is invisible unless someone is measuring it. The second channel is enterprise, where a customer signs an annual contract and asks to be invoiced on terms. Now the problem is delay. A corporate accounts-payable department pays on net-30 or net-60, and in practice those invoices often stretch toward ninety days, so cash you earned in January may not arrive until spring.

Why does this matter for an Austin startup in particular? Because the company is almost certainly burning venture money against a fixed runway, and cash sitting in receivables is cash not covering the burn. A startup paying office rent and engineering salaries goes through its bank balance quickly, and venture funding is meant to buy months of runway, not to sit frozen in an accounts-receivable line. Every week an invoice goes uncollected is a week of runway lent to a customer for free. The Austin advantage is on the other side of the ledger, because Texas charges no state personal income tax and no state tax on a founder’s share of pass-through profit, so unlike a founder in California or New York, an Austin founder does not watch a big slice of collected revenue disappear to a state. That makes collecting efficiently pure upside, but it does nothing to fix a slow enterprise book, which can still force a founder back into fundraising months earlier than planned.

The two channels demand different tactics, which is the core of why generic collections advice fails a SaaS company. Chasing a failed $59 card is a technical retry-and-recover problem solved with dunning software and smart retry timing. Chasing a late $80,000 enterprise invoice is a relationship-and-terms problem solved with follow-up cadence, escalation, and sometimes renegotiated payment schedules. Run them the same way and you either annoy enterprise buyers with robotic dunning emails or leave thousands in failed cards unrecovered because nobody built the retry flow. The self-serve book rewards automation and volume discipline, while the enterprise book rewards judgment about which relationships to press and which to give room.

There is a compounding effect too. Failed cards that go unrecovered do not just cost you this month’s charge, they cost every future month that customer would have paid, so a single unrecovered $80 subscription can quietly represent close to a thousand dollars of lost lifetime value. A late enterprise invoice, by contrast, will usually be paid eventually, so its cost is the time value of the money and the operational drag of chasing it rather than an outright loss. Understanding that difference is what lets us prioritize correctly instead of spending equal effort on a permanent loss and a temporary delay.

Here is a concrete illustration of the stakes. Imagine an Austin SaaS company with 1,500 recurring subscriptions averaging $90 a month, plus a dozen enterprise accounts on annual invoices totaling $600,000 a year. If 5 percent of the recurring charges fail monthly, that is 75 failed charges worth about $6,750 of monthly recurring revenue, over $80,000 annualized, hanging on whether a dunning process exists. Meanwhile, if the enterprise invoices average sixty days to collect instead of thirty, roughly $50,000 of cash is perpetually locked up in float that better terms could free. We separate these books, run each with the right playbook, and reconcile the results to your bookkeeping. The IRS accounting-methods guidance and the Texas Comptroller franchise tax rules both bear on how and when that revenue is recognized and reported.

Dunning is the systematic process of recovering failed recurring payments, and for a SaaS startup it is the single highest-return piece of a receivables and collections function, because the money it recovers is money you already earned and would otherwise lose for no reason. When a subscription charge fails, the customer usually did not decide to leave. Their card expired, or hit a limit, or a bank flagged the transaction. Payment processors make a token attempt or two and then give up, and if nothing else happens the subscription simply lapses. The customer is gone, not because your product failed them but because a routine payment hiccup was never followed up. Multiply that across hundreds or thousands of subscriptions and involuntary churn becomes one of the largest and most fixable leaks in the business.

A proper dunning process attacks the problem on two fronts. The first is intelligent retry timing. Rather than retrying a failed card immediately and failing again, a good system retries at times when the charge is more likely to succeed, after a weekend, after a payday, spaced across several days, giving temporary limits and holds time to clear. The second front is communication. The customer gets a clear, friendly sequence of emails letting them know the payment did not go through and asking them to update their card before they lose access. The tone matters, because these are customers you want to keep, not deadbeats to harass. Combine smart retries with good email and a large share of failed charges convert back to paying customers within a couple of weeks.

The reason this belongs with a firm that watches your books rather than being left entirely to software is reconciliation and measurement. You need to know what failed, what recovered, what was ultimately written off, and what the net recovery rate is, because that rate is an operating metric an Austin venture investor will ask about when they dig into your retention. Recovery has to be tied back to the accounting so recovered revenue is recognized correctly and genuinely lost revenue is removed from the receivables balance. Software runs the retries, but someone has to close the loop and make the numbers honest.

Consider the math on a company with 2,500 subscriptions at an average of $70 per month, where 6 percent of charges fail in a typical month. That is 150 failed charges representing $10,500 of monthly recurring revenue at risk. With no dunning, most of that becomes churn, roughly $126,000 a year of lost recurring revenue. With a disciplined dunning process recovering, say, 60 percent, you bring back about $6,300 a month, more than $75,000 a year, that would otherwise have evaporated. For a startup measuring runway in months, recovering three-quarters of that leak is meaningful cash that buys time, and because Texas takes no income tax, every recovered dollar stays in the business rather than partly funding a state bill. We build the retry and email sequence, reconcile recoveries against write-offs, and fold the results into your monthly financial reporting. The IRS guidance on business income and the Texas Comptroller of Public Accounts govern how recovered and written-off amounts are treated.

Receivables and collections management protects an Austin startup’s runway by converting revenue you have earned into cash you can actually spend, faster and more reliably, and in a business funded by a finite pile of venture money that conversion speed is close to a survival metric. Runway is how many months you can operate before the money runs out. It is a function of your cash balance and your burn rate, and receivables sit right in the middle of that equation. Revenue you have booked but not collected does nothing to extend your runway, because you cannot pay an engineering salary or an office lease with an accounts-receivable entry. Only collected cash counts. So the faster receivables turn into cash, the more months of runway you effectively have from the same amount of business.

The metric that captures this is days sales outstanding, or DSO, the average number of days between billing a customer and collecting the payment. A high DSO means your money spends a long time in other companies’ bank accounts before it reaches yours. For an enterprise-heavy SaaS company, DSO can quietly balloon as customers stretch net-30 terms to sixty or ninety days, and each additional week is runway you are lending to your customers interest-free. Bringing DSO down, through tighter terms, prompt invoicing, disciplined follow-up, and occasional renegotiation, directly frees cash and extends the runway without closing a single new deal. It is one of the few levers that improves your cash position using business you have already won.

There is an Austin edge to this, and it runs the founder’s way. Because Texas has no state personal income tax and its franchise tax leaves companies under roughly $2.65 million in revenue owing nothing, an Austin founder keeps more of every collected dollar than a founder in a high-tax state, so improving collections drops straight to usable runway without a state taking a cut. A founder who moved to Austin for the talent and the venture density inherits a cost base without a state income layer, which means receivables discipline is pure gain rather than partly offset by taxes on the collected revenue. Slow collections still hurt, because cash you have not collected cannot fund payroll, but the reward for fixing them is not diluted by a state income charge.

Put numbers to it. Suppose a startup bills $1.2 million a year, mostly on enterprise invoices, and its DSO sits at 75 days. That means roughly $246,000 of cash is tied up in receivables at any moment. Cut DSO to 45 days through better terms and follow-up, and the tied-up amount drops to about $148,000, freeing nearly $100,000 of cash that moves onto the balance sheet and directly buys additional runway. At a burn rate of $150,000 a month, that freed cash is close to three extra weeks of operating life, earned purely by collecting faster, and none of it is lost to a state income tax. We track DSO, work the aging report, and tie the timing into your financial reconciliation. The IRS Publication 538 on accounting methods and the Texas Comptroller of Public Accounts frame how the timing of collections interacts with taxable income and the franchise report.

Receivables and collections interact with deferred revenue and ASC 606 in a way that trips up almost every SaaS founder who has not had it explained, and getting it straight is what keeps a startup’s balance sheet honest enough to survive diligence in an Austin fundraise. The confusion starts because three different things, cash, revenue, and receivables, all move on different timelines in a subscription business, and ASC 606 is the accounting standard that forces you to keep them separate. ASC 606 says you recognize revenue as you satisfy your obligation to the customer, which for SaaS means as you deliver the software over the subscription term, not when the cash arrives and not when you send the invoice. That single rule creates the interaction with receivables.

Walk through the two upfront-invoice cases. First, a customer pays an annual subscription in advance. You now hold cash, but you have delivered only a fraction of the year of service, so most of that payment is deferred revenue, a liability, recognized into income month by month. There is no receivable because they already paid. Second, and this is where it gets subtle, a customer signs an annual deal and asks to be invoiced but has not yet paid. Now you have a receivable, because they owe you, and you also have deferred revenue, because you have not yet delivered the service you will recognize over the year. The same contract sits on the balance sheet as both an asset and a liability at once, and as the year progresses the receivable is reduced by payments while the deferred revenue is reduced by service delivery, on two separate clocks.

Why does this matter beyond bookkeeping elegance? Because a founder who conflates these numbers reports figures that fall apart under scrutiny. Booking an entire annual invoice as revenue on day one overstates revenue and growth. Treating uncollected invoices as if the cash were in hand overstates the real cash position. When a well-resourced Austin investor or acquirer runs diligence, they recalculate all of this correctly, and discrepancies between what you reported and what the standard requires undermine confidence in every other number in your deck. Clean receivables and clean revenue recognition are two halves of a balance sheet that holds up. There is a Texas angle too, but it cuts in the founder’s favor, since Texas has no state income tax and the franchise tax only reaches companies above roughly $2.65 million in revenue, so the recognition discipline that satisfies an acquirer is not also feeding a state income charge the way it would in California.

Here is a worked example. A SaaS company signs a $120,000 annual contract in March and invoices the customer, who pays in two installments, $60,000 in April and $60,000 in July. On signing, the company records a $120,000 receivable and $120,000 of deferred revenue. Starting in March it recognizes $10,000 of revenue each month as it delivers the service, drawing down deferred revenue. Separately, the receivable falls to $60,000 in April and to zero in July as payments land. By December, deferred revenue is fully recognized and the receivable is long gone, but at any midyear moment the two numbers are different and both are correct. Miss this and you might report $120,000 of March revenue and no receivable discipline, a double error. We keep the receivable ledger and the deferred-revenue schedule reconciled inside your bookkeeping. The IRS accounting-periods guidance and the IRS accrual-method rules govern the tax side of this timing.

Receivables and collections touch the Texas franchise tax for an Austin startup only lightly, and understanding why is part of understanding how much simpler the Texas state picture is than what founders face in California or New York, because Texas has no personal income tax and its franchise tax leaves most young companies owing nothing. Texas does levy a franchise tax, sometimes called the margin tax, on business entities, but it only applies once a company crosses roughly $2.65 million in annualized revenue. Below that threshold, an entity files a no-tax-due report and pays the state nothing, so a typical early-stage startup has no franchise tax to plan around, only a report to file with the Texas Comptroller. There is no California-style $800 annual minimum and no LLC gross-receipts fee, so the state charge that dominates a Los Angeles founder’s planning simply does not exist here.

Where receivables and recognition come in is at the point a company grows past that revenue line. The franchise tax, when it applies, is calculated on a margin figure derived from revenue, and for an accrual-basis company revenue is recognized as it is earned rather than when cash arrives. That means how receivables, unbilled revenue, and deferred revenue are handled feeds the revenue figure the margin tax is measured against, once the company is large enough to owe it. A company recognizing revenue sloppily, booking prepayments too early or missing what it has earned, could misstate the base. But for the great majority of startups, which sit below the threshold, this is a filing exercise rather than a tax bill, and the receivables work is about cash and diligence rather than about a state charge.

The practical result is that an Austin founder gets to focus receivables and collections almost entirely on the things that actually matter for a startup, collecting the cash that funds runway and keeping the revenue numbers clean for the board and for investors, without a meaningful state tax consequence riding on the recognition timing. That is a genuine simplification compared with a California LLC, whose gross-receipts fee turns every recognition decision into a state-cost decision. The federal picture still applies, and a C corporation pays the flat 21 percent federal rate on profit it actually earns, but the state side stays light.

Here is the math that shows the contrast. Suppose an Austin SaaS company has $1,000,000 of revenue for the year. In California, an equivalent LLC would owe the $800 minimum plus a gross-receipts fee running into the low thousands, all driven by recognized revenue, so collections and recognition would feed a real state bill. In Texas, that same $1,000,000 company is well under the roughly $2.65 million franchise threshold, so it files a no-tax-due report and owes the state zero, and its receivables discipline affects only its cash position and its diligence readiness, not a state tax. If the company later grows past the threshold, we make sure the recognized-revenue figure behind the margin tax is accurate. We keep revenue recognition clean and coordinate the Texas report through tax strategy consulting. The Texas Comptroller franchise tax page and the Texas Comptroller of Public Accounts set out the governing rules.