Jisr × Microsoft Dynamics 365 — Accounting Integration

For enterprise customers, the deal rarely stalled on HR features — it stalled on finance. HR teams saw Jisr's value quickly, but finance and accounting teams wouldn't sign off until they were certain payroll, expenses, and settlements would post correctly into the accounting systems they already trusted — Microsoft Dynamics 365 first among them.

That made the work far more than a technical connector. The integration moves users across systems, asks for sensitive connection details, and requires mapping subsidiaries, cost centers, and a full chart of accounts precisely — without ever feeling long, technical, or risky. A single wrong mapping means a transaction posted incorrectly, and that alone breaks trust.

I led this project end to end — research, design, and team alignment.

I went in with a clear conviction: I couldn't design the screen flows or the integration with financial and accounting systems until I understood how these people actually work — independent of the solution we were aiming for. What tools do they use? What problems do they face with HR around financial transactions? And how is trust built between them? I refused to draw a single screen before I understood that — and before I understood our own constraints inside Jisr — so the integration would come out simplified, not complicated.

I spent about three months understanding the domain — with the product manager, finance experts, and accountants, and across organizations of different sizes, because the way financial structures are built differs from one company to the next.

The interviews were with the finance and accounting teams of organizations planning to adopt the solution, through online sessions and in-person meetings. I focused on which tools they connect through, how data is pulled and financial structures are built, and exactly where the handoff between them and HR breaks down.