TRANSCRIPT 🔗
WEBVTT
00:00:09.439 --> 00:00:10.880
Welcome to Beyond the Ledger.
00:00:10.960 --> 00:00:12.720
I'm your host, Shardet Layfield.
00:00:12.880 --> 00:00:15.759
For software companies, growth can happen fast.
00:00:16.160 --> 00:00:19.519
New customers, new markets, and new revenue streams.
00:00:19.679 --> 00:00:25.920
But that growth can also create sales tax obligations that are easy to overlook and costly to ignore.
00:00:26.160 --> 00:00:29.519
To dive more into the details, let's start the conversation.
00:00:30.879 --> 00:00:40.640
Today I'm joined by Adrian Eccles, Director and Bennett Thrasher of State and Local Tax Practice to talk about the sales tax challenges facing SaaS and software businesses.
00:00:40.880 --> 00:00:53.359
We'll unpack where companies commonly get caught off guard, how Nexus and Ta's ability can change from state to state, what to do when you uncover past exposure, and where automation fits into the compliance picture.
00:00:53.679 --> 00:00:55.679
Adrian, welcome back to the show.
00:00:55.840 --> 00:00:56.479
I'm excited to be here.
00:00:56.640 --> 00:00:58.320
Hey Charlotte, good to be here again.
00:00:58.719 --> 00:01:03.840
Congratulations on your director role, which is a very exciting news.
00:01:04.239 --> 00:01:04.640
Thank you.
00:01:04.799 --> 00:01:05.040
Thank you.
00:01:05.359 --> 00:01:06.000
You're welcome.
00:01:06.079 --> 00:01:07.599
So you ready to dive in?
00:01:07.920 --> 00:01:08.480
I am.
00:01:08.799 --> 00:01:09.920
All right, let's do it.
00:01:10.159 --> 00:01:10.640
All right.
00:01:10.799 --> 00:01:17.120
Software companies are built to scale fast, but sales tax rules don't exactly make scaling easy.
00:01:17.359 --> 00:01:23.439
So where do you typically see a growing company, a growing software company first get caught off guard?
00:01:23.840 --> 00:01:25.040
Yeah, that's a great question.
00:01:25.120 --> 00:01:36.719
So as you're scaling, uh the first surprise is often that that quick growth creates can create a filing obligation before your tax team internally uh even realizes it.
00:01:36.799 --> 00:01:41.120
So a company can cross economic nexus threshold through sales alone.
00:01:41.359 --> 00:01:45.040
They could create physical nexus through an employee to travel.
00:01:45.280 --> 00:01:53.040
So a remote employee working in that state that they hire on, where they're making sales, travel by their existing employees into that jurisdiction.
00:01:53.280 --> 00:01:55.840
And sometimes uh third-party relationships.
00:01:55.920 --> 00:01:59.439
Uh we've got something known as click-through nexus or affiliate nexus.
00:01:59.519 --> 00:02:07.359
Um, and all those things can create a technical obligation and a filing obligation before you even realize you need to start charge of tax.
00:02:07.519 --> 00:02:11.360
Uh, another surprise is product taxability at its core.
00:02:11.439 --> 00:02:30.240
Uh, what a business refers to as SaaS can be treated differently uh by a state, and that can include things like pre-written software, sometimes data processing and information services, uh, digital products, or even some non-taxable professional services, configuration, implementation, things like that.
00:02:30.400 --> 00:02:34.240
And when they get bundled, um, yeah, that creates complexity in and of itself.
00:02:34.319 --> 00:02:41.120
And so each state has to be reviewed for how they treat all those specific underlying or subcomponents.
00:02:41.199 --> 00:02:48.719
Uh, we often look at a contract and try to determine what the actual elements of that contract are and then assign taxability at that level.
00:02:49.039 --> 00:03:00.479
So um going back to the sort of bigger picture question, I generally would recommend reviewing uh Nexus first and then uh product classification and then customer location data.
00:03:00.639 --> 00:03:03.439
And we do that in what's known as a Nexus study.
00:03:03.520 --> 00:03:07.360
Uh, and we would view invoices and contracts uh as part of that.
00:03:07.680 --> 00:03:21.759
Rather than you know, treating anything or any state as just a standalone issue, we want to get sort of a holistic uh perspective on where you've got the filing obligation and make sure you know you're not creating exposure by continuing to make sales without registration.
00:03:22.479 --> 00:03:24.240
Yes, it does sound complex.
00:03:24.800 --> 00:03:28.400
But you've got a plan to like just solve all the issues.
00:03:28.719 --> 00:03:29.120
That's it.
00:03:29.360 --> 00:03:30.960
We've got a plan, absolutely.
00:03:31.199 --> 00:03:34.400
All right, so let's play myth versus reality for a second.
00:03:34.639 --> 00:03:34.879
Okay.
00:03:35.120 --> 00:03:38.560
We sell software, so we don't really have to worry about sales tax.
00:03:38.719 --> 00:03:40.560
How wrong can that assumption be?
00:03:40.960 --> 00:03:44.240
Yeah, so keeping with the theme, I would say that's a myth.
00:03:44.479 --> 00:03:49.759
Um, the assumption, that assumption's gotten a lot of folks in trouble with the various states' DORs.
00:03:49.919 --> 00:03:54.479
Um, software in and itself is not really one uniform sales tax category.
00:03:54.639 --> 00:04:04.400
And so then the answer on sales tax consequence or taxability determination is going to vary by state, your delivery method, the type of customers you sell to, uh, contract terms.
00:04:04.479 --> 00:04:21.839
Uh, like I mentioned before, as an example, you know, like a hosted software platform might be taxable in one jurisdiction, could be exempted another, partially taxable, uh, subject to a reduced rate in some places, depending on the nature of that customer relationship, uh, what type of customer it is.
00:04:22.079 --> 00:04:38.959
So, and even when the core offering isn't necessarily taxable on its face, um, other different elements that we've mentioned in the sort of contract review and underlying subcategory assignment, those things combined create this sort of
Load full transcript
bundling effect and it can change the result.
00:04:39.199 --> 00:04:42.319
Um, the practical takeaway there is yeah, it's a myth.
00:04:42.399 --> 00:04:53.680
Uh, and this general overarching, you know, uh idea that we just sell software, we we just sell services that are non-taxable, um is a good trigger for an analysis needed.
00:04:53.759 --> 00:04:57.439
Uh, it should not ever be sort of the the conclusion to draw.
00:04:57.839 --> 00:04:59.839
And what I hear is never assume.
00:05:00.000 --> 00:05:01.839
Um things are always changing.
00:05:01.920 --> 00:05:11.360
So if you assume and don't dig a little bit deeper or have someone that is an expert, you might you might just just re-revisit, revisit.
00:05:11.600 --> 00:05:12.160
That's it.
00:05:12.319 --> 00:05:13.040
That's it.
00:05:13.360 --> 00:05:20.879
Okay, so two companies can sell what feels essentially the same software and end with very different sales tax obligations.
00:05:21.120 --> 00:05:26.800
So, what details about how a product is sold or delivered can completely change the tax answer?
00:05:27.199 --> 00:05:28.639
Yeah, it's a great question.
00:05:28.720 --> 00:05:40.800
Uh, it's a little bit nuanced, but um, one one simple example where uh two companies sell what feel like the same software goes back to my example about the type of customer you sell to.
00:05:40.959 --> 00:05:43.920
So, in a number of different states, there are B2B exemptions.
00:05:44.000 --> 00:06:08.480
And so you might sell uh to one type of customer, and your competitor selling a very similar software sells to another type of customer, maybe a business, whereas you sell directly to an end user or one sells for resale, that can change the fact pattern and ultimately the taxability shifting from taxable to reduced rate to non-taxable, uh uh sort of across the spectrum based on your uh customer.
00:06:08.800 --> 00:06:09.759
Okay, got it.
00:06:10.000 --> 00:06:11.600
Okay, so here's a scenario.
00:06:11.839 --> 00:06:18.720
A SaaS company is growing, customers are popping up across the country, and no one has really been tracking Nexus.
00:06:18.879 --> 00:06:22.800
What would make you say, okay, we need to look at this like right now?
00:06:23.360 --> 00:06:24.160
Absolutely.
00:06:24.319 --> 00:06:28.000
Um, so I I like that you use the term uh Nexus.
00:06:28.160 --> 00:06:29.360
No one's been tracking it.
00:06:29.439 --> 00:06:33.680
That in and of itself is the trigger that yes, we do need to look at this.
00:06:33.759 --> 00:06:37.839
So you do want to get your arms around your Nexus factors, economic and physical.
00:06:37.920 --> 00:06:41.199
Uh physical could be, again, remote employees.
00:06:41.360 --> 00:06:46.319
Um, it could be you know inventory, even inventory managed by 3PL.
00:06:46.560 --> 00:06:54.560
Uh it could be a brick and mortar, it could be third-party relationships, uh, independent sales reps, subcontractors who hold open a market on your behalf.
00:06:54.720 --> 00:06:57.759
Any of those things can trip physical nexus.
00:06:57.839 --> 00:06:59.439
And then economic considerations.
00:06:59.600 --> 00:07:07.199
So the general rule of thumb that folks that are you know sort of in the no will point to is gonna be$100,000 in gross receipts.
00:07:07.360 --> 00:07:11.920
There are exclusions in certain states from your sales counting toward that.
00:07:12.079 --> 00:07:18.079
Um, typically we look at that over a 12-month period, whether it's calendar year in some states, trailing 12 months.
00:07:18.160 --> 00:07:20.000
Um, it just varies from state to state.
00:07:20.079 --> 00:07:23.120
So getting your arms around Nexus is absolutely critical.
00:07:23.279 --> 00:07:28.800
And right behind that is gonna be well, do we have a sales tax consequence transaction into that state?
00:07:28.959 --> 00:07:39.279
So Nexus tells you if you've got an obligation, and then sort of categorization and understanding of your sales revenue streams tells you you've got exposure.
00:07:39.600 --> 00:07:40.720
Ooh, got it.
00:07:40.959 --> 00:07:41.279
Okay.
00:07:41.839 --> 00:07:48.319
So what's a sales tax red flag that might look harmless on the surface but immediately gets your attention when you see it?
00:07:48.560 --> 00:07:49.600
It's a good question.
00:07:49.839 --> 00:08:04.160
Um, one might be maybe a material revenue stream that doesn't necessarily reconcile from invoicing system back to your ERP or doesn't reconcile from ERP to your sales tax software.
00:08:04.319 --> 00:08:18.000
Um, sometimes you see that with companies who sell through marketplace facilitators or a number of different sales channels where you know you're not necessarily compiling all that data correctly to represent gross receipts on your returns.
00:08:18.240 --> 00:08:27.519
Um and with that, when you're missing data, there's an under-reporting issue potentially, and then there's also then that tax consequence on that revenue stream.
00:08:27.759 --> 00:08:33.759
So you've got a couple of different problems that can result from your systems not being configured correctly or talking to one another correctly.
00:08:34.159 --> 00:08:34.480
Okay.
00:08:34.799 --> 00:08:35.360
Thanks.
00:08:35.679 --> 00:08:36.000
All right.
00:08:36.080 --> 00:08:41.519
Let's say a CFO realizes the company may have several years of sales tax exposure.
00:08:41.759 --> 00:08:46.320
There's probably an instinct to just start filing and fix it moving forward.
00:08:46.480 --> 00:08:49.519
Why might that actually be the wrong first move?
00:08:49.919 --> 00:08:50.879
It's a great question.
00:08:51.039 --> 00:08:52.320
Something we encounter often.
00:08:52.720 --> 00:09:04.240
There's often a lean in business decision making in the C-suite level in particular, toward, well, let's stop the bleed and get it right going forward and you know, um kind of let the rest fly into the radar.
00:09:04.399 --> 00:09:05.679
It's never a good approach.
00:09:05.759 -->
00:09:18.000
Um, and starting prospectively without understanding your history can really hamper your ability to take advantage of programs that exist to mitigate or lessen that historical burden.
00:09:18.159 --> 00:09:31.679
Um, one of the ways that we resolve back exposure, historical exposure, um, that's identified in our Nexus and exposure reviews is uh entering into voluntary disclosure agreements with states.
00:09:31.919 --> 00:09:34.720
What that does is it limits the look back for the state.
00:09:34.879 --> 00:09:52.000
So you might have been selling for 10 years and have exposure for 10 years, but if we can approach the state and engage them in in a voluntary disclosure and secure that for a client, we can um stop the look back to statute limitations, which is typically three to four years.
00:09:52.159 --> 00:09:55.440
So the complimentary or remaining six or seven years would fall off.
00:09:55.600 --> 00:10:00.639
Uh that's barring any evidence of tech or instance of tax collected not remitted, of course.
00:10:00.799 --> 00:10:08.720
But um that's one strategy that prospective filing will ultimately preclude you from being able to take advantage of.
00:10:08.879 --> 00:10:16.960
So we always recommend getting your arms around like the big picture and then making the decision on as to how to remediate that exposure.
00:10:17.279 --> 00:10:17.759
Got it.
00:10:17.919 --> 00:10:18.240
Wow.
00:10:18.399 --> 00:10:18.720
Okay.
00:10:19.039 --> 00:10:23.840
So we hear a lot of voluntary disclosure agreements as a way to address past exposure.
00:10:24.080 --> 00:10:28.399
When is a VDA a smart move and when might another approach make more sense?
00:10:28.799 --> 00:10:29.120
Yep.
00:10:29.200 --> 00:10:32.559
And that that builds on the last point there in the prior question, right?
00:10:32.720 --> 00:10:44.159
A VDA is is a great strategy, especially when you've got material exposure or exposure that extends well past the state's normal look back period or past their statute of limitations.
00:10:44.320 --> 00:10:48.480
I think you know, understanding your eligibility to participate in a VDA is important.
00:10:48.559 --> 00:10:55.200
Uh, you're often precluded, one, if you've got a registration out there for sales tax already and been missing you know return filing deadlines.
00:10:55.360 --> 00:11:02.639
If you've got you know existing returns and have been uh materially under reporting, uh that could that would preclude you.
00:11:02.720 --> 00:11:10.159
Uh some states will allow you in some cases to take advantage of a BDA, even when you've got an existing registration.
00:11:10.320 --> 00:11:19.679
Um, if you've got notices or audit questionnaires or nexus questionnaires from a state, that can sometimes preclude you from participating and taking advantage of a BDA.
00:11:19.919 --> 00:11:36.080
Um But generally speaking, the rule of thumb is if your materiality or if the the value of your exposure uh exceeds a certain point to where you know the guaranteed waiver of penalty makes makes sense, I would say uh pursuing a BDA is definitely a strong option.
00:11:36.240 --> 00:11:44.159
Um the alternative would be just simply registering and filing going back to your first Nexus trigger date.
00:11:44.320 --> 00:11:50.799
Um and you have to do that technically because when you register, uh you're doing so under penalty of perjury.
00:11:50.960 --> 00:11:56.879
And so prospective registration, as we mentioned in the prior question, is not really a legal option.
00:11:57.039 --> 00:12:06.879
Um and so it's really a matter of once you identify that historical exposure, if it's not that material, registering back to original Nexus trigger day, it's often the right move.
00:12:07.039 --> 00:12:09.200
It's fast, it's it's easy.
00:12:09.440 --> 00:12:13.279
Um, you you get automatic penalty and interest applied.
00:12:13.440 --> 00:12:16.000
Sometimes you can ask for a waiver of penalty.
00:12:16.159 --> 00:12:32.639
Very rarely can you ask for a waiver of interest, but if it exceeds materiality, um, or you've got a really long look back period that would create a ton of um penalties, interest, uh delinquency, uh fees, it makes good sense often to pursue a BDA.
00:12:32.960 --> 00:12:33.440
Got it.
00:12:33.679 --> 00:12:34.000
Okay.
00:12:34.240 --> 00:12:36.960
So here's another one I think catches companies.
00:12:37.200 --> 00:12:41.600
Most of our companies are businesses, so our sales are probably exempt.
00:12:42.480 --> 00:12:45.919
From your perspective, what's missing from that assumption?
00:12:46.399 --> 00:12:50.159
Yeah, I think it's it's a very narrow uh assumption.
00:12:50.320 --> 00:12:53.600
There are some there are a number of states that offer a B2B exemption.
00:12:53.679 --> 00:12:55.679
It's got to be documented supported.
00:12:55.840 --> 00:13:00.799
Um, I think generally expecting that to be the case is not a dominant strategy.
00:13:00.960 --> 00:13:02.559
I think it creates exposure.
00:13:02.799 --> 00:13:13.279
And uh you want to vet that assumption fully and make sure you're documenting and supporting that position correctly because taking that as a blanket sort of approach is just it's it's risky, frankly.
00:13:13.600 --> 00:13:14.159
Got it.
00:13:14.320 --> 00:13:14.639
Okay.
00:13:15.039 --> 00:13:20.960
So with all the sales technology available now, you'd think compliance would be getting easier.
00:13:21.200 --> 00:13:25.679
So what's something automation still can't protect a software company from?
00:13:26.399 --> 00:13:31.759
Yeah, there are a ton of different uh automations out there and sales tech software's out there.
00:13:31.840 --> 00:13:34.159
Uh I'm agnostic to all of them.
00:13:34.240 --> 00:13:41.120
I have to support all of them just because I support clients who use uh a number of them across the spectrum of available options.
00:13:41.360 --> 00:13:44.399
Um so I don't I won't choose a favorite or anything like that.
00:13:45.440 --> 00:13:47.200
You don't have to name names right now.
00:13:47.519 --> 00:13:54.320
But I will say that that automation is only as good as the configuration of the software.
00:13:54.559 --> 00:13:58.399
And so that automation can't protect you from taking a bad tax position.
00:13:58.480 --> 00:14:10.399
And what that really looks like in practical terms is mapping your product to the best fit product tax code or tax category code, or depending on what software you use, there's different nomenclature for those.
00:14:10.559 --> 00:14:27.519
But um, ultimately, the the mapping of your product to their uh category, which then pings off of their maintained matrix to get a tax determination, that at its core is something that their automation is not going to fix for you or identify risk for you.
00:14:27.679 --> 00:14:32.799
And that's where you want to involve a competent third party who deals in this uh daily.
00:14:33.200 --> 00:14:38.320
Um if a product's misclassified, um that that in and of itself, that's the problem.
00:14:38.480 --> 00:14:44.960
Um sometimes integrations can drop transactions or transactions can get held up uh for a number of reasons.
00:14:45.039 --> 00:14:46.960
Uh there's timing that can come into play.
00:14:47.120 --> 00:15:00.399
Sometimes the ERP doesn't talk correctly to the tax software and you know misses out on credit memos that are created manually and don't hit the API call that's made from your ERP to the tax software.
00:15:00.559 --> 00:15:05.519
Uh sometimes the tax software isn't configured to pull from all your different revenue streams.
00:15:05.600 --> 00:15:12.799
If they don't flow through or they're they have uh different invoicing platforms, you often see the connectors are only picking from one of those.
00:15:12.960 --> 00:15:19.519
And so making sure you've got a good team helping with that configuration and integration is is critical.
00:15:19.919 --> 00:15:27.600
Okay, so the best way to make your data has to be good and your configuration has to be good to make sure your automation is like spot on.
00:15:27.919 --> 00:15:28.399
That's right.
00:15:29.120 --> 00:15:37.200
Clean data moving from invoicing or ERP to software and then the decisions to map those those data points in between.
00:15:37.519 --> 00:15:38.799
That's what it comes down to.
00:15:39.279 --> 00:15:39.600
Okay.
00:15:39.840 --> 00:15:40.960
All right, last one.
00:15:41.120 --> 00:15:41.919
Let's do it.
00:15:42.240 --> 00:15:52.559
If you could sit down with a software company before it expands into five or ten states, what would you want them to get right before that growth even happens?
00:15:53.600 --> 00:15:54.639
Great question.
00:15:54.799 --> 00:16:09.840
Um, I think there's a lot of right answers here, but I think uh if we build on the last answer, it's all about data and mapping your products correctly and making sure it's all flowing into the sales tax uh determination software ultimately.
00:16:10.000 --> 00:16:15.919
And so I really would suggest that they just establish a scalable foundation as these new states are coming online.
00:16:16.159 --> 00:16:19.519
Uh having that clean product mapping is paramount.
00:16:19.840 --> 00:16:23.519
Um, making sure you're documenting the tax classifications where needed.
00:16:23.679 --> 00:16:31.360
If you need a third party to create a sort of taxability memo that sort of documents some of those decisions that are being made, um, that's really helpful.
00:16:31.519 --> 00:16:36.320
Uh on the data front, scrubbing that, making sure you've got reliable customer location data.
00:16:36.480 --> 00:16:54.799
Um, we often see software companies have issues with sourcing because some transactions are sourced to the bill to, some are sourced to the ship to, uh, and then figuring out which is the correct jurisdiction to evaluate the taxability for that product is it comes into play.
00:16:55.039 --> 00:17:02.720
Um, I think contracts and invoices as part of your foundation should address tax to an extent.
00:17:02.879 --> 00:17:05.839
I think a tax clause makes a lot of sense in many cases.
00:17:06.000 --> 00:17:12.960
I think working with an advisor to make sure your billing is the most tax efficient manner.
00:17:13.119 --> 00:17:21.599
And sometimes that means um taking the bundle and breaking it into its component pieces or grouping things with like taxability.
00:17:21.680 --> 00:17:23.920
Uh, there are a number of different strategies there.
00:17:24.160 --> 00:17:39.599
And then understanding your customer profile and making folks within the org aware who are working on those customer relationships, um, making sure they understand, you know, when when a customer says, hey, we're exempt, what does that really mean?
00:17:39.759 --> 00:17:41.839
And what are you collecting to document that?
00:17:42.000 --> 00:17:43.680
Are you collecting a resale certificate?
00:17:43.839 --> 00:17:47.200
Are you collecting a multiple points of use exemption certificate?
00:17:47.440 --> 00:17:51.039
Is it exempt based on uh 501c3?
00:17:51.440 --> 00:17:58.319
Is it a B2B exemption that should be applied that might reduce it from 6% to 1% in Connecticut?
00:17:58.480 --> 00:18:13.039
Um and you know, understanding Nexus ultimately, because when you go and register in the States, if you're purely a remote seller, your registration and the return mechanics look a little bit different than if you actually have physical presence.
00:18:13.200 --> 00:18:15.680
So that's a Nexus question, really.
00:18:15.920 --> 00:18:20.960
And but it will uh change how you need to set up your compliance effort.
00:18:21.119 --> 00:18:38.000
Um and understanding what your your growth is gonna look like and your uh the number of states you're gonna move into will also help inform you and a third party if they're helping you, a consultant, um, with picking the best sales tax software if you don't have one yet.
00:18:39.039 --> 00:18:39.359
Okay.
00:18:39.839 --> 00:18:46.640
Well, thank you, Adrian, for all of your insights on sales tax challenges with SaaS and software companies.
00:18:46.880 --> 00:18:52.079
I'm sure a lot of people are like, um, let me go dive into my records a little bit more.
00:18:52.960 --> 00:18:55.680
Um hopefully they don't find too many horrible things.
00:18:55.759 --> 00:18:57.680
But if they do, they know where to find everybody.
00:18:57.759 --> 00:18:58.559
So that's right.
00:18:58.880 --> 00:18:59.279
That's right.
00:18:59.359 --> 00:19:00.240
We do this all day.
00:19:00.720 --> 00:19:03.839
I know all day, and that will get you all set up.
00:19:04.240 --> 00:19:07.519
So thank you so much, and I hope to see you back on the show again.
00:19:07.759 --> 00:19:08.640
Thank you, Sardet.
00:19:08.799 --> 00:19:09.440
I appreciate it.
00:19:09.680 --> 00:19:10.319
No problem.
00:19:11.839 --> 00:19:18.559
The big takeaway from today's conversation is that sales tax can quickly become more complicated as a software company grows.
00:19:18.720 --> 00:19:27.839
Understanding where you have obligations, identifying potential exposure early, and putting the right processes in place can make a big difference as your business expands.
00:19:28.079 --> 00:19:30.000
Thanks for tuning in to Beyond the Ledger.
00:19:30.240 --> 00:19:35.839
For more insights and expert perspectives, visit btcpa.net and explore our latest resources.
00:19:36.079 --> 00:19:39.359
And don't forget to like, follow, share, and subscribe.
00:19:39.519 --> 00:19:43.359
Until next time, I'm Sardet Layfield, and we'll see you for the next conversation.