Combine Invoices: installation and first checks

Use the README inside your purchased Combine Invoices ZIP for exact commands. This checklist helps verify the result; it does not replace the version-specific integration instructions.

Before applying changes

Record the Paymenter, PHP and theme versions. Back up database and application files. Review the package's installer and core-hook requirements, especially if invoice screens or payment handling were customized previously.

Run the documented preview before applying. If the installer refuses an unsupported anchor, preserve the output and review the difference with the installation maintainer.

Confirm the customer workflow

With controlled test invoices, open Pay invoices together. Check that eligible unpaid renewals can be selected and that the review shows their correct total and currency.

Also verify a refusal: a credit deposit, prior payment attempt or different-currency invoice should not become selectable merely because its amount looks compatible.

Confirm the staff workflow

Check the native invoice bulk action using a staff account with the required invoice permissions. Confirm that a staff member lacking those permissions cannot perform the operation.

Review the replacement invoice's references to its originals. Creating a combination should not itself create a successful payment transaction.

Understand undo and payment

Undo is available only before checkout or a payment attempt starts. Once an attempt exists, pay the replacement invoice or ask support to inspect the arrangement. Do not pay both an old invoice link and its replacement.

Use payment-provider test facilities on a separate staging installation for payment testing. Never treat a fabricated Paid status as evidence of gateway success.

Related: Customer combination steps and eligibility questions.