The best candidates for automation are processes in which the same data is copied by hand between two programs, several times a week, following rules you can write down. The five below appear in almost every small or medium-sized company in Romania. For each one you'll find the signal that it's worth automating, the systems involved, the exceptions to clarify and what to measure after launch.
1. Moving requests from forms and email into the CRM
The signal: requests arrive through the form, email and WhatsApp, and someone copies them into a spreadsheet or CRM — or doesn't, and they get lost.
What the automation does: each new request becomes a record with its source, contact details, request details and an owner assigned by rules (area, type of service). The requester gets a confirmation, and the team gets a notification with the full context.
Exceptions to clarify: duplicate requests (same client, two channels), messages without enough data, spam. The rule for each is written beforehand, not afterwards.
What to measure: time to first response, requests without an owner after one hour, lost requests (these should drop to zero).
2. e-Factura: from SPV into accounting, on time
The signal: incoming invoices are downloaded by hand from SPV (the ANAF online portal), checked one by one and entered into the accounting software; issued invoices are uploaded late.
Why the deadline matters: since 1 January 2026, the deadline for submitting invoices to RO e-Factura is 5 working days from issue (Emergency Ordinance 89/2025). Missing it is fined RON 1,000 to 2,500 for small taxpayers and individuals, RON 2,500–5,000 for medium ones and RON 5,000–10,000 for large ones. In B2B, an invoice not sent through the system incurs a fine of 15% of its value. Since 1 January 2025, the obligation also covers invoices to consumers (B2C).
What the automation does: it periodically downloads invoices from SPV, extracts the supplier, amounts and VAT, checks for duplicates, prepares them for import into the accounting software (SAGA, Smartbill, an ERP) and flags only the exceptions: mismatched amounts, new suppliers, rejected invoices. For issuing, it checks the fields that cause rejections before sending.
Exceptions to clarify: invoices in foreign currency, corrections and reversals, suppliers without a valid tax ID, scanned documents instead of XML.
What to measure: invoices submitted on time (it should be all of them), processing time per invoice, the number of exceptions per month.
3. Recurring invoicing and payment follow-up
The signal: subscriptions, rents or maintenance contracts invoiced by hand every month; payment reminders sent “whenever someone remembers”.
What the automation does: it generates invoices on the set date from active contracts, sends them (including to e-Factura), checks receipts against the bank statement and sends reminders on an agreed schedule — polite on the due date, firm after a number of days you decide.
Exceptions to clarify: price changes during the contract, partial payments, clients who always pay late and have special arrangements.
What to measure: average days to payment, invoices unpaid at 30 days, the team's time spent on invoicing.
4. The Monday-morning report
The signal: someone spends the first hours of the week pulling data from invoicing, the CRM, the online shop and spreadsheets into a report that management reads in five minutes.
What the automation does: it extracts data from the agreed sources, puts it into the same format, calculates the agreed indicators and delivers the report (email, Slack, an internal page) at the set time, with the list of sources and the extraction date. When a source doesn't respond, the report says explicitly what is missing instead of showing a zero.
Exceptions to clarify: indicator definitions (what “order” or “new client” means in each system), lags between systems, retroactive corrections.
What to measure: hours saved per week, discrepancies found between systems, decisions made earlier.
5. Booking confirmations and reminders
The signal: clinics, salons, workshops, restaurants — bookings made by phone, written in a diary, with no-shows discovered only at the appointed time.
What the automation does: it confirms the booking immediately (SMS, WhatsApp, email), sends a reminder beforehand, allows rescheduling or cancelling from a link and updates the team's calendar. Freed-up slots can be offered automatically to people on the waiting list.
Exceptions to clarify: bookings without a valid phone number, clients who don't want messages, services that need human confirmation.
What to measure: no-shows per month, slots recovered from cancellations, confirmation calls the team no longer makes.
How to choose where to start
Put the five processes (and others from your company) into a table with three columns: how often it happens, how much time it takes each time and how clear the rules are. Start with the process that has high frequency, clear rules and a source system you can access. A single process fully automated, with its exceptions handled, is worth more than five automated halfway.
The wider context shows why it's worth it: in 2024, only 73% of EU SMEs had reached a basic level of digital intensity, and in 2023 Romania ranked last, with 72.1% of enterprises at a “very low” level (Eurostat). Automating an administrative process is usually the first concrete step.
See how we scope a project in Automation & integrations or read how much it costs to automate a process.