I'd add one point. The rate of tax is data. A fundamental principle of the database relational model is the Information Principle (Codd's Rule #1). This requires that all data be stored as values at column positions in rows in tables, and in no other way. So, if the rate is variable per product, as with Value Added Tax (VAT) for example, it would be stored in a column in the Products table, and assigned to a column in an InvoiceDetails table or similar when an invoice is raised. When computing the gross price, therefore, the expression would be:
GrossPrice: [NetPrice]*(1+[GST])
The GST value should be stored as a fractional value, 0.15 in this case, but can be formatted as Percent.
I don't know how it works with GST, but for VAT, the tax would only be added in the above way for retail transactions. Otherwise it would be added to the total net price for each group of line items which attract the same tax rate. For how to compute the tax in this context you'll find an example in InvoicePDF.zip in my public databases folder at:
https://onedrive.live.com/?cid=44CC60D7FEA42912&id=44CC60D7FEA42912!169
This little demo file is primarily intended to illustrate how to generate a report (the invoice) as a PDF file, but happens to use a simple hypothetical invoicing database.