Two monitors showing ERP modules and a purchase-to-accounts process flow

ServiceFinance & Business Advisory

Business process advisory

Finance processes that close on time, carry their own controls and are ready for the system you run them on.

Most finance problems that appear at month-end begin earlier, in the way a purchase is approved, a sales order is booked or a journal is posted. Business process advisory looks at those processes end to end: procure-to-pay, order-to-cash and record-to-report. The work covers reviewing how each process runs today, redesigning it where needed, writing standard operating procedures and a delegation of authority, and building controls into the steps themselves. Where a business is moving to a new ERP, the firm represents the finance view: requirements for the finance modules, data migration, cut-over and user acceptance testing. The firm is not a software implementer and does not configure, license or resell systems.

Service overview.

Processes in a growing business are usually built by habit. A purchase order is raised after the invoice arrives because the material was needed urgently. Credit notes are issued by the sales team without reference to accounts. Journals are posted by whoever has access, and reconciliations are done when the auditor asks for them. Each shortcut seems reasonable at the time; together they produce a close that takes three weeks, ledgers that need correcting at the year-end and figures that management does not fully trust.

The pressure to fix this tends to arrive with a specific event. The company is adding a plant, a warehouse or a state. A foreign parent wants the Indian entity to follow group policies. The statutory auditor reports weaknesses in internal financial controls. Or the business has decided to replace its accounting package with an ERP, and the implementation partner is asking finance to describe how things should work, a question nobody has written down an answer to.

In each case the need is the same: a clear, written description of how purchases, sales and the financial close should run, who may approve what, which controls sit at which step, and what the finance function needs from its systems. Without that, a new ERP tends to automate the existing workarounds, and a new policy remains a document rather than a practice.

The firm's role is to work through these processes with the people who run them, record what happens today, agree what should happen, and support finance during any system change so that the new system produces reliable accounting, tax and management information from the first period of use.

  • 07Areas of assistance
  • 08Process stages
  • 08Key deliverables
  • 02Sectors served

Business challenges.

  • Slow and unreliable period close

    The books take weeks to close because reconciliations, accruals and inter-branch entries are left to the month-end. Corrections are passed late, figures change after they are reported, and the finance team spends most of its time on the close rather than on analysis.

  • Purchases approved after the event

    Orders are placed by phone, goods arrive without a purchase order and invoices are paid on the strength of a signature. Three-way matching between order, receipt and invoice is not possible, and the business cannot see its commitments until bills reach accounts.

  • Revenue leakage in order-to-cash

    Prices, discounts and credit limits are applied inconsistently across branches. Credit notes, free goods and rate differences are issued without approval, and receivables include old disputed items that nobody owns. The result is lost margin and collections that are hard to follow up.

  • Unclear authority to approve

    Nobody can say with confidence who may sign a purchase order of a given value, approve a new vendor or write off a balance. Approvals depend on who is available, and the same person often initiates, approves and records a transaction.

  • ERP projects without a finance voice

    A system integrator configures the software to a timeline, while finance is busy with daily work. Chart of accounts, costing, tax and closing requirements are decided late or not at all, and problems are discovered only after go-live.

  • Data that does not survive migration

    Opening balances, open purchase orders, customer and vendor masters and inventory are moved into the new system without full reconciliation. Differences appear in the first months of use and are hard to trace back to the legacy system.

Our approach.

  1. 01

    Scoping with management

    Agreement on the processes, locations, entities and any system project in scope, and on what the business wants to achieve.

  2. 02

    Current-state walkthroughs

    Interviews and walkthroughs with process owners, tracing sample transactions from start to finish to see how work is actually done.

  3. 03

    Gap and risk analysis

    Comparison of current practice with the business's needs, statutory requirements and sound control practice, with gaps ranked by their effect.

  4. 04

    Future-state design

    Redesigned processes, approvals and controls agreed in workshops with the people who will run them.

  5. 05

    Documentation

    Process maps, SOPs, the delegation of authority and risk and control matrices drafted, reviewed and approved.

  6. 06

    System requirements and review

    Where an ERP is involved, finance requirements prepared and the integrator's design reviewed before build.

  7. 07

    Migration, testing and cut-over

    Data reconciliation, user acceptance testing from a finance view and a cut-over checklist, with defects tracked to closure.

  8. 08

    Stabilisation and handover

    Support for the first periods under the new process or system, and handover of documents to the process owners.

How the firm works with you

  • Finance at the centre

    Processes are designed from the point of view of the accounts they produce, so that each transaction leaves a clear trail to the financial statements.

  • Controls as part of the work

    Controls are placed inside the process steps, where they prevent errors, rather than added as a review at the end.

  • Built with process owners

    Designs are agreed in workshops with the people who run purchases, sales and accounts, so that the result reflects how the business actually works.

  • Independent of software vendors

    The firm does not sell, license or implement software, so its view on requirements and design is not tied to any product.

  • Documented and traceable

    Requirements, decisions, test results and sign-offs are recorded, so that auditors and the parent can follow what was agreed and why.

  • Plain communication

    Findings are explained in plain language to operating teams and management, with clear owners and dates for each action.

Scope & deliverables.

Each part of the service can be engaged on its own or together, depending on what the business needs.

  1. 01Procure-to-pay process review and redesign

    Procure-to-pay covers the cycle from a purchase requisition to payment of the supplier: requisition, vendor selection and onboarding, purchase order, goods or service receipt, invoice booking, matching, payment and vendor reconciliation.

    More detailLess detail

    The review traces actual transactions through each step, identifies where the documented process is bypassed and looks at vendor master controls, duplicate payments, advances, debit notes and compliance points such as withholding tax, GST input credit and payment timelines for micro and small enterprises.

    The firm documents the current process, agrees a future process with the purchase, stores and accounts teams, and specifies the approvals, matching rules and reports needed at each step.

    What you can expect: a written procure-to-pay process with clear hand-offs, defined approvals and matching rules, and a list of the control gaps found with practical fixes.

  2. 02Order-to-cash process review and redesign

    Order-to-cash runs from a customer order to cash in the bank: customer onboarding and credit limits, pricing and discount approval, order booking, dispatch, invoicing, returns and credit notes, collections and customer reconciliation.

    More detailLess detail

    Weaknesses here affect margin, cash and the accuracy of revenue.

    The work examines price and discount master controls, credit limit overrides, cut-off between dispatch and invoicing, approval of credit notes and schemes, ageing and the treatment of disputed balances. The firm then works with sales, logistics and accounts to agree a process that keeps commercial flexibility while recording every concession and its approver.

    What you can expect: an order-to-cash process that links each invoice, credit note and receipt to an authorised order, with a clear collections routine and receivables reporting.

  3. 03Record-to-report and the financial close

    Record-to-report covers how transactions become financial statements: journal entries and their approval, sub-ledger to general ledger reconciliation, bank and inter-company reconciliations, accruals and provisions, fixed asset accounting, the month-end checklist and the preparation of management and statutory reports.

    More detailLess detail

    The firm designs a close calendar with tasks, owners and deadlines, standard reconciliation formats, rules for manual journals and a review sequence before figures are released. Where the business follows Ind AS or prepares group reporting, the process is aligned with those requirements and the parent's timetable.

    What you can expect: a documented close process with a calendar and checklist, reconciliations that are prepared and reviewed every period, and a shorter, more predictable close.

  4. 04SOPs and delegation of authority

    Standard operating procedures turn an agreed process into instructions that staff can follow and auditors can test.

    More detailLess detail

    Each SOP sets out the purpose, scope, steps, responsibilities, documents, approvals and records for one activity. A delegation of authority matrix sets the limits within which each role may commit the business: purchases, capital expenditure, contracts, price and discount approvals, write-offs, payments and journal entries.

    The firm drafts SOPs and the delegation of authority with the process owners, reviews them against the organisation structure and segregation of duties, and presents them for approval by management or the board.

    What you can expect: concise, usable SOPs and an approved authority matrix that can be mapped directly to approval workflows in the system.

  5. 05Controls embedded in processes

    Controls work best when they are part of the process rather than a review after it.

    More detailLess detail

    The firm identifies the key risks in each process and designs controls at the relevant step: system-enforced approvals, three-way matching, master data change controls, maker-checker on payments and journals, exception reports and periodic reconciliations. Each control is recorded in a risk and control matrix with its owner, frequency and evidence.

    This work supports the company's internal financial controls framework under the Companies Act, 2013 and makes later testing by internal and statutory auditors more straightforward. It is a design exercise; independent testing of the controls is a separate internal audit engagement.

    What you can expect: a risk and control matrix for each process, with controls that are built into daily work and leave evidence that they operated.

  6. 06ERP finance-module requirements

    When a business selects or implements an ERP, finance needs to state its requirements before configuration begins.

    More detailLess detail

    The firm prepares finance requirements covering the chart of accounts and ledger structure, cost and profit centres, inventory valuation and costing methods, tax determination for GST and withholding tax, approval workflows from the delegation of authority, period-close functions, statutory and management reports, and the audit trail.

    Under the Companies (Accounts) Rules, 2014, companies that maintain books in accounting software must use software with an audit trail feature that cannot be disabled, and the auditor reports on this. The requirements document records this and other statutory needs so that they are addressed in the design.

    The firm reviews the integrator's design documents from a finance view and raises gaps before build. Configuration, development and licensing remain with the client's chosen software vendor or integrator.

    What you can expect: a finance requirements document the integrator can work from, and a finance review of the solution design before it is built.

  7. 07Data migration, cut-over and user acceptance testing

    Moving to a new system is a point of risk for the accounts.

    More detailLess detail

    The firm helps define what will be migrated (masters, opening balances, open documents, inventory and fixed assets), the cut-off date, reconciliation between the legacy and new systems, and sign-off by finance. A cut-over plan sets the sequence of closing the old system, loading data and opening the new one.

    In user acceptance testing, the firm prepares finance test scenarios and expected results, covering purchase and sales cycles, tax calculations, inventory valuation, the period close and financial statement output, and reviews results with the finance team. Defects are logged with the integrator and retested before sign-off. After go-live, the firm can support the first period closes and reconciliations.

    What you can expect: reconciled migration with documented sign-off, finance test scripts and results, and support through the first closes in the new system.

Key deliverables

  • Current-state process documentation

    Narratives and process maps showing how procure-to-pay, order-to-cash and record-to-report run today.

  • Gap and recommendations report

    Control and efficiency gaps ranked by effect, with practical recommendations.

  • Future-state process design

    Agreed processes with hand-offs, approvals and reports at each step.

  • SOPs and delegation of authority

    Approved procedures and an authority matrix ready to be mapped to system workflows.

  • Risk and control matrices

    Key risks, controls, owners, frequency and evidence for each process.

  • ERP finance requirements

    A requirements document for the finance and costing modules, with finance review of the design.

  • Migration and test records

    Reconciliations, sign-offs, finance test scripts and defect logs.

  • Cut-over and close checklists

    Step-by-step plans for go-live and for the period close.

Value & outcomes.

Who can benefit, and how

Manufacturing businesses
Need costing, inventory and procurement processes that support accurate margins and a timely close.
Automotive and engineering suppliers
Face customer pricing, tooling, job work and multi-plant transfers that test order-to-cash and inventory processes.
Companies implementing an ERP
Need finance requirements, migration controls and testing represented throughout the project.
Subsidiaries of foreign groups
Must align local processes with group policies, reporting calendars and control frameworks.
Growing MSMEs and family businesses
Have outgrown informal approvals and need written processes before adding locations or people.

Practical applications

These scenarios are illustrative. They describe common situations and are not accounts of particular clients or assignments.

  • Illustrative scenario 01

    An auto-component maker moving to an ERP

    A manufacturer supplying vehicle makers is replacing its accounting package with an ERP that will also run production and stores. The integrator needs finance requirements within weeks. The work covers a revised chart of accounts, standard costing and inventory valuation rules, GST determination, approval workflows and finance test scenarios, followed by reconciliation of opening stock and balances before go-live.

  • Illustrative scenario 02

    A multi-plant manufacturer with a long close

    An engineering company with three plants takes nearly a month to close its books. Inter-unit transfers do not agree and accruals are estimated at the year-end. The response is a close calendar with owners, standard reconciliation formats, monthly accrual routines and rules for manual journals, introduced over two or three closes.

  • Illustrative scenario 03

    A subsidiary aligning with group policy

    The Indian subsidiary of a foreign group must adopt the parent's procurement and approval policies. Local practice differs, and approval limits are informal. The firm maps current procure-to-pay practice, drafts SOPs and a delegation of authority consistent with group policy and Indian requirements, and designs controls that the parent's auditors can test.

  • Illustrative scenario 04

    A distributor tightening credit notes

    A consumer goods distributor finds that margins fall short of plan, and schemes and rate-difference credit notes are issued by the field team. Order-to-cash review traces each type of concession, sets approval limits, links credit notes to approved schemes and introduces a monthly exception report for management.

Frequently asked questions

Questions, answered plainly.

Do you implement or configure ERP software?

No. The firm is not a software implementer and does not configure, develop, license or resell systems. It represents the finance view in the project, preparing requirements, reviewing design, controlling migration and testing from a finance perspective, while the chosen vendor or integrator builds the system.

Can you help us choose an ERP?

The firm can prepare finance requirements and help assess how well proposed solutions meet them. The decision on a product and an implementation partner remains with management.

How long does a process review take?

It depends on the number of processes, locations and entities. A review of one process at a single location can be completed in a few weeks; a full redesign alongside an ERP project runs with the project timeline. The scope and timetable are agreed in the engagement letter.

Is this the same as internal audit?

No. Process advisory designs and documents processes and controls. Internal audit independently tests whether controls are working. The two can be done in sequence, though where independence matters the firm considers whether both roles should be carried out by the same team.

Can you work with our statutory auditor's requirements?

Yes. Processes and controls can be documented in a form that supports the internal financial controls work of management and the auditor. Where the firm is the company's statutory auditor, the services it may provide are restricted by the Companies Act, 2013 and the ICAI Code of Ethics, and the firm considers these before accepting the work.

What do you need from us to start?

An organisation chart, any existing policies and SOPs, the chart of accounts, recent audit observations, details of the current and any planned system, and time with the heads of purchase, sales, stores and accounts.

Discuss your requirements.

Discuss your process or system requirements with the firm. A short description of the business, its locations and any planned system change is enough to begin.