Recurring invoices

The recurring billing run generated the invoice, made the PDF and sent it. It never posted it to the general ledger. No receivable, no revenue. The money only reached the P&L if someone approved each invoice by hand.

They post now, as part of the run — before the PDF is made and before any card is charged. Posting first also means a customer’s credit is applied before the PDF is made, so the bill shows what they actually owe.

If an invoice can’t post — an account isn’t mapped, say — it still goes out, because the customer still owes it. But nothing is charged against it, the reason shows on the billing dashboard, and it’s listed on the Unposted Items report.

If you run recurring billing, check Unposted Items for recurring invoices dated before 2 September 2026. Those never posted.

Auto-charge

Charging a saved card on a recurring invoice credited accounts receivable for an invoice that had never debited it. Every auto-charged invoice pushed AR negative by its own amount.

Fixed by the change above. And auto-charge is now skipped entirely if the invoice didn’t post, so nothing is ever charged against a ledger that doesn’t carry it.

Customers with credit

A customer who paid ahead isn’t charged for a bill their credit already covers. The credit is applied when the invoice posts, the balance is recomputed, and at zero there’s no card charge.

More on where that credit comes from: The money that used to disappear.

Card surcharges

When a company had no Surcharge Revenue account mapped, the surcharge on a card payment was dropped from both sides of the entry. It balanced, and the bank was understated by the fee. Same shape as the prepayment bug.

Now that payment saves, doesn’t post, and shows up on Unposted Items until the account is mapped.