Running a Business: What You Actually Manage

Before the detail, the whole map in one table:

Why four rather than five? Because what usually gets added — customer relationships, marketing, planning — is either a branch of one of these or a separate category with its own tools.

Customer follow-up is a good example. It looks like a fifth file, and in a small business it is a branch of the books: who owes money, since when, and whether they paid. Once it grows into a sales pipeline with stages, it moves into its own category.

The use of drawing the boundary is knowing what not to buy: a tool promising a fifth file is usually reselling one of the four under another name.

The books are the one file that is heavy from day one in every activity without exception, because everything after them is built on them.

Three things you manage here:

1. What came in and what went out — every sales invoice and every expense 2. What you are owed and what you owe — customer and supplier balances 3. Where you stand — a correct trial balance at any moment

The common error is deferring all of it to year end and gathering the paperwork at once. The result is a figure you close with rather than manage with: you learn you made a profit or a loss after the moment to act on it has passed.

The working rule: the entry is created at the moment of the invoice, not a month later. When entries are created automatically with each operation, the trial balance becomes a by-product of your daily work rather than a separate task waiting to be done.

That alone separates an owner who knows their margin mid-month from one waiting on an accountant in March to describe last year.

If you sell a service this file is light for you, perhaps absent. If you sell goods it is often heavier than the books in your day.

What you manage here:

• What sits on the shelf — the actual quantity, not the expected one
• What is in transit — purchase orders not yet received
• What ran out or is close to it — before it runs out, not after
• What does not move — the most dangerous, because it is silent

Dead stock does not announce itself. It sits on a shelf for months with your money already spent on it, eating your liquidity without appearing in any report you look at daily.

Linking stock to sales is the whole matter: when the invoice deducts from the warehouse as it is issued, the number stays right without a stock count. When the two are separate, you find the difference at the annual count, by which time it is large enough to hurt.

⚠️ One limit stated: Snad tracks quantities, movement and reorder-point alerts, but it does not track expiry dates or batch numbers. If your activity is pharmaceutical or food-related and depends on shelf life, that is a need to ask about explicitly.

With one or two employees a sheet of paper is enough. At the third, questions begin that memory cannot answer: how much leave is left? How many overtime hours this month? When did end-of-service entitlement start?

What you manage here:

• Attendance — and the overtime built on it
• Leave and its balances
• Payroll — built from that same attendance rather than a second sheet
• The social insurance file

The recurring fault is calculating payroll in a file separate from the attendance record. Every month becomes an exercise in reconciliation, and every error in it touches someone's salary — the worst kind of error for a team.

When payroll comes out of attendance itself, the middle step disappears entirely. Overtime and deductions become a calculated result rather than a figure written from memory.

Its accounting effect is often missed: salaries are among the largest expense lines in most small businesses, so keeping them outside the books until month end means the profit figure you look at mid-month is not your figure.

Below the registration threshold this file is nearly absent. Above it, it becomes a periodic obligation that is not deferred.

What you manage here:

• A compliant invoice for the Zakat, Tax and Customs Authority with its mandatory fields
• Output tax — what you collected from customers
• Input tax — what you paid on purchases and deduct
• The periodic return — and the difference between the two

The commonest error is leaving the return until its due date and gathering invoices then. The result is input tax genuinely paid whose invoice cannot be found, so it is not deducted — meaning it was paid twice.

The remedy is structural rather than procedural: when every sales and purchase invoice is recorded in its own time, the return becomes a reading from the books rather than a gathering of paper. The figure exists before the filing date, and what remains is reviewing it.

⚠️ Integration with the Zakat, Tax and Customs Authority is not available on Snad's free plan — it is optional on Basic and included in Pro. If you are registered for tax, that alone decides your plan.

The same four files, in a different order. This table condenses what you see in the commonest activities:

The practical use: do not buy what is heavy for someone else. A consultancy paying for a point of sale it never opens has bought a file it does not have, and a restaurant starting with the books alone leaves its two heaviest files without a tool.

In Snad the nine apps sit in one system, so you switch on what is heavy for you and leave the rest — plans differ by number of users and number of apps running at once, not by which apps you get. The solutions by activity pages explain each one in its own order.

⚠️ What Snad does not do is stated: it is not a production planning system, it does not run several businesses with separate commercial registrations inside one account, and being cloud-based it does not work without a connection.