Principal, Regulated Finance Systems Transition — Loan-to-Ledger Evidence

The mandate

An NBFC is moving its accounting operation to a new system while retaining established loan-processing and bank interfaces. Technical migration progress does not establish that financial information remains traceable through the change. The principal will own the specialist finance transition method: mapping movements to ledger treatment, testing converted balances and designing the evidence needed for management's cutover decision. The project concerns the integrity of the agreed finance interfaces, not selection of an ERP vendor or a change in the company's loan-policy model.

Work starts on 26 October 2026 and runs for six months, with four days reserved weekly. The ₹66,00,000 fee is payable in 30%, 35% and 35% stages against accepted artifacts. Mumbai workshops and remote interface reviews are included. The sponsor provides current accounting rules, loan movement samples, bank records, conversion extracts and seven internal owners with protected test time. Missing or disputed source information must be recorded as an acceptance dependency rather than silently replaced by a convenient migration assumption.

On 15 December 2026, the first milestone delivers the transaction-to-ledger map and signed conversion baseline. On 25 February 2027, the second supplies tested interface cases, balance reconciliations and an exception-routing design. On 26 April 2027, final delivery provides the cutover evidence file, fallback decision criteria and independent internal replay. The CFO and ERP sponsor accept together, with controller validation of financial treatment. Acceptance tests cover duplicate, reversed, delayed and incomplete movements as well as normal cases, demonstrating whether the agreed design preserves both amount and meaning.

The principal is accountable for technical finance analysis, reproducible testing and a usable transfer package; management retains system operation and cutover authorisation. Scope excludes software coding, regulatory opinion, ongoing close management and redesign of credit processes. Added interfaces or revised policy conclusions require written scope, fee and schedule approval. Final payment depends on accepted evidence and user capability, not a future live-system outcome. A controlled recommendation to defer cutover can be a valid project conclusion if specified tests reveal unresolved risks that internal owners cannot yet responsibly accept.

What you will own

• Map the agreed loan and bank movements to accounting inputs, reviews and ledger consequences, distinguishing processing events from financial treatment before a technical field conversion is accepted as complete finance design.
• Establish the opening-balance conversion baseline with controllers, reconciling totals and significant attributes so an apparently balanced migration cannot conceal missing ageing, classification or evidence needed for subsequent financial judgement.
• Design interface tests for normal and adverse cases, including duplicates, reversals and late movements, agreeing expected finance treatment before developers or users assess the outputs against an attractive demonstration case.
• Produce reconciled second-stage results and exception routes with named owners, separating software defects, missing source evidence and disputed accounting interpretation because each requires a different authority and repair method.
• Develop cutover and fallback evidence criteria for sponsor approval, showing the financial consequence of unresolved cases without claiming authority to launch the system or direct the operating company's reporting decisions.
• Facilitate independent accountant replay of transaction cases and balances, correcting ambiguous guidance and retaining proof that internal owners can investigate a mismatch without depending on the principal to interpret every result.
• Deliver the final transition file with residual risks, maintenance ownership and agreed change boundaries, making deferred work visible rather than treating an unpriced period of post-go-live troubleshooting as part of completed consulting acceptance.

Candidate qualifications

• Bring twenty-eight years or more of professional experience, including senior accounting or financial-management responsibility in regulated services and a substantive ERP or finance-system transition. Explain a migration issue whose financial meaning differed from its technical appearance. Personal evidence must show the records you tested, the accounting owner involved and the acceptance decision changed by your work, rather than general participation in a successful implementation.
• Demonstrate strong loan-accounting, reconciliation and reporting competence through appropriate preparation or equivalent established senior practice. You must distinguish balance agreement from completeness of attributes and subsequent usability. Show how a converted amount was mathematically correct yet insufficient for reliable finance operation, and how qualified review determined the treatment without allowing the project to invent policy merely to make conversion easier.
• Have created repeatable finance-interface and cutover tests with technology and operating teams. Evidence should include a non-standard movement, the expected result agreed beforehand and an exception that required escalation rather than a manual adjustment. Specialist standing requires disciplined technical reasoning while preserving management's cutover authority and compliance owners' interpretation of regulated obligations outside the agreed migration analysis.
• Reserve the stated four-day capacity across all six months and demonstrate transfer through internal replay. Show how you recorded unavailable inputs, controlled added scope and reached an honest acceptance conclusion when readiness was incomplete. Confidential loan and customer records require protected handling. The engagement must end with usable evidence and accountable owners, not a promise that external expertise can guarantee every live processing or reporting outcome.

Application

Applications for this mandate are received in one way only: through the India Board Terminal's application process. It is automated end to end. Your Executive Passport travels to the mandate holder in its confidential form, your answers to the three questions below are read before anything else in your file, and every stage that follows is recorded on your applications page.

There is no address to write to and no intermediary to call. The mandate holder reads what the Terminal delivers and nothing else, which is what keeps the process the same for every applicant and keeps your name out of it until you release it. Applications close on 8 October 2026. Mandate reference CVU-CON-2026-IND-249.