What You’re Reporting and Why
A Balance is your customer’s position in a product on an Account: for deposit products, the money they hold; for credit products, the loan or line and the outstanding position against it. A Transaction is an individual item of activity against a balance. Because you are the ledger of record for your customers, these are reporting objects (Executing vs. Reporting) — you maintain them in your systems and report them to Lead, and Lead’s compliance oversight of your program depends on their accuracy and timeliness.Deposit Balances
Deposit balances are created and maintained entirely through the daily files. Lead reconciles what you report against its own records of the money on the core surface, including — where your program uses them —rewards_amount, dispute_balance, charge_off_balance, and interest_accrued_balance alongside balance.
Credit Balances
Credit balances are additionally created through the Subledger Balance API — the object itself, its two structures (non_revolving / revolving), and its terms live on The Balance Object in Lending & Receivables — and then serviced through the same daily files as everything else. The distinction matters operationally: the position you report gates what happens next. Available credit — which limits the next Funding draw — is computed from what you report, so reporting accuracy is load-bearing, not just compliance-relevant. Credit reconciliation covers balance and its components principal, fees, and interest, plus rewards_amount, dispute_balance, charge_off_balance, and past_due_balance where applicable — the same components readable back on the Balance object’s live position.
The Daily Reporting Rhythm
Balance and Transaction files are due by 6:00 a.m. CT the business day after the activity (T+1). Two habits keep the rhythm healthy:- Report empty days explicitly. Submit an empty file on days with nothing to report — silence is indistinguishable from a broken pipeline.
- Watch the alert channel. Every submission produces a Slack alert: 🟢 on validation success, 🔴 with an error code, detail, and action on failure. Fix the flagged file, upload the corrected version, and Lead re-validates the latest version of each file in the batch. Error codes and resolutions: File Submission Validation Errors and Balances & Transactions Files Troubleshooting.
Reconciliation
Lead reconciles your reported positions daily against one invariant:balance on T = balance on T−1 + the transactions affecting the balance on TAssert the same identity in your own pipeline before submission — a file that fails it at Lead will fail with a balance-mismatch error naming the expected sum and the delta, but catching it pre-submission keeps your reporting day clean. Full mechanics: Balance Reconciliation.