Accounting code fails on arithmetic, not layout: a total that disagrees with its line items by a cent, a tax rate applied before a discount. Each invoice here computes its own subtotal, tax and total from the actual line items, so the numbers reconcile.
What you can control
- Subtotal, tax and total are computed from the generated line items rather than filled independently.
- The tax rate is adjustable in half-point steps, covering the fractional rates that break rounding.
- A realistic status mix leans toward paid, with a minority overdue — which is what an aged-receivables report needs.
- Line item details can be expanded into a column when you need the individual rows.
Testing ideas
- Totals. Check your own invoice maths against the generated subtotal, tax and total. Tax is applied once to the subtotal, which is where per-line rounding bugs show up.
- Status mix. Use the realistic mix to test dashboards that group paid, open and overdue invoices.
- Many line items. Set twelve items per invoice and render a PDF: page breaks and table headers are where invoice templates fail.
- Zero tax. Set the tax rate to 0 and confirm the template neither divides by zero nor prints "Tax (0%)" if your design should hide it.
What this is not
Tax is applied as a flat percentage of the subtotal. Real tax handling varies by line item, jurisdiction and customer status, so do not use these figures to validate a tax engine.