Do I need another table for Receipts?

Ok my question is one that may get an a response like this.. "Just make the table lazy sod!"

I am reworking a a database for Invoicing. I have created several tables for Contacts and the Invoices, and Payments. I have also created auxiliary tables, linking the main tables with primary/foreign keys where many-to-many relationships exist. I understand that this is good practice in following the rules of normalisation and I am really happy with how well this makes thing work.

I am doing this using Filemaker by the way.

One of the last things to do is to issue a receipt to the Customer/Contact when they make a payment. Looking at the data available in the Payments table. Data regarding the Customer and Invoice is also available. One or Several payments can be made, each with it's own record to represent paying either the invoice in full or in instalments. I have this set up so that one can view a list of payments through a portal in a variant view of the invoice.

I am thinking that I can get away with just making a layout from the Payments table that will do as a receipt. There is just something niggling though at the back of my mind that says this is the wrong approach.

Can anyone give me a good reason why I need to build a table for the Receipts.