Users should need to fill in a lost receipt statement when they mark a transaction as 'no/lost receipt'
Currently, users can just mark a transaction as 'no/lost receipt' without needing to upload a lost receipt statement, and many don't know that the lost receipt statement pdf exists. This should be changed so that users must fill out a lost receipt statement form and have a PDF generated of the lost receipt statement.
Great ticket! I've got a couple of questions:
- What would the lost receipt statement form look like?
- Should that generated PDF be attached as the receipt? Or should it not be treated as a receipt
- Who needs access to the lost receipt statement? (finance team? ops?)
Great ticket! I've got a couple of questions:
- What would the lost receipt statement form look like?
- Should that generated PDF be attached as the receipt? Or should it not be treated as a receipt
- Who needs access to the lost receipt statement? (finance team? ops?)
@garyhtou
- See the Lost receipt statement letter in common documents on HCB
- yeah, attached as the receipt, but if it's deleted, the transaction should once again revert to missing receipt
- this is a record keeping thing and is useful for finance team
@Luke-Oldenburg would you be interested in working with @rluodev on this ticket sometime during the week of June 9th?
LostReceipt::Statement:
-
date: Date -
merchant: String -
purpose: String - belongs_to:
submitter: User - has_many:
lost_receipt_items: LostReceipt::Item
LostReceipt::Item:
-
description: String -
quantity: Integer -
unit_amount_cents: Integer -
def total_amount_cents: Integer
I made a few edits:
- Namespace
StatementandItemunderLostReceipt - change
vendortomerchant - rename
amount_cents_per_itemtounit_amount_cents
What if we used concerns and made LostReceipt a type of Receipt?