Employee Highlight: Puhiza Doci

At DualEntry, I've worked across our financial platform end to end, from user-facing approval flows to backend data pipelines and third-party integrations. Each layer has different constraints, but they all share the same requirement: correctness. In financial software, a single bug in transaction import or approval routing can undermine trust.

Building the Approvals Engine: State Machines, Routing & Integrity

A major early project was v2 of our approvals system. What sounds simple, routing records through configurable approval chains before posting, required orchestration, conditional evaluation, permissions, audit trails, and strict data integrity. I helped design a system that supported serial, parallel, and conditional routing while staying predictable and configurable, and that handled real-world edge cases like unavailable approvers, mid-approval workflow changes, and race conditions. Getting the state machine and transitions right was critical.

Migrating Financial Data at Scale: Reliability Under Real-World Conditions

I also maintained and improved our migrations engine for importing historical financial data during onboarding. The goal was completing imports within a day while remaining resilient to third-party API failures. I worked on safe shutdown and resume during deployments, long-running connection reliability, and defensive error handling for network issues, rate limits, and messy data. This included SSL connection recovery patterns, persisting state before propagating shutdown exceptions, and robust duplicate detection to prevent double-imports.

Integrations in Practice: Mapping Complex Systems into a Unified Ledger

On integrations, I built and maintained connectors with different accounting and data-shape challenges. For Paycom, I mapped payroll runs, expenses, tax withholdings, and benefits into our accounting model. For Tax1099, I implemented year-specific form template selection with fallback behavior. For Sitelink, I mapped self-storage workflows, including rental income, insurance, late fees, and move-in or move-out accounting, into journal entries. I also maintained Ramp, Brex, Cubby, and Stripe, improving duplicate detection, transaction categorization edge cases, data mappings, and recovery from unexpected API responses.

‍

Overall, the work has been about building reliability in the parts customers do not always see: correct state machines, resilient migrations, and integrations that handle real-world API behavior so customers can trust their financial data.