Feature lists make invoicing products look more similar than they are. “Recurring billing” might mean a scheduled draft, an automatically emailed invoice, or a card charged without a new invoice. “Inventory integration” might mean a shared product catalog—or automatic stock deduction.
Use this checklist to test behavior, not labels. Bring one representative client, quote, invoice, partial payment, expense, and export requirement to every trial.
1. Document fields and numbering
Check sender and customer identities, document numbers, issue and due dates, purchase-order references, service periods, currency, units, taxes, custom fields, public and private notes, and credit or cancellation behavior. Ask whether duplicates are allowed, how the next value is suggested, whether rules differ across organizations, and what happens when a document is deleted.
Test: Recreate a difficult real invoice, not the clean example from the demo.
2. Templates and customer-facing output
Inspect the final PDF and public view on desktop and mobile. Confirm logo quality, line-item labels, long descriptions, page breaks, tax display, footers, and accessibility. Use the invoice template anatomy to make the test repeatable. Determine whether “custom templates” means structured theme choices or a free-form editor.
Test: Use a two-page invoice with a long address and several tax rates.
3. Delivery and proof of access
Separate download, public-link sharing, application email, and client-portal delivery. They have different security and collaboration properties. Check attachment size and count, sending limits, reply-to behavior, and whether a public link can be revoked.
Test: Send to an address you control, inspect the reply path, and revoke the link.
4. Online payments
Ask who processes the money, where checkout is hosted, which account receives funds, how methods are selected, what fees apply, and how successful payments update the invoice. The Invoice Master and Stripe payment article is an example of the detail a vendor should disclose. Test partial payment, refund, chargeback, duplicate payment, and webhook delay—not just a successful card.
Red flag: A page promises every payment method without tying availability to country, currency, account capability, and processor settings.
5. Reminders and collections
Look for due-date visibility, an overdue queue, configurable timing, customer versus owner notices, pause controls, audit history, and bulk actions. Automated reminders should stop or pause when an invoice is paid, cancelled, disputed, or otherwise ineligible.
Test: Ask exactly what event schedules the first reminder and which timezone is used.
6. Recurring work
Determine what is saved, what is generated, whether the result is a draft or sent document, whether payment links and attachments carry over, how the next date advances, and what happens when a plan limit is reached.
Test: Set a monthly schedule for the 31st, change a line item, and inspect the next generated record.
7. Contacts, projects, time, expenses, and products
Adjacent records can prevent duplicate entry, but only if the connections are real. Does selected time become invoice line items? Do bills affect a project’s financial view? Does putting a product on an invoice change stock? Does a task status trigger billing? Write each required handoff as a sentence and make the vendor demonstrate it.
8. Dashboard and reports
Define every number before trusting a chart. “Revenue” may mean issued invoices, paid invoices, or cash received. “Profit” may ignore payroll or other costs outside the tool. Check date basis, currency handling, tax inclusion, refunds, aging buckets, filtering, and export formats.
Test: Reconcile one chart to its underlying documents manually.
9. Portability and retention
Ask for a complete export and inspect it. PDF is useful for human-readable records; CSV is useful for tabular analysis; JSON can preserve relationships for application migration. Confirm whether attachment binaries are included, what an import restores, and which data may remain after account deletion for legal, billing, log, backup, or processor obligations.
10. Plans, permissions, and support
Map every required action to a plan—not just record counts. Email delivery, reports, payment links, attachments, teammates, and portal access are often gated separately. Check monthly limits, reset behavior, watermarking, rate limits, ownership roles, and what happens after a downgrade. For this product, the Basic-versus-Premium decision maps those gates to concrete use cases.
Applying the checklist to Invoice Master
Invoice Master supports invoices, quotes, five PDF layouts, public links, contacts and companies, projects, time billing, bills, boards, CRM records, inventory locations and movements, recurring invoice drafts, a dashboard, and organization JSON export/import. Premium adds document email, Stripe payment links, up to three attachments per invoice or quote, dunning, reports, invitations, unlimited usage entitlements, and watermark-free PDFs.
Important boundaries are equally concrete: recurring invoices are generated as drafts; invoice and quote numbers are user-chosen labels that may be duplicated, while automatic numbering only suggests a next value; invoice line items do not automatically deduct inventory; bills do not store receipt images; there is no direct QuickBooks or Xero sync; and the app does not calculate exchange rates or determine tax compliance.
That final paragraph is the standard to expect from any vendor: not simply what the product has, but exactly what each feature does and where it stops.