Preduzmi vs Excel: Why Spreadsheets Break Down for Paušal Compliance

Last updated: October 2026. Product behaviour described as of this date.

Most paušalci start with a spreadsheet. A Google Sheet with a few columns — invoice number, date, amount, running total. It works fine for the first few months. Then you issue an invoice in EUR and need the NBS middle rate for that date. Then you realise you have been summing payment dates instead of service dates. Then the rolling 12-month total goes stale and you only notice how close you are to the 8,000,000 RSD VAT threshold when someone else mentions it.

Spreadsheets are powerful general-purpose tools. Paušal compliance has specific, rule-bound requirements that a spreadsheet handles only as well as you remember every rule, every formula and every edge case, every time.

This article compares managing paušal obligations by hand (spreadsheets, bank statements, mental checklists) with Preduzmi, a tool built for Serbian paušalci. The Preduzmi column describes what the product does today, including where it stops.

Feature-by-feature comparison

Where spreadsheets actually work fine

For some paušalci, a spreadsheet is genuinely enough.

You might not need Preduzmi if:

• You issue a few invoices a month, all in RSD, to Serbian clients
• Your revenue sits far below both limits
• You have a single bank account with simple transactions
• You are comfortable with formulas and maintain the sheet carefully
• You already have a system that works

In these cases a dedicated tool may not be worth the cost. A well-kept Google Sheet with correct formulas does the job.

The spreadsheet starts to strain when:

• You invoice in foreign currency and need the NBS rate for every invoice
• Your revenue gets close enough to either limit that the exact total matters
• Payments arrive in more than one account or bank
• You want to check the four monthly payments against the bank statement every month
• You have ever changed the sheet's structure and forgotten a formula
• You have ever found a calculation error months later

The hidden cost of spreadsheet errors

Spreadsheet compliance fails silently. A broken formula, a wrong cell reference or a filter that hides a row does not announce itself. Typical ways it surfaces:

• You realise in November that the sheet summed issue dates instead of service dates, and the limit total was wrong all year
• A duplicated row inflated the revenue total, and you worried about a limit you were not near
• A missed row deflated it, and you were nearer the limit than you thought

The rules behind the two totals are in revenue limits: the 6,000,000 RSD paušal ceiling (ZPDG čl. 40 st. 2 t. 4) and the 8,000,000 RSD VAT threshold (ZPDV čl. 33 st. 1). A tool does not remove every risk, but it removes the risk of building and maintaining the calculation yourself. Its results are still yours to check.

What Preduzmi doesn't do

Preduzmi is a tracking tool, not an accounting system and not a substitute for professional advice:

• It doesn't replace an accountant in complex cases: moving to bookkeeping (knjigaš), entering the VAT system, the annual income tax, an independence-test question
• It doesn't submit anything for you. Nothing goes to the Poreska uprava, ePorezi, SEF or your local tax administration; you make the four monthly payments yourself
• It doesn't check that an invoice is legally complete. The generated document is a template filled from your data; the required elements are yours to verify
• It isn't built for a DOO, a knjigaš or trade in goods
• It doesn't give legal or tax advice. When a situation needs interpretation of the law, ask a professional

What it does is put the routine in one place: statement import, the KPO and invoice-payment reconciliation in a single tool, so that the questions left for you and your accountant are the ones that need judgment. We cover whether a paušalac needs an accountant in a separate guide.

Migration from spreadsheet to Preduzmi

If you have been using a spreadsheet and want to switch:

1. Collect your invoice files (PDF, DOCX or images) for the year
2. Upload them — the parser extracts the data, and you check each invoice against your spreadsheet before confirming it
3. For invoices without a file, enter them by hand from your spreadsheet
4. Import your bank statements to build the transaction history
5. Compare the totals with your spreadsheet. If they differ, one of the two has an error, and now you can find it

The migration is a one-time effort. After it, the ongoing work is adding new invoices and statements as they come. KPO vs bank statement explains why the two totals rarely match exactly.

Key takeaways

1. Spreadsheets work for simple cases — few invoices, one currency, revenue far below the limits. If that is you, keep your spreadsheet.
2. Spreadsheets strain with complexity — foreign currency, revenue near a limit, several accounts, and formula errors that accumulate silently.
3. A dedicated tool's real advantage is fewer silent errors — wrong dates, broken formulas, missed conversions, duplicate rows.
4. Preduzmi puts statement import, the KPO and reconciliation in one tool. It tracks; it does not file, and it does not replace an accountant in complex cases.
5. The comparison isn't only subscription vs free — it is also the time spent maintaining formulas and the cost of an error found late.