Kascado Accounts Receivable for WooCommerce
Database requirement: this plugin stores money in its own tables and relies on transactions to keep a payment and the invoices it settles consistent with each other. Those tables must use InnoDB, which is the default on every MySQL since 5.5 and every MariaDB. On a server configured to default to My
About this tool.
Database requirement: this plugin stores money in its own tables and relies on transactions to keep a payment and the invoices it settles consistent with each other. Those tables must use InnoDB, which is the default on every MySQL since 5.5 and every MariaDB. On a server configured to default to MyISAM the tables are created without transaction support and a failure part-way through recording a payment could leave the entry saved and its allocation missing.
If your store ships before it gets paid, WooCommerce alone cannot tell you what you are owed. An order marked Processing means the goods went out, not that the money came in, and the gap between the two is where a spreadsheet usually appears.
This plugin closes that gap. It watches orders placed through the payment methods you nominate — bank transfer, cheque, cash on delivery, purchase order, anything that defers payment — and records each one as a charge against that customer. When money arrives, you record it, and the balance moves.
What it does
- An accounts receivable dashboard: total outstanding, how many customers carry a balance, and how much is overdue including the age of the oldest overdue amount
- A receivables trend chart covering the last six months
- A customer list showing each account’s balance, company, email and oldest unpaid date, sortable by balance, name or oldest unpaid date
- Charges created automatically from orders placed with the payment methods you choose
- Payments recorded against a customer with the amount, the date the money actually arrived, the method, a reference such as a cheque number, and a note
- Payments applied automatically to the oldest open charges first, which is how B2B receivables are normally settled
- Credits and write-offs, each requiring a note, and corrections for an entry recorded in error
- Payment terms for the store — Due on Receipt through NET 120 — giving every new charge a due date
- A screen for each customer: their balance, the invoices still open against them, and their full history with a running balance
- Historical import, so orders already in your store can be brought in as charges without duplicating anything — an order that was already refunded arrives as its gross invoice plus each refund as its own dated credit
