Global Senior Director Finance Operations — Software Entity Settlement

The mandate

Payment capacity in an international software group is still organised around service-centre queues rather than the obligations of individual legal entities. A supplier may be ready for settlement but assigned to an entity with an unresolved cash request; an employee expense may be approved yet miss the only authorised local payment window. The new global senior director will own the operational settlement architecture across three locations. Employment is open-ended, with the first twenty-four months building a service model that makes ownership and timing dependable as transaction volumes grow.

Your central question is whether each scheduled payment is supported, correctly assigned and fundable under the entity's authorised arrangements. The team must distinguish invoice readiness from cash availability and payment-file acceptance from actual beneficiary settlement. You will connect obligations to local calendars, treasury funding requests and bank rejection evidence. Intercompany settlement adds another layer: a net group balance does not eliminate the obligations of separate entities or permit operational teams to offset amounts where agreements do not authorise that treatment.

The remit covers 165 colleagues in payment operations, employee expenses and entity settlement. You may allocate operational capacity, establish run schedules and pause files with unresolved evidence. Treasury determines cash positioning, borrowing and bank mandates; controllers approve accounting and intercompany treatments; local authorised signatories release payments. Material service-location changes require executive approval. The role owns the discipline of preparing accurate, timely decisions for those authorities, not an informal power to move funds simply because the service centre believes a vendor is important.

The initial programme should leave an obligation-to-settlement forecast whose differences are explained by entity, currency and accountable action. Repeat failures must show whether data, funding, approval timing or payment connectivity caused the delay. Beyond the opening agenda, you will run ongoing service economics, workforce development and new-entity onboarding. Hyderabad is the operating base, with protected global overlap hours and planned cross-location visits. Senior managers will be expected to resolve ordinary run decisions independently so resilience does not depend on one executive remaining online across every time zone.

What you will own

• Establish the obligation-to-settlement forecast by entity and currency, tracing scheduled payments through funding requests, approval windows and bank status rather than treating payment-file creation as completion.
• Determine operational run calendars with local finance owners, defining how holidays, payroll-adjacent obligations and restricted release windows affect cut-offs and the capacity required at each service location.
• Set rejection and return escalation rules using bank evidence, distinguishing incorrect beneficiary information, unavailable funding and connectivity failures so corrective work goes to the owner able to resolve it.
• Build intercompany settlement operating controls around approved agreements and controller treatments, retaining entity-level obligations and prohibiting unauthorised offsets even when they simplify consolidated service reporting.
• Decide employee-expense service standards that link policy approval, payable readiness and local settlement, separating legitimate compliance review from repetitive processing delay that managers can remove operationally.
• Review service cost and resilience across the three locations using run complexity, critical coverage and actual rework, recommending capacity investment where settlement risk outweighs a superficially lower transaction cost.
• Develop entity-settlement managers through failed-run analysis and controlled absence exercises, demonstrating that delegated decisions remain sound when senior leaders are unavailable during a critical payment window.

Candidate qualifications

• Explain a multi-country payment operation you personally made more reliable. Identify the obligations involved, the authorised funding and release owners, and how you proved beneficiary settlement rather than relying on a successful file submission. Experience with unresolved bank responses, returned payments or entity cash constraints should show how you assigned cause without moving risk into another department's queue.
• A 22–28-year finance-operations career must include leadership across locations or a global delivery perimeter in software, technology or financial services. Establish responsibility beyond an individual payable team: operating calendars, senior-manager accountability and service capacity should have been yours to shape. Demonstrate the geographical complexity you handled and the routine decisions your managers could exercise independently.
• Bring working-capital and intercompany process knowledge sufficient to challenge an unreliable settlement forecast. You must recognise the difference between a consolidated balance, a legally payable entity obligation and a permitted settlement mechanism. Strong professional finance learning or equivalent applied depth should support productive collaboration with treasury, controllers and tax specialists without assuming their approvals can be replaced by an operations dashboard.
• Show evidence of ERP-enabled standardisation and practical service governance where local exceptions remained justified and controlled. Describe an employee-expense or payment pathway you redesigned, including access rights, approval evidence and failed-run recovery. The appointment needs someone who can build a sustainable global management bench and protect sensitive payment data, not a leader whose personal availability substitutes for resilient operating design.

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 14 October 2026. Mandate reference CVU-PER-2026-IND-127.