A system that works,
not one you feed

A service entirely separate from accounting. Whether you're looking for a new system or have one that isn't used as it should be, we start from what your management needs, then build the solution around it.

We work onOdooOther cloud systemsOn-premise systems

The difference in a single working day

When the system is filled in at month-end

  • Reports are built by hand in spreadsheets outside the system.
  • Every department works in its own system or file.
  • Balances don't match the stock count or the bank statement.
  • Nobody knows who approved what, or when.
  • The e-invoice comes from one place, the journal entry from another.

When the system works alongside the team

  • Reports and dashboards come straight from the system.
  • One cycle, from request to journal entry.
  • Inventory and banks reconciled inside the system.
  • An approval workflow, with a record of every sign-off.
  • Invoice and entry from a single document.

How much of your system do you actually use?

Tick what is really done inside your system today — not what could be. The result is calculated in your browser, and nothing is sent.

Sales
Purchasing
Inventory
Accounting
Management

The same cycle, before and after the system

Pick a cycle and compare the number of manual steps before and after proper configuration.

Todaymanual: 7

  1. Request by word of mouth or email
  2. Quote sitting in someone's inbox
  3. Purchase order typed in Word
  4. Goods received with no record in the system
  5. Invoice keyed in by hand
  6. Matching in Excel
  7. Manual journal entry

After configurationmanual: 2 · automatic: 3

  1. Purchase request in the system
  2. Approval by authority level
  3. Purchase order from the request
  4. Receipt updates stock
  5. Matched invoice, automatic entry

What we deliver on systems

  • Needs analysis & system selection

    Defining each department's needs and comparing the available options on cost and timeline.

  • Configuration & customisation

    Chart of accounts, cost centres, and purchasing, sales and inventory cycles.

  • Access rights & approvals

    Setting what each user sees and approves, and the approval workflow.

  • Custom modules

    Screens, workflows and reports designed around the way your business works.

  • Data migration

    Opening balances, items, customers and suppliers, and transaction history.

  • E-invoicing

    Configuring the system to ZATCA's requirements.

  • Integration with other systems

    Point of sale, online stores and payroll systems.

  • Reports & dashboards

    Dashboards showing each department's KPIs as they happen, with no manual preparation.

  • Training

    User training, plus short how-to guides for each role.

  • Support & maintenance

    Resolving issues, keeping up with updates, and continuous improvement.

The implementation cycle

Six phases, each with a deliverable you review and sign off before we move to the next.

1 of 6

Analysis

Sessions with each department to map the current cycle and what needs to change.

Deliverable: Requirements document

Erroba is an independent service provider, not an Odoo agent. We help you choose the system that fits your needs and budget.

What you receive, and when

A written deliverable at every phase, and follow-up after go-live that comes with numbers.

During the project

  • Requirements document and solution blueprint
  • Balance reconciliation record after migration
  • Approved test scenarios
  • A written guide for each role in the system

After go-live

  • Staying with the team until operations settle
  • Issues resolved by clear priority
  • A stability report after the first close on the system

With annual support

  • An annual bundle of hours, used as needed
  • A monthly timesheet of work done
  • Reviewing system updates and their impact before applying them

System licences and subscriptions are paid directly to the vendor and are not part of our fees.

The first thirty days with an existing system

Before any development, we understand what you have — many problems are solved by correct configuration, not code.

  1. 1

    Week one

    Reviewing settings, the chart of accounts and access rights, plus short sessions with each department.

  2. 2

    Week two

    A written gap report: what doesn't work, what isn't used, and the impact of each.

  3. 3

    Week three

    Implementing the quick wins that need no development.

  4. 4

    Week four

    An implementation plan for the rest: phases, timelines and deliverables.

Questions about our systems service

Is Erroba an Odoo agent?

No. We aren't tied to any system vendor, which is why our recommendation is based on your needs alone — not on any particular system.

Do we have to move to Odoo?

No. We work on Odoo and on other cloud and on-premise systems. If your current system is good enough, it's usually better to make fuller use of it than to replace it.

How long does implementing a new system take?

It depends on the number of departments and branches, the volume of data and the development required. After the analysis phase, we provide a written plan with the phases and their timelines.

Who pays for the system licences?

They are paid directly to the vendor in your company's name, and the accounts and data remain yours.

What happens after go-live?

Once operations are stable, we move to annual support with a bundle of hours, plus a monthly statement of the work done.