You might be wondering why the need to call it "CustomerInvoice" instead of just "Invoice" for that model. In this case it's mostly just for illustration. But there are a lot of cases where we need to get more specific about what a table is used for.

The same holds true if you're dealing with field names outside the context of a relation. To get the invoice number in CustomerInvoice, as it stands, we'd need to do `prisma.customerInvoice.invoiceNumber`. That's a bit redundant.

When we set up a relation between Customer and CustomerInvoice, the field name that gets auto-populated is "CustomerInvoice". A good start is to just rename this to "customerInvoices" to keep consistency.

youtu.be/e2PPiXf18Cc How to go faster and to automate the selection of the right customer invoice and supplier bill in Reconciliation? Let's check the video to know more. #reconciliation #customerinvoice #supplierbill #automate

From the archives: Print your Invoices Easily with the Smart App and Smart Dashboard bit.ly/2z8KnBk #CustomerInvoice #SmartAccount