Sufyan Taskin
All work

Accounting software for law firms. I own the project end to end.

Credit notes at a legal accounting product

Making credit notes a first-class document, split into eight pipelined slices.

I buildQA testsTimeSlice 1Slice 2Slice 1Slice 3Slice 2Slice 4Slice 3Slice 5Slice 4Slice 6Slice 5Slice 7Slice 6Slice 8Slice 7Slice 8
Eight slices, pipelined. While QA tests one slice, I build the next, so building and testing run side by side.

The problem

Credit notes were entered as negative purchases. Payments could not offset them cleanly, and every report had to work around it.

What I did

I made credit notes a first-class document with their own entry screen, offset against purchases at payment.

I reworked batch pay so users group several purchases and credit notes into one payment. I traced and changed every report and code path that touches purchases.

The key decision and its tradeoff

How to work with a busy PO. I wrote the company’s first BRD so every decision sat in one document. The PO approved it in one meeting. I designed the screens with AI before coding.

The work was split into 8 slices and pipelined: QA tests one slice while I build the next. I write the tickets and direct QA.

The result

[TODO: status or outcome when available]