Business Analyst

Proviniti; United States; On-site; USD 95,000 - 140,000; Full time

Job summary

Proviniti is seeking a seasoned Business Analyst to join our Finance and Payments team in the United States. You will lead interviews with client leads, document current processes, and map data flows across Salesforce, NetSuite and payments platforms.

The role focuses on reconciling data, defining KPIs, and drafting Phase 2 requirements and UAT scripts. Strong Excel, SQL and BI skills are essential, with a payments background preferred.

Qualifications

• 7+ years as a business analyst in payments/fintech
• Experience with merchant acquiring, ISO, or fintech finance
• Proficient in SQL and data reconciliation

Responsibilities

• Document for Phase 2 through interviews and process mapping
• Map data flows across Salesforce, NetSuite and payments platform
• Define KPIs and the system-of-record matrix with owners and conflicts
• Draft requirements and UAT scripts for Phase 2

Skills

Advanced Excel

SQL basics

Power BI

Tools

NetSuite

Salesforce

Job description

Phase 1 is mostly fact-finding, and the business analysts do most of it. They sit with the client’s leads, work out how each process runs today and where the data goes wrong, and write it down well enough that the next phase can be built from it. The Phase 1 deliverables are, in effect, the requirements for Phase 2.

Much of what the client knows lives in people’s heads rather than in documentation. Both analysts need to be comfortable drawing that knowledge out in interviews and then checking it against the data.

What analyst does

• Prepare for, run and write up one-on-one interviews with the client’s functional leads.
• Document the life cycle of each business use case, such as boarding a new merchant, adding a merchant ID or setting up a new partnership. Capture the steps, systems, hand-offs, exceptions and manual work.
• Map entities, fields and process flows across Salesforce, NetSuite and the payments platform.
• Fill in the system-of-record matrix: for each critical field, where it is created, where it is edited, where it is consumed, who owns it today and who should own it.
• Define KPIs for the metric catalog, with the business definition, the source, the owner and any conflicts between teams.
• Record historical data requirements for each business area: how far back data must be corrected, how long it must be kept, and which elements must be real-time.
• Point out where the client can cut time or cost from a process.
• Draft requirements, exception rules and UAT scripts for Phase 2.

Finance and Payments

This analyst works with Finance and FP&A (daily volume, roll-forward reporting) and with Billing and Accounting (book-to-bill). The work centers on why Finance, Sales and Operations report different numbers, and what it takes to make them agree.

Problems this analyst will dig into

• Financial truth comes from third-party processors in monthly files that arrive about 23 days after month end. Each processor sends different fields.
• Daily gateway data and monthly processor data use different timing, settlement and batching rules. Finance reconciles them by hand today.
• When a merchant moves between processors, its merchant ID changes, so the merchant shows up as both lost and new. That corrupts cohort, attrition and revenue reporting.
• Thousands of merchants exist only in processor data and not in any internal system.

Required

• 7 or more years as a business analyst, with at least 3 years in payments, merchant acquiring, an ISO or payment facilitator, or fintech finance.
• Working knowledge of interchange, residuals, settlement, chargebacks, merchant IDs and merchant hierarchies.
• Experience with month-end close, revenue reporting and the reconciliations behind them.
• NetSuite or a comparable ERP, from the reporting side.
• Strong Excel, and enough SQL to reconcile two data sets yourself. Preferred for this track
• Power BI or another BI tool.
• Healthcare or practice-management software.

What good looks like at week 12

• Every use case in the analyst’s functions documented and confirmed by the client lead who owns it.
• The analyst’s rows of the system-of-record matrix and KPI catalog complete, with conflicts called out by name.
• A list of process fixes, with the time or cost each would save.
• Requirements and UAT scripts the Phase 2 team can start from.