WooCommerce Invoice System plugins typically save the invoice number, invoice date, due date, and a paid/unpaid flag as postmeta keys on the parent shop_order. Common keys include _invoice_number, _invoice_date, _invoice_due_date, and a paid flag like _invoice_paid. PDF attachments are usually generated on demand, not stored as posts.

The default Orders screen doesn't show any of that. AR teams need to open every order to confirm the invoice has been issued, when it's due, and whether it's overdue. Sorting by due date or filtering to unpaid invoices needs custom SQL or a paid extension.

SleekView reads postmeta directly and exposes invoice number, due date, days-overdue, and paid status as first-class columns. AR ops sees the unpaid backlog ranked by days overdue, dunning emails go out from a saved view, and accounting gets a clean monthly close.

Accounts receivable lives on the unpaid backlog and the days-overdue distribution, not on individual invoices. A store with a hundred unpaid invoices, half of them less than a week overdue and half over forty days, has a healthier ledger than one with twenty invoices all sixty days late, but the default Orders screen makes that distribution invisible. The data is in postmeta (or wc_orders_meta): invoice number, due date, paid flag, customer.

What's missing is a single screen where AR can sort by days-overdue, filter to unpaid only, and process dunning inline. SleekView's pivot creates that screen. AR teams run dunning from saved views instead of CSV exports, accounting closes the month against a grouped-by-invoice-date view, and support answers "has my invoice been paid yet" without opening the order.

The plugin already does the invoice capture, SleekView just makes it operational.