✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount

SleekView for WP-Invoice: invoices & payments as tables

WP-Invoice stores invoices as the wpi_object custom post type with line items packed into postmeta. SleekView reads them as proper rows so finance can sort by amount, filter by status, and inline-edit due dates.

♾️ Lifetime License available

SleekView table view for WP-Invoice

Invoices as a real ledger, not a CPT list

WP-Invoice (Usability Dynamics) registers invoices as the wpi_object custom post type. Recipient details, line items, currency, and the entire payment history are scattered across postmeta keys, which is why the default WordPress list table is so unhelpful — it can show titles and dates, but not totals or amounts owed. Finance teams end up clicking into every invoice individually just to see what's outstanding.

SleekView reads the CPT, unpacks the relevant meta keys, and pivots them into named columns: total, balance, due-date, status, recipient, currency. "Overdue" becomes a computed column derived from the due-date meta and today's date, so a single saved filter surfaces every invoice past 14 days due, sorted by amount. The default admin can't express that query without custom SQL.

Inline edits go through the standard WordPress post and meta APIs, so any payment-gateway integration that hooks into save_post or updated_post_meta fires the same way it would from the post editor. Marking an invoice paid in the row triggers the same webhook, the same email, the same audit log entry.

Workflow

From wpi_object posts to a real invoicing ledger

1

Read the wpi_object CPT

Point SleekView at the WP-Invoice post type. The agent UI auto-discovers the postmeta keys WP-Invoice uses for total, recipient, due-date, currency, and payment status.
2

Pivot meta into columns

Promote total, balance, status, due, and recipient from buried postmeta into proper sortable columns. Currency becomes a filter dimension for multi-region installs.
3

Add the overdue computation

Build a derived "days overdue" column from the due-date meta minus today. Saved filter "Overdue more than 14 days" becomes the daily collections queue.
4

Inline-edit and reconcile

Mark invoices paid, push due dates, update notes from the row. Writes flow through update_post_meta so payment-hook integrations fire normally.

Sample columns

A typical WP-Invoice invoices view

SleekView reads the invoice CPT and pivots payment-status, total, and recipient meta into named columns.
Source: wp_posts (wpi_object) + wp_postmeta
Invoice # Recipient Total Status Due Issued
INV-1042 alex@studio.co $1,250.00 Sent May 08 Apr 24
INV-1041 ria@design.io $480.00 Paid Apr 30 Apr 16
INV-1040 tom@hello.dev $2,100.00 Overdue Apr 18 Apr 04
INV-1039 mia@brew.coop $96.00 Paid Apr 22 Apr 08

Comparison

Default WP-Invoice admin vs SleekView

Default WP-Invoice admin

  • Invoices are stored as wpi_object posts with totals in postmeta — no totals column in default list
  • Filtering is by post status only — no "overdue", "unpaid", or "recently paid"
  • Payment history is hidden behind the invoice editor
  • Bulk status changes require opening each invoice
  • Custom recipient fields aren't surfaced in the list

SleekView

  • Read wpi_object with total, balance, and status pivoted from postmeta
  • Compute overdue from due-date meta as a real status
  • Inline-edit due date and payment status across many invoices
  • Save filters like "Overdue more than 14 days" for collections workflows
  • Show invoices, payments, and recipients in a tabbed surface

Features

What SleekView gives you for WP-Invoice

Totals and balance as real columns

WP-Invoice stores totals in postmeta. SleekView pivots them into proper columns so finance can sort by amount, balance, or days-overdue without opening invoices.

Compute overdue inline

Compare due-date meta against today to surface overdue invoices as a sortable column. Save the filter as a collections queue the team revisits every morning.

Inline status updates

Mark invoices paid, sent, or refunded directly in the row. Bulk-update payment status across dozens of invoices in one pass — gateway hooks fire normally.

Audience

Who uses SleekView for WP-Invoice

Finance ops

Daily reconciliation: sort by status and date, filter to overdue, mark payments inline. No opening individual invoices to copy totals into a spreadsheet.

Solo consultants

One "Outstanding" view with totals and days-overdue visible at a glance, plus inline edits for chasing payment without leaving the dashboard.

Support teams

Search by recipient email, see full invoice history with status, and update notes inline while on a customer call. Faster than the default admin path.

The bigger picture

Why finance ops needs a real ledger view

Invoicing plugins built on the CPT-plus-postmeta pattern are extremely common in the WordPress ecosystem, and they share a single weakness: the default admin can't surface the numbers that finance actually cares about. WP-Invoice is a clean example. The data is there, complete and normalized in postmeta, but the WordPress list table renders title and date because that's all it can render generically.

Finance teams either build a custom admin column plugin, write SQL into a reporting tool, or — most commonly — open every invoice in a new tab and copy totals into a spreadsheet. None of those scale past a hundred invoices a month. The cost is real: invoices age past their due date silently, partial payments stay invisible, and the team spends hours on Friday reconciling what should have been a glance.

A flat, filterable, inline-editable ledger isn't a fancy feature — it's the basic interface a finance role expects, and the one the CPT-plus-meta pattern systematically fails to provide.

Questions

Common questions about SleekView for WP-Invoice

Yes, on installs that still run a working copy of the plugin. WP-Invoice was closed for security reasons in 2022; if your site has the plugin active, SleekView can read its wpi_object data without modification. We recommend evaluating an actively maintained alternative for new installs, but for legacy ledgers the data is fully accessible through standard WordPress APIs.

 

Invoices are the wpi_object custom post type. Line items, totals, recipient details, currency, and the full payment history all live in postmeta on each invoice post. SleekView reads both the post and the meta, pivots the relevant keys into named columns, and exposes them for sort and filter.

 

Yes. Each invoice is one row in the main view, with line items available as an expandable detail panel under the row. For finance teams that prefer a separate line-item view, SleekView can render line items as their own table in a tabbed setup with invoice number as a join key.

 

SleekView writes through the WordPress post and meta APIs. Payment-gateway integrations that hook into save_post, updated_post_meta, or WP-Invoice's own action hooks fire as expected. Marking an invoice paid from a SleekView row triggers the same gateway webhook the post-editor save would.

 

Yes. Filtered views export to CSV with the visible columns. Useful for accountant handoffs, quarterly tax prep, or for reconciling against external bookkeeping tools that expect a flat row-per-invoice format.

 

Yes. WP-Invoice stores currency in postmeta on each invoice. SleekView surfaces it as a column and lets you filter by currency for region-specific reporting. Totals stay in their original currency — SleekView doesn't auto-convert, which is the correct default for audit-grade ledgers.

 

Yes. Payment history is stored in postmeta as a serialized array. SleekView can pivot it into a "payments received" column or render the full history in an expandable detail panel. Balance is computed as total minus the sum of received payments.

 

Yes. WP-Invoice's meta key naming has changed across versions. The SleekView agent UI scans an existing invoice, lists the candidate keys with their values, and lets you map the right ones to columns. Useful when the docs are out of date or when a custom child plugin has added extra fields.

 

Pricing

More than 1000+
happy customers

Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.

Starter

€79

EUR

per year

  • 3 websites
  • 1 year of updates
  • 1 year of support

Pro

€149

EUR

per year

  • Unlimited websites
  • 1 year of updates
  • 1 year of support

Lifetime ♾️

Most popular

€249

EUR

once

  • Unlimited websites
  • Lifetime updates
  • Lifetime support

...or get the Bundle Deal
and save €250 🎁

The Bundle (unlimited sites)

Pay once, own it forever

Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.

What’s included

  • SleekAI

  • SleekByte

  • SleekMotion

  • SleekPixel

  • SleekRank

  • SleekView