SaaS Subscriptions: Controlling What You Spend, and the VAT Line You Are Missing

Nobody decides to spend OMR 900 a month on software. It accumulates.

A project tool on someone’s personal card. A design subscription left over from a campaign two years ago. Three cloud storage plans, because nobody knew about the first two. An accounting product on annual billing that renewed last Thursday without a conversation.

The problem with subscription software is not that any one line is expensive. It is that no single purchase was ever large enough to need approval, so the total was never decided by anyone. It was arrived at.

This article is about getting the total back under control — and about one line on your VAT return that a great many businesses in Oman do not know is theirs to file.

The short answer

• Build the list first. Almost every business underestimates its own subscription count, and you cannot manage a number nobody has written down.
• The two things that actually drive the bill are per-user pricing and tier jumps. Both make success expensive.
• Foreign software subscriptions are imported services. If you are VAT-registered they belong on your return under the reverse charge — and for a fully taxable business the net effect is nil, but only if you file it.
• Cancelling a subscription can destroy invoices you are required to keep for ten years. Export before you cancel, not after.
• Currency is not your problem. The rial’s peg has not moved since 1986.

The line most businesses do not know is theirs

Here is the part that generic advice on software cost control will never tell you, because it was written for a country that is not this one.

When you buy software from a company outside Oman — a subscription billed from Ireland, the United States or the UAE — you have imported a service. Oman’s VAT Law places the tax on the recipient in that situation rather than on the foreign supplier, through the reverse charge mechanism. Tax advisers writing on Omani VAT consistently list software licensing and cloud-based IT services purchased from non-resident suppliers among the supplies this catches.

In practice, for a VAT-registered business, it works like this:

• You declare 5% of the value of the imported service as output tax on your return.
• If you are fully taxable, you claim the same amount as input tax on the same return.
• The two cancel. Net payment: zero.

Which is exactly why it gets missed. The arithmetic nets to nothing, so nothing appears to be at stake — and a return that omits it is still a return that is wrong. The obligation is to declare, not to pay.

Two situations where it stops netting to zero, and both matter:

If you make exempt supplies, your right to recover input tax is restricted. The output side is then declared in full and the input side is not, and the reverse charge becomes a real 5% cost on every foreign subscription you hold. Businesses in financial services, healthcare, education and residential leasing should establish this position deliberately rather than discover it.

If your accounting software cannot post a reverse charge, you have a recording problem before you have a compliance problem. Plenty of inexpensive products handle domestic VAT and nothing else. This belongs on the requirements list when you choose one — see accounting software for a small business in Oman.

If you are not registered for VAT, none of this applies to you yet. It applies on the day you register, and mandatory registration arrives at OMR 38,500 of taxable supplies on a rolling twelve-month basis. Knowing about it beforehand is considerably cheaper than being told about it during a review. Confirm your own position with the Tax Authority or your tax adviser — the point here is that the line exists and is yours, not a substitute for advice on your particular case.

Currency is the problem you do not have

A short section, because the conclusion is unusually clean.

Most of your software is priced in US dollars. In most countries that means a currency exposure to be watched and sometimes hedged. In Oman it does not. The rial has been pegged to the dollar at USD 2.6008 per rial since 1986, and the parity has not changed since. A USD 40 per-user subscription costs the same in rials this year as it did last year unless the vendor raised the price.

Two qualifications, both small and both worth checking once:

• Your bank is not free. Card issuers apply a foreign-transaction fee and a conversion margin regardless of the peg. That is a bank charge, not a currency risk, and the way to deal with it is to ask your bank what the rate is on the card you are actually using.
• Not everything is priced in dollars. Tools billed in euros or pounds do move against the rial, because those currencies move against the dollar. If a material share of your software spend is non-USD, that share behaves like everyone else’s.

So when you read that software costs are unpredictable, note that in Oman the unpredictability is not coming from the exchange rate. It is coming from your own headcount.

Where the money actually goes

Four drivers, in order of how much damage they do.

1. Per-user, per-month pricing. The dominant model, and its defining feature is that the moment of highest value is also the moment of highest cost. A tool at OMR 12 per user for four people is OMR 48. The same tool at thirty people is OMR 360, for the same functionality. Nothing improved; you simply grew. Every per-user tool should be priced at your expected headcount in two years, not at today’s.

2. The tier jump. Pricing pages are built around one or two capabilities placed deliberately at the top of a tier — single sign-on, an audit log, a real permissions model, API access. You need one of them, and the whole account moves up a band, for every user. The increase is rarely proportional to the feature. Find out which capabilities live in which tier before you standardise on a product, because the tier you will eventually need is the price you are actually paying.

3. Annual billing that renews in silence. Annual plans are usually cheaper per month and always harder to leave. A renewal that happens without a decision is the purest form of the problem in this article: money moving without anyone choosing. Every annual renewal date belongs in a calendar, thirty days early, with a name attached.

4. The tools nobody cancelled. Trials that converted. Seats for people who left. A product that was replaced by another product, where nobody closed the first account. This is the cheapest money you will ever save, because cancelling it costs nothing and changes nothing.

Build the list

None of the above is possible without an inventory, and the inventory is harder to assemble than it sounds, because the spending is distributed by design.

Five places to look. Do all five:

1. Bank and card statements for the last twelve months. Twelve, not three — annual subscriptions only appear once.
2. Personal cards being reimbursed through expenses. This is where the subscriptions nobody knows about live.
3. A mailbox search for “receipt”, “invoice”, “your subscription” and “renewal”.
4. The app store and browser extension lists on company devices.
5. Ask people what they use. Not what they pay for — what they use. The gap between those two answers is the point of the exercise.

Then one row per tool: what it is, who owns it, what it costs, how it is billed, when it renews, how many seats, how many of those seats are active, and where the data would go if you left.

That last column turns a spending list into a risk register. It also feeds two things you need anyway: the record of processors handling personal data expected under the PDPL, and the account inventory behind a security baseline. Where the data physically sits is a separate question with its own answer — data residency and cloud hosting in Oman.

Cancelling can destroy records you are required to keep

This is the most expensive mistake in this article, and it is made while trying to save money.

Under Article 70 of the VAT Law, tax invoices and accounting records must be kept for ten years after the end of the tax year in which the return was filed, and must remain legible throughout. A subscription invoice from a foreign software vendor is a purchase record, and if you reverse-charged it, it supports a figure on a return you have already filed.

Where do those invoices live? Almost always in the vendor’s billing portal — behind the login you are about to close.

Cancel the subscription and access to the billing history usually goes with it. Some vendors offer a grace period; many do not; none of them are obliged to hold your records for a decade on your behalf. The same applies to the data itself: an export that is available while you are a paying customer often does not survive the account being closed.

So the order matters, and it is not the intuitive one:

1. Export the billing history — every invoice, as PDF, to storage you control.
2. Export the data, and open one of the exported files to confirm it is genuinely readable rather than an empty archive.
3. Then cancel.

Doing it in the other order is how a business ends up with a filed return it cannot support.

What to do with the list

Finding	Action
Nobody uses it	Cancel. Today.
Duplicate of another tool	Pick one, migrate, cancel the other
Paid seats exceed active users	Reduce the seat count at renewal
Monthly billing on a tool you will keep for years	Move to annual, with the renewal diarised
Annual billing on a tool you are unsure about	Move to monthly, and pay the premium for the option to leave
Charged to a personal card	Move to a company payment method with a named owner
No named owner	Assign one, or cancel it
Holds personal data or statutory records	Keep it, and document it properly

The interesting rows are the fourth and the fifth. Annual billing is a discount in exchange for optionality: a good trade on the tools you are certain about, a bad one on everything else. Most businesses have it backwards — annual on the experiments, monthly on the essentials.

What goes wrong

A cost-cutting exercise instead of a habit. A one-off cleanup finds real savings, and then the sprawl returns, because the mechanism that produced it was never changed. The fix is a fifteen-minute quarterly review of the list, not an annual project.

Cancelling the wrong thing. A tool with low usage may be low-usage and load-bearing — the one person who runs payroll on it, the integration nobody remembers exists. Ask before cancelling. Once is enough.

Central purchasing as the answer. Requiring approval for every subscription produces the same subscriptions on personal cards, and now you cannot see them. Visibility with a low approval threshold beats control with a high one.

Counting only the subscription. The real cost of a tool includes the time to administer it, the effort of moving data in and out, and the training of everyone who touches it. This is why consolidating four tools into one that is nominally more expensive can still be the cheaper decision — and why measuring it properly is worth the trouble, which is the subject of dashboards and what to measure.

Nobody owns the total. An owner per tool is necessary and insufficient. One person should be able to answer “what do we spend on software each month” without doing research.

Before you add the next one

Six questions. They take ten minutes and they prevent most of what is above.

1. Does something we already pay for do this? The commonest source of duplicate spend is not knowing what you own.
2. What does it cost at three times our current headcount? Look it up now, on the pricing page.
3. Which tier holds the capability we will eventually need? Single sign-on, permissions, audit log, API. Price that tier, not the one you are joining on.
4. Who owns it, and who is the second person who can administer it? A name and a backup, exactly as with no-code tools.
5. How do we get our data out, and has anyone tested it? An export button nobody has pressed is a claim, not a feature.
6. Is the supplier foreign, and does our accounting treatment reflect that? The reverse charge is not optional, and it is far easier to set up on day one than to reconstruct at the year end.

If a tool passes all six, buy it monthly for three months before committing annually. Three months cost very little and answer the only question that matters, which is whether anyone actually uses it.

Questions people ask

How much should a small business spend on software? There is no useful benchmark, and any percentage-of-revenue figure you are quoted was calculated on a different kind of business. The right question is per tool: what does this replace, and what would we do without it? A tool that removes ten hours of manual work a month justifies itself at almost any small-business price. A tool three people log into out of habit does not justify itself at any price.

Is it cheaper to build our own instead of subscribing? Almost never for something standard, and the comparison people run is the wrong one — building is a capital cost with a permanent maintenance obligation attached, and the subscription is the maintenance. Custom is right when the process is genuinely unusual, and the test is in signs your business needs custom software.

Do I have to charge myself VAT on a foreign subscription? If you are VAT-registered, the reverse charge means you account for the tax on your own return rather than paying it to the supplier. For a fully taxable business the output and input entries cancel, so nothing leaves your bank — but it still has to appear. Confirm your treatment with your tax adviser.

The vendor’s invoice does not show Omani VAT. Is that right? For a non-resident supplier, generally yes — that is what the reverse charge is for. The absence of VAT on the supplier’s invoice is not evidence that no VAT obligation exists; it is an indication that the obligation is yours.

We use dozens of free tools. Is that better? It is cheaper, and it is not free. Free tiers carry the same data-location and personal-data questions as paid ones, usually with weaker contractual commitments and no support when something goes wrong. Free is a pricing decision, not a risk decision — put them on the same list.

What is the fastest saving available? Seats belonging to people who have left. Every business has some, they cost the full rate, and removing them takes minutes. It is also a security fix, because a paid seat is usually a live login.

Should we consolidate onto one big platform? Sometimes. Consolidation reduces the number of integrations, logins and invoices, and it increases how much a single vendor decision can hurt you. It is a good trade when the pieces being replaced are genuinely mediocre, and a bad one when you are giving up a tool people like for a module they will merely tolerate. The wider question of what belongs in one system is in which business system do you actually need.