Accounting & reconciliation

Keep the books tied to reality. The platform records the journal activity behind funding, collections, and payouts, and helps you reconcile against the bank.

Journal entries

Money-moving events post journal entries with balanced debits and credits, in integer cents. This gives you a ledger you can trust without exporting to a spreadsheet first.

Bank reconciliation

Match posted activity against your bank statement to confirm what actually cleared. Reconciliation surfaces discrepancies - missing deposits, unexpected returns - so nothing slips through.

Statements

Schedule periodic merchant statements summarizing balance and activity. The worker generates and sends them automatically on the cadence you choose, so merchants always know where they stand.

Payment types

Every row on a deal ledger has a type that decides where it lands in accounting and reports:

| Type | Meaning | | --- | --- | | Original advance payback | The scheduled collection pulling back the advance — the standard daily/weekly/monthly debit. | | Advance payback | An extra payback outside the original schedule — a catch-up debit, manual payment or wire-in. | | Payback adjustment | A correction to collected payback (up or down) so the ledger reconciles. | | Participation payout | Money out to a syndicator — their distribution from collections. | | Payout adjustment | A correction to a syndicator payout. | | Wire fee | Charge to the merchant for wiring funds; posts to its own fee-income account. | | UCC fee | UCC filing charge to the merchant; posts to its own fee-income account. | | Application fee | Application/origination charge to the merchant; posts to its own fee-income account. | | Bounce fee | Charge to the merchant after a returned (bounced) payment. | | Other fee | Any other charge on the deal ledger that doesn't fit the types above. |

The same descriptions appear as hover tooltips on the type dropdowns on a deal's ledger. Payback types count toward collections and the running balance; fee types count as fee income; payout types are money out to participants.

Bounces & make-up payments

When a pull bounces and the merchant later catches up (a wire, a re-pull), the books keep both facts — the return and the recovery — without rewriting either:

• The bounce stays a bounce. It keeps its original due date (the scheduled date) and its return code. That's your NSF history; it never disappears.
• The catch-up payment keeps its real paid date. Cash is never back-dated: the wire cleared the day it cleared, and bank reconciliation, collected-in- period reports and syndicator splits all depend on that real date.
• The link is what resolves it. On the deal ledger, use Make up… on the bounced row to point it at the PAID payment that covered it (one catch-up wire can cover several bounces). The bounce then shows due date (its own) and paid date (the covering payment's).

The dashboard counts only outstanding bounces in red — made-up bounces move to a green "made up" tag but stay in the return history and the by-reason chart. Unlinking (✕) puts the bounce back in the outstanding count.

Can’t find what you need? Return to the app or contact your administrator.