Sprout Invoices stores every invoice as a sa_invoice custom post type and every estimate as a sa_est post type. Each record lives in wp_posts with a post_status like sa-draft, sa-pending, sa-partial, sa-paid, sa-overdue, or sa-writeoff, plus metadata in wp_postmeta for the client, the line items, the total, and the due date. The native admin lists every invoice as a sortable table, which makes it hard to see how many invoices are overdue this week versus how many are still awaiting client approval.

SleekView Kanban reads the same invoice and estimate rows you would query with SI_Invoice or WP_Query. Pick post_status as the group column and every record becomes a card slotted under Draft, Pending, Paid, or Overdue. Card fronts show the client name from the linked sa_client post, the invoice number, the total in store currency, the due date, and the days overdue if any, so an account manager triaging late invoices sees everything on the board.

Dragging a card from Pending to Paid runs the same status helper Sprout Invoices uses internally, which fires si_payment_recorded and the matching invoice status hooks. Payment notifications send through the email module, the client portal updates immediately for self-service viewing, and any extension listening on the Sprout Invoices status filters reacts, exactly as it would after a manual update from the invoice edit screen.

Agencies and freelancers running Sprout Invoices typically have dozens of open invoices at any given moment. Some are estimates waiting on client approval, some are invoices sitting in NET 30, and a steady trickle slip into overdue territory and need follow-up. The default invoice screen treats them all the same, which means account managers keep parallel spreadsheets of who owes what and finance never knows which clients are at real risk of going to collections.

The disconnect between what the billing system holds and what the team can act on shows up in the worst places. An overdue invoice goes uncollected for a month because nobody noticed the due date passed. A client pays a wire transfer and the invoice stays Pending for a week because the team forgot to record the payment.

A kanban view that reads and writes the same sa_invoice records the client portal reads keeps the team and the books honest. Every drag is a real status change, every column count reflects the real billing health, and the cards themselves carry enough context for a new account manager to handle collections on day one of the job.