Reading partner settlement files before they reach the ledger

Partner settlement files are rarely written for your chart of accounts. They arrive with their own batch IDs, fee columns, and cut-off conventions. Teams that post first and reconcile later spend the month explaining the same breaks.

Start with the partner’s cut-off language. Does “settlement date” mean when the partner initiates the transfer, when the bank credits you, or when the batch closes in their portal? Write the answer down. Audits for fintech that ignore cut-off language produce false exceptions and miss real ones.

Next, separate gross customer funds from fees and FX adjustments. Many ledgers collapse these into a single clearing account. That can work for a quiet month; it fails when a reviewer asks you to prove segregation or to explain a fee spike.

When White Pine traces settlement batches, we ask for three artifacts side by side: the partner file, the bank credit, and the ledger posting. If any one is missing, the trail stops — and the finding is about evidence hygiene, not necessarily about misstated balances.

If your operations team can produce that trio for ten consecutive batches without hunting through chat threads, you are already ahead of most diligence conversations.