Proposal: don't require matching every record to a merchant for bulk uploading

[officialdavidtaylor]

Implementation details:

• introduce merchantDescription field to the transaction table (nullable? see note in question marks section)
• allow merchantId to be null in the transaction table

Some benefits include:

• merchantId can be used to aggregate franchise location POS entry differences

Some question marks:

• not sure what this means exactly for individual transaction uploading... maybe in that case the UI can enforce a merchantId to be assigned to the record.

[officialdavidtaylor]

This train of thought just lead me to a simplified method of de-duplicating transactions (for cases where someone adds individual records throughout the month, then adds the statement sheet at the end of the month).

I can add a field to the transaction table to track the upload method (single vs bulk) and for the bulk mutation I'll query for all of the singles for that particular account within the time span in question, then do an in-memory splice to allow an upsert operation.