The process areas we redesign
- Procure-to-pay: purchase requests, approvals by value, purchase orders, goods receipt, three-way match, vendor payment and TDS. See three-way match.
- Order-to-cash: quotes, credit checks, sales orders, dispatch, invoicing, e-invoicing where applicable, collections and credit notes.
- Record-to-report, including the financial statement close process (FSCP): journals, accruals, reconciliations, close calendar, financial statements and management reporting. See the month-end close checklist.
- Inventory: receipts, transfers between locations, issues to production, cycle counts and valuation.
- Hire-to-retire: onboarding, attendance and leave, payroll inputs, salary changes, full and final settlement.
- Fixed assets and capex: capex approval, capitalisation, asset register, physical verification and depreciation.
- Tax and compliance: compliance calendar, GST and TDS processes and reconciliations.
- Treasury: cash forecasting, bank mandates, payment release and forex.
- IT general controls: user access, roles, change management and backups.
- Entity-level and governance controls: policies, delegation of authority, risk register and board reporting.
How we design the future state
We follow the DMAIC cycle (Define, Measure, Analyse, Improve, Control), so every redesign starts from measured facts and ends with owners and measures that keep it working.
- Challenge each step. Every step in the current-state map must earn its place: does it add value, prevent a risk, or meet a legal requirement?
- Set owners and hand-offs. One owner per step, with a RACI for the whole process.
- Place the controls. We run an FMEA on the future-state process to rank each possible failure by severity, likelihood and detectability, then place approvals, maker-checker, reconciliations and system restrictions where the risk is highest rather than everywhere.
- Map to systems. Mark which system records each step and where the data flows next.
- Define the measures. Cycle time, error rate or days-to-close, so you can tell whether the new process works.
What you get
A future-state map for each process, a fit-gap list against your current or planned system, and a change plan. The design then feeds SOP documentation and, if you choose, Zoho implementation.
Frequently asked questions
What is the difference between process design and process re-engineering?
Process design creates a process where none is defined, which is common in young companies. Re-engineering rethinks an existing process that has grown messy. The method is the same: map, challenge each step, then design the future state.
Do you design processes around a particular software?
We design around the business first. In the Design stage we then mark which Zoho app, or which system you already use, runs each step, and flag any gaps.
Will the new process slow people down with extra approvals?
It should not. We set approval limits by value and risk, so routine low-value items flow straight through and only exceptions wait for a senior approver.
General information only, not legal, tax or software licensing advice. Zoho features, editions and prices change, so confirm the current position with Zoho or with our team before you commit. See our disclaimer.
