Saga limitations for large companies in 2026: what your accountant isn't telling you (CFO analysis)
When a company exceeds €10M in turnover, Saga starts to struggle. Here is exactly where the issues arise and how to fix them without scrapping the software.
Ionut Mihaescu — Full Stack Developer Azuvio · 2026-05-21 · 10 min · ERP & Integrations
Who this article is for
For the CFO, financial controller, or entrepreneur leading a €10-50M turnover company, multi-channel or multi-entity, still running on Saga, who has asked themselves at least once in 2026: "Is Saga still enough for us?"
The answer is neither "yes, it's perfect" nor "you must scrap it." The correct answer is: Saga remains excellent at what it does well (accounting, tax reporting), but it has 6 clear limitations that emerge during scale-up. Almost all can be solved with an operational layer on top, not a new €100k ERP.
Limitation #1 — Lack of real-time operational visibility
Saga closes the day / month. You need real-time visibility into: pipeline orders, branch stocks, outstanding invoices, margins per client. Saga isn't built for this — it's not a "bug", it's by design (it's an accounting tool, not an operations tool).
CFO Symptom: Monday morning management meeting using reports from last Friday. Decisions delayed by 3-5 days.
The right solution: An operational layer (Azuvio or equivalent) that aggregates live data from sales channels + Saga. Saga remains the fiscal source.
Limitation #2 — Manual multi-entity consolidation
You have 3+ companies in the group (usually a distributor + 2 legally separate branches or a holding + operational units). Saga runs in isolation for each. Consolidation = monthly Excel copy-pasting.
Real risk: Consolidation error → wrong board-pack → decisions based on false data. I saw a group invest €1.2M in a branch based on a consolidation with a €280k error in non-eliminated internal receivables.
The right solution: Automated ETL from all Saga instances into a data warehouse (even a simple PostgreSQL), with consolidation elimination rules configured once. Cost: €4-8k/year vs. €80-150k for an enterprise ERP with a consolidation module.
Limitation #3 — Limited API for modern integrations
Saga relies on file-based import/export (XML, TXT), not a modern REST API. If you have an online shop with 500 orders/day, direct integration with Saga is clunky and fragile.
Symptom: "Scripts break at every Saga update" or "the import crashed overnight and today we have 1,200 orders that need to be invoiced manually."
The right solution: Middleware that talks to Saga via controlled import/export (batches of 200-500 invoices, validation, rollback) and to modern channels via API. Azuvio does exactly this — see the Saga ↔ Azuvio connector.
Limitation #4 — Performance at high volumes
Under 1,000 invoices/month, Saga flies. At 5,000+/month on a single database, you start feeling sluggishness in complex reports, balance sheet locks, and necessary re-indexing. At a sustainable 10,000+/month, you need to fragment the databases.
The right solution: A clean Saga database (fiscal only), while operational volume stays in the operations layer. Saga receives daily/weekly aggregates, not every individual order. The volume of entries in Saga drops by 70-90%.
Limitation #5 — Non-existent cash-flow forecast
Saga shows you what happened (historical). It doesn't show you what will happen in 30/60/90 days. The CFO needs a forecast based on: issued invoices + maturities + planned payments + pipeline orders + seasonality.
The right solution: BI on top of Saga + Azuvio with a forward-looking cash-flow model. Many firms already use Power BI or Tableau for this; Azuvio delivers the pre-validated data.
Limitation #6 — Audit trail and granular access controls
With 50+ employees touching Saga (sales, procurement, warehouse, accounting), you need granular control: who sees what, who modifies what, audit logs for ANAF (the Romanian tax authority) / due-diligence / investors. Saga has access control, but not at an enterprise level (attribute-based, contextual segregation, MFA).
The right solution: Fine-grained access control lives in the operational layer (Azuvio logs who created which order, which invoice, with which exceptions), while Saga only hosts accounting users (5-10 people, not 50).
The 3 real exceptions when you should switch from Saga
I repeat from the article "When Saga becomes too small" — there are only 3 cases where Saga is truly no longer enough:
1. Mandatory multi-currency IFRS consolidation (multinational group, stock exchange listing, strategic investor requiring IFRS).
2. Complex multi-level MRP/BOM production (manufacturing, not distribution).
3. Specific certifications for pharma/aviation/military (GxP, FDA, specific health authority audits).
In all other cases — which represent >90% of large SMEs in Romania — Saga + the Azuvio operational layer = the optimal cost/functionality solution.
Conclusion for the CFO
Saga's limitations at scale-up are real, but they are limitations of scope, not quality. Saga is excellent at what it was built to do: clean, compliant, affordable Romanian accounting. It wasn't built to be an enterprise ERP — and that's good for you, because an enterprise ERP costs 50x more. The modern solution for the €10-50M company is: keep Saga as the fiscal source, add the Azuvio operational layer for everything regarding multi-channel, multi-entity, real-time operations. Request a 30-min CFO demo — we'll show you exactly the architecture and the ROI for your case.