I'm helping create a database for basic invoicing, which I've never done before. They need to track multiple items per invoice - e.g. six different tasks were done for a customer, each with its own price and description.

I'm assuming the best way to handle this is to create a secondary textbase, linking to the customer information on the invoice ID. One would carry all the basic information, the other would have the line items? If so, should each item on the invoice be a separate record within the line item DB?

Any advice on best practices here is appreciated.

Dan