Data Warehouse: Wallet Balances table rebuilt

WALLET_BALANCES now derives each wallet's balance directly from its transaction history — and matches what the Monta API's GET /api/v1/wallets/{walletId} endpoint returns.

What's new

• Full wallet coverage. Every wallet in your scope now gets a row — including wallets with no transaction history, which report a balance of 0. Expect a significant jump in row count.
• New BALANCE_AT column. Shows the timestamp of the most recent completed transaction behind each balance, so you can see how current a row is.

Action required

• ID values have changed. ID is still unique and stable per wallet, but values don't carry over from the previous table. If you store or join on ID, re-key on WALLET_ID — that's the reliable identifier for a wallet's balance.
• Three columns removed: CREATED_AT, UPDATED_AT, and NEGATIVE_BALANCE_AT. These tracked internal record-keeping, not the balance itself, and are no longer populated. Remove any references to them.
• Need a real-time balance? Use GET /api/v1/wallets/{walletId} in the Monta API. The wallet list endpoint doesn't include balances, so the Data Warehouse remains the efficient way to read balances in bulk.