Invoices Losing Rows

Problem

Using stock printed form layouts, a few types of transactions can lose one or two rows, when the invoice extends onto multiple pages. This can occur in Billing Statements, and a few types of itemized invoices printed from Billing Records.

The problem is caused by incorrect printer margins in the Printed Form layouts. A few forms were incorrectly set up with zero width printer margins, which causes multiple-page lists of invoice items to be placed on the very edge of the paper, beyond where the printer can actually print.

Caught By

User bug report.

Workaround

If you have customized the printed form layouts, or if you'd like to fix this manually in Goldenseal accounting software version 4.2 or earlier, follow these steps:

  1. Choose Custom Layouts from the Options menu, and choose Printed Forms from the submenu.
  2. Enter Billing Statement into the Transaction popup field at upper left.
  3. Choose Size & Margins from the Options menu.
  4. Enter 1/4" into the Margins popup field (that width is sufficient for most printers).
  5. Click OK.
  6. The layout will become slightly smaller, so you may need to move some items to fit the new space.
  7. Choose Save from the File menu.
  8. Repeat steps 2 to 7 for Billing Records. You'll need to change all four types of invoice layouts.

Solution

Starting with Goldenseal accounting software version 4.3, we have adjusted all stock printed forms to use wider margins, if they include a breakdown table that might extend to a second page.

If you haven't changed the Billing Statement or Billing Record layouts, the new setup will be used automatically.

If you have customized the layouts, you can do either of two things:

  1. Follow the steps above to adjust the printer margins.
  2. Open the layout, and choose Revert to Original from the File menu. It will return the layout to the stock format, which has wider margins. You can then redo any customizing.

Technical Details

Changed margins in the stock printed forms (stored in resources). There were no code changes needed.