Timeline for What is an appropriate abstraction which encompasses both 'receipt' and 'invoice'?

Current License: CC BY-SA 3.0

4 events

when toggle format	what		by	license	comment
Nov 8, 2011 at 15:12	comment	added	Alexis Petrounias		I agree that 'bill' is an acceptable abstraction, however, given the context within which 'receipt' and 'invoice' would typically exist (a commerce application with numerous other financial constructs), wouldn't 'bill' or 'billing' be more suitable to what is presented prior to payment and invoicing? If not, then we would have to use 'order summary' to denote the role of what would more naturally be called 'bill'; but then, an actual summary of an order, which culminates in its billing aspect, would need renaming.
Nov 8, 2011 at 14:58	comment	added	Joel Brown		"Bill" is often used to indicate a statement of what is expected to be paid i.e., it can preceed payment. This is the sense in which "invoice" is typically used. However, "bill" is also frequently used to indicate what has been paid, which is the sense most strongly implied by "receipt". Therefore "bill" could apply pretty well to both sub-types and benefits from being both broadly understood and succinct - both of which are good qualities for a class name.
Nov 8, 2011 at 14:51	comment	added	Alexis Petrounias		Thanks. Unfortunately you guessed correctly regarding my target audience, as requirements, specifications, and design documents must be primarily handled by business people, accountants, and lawyers, and 'bill' or 'billing' is mostly used for what is presented to a customer before payments or proofs of purchase are issued.
Nov 8, 2011 at 11:38	history	answered	Joel Brown	CC BY-SA 3.0