Settlement Trail Review
A focused examination of payment and payout settlement files against ledger postings when partner reports and your books disagree on timing or amounts.
Read the briefTaipei desk · Taiwan engagements
White Pine Ledger Review
We read fintech ledgers the way directors and counterparties will: following customer funds, settlement batches, and control claims until the story either holds or breaks.
Evidence first: bank credits, partner files, and the journals that claim to match them.
Flagship engagement
Ledger & Control Audit
For payment, lending, and wallet operators who need an independent view of whether balances, clearing accounts, and stated controls stand up under questions. The engagement produces a findings memorandum, reconciled sample trails, and a remediation sequence your team can actually staff.
Related engagements
Other work on the same desk
Supporting reviews for teams who need a narrower cut before — or after — a full ledger audit.
Pre-Licence Control Readiness
A readiness review of control narratives, segregation evidence, and ledger hygiene before you invite supervisory or investor diligence on a new fintech licence path.
Read the brief
Board Pack Finance Review
An independent challenge of the finance section in your board pack — balances, variance stories, and risk footnotes — before directors meet.
Read the briefFrom the field
What clients remember afterward
“They traced a remittance corridor we thought was clean and found the fee column was posting two days behind the principal. The board pack that month finally matched the partner file.”Mei-Ling Chen · Finance lead, cross-border payments operator
“The readiness scorecard was useful, though it took us longer than we hoped to gather bank letters. Once evidence arrived, the gap list was specific enough to assign owners without another workshop.”Arthur Wu · COO, pre-licence wallet venture
How we work
Document-first, then interviews
We begin with ledger extracts and partner files, not a slide workshop. Interviews happen after samples are chosen, so questions stay concrete. Remediations are sequenced for close cycles you already run — not for a theoretical operating model.