Support for an ERP that keeps the business running after go-live

Support is more than a help desk. The work falls into four kinds. Incidents are things that are broken now: a posting fails, a batch job stops, an interface to the bank returns errors. Service requests are routine asks such as a new user, a new report layout or a new approval limit. Changes are modifications to configuration or code. Problems are the root causes behind repeated incidents.

We separate these on purpose because they need different handling. An incident needs speed. A change needs testing and approval. A problem needs analysis and a permanent fix, otherwise the same ticket returns every month. A support plan that only reacts to incidents leaves you paying for the same fault repeatedly.

Each plan sets response and target resolution times by priority. A blocked month-end close counts as urgent; a cosmetic report change does not. We agree the definitions with you in writing, so there is no argument at the moment of pressure. Indicative takeover time for an existing system is one to two weeks, including the documentation pass.

Every ERP changes under you. SAP issues support packages and release upgrades, Odoo ships a new major version each year, and Microsoft updates Dynamics 365 on a regular release cycle. Each of these can break a customization or an integration. Skipping them is not safe either, because security fixes and regulatory updates arrive through the same channel.

Our approach is to keep a test copy of your system, apply each release there first, and run a fixed set of regression tests: posting an invoice, receiving stock, running payroll inputs, producing a ZATCA e-invoice, running the month-end reports. We report what broke, fix it, and schedule the production change outside working hours with a rollback plan.

Custom code is the usual problem. We review it for upgrade risk, remove what the standard system now does itself, and bring the remainder under version control with tests. For Odoo that is a custom module repository, for Dynamics 365 it is extensions, and for SAP it is a short list of approved enhancements. You keep the source and the documentation.

A Saudi ERP carries rules that move. ZATCA updates its e-invoicing specifications and its waves of affected taxpayers. VAT treatment can change for a type of supply. Certificates used to stamp e-invoices expire and must be renewed before they do. Left unattended, any of these turns into rejected invoices or a stuck month-end.

We keep a calendar of certificate expiries, track ZATCA announcements, and apply and test configuration changes before they reach production. Where a change needs a decision from you, such as how to treat a new invoice scenario, we bring the question with a recommendation, not an open problem.

Support also covers the security basics the National Cybersecurity Authority's controls expect of any business system: access reviews, removal of leavers, patching and backup testing, with logs kept as evidence. Where your data sits matters under the Personal Data Protection Law and cloud rules, and we can run support for systems hosted inside the Kingdom. We do not claim your company is compliant by virtue of our support. We make the routine work visible so your own compliance team can rely on it.