Financial Systems Analyst - Payments Ledger

Financial Systems Analyst - Payments Ledger
Location: Remote, US based only. Pacific time zone office hours.
Duration: 6 months

About the Role
Valutics is seeking a Financial Systems Analyst for a fintech program to move high-volume payment products onto a double-entry ledger. You will establish how money actually moves through each payment product, identify every ledger-able event, reconcile internal records to processor and bank files, and document ledger requirements that engineering can build from. Prior knowledge of the payment products is not required. The ability to learn fast and verify rigorously is, because a plausible but wrong answer in a ledger specification becomes a production defect.
This is a discovery and analysis role that works ahead of engineering. You will help move each payment rail from an initial ledger requirement to an approved chart of accounts design and a transaction simulation that engineering can build against. You will own the evidence, the analysis, the documentation, the open question log, and the handoff package.

Required Qualifications

• Experience: At least three years of hands-on experience in an analytical role where financial accuracy is critical, such as payment operations, reconciliation, revenue or technical accounting, financial systems, implementation, business analysis, or product analysis at a fintech company.
• Payment flow analysis: Demonstrated experience tracing how money moves through a live payment product, based on how it behaves rather than how it is documented, and identifying each financial event and the system trigger behind it.
• SQL: Ability to write SQL independently to extract data and confirm which fields are populated for real transactions.
• Reconciliation: Experience working out how a processor or bank reconciles, including with Claude, then tying internal transactions to its settlement, confirmation, or return files in spreadsheets and explaining variances.
• Requirements documentation: Experience defining data requirements, transaction scenarios (returns, reversals, disputes, refunds), acceptance criteria, and epics and user stories that engineering can build from without follow-up questions.
• Organizational discipline: Experience managing an open issues log across multiple workstreams and stakeholder teams, driving each item to resolution and escalating when needed.
• Persistence: Ability to follow up diplomatically with stakeholders who are slow to respond, without straining relationships.
• Clear communication: Ability to prepare design reviews, capture decisions and their rationale, and make complex analysis clear to engineers, accountants, and business stakeholders.
• Learning speed and rigor: Ability to use Claude extensively to close knowledge gaps quickly, such as an unfamiliar return code, accounting concept, or SQL pattern, and to verify every finding against a primary source or subject matter expert before it enters a specification.

Preferred Qualifications

• Exposure to ACH (return codes, effective entry date versus settlement date), card acquiring (authorization, capture, settlement, interchange, chargebacks), or cross-border payments.
• Familiarity with BAI2 or other bank statement formats.
• Working knowledge of double-entry accounting, including debits, credits, and the distinction between customer liabilities, revenue, and receivables, sufficient to follow and document journal entry discussions.
• Exposure to a ledger platform such as Fragment, Modern Treasury, Formance, or Increase, or to a home-grown ledger.
• Experience with Jira or a similar delivery tool.
• Experience supporting transaction simulations or user acceptance testing for financial systems.