YITH Deposits writes deposit and payment-plan meta onto wc_orders: deposit amount, remaining balance, next payment due date and the chosen plan. The default Orders screen treats deposit orders the same as full-payment ones and hides the data that actually matters for cashflow. Finance teams reconstruct the receivables view from per-order screens or CSV exports.

SleekView reads the same deposit meta from wc_orders (or wp_postmeta under legacy storage) and renders deposit-flagged orders as a sortable table. Customer, order total, deposit amount, remaining balance, plan name and balance-due date all sit as real columns. Filter to remaining balance > 0 to scope the live receivables view. Filter to due date within 7 days to triage collections. Sort by remaining balance desc to prioritize high-value follow-ups.

The plugin keeps owning the checkout flow, the balance email and the customer portal. SleekView owns the receivables surface, so the deposit data YITH already records stops hiding in the standard orders list and becomes a finance-grade audit grid.

Letting buyers pay a deposit and the balance later unlocks high-ticket sales that WooCommerce stores would otherwise lose. The trade-off is receivables, and receivables need an aggregate row-level surface, not a per-order screen. YITH stores the data cleanly on wc_orders, the gap is the audit view.

SleekView reads the same meta and renders every deposit order as a row with deposit amount, remaining balance, plan and balance-due as real columns. Filters stack into a single query so the live receivables view, the due-this-week queue and the overdue follow-up list become saved views rather than spreadsheet rituals. The plugin keeps owning the checkout flow and the balance email, while finance and collections get the per-row surface the dataset always deserved.