What the work looked like from the other side of the table
These notes name the engagement and the constraint. They are not star widgets.
Their payment-control walkthrough caught a settlement cut-off mismatch we had lived with for two quarters. The working papers were dense, but the board summary was usable the same afternoon.
We asked for a licensing readiness check before our FSC filing. The team declined to rubber-stamp incomplete KYC sampling — that honesty slowed us by three weeks and saved a worse conversation with examiners.
Investor diligence kept circling our lending underwriting files. Pine Current mapped the gaps against our actual credit committee minutes, not a generic checklist.
The reconciliation sampling felt thorough without turning into theatre. One mild reservation: fieldwork ran a day longer than the estimate when our ledger export failed twice.
Extended case notes
Cut-off mismatch at a Kaohsiung e-wallet
A Payment Control Review for a mid-size wallet operator found that weekend remittance files posted to Monday’s ledger while exception aging reset on Sunday night. Sample testing across two cycles showed the pattern was structural, not a holiday anomaly. Management adjusted cut-off ownership before the next board pack; our letter ranked the residual risk as medium pending a full calendar rewrite.
Licensing pack delayed on purpose
A remittance startup requested a Licensing Readiness Audit three weeks before an intended FSC filing. KYC sampling failed dual-review claims on high-risk corridors. We declined to soften the gap list. The team postponed filing, rebuilt sampling evidence, and returned eight weeks later with a cleaner pack. The delay was inconvenient; an unsupported narrative would have been worse.
Start with a scoping call
If your constraint is a board date, a filing window, or an investor data room, say so early — it shapes sample size and delivery mode.