About The Role Stavtar builds StavPay, the expense, invoice, allocation and payments platform used by hedge funds, private-equity firms and family offices to run their entire payables cycle — from invoice capture and multi-entity allocation through to money actually leaving the bank.

This role sits in the Dev.Payment.Banks pod, which owns everything between a StavPay invoice and a bank. That means the payment rails themselves (ACH, wire, cheque, positive pay, ISO 20022), the bank-specific file templates, the FTP/API transmission jobs, the return and acknowledgement processing, and the reconciliation back into the GL feed.

This is a configuration, integration and onboarding role. The bulk of the week is spent standing up payment rails for new clients and banks, keeping live rails running, and diagnosing what went wrong when a payment file does not land. The depth required is in SQL, in payment file formats, and in the discipline of tracing a failure to its actual cause.

What the work actually looks like Client L3 support & production troubleshooting - ~20%

Root-cause analysis on live payment failures across 30+ client instances — failed ACH/ISO files, stuck batches, mis-set invoice states, FTP delivery gaps, reconciliation breaks.

Client & bank onboarding - ~29%

Standing up new clients and new banking relationships: debit/credit account loads, payment rules, vendor payment detail grids, template configuration, FTP credentials and key vault setup.

Enablement & internal projects - ~22%

Domain deep-dives, documentation, QA and UAT environment setup, process improvement, training.

Meetings & coordination - ~17%

Working directly with BAs, QA, BPO, DBA/deployment, and occasionally client-side and bank-side contacts.

Infrastructure & scheduled jobs - ~12%

Job schedulers, FTP/SFTP configuration, environment sync between QA/UAT/Prod, deployment support.

Key responsibilities Payment rails & bank integration

- Configure and maintain bank payment templates end to end — invoice grid, preview grid, payment grid, header queries, template filters and payment-rule logic — for ACH, wire, cheque, positive pay and ISO 20022 rails.
- Build and troubleshoot ISO 20022 (pain.001, pain.002, CAMT) and NACHA-format file generation, including tag ordering, mandatory field mapping and bank-specific deviations.
- Own the transmission layer: FTP/SFTP connections, key vault credentials, folder paths, job schedulers, and the acknowledgement/return file loops that close them out.




- Onboard recent banking relationships alongside BAs and the client — most recently JPMorgan, Bank of America, BankUnited, Citizens, Citibank, Mercury, Banc of California, Kyriba and Dwolla.

Data, diagnosis & scripting

- Write and review T-SQL against a multi-tenant SQL Server estate — stored procedures, views, and DML/DDL scripts delivered through pull requests in Azure DevOps.
- Perform genuine root-cause analysis rather than symptom patching: trace a failure from the UI through the API and query layer into the allocation and payment tables, and state the actual cause with evidence.
- Prepare and execute controlled data fixes on production data — bulk account loads, allocation-payment corrections, payment-status remediation — with scripts that are peer-reviewed and reversible.
- Read Azure application logs to diagnose job failures, file-transmission errors and integration faults, and hand a clean, reproducible defect write-up to the development team when a code change is required.

Client support & delivery

- Act as L3 escalation for payment issues across the client base, working with BAs and the BPO team to reproduce, diagnose, communicate and resolve.
- Own assigned clients through onboarding and into steady state, so that the person who configured a rail is the person who supports it.
- Support QA and UAT: configure templates on request, sync environment configuration, and unblock test cycles.
- Communicate clearly in writing. Every work item should carry a note a BA or a manager can read and understand without asking a follow-up question.

What we need you to bring Must have

- 3–6 years implementing or supporting enterprise software for external clients. You have worked hands-on against a live production system, not only in a shadowing or training capacity.
- SQL Server — this is the core technical gate. Confident with complex T-SQL, reading and modifying stored procedures and views, query performance, and writing safe DML/DDL scripts against production data.
- Payments domain exposure — real, hands-on work with at least one of: ACH/NACHA, wires, ISO 20022 / SWIFT MT,



cheque and positive pay, or bank host-to-host file integration.
- File and system integration — SFTP/FTP, scheduled jobs, file parsing and generation, retry and failure handling.
- Configuration-heavy product experience — you are comfortable that much of the behaviour lives in data and config, not only in code, and you keep that config disciplined.
- Clear written English — you can explain a root cause to a business analyst in three sentences.
- Working-hours overlap — a meaningful daily overlap with US Eastern hours, plus availability during month-end and payment-run peaks.

Strongly preferred

- Financial services background — fund administration, treasury, hedge fund / private equity operations, accounts payable or expense management platforms.
- Familiarity with invoice-to-payment lifecycles: approval workflows, multi-entity allocation, legal entities, chargebacks and credit notes.
- GL integration experience — Dynamics GP, NetSuite, or similar accounting-system feeds.
- Azure: App Insights / Azure Monitor for log-driven diagnosis, Key Vault, scheduled jobs.
- Azure DevOps — repos, pull requests, pipelines and work-item hygiene.
- Exposure to bank portals and treasury platforms such as Kyriba, or payment providers such as Dwolla.

Nice to have

- C# / .NET — enough to read the application code and follow a request from the UI through the API into the database, and to make small reviewed fixes. Useful, but not a requirement; we will take deep SQL and payments knowledge over it every time.
- Prior experience at a fund administrator, fund accounting vendor, or payments / treasury software company.
- Experience replacing a manual configuration process with a repeatable or automated one.
- SQL Server temporal / system-versioned table experience.
- Exposure to positive pay, reverse positive pay, or bank fraud-control file exchange.

Technical environment Backend C# / .NET, Web API, Dynamic LINQ query layer, background job framework Data SQL Server — stored procedures, views, system-versioned temporal tables, multi-tenant client databases

Payment formats ISO 20022 (pain.001, pain.002, CAMT), NACHA ACH, wire, cheque / positive pay, bank-proprietary CSV and XML

Integration SFTP / FTP host-to-host, bank APIs, Kyriba, Dwolla, SEI, custodian and administrator feeds

Cloud & tooling Azure (App Service, Key Vault, App Insights / Log Analytics), Azure DevOps repos, pipelines and boards

📌 Payments Engineer (Bengaluru)
🏢 Stavtar Solutions
📍 Bengaluru