✨ 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 Kanban for WP-Invoice

WP-Invoice stores invoices as a custom post type with the invoice status in post_status and metadata such as amount, recipient, and due date in post meta. SleekView reads the post table joined with postmeta, groups invoices by status, and renders one card per invoice.

♾️ Lifetime License available

SleekView Kanban board for WP-Invoice

Read your WP-Invoice ledger as a board, not a list

WP-Invoice stores every invoice as a row in the WordPress posts table under its own post type, with a status that moves through draft, active (sent), paid, refund, and archived. Amount, recipient, due date, and line items live in postmeta under WP-Invoice's own keys, and payments are recorded against the invoice ID once a gateway settles. The result is a flat list in the admin grouped only by paginated date.

SleekView reads the posts table filtered to the WP-Invoice post type and joins on postmeta to expose amount, due date, and recipient as fields on every row. The natural column to group by is the WP-Invoice post_status, which moves an invoice through Draft, Sent, Paid, Refund, and Archived. Cards show the invoice number from post meta, the recipient, the total, and the due date so accounts receivable reads the queue without opening anything.

Dragging a card from Sent to Paid writes the new post_status value through wp_update_post, which is the same call the WP-Invoice admin makes when an invoice is marked paid manually. WP-Invoice hooks listening on the status transition fire normally, so any thank-you email, accounting export, or follow-up automation behaves the same as it would on a manual mark. Refunded and archived invoices stay visible as their own columns instead of disappearing behind a filter, which matters when month-end reconciliation pulls every state into a single view.

Workflow

From the posts table to a WP-Invoice board in four steps

1

Point SleekView at the WP-Invoice post type

Add a SleekView data source for the posts table filtered to the WP-Invoice post type and joined to postmeta. SleekView picks up post_status, the invoice number, amount, recipient, and due date as fields you can put on the card front.
2

Pick post_status as the grouping column

Switch the view to Kanban and select post_status as the column the board groups by. SleekView renders one column for Draft, Sent, Paid, Refund, and Archived and counts how many invoices sit in each one across the selected date range.
3

Choose what shows on cards

Pick the fields that go on the card front: invoice number, recipient, total, and due date. Skip the rest so the board stays scannable when the practice has hundreds of invoices open and AR only needs the basics to chase payment.
4

Enable drag and drop

Turn on drag and drop and scope it per role. Dragging a card from Sent to Paid writes the new post_status through wp_update_post, which is the same call WP-Invoice makes when an invoice is marked paid by hand, so transition hooks fire normally.

Sample board

Sample WP-Invoice board

Four columns grouped by WP-Invoice status, with a typical mix of drafts in progress, invoices sent, payments cleared, and one refund inside the same month.
Draft
11
INV-2419, Northbridge Studio
$2,400.00, due Apr 30
INV-2420, Ironbloom Co
$1,150.00, due May 03
INV-2421, Solstice Trading
$3,820.00, due May 07
Sent
24
INV-2402, Northbridge Studio
$2,400.00, due Apr 22
INV-2405, Pacific Tile Group
$1,820.00, due Apr 24
INV-2410, Alpine Foods Ltd
$4,150.00, due Apr 28
Paid
148
INV-2380, Coastal Outfit Co
$1,300.00, paid Apr 18
INV-2385, Harvest Crate Co
$2,950.00, paid Apr 19
INV-2390, Riverbend Retail
$880.00, paid Apr 20
Refund
3
INV-2370, Verdant Florist Co
$640.00, refunded Apr 15
INV-2372, Quick Resell LLC
$320.00, refunded Apr 16
INV-2376, Bargain Hunt Co
$1,180.00, refunded Apr 17

Comparison

Default WP-Invoice list vs SleekView Kanban

Default WP-Invoice list

  • Invoices live in a paginated list with no grouped view by status
  • Marking paid means opening each invoice and saving the edit form
  • Refunded invoices hide behind a post_status dropdown filter
  • No way to read draft, sent, and paid invoices side by side
  • Overdue chase needs a custom report against the due date meta key

SleekView Kanban

  • Reads the WP-Invoice post type joined with postmeta
  • Groups by post_status so every invoice lands in a column
  • Drag from Sent to Paid writes via wp_update_post
  • Card fronts show invoice number, recipient, total, and due date
  • Refunded and archived invoices stay visible as their own columns

Features

What SleekView Kanban gives you for WP-Invoice

Group by invoice status

Group by post_status so Draft, Sent, Paid, Refund, and Archived each get a column with a live count. Switch the grouping to recipient on a saved view to read one client's full ledger as columns of invoices instead of a filtered list.

Drag and drop runs WP-Invoice hooks

Cards move with the pointer or arrow keys and SleekView writes the new post_status via wp_update_post. WP-Invoice hooks on the status transition fire normally so thank-you emails, accounting exports, and any follow-up automation behave the same as a manual mark paid.

Sort by due date for overdue chase

Sorting the Sent column by due date surfaces overdue invoices at the top. AR pulls the oldest first, sends a reminder, and drags whatever clears to Paid through the day without writing a custom overdue report.

Audience

Where a WP-Invoice kanban earns its keep

Weekly AR sweep

Sent is the active receivable column. AR works the oldest cards first, drags the ones that paid into Paid, and watches the column count fall during the week as the books close on each invoice.

Per-client ledger

A saved view grouped by recipient reads a single client's full history as columns of invoices. Sales and AR check the column counts on a renewal call to spot late payers before pitching a new engagement.

Month-end reconciliation

Filtering by month puts every invoice issued in the period on one board. Paid, Refund, and Archived stay visible so finance reconciles against the bank feed without flipping filters back and forth.

The bigger picture

Why a board beats the default WP-Invoice list

WP-Invoice does a clean job of issuing and tracking invoices, but it leans on the WordPress posts list pattern, which means a paginated table sorted by date with a status filter. AR teams think in columns, not filters: drafts they are still writing, invoices sent that they are chasing, payments cleared, and refunds that need reconciling against the bank. A kanban grouped by post_status gives that view directly.

Draft, Sent, Paid, Refund, and Archived become columns the team works through the week, counts on each column expose the receivable position at a glance, and each card carries the invoice number, the recipient, the total, and the due date so a chase email is one click away. Dragging a card writes via wp_update_post, the same call WP-Invoice makes on a manual mark, so plugin hooks fire normally. Refunded and archived invoices stay visible as their own columns, which is what month-end reconciliation against the bank feed needs.

Questions

Common questions about SleekView Kanban for WP-Invoice

No. SleekView Kanban is an extra reading layer on the same posts and postmeta tables. The WP-Invoice edit screen, settings, and per-invoice payment history keep working. The board only changes how AR reads the queue and updates status, and every write goes through wp_update_post.

 

The columns are the values WP-Invoice writes to post_status on each invoice: Draft, Sent, Paid, Refund, and Archived, plus any custom status the plugin adds. SleekView only renders columns that actually have rows in the date range so a quiet month does not show empty buckets.

 

Yes. SleekView writes via wp_update_post, which is the same call WP-Invoice makes when an invoice is marked paid by hand. The plugin's transition hooks fire normally, so thank-you emails, accounting exports, and any follow-up automation behave the same way.

 

Yes. Any meta key on the invoice can be the grouping column, including the recipient ID or company. A saved view that groups by recipient reads one client's full ledger as columns of invoices, useful for renewals and per-client reporting.

 

Yes. The due date meta key is exposed as a field and can sit on the card front. Sorting the Sent column by due date surfaces the oldest invoices at the top, which is exactly the order AR wants to work the chase queue.

 

Yes. SleekView checks the WordPress capability before writing a status change. Drag and drop can be limited to roles with edit_invoice capability or a custom AR role while support and admin staff see the board read-only and cannot mark cards paid.

 

Not on the front of the card to keep the board scannable. The card back can render the line items pulled from postmeta when the team needs to confirm what they are chasing, and the card title carries the invoice number so the full record is always one click away.

 

Yes. A date range filter on the invoice issue date scopes the board to the period you choose. Counts on each column update accordingly, which makes month-end reconciliation a focused board view instead of a series of saved searches.

 

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