Navigation
14.21. Page Setup, Preview, and Troubleshooting for Alga PSA Invoice Layouts
Set AlgaPSA invoice layout paper size, margins, and PDF safe zones, preview with sample or existing invoices, and troubleshoot common rendering issues before assigning a layout to clients.
Invoice layouts are ultimately client-facing documents. Even when clients view invoices digitally, the layout still needs to render cleanly as a PDF and print properly when needed. This page covers the page-setup controls, the preview workflow, and the troubleshooting moves you'll use to keep layouts safe to ship.
When no component is selected in the invoice designer, the inspector shows page setup controls.
Figure 1: Page setup controls define the paper preset and margins used by the invoice layout.
Paper presets
Choose the paper size that matches your normal client delivery.
| Preset | Use it when |
|---|---|
| Letter | Most common for US-based MSPs and clients. |
| A4 | Common for international clients and regions that use A4 business documents. |
| Legal | Use only when your invoice format requires extra vertical space and clients expect legal-size documents. |
For most MSPs, Letter or A4 is the right choice.
Margins
Margins keep content away from the edge of the page. Good margins prevent clipping in PDFs and printed copies.
Guidelines:
- keep enough space around the page for printing;
- avoid placing totals or payment instructions too close to the bottom edge;
- use preview to check whether long tables push content outside the expected area;
- use consistent margins across layouts unless a client-specific document requires otherwise.
Preview sources
Preview and validation are the safety net for invoice layouts. They catch missing fields, layout overlap, transform mistakes, and PDF rendering issues before clients see the invoice.
Figure 2: The Preview tab renders the layout and shows whether the layout shape and render steps succeeded.
| Source | Use it for |
|---|---|
| Sample data | Fast checks while building the layout. Good for early design work and quick iteration on structure and styling. |
| Existing invoice | Final review using real invoice complexity, client data, taxes, and line items pulled from billing. |
Start with sample data, then test with an existing invoice before assigning the layout to production billing. Switching sources from inside the Preview tab lets you compare how the same layout behaves against simple scaffolding versus a fully populated invoice.
Validation checklist
| Area | What to check |
|---|---|
| Header | Logo, MSP name, invoice number, issue date, due date, and client name. |
| Billing details | Customer address, PO number, service period, and any required client reference. |
| Line items | Descriptions, quantities, rates, amounts, service periods, and wrapping. |
| Totals | Subtotal, tax, discounts, credits, and final total. |
| Styling | Colors, spacing, alignment, borders, and readability. |
| PDF fit | Page size, margins, table length, footer placement, and no overlap. |
| Data rules | Filters, sorts, groups, and totals match billing expectations. |
PDF-safe checklist
Before assigning or making a layout default:
- preview with a simple invoice and a detailed invoice;
- test invoices with long descriptions;
- test invoices with several line items;
- verify totals and footer placement;
- download or generate a PDF if available in your workflow;
- have billing staff review the PDF as the client would see it.
Common troubleshooting issues
| Symptom | What to check |
|---|---|
| A field is blank | Confirm the invoice actually has that value and the correct field is bound to the component. |
| Line items do not appear | Check the line-item table binding and preview with an invoice that has billable lines. |
| Totals look wrong | Confirm the totals component is bound to invoice totals and that custom transforms are not excluding rows. |
| Text overlaps | Increase component width or height, adjust container spacing, or reduce font size. |
| Table columns are cramped | Widen the table, reduce optional columns, or shorten column labels. |
| Logo is distorted | Adjust image size and preserve the expected aspect ratio. |
| Preview works with sample data but not an existing invoice | Compare the sample structure to the existing invoice; check optional fields, long descriptions, taxes, and line-item counts. |
| PDF cuts off content | Review paper preset, margins, component placement, and long dynamic tables. |
Safe rollout process
- Build or edit the layout as a draft.
- Preview with sample data.
- Preview with at least one simple existing invoice.
- Preview with one detailed invoice that includes multiple line items, tax, and service period data.
- Ask billing staff to review the PDF as the client would see it.
- Assign the layout to a narrow scope first when possible (for example, one client or one contract type).
- Monitor the first invoices generated with the new layout before expanding the assignment.
When to pause and revise
Do not use a layout for client billing if:
- invoice number, client name, due date, or total is missing;
- line items are hidden or unreadable;
- totals do not match the invoice;
- client-specific wording appears in a general default;
- PDF output cuts off content;
- billing staff cannot explain why a transform or grouping rule exists.
A layout should make billing clearer. If it creates confusion during preview, simplify it before assigning it.