Microformats Wiki - User contributions [en]

receipt-examples

2007-08-30T22:44:46Z

Lastorset: /* Real-World Examples */ linked to top 500 list of retailers; focused Marv's link

= Receipt examples =

=== Contributors ===
*Rob Manson
*Leif Arne Storset

== Real-World Examples ==
InternetRetailer's [http://www.internetretailer.com/top500/list.asp list of top 500 retail web sites] may be useful in the receipt-collecting process.

=== Bill / Invoice ===

Bills or Invoices are "yet to be paid" items.

Question: Perhaps these examples (yet to be provided) should be moved to a separate page as Bill/Invoice is quite different from Receipt.

: With [[hResume]], I've [[hresume-brainstorming#Actively_Seeking_Employment|suggested]] that the subtle difference between actively seeking work and just presenting your resume be a case of including [[hlisting]] markup.
: With bills vs invoices, it may turn out that the content found within would be identical, and it might just be a case of putting in a class flag to indicate whether the presented document has been paid for or not.
: [[User:SignpostMarv|SignpostMarv]] 12:55, 21 Jul 2007 (PDT)

::I think a class flag is a great idea, but I don't believe we have any samples for invoices. However, if we look at order review vs. order summary rather than invoices vs. receipts, the payment flag does become relevant in many of the sampled online stores.
::How would such a flag be implemented?
::*<code><nowiki><div class="hreceipt unpaid"/"hreceipt paid">...</nowiki></code>
::*<code><nowiki><div class="hreceipt" title="paid">...</div></nowiki></code>
::[[User:Lastorset|Lastorset]] 14:55, 16 Aug 2007 (PDT)

=== Receipts ===

Receipts are post-purchase items.

==== Amazon ====
* [http://mobileonlinebusiness.com.au/uf/receipt/Amazon.com-Vieworder-anon.htm Example]
* contains:
**<del>email address</del> (could not find in examples)
**date of order
**order id
**shipments
***shipping estimate
***delivery estimate
***shipping address
***shipping speed
***shipping preference (item grouping)
***items
****quantity
****seller
****price
****item information
**payment
***card type
***last 5 digits
***expiration date
***billing address
***subtotal
***shipping and handling price
***total before tax
***tax
***grand total
**<del>discount price</del> (could not find in examples)
* Little semantic HTML of interest, except an anchor with id "payment-info"

Notes:
*Supports multiple shipments.
*Supports one seller per item.
*Displays shipping and delivery estimate.
*Offers item grouping preference.
*Gift options.

==== Skype ====

===== Skype Phone =====
*[[receipt-example-skype-phone|example source code]]
*[http://mobileonlinebusiness.com.au/uf/receipt/Skype-order-history.html Skype order history]

* Shipping Address
* date in dd/mm/yyyy format
* Order number in nnnn-nnnnnnn-nnn format
* Reference (was blank in example, presumed to appear on bank statement for this transaction)
* Items
** Quantity
** Description
** Price
** Total
** VAT (tax) %
* Payment
** subtotal ("total")
** shipping cost
** grand total ("total (gross)")
** total (VAT excluded)
** VAT (amount)
* Chosen payment method: "Your payment method is: Credit card"
* Legal blurb

Semantic HTML:
* Order resume class="order-listing"
* Each item class="row"
* All totals rows class="totals-row" except grand total class="grandtotal-row"

Notes:
*Displayed credit-card-statement reference (presumably).

==== Internet banking transaction receipts ====
===== Example 1 =====
<pre><nowiki>
receipt number
date
time
receipt type (e.g. TRANSFER BETWEEN MY ACCOUNTS)
transfer from
transfer to
amount
description
information/comment
</nowiki></pre>

==== Digital product purchase receipts ====
===== Example 1 : Software =====
<pre><nowiki>
receipt title/type
order/receipt number
seller's details
sold by (hCard candidate)
org
adr
tax number (VAT in this example)
tax id (Federal Tax ID)
buyer's details
buyer (hCard candidate)
name
org
street-address
locality
region
postal-code
country-name
tel
email
credit card number (PAN truncated - with type)
item list
product code
name
comments
price
delivery method
quantity
total in selected currency
total in sellers currency
total (sum of item list totals)
processing fee
grand total (final amount charged)
information (caveats and tax info)
permalink
</nowiki></pre>

===== Example 2 : SSL certificate =====
<pre><nowiki>
receipt title/type
seller (hCard candidate)
org
street-address
locality
region
postal-code
purchase information
order id
product name
domain name
validity period
number of licenses
card number (PAN truncated)
amount (with selected currency)
</nowiki></pre>

==== Physical product purchase receipts ====
===== Example 1 : Computer hardware =====
<pre><nowiki>
receipt title/type
seller's name (hCard candidate)
seller's URL (hCard candidate)
invoice id
org govt reference (ABN - Australian Business Number)
date
seller details (hCard candidate)
street-address
locality
region
postal-code
buyer (hCard candidate)
fn
billing address
street-address
locality
region
postal-code
delivery address
street-address
locality
region
postal-code
phone
item list
item
description
amount
quantity
product url
total
delivery cost
total excluding tax
tax (GST - Goods and Service Tax)
total including tax
</nowiki></pre>

==== Service purchase receipts ====
===== Example 1 : Online subscription =====
<pre><nowiki>
seller's details (hCard candidate)
org
street-address
locality
region
postal-code
country-name
buyer's details (hCard candidate)
fn
street-address
locality
region
postal-code
phone
date
receipt id
item list
product description
quantity
rate (per unit)
price
sub total
amount paid
balance due
information
transaction id
</nowiki></pre>

===== Example 2 : Co-location =====
<pre><nowiki>
receipt title/type
sellers details (hCard candidate)
org
url
phone
message
receipt number
date
amount
information
</nowiki></pre>

==== A1Books ====
[http://mobileonlinebusiness.com.au/uf/receipt/A1Books-Sales-Order-anon.htm Example]

*vendor
**name
**fax
*date
*order number
*shipping address
*billing address
*items
**description
**list price
**sale price
**quantity
**amount
*subtotal
*shipping
*total
**quantity
**amount
*account information
**phone
**e-mail
*payment
**method
**last four digits

No semantic HTML.

Notes:
*Supports one seller per item.
*Does not display tax.

==== Barnes&Noble ====
[http://mobileonlinebusiness.com.au/uf/receipt/BarnesAndNoble.com-receipt.anon.tidied.htm Example]

*date
*shipping address
*billing address
*payment
**method
**last 4 digits
**exp. date
**charge
*savings on shipping
*order no.
*delivery option
*items
**description: title, author, ISBN, price
**qty
**gift options: wrap, message
**total price
*shipment subtotal
*shipping cost
*tax
*shipment total (seems to account for orders requiring multiple shipments)
*order total

Semantic HTML:
*receiptOrderNumbers
*receiptOrderPlacedOn
*orderInformation
**shippingAddress
**billingAddress
**paymentInformation
*shippingSelections
*showProducts
**reviewTable
***qtyValuePosition
***reviewGiftOptions
*reviewTotalsDisplay
**reviewTotalsSummary
**reviewTotalsNote
**reviewTotalsBreakdown
*reviewTotalsSummary
**reviewGrandTotal
*reviewCreditCardCharged
*review

The semantic class names found are a good start, although the "review" part appears to be context-specific (reviewing an order). Additionally, the implied hierarchy in names such as "reviewTotalsSummary" and "receiptOrderPlacedOn" is probably unnecessary for our purposes.

Notes:
*Supports multiple shipments.
*Gift options.
*Explicitly stated credit-card charge.

==== Facebook ====
[http://mobileonlinebusiness.com.au/uf/receipt/Facebook-gift-receipt.html Example]

*purchase total
*items (informal description of two items, including quantity)
*recipient name
*order id
*billed-to name

No relevant semantic HTML.

Notes:
*Quite minimal and informal receipt. Good example of how a microformat would preserve human readability and informal style while enabling machine reading.

==== Google Checkout ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Google-Checkout-e-mail-receipt.tidied.html Example email receipt]
*[http://mobileonlinebusiness.com.au/uf/receipt/Google-Checkout-Order-Receipt_DVD-Empire.tidied.htm Example web receipt]

*vendor address
*shipping address
*date
*order id
*items
**shipping status ("Not yet shipped", etc.)
**qty.
**description
**price
*shipping cost
*tax
*total
*order history (placed, received, charged, shipped) (web receipt only)
**credit-card statement reference (only after the charge has been made)
*payment info (web receipt only)
**card type
**last 4 digits
**exp. date
**cardholder address
*permalink

Semantic HTML:
*taxRow
**taxIdentifier
**taxAmount
*totalAmount

Notes:
*Explicit seller address (one per order).
*Current shipping status of each item.
*E-mail receipt has permalink.
*Order history (date placed, received, charged, shipped).
*Displayed credit-card statement reference only after card was charged.

==== iTunes ====
*[http://mobileonlinebusiness.com.au/uf/receipt/iTunes-receipt-e-mail.html iTunes e-mail receipt]

*billing address
*order no.
*receipt date
*order total
*card
**type
**last 4 digits
*item
**item no.
**description (including link to write a review)
**unit price
*subtotal
*tax

No relevant semantic HTML.

Notes:
*No quantity information.

==== Longs/FujiFilm ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Longs-Fujifilm-photo-receipt.html Longs/Fujifilm e-mail receipt]

*order no.
*payment info
**method (COD, credit card, etc.)
*customer address
*pickup address
*items
**name
**qty.
**description
**price
**line item subtotal
*order items total
*tax
*order total

Semantic HTML:
*payment-heading

Notes:
*No order date; has pick-up date instead.
*Has pickup address rather than shipping address.

==== Mobivox/PayPal ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Mobivox-PayPal.htm Mobivox/PayPal receipt]
*[http://mobileonlinebusiness.com.au/uf/receipt/Mobivox-PayPal-printable.htm Mobivox/PayPal printable receipt]

*seller address
*receipt id
*date of order
*items
**description
**item option (not quite sure what this is for)
**unit price
**qty
**total
*subtotal
*tax
*total amount
*payment info
**method
**last 4 digits
**charge
**appears on bill/statement as "MOBIVOXCORP"
*buyer contact

Relevant semantic HTML:
*order-summary
**cart
***(unnamed tr)
****item-name
****item-total
****item-option (not quite sure what this is for)
**subtotal
**totals-value
**totals-currency
**purchase-summary
***summary-total
****price-total
****price-currency
*funding-mix
**payment-type
**amount
**ccStatement
*contact-information (contains hCard microformat)

This semantic HTML is the most complete and well-thought-out I've seen in this analysis. It even makes use of the fieldset element in forms, something I've never seen before.[[User:Lastorset|Lastorset]] 16:21, 25 Jul 2007 (PDT)

Microformats used:
*hCard (non-compliant due to missing formatted name): buyer contact info

Notes:
*Explicitly stated credit-card charge.
*Displayed credit-card-statement reference.
*Explicitly displayed seller address (one seller per order).

==== Symantec ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Symantec-reminder-e-mail.html Symantec e-mail reminder]

*buyer name
*date
*payment method
*last 4 digits
*appears on statement as "DR *Symantec"
*items
**qty
**product name
**platform
**delivery method
**price
*subtotal
*grand total
*permalink

No relevant semantic HTML

Notes:
*As an e-mail "order reminder" rather than a receipt, this was slightly more informal than the other samples. As such there was
**no order id
**a permalink
*"Delivery method" could be download or ship.

== Analysis ==

=== Analysis of Bills ===

=== Analysis of Receipts ===
Analyzed using spreadsheet available at http://spreadsheets.google.com/pub?key=pAGYQr-yhoUh6sl5NaqEVZw. E-mail <code>leifarne at storset dot net</code> if you want edit permissions.

The analysis was performed on the following samples:


*[[#Amazon|Amazon]]
*[[#Skype|Skype]]
*[[#A1Books|A1Books]]
*[[#Barnes&Noble|Barnes&Noble]]
*[[#Facebook|Facebook]]
*[[#Google Checkout|Google Checkout]]
*[[#iTunes|iTunes]]
*[[#Longs/FujiFilm|Longs/FujiFilm]]
*[[#Mobivox/PayPal|Mobivox/PayPal]]
*[[#Symantec|Symantec]]

====Addresses====
All receipts have hCard candidates (i. e. name and/or address) of at least one of these types:
*buyer/customer
*seller
*shipping
*billing
*pickup

====Shipping====
These vendors supported '''multiple shipments''':
*Amazon.com
*Barnes&Noble
**Also displayed shipment subtotals.

These displayed '''shipping method/speed''':
*Amazon.com
*Barnes&Noble
*Symantec

These displayed '''gift''' choices:
*Amazon.com
*Barnes&Noble

For most vendors, each item had the following information:
*description
*quantity
*unit price
*line total
Google Checkout additionally provided shipping status.

====Payment information====
Most vendors displayed:
*payment method (credit card or COD, card type)
*last 4 or 5 digits of credit card
*expiration date of credit card

Some also displayed
*reference on credit-card statement ("This order will appear as ABCD0001234 on your credit-card statement.")
*the credit-card charge itself

====Totals====
Most displayed:
*subtotal
*shipping and handling cost (if applicable)
*tax
*grand total

Some also displayed:
*total before tax
*total quantity (only A1Books)

====Marketplace====
Most receipt formats are for one seller only. The following support different sellers:
*A1Books: per item
*Amazon.com: per item
*Google Checkout: per receipt
*PayPal: per receipt

====Other properties====
Almost all receipts had
*order date
**Facebook had no date.
**Longs/FujiFilm had pick-up date instead.
*order id
**Symantec did not mention order id.

Other interesting items:
*permalink (on most e-mail receipts)
*link to purchase history
*order history (Google Checkout):
**placed
**received
**charged
**shipped

====Conclusion====
Central [[microformats#the_microformats_principles|microformat principles]] are to "start as simple as possible" and use the Pareto principle. Accordingly, an 80/20 solution should focus on solving the critical few problems. One way of doing so is to look at the elements that are found in all or nearly all samples:
*addresses (buyer/customer, seller, shipping, billing, pickup)
*line item information (description, quantity, unit price)
*payment method (with credit-card information, if applicable)
*totals and charges (subtotal, shipping & handling, tax, grand total)
*order date
*order id

The following elements are more rarely seen:
*multiple shipments
*shipping details
*gift options
*credit-card-statement reference
*seller information per item
*permalink

== Existing Practices ==

Listed below is an overview of existing patterns and practices found in the wild for bill and receipt data.

===Summary of common patterns discovered===

===Other attempts to solve The Problem===
For paper receipts, [http://www.neatreceipts.com/ NeatReceipts Scanalizer] offers a heuristic-based solution.

===Open Financial Exchange===
* http://en.wikipedia.org/wiki/OFX aka OFX

== Proposal ==

== See Also ==
* [[currency]]
* [[receipt]]
* http://en.wikipedia.org/wiki/Receipt

receipt-formats

2007-08-20T22:17:24Z

Lastorset:

=Existing receipt formats=

==Contributors==
*Leif Arne Storset

==Quicken Interchange Format (QIF)==
Quicken Interchange Format (QIF) is an open specification for reading and writing financial data to media (i.e. files). It's unclear what invoice/receipt support is available, but invoice accounts are mentioned in the Wikipedia article. Further analysis needed.

===Further reading===
*[http://en.wikipedia.org/wiki/QIF Wikipedia article]

==Open Financial Exchange==
Analysis needed.

===Further reading===
*[http://en.wikipedia.org/wiki/Open_Financial_Exchange Wikipedia article]

==Google Checkout API==
Google Checkout offers an API for submitting invoice information. Two variants are provided: a simple HTML form method and a more sophisticated XML API.

===Simple HTML form===
*Item information
**name (required)
**description (required)
**quantity
**price (required)
**currency
*Shipping methods
**name
**price
**currency
**U. S. area where the method is available
*Tax
**U. S. state in which you charge tax
**tax rate

===XML API===
*Shopping cart with item information and optional expiry date
**name
**description
**unit price
**quantity
**item id (in merchant's database)
**tax table to use
**whether the item is digitally delivered and how (e-mail or download key)
**other information
*Checkout-flow support
**tax tables
***whether shipping is taxed
***tax rate
***geographic area
**shipping options
***pickup
***flat-rate shipping
****price
****applicable areas
***calculated by custom web service
*Order-processing support
**how to convey authorization information

===Further reading===
*[http://code.google.com/apis/checkout/developer/google_checkout_html_api.html#checkout_api Google Checkout HTML API]
*[http://code.google.com/apis/checkout/developer/index.html#checkout_api Google Checkout XML API]

== See Also ==
* [[receipt]]

receipt-examples

2007-08-20T21:18:44Z

Lastorset: /* Conclusion */ style

= Receipt examples =

=== Contributors ===
*Rob Manson
*Leif Arne Storset

== Real-World Examples ==

=== Bill / Invoice ===

Bills or Invoices are "yet to be paid" items.

Question: Perhaps these examples (yet to be provided) should be moved to a separate page as Bill/Invoice is quite different from Receipt.

: With [[hResume]], I've [[hresume-brainstorming|suggested]] that the subtle difference between actively seeking work and just presenting your resume be a case of including [[hlisting]] markup.
: With bills vs invoices, it may turn out that the content found within would be identical, and it might just be a case of putting in a class flag to indicate whether the presented document has been paid for or not.
: [[User:SignpostMarv|SignpostMarv]] 12:55, 21 Jul 2007 (PDT)

::I think a class flag is a great idea, but I don't believe we have any samples for invoices. However, if we look at order review vs. order summary rather than invoices vs. receipts, the payment flag does become relevant in many of the sampled online stores.
::How would such a flag be implemented?
::*<code><nowiki><div class="hreceipt unpaid"/"hreceipt paid">...</nowiki></code>
::*<code><nowiki><div class="hreceipt" title="paid">...</div></nowiki></code>
::[[User:Lastorset|Lastorset]] 14:55, 16 Aug 2007 (PDT)

=== Receipts ===

Receipts are post-purchase items.

==== Amazon ====
* [http://mobileonlinebusiness.com.au/uf/receipt/Amazon.com-Vieworder-anon.htm Example]
* contains:
**<del>email address</del> (could not find in examples)
**date of order
**order id
**shipments
***shipping estimate
***delivery estimate
***shipping address
***shipping speed
***shipping preference (item grouping)
***items
****quantity
****seller
****price
****item information
**payment
***card type
***last 5 digits
***expiration date
***billing address
***subtotal
***shipping and handling price
***total before tax
***tax
***grand total
**<del>discount price</del> (could not find in examples)
* Little semantic HTML of interest, except an anchor with id "payment-info"

Notes:
*Supports multiple shipments.
*Supports one seller per item.
*Displays shipping and delivery estimate.
*Offers item grouping preference.
*Gift options.

==== Skype ====

===== Skype Phone =====
*[[receipt-example-skype-phone|example source code]]
*[http://mobileonlinebusiness.com.au/uf/receipt/Skype-order-history.html Skype order history]

* Shipping Address
* date in dd/mm/yyyy format
* Order number in nnnn-nnnnnnn-nnn format
* Reference (was blank in example, presumed to appear on bank statement for this transaction)
* Items
** Quantity
** Description
** Price
** Total
** VAT (tax) %
* Payment
** subtotal ("total")
** shipping cost
** grand total ("total (gross)")
** total (VAT excluded)
** VAT (amount)
* Chosen payment method: "Your payment method is: Credit card"
* Legal blurb

Semantic HTML:
* Order resume class="order-listing"
* Each item class="row"
* All totals rows class="totals-row" except grand total class="grandtotal-row"

Notes:
*Displayed credit-card-statement reference (presumably).

==== Internet banking transaction receipts ====
===== Example 1 =====
<pre><nowiki>
receipt number
date
time
receipt type (e.g. TRANSFER BETWEEN MY ACCOUNTS)
transfer from
transfer to
amount
description
information/comment
</nowiki></pre>

==== Digital product purchase receipts ====
===== Example 1 : Software =====
<pre><nowiki>
receipt title/type
order/receipt number
seller's details
sold by (hCard candidate)
org
adr
tax number (VAT in this example)
tax id (Federal Tax ID)
buyer's details
buyer (hCard candidate)
name
org
street-address
locality
region
postal-code
country-name
tel
email
credit card number (PAN truncated - with type)
item list
product code
name
comments
price
delivery method
quantity
total in selected currency
total in sellers currency
total (sum of item list totals)
processing fee
grand total (final amount charged)
information (caveats and tax info)
permalink
</nowiki></pre>

===== Example 2 : SSL certificate =====
<pre><nowiki>
receipt title/type
seller (hCard candidate)
org
street-address
locality
region
postal-code
purchase information
order id
product name
domain name
validity period
number of licenses
card number (PAN truncated)
amount (with selected currency)
</nowiki></pre>

==== Physical product purchase receipts ====
===== Example 1 : Computer hardware =====
<pre><nowiki>
receipt title/type
seller's name (hCard candidate)
seller's URL (hCard candidate)
invoice id
org govt reference (ABN - Australian Business Number)
date
seller details (hCard candidate)
street-address
locality
region
postal-code
buyer (hCard candidate)
fn
billing address
street-address
locality
region
postal-code
delivery address
street-address
locality
region
postal-code
phone
item list
item
description
amount
quantity
product url
total
delivery cost
total excluding tax
tax (GST - Goods and Service Tax)
total including tax
</nowiki></pre>

==== Service purchase receipts ====
===== Example 1 : Online subscription =====
<pre><nowiki>
seller's details (hCard candidate)
org
street-address
locality
region
postal-code
country-name
buyer's details (hCard candidate)
fn
street-address
locality
region
postal-code
phone
date
receipt id
item list
product description
quantity
rate (per unit)
price
sub total
amount paid
balance due
information
transaction id
</nowiki></pre>

===== Example 2 : Co-location =====
<pre><nowiki>
receipt title/type
sellers details (hCard candidate)
org
url
phone
message
receipt number
date
amount
information
</nowiki></pre>

==== A1Books ====
[http://mobileonlinebusiness.com.au/uf/receipt/A1Books-Sales-Order-anon.htm Example]

*vendor
**name
**fax
*date
*order number
*shipping address
*billing address
*items
**description
**list price
**sale price
**quantity
**amount
*subtotal
*shipping
*total
**quantity
**amount
*account information
**phone
**e-mail
*payment
**method
**last four digits

No semantic HTML.

Notes:
*Supports one seller per item.
*Does not display tax.

==== Barnes&Noble ====
[http://mobileonlinebusiness.com.au/uf/receipt/BarnesAndNoble.com-receipt.anon.tidied.htm Example]

*date
*shipping address
*billing address
*payment
**method
**last 4 digits
**exp. date
**charge
*savings on shipping
*order no.
*delivery option
*items
**description: title, author, ISBN, price
**qty
**gift options: wrap, message
**total price
*shipment subtotal
*shipping cost
*tax
*shipment total (seems to account for orders requiring multiple shipments)
*order total

Semantic HTML:
*receiptOrderNumbers
*receiptOrderPlacedOn
*orderInformation
**shippingAddress
**billingAddress
**paymentInformation
*shippingSelections
*showProducts
**reviewTable
***qtyValuePosition
***reviewGiftOptions
*reviewTotalsDisplay
**reviewTotalsSummary
**reviewTotalsNote
**reviewTotalsBreakdown
*reviewTotalsSummary
**reviewGrandTotal
*reviewCreditCardCharged
*review

The semantic class names found are a good start, although the "review" part appears to be context-specific (reviewing an order). Additionally, the implied hierarchy in names such as "reviewTotalsSummary" and "receiptOrderPlacedOn" is probably unnecessary for our purposes.

Notes:
*Supports multiple shipments.
*Gift options.
*Explicitly stated credit-card charge.

==== Facebook ====
[http://mobileonlinebusiness.com.au/uf/receipt/Facebook-gift-receipt.html Example]

*purchase total
*items (informal description of two items, including quantity)
*recipient name
*order id
*billed-to name

No relevant semantic HTML.

Notes:
*Quite minimal and informal receipt. Good example of how a microformat would preserve human readability and informal style while enabling machine reading.

==== Google Checkout ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Google-Checkout-e-mail-receipt.tidied.html Example email receipt]
*[http://mobileonlinebusiness.com.au/uf/receipt/Google-Checkout-Order-Receipt_DVD-Empire.tidied.htm Example web receipt]

*vendor address
*shipping address
*date
*order id
*items
**shipping status ("Not yet shipped", etc.)
**qty.
**description
**price
*shipping cost
*tax
*total
*order history (placed, received, charged, shipped) (web receipt only)
**credit-card statement reference (only after the charge has been made)
*payment info (web receipt only)
**card type
**last 4 digits
**exp. date
**cardholder address
*permalink

Semantic HTML:
*taxRow
**taxIdentifier
**taxAmount
*totalAmount

Notes:
*Explicit seller address (one per order).
*Current shipping status of each item.
*E-mail receipt has permalink.
*Order history (date placed, received, charged, shipped).
*Displayed credit-card statement reference only after card was charged.

==== iTunes ====
*[http://mobileonlinebusiness.com.au/uf/receipt/iTunes-receipt-e-mail.html iTunes e-mail receipt]

*billing address
*order no.
*receipt date
*order total
*card
**type
**last 4 digits
*item
**item no.
**description (including link to write a review)
**unit price
*subtotal
*tax

No relevant semantic HTML.

Notes:
*No quantity information.

==== Longs/FujiFilm ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Longs-Fujifilm-photo-receipt.html Longs/Fujifilm e-mail receipt]

*order no.
*payment info
**method (COD, credit card, etc.)
*customer address
*pickup address
*items
**name
**qty.
**description
**price
**line item subtotal
*order items total
*tax
*order total

Semantic HTML:
*payment-heading

Notes:
*No order date; has pick-up date instead.
*Has pickup address rather than shipping address.

==== Mobivox/PayPal ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Mobivox-PayPal.htm Mobivox/PayPal receipt]
*[http://mobileonlinebusiness.com.au/uf/receipt/Mobivox-PayPal-printable.htm Mobivox/PayPal printable receipt]

*seller address
*receipt id
*date of order
*items
**description
**item option (not quite sure what this is for)
**unit price
**qty
**total
*subtotal
*tax
*total amount
*payment info
**method
**last 4 digits
**charge
**appears on bill/statement as "MOBIVOXCORP"
*buyer contact

Relevant semantic HTML:
*order-summary
**cart
***(unnamed tr)
****item-name
****item-total
****item-option (not quite sure what this is for)
**subtotal
**totals-value
**totals-currency
**purchase-summary
***summary-total
****price-total
****price-currency
*funding-mix
**payment-type
**amount
**ccStatement
*contact-information (contains hCard microformat)

This semantic HTML is the most complete and well-thought-out I've seen in this analysis. It even makes use of the fieldset element in forms, something I've never seen before.[[User:Lastorset|Lastorset]] 16:21, 25 Jul 2007 (PDT)

Microformats used:
*hCard (non-compliant due to missing formatted name): buyer contact info

Notes:
*Explicitly stated credit-card charge.
*Displayed credit-card-statement reference.
*Explicitly displayed seller address (one seller per order).

==== Symantec ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Symantec-reminder-e-mail.html Symantec e-mail reminder]

*buyer name
*date
*payment method
*last 4 digits
*appears on statement as "DR *Symantec"
*items
**qty
**product name
**platform
**delivery method
**price
*subtotal
*grand total
*permalink

No relevant semantic HTML

Notes:
*As an e-mail "order reminder" rather than a receipt, this was slightly more informal than the other samples. As such there was
**no order id
**a permalink
*"Delivery method" could be download or ship.

== Analysis ==

=== Analysis of Bills ===

=== Analysis of Receipts ===
Analyzed using spreadsheet available at http://spreadsheets.google.com/pub?key=pAGYQr-yhoUh6sl5NaqEVZw. E-mail <code>leifarne at storset dot net</code> if you want edit permissions.

The analysis was performed on the following samples:


*[[#Amazon|Amazon]]
*[[#Skype|Skype]]
*[[#A1Books|A1Books]]
*[[#Barnes&Noble|Barnes&Noble]]
*[[#Facebook|Facebook]]
*[[#Google Checkout|Google Checkout]]
*[[#iTunes|iTunes]]
*[[#Longs/FujiFilm|Longs/FujiFilm]]
*[[#Mobivox/PayPal|Mobivox/PayPal]]
*[[#Symantec|Symantec]]

====Addresses====
All receipts have hCard candidates (i. e. name and/or address) of at least one of these types:
*buyer/customer
*seller
*shipping
*billing
*pickup

====Shipping====
These vendors supported '''multiple shipments''':
*Amazon.com
*Barnes&Noble
**Also displayed shipment subtotals.

These displayed '''shipping method/speed''':
*Amazon.com
*Barnes&Noble
*Symantec

These displayed '''gift''' choices:
*Amazon.com
*Barnes&Noble

For most vendors, each item had the following information:
*description
*quantity
*unit price
*line total
Google Checkout additionally provided shipping status.

====Payment information====
Most vendors displayed:
*payment method (credit card or COD, card type)
*last 4 or 5 digits of credit card
*expiration date of credit card

Some also displayed
*reference on credit-card statement ("This order will appear as ABCD0001234 on your credit-card statement.")
*the credit-card charge itself

====Totals====
Most displayed:
*subtotal
*shipping and handling cost (if applicable)
*tax
*grand total

Some also displayed:
*total before tax
*total quantity (only A1Books)

====Marketplace====
Most receipt formats are for one seller only. The following support different sellers:
*A1Books: per item
*Amazon.com: per item
*Google Checkout: per receipt
*PayPal: per receipt

====Other properties====
Almost all receipts had
*order date
**Facebook had no date.
**Longs/FujiFilm had pick-up date instead.
*order id
**Symantec did not mention order id.

Other interesting items:
*permalink (on most e-mail receipts)
*link to purchase history
*order history (Google Checkout):
**placed
**received
**charged
**shipped

====Conclusion====
Central [[microformats#the_microformats_principles|microformat principles]] are to "start as simple as possible" and use the Pareto principle. Accordingly, an 80/20 solution should focus on solving the critical few problems. One way of doing so is to look at the elements that are found in all or nearly all samples:
*addresses (buyer/customer, seller, shipping, billing, pickup)
*line item information (description, quantity, unit price)
*payment method (with credit-card information, if applicable)
*totals and charges (subtotal, shipping & handling, tax, grand total)
*order date
*order id

The following elements are more rarely seen:
*multiple shipments
*shipping details
*gift options
*credit-card-statement reference
*seller information per item
*permalink

== Existing Practices ==

Listed below is an overview of existing patterns and practices found in the wild for bill and receipt data.

===Summary of common patterns discovered===

===Other attempts to solve The Problem===
For paper receipts, [http://www.neatreceipts.com/ NeatReceipts Scanalizer] offers a heuristic-based solution.

== Proposal ==

== See Also ==
* [[receipt]]
* http://en.wikipedia.org/wiki/Receipt

receipt-examples

2007-08-20T21:09:22Z

Lastorset: /* Conclusion */ wrote summary

= Receipt examples =

=== Contributors ===
*Rob Manson
*Leif Arne Storset

== Real-World Examples ==

=== Bill / Invoice ===

Bills or Invoices are "yet to be paid" items.

Question: Perhaps these examples (yet to be provided) should be moved to a separate page as Bill/Invoice is quite different from Receipt.

: With [[hResume]], I've [[hresume-brainstorming|suggested]] that the subtle difference between actively seeking work and just presenting your resume be a case of including [[hlisting]] markup.
: With bills vs invoices, it may turn out that the content found within would be identical, and it might just be a case of putting in a class flag to indicate whether the presented document has been paid for or not.
: [[User:SignpostMarv|SignpostMarv]] 12:55, 21 Jul 2007 (PDT)

::I think a class flag is a great idea, but I don't believe we have any samples for invoices. However, if we look at order review vs. order summary rather than invoices vs. receipts, the payment flag does become relevant in many of the sampled online stores.
::How would such a flag be implemented?
::*<code><nowiki><div class="hreceipt unpaid"/"hreceipt paid">...</nowiki></code>
::*<code><nowiki><div class="hreceipt" title="paid">...</div></nowiki></code>
::[[User:Lastorset|Lastorset]] 14:55, 16 Aug 2007 (PDT)

=== Receipts ===

Receipts are post-purchase items.

==== Amazon ====
* [http://mobileonlinebusiness.com.au/uf/receipt/Amazon.com-Vieworder-anon.htm Example]
* contains:
**<del>email address</del> (could not find in examples)
**date of order
**order id
**shipments
***shipping estimate
***delivery estimate
***shipping address
***shipping speed
***shipping preference (item grouping)
***items
****quantity
****seller
****price
****item information
**payment
***card type
***last 5 digits
***expiration date
***billing address
***subtotal
***shipping and handling price
***total before tax
***tax
***grand total
**<del>discount price</del> (could not find in examples)
* Little semantic HTML of interest, except an anchor with id "payment-info"

Notes:
*Supports multiple shipments.
*Supports one seller per item.
*Displays shipping and delivery estimate.
*Offers item grouping preference.
*Gift options.

==== Skype ====

===== Skype Phone =====
*[[receipt-example-skype-phone|example source code]]
*[http://mobileonlinebusiness.com.au/uf/receipt/Skype-order-history.html Skype order history]

* Shipping Address
* date in dd/mm/yyyy format
* Order number in nnnn-nnnnnnn-nnn format
* Reference (was blank in example, presumed to appear on bank statement for this transaction)
* Items
** Quantity
** Description
** Price
** Total
** VAT (tax) %
* Payment
** subtotal ("total")
** shipping cost
** grand total ("total (gross)")
** total (VAT excluded)
** VAT (amount)
* Chosen payment method: "Your payment method is: Credit card"
* Legal blurb

Semantic HTML:
* Order resume class="order-listing"
* Each item class="row"
* All totals rows class="totals-row" except grand total class="grandtotal-row"

Notes:
*Displayed credit-card-statement reference (presumably).

==== Internet banking transaction receipts ====
===== Example 1 =====
<pre><nowiki>
receipt number
date
time
receipt type (e.g. TRANSFER BETWEEN MY ACCOUNTS)
transfer from
transfer to
amount
description
information/comment
</nowiki></pre>

==== Digital product purchase receipts ====
===== Example 1 : Software =====
<pre><nowiki>
receipt title/type
order/receipt number
seller's details
sold by (hCard candidate)
org
adr
tax number (VAT in this example)
tax id (Federal Tax ID)
buyer's details
buyer (hCard candidate)
name
org
street-address
locality
region
postal-code
country-name
tel
email
credit card number (PAN truncated - with type)
item list
product code
name
comments
price
delivery method
quantity
total in selected currency
total in sellers currency
total (sum of item list totals)
processing fee
grand total (final amount charged)
information (caveats and tax info)
permalink
</nowiki></pre>

===== Example 2 : SSL certificate =====
<pre><nowiki>
receipt title/type
seller (hCard candidate)
org
street-address
locality
region
postal-code
purchase information
order id
product name
domain name
validity period
number of licenses
card number (PAN truncated)
amount (with selected currency)
</nowiki></pre>

==== Physical product purchase receipts ====
===== Example 1 : Computer hardware =====
<pre><nowiki>
receipt title/type
seller's name (hCard candidate)
seller's URL (hCard candidate)
invoice id
org govt reference (ABN - Australian Business Number)
date
seller details (hCard candidate)
street-address
locality
region
postal-code
buyer (hCard candidate)
fn
billing address
street-address
locality
region
postal-code
delivery address
street-address
locality
region
postal-code
phone
item list
item
description
amount
quantity
product url
total
delivery cost
total excluding tax
tax (GST - Goods and Service Tax)
total including tax
</nowiki></pre>

==== Service purchase receipts ====
===== Example 1 : Online subscription =====
<pre><nowiki>
seller's details (hCard candidate)
org
street-address
locality
region
postal-code
country-name
buyer's details (hCard candidate)
fn
street-address
locality
region
postal-code
phone
date
receipt id
item list
product description
quantity
rate (per unit)
price
sub total
amount paid
balance due
information
transaction id
</nowiki></pre>

===== Example 2 : Co-location =====
<pre><nowiki>
receipt title/type
sellers details (hCard candidate)
org
url
phone
message
receipt number
date
amount
information
</nowiki></pre>

==== A1Books ====
[http://mobileonlinebusiness.com.au/uf/receipt/A1Books-Sales-Order-anon.htm Example]

*vendor
**name
**fax
*date
*order number
*shipping address
*billing address
*items
**description
**list price
**sale price
**quantity
**amount
*subtotal
*shipping
*total
**quantity
**amount
*account information
**phone
**e-mail
*payment
**method
**last four digits

No semantic HTML.

Notes:
*Supports one seller per item.
*Does not display tax.

==== Barnes&Noble ====
[http://mobileonlinebusiness.com.au/uf/receipt/BarnesAndNoble.com-receipt.anon.tidied.htm Example]

*date
*shipping address
*billing address
*payment
**method
**last 4 digits
**exp. date
**charge
*savings on shipping
*order no.
*delivery option
*items
**description: title, author, ISBN, price
**qty
**gift options: wrap, message
**total price
*shipment subtotal
*shipping cost
*tax
*shipment total (seems to account for orders requiring multiple shipments)
*order total

Semantic HTML:
*receiptOrderNumbers
*receiptOrderPlacedOn
*orderInformation
**shippingAddress
**billingAddress
**paymentInformation
*shippingSelections
*showProducts
**reviewTable
***qtyValuePosition
***reviewGiftOptions
*reviewTotalsDisplay
**reviewTotalsSummary
**reviewTotalsNote
**reviewTotalsBreakdown
*reviewTotalsSummary
**reviewGrandTotal
*reviewCreditCardCharged
*review

The semantic class names found are a good start, although the "review" part appears to be context-specific (reviewing an order). Additionally, the implied hierarchy in names such as "reviewTotalsSummary" and "receiptOrderPlacedOn" is probably unnecessary for our purposes.

Notes:
*Supports multiple shipments.
*Gift options.
*Explicitly stated credit-card charge.

==== Facebook ====
[http://mobileonlinebusiness.com.au/uf/receipt/Facebook-gift-receipt.html Example]

*purchase total
*items (informal description of two items, including quantity)
*recipient name
*order id
*billed-to name

No relevant semantic HTML.

Notes:
*Quite minimal and informal receipt. Good example of how a microformat would preserve human readability and informal style while enabling machine reading.

==== Google Checkout ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Google-Checkout-e-mail-receipt.tidied.html Example email receipt]
*[http://mobileonlinebusiness.com.au/uf/receipt/Google-Checkout-Order-Receipt_DVD-Empire.tidied.htm Example web receipt]

*vendor address
*shipping address
*date
*order id
*items
**shipping status ("Not yet shipped", etc.)
**qty.
**description
**price
*shipping cost
*tax
*total
*order history (placed, received, charged, shipped) (web receipt only)
**credit-card statement reference (only after the charge has been made)
*payment info (web receipt only)
**card type
**last 4 digits
**exp. date
**cardholder address
*permalink

Semantic HTML:
*taxRow
**taxIdentifier
**taxAmount
*totalAmount

Notes:
*Explicit seller address (one per order).
*Current shipping status of each item.
*E-mail receipt has permalink.
*Order history (date placed, received, charged, shipped).
*Displayed credit-card statement reference only after card was charged.

==== iTunes ====
*[http://mobileonlinebusiness.com.au/uf/receipt/iTunes-receipt-e-mail.html iTunes e-mail receipt]

*billing address
*order no.
*receipt date
*order total
*card
**type
**last 4 digits
*item
**item no.
**description (including link to write a review)
**unit price
*subtotal
*tax

No relevant semantic HTML.

Notes:
*No quantity information.

==== Longs/FujiFilm ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Longs-Fujifilm-photo-receipt.html Longs/Fujifilm e-mail receipt]

*order no.
*payment info
**method (COD, credit card, etc.)
*customer address
*pickup address
*items
**name
**qty.
**description
**price
**line item subtotal
*order items total
*tax
*order total

Semantic HTML:
*payment-heading

Notes:
*No order date; has pick-up date instead.
*Has pickup address rather than shipping address.

==== Mobivox/PayPal ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Mobivox-PayPal.htm Mobivox/PayPal receipt]
*[http://mobileonlinebusiness.com.au/uf/receipt/Mobivox-PayPal-printable.htm Mobivox/PayPal printable receipt]

*seller address
*receipt id
*date of order
*items
**description
**item option (not quite sure what this is for)
**unit price
**qty
**total
*subtotal
*tax
*total amount
*payment info
**method
**last 4 digits
**charge
**appears on bill/statement as "MOBIVOXCORP"
*buyer contact

Relevant semantic HTML:
*order-summary
**cart
***(unnamed tr)
****item-name
****item-total
****item-option (not quite sure what this is for)
**subtotal
**totals-value
**totals-currency
**purchase-summary
***summary-total
****price-total
****price-currency
*funding-mix
**payment-type
**amount
**ccStatement
*contact-information (contains hCard microformat)

This semantic HTML is the most complete and well-thought-out I've seen in this analysis. It even makes use of the fieldset element in forms, something I've never seen before.[[User:Lastorset|Lastorset]] 16:21, 25 Jul 2007 (PDT)

Microformats used:
*hCard (non-compliant due to missing formatted name): buyer contact info

Notes:
*Explicitly stated credit-card charge.
*Displayed credit-card-statement reference.
*Explicitly displayed seller address (one seller per order).

==== Symantec ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Symantec-reminder-e-mail.html Symantec e-mail reminder]

*buyer name
*date
*payment method
*last 4 digits
*appears on statement as "DR *Symantec"
*items
**qty
**product name
**platform
**delivery method
**price
*subtotal
*grand total
*permalink

No relevant semantic HTML

Notes:
*As an e-mail "order reminder" rather than a receipt, this was slightly more informal than the other samples. As such there was
**no order id
**a permalink
*"Delivery method" could be download or ship.

== Analysis ==

=== Analysis of Bills ===

=== Analysis of Receipts ===
Analyzed using spreadsheet available at http://spreadsheets.google.com/pub?key=pAGYQr-yhoUh6sl5NaqEVZw. E-mail <code>leifarne at storset dot net</code> if you want edit permissions.

The analysis was performed on the following samples:


*[[#Amazon|Amazon]]
*[[#Skype|Skype]]
*[[#A1Books|A1Books]]
*[[#Barnes&Noble|Barnes&Noble]]
*[[#Facebook|Facebook]]
*[[#Google Checkout|Google Checkout]]
*[[#iTunes|iTunes]]
*[[#Longs/FujiFilm|Longs/FujiFilm]]
*[[#Mobivox/PayPal|Mobivox/PayPal]]
*[[#Symantec|Symantec]]

====Addresses====
All receipts have hCard candidates (i. e. name and/or address) of at least one of these types:
*buyer/customer
*seller
*shipping
*billing
*pickup

====Shipping====
These vendors supported '''multiple shipments''':
*Amazon.com
*Barnes&Noble
**Also displayed shipment subtotals.

These displayed '''shipping method/speed''':
*Amazon.com
*Barnes&Noble
*Symantec

These displayed '''gift''' choices:
*Amazon.com
*Barnes&Noble

For most vendors, each item had the following information:
*description
*quantity
*unit price
*line total
Google Checkout additionally provided shipping status.

====Payment information====
Most vendors displayed:
*payment method (credit card or COD, card type)
*last 4 or 5 digits of credit card
*expiration date of credit card

Some also displayed
*reference on credit-card statement ("This order will appear as ABCD0001234 on your credit-card statement.")
*the credit-card charge itself

====Totals====
Most displayed:
*subtotal
*shipping and handling cost (if applicable)
*tax
*grand total

Some also displayed:
*total before tax
*total quantity (only A1Books)

====Marketplace====
Most receipt formats are for one seller only. The following support different sellers:
*A1Books: per item
*Amazon.com: per item
*Google Checkout: per receipt
*PayPal: per receipt

====Other properties====
Almost all receipts had
*order date
**Facebook had no date.
**Longs/FujiFilm had pick-up date instead.
*order id
**Symantec did not mention order id.

Other interesting items:
*permalink (on most e-mail receipts)
*link to purchase history
*order history (Google Checkout):
**placed
**received
**charged
**shipped

====Conclusion====
Central [[microformats#the_microformats_principles|microformat principles]] are to "start as simple as possible" and use the Pareto principle. Accordingly, an 80/20 solution should focus on solving the critical few problems. One way of doing so is to focus on the elements that are found in all or nearly all samples:
*addresses (buyer/customer, seller, shipping, billing, pickup)
*line item information (description, quantity, unit price)
*payment method (with credit-card information, if applicable)
*totals and charges (subtotal, shipping & handling, tax, grand total)
*order date
*order id

The following elements are more rarely seen:
*multiple shipments
*shipping details
*gift options
*credit-card-statement reference
*seller information per item
*permalink

== Existing Practices ==

Listed below is an overview of existing patterns and practices found in the wild for bill and receipt data.

===Summary of common patterns discovered===

===Other attempts to solve The Problem===
For paper receipts, [http://www.neatreceipts.com/ NeatReceipts Scanalizer] offers a heuristic-based solution.

== Proposal ==

== See Also ==
* [[receipt]]
* http://en.wikipedia.org/wiki/Receipt

receipt-examples

2007-08-20T20:16:03Z

Lastorset: /* Analysis of Receipts */ Made basis of analysis explicit

= Receipt examples =

=== Contributors ===
*Rob Manson
*Leif Arne Storset

== Real-World Examples ==

=== Bill / Invoice ===

Bills or Invoices are "yet to be paid" items.

Question: Perhaps these examples (yet to be provided) should be moved to a separate page as Bill/Invoice is quite different from Receipt.

: With [[hResume]], I've [[hresume-brainstorming|suggested]] that the subtle difference between actively seeking work and just presenting your resume be a case of including [[hlisting]] markup.
: With bills vs invoices, it may turn out that the content found within would be identical, and it might just be a case of putting in a class flag to indicate whether the presented document has been paid for or not.
: [[User:SignpostMarv|SignpostMarv]] 12:55, 21 Jul 2007 (PDT)

::I think a class flag is a great idea, but I don't believe we have any samples for invoices. However, if we look at order review vs. order summary rather than invoices vs. receipts, the payment flag does become relevant in many of the sampled online stores.
::How would such a flag be implemented?
::*<code><nowiki><div class="hreceipt unpaid"/"hreceipt paid">...</nowiki></code>
::*<code><nowiki><div class="hreceipt" title="paid">...</div></nowiki></code>
::[[User:Lastorset|Lastorset]] 14:55, 16 Aug 2007 (PDT)

=== Receipts ===

Receipts are post-purchase items.

==== Amazon ====
* [http://mobileonlinebusiness.com.au/uf/receipt/Amazon.com-Vieworder-anon.htm Example]
* contains:
**<del>email address</del> (could not find in examples)
**date of order
**order id
**shipments
***shipping estimate
***delivery estimate
***shipping address
***shipping speed
***shipping preference (item grouping)
***items
****quantity
****seller
****price
****item information
**payment
***card type
***last 5 digits
***expiration date
***billing address
***subtotal
***shipping and handling price
***total before tax
***tax
***grand total
**<del>discount price</del> (could not find in examples)
* Little semantic HTML of interest, except an anchor with id "payment-info"

Notes:
*Supports multiple shipments.
*Supports one seller per item.
*Displays shipping and delivery estimate.
*Offers item grouping preference.
*Gift options.

==== Skype ====

===== Skype Phone =====
*[[receipt-example-skype-phone|example source code]]
*[http://mobileonlinebusiness.com.au/uf/receipt/Skype-order-history.html Skype order history]

* Shipping Address
* date in dd/mm/yyyy format
* Order number in nnnn-nnnnnnn-nnn format
* Reference (was blank in example, presumed to appear on bank statement for this transaction)
* Items
** Quantity
** Description
** Price
** Total
** VAT (tax) %
* Payment
** subtotal ("total")
** shipping cost
** grand total ("total (gross)")
** total (VAT excluded)
** VAT (amount)
* Chosen payment method: "Your payment method is: Credit card"
* Legal blurb

Semantic HTML:
* Order resume class="order-listing"
* Each item class="row"
* All totals rows class="totals-row" except grand total class="grandtotal-row"

Notes:
*Displayed credit-card-statement reference (presumably).

==== Internet banking transaction receipts ====
===== Example 1 =====
<pre><nowiki>
receipt number
date
time
receipt type (e.g. TRANSFER BETWEEN MY ACCOUNTS)
transfer from
transfer to
amount
description
information/comment
</nowiki></pre>

==== Digital product purchase receipts ====
===== Example 1 : Software =====
<pre><nowiki>
receipt title/type
order/receipt number
seller's details
sold by (hCard candidate)
org
adr
tax number (VAT in this example)
tax id (Federal Tax ID)
buyer's details
buyer (hCard candidate)
name
org
street-address
locality
region
postal-code
country-name
tel
email
credit card number (PAN truncated - with type)
item list
product code
name
comments
price
delivery method
quantity
total in selected currency
total in sellers currency
total (sum of item list totals)
processing fee
grand total (final amount charged)
information (caveats and tax info)
permalink
</nowiki></pre>

===== Example 2 : SSL certificate =====
<pre><nowiki>
receipt title/type
seller (hCard candidate)
org
street-address
locality
region
postal-code
purchase information
order id
product name
domain name
validity period
number of licenses
card number (PAN truncated)
amount (with selected currency)
</nowiki></pre>

==== Physical product purchase receipts ====
===== Example 1 : Computer hardware =====
<pre><nowiki>
receipt title/type
seller's name (hCard candidate)
seller's URL (hCard candidate)
invoice id
org govt reference (ABN - Australian Business Number)
date
seller details (hCard candidate)
street-address
locality
region
postal-code
buyer (hCard candidate)
fn
billing address
street-address
locality
region
postal-code
delivery address
street-address
locality
region
postal-code
phone
item list
item
description
amount
quantity
product url
total
delivery cost
total excluding tax
tax (GST - Goods and Service Tax)
total including tax
</nowiki></pre>

==== Service purchase receipts ====
===== Example 1 : Online subscription =====
<pre><nowiki>
seller's details (hCard candidate)
org
street-address
locality
region
postal-code
country-name
buyer's details (hCard candidate)
fn
street-address
locality
region
postal-code
phone
date
receipt id
item list
product description
quantity
rate (per unit)
price
sub total
amount paid
balance due
information
transaction id
</nowiki></pre>

===== Example 2 : Co-location =====
<pre><nowiki>
receipt title/type
sellers details (hCard candidate)
org
url
phone
message
receipt number
date
amount
information
</nowiki></pre>

==== A1Books ====
[http://mobileonlinebusiness.com.au/uf/receipt/A1Books-Sales-Order-anon.htm Example]

*vendor
**name
**fax
*date
*order number
*shipping address
*billing address
*items
**description
**list price
**sale price
**quantity
**amount
*subtotal
*shipping
*total
**quantity
**amount
*account information
**phone
**e-mail
*payment
**method
**last four digits

No semantic HTML.

Notes:
*Supports one seller per item.
*Does not display tax.

==== Barnes&Noble ====
[http://mobileonlinebusiness.com.au/uf/receipt/BarnesAndNoble.com-receipt.anon.tidied.htm Example]

*date
*shipping address
*billing address
*payment
**method
**last 4 digits
**exp. date
**charge
*savings on shipping
*order no.
*delivery option
*items
**description: title, author, ISBN, price
**qty
**gift options: wrap, message
**total price
*shipment subtotal
*shipping cost
*tax
*shipment total (seems to account for orders requiring multiple shipments)
*order total

Semantic HTML:
*receiptOrderNumbers
*receiptOrderPlacedOn
*orderInformation
**shippingAddress
**billingAddress
**paymentInformation
*shippingSelections
*showProducts
**reviewTable
***qtyValuePosition
***reviewGiftOptions
*reviewTotalsDisplay
**reviewTotalsSummary
**reviewTotalsNote
**reviewTotalsBreakdown
*reviewTotalsSummary
**reviewGrandTotal
*reviewCreditCardCharged
*review

The semantic class names found are a good start, although the "review" part appears to be context-specific (reviewing an order). Additionally, the implied hierarchy in names such as "reviewTotalsSummary" and "receiptOrderPlacedOn" is probably unnecessary for our purposes.

Notes:
*Supports multiple shipments.
*Gift options.
*Explicitly stated credit-card charge.

==== Facebook ====
[http://mobileonlinebusiness.com.au/uf/receipt/Facebook-gift-receipt.html Example]

*purchase total
*items (informal description of two items, including quantity)
*recipient name
*order id
*billed-to name

No relevant semantic HTML.

Notes:
*Quite minimal and informal receipt. Good example of how a microformat would preserve human readability and informal style while enabling machine reading.

==== Google Checkout ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Google-Checkout-e-mail-receipt.tidied.html Example email receipt]
*[http://mobileonlinebusiness.com.au/uf/receipt/Google-Checkout-Order-Receipt_DVD-Empire.tidied.htm Example web receipt]

*vendor address
*shipping address
*date
*order id
*items
**shipping status ("Not yet shipped", etc.)
**qty.
**description
**price
*shipping cost
*tax
*total
*order history (placed, received, charged, shipped) (web receipt only)
**credit-card statement reference (only after the charge has been made)
*payment info (web receipt only)
**card type
**last 4 digits
**exp. date
**cardholder address
*permalink

Semantic HTML:
*taxRow
**taxIdentifier
**taxAmount
*totalAmount

Notes:
*Explicit seller address (one per order).
*Current shipping status of each item.
*E-mail receipt has permalink.
*Order history (date placed, received, charged, shipped).
*Displayed credit-card statement reference only after card was charged.

==== iTunes ====
*[http://mobileonlinebusiness.com.au/uf/receipt/iTunes-receipt-e-mail.html iTunes e-mail receipt]

*billing address
*order no.
*receipt date
*order total
*card
**type
**last 4 digits
*item
**item no.
**description (including link to write a review)
**unit price
*subtotal
*tax

No relevant semantic HTML.

Notes:
*No quantity information.

==== Longs/FujiFilm ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Longs-Fujifilm-photo-receipt.html Longs/Fujifilm e-mail receipt]

*order no.
*payment info
**method (COD, credit card, etc.)
*customer address
*pickup address
*items
**name
**qty.
**description
**price
**line item subtotal
*order items total
*tax
*order total

Semantic HTML:
*payment-heading

Notes:
*No order date; has pick-up date instead.
*Has pickup address rather than shipping address.

==== Mobivox/PayPal ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Mobivox-PayPal.htm Mobivox/PayPal receipt]
*[http://mobileonlinebusiness.com.au/uf/receipt/Mobivox-PayPal-printable.htm Mobivox/PayPal printable receipt]

*seller address
*receipt id
*date of order
*items
**description
**item option (not quite sure what this is for)
**unit price
**qty
**total
*subtotal
*tax
*total amount
*payment info
**method
**last 4 digits
**charge
**appears on bill/statement as "MOBIVOXCORP"
*buyer contact

Relevant semantic HTML:
*order-summary
**cart
***(unnamed tr)
****item-name
****item-total
****item-option (not quite sure what this is for)
**subtotal
**totals-value
**totals-currency
**purchase-summary
***summary-total
****price-total
****price-currency
*funding-mix
**payment-type
**amount
**ccStatement
*contact-information (contains hCard microformat)

This semantic HTML is the most complete and well-thought-out I've seen in this analysis. It even makes use of the fieldset element in forms, something I've never seen before.[[User:Lastorset|Lastorset]] 16:21, 25 Jul 2007 (PDT)

Microformats used:
*hCard (non-compliant due to missing formatted name): buyer contact info

Notes:
*Explicitly stated credit-card charge.
*Displayed credit-card-statement reference.
*Explicitly displayed seller address (one seller per order).

==== Symantec ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Symantec-reminder-e-mail.html Symantec e-mail reminder]

*buyer name
*date
*payment method
*last 4 digits
*appears on statement as "DR *Symantec"
*items
**qty
**product name
**platform
**delivery method
**price
*subtotal
*grand total
*permalink

No relevant semantic HTML

Notes:
*As an e-mail "order reminder" rather than a receipt, this was slightly more informal than the other samples. As such there was
**no order id
**a permalink
*"Delivery method" could be download or ship.

== Analysis ==

=== Analysis of Bills ===

=== Analysis of Receipts ===
Analyzed using spreadsheet available at http://spreadsheets.google.com/pub?key=pAGYQr-yhoUh6sl5NaqEVZw. E-mail <code>leifarne at storset dot net</code> if you want edit permissions.

The analysis was performed on the following samples:


*[[#Amazon|Amazon]]
*[[#Skype|Skype]]
*[[#A1Books|A1Books]]
*[[#Barnes&Noble|Barnes&Noble]]
*[[#Facebook|Facebook]]
*[[#Google Checkout|Google Checkout]]
*[[#iTunes|iTunes]]
*[[#Longs/FujiFilm|Longs/FujiFilm]]
*[[#Mobivox/PayPal|Mobivox/PayPal]]
*[[#Symantec|Symantec]]

====Addresses====
All receipts have hCard candidates (i. e. name and/or address) of at least one of these types:
*buyer/customer
*seller
*shipping
*billing
*pickup

====Shipping====
These vendors supported '''multiple shipments''':
*Amazon.com
*Barnes&Noble
**Also displayed shipment subtotals.

These displayed '''shipping method/speed''':
*Amazon.com
*Barnes&Noble
*Symantec

These displayed '''gift''' choices:
*Amazon.com
*Barnes&Noble

For most vendors, each item had the following information:
*description
*quantity
*unit price
*line total
Google Checkout additionally provided shipping status.

====Payment information====
Most vendors displayed:
*payment method (credit card or COD, card type)
*last 4 or 5 digits of credit card
*expiration date of credit card

Some also displayed
*reference on credit-card statement ("This order will appear as ABCD0001234 on your credit-card statement.")
*the credit-card charge itself

====Totals====
Most displayed:
*subtotal
*shipping and handling cost (if applicable)
*tax
*grand total

Some also displayed:
*total before tax
*total quantity (only A1Books)

====Marketplace====
Most receipt formats are for one seller only. The following support different sellers:
*A1Books: per item
*Amazon.com: per item
*Google Checkout: per receipt
*PayPal: per receipt

====Other properties====
Almost all receipts had
*order date
**Facebook had no date.
**Longs/FujiFilm had pick-up date instead.
*order id
**Symantec did not mention order id.

Other interesting items:
*permalink (on most e-mail receipts)
*link to purchase history
*order history (Google Checkout):
**placed
**received
**charged
**shipped

== Existing Practices ==

Listed below is an overview of existing patterns and practices found in the wild for bill and receipt data.

===Summary of common patterns discovered===

===Other attempts to solve The Problem===
For paper receipts, [http://www.neatreceipts.com/ NeatReceipts Scanalizer] offers a heuristic-based solution.

== Proposal ==

== See Also ==
* [[receipt]]
* http://en.wikipedia.org/wiki/Receipt

receipt

2007-08-17T18:41:16Z

Lastorset: /* Related pages */ linked to receipt-formats

=Receipt=

Preparation for a possible receipt/ billing microformat.

== Contributors ==

*[[User:AndyMabbett|Andy Mabbett]]
*Rob Manson

== The Problem ==

The ability to securely purchase items through a web browser has created a large number of sites that contain the entire purchasing process online. It is common that a customer selects the items that they want to buy, a bill is displayed, a purchase occurs and finally a receipt is displayed to the customer. Currently, it is difficult for a computer to understand when a bill is displayed, when a receipt is displayed and what items are a part of that bill or receipt.

Typically, receipts are e-mailed to customers. It would be helpful if there was a better way to extract the receipt data from a website and process it using another piece of software. It would also be beneficial for other Microformats to be able to display a bill or receipt as part of their content. hListing, and hProduct, hAudio are a three examples of Microformats that could use a bill/receipt Microformat.

==Use cases==
Extract details to:
* accountancy/ personal finance software
* expense claim software
* tax return software
* ...

==Related pages==
*[[receipt-examples]]
*[[receipt-formats]]

trade-examples

2007-08-17T18:40:44Z

Lastorset: suggestion moving some content

= What trade is all about =

'''Trade''' is the act of transacting goods between two parties. Transactions may or may not involve the actual exchange of goods, as they may simply represent an order for goods.

This is an exploratory page to document trade examples currently published around the web. Typically, the metadata associated with this content is stored in non-semantic markup and proprietary formats. The purpose of the studies on this page is to serve as background for the design of a simple distributed trade microformat.

:The first part of this page (up to the examples) may fit better on a page simply named "trade". [[User:Lastorset|Leif Arne Storset]] 11:40, 17 Aug 2007 (PDT)

__TOC__

== Why do we need a trade microformat? ==

There are many examples of financial transactions across the web and in desktop applications, including bank statements, purchase receipts, wishlists, [[PersonalFinanceManager | PFM]] applications, etc. A standardized format would facilitate integration between vendors, financial institutions and applications to provide for far more robust financial accounting integration.

There is no published standard means of communicating trade. As such there are many different implementations, and much parsing occurs at both ends of the equation.

=== Example ===

* A bank stores structured transactional metadata in a mainframe.
* A consumer references this information in an online banking web application.
* A consumer tracks their finances using mobile banking.
* A consumer deposits their cash using an ATM.
* A consumer uses their mobile device and NFC technology to purchase items at a storefront.
* A consumer manages their personal goals using an online toolkit.
* A consumer also manages their budget using Quicken.
* A consumer purchases items with their credit card on an e-commerce portal.
* A consumer maintains a list of items they wish to purchase at a future date.
* A small business supplies services to a consumer, emails them an invoice and uses an e-check as payment.

Each of these platforms uses a proprietary means of displaying, structuring and storing the same data. A microformat devoted to trade would provide for easy interoperability between services and applications, facilitating further trade, and simplifying the means of transferring data.

== Participants ==
* [[ClayNewton | Clay Newton]]

== How people trade today ==

=== Current ===
* People transact through a number of electronic forms
** card transactions
** ACH (Automatic Clearing House)
** POS (Point of Sale)
** Check (e-checks)
** Transfers
*** Interbank
*** Intrabank
*** P2P
** ATM
*** Deposits
*** Transfers
*** Withdrawals
*** Purchases
* People use records of these transactions to
** Plan their finances
** Manage their expenses
** Report their PNL
* All of which create collections of records
** Bank statements
** Purchase orders
** wishlists
** Financial Management suites
** Account aggregators
** Budgets
*** Personal
*** Business / Enterprise

=== Human ===
People use a number of means to track their finances in meatspace.

Consumers use their check registers to track finances. Many times consumers will use a spreadsheet for budgeting, or Quicken / MS Money to track expenditures. Many people track their finances using envelopes to represent discretionary spending within specific categories. People are beginning to use tools like Mvelopes and Wesabe to do an electronic equivalent.

Business use robust financial software to manage their finances. Spreadsheets are common, as is the use of financial ledgers.

=== Behavior ===
* TODO: '''notes below are from the behavior boilerplate'''
* What people actually '''do'''. Think empirical evidence, much as in the same way that the scientific method requires gathering of empirical data.
* not:
** what they ''might'' do
** ''should have'' done
** ''would'' do
** Intention/Desire/Want. A common mistake done by folks researching background for formats is to explicitly *ask* folks what they *want* or *prefer*, as opposed to *studying* what they *do*. It is well known among behavioral researchers/surveyors that *asking* people what they *want*, or even *asking* people what they *do*, will give you very different (and worse / less accurate) answers than actually *studying* what they *do* in the real world.
** Formats. Formats are prescriptions for behavior, not behavior itself. For documenting formats, create a *-formats page.

=== Web ===
* TODO: '''notes below are from the WEB boilerplate'''
* The examples MUST focus on examples actually published on the Web, at a publicly available URL, which should be documented along with the example itself on the wiki page.
* Non-web examples are ok *only* for secondary/tertiary consideration, and by no means outweight (no matter what their quantity etc.) the Web examples.
** private files
** paper
** etc.

== Trade Examples ==
=== Bank of America ===
[http://www.bankofamerica.com Bank of America]
==== Deposit Accounts ====
Grouped by Account
* date
** posted
** scheduled
* payee Name
* type
** check image url (front)
** check image url (back)
* status
* amount
* running balance
* fee info
* amount held
* date held

'''Markup:'''
<pre><nowiki>
<tr class="module1bkgd3" id="row17">
<td class="mi" width="6"><a name="skip17"></a><img
src="spacer-image-url" alt="" border="0" width="6"></td>
<td class="mi" width="6">
<div id="fdi17" class="inline"><a href="some-url"
onclick="some-js()" class="linknormal" id="di17"><img
id="rtImg17" src="expand-image-url" alt="Expand this
form to view and enter additional details for this
transaction" align="absmiddle" border="0"></a></div>
</td>
<td class="tp" align="left" width="15%">07/31/2007</td>
<td class="t2" width="36%">
<div id="dld17" class="inline">
<a href="some-url" class="linknormal4" title="BANK
OF AMERICA DES:PAYROLL ID: INDN:NEWTON CLAY CO
ID:1042472499 PPD REF:000478766385121108250007211
00301576107073122" onclick="some-js()">BANK OF
AMERICA DES:PAYROLL ID: INDN:NEWT...</a>
</div>
</td>
<td class="mi" align="center" width="10%"><img
src="deposit-image-url" alt="Deposit"></td>
<td class="mi" align="center" width="10%">
<a onclick="some-js()" href="some-url"
class="linknormal2" title=""><img id="stat_17"
src="status-image-url" alt="Cleared. Select this
link to mark transaction as reconciled." border="0"></a>
</td>
<td class="mi" align="right" nowrap="nowrap"
width="75">
<div class="statementcolmn2"><span
class="textn2">$1,234.56</span></div>
</td>
<td class="module1bkgd4" width="1"><img
src="spacer-image-url" alt="" height="1"
width="1"></td>
<td class="mi" nowrap="nowrap" width="11%">
<div class="statementcolmn2">
<span class="textn2">$8,910.11</span>
</div>
</td>
<td width="10"><img src="spacer-image-url"
alt="" border="0" width="10"></td>
</tr>
</nowiki></pre>

==== Keep the Change ====
* date posted
* # of transactions
** transaction description
** transaction url
** is matched?
** transaction amount
* amount you keep
* to account
* no transfer
==== Card Accounts ====
* date
** transaction
** posted
* description
* amount
* running balance
* card type
* transaction type
* periodic rate
* reference number
* reward
** reward type
** reward url

=== Wells Fargo ===
[http://www.wellsfargo.com Wells Fargo]

enter notes here

=== Citibank ===
[http://www.citibank.com Citibank]

enter notes here

=== ING ===
[http://www.ing.com ING]

enter notes here

=== Amazon.com ===
[http://www.amazon.com Amazon.com]

enter notes here

=== eBay ===
[http://www.ebay.com Ebay]

enter notes here

=== Paypal ===
[http://www.paypal.com Paypal]

enter notes here

=== Quicken ===
[http://www.quicken.com Quicken]
==== Deposits Accounts ====
* post date (PostDt)
* transaction description (TrDesc)
* transaction amount (TrAmt)
* type (TT)
* running balance (RunningBal)

'''Markup:'''
<pre><nowiki><Item>
<PostDt>12/27/2005</PostDt>
<TrDesc>FIREWOOD CAFE-METREON 12/22 CARD #0265 PURCHASE #24388945357670320615609 SAN FRANCISCO, CA</TrDesc>
<TrAmt>-$10.95</TrAmt>
<TT>D</TT>
<RunningBal>$2,916.63</RunningBal>
</Item></nowiki></pre>

=== Quickbooks ===
enter notes here

=== Wesabe ===
[http://www.wesabe.com Wesabe]
<pre><nowiki>
<div id="TRANSACTION-ID" class="txaction_display" >
<div class="merchant_info">
<div class="date"> Friday, March 23rd </div>
<div class="merchant" id="TRANSACTION-ID">
<span class="name"><a href="MERCH-ID">Mojo JOJO</a></span>
<div class="tags">
<span class="rating_text">Rating: <span class="user">User</span></span>
Tags: <a href="TAG-URL">groceries</a>
</div>
</div>
</div>
<div class="balance">
<span class="credit">$988.56</span>
</div>
<div class="amount">
<span class="nowrap">-$7.56</span>
</div>
</div>
</nowiki></pre>

=== Yodlee ===
enter notes here

== See Also ==
* [[trade-brainstorming | Brainstorming trade]]

receipt-examples

2007-08-17T09:43:02Z

Lastorset: /* Google Checkout */ new info on statement reference

= Receipt examples =

=== Contributors ===
*Rob Manson
*Leif Arne Storset

== Real-World Examples ==

=== Bill / Invoice ===

Bills or Invoices are "yet to be paid" items.

Question: Perhaps these examples (yet to be provided) should be moved to a separate page as Bill/Invoice is quite different from Receipt.

: With [[hResume]], I've [[hresume-brainstorming|suggested]] that the subtle difference between actively seeking work and just presenting your resume be a case of including [[hlisting]] markup.
: With bills vs invoices, it may turn out that the content found within would be identical, and it might just be a case of putting in a class flag to indicate whether the presented document has been paid for or not.
: [[User:SignpostMarv|SignpostMarv]] 12:55, 21 Jul 2007 (PDT)

::I think a class flag is a great idea, but I don't believe we have any samples for invoices. However, if we look at order review vs. order summary rather than invoices vs. receipts, the payment flag does become relevant in many of the sampled online stores.
::How would such a flag be implemented?
::*<code><nowiki><div class="hreceipt unpaid"/"hreceipt paid">...</nowiki></code>
::*<code><nowiki><div class="hreceipt" title="paid">...</div></nowiki></code>
::[[User:Lastorset|Lastorset]] 14:55, 16 Aug 2007 (PDT)

=== Receipts ===

Receipts are post-purchase items.

==== Amazon ====
* [http://mobileonlinebusiness.com.au/uf/receipt/Amazon.com-Vieworder-anon.htm Example]
* contains:
**<del>email address</del> (could not find in examples)
**date of order
**order id
**shipments
***shipping estimate
***delivery estimate
***shipping address
***shipping speed
***shipping preference (item grouping)
***items
****quantity
****seller
****price
****item information
**payment
***card type
***last 5 digits
***expiration date
***billing address
***subtotal
***shipping and handling price
***total before tax
***tax
***grand total
**<del>discount price</del> (could not find in examples)
* Little semantic HTML of interest, except an anchor with id "payment-info"

Notes:
*Supports multiple shipments.
*Supports one seller per item.
*Displays shipping and delivery estimate.
*Offers item grouping preference.
*Gift options.

==== Skype ====

===== Skype Phone =====
*[[receipt-example-skype-phone|example source code]]
*[http://mobileonlinebusiness.com.au/uf/receipt/Skype-order-history.html Skype order history]

* Shipping Address
* date in dd/mm/yyyy format
* Order number in nnnn-nnnnnnn-nnn format
* Reference (was blank in example, presumed to appear on bank statement for this transaction)
* Items
** Quantity
** Description
** Price
** Total
** VAT (tax) %
* Payment
** subtotal ("total")
** shipping cost
** grand total ("total (gross)")
** total (VAT excluded)
** VAT (amount)
* Chosen payment method: "Your payment method is: Credit card"
* Legal blurb

Semantic HTML:
* Order resume class="order-listing"
* Each item class="row"
* All totals rows class="totals-row" except grand total class="grandtotal-row"

Notes:
*Displayed credit-card-statement reference (presumably).

==== Internet banking transaction receipts ====
===== Example 1 =====
<pre><nowiki>
receipt number
date
time
receipt type (e.g. TRANSFER BETWEEN MY ACCOUNTS)
transfer from
transfer to
amount
description
information/comment
</nowiki></pre>

==== Digital product purchase receipts ====
===== Example 1 : Software =====
<pre><nowiki>
receipt title/type
order/receipt number
seller's details
sold by (hCard candidate)
org
adr
tax number (VAT in this example)
tax id (Federal Tax ID)
buyer's details
buyer (hCard candidate)
name
org
street-address
locality
region
postal-code
country-name
tel
email
credit card number (PAN truncated - with type)
item list
product code
name
comments
price
delivery method
quantity
total in selected currency
total in sellers currency
total (sum of item list totals)
processing fee
grand total (final amount charged)
information (caveats and tax info)
permalink
</nowiki></pre>

===== Example 2 : SSL certificate =====
<pre><nowiki>
receipt title/type
seller (hCard candidate)
org
street-address
locality
region
postal-code
purchase information
order id
product name
domain name
validity period
number of licenses
card number (PAN truncated)
amount (with selected currency)
</nowiki></pre>

==== Physical product purchase receipts ====
===== Example 1 : Computer hardware =====
<pre><nowiki>
receipt title/type
seller's name (hCard candidate)
seller's URL (hCard candidate)
invoice id
org govt reference (ABN - Australian Business Number)
date
seller details (hCard candidate)
street-address
locality
region
postal-code
buyer (hCard candidate)
fn
billing address
street-address
locality
region
postal-code
delivery address
street-address
locality
region
postal-code
phone
item list
item
description
amount
quantity
product url
total
delivery cost
total excluding tax
tax (GST - Goods and Service Tax)
total including tax
</nowiki></pre>

==== Service purchase receipts ====
===== Example 1 : Online subscription =====
<pre><nowiki>
seller's details (hCard candidate)
org
street-address
locality
region
postal-code
country-name
buyer's details (hCard candidate)
fn
street-address
locality
region
postal-code
phone
date
receipt id
item list
product description
quantity
rate (per unit)
price
sub total
amount paid
balance due
information
transaction id
</nowiki></pre>

===== Example 2 : Co-location =====
<pre><nowiki>
receipt title/type
sellers details (hCard candidate)
org
url
phone
message
receipt number
date
amount
information
</nowiki></pre>

==== A1Books ====
[http://mobileonlinebusiness.com.au/uf/receipt/A1Books-Sales-Order-anon.htm Example]

*vendor
**name
**fax
*date
*order number
*shipping address
*billing address
*items
**description
**list price
**sale price
**quantity
**amount
*subtotal
*shipping
*total
**quantity
**amount
*account information
**phone
**e-mail
*payment
**method
**last four digits

No semantic HTML.

Notes:
*Supports one seller per item.
*Does not display tax.

==== Barnes&Noble ====
[http://mobileonlinebusiness.com.au/uf/receipt/BarnesAndNoble.com-receipt.anon.tidied.htm Example]

*date
*shipping address
*billing address
*payment
**method
**last 4 digits
**exp. date
**charge
*savings on shipping
*order no.
*delivery option
*items
**description: title, author, ISBN, price
**qty
**gift options: wrap, message
**total price
*shipment subtotal
*shipping cost
*tax
*shipment total (seems to account for orders requiring multiple shipments)
*order total

Semantic HTML:
*receiptOrderNumbers
*receiptOrderPlacedOn
*orderInformation
**shippingAddress
**billingAddress
**paymentInformation
*shippingSelections
*showProducts
**reviewTable
***qtyValuePosition
***reviewGiftOptions
*reviewTotalsDisplay
**reviewTotalsSummary
**reviewTotalsNote
**reviewTotalsBreakdown
*reviewTotalsSummary
**reviewGrandTotal
*reviewCreditCardCharged
*review

The semantic class names found are a good start, although the "review" part appears to be context-specific (reviewing an order). Additionally, the implied hierarchy in names such as "reviewTotalsSummary" and "receiptOrderPlacedOn" is probably unnecessary for our purposes.

Notes:
*Supports multiple shipments.
*Gift options.
*Explicitly stated credit-card charge.

==== Facebook ====
[http://mobileonlinebusiness.com.au/uf/receipt/Facebook-gift-receipt.html Example]

*purchase total
*items (informal description of two items, including quantity)
*recipient name
*order id
*billed-to name

No relevant semantic HTML.

Notes:
*Quite minimal and informal receipt. Good example of how a microformat would preserve human readability and informal style while enabling machine reading.

==== Google Checkout ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Google-Checkout-e-mail-receipt.tidied.html Example email receipt]
*[http://mobileonlinebusiness.com.au/uf/receipt/Google-Checkout-Order-Receipt_DVD-Empire.tidied.htm Example web receipt]

*vendor address
*shipping address
*date
*order id
*items
**shipping status ("Not yet shipped", etc.)
**qty.
**description
**price
*shipping cost
*tax
*total
*order history (placed, received, charged, shipped) (web receipt only)
**credit-card statement reference (only after the charge has been made)
*payment info (web receipt only)
**card type
**last 4 digits
**exp. date
**cardholder address
*permalink

Semantic HTML:
*taxRow
**taxIdentifier
**taxAmount
*totalAmount

Notes:
*Explicit seller address (one per order).
*Current shipping status of each item.
*E-mail receipt has permalink.
*Order history (date placed, received, charged, shipped).
*Displayed credit-card statement reference only after card was charged.

==== iTunes ====
*[http://mobileonlinebusiness.com.au/uf/receipt/iTunes-receipt-e-mail.html iTunes e-mail receipt]

*billing address
*order no.
*receipt date
*order total
*card
**type
**last 4 digits
*item
**item no.
**description (including link to write a review)
**unit price
*subtotal
*tax

No relevant semantic HTML.

Notes:
*No quantity information.

==== Longs/FujiFilm ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Longs-Fujifilm-photo-receipt.html Longs/Fujifilm e-mail receipt]

*order no.
*payment info
**method (COD, credit card, etc.)
*customer address
*pickup address
*items
**name
**qty.
**description
**price
**line item subtotal
*order items total
*tax
*order total

Semantic HTML:
*payment-heading

Notes:
*No order date; has pick-up date instead.
*Has pickup address rather than shipping address.

==== Mobivox/PayPal ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Mobivox-PayPal.htm Mobivox/PayPal receipt]
*[http://mobileonlinebusiness.com.au/uf/receipt/Mobivox-PayPal-printable.htm Mobivox/PayPal printable receipt]

*seller address
*receipt id
*date of order
*items
**description
**item option (not quite sure what this is for)
**unit price
**qty
**total
*subtotal
*tax
*total amount
*payment info
**method
**last 4 digits
**charge
**appears on bill/statement as "MOBIVOXCORP"
*buyer contact

Relevant semantic HTML:
*order-summary
**cart
***(unnamed tr)
****item-name
****item-total
****item-option (not quite sure what this is for)
**subtotal
**totals-value
**totals-currency
**purchase-summary
***summary-total
****price-total
****price-currency
*funding-mix
**payment-type
**amount
**ccStatement
*contact-information (contains hCard microformat)

This semantic HTML is the most complete and well-thought-out I've seen in this analysis. It even makes use of the fieldset element in forms, something I've never seen before.[[User:Lastorset|Lastorset]] 16:21, 25 Jul 2007 (PDT)

Microformats used:
*hCard (non-compliant due to missing formatted name): buyer contact info

Notes:
*Explicitly stated credit-card charge.
*Displayed credit-card-statement reference.
*Explicitly displayed seller address (one seller per order).

==== Symantec ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Symantec-reminder-e-mail.html Symantec e-mail reminder]

*buyer name
*date
*payment method
*last 4 digits
*appears on statement as "DR *Symantec"
*items
**qty
**product name
**platform
**delivery method
**price
*subtotal
*grand total
*permalink

No relevant semantic HTML

Notes:
*As an e-mail "order reminder" rather than a receipt, this was slightly more informal than the other samples. As such there was
**no order id
**a permalink
*"Delivery method" could be download or ship.

== Analysis ==

=== Analysis of Bills ===

=== Analysis of Receipts ===
Analyzed using spreadsheet available at http://spreadsheets.google.com/pub?key=pAGYQr-yhoUh6sl5NaqEVZw. E-mail <code>leifarne at storset dot net</code> if you want edit permissions.

====Addresses====
All receipts have hCard candidates (i. e. name and/or address) of at least one of these types:
*buyer/customer
*seller
*shipping
*billing
*pickup

====Shipping====
These vendors supported '''multiple shipments''':
*Amazon.com
*Barnes&Noble
**Also displayed shipment subtotals.

These displayed '''shipping method/speed''':
*Amazon.com
*Barnes&Noble
*Symantec

These displayed '''gift''' choices:
*Amazon.com
*Barnes&Noble

For most vendors, each item had the following information:
*description
*quantity
*unit price
*line total
Google Checkout additionally provided shipping status.

====Payment information====
Most vendors displayed:
*payment method (credit card or COD, card type)
*last 4 or 5 digits of credit card
*expiration date of credit card

Some also displayed
*reference on credit-card statement ("This order will appear as ABCD0001234 on your credit-card statement.")
*the credit-card charge itself

====Totals====
Most displayed:
*subtotal
*shipping and handling cost (if applicable)
*tax
*grand total

Some also displayed:
*total before tax
*total quantity (only A1Books)

====Marketplace====
Most receipt formats are for one seller only. The following support different sellers:
*A1Books: per item
*Amazon.com: per item
*Google Checkout: per receipt
*PayPal: per receipt

====Other properties====
Almost all receipts had
*order date
**Facebook had no date.
**Longs/FujiFilm had pick-up date instead.
*order id
**Symantec did not mention order id.

Other interesting items:
*permalink (on most e-mail receipts)
*link to purchase history
*order history (Google Checkout):
**placed
**received
**charged
**shipped

== Existing Practices ==

Listed below is an overview of existing patterns and practices found in the wild for bill and receipt data.

===Summary of common patterns discovered===

===Other attempts to solve The Problem===
For paper receipts, [http://www.neatreceipts.com/ NeatReceipts Scanalizer] offers a heuristic-based solution.

== Proposal ==

== See Also ==
* [[receipt]]
* http://en.wikipedia.org/wiki/Receipt

receipt-formats

2007-08-17T01:10:28Z

Lastorset: /* Open Financial Exchange */ Wikipedia link

receipt-formats

2007-08-17T01:07:26Z

Lastorset: added contributor section

receipt-examples

2007-08-17T01:07:07Z

Lastorset: Adjusted start of page a bit: changed title, added myself as a contributor

= Receipt examples =

=== Contributors ===
*Rob Manson
*Leif Arne Storset

== Real-World Examples ==

=== Bill / Invoice ===

Bills or Invoices are "yet to be paid" items.

Question: Perhaps these examples (yet to be provided) should be moved to a separate page as Bill/Invoice is quite different from Receipt.

: With [[hResume]], I've [[hresume-brainstorming|suggested]] that the subtle difference between actively seeking work and just presenting your resume be a case of including [[hlisting]] markup.
: With bills vs invoices, it may turn out that the content found within would be identical, and it might just be a case of putting in a class flag to indicate whether the presented document has been paid for or not.
: [[User:SignpostMarv|SignpostMarv]] 12:55, 21 Jul 2007 (PDT)

::I think a class flag is a great idea, but I don't believe we have any samples for invoices. However, if we look at order review vs. order summary rather than invoices vs. receipts, the payment flag does become relevant in many of the sampled online stores.
::How would such a flag be implemented?
::*<code><nowiki><div class="hreceipt unpaid"/"hreceipt paid">...</nowiki></code>
::*<code><nowiki><div class="hreceipt" title="paid">...</div></nowiki></code>
::[[User:Lastorset|Lastorset]] 14:55, 16 Aug 2007 (PDT)

=== Receipts ===

Receipts are post-purchase items.

==== Amazon ====
* [http://mobileonlinebusiness.com.au/uf/receipt/Amazon.com-Vieworder-anon.htm Example]
* contains:
**<del>email address</del> (could not find in examples)
**date of order
**order id
**shipments
***shipping estimate
***delivery estimate
***shipping address
***shipping speed
***shipping preference (item grouping)
***items
****quantity
****seller
****price
****item information
**payment
***card type
***last 5 digits
***expiration date
***billing address
***subtotal
***shipping and handling price
***total before tax
***tax
***grand total
**<del>discount price</del> (could not find in examples)
* Little semantic HTML of interest, except an anchor with id "payment-info"

Notes:
*Supports multiple shipments.
*Supports one seller per item.
*Displays shipping and delivery estimate.
*Offers item grouping preference.
*Gift options.

==== Skype ====

===== Skype Phone =====
*[[receipt-example-skype-phone|example source code]]
*[http://mobileonlinebusiness.com.au/uf/receipt/Skype-order-history.html Skype order history]

* Shipping Address
* date in dd/mm/yyyy format
* Order number in nnnn-nnnnnnn-nnn format
* Reference (was blank in example, presumed to appear on bank statement for this transaction)
* Items
** Quantity
** Description
** Price
** Total
** VAT (tax) %
* Payment
** subtotal ("total")
** shipping cost
** grand total ("total (gross)")
** total (VAT excluded)
** VAT (amount)
* Chosen payment method: "Your payment method is: Credit card"
* Legal blurb

Semantic HTML:
* Order resume class="order-listing"
* Each item class="row"
* All totals rows class="totals-row" except grand total class="grandtotal-row"

Notes:
*Displayed credit-card-statement reference (presumably).

==== Internet banking transaction receipts ====
===== Example 1 =====
<pre><nowiki>
receipt number
date
time
receipt type (e.g. TRANSFER BETWEEN MY ACCOUNTS)
transfer from
transfer to
amount
description
information/comment
</nowiki></pre>

==== Digital product purchase receipts ====
===== Example 1 : Software =====
<pre><nowiki>
receipt title/type
order/receipt number
seller's details
sold by (hCard candidate)
org
adr
tax number (VAT in this example)
tax id (Federal Tax ID)
buyer's details
buyer (hCard candidate)
name
org
street-address
locality
region
postal-code
country-name
tel
email
credit card number (PAN truncated - with type)
item list
product code
name
comments
price
delivery method
quantity
total in selected currency
total in sellers currency
total (sum of item list totals)
processing fee
grand total (final amount charged)
information (caveats and tax info)
permalink
</nowiki></pre>

===== Example 2 : SSL certificate =====
<pre><nowiki>
receipt title/type
seller (hCard candidate)
org
street-address
locality
region
postal-code
purchase information
order id
product name
domain name
validity period
number of licenses
card number (PAN truncated)
amount (with selected currency)
</nowiki></pre>

==== Physical product purchase receipts ====
===== Example 1 : Computer hardware =====
<pre><nowiki>
receipt title/type
seller's name (hCard candidate)
seller's URL (hCard candidate)
invoice id
org govt reference (ABN - Australian Business Number)
date
seller details (hCard candidate)
street-address
locality
region
postal-code
buyer (hCard candidate)
fn
billing address
street-address
locality
region
postal-code
delivery address
street-address
locality
region
postal-code
phone
item list
item
description
amount
quantity
product url
total
delivery cost
total excluding tax
tax (GST - Goods and Service Tax)
total including tax
</nowiki></pre>

==== Service purchase receipts ====
===== Example 1 : Online subscription =====
<pre><nowiki>
seller's details (hCard candidate)
org
street-address
locality
region
postal-code
country-name
buyer's details (hCard candidate)
fn
street-address
locality
region
postal-code
phone
date
receipt id
item list
product description
quantity
rate (per unit)
price
sub total
amount paid
balance due
information
transaction id
</nowiki></pre>

===== Example 2 : Co-location =====
<pre><nowiki>
receipt title/type
sellers details (hCard candidate)
org
url
phone
message
receipt number
date
amount
information
</nowiki></pre>

==== A1Books ====
[http://mobileonlinebusiness.com.au/uf/receipt/A1Books-Sales-Order-anon.htm Example]

*vendor
**name
**fax
*date
*order number
*shipping address
*billing address
*items
**description
**list price
**sale price
**quantity
**amount
*subtotal
*shipping
*total
**quantity
**amount
*account information
**phone
**e-mail
*payment
**method
**last four digits

No semantic HTML.

Notes:
*Supports one seller per item.
*Does not display tax.

==== Barnes&Noble ====
[http://mobileonlinebusiness.com.au/uf/receipt/BarnesAndNoble.com-receipt.anon.tidied.htm Example]

*date
*shipping address
*billing address
*payment
**method
**last 4 digits
**exp. date
**charge
*savings on shipping
*order no.
*delivery option
*items
**description: title, author, ISBN, price
**qty
**gift options: wrap, message
**total price
*shipment subtotal
*shipping cost
*tax
*shipment total (seems to account for orders requiring multiple shipments)
*order total

Semantic HTML:
*receiptOrderNumbers
*receiptOrderPlacedOn
*orderInformation
**shippingAddress
**billingAddress
**paymentInformation
*shippingSelections
*showProducts
**reviewTable
***qtyValuePosition
***reviewGiftOptions
*reviewTotalsDisplay
**reviewTotalsSummary
**reviewTotalsNote
**reviewTotalsBreakdown
*reviewTotalsSummary
**reviewGrandTotal
*reviewCreditCardCharged
*review

The semantic class names found are a good start, although the "review" part appears to be context-specific (reviewing an order). Additionally, the implied hierarchy in names such as "reviewTotalsSummary" and "receiptOrderPlacedOn" is probably unnecessary for our purposes.

Notes:
*Supports multiple shipments.
*Gift options.
*Explicitly stated credit-card charge.

==== Facebook ====
[http://mobileonlinebusiness.com.au/uf/receipt/Facebook-gift-receipt.html Example]

*purchase total
*items (informal description of two items, including quantity)
*recipient name
*order id
*billed-to name

No relevant semantic HTML.

Notes:
*Quite minimal and informal receipt. Good example of how a microformat would preserve human readability and informal style while enabling machine reading.

==== Google Checkout ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Google-Checkout-e-mail-receipt.tidied.html Example email receipt]
*[http://mobileonlinebusiness.com.au/uf/receipt/Google-Checkout-Order-Receipt_DVD-Empire.tidied.htm Example web receipt]

*vendor address
*shipping address
*date
*order id
*items
**shipping status ("Not yet shipped", etc.)
**qty.
**description
**price
*shipping cost
*tax
*total
*order history (placed, received, charged, shipped) (web receipt only)
*payment info (web receipt only)
**card type
**last 4 digits
**exp. date
**cardholder address
*permalink

Semantic HTML:
*taxRow
**taxIdentifier
**taxAmount
*totalAmount

Notes:
*Explicit seller address (one per order).
*Current shipping status of each item.
*E-mail receipt has permalink.
*Order history (date placed, received, charged, shipped).

==== iTunes ====
*[http://mobileonlinebusiness.com.au/uf/receipt/iTunes-receipt-e-mail.html iTunes e-mail receipt]

*billing address
*order no.
*receipt date
*order total
*card
**type
**last 4 digits
*item
**item no.
**description (including link to write a review)
**unit price
*subtotal
*tax

No relevant semantic HTML.

Notes:
*No quantity information.

==== Longs/FujiFilm ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Longs-Fujifilm-photo-receipt.html Longs/Fujifilm e-mail receipt]

*order no.
*payment info
**method (COD, credit card, etc.)
*customer address
*pickup address
*items
**name
**qty.
**description
**price
**line item subtotal
*order items total
*tax
*order total

Semantic HTML:
*payment-heading

Notes:
*No order date; has pick-up date instead.
*Has pickup address rather than shipping address.

==== Mobivox/PayPal ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Mobivox-PayPal.htm Mobivox/PayPal receipt]
*[http://mobileonlinebusiness.com.au/uf/receipt/Mobivox-PayPal-printable.htm Mobivox/PayPal printable receipt]

*seller address
*receipt id
*date of order
*items
**description
**item option (not quite sure what this is for)
**unit price
**qty
**total
*subtotal
*tax
*total amount
*payment info
**method
**last 4 digits
**charge
**appears on bill/statement as "MOBIVOXCORP"
*buyer contact

Relevant semantic HTML:
*order-summary
**cart
***(unnamed tr)
****item-name
****item-total
****item-option (not quite sure what this is for)
**subtotal
**totals-value
**totals-currency
**purchase-summary
***summary-total
****price-total
****price-currency
*funding-mix
**payment-type
**amount
**ccStatement
*contact-information (contains hCard microformat)

This semantic HTML is the most complete and well-thought-out I've seen in this analysis. It even makes use of the fieldset element in forms, something I've never seen before.[[User:Lastorset|Lastorset]] 16:21, 25 Jul 2007 (PDT)

Microformats used:
*hCard (non-compliant due to missing formatted name): buyer contact info

Notes:
*Explicitly stated credit-card charge.
*Displayed credit-card-statement reference.
*Explicitly displayed seller address (one seller per order).

==== Symantec ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Symantec-reminder-e-mail.html Symantec e-mail reminder]

*buyer name
*date
*payment method
*last 4 digits
*appears on statement as "DR *Symantec"
*items
**qty
**product name
**platform
**delivery method
**price
*subtotal
*grand total
*permalink

No relevant semantic HTML

Notes:
*As an e-mail "order reminder" rather than a receipt, this was slightly more informal than the other samples. As such there was
**no order id
**a permalink
*"Delivery method" could be download or ship.

== Analysis ==

=== Analysis of Bills ===

=== Analysis of Receipts ===
Analyzed using spreadsheet available at http://spreadsheets.google.com/pub?key=pAGYQr-yhoUh6sl5NaqEVZw. E-mail <code>leifarne at storset dot net</code> if you want edit permissions.

====Addresses====
All receipts have hCard candidates (i. e. name and/or address) of at least one of these types:
*buyer/customer
*seller
*shipping
*billing
*pickup

====Shipping====
These vendors supported '''multiple shipments''':
*Amazon.com
*Barnes&Noble
**Also displayed shipment subtotals.

These displayed '''shipping method/speed''':
*Amazon.com
*Barnes&Noble
*Symantec

These displayed '''gift''' choices:
*Amazon.com
*Barnes&Noble

For most vendors, each item had the following information:
*description
*quantity
*unit price
*line total
Google Checkout additionally provided shipping status.

====Payment information====
Most vendors displayed:
*payment method (credit card or COD, card type)
*last 4 or 5 digits of credit card
*expiration date of credit card

Some also displayed
*reference on credit-card statement ("This order will appear as ABCD0001234 on your credit-card statement.")
*the credit-card charge itself

====Totals====
Most displayed:
*subtotal
*shipping and handling cost (if applicable)
*tax
*grand total

Some also displayed:
*total before tax
*total quantity (only A1Books)

====Marketplace====
Most receipt formats are for one seller only. The following support different sellers:
*A1Books: per item
*Amazon.com: per item
*Google Checkout: per receipt
*PayPal: per receipt

====Other properties====
Almost all receipts had
*order date
**Facebook had no date.
**Longs/FujiFilm had pick-up date instead.
*order id
**Symantec did not mention order id.

Other interesting items:
*permalink (on most e-mail receipts)
*link to purchase history
*order history (Google Checkout):
**placed
**received
**charged
**shipped

== Existing Practices ==

Listed below is an overview of existing patterns and practices found in the wild for bill and receipt data.

===Summary of common patterns discovered===

===Other attempts to solve The Problem===
For paper receipts, [http://www.neatreceipts.com/ NeatReceipts Scanalizer] offers a heuristic-based solution.

== Proposal ==

== See Also ==
* [[receipt]]
* http://en.wikipedia.org/wiki/Receipt

receipt-formats

2007-08-17T01:04:58Z

Lastorset:

=Existing receipt formats=
==Quicken Interchange Format (QIF)==
Quicken Interchange Format (QIF) is an open specification for reading and writing financial data to media (i.e. files). It's unclear what invoice/receipt support is available, but invoice accounts are mentioned in the Wikipedia article. Further analysis needed.

===Further reading===
*[http://en.wikipedia.org/wiki/QIF Wikipedia article]

==Open Financial Exchange==
Analysis needed.
== See Also ==
* [[receipt]]

receipt-formats

2007-08-17T01:03:25Z

Lastorset:

==Quicken Interchange Format (QIF)==
Quicken Interchange Format (QIF) is an open specification for reading and writing financial data to media (i.e. files). It's unclear what invoice/receipt support is available, but invoice accounts are mentioned in the Wikipedia article. Further analysis needed.

===Further reading===
*[http://en.wikipedia.org/wiki/QIF Wikipedia article]

==Open Financial Exchange==
Analysis needed.
== See Also ==
* [[receipt]]

receipt-examples

2007-08-17T00:56:35Z

Lastorset: /* Analysis of Receipts */ linked to spreadsheet analysis

= Receipt =

Overview of Receipt exploratory discussion goes here...

== Authors ==

=== Contributors ===
Rob Manson

== Real-World Examples ==

=== Bill / Invoice ===

Bills or Invoices are "yet to be paid" items.

Question: Perhaps these examples (yet to be provided) should be moved to a separate page as Bill/Invoice is quite different from Receipt.

: With [[hResume]], I've [[hresume-brainstorming|suggested]] that the subtle difference between actively seeking work and just presenting your resume be a case of including [[hlisting]] markup.
: With bills vs invoices, it may turn out that the content found within would be identical, and it might just be a case of putting in a class flag to indicate whether the presented document has been paid for or not.
: [[User:SignpostMarv|SignpostMarv]] 12:55, 21 Jul 2007 (PDT)

::I think a class flag is a great idea, but I don't believe we have any samples for invoices. However, if we look at order review vs. order summary rather than invoices vs. receipts, the payment flag does become relevant in many of the sampled online stores.
::How would such a flag be implemented?
::*<code><nowiki><div class="hreceipt unpaid"/"hreceipt paid">...</nowiki></code>
::*<code><nowiki><div class="hreceipt" title="paid">...</div></nowiki></code>
::[[User:Lastorset|Lastorset]] 14:55, 16 Aug 2007 (PDT)

=== Receipts ===

Receipts are post-purchase items.

==== Amazon ====
* [http://mobileonlinebusiness.com.au/uf/receipt/Amazon.com-Vieworder-anon.htm Example]
* contains:
**<del>email address</del> (could not find in examples)
**date of order
**order id
**shipments
***shipping estimate
***delivery estimate
***shipping address
***shipping speed
***shipping preference (item grouping)
***items
****quantity
****seller
****price
****item information
**payment
***card type
***last 5 digits
***expiration date
***billing address
***subtotal
***shipping and handling price
***total before tax
***tax
***grand total
**<del>discount price</del> (could not find in examples)
* Little semantic HTML of interest, except an anchor with id "payment-info"

Notes:
*Supports multiple shipments.
*Supports one seller per item.
*Displays shipping and delivery estimate.
*Offers item grouping preference.
*Gift options.

==== Skype ====

===== Skype Phone =====
*[[receipt-example-skype-phone|example source code]]
*[http://mobileonlinebusiness.com.au/uf/receipt/Skype-order-history.html Skype order history]

* Shipping Address
* date in dd/mm/yyyy format
* Order number in nnnn-nnnnnnn-nnn format
* Reference (was blank in example, presumed to appear on bank statement for this transaction)
* Items
** Quantity
** Description
** Price
** Total
** VAT (tax) %
* Payment
** subtotal ("total")
** shipping cost
** grand total ("total (gross)")
** total (VAT excluded)
** VAT (amount)
* Chosen payment method: "Your payment method is: Credit card"
* Legal blurb

Semantic HTML:
* Order resume class="order-listing"
* Each item class="row"
* All totals rows class="totals-row" except grand total class="grandtotal-row"

Notes:
*Displayed credit-card-statement reference (presumably).

==== Internet banking transaction receipts ====
===== Example 1 =====
<pre><nowiki>
receipt number
date
time
receipt type (e.g. TRANSFER BETWEEN MY ACCOUNTS)
transfer from
transfer to
amount
description
information/comment
</nowiki></pre>

==== Digital product purchase receipts ====
===== Example 1 : Software =====
<pre><nowiki>
receipt title/type
order/receipt number
seller's details
sold by (hCard candidate)
org
adr
tax number (VAT in this example)
tax id (Federal Tax ID)
buyer's details
buyer (hCard candidate)
name
org
street-address
locality
region
postal-code
country-name
tel
email
credit card number (PAN truncated - with type)
item list
product code
name
comments
price
delivery method
quantity
total in selected currency
total in sellers currency
total (sum of item list totals)
processing fee
grand total (final amount charged)
information (caveats and tax info)
permalink
</nowiki></pre>

===== Example 2 : SSL certificate =====
<pre><nowiki>
receipt title/type
seller (hCard candidate)
org
street-address
locality
region
postal-code
purchase information
order id
product name
domain name
validity period
number of licenses
card number (PAN truncated)
amount (with selected currency)
</nowiki></pre>

==== Physical product purchase receipts ====
===== Example 1 : Computer hardware =====
<pre><nowiki>
receipt title/type
seller's name (hCard candidate)
seller's URL (hCard candidate)
invoice id
org govt reference (ABN - Australian Business Number)
date
seller details (hCard candidate)
street-address
locality
region
postal-code
buyer (hCard candidate)
fn
billing address
street-address
locality
region
postal-code
delivery address
street-address
locality
region
postal-code
phone
item list
item
description
amount
quantity
product url
total
delivery cost
total excluding tax
tax (GST - Goods and Service Tax)
total including tax
</nowiki></pre>

==== Service purchase receipts ====
===== Example 1 : Online subscription =====
<pre><nowiki>
seller's details (hCard candidate)
org
street-address
locality
region
postal-code
country-name
buyer's details (hCard candidate)
fn
street-address
locality
region
postal-code
phone
date
receipt id
item list
product description
quantity
rate (per unit)
price
sub total
amount paid
balance due
information
transaction id
</nowiki></pre>

===== Example 2 : Co-location =====
<pre><nowiki>
receipt title/type
sellers details (hCard candidate)
org
url
phone
message
receipt number
date
amount
information
</nowiki></pre>

==== A1Books ====
[http://mobileonlinebusiness.com.au/uf/receipt/A1Books-Sales-Order-anon.htm Example]

*vendor
**name
**fax
*date
*order number
*shipping address
*billing address
*items
**description
**list price
**sale price
**quantity
**amount
*subtotal
*shipping
*total
**quantity
**amount
*account information
**phone
**e-mail
*payment
**method
**last four digits

No semantic HTML.

Notes:
*Supports one seller per item.
*Does not display tax.

==== Barnes&Noble ====
[http://mobileonlinebusiness.com.au/uf/receipt/BarnesAndNoble.com-receipt.anon.tidied.htm Example]

*date
*shipping address
*billing address
*payment
**method
**last 4 digits
**exp. date
**charge
*savings on shipping
*order no.
*delivery option
*items
**description: title, author, ISBN, price
**qty
**gift options: wrap, message
**total price
*shipment subtotal
*shipping cost
*tax
*shipment total (seems to account for orders requiring multiple shipments)
*order total

Semantic HTML:
*receiptOrderNumbers
*receiptOrderPlacedOn
*orderInformation
**shippingAddress
**billingAddress
**paymentInformation
*shippingSelections
*showProducts
**reviewTable
***qtyValuePosition
***reviewGiftOptions
*reviewTotalsDisplay
**reviewTotalsSummary
**reviewTotalsNote
**reviewTotalsBreakdown
*reviewTotalsSummary
**reviewGrandTotal
*reviewCreditCardCharged
*review

The semantic class names found are a good start, although the "review" part appears to be context-specific (reviewing an order). Additionally, the implied hierarchy in names such as "reviewTotalsSummary" and "receiptOrderPlacedOn" is probably unnecessary for our purposes.

Notes:
*Supports multiple shipments.
*Gift options.
*Explicitly stated credit-card charge.

==== Facebook ====
[http://mobileonlinebusiness.com.au/uf/receipt/Facebook-gift-receipt.html Example]

*purchase total
*items (informal description of two items, including quantity)
*recipient name
*order id
*billed-to name

No relevant semantic HTML.

Notes:
*Quite minimal and informal receipt. Good example of how a microformat would preserve human readability and informal style while enabling machine reading.

==== Google Checkout ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Google-Checkout-e-mail-receipt.tidied.html Example email receipt]
*[http://mobileonlinebusiness.com.au/uf/receipt/Google-Checkout-Order-Receipt_DVD-Empire.tidied.htm Example web receipt]

*vendor address
*shipping address
*date
*order id
*items
**shipping status ("Not yet shipped", etc.)
**qty.
**description
**price
*shipping cost
*tax
*total
*order history (placed, received, charged, shipped) (web receipt only)
*payment info (web receipt only)
**card type
**last 4 digits
**exp. date
**cardholder address
*permalink

Semantic HTML:
*taxRow
**taxIdentifier
**taxAmount
*totalAmount

Notes:
*Explicit seller address (one per order).
*Current shipping status of each item.
*E-mail receipt has permalink.
*Order history (date placed, received, charged, shipped).

==== iTunes ====
*[http://mobileonlinebusiness.com.au/uf/receipt/iTunes-receipt-e-mail.html iTunes e-mail receipt]

*billing address
*order no.
*receipt date
*order total
*card
**type
**last 4 digits
*item
**item no.
**description (including link to write a review)
**unit price
*subtotal
*tax

No relevant semantic HTML.

Notes:
*No quantity information.

==== Longs/FujiFilm ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Longs-Fujifilm-photo-receipt.html Longs/Fujifilm e-mail receipt]

*order no.
*payment info
**method (COD, credit card, etc.)
*customer address
*pickup address
*items
**name
**qty.
**description
**price
**line item subtotal
*order items total
*tax
*order total

Semantic HTML:
*payment-heading

Notes:
*No order date; has pick-up date instead.
*Has pickup address rather than shipping address.

==== Mobivox/PayPal ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Mobivox-PayPal.htm Mobivox/PayPal receipt]
*[http://mobileonlinebusiness.com.au/uf/receipt/Mobivox-PayPal-printable.htm Mobivox/PayPal printable receipt]

*seller address
*receipt id
*date of order
*items
**description
**item option (not quite sure what this is for)
**unit price
**qty
**total
*subtotal
*tax
*total amount
*payment info
**method
**last 4 digits
**charge
**appears on bill/statement as "MOBIVOXCORP"
*buyer contact

Relevant semantic HTML:
*order-summary
**cart
***(unnamed tr)
****item-name
****item-total
****item-option (not quite sure what this is for)
**subtotal
**totals-value
**totals-currency
**purchase-summary
***summary-total
****price-total
****price-currency
*funding-mix
**payment-type
**amount
**ccStatement
*contact-information (contains hCard microformat)

This semantic HTML is the most complete and well-thought-out I've seen in this analysis. It even makes use of the fieldset element in forms, something I've never seen before.[[User:Lastorset|Lastorset]] 16:21, 25 Jul 2007 (PDT)

Microformats used:
*hCard (non-compliant due to missing formatted name): buyer contact info

Notes:
*Explicitly stated credit-card charge.
*Displayed credit-card-statement reference.
*Explicitly displayed seller address (one seller per order).

==== Symantec ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Symantec-reminder-e-mail.html Symantec e-mail reminder]

*buyer name
*date
*payment method
*last 4 digits
*appears on statement as "DR *Symantec"
*items
**qty
**product name
**platform
**delivery method
**price
*subtotal
*grand total
*permalink

No relevant semantic HTML

Notes:
*As an e-mail "order reminder" rather than a receipt, this was slightly more informal than the other samples. As such there was
**no order id
**a permalink
*"Delivery method" could be download or ship.

== Analysis ==

=== Analysis of Bills ===

=== Analysis of Receipts ===
Analyzed using spreadsheet available at http://spreadsheets.google.com/pub?key=pAGYQr-yhoUh6sl5NaqEVZw. E-mail <code>leifarne at storset dot net</code> if you want edit permissions.

====Addresses====
All receipts have hCard candidates (i. e. name and/or address) of at least one of these types:
*buyer/customer
*seller
*shipping
*billing
*pickup

====Shipping====
These vendors supported '''multiple shipments''':
*Amazon.com
*Barnes&Noble
**Also displayed shipment subtotals.

These displayed '''shipping method/speed''':
*Amazon.com
*Barnes&Noble
*Symantec

These displayed '''gift''' choices:
*Amazon.com
*Barnes&Noble

For most vendors, each item had the following information:
*description
*quantity
*unit price
*line total
Google Checkout additionally provided shipping status.

====Payment information====
Most vendors displayed:
*payment method (credit card or COD, card type)
*last 4 or 5 digits of credit card
*expiration date of credit card

Some also displayed
*reference on credit-card statement ("This order will appear as ABCD0001234 on your credit-card statement.")
*the credit-card charge itself

====Totals====
Most displayed:
*subtotal
*shipping and handling cost (if applicable)
*tax
*grand total

Some also displayed:
*total before tax
*total quantity (only A1Books)

====Marketplace====
Most receipt formats are for one seller only. The following support different sellers:
*A1Books: per item
*Amazon.com: per item
*Google Checkout: per receipt
*PayPal: per receipt

====Other properties====
Almost all receipts had
*order date
**Facebook had no date.
**Longs/FujiFilm had pick-up date instead.
*order id
**Symantec did not mention order id.

Other interesting items:
*permalink (on most e-mail receipts)
*link to purchase history
*order history (Google Checkout):
**placed
**received
**charged
**shipped

== Existing Practices ==

Listed below is an overview of existing patterns and practices found in the wild for bill and receipt data.

===Summary of common patterns discovered===

===Other attempts to solve The Problem===
For paper receipts, [http://www.neatreceipts.com/ NeatReceipts Scanalizer] offers a heuristic-based solution.

== Proposal ==

== See Also ==
* [[receipt]]
* http://en.wikipedia.org/wiki/Receipt

process

2007-08-17T00:29:18Z

Lastorset: /* Pages to create */ clarified list a bit

<div style="float:right;margin-left:1em">__TOC__</div>

If this is your first visit, please see the [[introduction]] page first.

<h1>So you wanna develop a new microformat?</h1>

== Get some experience first ==
Before even considering pursuing a new microformat, first:

# Make your site [[POSH]].
# Add <em>existing</em> microformats to your sites like [[hcard|hCard]] for your contact info etc., [[hcalendar|hCalendar]] for your events, [[hatom|hAtom]] for your episodic content (e.g. blogs). See [[get-started]] for more specific examples of adding microformats to your sites.

This will help familiarize you with how [[POSH]] and [[microformats]] currently work. Such "real world" experience will greatly help you with the development a new microformat.

Then, ask yourself:

==Why?==
There must be a problem to be solved. No problem, no microformat.

Once you've found your 'problem,' ask yourself: 'is there a simpler problem here?' If so, let's solve that problem first. We want to deal with the simplest problems first and only then build up to more complex problems.

Also, search around on the web. Chances are that someone else has encountered the same problem as you. If you still believe that you have an unsolved problem, post something to the [http://microformats.org/mailman/listinfo/microformats-new/ microformats-new] mailing list or any other public channel (see http://microformats.org/discuss/) We want to involve all interested parties in the discussion. Start the discussion '''BEFORE''' you start creating any pages on the wiki. We're not using the wiki as a general "scratch pad". If you can't summarize the problem you are trying to solve in a short email, and feel like you need a long document, you're probably trying to solve too big of a problem - see previous paragraph.

==Document Current Behavior==
Document examples of current human behavior. [[why-examples|Why examples first?]]

Remember, we're [http://ifindkarma.typepad.com/relax/2004/12/microformats.html paving the cowpaths]- before you do that you have to ''find'' the cowpaths. Your [[examples]] should be a collection of real world sites and pages which are publishing the kind of data you wish to structure with a microformat. From those pages and sites, you should extract markup examples and the schemas implied therein, and provide analysis.

This collection of examples should be public, preferably on a wiki because there's no way you can do it by yourself (no matter how many of you there are). The [[reviews-formats]] page is a good example of research done before the creation of a microformat. Before developing [[hreview|hReview]], the collaborators went out, documented current practices around reviews on web sites, and provided some analysis of the schemas implied therein.

It's quite possible during this step that you'll find someone else who has dealt with the problem you're addressing. Perhaps even solved it. Do your best to open a dialog with others who have encountered the same problem. We don't want to build walls between competing communities - we want people to work together to develop a good solution which will cover the majority of cases.

==Propose a Microformat==
Actually, '''DON'T!!!'''

There are other things to try before developing a microformat. First, ask yourself these questions:

# Is there a standard element in XHTML that would work?
# Is there a compound of XHTML elements that would work?
# Ok, if the answer to the above two is 'no,' we can talk about a microformat.

For more details on semantic XHTML, examples of using XHTML elements, and constructing XHTML compounds, see [http://tantek.com/presentations/2005/03/elementsofxhtml/ The Elements of Meaningful XHTML].

First you should observe [[microformats#the_microformats_principles|the microformats principles]].

After you understand the principes, ask yourself: "are there any well established, interoperably implemented standards we can look at which address this problem?" For example, hCard and hCalendar were built on top of the IETF standards for vCard and iCal, respectively, both of which are widely interoperably implemented, and dominant in their space (there were no competing formats with anywhere near the same levels of adoption). The developers of those standards had already spent many years in standards committees arguing about and developing the schemas. Better to leverage all the hard work that others have done before you, than to go off as a solo cowboy inventor, and waste time repeating all their mistakes. It's also much easier to start from a well established schema, and map into into XHTML than to develop a new schema.

Remember, microformats should be designed for humans first and machines second. Here are few questions that may help you decide if you really need a microformat for the problem you are trying to solve:

# If I looked at this microformat in a browser that didn't support CSS or had CSS turned off, would it still be human-readable?
# Are this format's elements stylable with CSS?

If the proposed format doesn't pass these two things, it's not likely to gain much acceptance. Remember: ''humans first, machines second''.

== Iterate ==
In the process of developing a microformat, you'll likely get a lot of feedback from others interested in microformats. The effort needs to be iterated and adapted. Microformat development should be collaborative and community-based.

Here's an ASCII-art flow diagram:
<pre>
DIAGRAM:
problem statement---->research/discussion---->proposal/draft---->standard
^________________V ^___________________V ^______________V
</pre>

Note that each stage involves iteration. That iteration consists of discussion and feedback and may result in major changes. Do not be afraid to make major changes and please don't get too attached to any particular solutions.

=== Naming considerations ===
'''DO NOT''' start with even labeling your effort "hXYZ". This is a ''very'' common mistake.

Always start with the general problem area.

Thus name the problem area (*- pages below) generically and specifically avoid starting with code name / brand name like hNewCoolFormat.

Good: '''[[product-examples]]'''. Bad: '''hProduct-examples'''.

=== Pages to create ===
A pattern has emerged from successful microformat development efforts of several specific kinds of wiki pages being created, in a particular order (though not always).

After a specific problem area (*) has been determined (principle 1), consider creating and filling out the following pages for it. If you're unable to come up with material for the pages, then you should probably reconsider whether or not the problem is worth (or ready for) solving.
# *-examples. Find examples on today's web of the the type of content you think needs a microformat. Document them with URLs. Document the implicit schemas that the content examples imply. This is the action that helps follow principle 3, design for humans first, machines second ... adapt to current behaviors and usage patterns. Start by cloning the [[examples]] page and filling it out.
# *-formats. Find widely adopted interoperable current data formats and standards that attempt to or have attempted to solve the problem previously. Document their explicit schemas. This is necessary prerequisite for following through with principle 4, "reuse building blocks from widely adopted standards".
# *-brainstorming. Use the current real-world web examples and their implicit schemas to determine an 80/20 as-simple-as-possible (principle 2) generic schema to represent their data. Yes, this means you will explicitly ''omit'' some features of some use cases, or perhaps entire use cases which are more edge-cases than representative of larger, aggregate/macro behaviors. See which existing microformats can be reused as building blocks (principle 5, modularity). Use those existing data formats and schemas as a [[existing-classes|source of names]] for the fields (principle 4). Consider how would you embed this microformat in other formats (also principle 5, embeddability). See the [[brainstorming]] page for a bit more info.
# With an 80/20 schema, and a source of field names, write up one or more straw proposals for a microformat in the *-brainstorming page. Make sure the straw proposals encourage the decentralized distribution of data (principle 6). Postpone the choice of root class name as it often overlaps with the naming of the microformat itself. Always keep close at hand the [[naming-principles|microformats naming principles]] when choosing names.
# Brainstorming about the substance of the microformat (its properties and values) should precede naming the microformat itself. Thus after proposals have been written up and are being discussed for the schema, create a naming section for the microformat itself and root class name, where various names can be considered.

When it seems like there is some amount of consensus around one of the straw proposals for a microformat with a specific name(**), write it up as a separate wiki page as a draft specification, and then start creating the following pages to track it.
# **-faq. There will likely be common questions about the new microformat which can/should be answered in an FAQ page.
# **-issues. Folks may also raise issues about the microformat which aren't immediately addressable. An issues document helps serves to capture these issues, who raised them, and when, so that folks working on the microformat can be sure to go through and thoroughly answer them.
# **-examples. Eventually there may be too many real world examples of a microformat to document them in an informative section at the end of the specification, thus the list deserves its own page.
# **-implementations. Eventually there may be too many implementations of a microformat to document them in an informative section at the end of the specification, thus the list deserves its own page.
# **-brainstorming. Eventually there will be non-trivial proposals/suggestions/clarifications for changes in the microformats as part of iteration. Create such a format specific [[brainstorming]] page for such suggestions.

=== Moving from Stage to Stage ===

These stages of development are mirrored on the main page where microformats are divided into "Exploratory Discussions", "Drafts", and "Specifications". How do microformats move from one stage to the other? To help answer this question, it's probably useful to write up a set of desiderata for each stage.

==== Exploratory Discussions ====

You need a problem, and you need to attempt to state it. You should do it on this wiki using current items under exploratory discussion as a guide. Then send a note to the microformats-new list to get the attention of others who are interested in microformats. This is probably a good chance to pull in people from outside the current microformats community who may also be experiencing the same issue.

Feedback will probably range the gamut. Others may challenge your problem statement, the need for a microformat, concur, or add. All constructive feedback is good.

As a result of feedback, you may decide to abort your microformat idea or substantially modify it. One thing you want to be sure to do at this stage is to avoid [[reinvented-wheels|reinventing the wheel]]. Are there elemental microformats you can reuse as building blocks? Doing this will save you effort and help you get implemented later because implementers will have less work to do.

However, do not be cowed from moving forward just because some people object. If you can find a group of people you respect who feel your idea has merit and, perhaps most importantly, are willing to continue working with you on getting it in shape, proceed.

==== Drafts ====

Here, you need to write what is essentially a specification, but with the idea that it could change a lot. Again, this needs to go in the wiki, and you should send a note to microformats-discuss to alert people that something new has happened. Don't hesitate to continue trying to pull in feedback from relevant resources outside the community. Drafts need to include at least the following:

* Statements regarding the fact that you will not patent and are adopting appropriate copyright as illustrated by current drafts.
* An XMDP stating attribute values. You may want to place this on a separate wiki page and link to it. In that case use the naming convention *-profile, e.g. [[hcard-profile]].
* Examples from current practice that show how the microformat would be used. Keep an eye out for how the microformat is actually improving things. If it's not, that might be an indication that you either need to abandon or change a lot.
* References that back up your design decisions for the microformat. To the extent possible, you do not want to invent things from whole cloth.
* A list of implementations (if any).
* An issues section for people to feed back to you with detailed objections.

==== Specifications ====

You will usually need at least one iteration to get past the draft stage. By the time something becomes a specification, it should be stable so that developers can pick it up and write to it. This in turn implies that there are at least a couple of implementations.

Before moving to the specifications section, drop a note to microformats-discuss and wait a day or two for major objections. If none are forthcoming, move the microformat to the specifications area. This move will wake up any sleeping editors, and they may raise an objection and move you back to draft. If you have followed the process, now is the time to pin them down. At this juncture, any remaining issues should be easy to resolve.

== Other Documents ==

=== Patterns ===

What about other types of pages on the wiki, like "patterns" (e.g. [[include-pattern]])?

How do those get created?

The short explanation is this:

The patterns are not formats at all. They do not stand on their own. They are merely documentation of pieces of other formats that are expected to (or are) being reused by other formats. The real world examples for includes in particular were documented in the context of [[resume-examples]], [[resume-formats]], and [[resume-brainstorming]] (as noted at the very top of [[include-pattern|the document]]) "Initially developed as part of resume-brainstorming..." Later, real world examples for reviews were found to need the include pattern as well.

== Related ==

* [[process-brainstorming]]

receipt-examples

2007-08-17T00:14:53Z

Lastorset: /* Analysis of Receipts */ subheadings

= Receipt =

Overview of Receipt exploratory discussion goes here...

== Authors ==

=== Contributors ===
Rob Manson

== Real-World Examples ==

=== Bill / Invoice ===

Bills or Invoices are "yet to be paid" items.

Question: Perhaps these examples (yet to be provided) should be moved to a separate page as Bill/Invoice is quite different from Receipt.

: With [[hResume]], I've [[hresume-brainstorming|suggested]] that the subtle difference between actively seeking work and just presenting your resume be a case of including [[hlisting]] markup.
: With bills vs invoices, it may turn out that the content found within would be identical, and it might just be a case of putting in a class flag to indicate whether the presented document has been paid for or not.
: [[User:SignpostMarv|SignpostMarv]] 12:55, 21 Jul 2007 (PDT)

::I think a class flag is a great idea, but I don't believe we have any samples for invoices. However, if we look at order review vs. order summary rather than invoices vs. receipts, the payment flag does become relevant in many of the sampled online stores.
::How would such a flag be implemented?
::*<code><nowiki><div class="hreceipt unpaid"/"hreceipt paid">...</nowiki></code>
::*<code><nowiki><div class="hreceipt" title="paid">...</div></nowiki></code>
::[[User:Lastorset|Lastorset]] 14:55, 16 Aug 2007 (PDT)

=== Receipts ===

Receipts are post-purchase items.

==== Amazon ====
* [http://mobileonlinebusiness.com.au/uf/receipt/Amazon.com-Vieworder-anon.htm Example]
* contains:
**<del>email address</del> (could not find in examples)
**date of order
**order id
**shipments
***shipping estimate
***delivery estimate
***shipping address
***shipping speed
***shipping preference (item grouping)
***items
****quantity
****seller
****price
****item information
**payment
***card type
***last 5 digits
***expiration date
***billing address
***subtotal
***shipping and handling price
***total before tax
***tax
***grand total
**<del>discount price</del> (could not find in examples)
* Little semantic HTML of interest, except an anchor with id "payment-info"

Notes:
*Supports multiple shipments.
*Supports one seller per item.
*Displays shipping and delivery estimate.
*Offers item grouping preference.
*Gift options.

==== Skype ====

===== Skype Phone =====
*[[receipt-example-skype-phone|example source code]]
*[http://mobileonlinebusiness.com.au/uf/receipt/Skype-order-history.html Skype order history]

* Shipping Address
* date in dd/mm/yyyy format
* Order number in nnnn-nnnnnnn-nnn format
* Reference (was blank in example, presumed to appear on bank statement for this transaction)
* Items
** Quantity
** Description
** Price
** Total
** VAT (tax) %
* Payment
** subtotal ("total")
** shipping cost
** grand total ("total (gross)")
** total (VAT excluded)
** VAT (amount)
* Chosen payment method: "Your payment method is: Credit card"
* Legal blurb

Semantic HTML:
* Order resume class="order-listing"
* Each item class="row"
* All totals rows class="totals-row" except grand total class="grandtotal-row"

Notes:
*Displayed credit-card-statement reference (presumably).

==== Internet banking transaction receipts ====
===== Example 1 =====
<pre><nowiki>
receipt number
date
time
receipt type (e.g. TRANSFER BETWEEN MY ACCOUNTS)
transfer from
transfer to
amount
description
information/comment
</nowiki></pre>

==== Digital product purchase receipts ====
===== Example 1 : Software =====
<pre><nowiki>
receipt title/type
order/receipt number
seller's details
sold by (hCard candidate)
org
adr
tax number (VAT in this example)
tax id (Federal Tax ID)
buyer's details
buyer (hCard candidate)
name
org
street-address
locality
region
postal-code
country-name
tel
email
credit card number (PAN truncated - with type)
item list
product code
name
comments
price
delivery method
quantity
total in selected currency
total in sellers currency
total (sum of item list totals)
processing fee
grand total (final amount charged)
information (caveats and tax info)
permalink
</nowiki></pre>

===== Example 2 : SSL certificate =====
<pre><nowiki>
receipt title/type
seller (hCard candidate)
org
street-address
locality
region
postal-code
purchase information
order id
product name
domain name
validity period
number of licenses
card number (PAN truncated)
amount (with selected currency)
</nowiki></pre>

==== Physical product purchase receipts ====
===== Example 1 : Computer hardware =====
<pre><nowiki>
receipt title/type
seller's name (hCard candidate)
seller's URL (hCard candidate)
invoice id
org govt reference (ABN - Australian Business Number)
date
seller details (hCard candidate)
street-address
locality
region
postal-code
buyer (hCard candidate)
fn
billing address
street-address
locality
region
postal-code
delivery address
street-address
locality
region
postal-code
phone
item list
item
description
amount
quantity
product url
total
delivery cost
total excluding tax
tax (GST - Goods and Service Tax)
total including tax
</nowiki></pre>

==== Service purchase receipts ====
===== Example 1 : Online subscription =====
<pre><nowiki>
seller's details (hCard candidate)
org
street-address
locality
region
postal-code
country-name
buyer's details (hCard candidate)
fn
street-address
locality
region
postal-code
phone
date
receipt id
item list
product description
quantity
rate (per unit)
price
sub total
amount paid
balance due
information
transaction id
</nowiki></pre>

===== Example 2 : Co-location =====
<pre><nowiki>
receipt title/type
sellers details (hCard candidate)
org
url
phone
message
receipt number
date
amount
information
</nowiki></pre>

==== A1Books ====
[http://mobileonlinebusiness.com.au/uf/receipt/A1Books-Sales-Order-anon.htm Example]

*vendor
**name
**fax
*date
*order number
*shipping address
*billing address
*items
**description
**list price
**sale price
**quantity
**amount
*subtotal
*shipping
*total
**quantity
**amount
*account information
**phone
**e-mail
*payment
**method
**last four digits

No semantic HTML.

Notes:
*Supports one seller per item.
*Does not display tax.

==== Barnes&Noble ====
[http://mobileonlinebusiness.com.au/uf/receipt/BarnesAndNoble.com-receipt.anon.tidied.htm Example]

*date
*shipping address
*billing address
*payment
**method
**last 4 digits
**exp. date
**charge
*savings on shipping
*order no.
*delivery option
*items
**description: title, author, ISBN, price
**qty
**gift options: wrap, message
**total price
*shipment subtotal
*shipping cost
*tax
*shipment total (seems to account for orders requiring multiple shipments)
*order total

Semantic HTML:
*receiptOrderNumbers
*receiptOrderPlacedOn
*orderInformation
**shippingAddress
**billingAddress
**paymentInformation
*shippingSelections
*showProducts
**reviewTable
***qtyValuePosition
***reviewGiftOptions
*reviewTotalsDisplay
**reviewTotalsSummary
**reviewTotalsNote
**reviewTotalsBreakdown
*reviewTotalsSummary
**reviewGrandTotal
*reviewCreditCardCharged
*review

The semantic class names found are a good start, although the "review" part appears to be context-specific (reviewing an order). Additionally, the implied hierarchy in names such as "reviewTotalsSummary" and "receiptOrderPlacedOn" is probably unnecessary for our purposes.

Notes:
*Supports multiple shipments.
*Gift options.
*Explicitly stated credit-card charge.

==== Facebook ====
[http://mobileonlinebusiness.com.au/uf/receipt/Facebook-gift-receipt.html Example]

*purchase total
*items (informal description of two items, including quantity)
*recipient name
*order id
*billed-to name

No relevant semantic HTML.

Notes:
*Quite minimal and informal receipt. Good example of how a microformat would preserve human readability and informal style while enabling machine reading.

==== Google Checkout ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Google-Checkout-e-mail-receipt.tidied.html Example email receipt]
*[http://mobileonlinebusiness.com.au/uf/receipt/Google-Checkout-Order-Receipt_DVD-Empire.tidied.htm Example web receipt]

*vendor address
*shipping address
*date
*order id
*items
**shipping status ("Not yet shipped", etc.)
**qty.
**description
**price
*shipping cost
*tax
*total
*order history (placed, received, charged, shipped) (web receipt only)
*payment info (web receipt only)
**card type
**last 4 digits
**exp. date
**cardholder address
*permalink

Semantic HTML:
*taxRow
**taxIdentifier
**taxAmount
*totalAmount

Notes:
*Explicit seller address (one per order).
*Current shipping status of each item.
*E-mail receipt has permalink.
*Order history (date placed, received, charged, shipped).

==== iTunes ====
*[http://mobileonlinebusiness.com.au/uf/receipt/iTunes-receipt-e-mail.html iTunes e-mail receipt]

*billing address
*order no.
*receipt date
*order total
*card
**type
**last 4 digits
*item
**item no.
**description (including link to write a review)
**unit price
*subtotal
*tax

No relevant semantic HTML.

Notes:
*No quantity information.

==== Longs/FujiFilm ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Longs-Fujifilm-photo-receipt.html Longs/Fujifilm e-mail receipt]

*order no.
*payment info
**method (COD, credit card, etc.)
*customer address
*pickup address
*items
**name
**qty.
**description
**price
**line item subtotal
*order items total
*tax
*order total

Semantic HTML:
*payment-heading

Notes:
*No order date; has pick-up date instead.
*Has pickup address rather than shipping address.

==== Mobivox/PayPal ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Mobivox-PayPal.htm Mobivox/PayPal receipt]
*[http://mobileonlinebusiness.com.au/uf/receipt/Mobivox-PayPal-printable.htm Mobivox/PayPal printable receipt]

*seller address
*receipt id
*date of order
*items
**description
**item option (not quite sure what this is for)
**unit price
**qty
**total
*subtotal
*tax
*total amount
*payment info
**method
**last 4 digits
**charge
**appears on bill/statement as "MOBIVOXCORP"
*buyer contact

Relevant semantic HTML:
*order-summary
**cart
***(unnamed tr)
****item-name
****item-total
****item-option (not quite sure what this is for)
**subtotal
**totals-value
**totals-currency
**purchase-summary
***summary-total
****price-total
****price-currency
*funding-mix
**payment-type
**amount
**ccStatement
*contact-information (contains hCard microformat)

This semantic HTML is the most complete and well-thought-out I've seen in this analysis. It even makes use of the fieldset element in forms, something I've never seen before.[[User:Lastorset|Lastorset]] 16:21, 25 Jul 2007 (PDT)

Microformats used:
*hCard (non-compliant due to missing formatted name): buyer contact info

Notes:
*Explicitly stated credit-card charge.
*Displayed credit-card-statement reference.
*Explicitly displayed seller address (one seller per order).

==== Symantec ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Symantec-reminder-e-mail.html Symantec e-mail reminder]

*buyer name
*date
*payment method
*last 4 digits
*appears on statement as "DR *Symantec"
*items
**qty
**product name
**platform
**delivery method
**price
*subtotal
*grand total
*permalink

No relevant semantic HTML

Notes:
*As an e-mail "order reminder" rather than a receipt, this was slightly more informal than the other samples. As such there was
**no order id
**a permalink
*"Delivery method" could be download or ship.

== Analysis ==

=== Analysis of Bills ===

=== Analysis of Receipts ===

====Addresses====
All receipts have hCard candidates (i. e. name and/or address) of at least one of these types:
*buyer/customer
*seller
*shipping
*billing
*pickup

====Shipping====
These vendors supported '''multiple shipments''':
*Amazon.com
*Barnes&Noble
**Also displayed shipment subtotals.

These displayed '''shipping method/speed''':
*Amazon.com
*Barnes&Noble
*Symantec

These displayed '''gift''' choices:
*Amazon.com
*Barnes&Noble

For most vendors, each item had the following information:
*description
*quantity
*unit price
*line total
Google Checkout additionally provided shipping status.

====Payment information====
Most vendors displayed:
*payment method (credit card or COD, card type)
*last 4 or 5 digits of credit card
*expiration date of credit card

Some also displayed
*reference on credit-card statement ("This order will appear as ABCD0001234 on your credit-card statement.")
*the credit-card charge itself

====Totals====
Most displayed:
*subtotal
*shipping and handling cost (if applicable)
*tax
*grand total

Some also displayed:
*total before tax
*total quantity (only A1Books)

====Marketplace====
Most receipt formats are for one seller only. The following support different sellers:
*A1Books: per item
*Amazon.com: per item
*Google Checkout: per receipt
*PayPal: per receipt

====Other properties====
Almost all receipts had
*order date
**Facebook had no date.
**Longs/FujiFilm had pick-up date instead.
*order id
**Symantec did not mention order id.

Other interesting items:
*permalink (on most e-mail receipts)
*link to purchase history
*order history (Google Checkout):
**placed
**received
**charged
**shipped

== Existing Practices ==

Listed below is an overview of existing patterns and practices found in the wild for bill and receipt data.

===Summary of common patterns discovered===

===Other attempts to solve The Problem===
For paper receipts, [http://www.neatreceipts.com/ NeatReceipts Scanalizer] offers a heuristic-based solution.

== Proposal ==

== See Also ==
* [[receipt]]
* http://en.wikipedia.org/wiki/Receipt

receipt-examples

2007-08-17T00:14:09Z

Lastorset: /* Analysis */ Group-analysis results

= Receipt =

Overview of Receipt exploratory discussion goes here...

== Authors ==

=== Contributors ===
Rob Manson

== Real-World Examples ==

=== Bill / Invoice ===

Bills or Invoices are "yet to be paid" items.

Question: Perhaps these examples (yet to be provided) should be moved to a separate page as Bill/Invoice is quite different from Receipt.

: With [[hResume]], I've [[hresume-brainstorming|suggested]] that the subtle difference between actively seeking work and just presenting your resume be a case of including [[hlisting]] markup.
: With bills vs invoices, it may turn out that the content found within would be identical, and it might just be a case of putting in a class flag to indicate whether the presented document has been paid for or not.
: [[User:SignpostMarv|SignpostMarv]] 12:55, 21 Jul 2007 (PDT)

::I think a class flag is a great idea, but I don't believe we have any samples for invoices. However, if we look at order review vs. order summary rather than invoices vs. receipts, the payment flag does become relevant in many of the sampled online stores.
::How would such a flag be implemented?
::*<code><nowiki><div class="hreceipt unpaid"/"hreceipt paid">...</nowiki></code>
::*<code><nowiki><div class="hreceipt" title="paid">...</div></nowiki></code>
::[[User:Lastorset|Lastorset]] 14:55, 16 Aug 2007 (PDT)

=== Receipts ===

Receipts are post-purchase items.

==== Amazon ====
* [http://mobileonlinebusiness.com.au/uf/receipt/Amazon.com-Vieworder-anon.htm Example]
* contains:
**<del>email address</del> (could not find in examples)
**date of order
**order id
**shipments
***shipping estimate
***delivery estimate
***shipping address
***shipping speed
***shipping preference (item grouping)
***items
****quantity
****seller
****price
****item information
**payment
***card type
***last 5 digits
***expiration date
***billing address
***subtotal
***shipping and handling price
***total before tax
***tax
***grand total
**<del>discount price</del> (could not find in examples)
* Little semantic HTML of interest, except an anchor with id "payment-info"

Notes:
*Supports multiple shipments.
*Supports one seller per item.
*Displays shipping and delivery estimate.
*Offers item grouping preference.
*Gift options.

==== Skype ====

===== Skype Phone =====
*[[receipt-example-skype-phone|example source code]]
*[http://mobileonlinebusiness.com.au/uf/receipt/Skype-order-history.html Skype order history]

* Shipping Address
* date in dd/mm/yyyy format
* Order number in nnnn-nnnnnnn-nnn format
* Reference (was blank in example, presumed to appear on bank statement for this transaction)
* Items
** Quantity
** Description
** Price
** Total
** VAT (tax) %
* Payment
** subtotal ("total")
** shipping cost
** grand total ("total (gross)")
** total (VAT excluded)
** VAT (amount)
* Chosen payment method: "Your payment method is: Credit card"
* Legal blurb

Semantic HTML:
* Order resume class="order-listing"
* Each item class="row"
* All totals rows class="totals-row" except grand total class="grandtotal-row"

Notes:
*Displayed credit-card-statement reference (presumably).

==== Internet banking transaction receipts ====
===== Example 1 =====
<pre><nowiki>
receipt number
date
time
receipt type (e.g. TRANSFER BETWEEN MY ACCOUNTS)
transfer from
transfer to
amount
description
information/comment
</nowiki></pre>

==== Digital product purchase receipts ====
===== Example 1 : Software =====
<pre><nowiki>
receipt title/type
order/receipt number
seller's details
sold by (hCard candidate)
org
adr
tax number (VAT in this example)
tax id (Federal Tax ID)
buyer's details
buyer (hCard candidate)
name
org
street-address
locality
region
postal-code
country-name
tel
email
credit card number (PAN truncated - with type)
item list
product code
name
comments
price
delivery method
quantity
total in selected currency
total in sellers currency
total (sum of item list totals)
processing fee
grand total (final amount charged)
information (caveats and tax info)
permalink
</nowiki></pre>

===== Example 2 : SSL certificate =====
<pre><nowiki>
receipt title/type
seller (hCard candidate)
org
street-address
locality
region
postal-code
purchase information
order id
product name
domain name
validity period
number of licenses
card number (PAN truncated)
amount (with selected currency)
</nowiki></pre>

==== Physical product purchase receipts ====
===== Example 1 : Computer hardware =====
<pre><nowiki>
receipt title/type
seller's name (hCard candidate)
seller's URL (hCard candidate)
invoice id
org govt reference (ABN - Australian Business Number)
date
seller details (hCard candidate)
street-address
locality
region
postal-code
buyer (hCard candidate)
fn
billing address
street-address
locality
region
postal-code
delivery address
street-address
locality
region
postal-code
phone
item list
item
description
amount
quantity
product url
total
delivery cost
total excluding tax
tax (GST - Goods and Service Tax)
total including tax
</nowiki></pre>

==== Service purchase receipts ====
===== Example 1 : Online subscription =====
<pre><nowiki>
seller's details (hCard candidate)
org
street-address
locality
region
postal-code
country-name
buyer's details (hCard candidate)
fn
street-address
locality
region
postal-code
phone
date
receipt id
item list
product description
quantity
rate (per unit)
price
sub total
amount paid
balance due
information
transaction id
</nowiki></pre>

===== Example 2 : Co-location =====
<pre><nowiki>
receipt title/type
sellers details (hCard candidate)
org
url
phone
message
receipt number
date
amount
information
</nowiki></pre>

==== A1Books ====
[http://mobileonlinebusiness.com.au/uf/receipt/A1Books-Sales-Order-anon.htm Example]

*vendor
**name
**fax
*date
*order number
*shipping address
*billing address
*items
**description
**list price
**sale price
**quantity
**amount
*subtotal
*shipping
*total
**quantity
**amount
*account information
**phone
**e-mail
*payment
**method
**last four digits

No semantic HTML.

Notes:
*Supports one seller per item.
*Does not display tax.

==== Barnes&Noble ====
[http://mobileonlinebusiness.com.au/uf/receipt/BarnesAndNoble.com-receipt.anon.tidied.htm Example]

*date
*shipping address
*billing address
*payment
**method
**last 4 digits
**exp. date
**charge
*savings on shipping
*order no.
*delivery option
*items
**description: title, author, ISBN, price
**qty
**gift options: wrap, message
**total price
*shipment subtotal
*shipping cost
*tax
*shipment total (seems to account for orders requiring multiple shipments)
*order total

Semantic HTML:
*receiptOrderNumbers
*receiptOrderPlacedOn
*orderInformation
**shippingAddress
**billingAddress
**paymentInformation
*shippingSelections
*showProducts
**reviewTable
***qtyValuePosition
***reviewGiftOptions
*reviewTotalsDisplay
**reviewTotalsSummary
**reviewTotalsNote
**reviewTotalsBreakdown
*reviewTotalsSummary
**reviewGrandTotal
*reviewCreditCardCharged
*review

The semantic class names found are a good start, although the "review" part appears to be context-specific (reviewing an order). Additionally, the implied hierarchy in names such as "reviewTotalsSummary" and "receiptOrderPlacedOn" is probably unnecessary for our purposes.

Notes:
*Supports multiple shipments.
*Gift options.
*Explicitly stated credit-card charge.

==== Facebook ====
[http://mobileonlinebusiness.com.au/uf/receipt/Facebook-gift-receipt.html Example]

*purchase total
*items (informal description of two items, including quantity)
*recipient name
*order id
*billed-to name

No relevant semantic HTML.

Notes:
*Quite minimal and informal receipt. Good example of how a microformat would preserve human readability and informal style while enabling machine reading.

==== Google Checkout ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Google-Checkout-e-mail-receipt.tidied.html Example email receipt]
*[http://mobileonlinebusiness.com.au/uf/receipt/Google-Checkout-Order-Receipt_DVD-Empire.tidied.htm Example web receipt]

*vendor address
*shipping address
*date
*order id
*items
**shipping status ("Not yet shipped", etc.)
**qty.
**description
**price
*shipping cost
*tax
*total
*order history (placed, received, charged, shipped) (web receipt only)
*payment info (web receipt only)
**card type
**last 4 digits
**exp. date
**cardholder address
*permalink

Semantic HTML:
*taxRow
**taxIdentifier
**taxAmount
*totalAmount

Notes:
*Explicit seller address (one per order).
*Current shipping status of each item.
*E-mail receipt has permalink.
*Order history (date placed, received, charged, shipped).

==== iTunes ====
*[http://mobileonlinebusiness.com.au/uf/receipt/iTunes-receipt-e-mail.html iTunes e-mail receipt]

*billing address
*order no.
*receipt date
*order total
*card
**type
**last 4 digits
*item
**item no.
**description (including link to write a review)
**unit price
*subtotal
*tax

No relevant semantic HTML.

Notes:
*No quantity information.

==== Longs/FujiFilm ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Longs-Fujifilm-photo-receipt.html Longs/Fujifilm e-mail receipt]

*order no.
*payment info
**method (COD, credit card, etc.)
*customer address
*pickup address
*items
**name
**qty.
**description
**price
**line item subtotal
*order items total
*tax
*order total

Semantic HTML:
*payment-heading

Notes:
*No order date; has pick-up date instead.
*Has pickup address rather than shipping address.

==== Mobivox/PayPal ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Mobivox-PayPal.htm Mobivox/PayPal receipt]
*[http://mobileonlinebusiness.com.au/uf/receipt/Mobivox-PayPal-printable.htm Mobivox/PayPal printable receipt]

*seller address
*receipt id
*date of order
*items
**description
**item option (not quite sure what this is for)
**unit price
**qty
**total
*subtotal
*tax
*total amount
*payment info
**method
**last 4 digits
**charge
**appears on bill/statement as "MOBIVOXCORP"
*buyer contact

Relevant semantic HTML:
*order-summary
**cart
***(unnamed tr)
****item-name
****item-total
****item-option (not quite sure what this is for)
**subtotal
**totals-value
**totals-currency
**purchase-summary
***summary-total
****price-total
****price-currency
*funding-mix
**payment-type
**amount
**ccStatement
*contact-information (contains hCard microformat)

This semantic HTML is the most complete and well-thought-out I've seen in this analysis. It even makes use of the fieldset element in forms, something I've never seen before.[[User:Lastorset|Lastorset]] 16:21, 25 Jul 2007 (PDT)

Microformats used:
*hCard (non-compliant due to missing formatted name): buyer contact info

Notes:
*Explicitly stated credit-card charge.
*Displayed credit-card-statement reference.
*Explicitly displayed seller address (one seller per order).

==== Symantec ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Symantec-reminder-e-mail.html Symantec e-mail reminder]

*buyer name
*date
*payment method
*last 4 digits
*appears on statement as "DR *Symantec"
*items
**qty
**product name
**platform
**delivery method
**price
*subtotal
*grand total
*permalink

No relevant semantic HTML

Notes:
*As an e-mail "order reminder" rather than a receipt, this was slightly more informal than the other samples. As such there was
**no order id
**a permalink
*"Delivery method" could be download or ship.

== Analysis ==

=== Analysis of Bills ===

=== Analysis of Receipts ===

====Addresses====
All receipts have hCard candidates (i. e. name and/or address) of at least one of these types:
*buyer/customer
*seller
*shipping
*billing
*pickup

====Shipping====
These vendors supported multiple shipments:
*Amazon.com
*Barnes&Noble
**Also displayed shipment subtotals.

These displayed shipping method/speed:
*Amazon.com
*Barnes&Noble
*Symantec

These displayed gift options:
*Amazon.com
*Barnes&Noble

For most vendors, each item had the following information:
*description
*quantity
*unit price
*line total
Google Checkout additionally provided shipping status.

====Payment information====
Most vendors displayed:
*payment method (credit card or COD, card type)
*last 4 or 5 digits of credit card
*expiration date of credit card

Some also displayed
*reference on credit-card statement ("This order will appear as ABCD0001234 on your credit-card statement.")
*the credit-card charge itself

====Totals====
Most displayed:
*subtotal
*shipping and handling cost (if applicable)
*tax
*grand total

Some also displayed:
*total before tax
*total quantity (only A1Books)

====Marketplace====
Most receipt formats are for one seller only. The following support different sellers:
*A1Books: per item
*Amazon.com: per item
*Google Checkout: per receipt
*PayPal: per receipt

====Other properties====
Almost all receipts had
*order date
**Facebook had no date.
**Longs/FujiFilm had pick-up date instead.
*order id
**Symantec did not mention order id.

Other interesting items:
*permalink (on most e-mail receipts)
*link to purchase history
*order history (Google Checkout):
**placed
**received
**charged
**shipped

== Existing Practices ==

Listed below is an overview of existing patterns and practices found in the wild for bill and receipt data.

===Summary of common patterns discovered===

===Other attempts to solve The Problem===
For paper receipts, [http://www.neatreceipts.com/ NeatReceipts Scanalizer] offers a heuristic-based solution.

== Proposal ==

== See Also ==
* [[receipt]]
* http://en.wikipedia.org/wiki/Receipt

receipt-examples

2007-08-16T23:49:11Z

Lastorset: /* Symantec */ Notable results from group analysis.

= Receipt =

Overview of Receipt exploratory discussion goes here...

== Authors ==

=== Contributors ===
Rob Manson

== Real-World Examples ==

=== Bill / Invoice ===

Bills or Invoices are "yet to be paid" items.

Question: Perhaps these examples (yet to be provided) should be moved to a separate page as Bill/Invoice is quite different from Receipt.

: With [[hResume]], I've [[hresume-brainstorming|suggested]] that the subtle difference between actively seeking work and just presenting your resume be a case of including [[hlisting]] markup.
: With bills vs invoices, it may turn out that the content found within would be identical, and it might just be a case of putting in a class flag to indicate whether the presented document has been paid for or not.
: [[User:SignpostMarv|SignpostMarv]] 12:55, 21 Jul 2007 (PDT)

::I think a class flag is a great idea, but I don't believe we have any samples for invoices. However, if we look at order review vs. order summary rather than invoices vs. receipts, the payment flag does become relevant in many of the sampled online stores.
::How would such a flag be implemented?
::*<code><nowiki><div class="hreceipt unpaid"/"hreceipt paid">...</nowiki></code>
::*<code><nowiki><div class="hreceipt" title="paid">...</div></nowiki></code>
::[[User:Lastorset|Lastorset]] 14:55, 16 Aug 2007 (PDT)

=== Receipts ===

Receipts are post-purchase items.

==== Amazon ====
* [http://mobileonlinebusiness.com.au/uf/receipt/Amazon.com-Vieworder-anon.htm Example]
* contains:
**<del>email address</del> (could not find in examples)
**date of order
**order id
**shipments
***shipping estimate
***delivery estimate
***shipping address
***shipping speed
***shipping preference (item grouping)
***items
****quantity
****seller
****price
****item information
**payment
***card type
***last 5 digits
***expiration date
***billing address
***subtotal
***shipping and handling price
***total before tax
***tax
***grand total
**<del>discount price</del> (could not find in examples)
* Little semantic HTML of interest, except an anchor with id "payment-info"

Notes:
*Supports multiple shipments.
*Supports one seller per item.
*Displays shipping and delivery estimate.
*Offers item grouping preference.
*Gift options.

==== Skype ====

===== Skype Phone =====
*[[receipt-example-skype-phone|example source code]]
*[http://mobileonlinebusiness.com.au/uf/receipt/Skype-order-history.html Skype order history]

* Shipping Address
* date in dd/mm/yyyy format
* Order number in nnnn-nnnnnnn-nnn format
* Reference (was blank in example, presumed to appear on bank statement for this transaction)
* Items
** Quantity
** Description
** Price
** Total
** VAT (tax) %
* Payment
** subtotal ("total")
** shipping cost
** grand total ("total (gross)")
** total (VAT excluded)
** VAT (amount)
* Chosen payment method: "Your payment method is: Credit card"
* Legal blurb

Semantic HTML:
* Order resume class="order-listing"
* Each item class="row"
* All totals rows class="totals-row" except grand total class="grandtotal-row"

Notes:
*Displayed credit-card-statement reference (presumably).

==== Internet banking transaction receipts ====
===== Example 1 =====
<pre><nowiki>
receipt number
date
time
receipt type (e.g. TRANSFER BETWEEN MY ACCOUNTS)
transfer from
transfer to
amount
description
information/comment
</nowiki></pre>

==== Digital product purchase receipts ====
===== Example 1 : Software =====
<pre><nowiki>
receipt title/type
order/receipt number
seller's details
sold by (hCard candidate)
org
adr
tax number (VAT in this example)
tax id (Federal Tax ID)
buyer's details
buyer (hCard candidate)
name
org
street-address
locality
region
postal-code
country-name
tel
email
credit card number (PAN truncated - with type)
item list
product code
name
comments
price
delivery method
quantity
total in selected currency
total in sellers currency
total (sum of item list totals)
processing fee
grand total (final amount charged)
information (caveats and tax info)
permalink
</nowiki></pre>

===== Example 2 : SSL certificate =====
<pre><nowiki>
receipt title/type
seller (hCard candidate)
org
street-address
locality
region
postal-code
purchase information
order id
product name
domain name
validity period
number of licenses
card number (PAN truncated)
amount (with selected currency)
</nowiki></pre>

==== Physical product purchase receipts ====
===== Example 1 : Computer hardware =====
<pre><nowiki>
receipt title/type
seller's name (hCard candidate)
seller's URL (hCard candidate)
invoice id
org govt reference (ABN - Australian Business Number)
date
seller details (hCard candidate)
street-address
locality
region
postal-code
buyer (hCard candidate)
fn
billing address
street-address
locality
region
postal-code
delivery address
street-address
locality
region
postal-code
phone
item list
item
description
amount
quantity
product url
total
delivery cost
total excluding tax
tax (GST - Goods and Service Tax)
total including tax
</nowiki></pre>

==== Service purchase receipts ====
===== Example 1 : Online subscription =====
<pre><nowiki>
seller's details (hCard candidate)
org
street-address
locality
region
postal-code
country-name
buyer's details (hCard candidate)
fn
street-address
locality
region
postal-code
phone
date
receipt id
item list
product description
quantity
rate (per unit)
price
sub total
amount paid
balance due
information
transaction id
</nowiki></pre>

===== Example 2 : Co-location =====
<pre><nowiki>
receipt title/type
sellers details (hCard candidate)
org
url
phone
message
receipt number
date
amount
information
</nowiki></pre>

==== A1Books ====
[http://mobileonlinebusiness.com.au/uf/receipt/A1Books-Sales-Order-anon.htm Example]

*vendor
**name
**fax
*date
*order number
*shipping address
*billing address
*items
**description
**list price
**sale price
**quantity
**amount
*subtotal
*shipping
*total
**quantity
**amount
*account information
**phone
**e-mail
*payment
**method
**last four digits

No semantic HTML.

Notes:
*Supports one seller per item.
*Does not display tax.

==== Barnes&Noble ====
[http://mobileonlinebusiness.com.au/uf/receipt/BarnesAndNoble.com-receipt.anon.tidied.htm Example]

*date
*shipping address
*billing address
*payment
**method
**last 4 digits
**exp. date
**charge
*savings on shipping
*order no.
*delivery option
*items
**description: title, author, ISBN, price
**qty
**gift options: wrap, message
**total price
*shipment subtotal
*shipping cost
*tax
*shipment total (seems to account for orders requiring multiple shipments)
*order total

Semantic HTML:
*receiptOrderNumbers
*receiptOrderPlacedOn
*orderInformation
**shippingAddress
**billingAddress
**paymentInformation
*shippingSelections
*showProducts
**reviewTable
***qtyValuePosition
***reviewGiftOptions
*reviewTotalsDisplay
**reviewTotalsSummary
**reviewTotalsNote
**reviewTotalsBreakdown
*reviewTotalsSummary
**reviewGrandTotal
*reviewCreditCardCharged
*review

The semantic class names found are a good start, although the "review" part appears to be context-specific (reviewing an order). Additionally, the implied hierarchy in names such as "reviewTotalsSummary" and "receiptOrderPlacedOn" is probably unnecessary for our purposes.

Notes:
*Supports multiple shipments.
*Gift options.
*Explicitly stated credit-card charge.

==== Facebook ====
[http://mobileonlinebusiness.com.au/uf/receipt/Facebook-gift-receipt.html Example]

*purchase total
*items (informal description of two items, including quantity)
*recipient name
*order id
*billed-to name

No relevant semantic HTML.

Notes:
*Quite minimal and informal receipt. Good example of how a microformat would preserve human readability and informal style while enabling machine reading.

==== Google Checkout ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Google-Checkout-e-mail-receipt.tidied.html Example email receipt]
*[http://mobileonlinebusiness.com.au/uf/receipt/Google-Checkout-Order-Receipt_DVD-Empire.tidied.htm Example web receipt]

*vendor address
*shipping address
*date
*order id
*items
**shipping status ("Not yet shipped", etc.)
**qty.
**description
**price
*shipping cost
*tax
*total
*order history (placed, received, charged, shipped) (web receipt only)
*payment info (web receipt only)
**card type
**last 4 digits
**exp. date
**cardholder address
*permalink

Semantic HTML:
*taxRow
**taxIdentifier
**taxAmount
*totalAmount

Notes:
*Explicit seller address (one per order).
*Current shipping status of each item.
*E-mail receipt has permalink.
*Order history (date placed, received, charged, shipped).

==== iTunes ====
*[http://mobileonlinebusiness.com.au/uf/receipt/iTunes-receipt-e-mail.html iTunes e-mail receipt]

*billing address
*order no.
*receipt date
*order total
*card
**type
**last 4 digits
*item
**item no.
**description (including link to write a review)
**unit price
*subtotal
*tax

No relevant semantic HTML.

Notes:
*No quantity information.

==== Longs/FujiFilm ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Longs-Fujifilm-photo-receipt.html Longs/Fujifilm e-mail receipt]

*order no.
*payment info
**method (COD, credit card, etc.)
*customer address
*pickup address
*items
**name
**qty.
**description
**price
**line item subtotal
*order items total
*tax
*order total

Semantic HTML:
*payment-heading

Notes:
*No order date; has pick-up date instead.
*Has pickup address rather than shipping address.

==== Mobivox/PayPal ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Mobivox-PayPal.htm Mobivox/PayPal receipt]
*[http://mobileonlinebusiness.com.au/uf/receipt/Mobivox-PayPal-printable.htm Mobivox/PayPal printable receipt]

*seller address
*receipt id
*date of order
*items
**description
**item option (not quite sure what this is for)
**unit price
**qty
**total
*subtotal
*tax
*total amount
*payment info
**method
**last 4 digits
**charge
**appears on bill/statement as "MOBIVOXCORP"
*buyer contact

Relevant semantic HTML:
*order-summary
**cart
***(unnamed tr)
****item-name
****item-total
****item-option (not quite sure what this is for)
**subtotal
**totals-value
**totals-currency
**purchase-summary
***summary-total
****price-total
****price-currency
*funding-mix
**payment-type
**amount
**ccStatement
*contact-information (contains hCard microformat)

This semantic HTML is the most complete and well-thought-out I've seen in this analysis. It even makes use of the fieldset element in forms, something I've never seen before.[[User:Lastorset|Lastorset]] 16:21, 25 Jul 2007 (PDT)

Microformats used:
*hCard (non-compliant due to missing formatted name): buyer contact info

Notes:
*Explicitly stated credit-card charge.
*Displayed credit-card-statement reference.
*Explicitly displayed seller address (one seller per order).

==== Symantec ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Symantec-reminder-e-mail.html Symantec e-mail reminder]

*buyer name
*date
*payment method
*last 4 digits
*appears on statement as "DR *Symantec"
*items
**qty
**product name
**platform
**delivery method
**price
*subtotal
*grand total
*permalink

No relevant semantic HTML

Notes:
*As an e-mail "order reminder" rather than a receipt, this was slightly more informal than the other samples. As such there was
**no order id
**a permalink
*"Delivery method" could be download or ship.

=== Analysis ===

==== Analysis of Bills ====

==== Analysis of Receipts ====

== Existing Practices ==

Listed below is an overview of existing patterns and practices found in the wild for bill and receipt data.

===Summary of common patterns discovered===

===Other attempts to solve The Problem===
For paper receipts, [http://www.neatreceipts.com/ NeatReceipts Scanalizer] offers a heuristic-based solution.

== Proposal ==

== See Also ==
* [[receipt]]
* http://en.wikipedia.org/wiki/Receipt

receipt-examples

2007-08-16T23:46:45Z

Lastorset: /* Skype */ Notable results from group analysis.

= Receipt =

Overview of Receipt exploratory discussion goes here...

== Authors ==

=== Contributors ===
Rob Manson

== Real-World Examples ==

=== Bill / Invoice ===

Bills or Invoices are "yet to be paid" items.

Question: Perhaps these examples (yet to be provided) should be moved to a separate page as Bill/Invoice is quite different from Receipt.

: With [[hResume]], I've [[hresume-brainstorming|suggested]] that the subtle difference between actively seeking work and just presenting your resume be a case of including [[hlisting]] markup.
: With bills vs invoices, it may turn out that the content found within would be identical, and it might just be a case of putting in a class flag to indicate whether the presented document has been paid for or not.
: [[User:SignpostMarv|SignpostMarv]] 12:55, 21 Jul 2007 (PDT)

::I think a class flag is a great idea, but I don't believe we have any samples for invoices. However, if we look at order review vs. order summary rather than invoices vs. receipts, the payment flag does become relevant in many of the sampled online stores.
::How would such a flag be implemented?
::*<code><nowiki><div class="hreceipt unpaid"/"hreceipt paid">...</nowiki></code>
::*<code><nowiki><div class="hreceipt" title="paid">...</div></nowiki></code>
::[[User:Lastorset|Lastorset]] 14:55, 16 Aug 2007 (PDT)

=== Receipts ===

Receipts are post-purchase items.

==== Amazon ====
* [http://mobileonlinebusiness.com.au/uf/receipt/Amazon.com-Vieworder-anon.htm Example]
* contains:
**<del>email address</del> (could not find in examples)
**date of order
**order id
**shipments
***shipping estimate
***delivery estimate
***shipping address
***shipping speed
***shipping preference (item grouping)
***items
****quantity
****seller
****price
****item information
**payment
***card type
***last 5 digits
***expiration date
***billing address
***subtotal
***shipping and handling price
***total before tax
***tax
***grand total
**<del>discount price</del> (could not find in examples)
* Little semantic HTML of interest, except an anchor with id "payment-info"

Notes:
*Supports multiple shipments.
*Supports one seller per item.
*Displays shipping and delivery estimate.
*Offers item grouping preference.
*Gift options.

==== Skype ====

===== Skype Phone =====
*[[receipt-example-skype-phone|example source code]]
*[http://mobileonlinebusiness.com.au/uf/receipt/Skype-order-history.html Skype order history]

* Shipping Address
* date in dd/mm/yyyy format
* Order number in nnnn-nnnnnnn-nnn format
* Reference (was blank in example, presumed to appear on bank statement for this transaction)
* Items
** Quantity
** Description
** Price
** Total
** VAT (tax) %
* Payment
** subtotal ("total")
** shipping cost
** grand total ("total (gross)")
** total (VAT excluded)
** VAT (amount)
* Chosen payment method: "Your payment method is: Credit card"
* Legal blurb

Semantic HTML:
* Order resume class="order-listing"
* Each item class="row"
* All totals rows class="totals-row" except grand total class="grandtotal-row"

Notes:
*Displayed credit-card-statement reference (presumably).

==== Internet banking transaction receipts ====
===== Example 1 =====
<pre><nowiki>
receipt number
date
time
receipt type (e.g. TRANSFER BETWEEN MY ACCOUNTS)
transfer from
transfer to
amount
description
information/comment
</nowiki></pre>

==== Digital product purchase receipts ====
===== Example 1 : Software =====
<pre><nowiki>
receipt title/type
order/receipt number
seller's details
sold by (hCard candidate)
org
adr
tax number (VAT in this example)
tax id (Federal Tax ID)
buyer's details
buyer (hCard candidate)
name
org
street-address
locality
region
postal-code
country-name
tel
email
credit card number (PAN truncated - with type)
item list
product code
name
comments
price
delivery method
quantity
total in selected currency
total in sellers currency
total (sum of item list totals)
processing fee
grand total (final amount charged)
information (caveats and tax info)
permalink
</nowiki></pre>

===== Example 2 : SSL certificate =====
<pre><nowiki>
receipt title/type
seller (hCard candidate)
org
street-address
locality
region
postal-code
purchase information
order id
product name
domain name
validity period
number of licenses
card number (PAN truncated)
amount (with selected currency)
</nowiki></pre>

==== Physical product purchase receipts ====
===== Example 1 : Computer hardware =====
<pre><nowiki>
receipt title/type
seller's name (hCard candidate)
seller's URL (hCard candidate)
invoice id
org govt reference (ABN - Australian Business Number)
date
seller details (hCard candidate)
street-address
locality
region
postal-code
buyer (hCard candidate)
fn
billing address
street-address
locality
region
postal-code
delivery address
street-address
locality
region
postal-code
phone
item list
item
description
amount
quantity
product url
total
delivery cost
total excluding tax
tax (GST - Goods and Service Tax)
total including tax
</nowiki></pre>

==== Service purchase receipts ====
===== Example 1 : Online subscription =====
<pre><nowiki>
seller's details (hCard candidate)
org
street-address
locality
region
postal-code
country-name
buyer's details (hCard candidate)
fn
street-address
locality
region
postal-code
phone
date
receipt id
item list
product description
quantity
rate (per unit)
price
sub total
amount paid
balance due
information
transaction id
</nowiki></pre>

===== Example 2 : Co-location =====
<pre><nowiki>
receipt title/type
sellers details (hCard candidate)
org
url
phone
message
receipt number
date
amount
information
</nowiki></pre>

==== A1Books ====
[http://mobileonlinebusiness.com.au/uf/receipt/A1Books-Sales-Order-anon.htm Example]

*vendor
**name
**fax
*date
*order number
*shipping address
*billing address
*items
**description
**list price
**sale price
**quantity
**amount
*subtotal
*shipping
*total
**quantity
**amount
*account information
**phone
**e-mail
*payment
**method
**last four digits

No semantic HTML.

Notes:
*Supports one seller per item.
*Does not display tax.

==== Barnes&Noble ====
[http://mobileonlinebusiness.com.au/uf/receipt/BarnesAndNoble.com-receipt.anon.tidied.htm Example]

*date
*shipping address
*billing address
*payment
**method
**last 4 digits
**exp. date
**charge
*savings on shipping
*order no.
*delivery option
*items
**description: title, author, ISBN, price
**qty
**gift options: wrap, message
**total price
*shipment subtotal
*shipping cost
*tax
*shipment total (seems to account for orders requiring multiple shipments)
*order total

Semantic HTML:
*receiptOrderNumbers
*receiptOrderPlacedOn
*orderInformation
**shippingAddress
**billingAddress
**paymentInformation
*shippingSelections
*showProducts
**reviewTable
***qtyValuePosition
***reviewGiftOptions
*reviewTotalsDisplay
**reviewTotalsSummary
**reviewTotalsNote
**reviewTotalsBreakdown
*reviewTotalsSummary
**reviewGrandTotal
*reviewCreditCardCharged
*review

The semantic class names found are a good start, although the "review" part appears to be context-specific (reviewing an order). Additionally, the implied hierarchy in names such as "reviewTotalsSummary" and "receiptOrderPlacedOn" is probably unnecessary for our purposes.

Notes:
*Supports multiple shipments.
*Gift options.
*Explicitly stated credit-card charge.

==== Facebook ====
[http://mobileonlinebusiness.com.au/uf/receipt/Facebook-gift-receipt.html Example]

*purchase total
*items (informal description of two items, including quantity)
*recipient name
*order id
*billed-to name

No relevant semantic HTML.

Notes:
*Quite minimal and informal receipt. Good example of how a microformat would preserve human readability and informal style while enabling machine reading.

==== Google Checkout ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Google-Checkout-e-mail-receipt.tidied.html Example email receipt]
*[http://mobileonlinebusiness.com.au/uf/receipt/Google-Checkout-Order-Receipt_DVD-Empire.tidied.htm Example web receipt]

*vendor address
*shipping address
*date
*order id
*items
**shipping status ("Not yet shipped", etc.)
**qty.
**description
**price
*shipping cost
*tax
*total
*order history (placed, received, charged, shipped) (web receipt only)
*payment info (web receipt only)
**card type
**last 4 digits
**exp. date
**cardholder address
*permalink

Semantic HTML:
*taxRow
**taxIdentifier
**taxAmount
*totalAmount

Notes:
*Explicit seller address (one per order).
*Current shipping status of each item.
*E-mail receipt has permalink.
*Order history (date placed, received, charged, shipped).

==== iTunes ====
*[http://mobileonlinebusiness.com.au/uf/receipt/iTunes-receipt-e-mail.html iTunes e-mail receipt]

*billing address
*order no.
*receipt date
*order total
*card
**type
**last 4 digits
*item
**item no.
**description (including link to write a review)
**unit price
*subtotal
*tax

No relevant semantic HTML.

Notes:
*No quantity information.

==== Longs/FujiFilm ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Longs-Fujifilm-photo-receipt.html Longs/Fujifilm e-mail receipt]

*order no.
*payment info
**method (COD, credit card, etc.)
*customer address
*pickup address
*items
**name
**qty.
**description
**price
**line item subtotal
*order items total
*tax
*order total

Semantic HTML:
*payment-heading

Notes:
*No order date; has pick-up date instead.
*Has pickup address rather than shipping address.

==== Mobivox/PayPal ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Mobivox-PayPal.htm Mobivox/PayPal receipt]
*[http://mobileonlinebusiness.com.au/uf/receipt/Mobivox-PayPal-printable.htm Mobivox/PayPal printable receipt]

*seller address
*receipt id
*date of order
*items
**description
**item option (not quite sure what this is for)
**unit price
**qty
**total
*subtotal
*tax
*total amount
*payment info
**method
**last 4 digits
**charge
**appears on bill/statement as "MOBIVOXCORP"
*buyer contact

Relevant semantic HTML:
*order-summary
**cart
***(unnamed tr)
****item-name
****item-total
****item-option (not quite sure what this is for)
**subtotal
**totals-value
**totals-currency
**purchase-summary
***summary-total
****price-total
****price-currency
*funding-mix
**payment-type
**amount
**ccStatement
*contact-information (contains hCard microformat)

This semantic HTML is the most complete and well-thought-out I've seen in this analysis. It even makes use of the fieldset element in forms, something I've never seen before.[[User:Lastorset|Lastorset]] 16:21, 25 Jul 2007 (PDT)

Microformats used:
*hCard (non-compliant due to missing formatted name): buyer contact info

Notes:
*Explicitly stated credit-card charge.
*Displayed credit-card-statement reference.
*Explicitly displayed seller address (one seller per order).

==== Symantec ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Symantec-reminder-e-mail.html Symantec e-mail reminder]

*buyer name
*date
*payment method
*last 4 digits
*appears on statement as "DR *Symantec"
*items
**qty
**product name
**platform
**delivery method
**price
*subtotal
*grand total
*permalink

No relevant semantic HTML

=== Analysis ===

==== Analysis of Bills ====

==== Analysis of Receipts ====

== Existing Practices ==

Listed below is an overview of existing patterns and practices found in the wild for bill and receipt data.

===Summary of common patterns discovered===

===Other attempts to solve The Problem===
For paper receipts, [http://www.neatreceipts.com/ NeatReceipts Scanalizer] offers a heuristic-based solution.

== Proposal ==

== See Also ==
* [[receipt]]
* http://en.wikipedia.org/wiki/Receipt

receipt-examples

2007-08-16T23:44:52Z

Lastorset: /* Mobivox/PayPal */ Notable results from group analysis

= Receipt =

Overview of Receipt exploratory discussion goes here...

== Authors ==

=== Contributors ===
Rob Manson

== Real-World Examples ==

=== Bill / Invoice ===

Bills or Invoices are "yet to be paid" items.

Question: Perhaps these examples (yet to be provided) should be moved to a separate page as Bill/Invoice is quite different from Receipt.

: With [[hResume]], I've [[hresume-brainstorming|suggested]] that the subtle difference between actively seeking work and just presenting your resume be a case of including [[hlisting]] markup.
: With bills vs invoices, it may turn out that the content found within would be identical, and it might just be a case of putting in a class flag to indicate whether the presented document has been paid for or not.
: [[User:SignpostMarv|SignpostMarv]] 12:55, 21 Jul 2007 (PDT)

::I think a class flag is a great idea, but I don't believe we have any samples for invoices. However, if we look at order review vs. order summary rather than invoices vs. receipts, the payment flag does become relevant in many of the sampled online stores.
::How would such a flag be implemented?
::*<code><nowiki><div class="hreceipt unpaid"/"hreceipt paid">...</nowiki></code>
::*<code><nowiki><div class="hreceipt" title="paid">...</div></nowiki></code>
::[[User:Lastorset|Lastorset]] 14:55, 16 Aug 2007 (PDT)

=== Receipts ===

Receipts are post-purchase items.

==== Amazon ====
* [http://mobileonlinebusiness.com.au/uf/receipt/Amazon.com-Vieworder-anon.htm Example]
* contains:
**<del>email address</del> (could not find in examples)
**date of order
**order id
**shipments
***shipping estimate
***delivery estimate
***shipping address
***shipping speed
***shipping preference (item grouping)
***items
****quantity
****seller
****price
****item information
**payment
***card type
***last 5 digits
***expiration date
***billing address
***subtotal
***shipping and handling price
***total before tax
***tax
***grand total
**<del>discount price</del> (could not find in examples)
* Little semantic HTML of interest, except an anchor with id "payment-info"

Notes:
*Supports multiple shipments.
*Supports one seller per item.
*Displays shipping and delivery estimate.
*Offers item grouping preference.
*Gift options.

==== Skype ====

===== Skype Phone =====
*[[receipt-example-skype-phone|example source code]]
*[http://mobileonlinebusiness.com.au/uf/receipt/Skype-order-history.html Skype order history]

* Shipping Address
* date in dd/mm/yyyy format
* Order number in nnnn-nnnnnnn-nnn format
* Reference (was blank in example, presumed to appear on bank statement for this transaction)
* Items
** Quantity
** Description
** Price
** Total
** VAT (tax) %
* Payment
** subtotal ("total")
** shipping cost
** grand total ("total (gross)")
** total (VAT excluded)
** VAT (amount)
* Chosen payment method: "Your payment method is: Credit card"
* Legal blurb

Semantic HTML:
* Order resume class="order-listing"
* Each item class="row"
* All totals rows class="totals-row" except grand total class="grandtotal-row"

==== Internet banking transaction receipts ====
===== Example 1 =====
<pre><nowiki>
receipt number
date
time
receipt type (e.g. TRANSFER BETWEEN MY ACCOUNTS)
transfer from
transfer to
amount
description
information/comment
</nowiki></pre>

==== Digital product purchase receipts ====
===== Example 1 : Software =====
<pre><nowiki>
receipt title/type
order/receipt number
seller's details
sold by (hCard candidate)
org
adr
tax number (VAT in this example)
tax id (Federal Tax ID)
buyer's details
buyer (hCard candidate)
name
org
street-address
locality
region
postal-code
country-name
tel
email
credit card number (PAN truncated - with type)
item list
product code
name
comments
price
delivery method
quantity
total in selected currency
total in sellers currency
total (sum of item list totals)
processing fee
grand total (final amount charged)
information (caveats and tax info)
permalink
</nowiki></pre>

===== Example 2 : SSL certificate =====
<pre><nowiki>
receipt title/type
seller (hCard candidate)
org
street-address
locality
region
postal-code
purchase information
order id
product name
domain name
validity period
number of licenses
card number (PAN truncated)
amount (with selected currency)
</nowiki></pre>

==== Physical product purchase receipts ====
===== Example 1 : Computer hardware =====
<pre><nowiki>
receipt title/type
seller's name (hCard candidate)
seller's URL (hCard candidate)
invoice id
org govt reference (ABN - Australian Business Number)
date
seller details (hCard candidate)
street-address
locality
region
postal-code
buyer (hCard candidate)
fn
billing address
street-address
locality
region
postal-code
delivery address
street-address
locality
region
postal-code
phone
item list
item
description
amount
quantity
product url
total
delivery cost
total excluding tax
tax (GST - Goods and Service Tax)
total including tax
</nowiki></pre>

==== Service purchase receipts ====
===== Example 1 : Online subscription =====
<pre><nowiki>
seller's details (hCard candidate)
org
street-address
locality
region
postal-code
country-name
buyer's details (hCard candidate)
fn
street-address
locality
region
postal-code
phone
date
receipt id
item list
product description
quantity
rate (per unit)
price
sub total
amount paid
balance due
information
transaction id
</nowiki></pre>

===== Example 2 : Co-location =====
<pre><nowiki>
receipt title/type
sellers details (hCard candidate)
org
url
phone
message
receipt number
date
amount
information
</nowiki></pre>

==== A1Books ====
[http://mobileonlinebusiness.com.au/uf/receipt/A1Books-Sales-Order-anon.htm Example]

*vendor
**name
**fax
*date
*order number
*shipping address
*billing address
*items
**description
**list price
**sale price
**quantity
**amount
*subtotal
*shipping
*total
**quantity
**amount
*account information
**phone
**e-mail
*payment
**method
**last four digits

No semantic HTML.

Notes:
*Supports one seller per item.
*Does not display tax.

==== Barnes&Noble ====
[http://mobileonlinebusiness.com.au/uf/receipt/BarnesAndNoble.com-receipt.anon.tidied.htm Example]

*date
*shipping address
*billing address
*payment
**method
**last 4 digits
**exp. date
**charge
*savings on shipping
*order no.
*delivery option
*items
**description: title, author, ISBN, price
**qty
**gift options: wrap, message
**total price
*shipment subtotal
*shipping cost
*tax
*shipment total (seems to account for orders requiring multiple shipments)
*order total

Semantic HTML:
*receiptOrderNumbers
*receiptOrderPlacedOn
*orderInformation
**shippingAddress
**billingAddress
**paymentInformation
*shippingSelections
*showProducts
**reviewTable
***qtyValuePosition
***reviewGiftOptions
*reviewTotalsDisplay
**reviewTotalsSummary
**reviewTotalsNote
**reviewTotalsBreakdown
*reviewTotalsSummary
**reviewGrandTotal
*reviewCreditCardCharged
*review

The semantic class names found are a good start, although the "review" part appears to be context-specific (reviewing an order). Additionally, the implied hierarchy in names such as "reviewTotalsSummary" and "receiptOrderPlacedOn" is probably unnecessary for our purposes.

Notes:
*Supports multiple shipments.
*Gift options.
*Explicitly stated credit-card charge.

==== Facebook ====
[http://mobileonlinebusiness.com.au/uf/receipt/Facebook-gift-receipt.html Example]

*purchase total
*items (informal description of two items, including quantity)
*recipient name
*order id
*billed-to name

No relevant semantic HTML.

Notes:
*Quite minimal and informal receipt. Good example of how a microformat would preserve human readability and informal style while enabling machine reading.

==== Google Checkout ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Google-Checkout-e-mail-receipt.tidied.html Example email receipt]
*[http://mobileonlinebusiness.com.au/uf/receipt/Google-Checkout-Order-Receipt_DVD-Empire.tidied.htm Example web receipt]

*vendor address
*shipping address
*date
*order id
*items
**shipping status ("Not yet shipped", etc.)
**qty.
**description
**price
*shipping cost
*tax
*total
*order history (placed, received, charged, shipped) (web receipt only)
*payment info (web receipt only)
**card type
**last 4 digits
**exp. date
**cardholder address
*permalink

Semantic HTML:
*taxRow
**taxIdentifier
**taxAmount
*totalAmount

Notes:
*Explicit seller address (one per order).
*Current shipping status of each item.
*E-mail receipt has permalink.
*Order history (date placed, received, charged, shipped).

==== iTunes ====
*[http://mobileonlinebusiness.com.au/uf/receipt/iTunes-receipt-e-mail.html iTunes e-mail receipt]

*billing address
*order no.
*receipt date
*order total
*card
**type
**last 4 digits
*item
**item no.
**description (including link to write a review)
**unit price
*subtotal
*tax

No relevant semantic HTML.

Notes:
*No quantity information.

==== Longs/FujiFilm ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Longs-Fujifilm-photo-receipt.html Longs/Fujifilm e-mail receipt]

*order no.
*payment info
**method (COD, credit card, etc.)
*customer address
*pickup address
*items
**name
**qty.
**description
**price
**line item subtotal
*order items total
*tax
*order total

Semantic HTML:
*payment-heading

Notes:
*No order date; has pick-up date instead.
*Has pickup address rather than shipping address.

==== Mobivox/PayPal ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Mobivox-PayPal.htm Mobivox/PayPal receipt]
*[http://mobileonlinebusiness.com.au/uf/receipt/Mobivox-PayPal-printable.htm Mobivox/PayPal printable receipt]

*seller address
*receipt id
*date of order
*items
**description
**item option (not quite sure what this is for)
**unit price
**qty
**total
*subtotal
*tax
*total amount
*payment info
**method
**last 4 digits
**charge
**appears on bill/statement as "MOBIVOXCORP"
*buyer contact

Relevant semantic HTML:
*order-summary
**cart
***(unnamed tr)
****item-name
****item-total
****item-option (not quite sure what this is for)
**subtotal
**totals-value
**totals-currency
**purchase-summary
***summary-total
****price-total
****price-currency
*funding-mix
**payment-type
**amount
**ccStatement
*contact-information (contains hCard microformat)

This semantic HTML is the most complete and well-thought-out I've seen in this analysis. It even makes use of the fieldset element in forms, something I've never seen before.[[User:Lastorset|Lastorset]] 16:21, 25 Jul 2007 (PDT)

Microformats used:
*hCard (non-compliant due to missing formatted name): buyer contact info

Notes:
*Explicitly stated credit-card charge.
*Displayed credit-card-statement reference.
*Explicitly displayed seller address (one seller per order).

==== Symantec ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Symantec-reminder-e-mail.html Symantec e-mail reminder]

*buyer name
*date
*payment method
*last 4 digits
*appears on statement as "DR *Symantec"
*items
**qty
**product name
**platform
**delivery method
**price
*subtotal
*grand total
*permalink

No relevant semantic HTML

=== Analysis ===

==== Analysis of Bills ====

==== Analysis of Receipts ====

== Existing Practices ==

Listed below is an overview of existing patterns and practices found in the wild for bill and receipt data.

===Summary of common patterns discovered===

===Other attempts to solve The Problem===
For paper receipts, [http://www.neatreceipts.com/ NeatReceipts Scanalizer] offers a heuristic-based solution.

== Proposal ==

== See Also ==
* [[receipt]]
* http://en.wikipedia.org/wiki/Receipt

receipt-examples

2007-08-16T23:43:05Z

Lastorset: /* Barnes&Noble */ Notable results from group analysis

= Receipt =

Overview of Receipt exploratory discussion goes here...

== Authors ==

=== Contributors ===
Rob Manson

== Real-World Examples ==

=== Bill / Invoice ===

Bills or Invoices are "yet to be paid" items.

Question: Perhaps these examples (yet to be provided) should be moved to a separate page as Bill/Invoice is quite different from Receipt.

: With [[hResume]], I've [[hresume-brainstorming|suggested]] that the subtle difference between actively seeking work and just presenting your resume be a case of including [[hlisting]] markup.
: With bills vs invoices, it may turn out that the content found within would be identical, and it might just be a case of putting in a class flag to indicate whether the presented document has been paid for or not.
: [[User:SignpostMarv|SignpostMarv]] 12:55, 21 Jul 2007 (PDT)

::I think a class flag is a great idea, but I don't believe we have any samples for invoices. However, if we look at order review vs. order summary rather than invoices vs. receipts, the payment flag does become relevant in many of the sampled online stores.
::How would such a flag be implemented?
::*<code><nowiki><div class="hreceipt unpaid"/"hreceipt paid">...</nowiki></code>
::*<code><nowiki><div class="hreceipt" title="paid">...</div></nowiki></code>
::[[User:Lastorset|Lastorset]] 14:55, 16 Aug 2007 (PDT)

=== Receipts ===

Receipts are post-purchase items.

==== Amazon ====
* [http://mobileonlinebusiness.com.au/uf/receipt/Amazon.com-Vieworder-anon.htm Example]
* contains:
**<del>email address</del> (could not find in examples)
**date of order
**order id
**shipments
***shipping estimate
***delivery estimate
***shipping address
***shipping speed
***shipping preference (item grouping)
***items
****quantity
****seller
****price
****item information
**payment
***card type
***last 5 digits
***expiration date
***billing address
***subtotal
***shipping and handling price
***total before tax
***tax
***grand total
**<del>discount price</del> (could not find in examples)
* Little semantic HTML of interest, except an anchor with id "payment-info"

Notes:
*Supports multiple shipments.
*Supports one seller per item.
*Displays shipping and delivery estimate.
*Offers item grouping preference.
*Gift options.

==== Skype ====

===== Skype Phone =====
*[[receipt-example-skype-phone|example source code]]
*[http://mobileonlinebusiness.com.au/uf/receipt/Skype-order-history.html Skype order history]

* Shipping Address
* date in dd/mm/yyyy format
* Order number in nnnn-nnnnnnn-nnn format
* Reference (was blank in example, presumed to appear on bank statement for this transaction)
* Items
** Quantity
** Description
** Price
** Total
** VAT (tax) %
* Payment
** subtotal ("total")
** shipping cost
** grand total ("total (gross)")
** total (VAT excluded)
** VAT (amount)
* Chosen payment method: "Your payment method is: Credit card"
* Legal blurb

Semantic HTML:
* Order resume class="order-listing"
* Each item class="row"
* All totals rows class="totals-row" except grand total class="grandtotal-row"

==== Internet banking transaction receipts ====
===== Example 1 =====
<pre><nowiki>
receipt number
date
time
receipt type (e.g. TRANSFER BETWEEN MY ACCOUNTS)
transfer from
transfer to
amount
description
information/comment
</nowiki></pre>

==== Digital product purchase receipts ====
===== Example 1 : Software =====
<pre><nowiki>
receipt title/type
order/receipt number
seller's details
sold by (hCard candidate)
org
adr
tax number (VAT in this example)
tax id (Federal Tax ID)
buyer's details
buyer (hCard candidate)
name
org
street-address
locality
region
postal-code
country-name
tel
email
credit card number (PAN truncated - with type)
item list
product code
name
comments
price
delivery method
quantity
total in selected currency
total in sellers currency
total (sum of item list totals)
processing fee
grand total (final amount charged)
information (caveats and tax info)
permalink
</nowiki></pre>

===== Example 2 : SSL certificate =====
<pre><nowiki>
receipt title/type
seller (hCard candidate)
org
street-address
locality
region
postal-code
purchase information
order id
product name
domain name
validity period
number of licenses
card number (PAN truncated)
amount (with selected currency)
</nowiki></pre>

==== Physical product purchase receipts ====
===== Example 1 : Computer hardware =====
<pre><nowiki>
receipt title/type
seller's name (hCard candidate)
seller's URL (hCard candidate)
invoice id
org govt reference (ABN - Australian Business Number)
date
seller details (hCard candidate)
street-address
locality
region
postal-code
buyer (hCard candidate)
fn
billing address
street-address
locality
region
postal-code
delivery address
street-address
locality
region
postal-code
phone
item list
item
description
amount
quantity
product url
total
delivery cost
total excluding tax
tax (GST - Goods and Service Tax)
total including tax
</nowiki></pre>

==== Service purchase receipts ====
===== Example 1 : Online subscription =====
<pre><nowiki>
seller's details (hCard candidate)
org
street-address
locality
region
postal-code
country-name
buyer's details (hCard candidate)
fn
street-address
locality
region
postal-code
phone
date
receipt id
item list
product description
quantity
rate (per unit)
price
sub total
amount paid
balance due
information
transaction id
</nowiki></pre>

===== Example 2 : Co-location =====
<pre><nowiki>
receipt title/type
sellers details (hCard candidate)
org
url
phone
message
receipt number
date
amount
information
</nowiki></pre>

==== A1Books ====
[http://mobileonlinebusiness.com.au/uf/receipt/A1Books-Sales-Order-anon.htm Example]

*vendor
**name
**fax
*date
*order number
*shipping address
*billing address
*items
**description
**list price
**sale price
**quantity
**amount
*subtotal
*shipping
*total
**quantity
**amount
*account information
**phone
**e-mail
*payment
**method
**last four digits

No semantic HTML.

Notes:
*Supports one seller per item.
*Does not display tax.

==== Barnes&Noble ====
[http://mobileonlinebusiness.com.au/uf/receipt/BarnesAndNoble.com-receipt.anon.tidied.htm Example]

*date
*shipping address
*billing address
*payment
**method
**last 4 digits
**exp. date
**charge
*savings on shipping
*order no.
*delivery option
*items
**description: title, author, ISBN, price
**qty
**gift options: wrap, message
**total price
*shipment subtotal
*shipping cost
*tax
*shipment total (seems to account for orders requiring multiple shipments)
*order total

Semantic HTML:
*receiptOrderNumbers
*receiptOrderPlacedOn
*orderInformation
**shippingAddress
**billingAddress
**paymentInformation
*shippingSelections
*showProducts
**reviewTable
***qtyValuePosition
***reviewGiftOptions
*reviewTotalsDisplay
**reviewTotalsSummary
**reviewTotalsNote
**reviewTotalsBreakdown
*reviewTotalsSummary
**reviewGrandTotal
*reviewCreditCardCharged
*review

The semantic class names found are a good start, although the "review" part appears to be context-specific (reviewing an order). Additionally, the implied hierarchy in names such as "reviewTotalsSummary" and "receiptOrderPlacedOn" is probably unnecessary for our purposes.

Notes:
*Supports multiple shipments.
*Gift options.
*Explicitly stated credit-card charge.

==== Facebook ====
[http://mobileonlinebusiness.com.au/uf/receipt/Facebook-gift-receipt.html Example]

*purchase total
*items (informal description of two items, including quantity)
*recipient name
*order id
*billed-to name

No relevant semantic HTML.

Notes:
*Quite minimal and informal receipt. Good example of how a microformat would preserve human readability and informal style while enabling machine reading.

==== Google Checkout ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Google-Checkout-e-mail-receipt.tidied.html Example email receipt]
*[http://mobileonlinebusiness.com.au/uf/receipt/Google-Checkout-Order-Receipt_DVD-Empire.tidied.htm Example web receipt]

*vendor address
*shipping address
*date
*order id
*items
**shipping status ("Not yet shipped", etc.)
**qty.
**description
**price
*shipping cost
*tax
*total
*order history (placed, received, charged, shipped) (web receipt only)
*payment info (web receipt only)
**card type
**last 4 digits
**exp. date
**cardholder address
*permalink

Semantic HTML:
*taxRow
**taxIdentifier
**taxAmount
*totalAmount

Notes:
*Explicit seller address (one per order).
*Current shipping status of each item.
*E-mail receipt has permalink.
*Order history (date placed, received, charged, shipped).

==== iTunes ====
*[http://mobileonlinebusiness.com.au/uf/receipt/iTunes-receipt-e-mail.html iTunes e-mail receipt]

*billing address
*order no.
*receipt date
*order total
*card
**type
**last 4 digits
*item
**item no.
**description (including link to write a review)
**unit price
*subtotal
*tax

No relevant semantic HTML.

Notes:
*No quantity information.

==== Longs/FujiFilm ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Longs-Fujifilm-photo-receipt.html Longs/Fujifilm e-mail receipt]

*order no.
*payment info
**method (COD, credit card, etc.)
*customer address
*pickup address
*items
**name
**qty.
**description
**price
**line item subtotal
*order items total
*tax
*order total

Semantic HTML:
*payment-heading

Notes:
*No order date; has pick-up date instead.
*Has pickup address rather than shipping address.

==== Mobivox/PayPal ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Mobivox-PayPal.htm Mobivox/PayPal receipt]
*[http://mobileonlinebusiness.com.au/uf/receipt/Mobivox-PayPal-printable.htm Mobivox/PayPal printable receipt]

*seller address
*receipt id
*date of order
*items
**description
**item option (not quite sure what this is for)
**unit price
**qty
**total
*subtotal
*tax
*total amount
*payment info
**method
**last 4 digits
**charge
**appears on bill/statement as "MOBIVOXCORP"
*buyer contact

Relevant semantic HTML:
*order-summary
**cart
***(unnamed tr)
****item-name
****item-total
****item-option (not quite sure what this is for)
**subtotal
**totals-value
**totals-currency
**purchase-summary
***summary-total
****price-total
****price-currency
*funding-mix
**payment-type
**amount
**ccStatement
*contact-information (contains hCard microformat)

This semantic HTML is the most complete and well-thought-out I've seen in this analysis. It even makes use of the fieldset element in forms, something I've never seen before.[[User:Lastorset|Lastorset]] 16:21, 25 Jul 2007 (PDT)

Microformats used:
*hCard (non-compliant due to missing formatted name): buyer contact info

==== Symantec ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Symantec-reminder-e-mail.html Symantec e-mail reminder]

*buyer name
*date
*payment method
*last 4 digits
*appears on statement as "DR *Symantec"
*items
**qty
**product name
**platform
**delivery method
**price
*subtotal
*grand total
*permalink

No relevant semantic HTML

=== Analysis ===

==== Analysis of Bills ====

==== Analysis of Receipts ====

== Existing Practices ==

Listed below is an overview of existing patterns and practices found in the wild for bill and receipt data.

===Summary of common patterns discovered===

===Other attempts to solve The Problem===
For paper receipts, [http://www.neatreceipts.com/ NeatReceipts Scanalizer] offers a heuristic-based solution.

== Proposal ==

== See Also ==
* [[receipt]]
* http://en.wikipedia.org/wiki/Receipt

receipt-examples

2007-08-16T23:42:17Z

Lastorset: /* Longs/FujiFilm */ Notable results from group analysis

= Receipt =

Overview of Receipt exploratory discussion goes here...

== Authors ==

=== Contributors ===
Rob Manson

== Real-World Examples ==

=== Bill / Invoice ===

Bills or Invoices are "yet to be paid" items.

Question: Perhaps these examples (yet to be provided) should be moved to a separate page as Bill/Invoice is quite different from Receipt.

: With [[hResume]], I've [[hresume-brainstorming|suggested]] that the subtle difference between actively seeking work and just presenting your resume be a case of including [[hlisting]] markup.
: With bills vs invoices, it may turn out that the content found within would be identical, and it might just be a case of putting in a class flag to indicate whether the presented document has been paid for or not.
: [[User:SignpostMarv|SignpostMarv]] 12:55, 21 Jul 2007 (PDT)

::I think a class flag is a great idea, but I don't believe we have any samples for invoices. However, if we look at order review vs. order summary rather than invoices vs. receipts, the payment flag does become relevant in many of the sampled online stores.
::How would such a flag be implemented?
::*<code><nowiki><div class="hreceipt unpaid"/"hreceipt paid">...</nowiki></code>
::*<code><nowiki><div class="hreceipt" title="paid">...</div></nowiki></code>
::[[User:Lastorset|Lastorset]] 14:55, 16 Aug 2007 (PDT)

=== Receipts ===

Receipts are post-purchase items.

==== Amazon ====
* [http://mobileonlinebusiness.com.au/uf/receipt/Amazon.com-Vieworder-anon.htm Example]
* contains:
**<del>email address</del> (could not find in examples)
**date of order
**order id
**shipments
***shipping estimate
***delivery estimate
***shipping address
***shipping speed
***shipping preference (item grouping)
***items
****quantity
****seller
****price
****item information
**payment
***card type
***last 5 digits
***expiration date
***billing address
***subtotal
***shipping and handling price
***total before tax
***tax
***grand total
**<del>discount price</del> (could not find in examples)
* Little semantic HTML of interest, except an anchor with id "payment-info"

Notes:
*Supports multiple shipments.
*Supports one seller per item.
*Displays shipping and delivery estimate.
*Offers item grouping preference.
*Gift options.

==== Skype ====

===== Skype Phone =====
*[[receipt-example-skype-phone|example source code]]
*[http://mobileonlinebusiness.com.au/uf/receipt/Skype-order-history.html Skype order history]

* Shipping Address
* date in dd/mm/yyyy format
* Order number in nnnn-nnnnnnn-nnn format
* Reference (was blank in example, presumed to appear on bank statement for this transaction)
* Items
** Quantity
** Description
** Price
** Total
** VAT (tax) %
* Payment
** subtotal ("total")
** shipping cost
** grand total ("total (gross)")
** total (VAT excluded)
** VAT (amount)
* Chosen payment method: "Your payment method is: Credit card"
* Legal blurb

Semantic HTML:
* Order resume class="order-listing"
* Each item class="row"
* All totals rows class="totals-row" except grand total class="grandtotal-row"

==== Internet banking transaction receipts ====
===== Example 1 =====
<pre><nowiki>
receipt number
date
time
receipt type (e.g. TRANSFER BETWEEN MY ACCOUNTS)
transfer from
transfer to
amount
description
information/comment
</nowiki></pre>

==== Digital product purchase receipts ====
===== Example 1 : Software =====
<pre><nowiki>
receipt title/type
order/receipt number
seller's details
sold by (hCard candidate)
org
adr
tax number (VAT in this example)
tax id (Federal Tax ID)
buyer's details
buyer (hCard candidate)
name
org
street-address
locality
region
postal-code
country-name
tel
email
credit card number (PAN truncated - with type)
item list
product code
name
comments
price
delivery method
quantity
total in selected currency
total in sellers currency
total (sum of item list totals)
processing fee
grand total (final amount charged)
information (caveats and tax info)
permalink
</nowiki></pre>

===== Example 2 : SSL certificate =====
<pre><nowiki>
receipt title/type
seller (hCard candidate)
org
street-address
locality
region
postal-code
purchase information
order id
product name
domain name
validity period
number of licenses
card number (PAN truncated)
amount (with selected currency)
</nowiki></pre>

==== Physical product purchase receipts ====
===== Example 1 : Computer hardware =====
<pre><nowiki>
receipt title/type
seller's name (hCard candidate)
seller's URL (hCard candidate)
invoice id
org govt reference (ABN - Australian Business Number)
date
seller details (hCard candidate)
street-address
locality
region
postal-code
buyer (hCard candidate)
fn
billing address
street-address
locality
region
postal-code
delivery address
street-address
locality
region
postal-code
phone
item list
item
description
amount
quantity
product url
total
delivery cost
total excluding tax
tax (GST - Goods and Service Tax)
total including tax
</nowiki></pre>

==== Service purchase receipts ====
===== Example 1 : Online subscription =====
<pre><nowiki>
seller's details (hCard candidate)
org
street-address
locality
region
postal-code
country-name
buyer's details (hCard candidate)
fn
street-address
locality
region
postal-code
phone
date
receipt id
item list
product description
quantity
rate (per unit)
price
sub total
amount paid
balance due
information
transaction id
</nowiki></pre>

===== Example 2 : Co-location =====
<pre><nowiki>
receipt title/type
sellers details (hCard candidate)
org
url
phone
message
receipt number
date
amount
information
</nowiki></pre>

==== A1Books ====
[http://mobileonlinebusiness.com.au/uf/receipt/A1Books-Sales-Order-anon.htm Example]

*vendor
**name
**fax
*date
*order number
*shipping address
*billing address
*items
**description
**list price
**sale price
**quantity
**amount
*subtotal
*shipping
*total
**quantity
**amount
*account information
**phone
**e-mail
*payment
**method
**last four digits

No semantic HTML.

Notes:
*Supports one seller per item.
*Does not display tax.

==== Barnes&Noble ====
[http://mobileonlinebusiness.com.au/uf/receipt/BarnesAndNoble.com-receipt.anon.tidied.htm Example]

*date
*shipping address
*billing address
*payment
**method
**last 4 digits
**exp. date
**charge
*savings on shipping
*order no.
*delivery option
*items
**description: title, author, ISBN, price
**qty
**gift options: wrap, message
**total price
*shipment subtotal
*shipping cost
*tax
*shipment total (seems to account for orders requiring multiple shipments)
*order total

Semantic HTML:
*receiptOrderNumbers
*receiptOrderPlacedOn
*orderInformation
**shippingAddress
**billingAddress
**paymentInformation
*shippingSelections
*showProducts
**reviewTable
***qtyValuePosition
***reviewGiftOptions
*reviewTotalsDisplay
**reviewTotalsSummary
**reviewTotalsNote
**reviewTotalsBreakdown
*reviewTotalsSummary
**reviewGrandTotal
*reviewCreditCardCharged
*review

The semantic class names found are a good start, although the "review" part appears to be context-specific (reviewing an order). Additionally, the implied hierarchy in names such as "reviewTotalsSummary" and "receiptOrderPlacedOn" is probably unnecessary for our purposes.

Notes:
*Supports multiple shipments.
*Gift options.

==== Facebook ====
[http://mobileonlinebusiness.com.au/uf/receipt/Facebook-gift-receipt.html Example]

*purchase total
*items (informal description of two items, including quantity)
*recipient name
*order id
*billed-to name

No relevant semantic HTML.

Notes:
*Quite minimal and informal receipt. Good example of how a microformat would preserve human readability and informal style while enabling machine reading.

==== Google Checkout ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Google-Checkout-e-mail-receipt.tidied.html Example email receipt]
*[http://mobileonlinebusiness.com.au/uf/receipt/Google-Checkout-Order-Receipt_DVD-Empire.tidied.htm Example web receipt]

*vendor address
*shipping address
*date
*order id
*items
**shipping status ("Not yet shipped", etc.)
**qty.
**description
**price
*shipping cost
*tax
*total
*order history (placed, received, charged, shipped) (web receipt only)
*payment info (web receipt only)
**card type
**last 4 digits
**exp. date
**cardholder address
*permalink

Semantic HTML:
*taxRow
**taxIdentifier
**taxAmount
*totalAmount

Notes:
*Explicit seller address (one per order).
*Current shipping status of each item.
*E-mail receipt has permalink.
*Order history (date placed, received, charged, shipped).

==== iTunes ====
*[http://mobileonlinebusiness.com.au/uf/receipt/iTunes-receipt-e-mail.html iTunes e-mail receipt]

*billing address
*order no.
*receipt date
*order total
*card
**type
**last 4 digits
*item
**item no.
**description (including link to write a review)
**unit price
*subtotal
*tax

No relevant semantic HTML.

Notes:
*No quantity information.

==== Longs/FujiFilm ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Longs-Fujifilm-photo-receipt.html Longs/Fujifilm e-mail receipt]

*order no.
*payment info
**method (COD, credit card, etc.)
*customer address
*pickup address
*items
**name
**qty.
**description
**price
**line item subtotal
*order items total
*tax
*order total

Semantic HTML:
*payment-heading

Notes:
*No order date; has pick-up date instead.
*Has pickup address rather than shipping address.

==== Mobivox/PayPal ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Mobivox-PayPal.htm Mobivox/PayPal receipt]
*[http://mobileonlinebusiness.com.au/uf/receipt/Mobivox-PayPal-printable.htm Mobivox/PayPal printable receipt]

*seller address
*receipt id
*date of order
*items
**description
**item option (not quite sure what this is for)
**unit price
**qty
**total
*subtotal
*tax
*total amount
*payment info
**method
**last 4 digits
**charge
**appears on bill/statement as "MOBIVOXCORP"
*buyer contact

Relevant semantic HTML:
*order-summary
**cart
***(unnamed tr)
****item-name
****item-total
****item-option (not quite sure what this is for)
**subtotal
**totals-value
**totals-currency
**purchase-summary
***summary-total
****price-total
****price-currency
*funding-mix
**payment-type
**amount
**ccStatement
*contact-information (contains hCard microformat)

This semantic HTML is the most complete and well-thought-out I've seen in this analysis. It even makes use of the fieldset element in forms, something I've never seen before.[[User:Lastorset|Lastorset]] 16:21, 25 Jul 2007 (PDT)

Microformats used:
*hCard (non-compliant due to missing formatted name): buyer contact info

==== Symantec ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Symantec-reminder-e-mail.html Symantec e-mail reminder]

*buyer name
*date
*payment method
*last 4 digits
*appears on statement as "DR *Symantec"
*items
**qty
**product name
**platform
**delivery method
**price
*subtotal
*grand total
*permalink

No relevant semantic HTML

=== Analysis ===

==== Analysis of Bills ====

==== Analysis of Receipts ====

== Existing Practices ==

Listed below is an overview of existing patterns and practices found in the wild for bill and receipt data.

===Summary of common patterns discovered===

===Other attempts to solve The Problem===
For paper receipts, [http://www.neatreceipts.com/ NeatReceipts Scanalizer] offers a heuristic-based solution.

== Proposal ==

== See Also ==
* [[receipt]]
* http://en.wikipedia.org/wiki/Receipt

receipt-examples

2007-08-16T23:39:14Z

Lastorset: /* iTunes */ Notable results from group analysis

= Receipt =

Overview of Receipt exploratory discussion goes here...

== Authors ==

=== Contributors ===
Rob Manson

== Real-World Examples ==

=== Bill / Invoice ===

Bills or Invoices are "yet to be paid" items.

Question: Perhaps these examples (yet to be provided) should be moved to a separate page as Bill/Invoice is quite different from Receipt.

: With [[hResume]], I've [[hresume-brainstorming|suggested]] that the subtle difference between actively seeking work and just presenting your resume be a case of including [[hlisting]] markup.
: With bills vs invoices, it may turn out that the content found within would be identical, and it might just be a case of putting in a class flag to indicate whether the presented document has been paid for or not.
: [[User:SignpostMarv|SignpostMarv]] 12:55, 21 Jul 2007 (PDT)

::I think a class flag is a great idea, but I don't believe we have any samples for invoices. However, if we look at order review vs. order summary rather than invoices vs. receipts, the payment flag does become relevant in many of the sampled online stores.
::How would such a flag be implemented?
::*<code><nowiki><div class="hreceipt unpaid"/"hreceipt paid">...</nowiki></code>
::*<code><nowiki><div class="hreceipt" title="paid">...</div></nowiki></code>
::[[User:Lastorset|Lastorset]] 14:55, 16 Aug 2007 (PDT)

=== Receipts ===

Receipts are post-purchase items.

==== Amazon ====
* [http://mobileonlinebusiness.com.au/uf/receipt/Amazon.com-Vieworder-anon.htm Example]
* contains:
**<del>email address</del> (could not find in examples)
**date of order
**order id
**shipments
***shipping estimate
***delivery estimate
***shipping address
***shipping speed
***shipping preference (item grouping)
***items
****quantity
****seller
****price
****item information
**payment
***card type
***last 5 digits
***expiration date
***billing address
***subtotal
***shipping and handling price
***total before tax
***tax
***grand total
**<del>discount price</del> (could not find in examples)
* Little semantic HTML of interest, except an anchor with id "payment-info"

Notes:
*Supports multiple shipments.
*Supports one seller per item.
*Displays shipping and delivery estimate.
*Offers item grouping preference.
*Gift options.

==== Skype ====

===== Skype Phone =====
*[[receipt-example-skype-phone|example source code]]
*[http://mobileonlinebusiness.com.au/uf/receipt/Skype-order-history.html Skype order history]

* Shipping Address
* date in dd/mm/yyyy format
* Order number in nnnn-nnnnnnn-nnn format
* Reference (was blank in example, presumed to appear on bank statement for this transaction)
* Items
** Quantity
** Description
** Price
** Total
** VAT (tax) %
* Payment
** subtotal ("total")
** shipping cost
** grand total ("total (gross)")
** total (VAT excluded)
** VAT (amount)
* Chosen payment method: "Your payment method is: Credit card"
* Legal blurb

Semantic HTML:
* Order resume class="order-listing"
* Each item class="row"
* All totals rows class="totals-row" except grand total class="grandtotal-row"

==== Internet banking transaction receipts ====
===== Example 1 =====
<pre><nowiki>
receipt number
date
time
receipt type (e.g. TRANSFER BETWEEN MY ACCOUNTS)
transfer from
transfer to
amount
description
information/comment
</nowiki></pre>

==== Digital product purchase receipts ====
===== Example 1 : Software =====
<pre><nowiki>
receipt title/type
order/receipt number
seller's details
sold by (hCard candidate)
org
adr
tax number (VAT in this example)
tax id (Federal Tax ID)
buyer's details
buyer (hCard candidate)
name
org
street-address
locality
region
postal-code
country-name
tel
email
credit card number (PAN truncated - with type)
item list
product code
name
comments
price
delivery method
quantity
total in selected currency
total in sellers currency
total (sum of item list totals)
processing fee
grand total (final amount charged)
information (caveats and tax info)
permalink
</nowiki></pre>

===== Example 2 : SSL certificate =====
<pre><nowiki>
receipt title/type
seller (hCard candidate)
org
street-address
locality
region
postal-code
purchase information
order id
product name
domain name
validity period
number of licenses
card number (PAN truncated)
amount (with selected currency)
</nowiki></pre>

==== Physical product purchase receipts ====
===== Example 1 : Computer hardware =====
<pre><nowiki>
receipt title/type
seller's name (hCard candidate)
seller's URL (hCard candidate)
invoice id
org govt reference (ABN - Australian Business Number)
date
seller details (hCard candidate)
street-address
locality
region
postal-code
buyer (hCard candidate)
fn
billing address
street-address
locality
region
postal-code
delivery address
street-address
locality
region
postal-code
phone
item list
item
description
amount
quantity
product url
total
delivery cost
total excluding tax
tax (GST - Goods and Service Tax)
total including tax
</nowiki></pre>

==== Service purchase receipts ====
===== Example 1 : Online subscription =====
<pre><nowiki>
seller's details (hCard candidate)
org
street-address
locality
region
postal-code
country-name
buyer's details (hCard candidate)
fn
street-address
locality
region
postal-code
phone
date
receipt id
item list
product description
quantity
rate (per unit)
price
sub total
amount paid
balance due
information
transaction id
</nowiki></pre>

===== Example 2 : Co-location =====
<pre><nowiki>
receipt title/type
sellers details (hCard candidate)
org
url
phone
message
receipt number
date
amount
information
</nowiki></pre>

==== A1Books ====
[http://mobileonlinebusiness.com.au/uf/receipt/A1Books-Sales-Order-anon.htm Example]

*vendor
**name
**fax
*date
*order number
*shipping address
*billing address
*items
**description
**list price
**sale price
**quantity
**amount
*subtotal
*shipping
*total
**quantity
**amount
*account information
**phone
**e-mail
*payment
**method
**last four digits

No semantic HTML.

Notes:
*Supports one seller per item.
*Does not display tax.

==== Barnes&Noble ====
[http://mobileonlinebusiness.com.au/uf/receipt/BarnesAndNoble.com-receipt.anon.tidied.htm Example]

*date
*shipping address
*billing address
*payment
**method
**last 4 digits
**exp. date
**charge
*savings on shipping
*order no.
*delivery option
*items
**description: title, author, ISBN, price
**qty
**gift options: wrap, message
**total price
*shipment subtotal
*shipping cost
*tax
*shipment total (seems to account for orders requiring multiple shipments)
*order total

Semantic HTML:
*receiptOrderNumbers
*receiptOrderPlacedOn
*orderInformation
**shippingAddress
**billingAddress
**paymentInformation
*shippingSelections
*showProducts
**reviewTable
***qtyValuePosition
***reviewGiftOptions
*reviewTotalsDisplay
**reviewTotalsSummary
**reviewTotalsNote
**reviewTotalsBreakdown
*reviewTotalsSummary
**reviewGrandTotal
*reviewCreditCardCharged
*review

The semantic class names found are a good start, although the "review" part appears to be context-specific (reviewing an order). Additionally, the implied hierarchy in names such as "reviewTotalsSummary" and "receiptOrderPlacedOn" is probably unnecessary for our purposes.

Notes:
*Supports multiple shipments.
*Gift options.

==== Facebook ====
[http://mobileonlinebusiness.com.au/uf/receipt/Facebook-gift-receipt.html Example]

*purchase total
*items (informal description of two items, including quantity)
*recipient name
*order id
*billed-to name

No relevant semantic HTML.

Notes:
*Quite minimal and informal receipt. Good example of how a microformat would preserve human readability and informal style while enabling machine reading.

==== Google Checkout ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Google-Checkout-e-mail-receipt.tidied.html Example email receipt]
*[http://mobileonlinebusiness.com.au/uf/receipt/Google-Checkout-Order-Receipt_DVD-Empire.tidied.htm Example web receipt]

*vendor address
*shipping address
*date
*order id
*items
**shipping status ("Not yet shipped", etc.)
**qty.
**description
**price
*shipping cost
*tax
*total
*order history (placed, received, charged, shipped) (web receipt only)
*payment info (web receipt only)
**card type
**last 4 digits
**exp. date
**cardholder address
*permalink

Semantic HTML:
*taxRow
**taxIdentifier
**taxAmount
*totalAmount

Notes:
*Explicit seller address (one per order).
*Current shipping status of each item.
*E-mail receipt has permalink.
*Order history (date placed, received, charged, shipped).

==== iTunes ====
*[http://mobileonlinebusiness.com.au/uf/receipt/iTunes-receipt-e-mail.html iTunes e-mail receipt]

*billing address
*order no.
*receipt date
*order total
*card
**type
**last 4 digits
*item
**item no.
**description (including link to write a review)
**unit price
*subtotal
*tax

No relevant semantic HTML.

Notes:
*No quantity information.

==== Longs/FujiFilm ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Longs-Fujifilm-photo-receipt.html Longs/Fujifilm e-mail receipt]

*order no.
*payment info
**method (COD, credit card, etc.)
*customer address
*pickup address
*items
**name
**qty.
**description
**price
**line item subtotal
*order items total
*tax
*order total

Semantic HTML:
*payment-heading

==== Mobivox/PayPal ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Mobivox-PayPal.htm Mobivox/PayPal receipt]
*[http://mobileonlinebusiness.com.au/uf/receipt/Mobivox-PayPal-printable.htm Mobivox/PayPal printable receipt]

*seller address
*receipt id
*date of order
*items
**description
**item option (not quite sure what this is for)
**unit price
**qty
**total
*subtotal
*tax
*total amount
*payment info
**method
**last 4 digits
**charge
**appears on bill/statement as "MOBIVOXCORP"
*buyer contact

Relevant semantic HTML:
*order-summary
**cart
***(unnamed tr)
****item-name
****item-total
****item-option (not quite sure what this is for)
**subtotal
**totals-value
**totals-currency
**purchase-summary
***summary-total
****price-total
****price-currency
*funding-mix
**payment-type
**amount
**ccStatement
*contact-information (contains hCard microformat)

This semantic HTML is the most complete and well-thought-out I've seen in this analysis. It even makes use of the fieldset element in forms, something I've never seen before.[[User:Lastorset|Lastorset]] 16:21, 25 Jul 2007 (PDT)

Microformats used:
*hCard (non-compliant due to missing formatted name): buyer contact info

==== Symantec ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Symantec-reminder-e-mail.html Symantec e-mail reminder]

*buyer name
*date
*payment method
*last 4 digits
*appears on statement as "DR *Symantec"
*items
**qty
**product name
**platform
**delivery method
**price
*subtotal
*grand total
*permalink

No relevant semantic HTML

=== Analysis ===

==== Analysis of Bills ====

==== Analysis of Receipts ====

== Existing Practices ==

Listed below is an overview of existing patterns and practices found in the wild for bill and receipt data.

===Summary of common patterns discovered===

===Other attempts to solve The Problem===
For paper receipts, [http://www.neatreceipts.com/ NeatReceipts Scanalizer] offers a heuristic-based solution.

== Proposal ==

== See Also ==
* [[receipt]]
* http://en.wikipedia.org/wiki/Receipt

receipt-examples

2007-08-16T23:38:19Z

Lastorset: /* Google Checkout */ Notable results from group analysis

= Receipt =

Overview of Receipt exploratory discussion goes here...

== Authors ==

=== Contributors ===
Rob Manson

== Real-World Examples ==

=== Bill / Invoice ===

Bills or Invoices are "yet to be paid" items.

Question: Perhaps these examples (yet to be provided) should be moved to a separate page as Bill/Invoice is quite different from Receipt.

: With [[hResume]], I've [[hresume-brainstorming|suggested]] that the subtle difference between actively seeking work and just presenting your resume be a case of including [[hlisting]] markup.
: With bills vs invoices, it may turn out that the content found within would be identical, and it might just be a case of putting in a class flag to indicate whether the presented document has been paid for or not.
: [[User:SignpostMarv|SignpostMarv]] 12:55, 21 Jul 2007 (PDT)

::I think a class flag is a great idea, but I don't believe we have any samples for invoices. However, if we look at order review vs. order summary rather than invoices vs. receipts, the payment flag does become relevant in many of the sampled online stores.
::How would such a flag be implemented?
::*<code><nowiki><div class="hreceipt unpaid"/"hreceipt paid">...</nowiki></code>
::*<code><nowiki><div class="hreceipt" title="paid">...</div></nowiki></code>
::[[User:Lastorset|Lastorset]] 14:55, 16 Aug 2007 (PDT)

=== Receipts ===

Receipts are post-purchase items.

==== Amazon ====
* [http://mobileonlinebusiness.com.au/uf/receipt/Amazon.com-Vieworder-anon.htm Example]
* contains:
**<del>email address</del> (could not find in examples)
**date of order
**order id
**shipments
***shipping estimate
***delivery estimate
***shipping address
***shipping speed
***shipping preference (item grouping)
***items
****quantity
****seller
****price
****item information
**payment
***card type
***last 5 digits
***expiration date
***billing address
***subtotal
***shipping and handling price
***total before tax
***tax
***grand total
**<del>discount price</del> (could not find in examples)
* Little semantic HTML of interest, except an anchor with id "payment-info"

Notes:
*Supports multiple shipments.
*Supports one seller per item.
*Displays shipping and delivery estimate.
*Offers item grouping preference.
*Gift options.

==== Skype ====

===== Skype Phone =====
*[[receipt-example-skype-phone|example source code]]
*[http://mobileonlinebusiness.com.au/uf/receipt/Skype-order-history.html Skype order history]

* Shipping Address
* date in dd/mm/yyyy format
* Order number in nnnn-nnnnnnn-nnn format
* Reference (was blank in example, presumed to appear on bank statement for this transaction)
* Items
** Quantity
** Description
** Price
** Total
** VAT (tax) %
* Payment
** subtotal ("total")
** shipping cost
** grand total ("total (gross)")
** total (VAT excluded)
** VAT (amount)
* Chosen payment method: "Your payment method is: Credit card"
* Legal blurb

Semantic HTML:
* Order resume class="order-listing"
* Each item class="row"
* All totals rows class="totals-row" except grand total class="grandtotal-row"

==== Internet banking transaction receipts ====
===== Example 1 =====
<pre><nowiki>
receipt number
date
time
receipt type (e.g. TRANSFER BETWEEN MY ACCOUNTS)
transfer from
transfer to
amount
description
information/comment
</nowiki></pre>

==== Digital product purchase receipts ====
===== Example 1 : Software =====
<pre><nowiki>
receipt title/type
order/receipt number
seller's details
sold by (hCard candidate)
org
adr
tax number (VAT in this example)
tax id (Federal Tax ID)
buyer's details
buyer (hCard candidate)
name
org
street-address
locality
region
postal-code
country-name
tel
email
credit card number (PAN truncated - with type)
item list
product code
name
comments
price
delivery method
quantity
total in selected currency
total in sellers currency
total (sum of item list totals)
processing fee
grand total (final amount charged)
information (caveats and tax info)
permalink
</nowiki></pre>

===== Example 2 : SSL certificate =====
<pre><nowiki>
receipt title/type
seller (hCard candidate)
org
street-address
locality
region
postal-code
purchase information
order id
product name
domain name
validity period
number of licenses
card number (PAN truncated)
amount (with selected currency)
</nowiki></pre>

==== Physical product purchase receipts ====
===== Example 1 : Computer hardware =====
<pre><nowiki>
receipt title/type
seller's name (hCard candidate)
seller's URL (hCard candidate)
invoice id
org govt reference (ABN - Australian Business Number)
date
seller details (hCard candidate)
street-address
locality
region
postal-code
buyer (hCard candidate)
fn
billing address
street-address
locality
region
postal-code
delivery address
street-address
locality
region
postal-code
phone
item list
item
description
amount
quantity
product url
total
delivery cost
total excluding tax
tax (GST - Goods and Service Tax)
total including tax
</nowiki></pre>

==== Service purchase receipts ====
===== Example 1 : Online subscription =====
<pre><nowiki>
seller's details (hCard candidate)
org
street-address
locality
region
postal-code
country-name
buyer's details (hCard candidate)
fn
street-address
locality
region
postal-code
phone
date
receipt id
item list
product description
quantity
rate (per unit)
price
sub total
amount paid
balance due
information
transaction id
</nowiki></pre>

===== Example 2 : Co-location =====
<pre><nowiki>
receipt title/type
sellers details (hCard candidate)
org
url
phone
message
receipt number
date
amount
information
</nowiki></pre>

==== A1Books ====
[http://mobileonlinebusiness.com.au/uf/receipt/A1Books-Sales-Order-anon.htm Example]

*vendor
**name
**fax
*date
*order number
*shipping address
*billing address
*items
**description
**list price
**sale price
**quantity
**amount
*subtotal
*shipping
*total
**quantity
**amount
*account information
**phone
**e-mail
*payment
**method
**last four digits

No semantic HTML.

Notes:
*Supports one seller per item.
*Does not display tax.

==== Barnes&Noble ====
[http://mobileonlinebusiness.com.au/uf/receipt/BarnesAndNoble.com-receipt.anon.tidied.htm Example]

*date
*shipping address
*billing address
*payment
**method
**last 4 digits
**exp. date
**charge
*savings on shipping
*order no.
*delivery option
*items
**description: title, author, ISBN, price
**qty
**gift options: wrap, message
**total price
*shipment subtotal
*shipping cost
*tax
*shipment total (seems to account for orders requiring multiple shipments)
*order total

Semantic HTML:
*receiptOrderNumbers
*receiptOrderPlacedOn
*orderInformation
**shippingAddress
**billingAddress
**paymentInformation
*shippingSelections
*showProducts
**reviewTable
***qtyValuePosition
***reviewGiftOptions
*reviewTotalsDisplay
**reviewTotalsSummary
**reviewTotalsNote
**reviewTotalsBreakdown
*reviewTotalsSummary
**reviewGrandTotal
*reviewCreditCardCharged
*review

The semantic class names found are a good start, although the "review" part appears to be context-specific (reviewing an order). Additionally, the implied hierarchy in names such as "reviewTotalsSummary" and "receiptOrderPlacedOn" is probably unnecessary for our purposes.

Notes:
*Supports multiple shipments.
*Gift options.

==== Facebook ====
[http://mobileonlinebusiness.com.au/uf/receipt/Facebook-gift-receipt.html Example]

*purchase total
*items (informal description of two items, including quantity)
*recipient name
*order id
*billed-to name

No relevant semantic HTML.

Notes:
*Quite minimal and informal receipt. Good example of how a microformat would preserve human readability and informal style while enabling machine reading.

==== Google Checkout ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Google-Checkout-e-mail-receipt.tidied.html Example email receipt]
*[http://mobileonlinebusiness.com.au/uf/receipt/Google-Checkout-Order-Receipt_DVD-Empire.tidied.htm Example web receipt]

*vendor address
*shipping address
*date
*order id
*items
**shipping status ("Not yet shipped", etc.)
**qty.
**description
**price
*shipping cost
*tax
*total
*order history (placed, received, charged, shipped) (web receipt only)
*payment info (web receipt only)
**card type
**last 4 digits
**exp. date
**cardholder address
*permalink

Semantic HTML:
*taxRow
**taxIdentifier
**taxAmount
*totalAmount

Notes:
*Explicit seller address (one per order).
*Current shipping status of each item.
*E-mail receipt has permalink.
*Order history (date placed, received, charged, shipped).

==== iTunes ====
*[http://mobileonlinebusiness.com.au/uf/receipt/iTunes-receipt-e-mail.html iTunes e-mail receipt]

*billing address
*order no.
*receipt date
*order total
*card
**type
**last 4 digits
*item
**item no.
**description (including link to write a review)
**unit price
*subtotal
*tax

No relevant semantic HTML.

==== Longs/FujiFilm ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Longs-Fujifilm-photo-receipt.html Longs/Fujifilm e-mail receipt]

*order no.
*payment info
**method (COD, credit card, etc.)
*customer address
*pickup address
*items
**name
**qty.
**description
**price
**line item subtotal
*order items total
*tax
*order total

Semantic HTML:
*payment-heading

==== Mobivox/PayPal ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Mobivox-PayPal.htm Mobivox/PayPal receipt]
*[http://mobileonlinebusiness.com.au/uf/receipt/Mobivox-PayPal-printable.htm Mobivox/PayPal printable receipt]

*seller address
*receipt id
*date of order
*items
**description
**item option (not quite sure what this is for)
**unit price
**qty
**total
*subtotal
*tax
*total amount
*payment info
**method
**last 4 digits
**charge
**appears on bill/statement as "MOBIVOXCORP"
*buyer contact

Relevant semantic HTML:
*order-summary
**cart
***(unnamed tr)
****item-name
****item-total
****item-option (not quite sure what this is for)
**subtotal
**totals-value
**totals-currency
**purchase-summary
***summary-total
****price-total
****price-currency
*funding-mix
**payment-type
**amount
**ccStatement
*contact-information (contains hCard microformat)

This semantic HTML is the most complete and well-thought-out I've seen in this analysis. It even makes use of the fieldset element in forms, something I've never seen before.[[User:Lastorset|Lastorset]] 16:21, 25 Jul 2007 (PDT)

Microformats used:
*hCard (non-compliant due to missing formatted name): buyer contact info

==== Symantec ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Symantec-reminder-e-mail.html Symantec e-mail reminder]

*buyer name
*date
*payment method
*last 4 digits
*appears on statement as "DR *Symantec"
*items
**qty
**product name
**platform
**delivery method
**price
*subtotal
*grand total
*permalink

No relevant semantic HTML

=== Analysis ===

==== Analysis of Bills ====

==== Analysis of Receipts ====

== Existing Practices ==

Listed below is an overview of existing patterns and practices found in the wild for bill and receipt data.

===Summary of common patterns discovered===

===Other attempts to solve The Problem===
For paper receipts, [http://www.neatreceipts.com/ NeatReceipts Scanalizer] offers a heuristic-based solution.

== Proposal ==

== See Also ==
* [[receipt]]
* http://en.wikipedia.org/wiki/Receipt

receipt-examples

2007-08-16T23:34:58Z

Lastorset: /* Facebook */ Notable results from group analysis

= Receipt =

Overview of Receipt exploratory discussion goes here...

== Authors ==

=== Contributors ===
Rob Manson

== Real-World Examples ==

=== Bill / Invoice ===

Bills or Invoices are "yet to be paid" items.

Question: Perhaps these examples (yet to be provided) should be moved to a separate page as Bill/Invoice is quite different from Receipt.

: With [[hResume]], I've [[hresume-brainstorming|suggested]] that the subtle difference between actively seeking work and just presenting your resume be a case of including [[hlisting]] markup.
: With bills vs invoices, it may turn out that the content found within would be identical, and it might just be a case of putting in a class flag to indicate whether the presented document has been paid for or not.
: [[User:SignpostMarv|SignpostMarv]] 12:55, 21 Jul 2007 (PDT)

::I think a class flag is a great idea, but I don't believe we have any samples for invoices. However, if we look at order review vs. order summary rather than invoices vs. receipts, the payment flag does become relevant in many of the sampled online stores.
::How would such a flag be implemented?
::*<code><nowiki><div class="hreceipt unpaid"/"hreceipt paid">...</nowiki></code>
::*<code><nowiki><div class="hreceipt" title="paid">...</div></nowiki></code>
::[[User:Lastorset|Lastorset]] 14:55, 16 Aug 2007 (PDT)

=== Receipts ===

Receipts are post-purchase items.

==== Amazon ====
* [http://mobileonlinebusiness.com.au/uf/receipt/Amazon.com-Vieworder-anon.htm Example]
* contains:
**<del>email address</del> (could not find in examples)
**date of order
**order id
**shipments
***shipping estimate
***delivery estimate
***shipping address
***shipping speed
***shipping preference (item grouping)
***items
****quantity
****seller
****price
****item information
**payment
***card type
***last 5 digits
***expiration date
***billing address
***subtotal
***shipping and handling price
***total before tax
***tax
***grand total
**<del>discount price</del> (could not find in examples)
* Little semantic HTML of interest, except an anchor with id "payment-info"

Notes:
*Supports multiple shipments.
*Supports one seller per item.
*Displays shipping and delivery estimate.
*Offers item grouping preference.
*Gift options.

==== Skype ====

===== Skype Phone =====
*[[receipt-example-skype-phone|example source code]]
*[http://mobileonlinebusiness.com.au/uf/receipt/Skype-order-history.html Skype order history]

* Shipping Address
* date in dd/mm/yyyy format
* Order number in nnnn-nnnnnnn-nnn format
* Reference (was blank in example, presumed to appear on bank statement for this transaction)
* Items
** Quantity
** Description
** Price
** Total
** VAT (tax) %
* Payment
** subtotal ("total")
** shipping cost
** grand total ("total (gross)")
** total (VAT excluded)
** VAT (amount)
* Chosen payment method: "Your payment method is: Credit card"
* Legal blurb

Semantic HTML:
* Order resume class="order-listing"
* Each item class="row"
* All totals rows class="totals-row" except grand total class="grandtotal-row"

==== Internet banking transaction receipts ====
===== Example 1 =====
<pre><nowiki>
receipt number
date
time
receipt type (e.g. TRANSFER BETWEEN MY ACCOUNTS)
transfer from
transfer to
amount
description
information/comment
</nowiki></pre>

==== Digital product purchase receipts ====
===== Example 1 : Software =====
<pre><nowiki>
receipt title/type
order/receipt number
seller's details
sold by (hCard candidate)
org
adr
tax number (VAT in this example)
tax id (Federal Tax ID)
buyer's details
buyer (hCard candidate)
name
org
street-address
locality
region
postal-code
country-name
tel
email
credit card number (PAN truncated - with type)
item list
product code
name
comments
price
delivery method
quantity
total in selected currency
total in sellers currency
total (sum of item list totals)
processing fee
grand total (final amount charged)
information (caveats and tax info)
permalink
</nowiki></pre>

===== Example 2 : SSL certificate =====
<pre><nowiki>
receipt title/type
seller (hCard candidate)
org
street-address
locality
region
postal-code
purchase information
order id
product name
domain name
validity period
number of licenses
card number (PAN truncated)
amount (with selected currency)
</nowiki></pre>

==== Physical product purchase receipts ====
===== Example 1 : Computer hardware =====
<pre><nowiki>
receipt title/type
seller's name (hCard candidate)
seller's URL (hCard candidate)
invoice id
org govt reference (ABN - Australian Business Number)
date
seller details (hCard candidate)
street-address
locality
region
postal-code
buyer (hCard candidate)
fn
billing address
street-address
locality
region
postal-code
delivery address
street-address
locality
region
postal-code
phone
item list
item
description
amount
quantity
product url
total
delivery cost
total excluding tax
tax (GST - Goods and Service Tax)
total including tax
</nowiki></pre>

==== Service purchase receipts ====
===== Example 1 : Online subscription =====
<pre><nowiki>
seller's details (hCard candidate)
org
street-address
locality
region
postal-code
country-name
buyer's details (hCard candidate)
fn
street-address
locality
region
postal-code
phone
date
receipt id
item list
product description
quantity
rate (per unit)
price
sub total
amount paid
balance due
information
transaction id
</nowiki></pre>

===== Example 2 : Co-location =====
<pre><nowiki>
receipt title/type
sellers details (hCard candidate)
org
url
phone
message
receipt number
date
amount
information
</nowiki></pre>

==== A1Books ====
[http://mobileonlinebusiness.com.au/uf/receipt/A1Books-Sales-Order-anon.htm Example]

*vendor
**name
**fax
*date
*order number
*shipping address
*billing address
*items
**description
**list price
**sale price
**quantity
**amount
*subtotal
*shipping
*total
**quantity
**amount
*account information
**phone
**e-mail
*payment
**method
**last four digits

No semantic HTML.

Notes:
*Supports one seller per item.
*Does not display tax.

==== Barnes&Noble ====
[http://mobileonlinebusiness.com.au/uf/receipt/BarnesAndNoble.com-receipt.anon.tidied.htm Example]

*date
*shipping address
*billing address
*payment
**method
**last 4 digits
**exp. date
**charge
*savings on shipping
*order no.
*delivery option
*items
**description: title, author, ISBN, price
**qty
**gift options: wrap, message
**total price
*shipment subtotal
*shipping cost
*tax
*shipment total (seems to account for orders requiring multiple shipments)
*order total

Semantic HTML:
*receiptOrderNumbers
*receiptOrderPlacedOn
*orderInformation
**shippingAddress
**billingAddress
**paymentInformation
*shippingSelections
*showProducts
**reviewTable
***qtyValuePosition
***reviewGiftOptions
*reviewTotalsDisplay
**reviewTotalsSummary
**reviewTotalsNote
**reviewTotalsBreakdown
*reviewTotalsSummary
**reviewGrandTotal
*reviewCreditCardCharged
*review

The semantic class names found are a good start, although the "review" part appears to be context-specific (reviewing an order). Additionally, the implied hierarchy in names such as "reviewTotalsSummary" and "receiptOrderPlacedOn" is probably unnecessary for our purposes.

Notes:
*Supports multiple shipments.
*Gift options.

==== Facebook ====
[http://mobileonlinebusiness.com.au/uf/receipt/Facebook-gift-receipt.html Example]

*purchase total
*items (informal description of two items, including quantity)
*recipient name
*order id
*billed-to name

No relevant semantic HTML.

Notes:
*Quite minimal and informal receipt. Good example of how a microformat would preserve human readability and informal style while enabling machine reading.

==== Google Checkout ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Google-Checkout-e-mail-receipt.tidied.html Example email receipt]
*[http://mobileonlinebusiness.com.au/uf/receipt/Google-Checkout-Order-Receipt_DVD-Empire.tidied.htm Example web receipt]

*vendor address
*shipping address
*date
*order id
*items
**shipping status ("Not yet shipped", etc.)
**qty.
**description
**price
*shipping cost
*tax
*total
*order history (placed, received, charged, shipped) (web receipt only)
*payment info (web receipt only)
**card type
**last 4 digits
**exp. date
**cardholder address
*permalink

Semantic HTML:
*taxRow
**taxIdentifier
**taxAmount
*totalAmount

==== iTunes ====
*[http://mobileonlinebusiness.com.au/uf/receipt/iTunes-receipt-e-mail.html iTunes e-mail receipt]

*billing address
*order no.
*receipt date
*order total
*card
**type
**last 4 digits
*item
**item no.
**description (including link to write a review)
**unit price
*subtotal
*tax

No relevant semantic HTML.

==== Longs/FujiFilm ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Longs-Fujifilm-photo-receipt.html Longs/Fujifilm e-mail receipt]

*order no.
*payment info
**method (COD, credit card, etc.)
*customer address
*pickup address
*items
**name
**qty.
**description
**price
**line item subtotal
*order items total
*tax
*order total

Semantic HTML:
*payment-heading

==== Mobivox/PayPal ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Mobivox-PayPal.htm Mobivox/PayPal receipt]
*[http://mobileonlinebusiness.com.au/uf/receipt/Mobivox-PayPal-printable.htm Mobivox/PayPal printable receipt]

*seller address
*receipt id
*date of order
*items
**description
**item option (not quite sure what this is for)
**unit price
**qty
**total
*subtotal
*tax
*total amount
*payment info
**method
**last 4 digits
**charge
**appears on bill/statement as "MOBIVOXCORP"
*buyer contact

Relevant semantic HTML:
*order-summary
**cart
***(unnamed tr)
****item-name
****item-total
****item-option (not quite sure what this is for)
**subtotal
**totals-value
**totals-currency
**purchase-summary
***summary-total
****price-total
****price-currency
*funding-mix
**payment-type
**amount
**ccStatement
*contact-information (contains hCard microformat)

This semantic HTML is the most complete and well-thought-out I've seen in this analysis. It even makes use of the fieldset element in forms, something I've never seen before.[[User:Lastorset|Lastorset]] 16:21, 25 Jul 2007 (PDT)

Microformats used:
*hCard (non-compliant due to missing formatted name): buyer contact info

==== Symantec ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Symantec-reminder-e-mail.html Symantec e-mail reminder]

*buyer name
*date
*payment method
*last 4 digits
*appears on statement as "DR *Symantec"
*items
**qty
**product name
**platform
**delivery method
**price
*subtotal
*grand total
*permalink

No relevant semantic HTML

=== Analysis ===

==== Analysis of Bills ====

==== Analysis of Receipts ====

== Existing Practices ==

Listed below is an overview of existing patterns and practices found in the wild for bill and receipt data.

===Summary of common patterns discovered===

===Other attempts to solve The Problem===
For paper receipts, [http://www.neatreceipts.com/ NeatReceipts Scanalizer] offers a heuristic-based solution.

== Proposal ==

== See Also ==
* [[receipt]]
* http://en.wikipedia.org/wiki/Receipt

receipt-examples

2007-08-16T23:31:18Z

Lastorset: /* Barnes&Noble */ Notable items from group analysis

= Receipt =

Overview of Receipt exploratory discussion goes here...

== Authors ==

=== Contributors ===
Rob Manson

== Real-World Examples ==

=== Bill / Invoice ===

Bills or Invoices are "yet to be paid" items.

Question: Perhaps these examples (yet to be provided) should be moved to a separate page as Bill/Invoice is quite different from Receipt.

: With [[hResume]], I've [[hresume-brainstorming|suggested]] that the subtle difference between actively seeking work and just presenting your resume be a case of including [[hlisting]] markup.
: With bills vs invoices, it may turn out that the content found within would be identical, and it might just be a case of putting in a class flag to indicate whether the presented document has been paid for or not.
: [[User:SignpostMarv|SignpostMarv]] 12:55, 21 Jul 2007 (PDT)

::I think a class flag is a great idea, but I don't believe we have any samples for invoices. However, if we look at order review vs. order summary rather than invoices vs. receipts, the payment flag does become relevant in many of the sampled online stores.
::How would such a flag be implemented?
::*<code><nowiki><div class="hreceipt unpaid"/"hreceipt paid">...</nowiki></code>
::*<code><nowiki><div class="hreceipt" title="paid">...</div></nowiki></code>
::[[User:Lastorset|Lastorset]] 14:55, 16 Aug 2007 (PDT)

=== Receipts ===

Receipts are post-purchase items.

==== Amazon ====
* [http://mobileonlinebusiness.com.au/uf/receipt/Amazon.com-Vieworder-anon.htm Example]
* contains:
**<del>email address</del> (could not find in examples)
**date of order
**order id
**shipments
***shipping estimate
***delivery estimate
***shipping address
***shipping speed
***shipping preference (item grouping)
***items
****quantity
****seller
****price
****item information
**payment
***card type
***last 5 digits
***expiration date
***billing address
***subtotal
***shipping and handling price
***total before tax
***tax
***grand total
**<del>discount price</del> (could not find in examples)
* Little semantic HTML of interest, except an anchor with id "payment-info"

Notes:
*Supports multiple shipments.
*Supports one seller per item.
*Displays shipping and delivery estimate.
*Offers item grouping preference.
*Gift options.

==== Skype ====

===== Skype Phone =====
*[[receipt-example-skype-phone|example source code]]
*[http://mobileonlinebusiness.com.au/uf/receipt/Skype-order-history.html Skype order history]

* Shipping Address
* date in dd/mm/yyyy format
* Order number in nnnn-nnnnnnn-nnn format
* Reference (was blank in example, presumed to appear on bank statement for this transaction)
* Items
** Quantity
** Description
** Price
** Total
** VAT (tax) %
* Payment
** subtotal ("total")
** shipping cost
** grand total ("total (gross)")
** total (VAT excluded)
** VAT (amount)
* Chosen payment method: "Your payment method is: Credit card"
* Legal blurb

Semantic HTML:
* Order resume class="order-listing"
* Each item class="row"
* All totals rows class="totals-row" except grand total class="grandtotal-row"

==== Internet banking transaction receipts ====
===== Example 1 =====
<pre><nowiki>
receipt number
date
time
receipt type (e.g. TRANSFER BETWEEN MY ACCOUNTS)
transfer from
transfer to
amount
description
information/comment
</nowiki></pre>

==== Digital product purchase receipts ====
===== Example 1 : Software =====
<pre><nowiki>
receipt title/type
order/receipt number
seller's details
sold by (hCard candidate)
org
adr
tax number (VAT in this example)
tax id (Federal Tax ID)
buyer's details
buyer (hCard candidate)
name
org
street-address
locality
region
postal-code
country-name
tel
email
credit card number (PAN truncated - with type)
item list
product code
name
comments
price
delivery method
quantity
total in selected currency
total in sellers currency
total (sum of item list totals)
processing fee
grand total (final amount charged)
information (caveats and tax info)
permalink
</nowiki></pre>

===== Example 2 : SSL certificate =====
<pre><nowiki>
receipt title/type
seller (hCard candidate)
org
street-address
locality
region
postal-code
purchase information
order id
product name
domain name
validity period
number of licenses
card number (PAN truncated)
amount (with selected currency)
</nowiki></pre>

==== Physical product purchase receipts ====
===== Example 1 : Computer hardware =====
<pre><nowiki>
receipt title/type
seller's name (hCard candidate)
seller's URL (hCard candidate)
invoice id
org govt reference (ABN - Australian Business Number)
date
seller details (hCard candidate)
street-address
locality
region
postal-code
buyer (hCard candidate)
fn
billing address
street-address
locality
region
postal-code
delivery address
street-address
locality
region
postal-code
phone
item list
item
description
amount
quantity
product url
total
delivery cost
total excluding tax
tax (GST - Goods and Service Tax)
total including tax
</nowiki></pre>

==== Service purchase receipts ====
===== Example 1 : Online subscription =====
<pre><nowiki>
seller's details (hCard candidate)
org
street-address
locality
region
postal-code
country-name
buyer's details (hCard candidate)
fn
street-address
locality
region
postal-code
phone
date
receipt id
item list
product description
quantity
rate (per unit)
price
sub total
amount paid
balance due
information
transaction id
</nowiki></pre>

===== Example 2 : Co-location =====
<pre><nowiki>
receipt title/type
sellers details (hCard candidate)
org
url
phone
message
receipt number
date
amount
information
</nowiki></pre>

==== A1Books ====
[http://mobileonlinebusiness.com.au/uf/receipt/A1Books-Sales-Order-anon.htm Example]

*vendor
**name
**fax
*date
*order number
*shipping address
*billing address
*items
**description
**list price
**sale price
**quantity
**amount
*subtotal
*shipping
*total
**quantity
**amount
*account information
**phone
**e-mail
*payment
**method
**last four digits

No semantic HTML.

Notes:
*Supports one seller per item.
*Does not display tax.

==== Barnes&Noble ====
[http://mobileonlinebusiness.com.au/uf/receipt/BarnesAndNoble.com-receipt.anon.tidied.htm Example]

*date
*shipping address
*billing address
*payment
**method
**last 4 digits
**exp. date
**charge
*savings on shipping
*order no.
*delivery option
*items
**description: title, author, ISBN, price
**qty
**gift options: wrap, message
**total price
*shipment subtotal
*shipping cost
*tax
*shipment total (seems to account for orders requiring multiple shipments)
*order total

Semantic HTML:
*receiptOrderNumbers
*receiptOrderPlacedOn
*orderInformation
**shippingAddress
**billingAddress
**paymentInformation
*shippingSelections
*showProducts
**reviewTable
***qtyValuePosition
***reviewGiftOptions
*reviewTotalsDisplay
**reviewTotalsSummary
**reviewTotalsNote
**reviewTotalsBreakdown
*reviewTotalsSummary
**reviewGrandTotal
*reviewCreditCardCharged
*review

The semantic class names found are a good start, although the "review" part appears to be context-specific (reviewing an order). Additionally, the implied hierarchy in names such as "reviewTotalsSummary" and "receiptOrderPlacedOn" is probably unnecessary for our purposes.

Notes:
*Supports multiple shipments.
*Gift options.

==== Facebook ====
[http://mobileonlinebusiness.com.au/uf/receipt/Facebook-gift-receipt.html Example]

*purchase total
*items (informal description of two items, including quantity)
*recipient name
*order id
*billed-to name

No relevant semantic HTML.

==== Google Checkout ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Google-Checkout-e-mail-receipt.tidied.html Example email receipt]
*[http://mobileonlinebusiness.com.au/uf/receipt/Google-Checkout-Order-Receipt_DVD-Empire.tidied.htm Example web receipt]

*vendor address
*shipping address
*date
*order id
*items
**shipping status ("Not yet shipped", etc.)
**qty.
**description
**price
*shipping cost
*tax
*total
*order history (placed, received, charged, shipped) (web receipt only)
*payment info (web receipt only)
**card type
**last 4 digits
**exp. date
**cardholder address
*permalink

Semantic HTML:
*taxRow
**taxIdentifier
**taxAmount
*totalAmount

==== iTunes ====
*[http://mobileonlinebusiness.com.au/uf/receipt/iTunes-receipt-e-mail.html iTunes e-mail receipt]

*billing address
*order no.
*receipt date
*order total
*card
**type
**last 4 digits
*item
**item no.
**description (including link to write a review)
**unit price
*subtotal
*tax

No relevant semantic HTML.

==== Longs/FujiFilm ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Longs-Fujifilm-photo-receipt.html Longs/Fujifilm e-mail receipt]

*order no.
*payment info
**method (COD, credit card, etc.)
*customer address
*pickup address
*items
**name
**qty.
**description
**price
**line item subtotal
*order items total
*tax
*order total

Semantic HTML:
*payment-heading

==== Mobivox/PayPal ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Mobivox-PayPal.htm Mobivox/PayPal receipt]
*[http://mobileonlinebusiness.com.au/uf/receipt/Mobivox-PayPal-printable.htm Mobivox/PayPal printable receipt]

*seller address
*receipt id
*date of order
*items
**description
**item option (not quite sure what this is for)
**unit price
**qty
**total
*subtotal
*tax
*total amount
*payment info
**method
**last 4 digits
**charge
**appears on bill/statement as "MOBIVOXCORP"
*buyer contact

Relevant semantic HTML:
*order-summary
**cart
***(unnamed tr)
****item-name
****item-total
****item-option (not quite sure what this is for)
**subtotal
**totals-value
**totals-currency
**purchase-summary
***summary-total
****price-total
****price-currency
*funding-mix
**payment-type
**amount
**ccStatement
*contact-information (contains hCard microformat)

This semantic HTML is the most complete and well-thought-out I've seen in this analysis. It even makes use of the fieldset element in forms, something I've never seen before.[[User:Lastorset|Lastorset]] 16:21, 25 Jul 2007 (PDT)

Microformats used:
*hCard (non-compliant due to missing formatted name): buyer contact info

==== Symantec ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Symantec-reminder-e-mail.html Symantec e-mail reminder]

*buyer name
*date
*payment method
*last 4 digits
*appears on statement as "DR *Symantec"
*items
**qty
**product name
**platform
**delivery method
**price
*subtotal
*grand total
*permalink

No relevant semantic HTML

=== Analysis ===

==== Analysis of Bills ====

==== Analysis of Receipts ====

== Existing Practices ==

Listed below is an overview of existing patterns and practices found in the wild for bill and receipt data.

===Summary of common patterns discovered===

===Other attempts to solve The Problem===
For paper receipts, [http://www.neatreceipts.com/ NeatReceipts Scanalizer] offers a heuristic-based solution.

== Proposal ==

== See Also ==
* [[receipt]]
* http://en.wikipedia.org/wiki/Receipt

receipt-examples

2007-08-16T23:27:18Z

Lastorset: /* Amazon */ Notable items from group analysis

= Receipt =

Overview of Receipt exploratory discussion goes here...

== Authors ==

=== Contributors ===
Rob Manson

== Real-World Examples ==

=== Bill / Invoice ===

Bills or Invoices are "yet to be paid" items.

Question: Perhaps these examples (yet to be provided) should be moved to a separate page as Bill/Invoice is quite different from Receipt.

: With [[hResume]], I've [[hresume-brainstorming|suggested]] that the subtle difference between actively seeking work and just presenting your resume be a case of including [[hlisting]] markup.
: With bills vs invoices, it may turn out that the content found within would be identical, and it might just be a case of putting in a class flag to indicate whether the presented document has been paid for or not.
: [[User:SignpostMarv|SignpostMarv]] 12:55, 21 Jul 2007 (PDT)

::I think a class flag is a great idea, but I don't believe we have any samples for invoices. However, if we look at order review vs. order summary rather than invoices vs. receipts, the payment flag does become relevant in many of the sampled online stores.
::How would such a flag be implemented?
::*<code><nowiki><div class="hreceipt unpaid"/"hreceipt paid">...</nowiki></code>
::*<code><nowiki><div class="hreceipt" title="paid">...</div></nowiki></code>
::[[User:Lastorset|Lastorset]] 14:55, 16 Aug 2007 (PDT)

=== Receipts ===

Receipts are post-purchase items.

==== Amazon ====
* [http://mobileonlinebusiness.com.au/uf/receipt/Amazon.com-Vieworder-anon.htm Example]
* contains:
**<del>email address</del> (could not find in examples)
**date of order
**order id
**shipments
***shipping estimate
***delivery estimate
***shipping address
***shipping speed
***shipping preference (item grouping)
***items
****quantity
****seller
****price
****item information
**payment
***card type
***last 5 digits
***expiration date
***billing address
***subtotal
***shipping and handling price
***total before tax
***tax
***grand total
**<del>discount price</del> (could not find in examples)
* Little semantic HTML of interest, except an anchor with id "payment-info"

Notes:
*Supports multiple shipments.
*Supports one seller per item.
*Displays shipping and delivery estimate.
*Offers item grouping preference.
*Gift options.

==== Skype ====

===== Skype Phone =====
*[[receipt-example-skype-phone|example source code]]
*[http://mobileonlinebusiness.com.au/uf/receipt/Skype-order-history.html Skype order history]

* Shipping Address
* date in dd/mm/yyyy format
* Order number in nnnn-nnnnnnn-nnn format
* Reference (was blank in example, presumed to appear on bank statement for this transaction)
* Items
** Quantity
** Description
** Price
** Total
** VAT (tax) %
* Payment
** subtotal ("total")
** shipping cost
** grand total ("total (gross)")
** total (VAT excluded)
** VAT (amount)
* Chosen payment method: "Your payment method is: Credit card"
* Legal blurb

Semantic HTML:
* Order resume class="order-listing"
* Each item class="row"
* All totals rows class="totals-row" except grand total class="grandtotal-row"

==== Internet banking transaction receipts ====
===== Example 1 =====
<pre><nowiki>
receipt number
date
time
receipt type (e.g. TRANSFER BETWEEN MY ACCOUNTS)
transfer from
transfer to
amount
description
information/comment
</nowiki></pre>

==== Digital product purchase receipts ====
===== Example 1 : Software =====
<pre><nowiki>
receipt title/type
order/receipt number
seller's details
sold by (hCard candidate)
org
adr
tax number (VAT in this example)
tax id (Federal Tax ID)
buyer's details
buyer (hCard candidate)
name
org
street-address
locality
region
postal-code
country-name
tel
email
credit card number (PAN truncated - with type)
item list
product code
name
comments
price
delivery method
quantity
total in selected currency
total in sellers currency
total (sum of item list totals)
processing fee
grand total (final amount charged)
information (caveats and tax info)
permalink
</nowiki></pre>

===== Example 2 : SSL certificate =====
<pre><nowiki>
receipt title/type
seller (hCard candidate)
org
street-address
locality
region
postal-code
purchase information
order id
product name
domain name
validity period
number of licenses
card number (PAN truncated)
amount (with selected currency)
</nowiki></pre>

==== Physical product purchase receipts ====
===== Example 1 : Computer hardware =====
<pre><nowiki>
receipt title/type
seller's name (hCard candidate)
seller's URL (hCard candidate)
invoice id
org govt reference (ABN - Australian Business Number)
date
seller details (hCard candidate)
street-address
locality
region
postal-code
buyer (hCard candidate)
fn
billing address
street-address
locality
region
postal-code
delivery address
street-address
locality
region
postal-code
phone
item list
item
description
amount
quantity
product url
total
delivery cost
total excluding tax
tax (GST - Goods and Service Tax)
total including tax
</nowiki></pre>

==== Service purchase receipts ====
===== Example 1 : Online subscription =====
<pre><nowiki>
seller's details (hCard candidate)
org
street-address
locality
region
postal-code
country-name
buyer's details (hCard candidate)
fn
street-address
locality
region
postal-code
phone
date
receipt id
item list
product description
quantity
rate (per unit)
price
sub total
amount paid
balance due
information
transaction id
</nowiki></pre>

===== Example 2 : Co-location =====
<pre><nowiki>
receipt title/type
sellers details (hCard candidate)
org
url
phone
message
receipt number
date
amount
information
</nowiki></pre>

==== A1Books ====
[http://mobileonlinebusiness.com.au/uf/receipt/A1Books-Sales-Order-anon.htm Example]

*vendor
**name
**fax
*date
*order number
*shipping address
*billing address
*items
**description
**list price
**sale price
**quantity
**amount
*subtotal
*shipping
*total
**quantity
**amount
*account information
**phone
**e-mail
*payment
**method
**last four digits

No semantic HTML.

Notes:
*Supports one seller per item.
*Does not display tax.

==== Barnes&Noble ====
[http://mobileonlinebusiness.com.au/uf/receipt/BarnesAndNoble.com-receipt.anon.tidied.htm Example]

*date
*shipping address
*billing address
*payment
**method
**last 4 digits
**exp. date
**charge
*savings on shipping
*order no.
*delivery option
*items
**description: title, author, ISBN, price
**qty
**gift options: wrap, message
**total price
*shipment subtotal
*shipping cost
*tax
*shipment total (seems to account for orders requiring multiple shipments)
*order total

Semantic HTML:
*receiptOrderNumbers
*receiptOrderPlacedOn
*orderInformation
**shippingAddress
**billingAddress
**paymentInformation
*shippingSelections
*showProducts
**reviewTable
***qtyValuePosition
***reviewGiftOptions
*reviewTotalsDisplay
**reviewTotalsSummary
**reviewTotalsNote
**reviewTotalsBreakdown
*reviewTotalsSummary
**reviewGrandTotal
*reviewCreditCardCharged
*review

The semantic class names found are a good start, although the "review" part appears to be context-specific (reviewing an order). Additionally, the implied hierarchy in names such as "reviewTotalsSummary" and "receiptOrderPlacedOn" is probably unnecessary for our purposes.

==== Facebook ====
[http://mobileonlinebusiness.com.au/uf/receipt/Facebook-gift-receipt.html Example]

*purchase total
*items (informal description of two items, including quantity)
*recipient name
*order id
*billed-to name

No relevant semantic HTML.

==== Google Checkout ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Google-Checkout-e-mail-receipt.tidied.html Example email receipt]
*[http://mobileonlinebusiness.com.au/uf/receipt/Google-Checkout-Order-Receipt_DVD-Empire.tidied.htm Example web receipt]

*vendor address
*shipping address
*date
*order id
*items
**shipping status ("Not yet shipped", etc.)
**qty.
**description
**price
*shipping cost
*tax
*total
*order history (placed, received, charged, shipped) (web receipt only)
*payment info (web receipt only)
**card type
**last 4 digits
**exp. date
**cardholder address
*permalink

Semantic HTML:
*taxRow
**taxIdentifier
**taxAmount
*totalAmount

==== iTunes ====
*[http://mobileonlinebusiness.com.au/uf/receipt/iTunes-receipt-e-mail.html iTunes e-mail receipt]

*billing address
*order no.
*receipt date
*order total
*card
**type
**last 4 digits
*item
**item no.
**description (including link to write a review)
**unit price
*subtotal
*tax

No relevant semantic HTML.

==== Longs/FujiFilm ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Longs-Fujifilm-photo-receipt.html Longs/Fujifilm e-mail receipt]

*order no.
*payment info
**method (COD, credit card, etc.)
*customer address
*pickup address
*items
**name
**qty.
**description
**price
**line item subtotal
*order items total
*tax
*order total

Semantic HTML:
*payment-heading

==== Mobivox/PayPal ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Mobivox-PayPal.htm Mobivox/PayPal receipt]
*[http://mobileonlinebusiness.com.au/uf/receipt/Mobivox-PayPal-printable.htm Mobivox/PayPal printable receipt]

*seller address
*receipt id
*date of order
*items
**description
**item option (not quite sure what this is for)
**unit price
**qty
**total
*subtotal
*tax
*total amount
*payment info
**method
**last 4 digits
**charge
**appears on bill/statement as "MOBIVOXCORP"
*buyer contact

Relevant semantic HTML:
*order-summary
**cart
***(unnamed tr)
****item-name
****item-total
****item-option (not quite sure what this is for)
**subtotal
**totals-value
**totals-currency
**purchase-summary
***summary-total
****price-total
****price-currency
*funding-mix
**payment-type
**amount
**ccStatement
*contact-information (contains hCard microformat)

This semantic HTML is the most complete and well-thought-out I've seen in this analysis. It even makes use of the fieldset element in forms, something I've never seen before.[[User:Lastorset|Lastorset]] 16:21, 25 Jul 2007 (PDT)

Microformats used:
*hCard (non-compliant due to missing formatted name): buyer contact info

==== Symantec ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Symantec-reminder-e-mail.html Symantec e-mail reminder]

*buyer name
*date
*payment method
*last 4 digits
*appears on statement as "DR *Symantec"
*items
**qty
**product name
**platform
**delivery method
**price
*subtotal
*grand total
*permalink

No relevant semantic HTML

=== Analysis ===

==== Analysis of Bills ====

==== Analysis of Receipts ====

== Existing Practices ==

Listed below is an overview of existing patterns and practices found in the wild for bill and receipt data.

===Summary of common patterns discovered===

===Other attempts to solve The Problem===
For paper receipts, [http://www.neatreceipts.com/ NeatReceipts Scanalizer] offers a heuristic-based solution.

== Proposal ==

== See Also ==
* [[receipt]]
* http://en.wikipedia.org/wiki/Receipt

receipt-examples

2007-08-16T23:21:43Z

Lastorset: /* A1Books */ Notable items from group analysis

= Receipt =

Overview of Receipt exploratory discussion goes here...

== Authors ==

=== Contributors ===
Rob Manson

== Real-World Examples ==

=== Bill / Invoice ===

Bills or Invoices are "yet to be paid" items.

Question: Perhaps these examples (yet to be provided) should be moved to a separate page as Bill/Invoice is quite different from Receipt.

: With [[hResume]], I've [[hresume-brainstorming|suggested]] that the subtle difference between actively seeking work and just presenting your resume be a case of including [[hlisting]] markup.
: With bills vs invoices, it may turn out that the content found within would be identical, and it might just be a case of putting in a class flag to indicate whether the presented document has been paid for or not.
: [[User:SignpostMarv|SignpostMarv]] 12:55, 21 Jul 2007 (PDT)

::I think a class flag is a great idea, but I don't believe we have any samples for invoices. However, if we look at order review vs. order summary rather than invoices vs. receipts, the payment flag does become relevant in many of the sampled online stores.
::How would such a flag be implemented?
::*<code><nowiki><div class="hreceipt unpaid"/"hreceipt paid">...</nowiki></code>
::*<code><nowiki><div class="hreceipt" title="paid">...</div></nowiki></code>
::[[User:Lastorset|Lastorset]] 14:55, 16 Aug 2007 (PDT)

=== Receipts ===

Receipts are post-purchase items.

==== Amazon ====
* [http://mobileonlinebusiness.com.au/uf/receipt/Amazon.com-Vieworder-anon.htm Example]
* contains:
**<del>email address</del> (could not find in examples)
**date of order
**order id
**shipments
***shipping estimate
***delivery estimate
***shipping address
***shipping speed
***shipping preference (item grouping)
***items
****quantity
****seller
****price
****item information
**payment
***card type
***last 5 digits
***expiration date
***billing address
***subtotal
***shipping and handling price
***total before tax
***tax
***grand total
**<del>discount price</del> (could not find in examples)
* Little semantic HTML of interest, except an anchor with id "payment-info"

==== Skype ====

===== Skype Phone =====
*[[receipt-example-skype-phone|example source code]]
*[http://mobileonlinebusiness.com.au/uf/receipt/Skype-order-history.html Skype order history]

* Shipping Address
* date in dd/mm/yyyy format
* Order number in nnnn-nnnnnnn-nnn format
* Reference (was blank in example, presumed to appear on bank statement for this transaction)
* Items
** Quantity
** Description
** Price
** Total
** VAT (tax) %
* Payment
** subtotal ("total")
** shipping cost
** grand total ("total (gross)")
** total (VAT excluded)
** VAT (amount)
* Chosen payment method: "Your payment method is: Credit card"
* Legal blurb

Semantic HTML:
* Order resume class="order-listing"
* Each item class="row"
* All totals rows class="totals-row" except grand total class="grandtotal-row"

==== Internet banking transaction receipts ====
===== Example 1 =====
<pre><nowiki>
receipt number
date
time
receipt type (e.g. TRANSFER BETWEEN MY ACCOUNTS)
transfer from
transfer to
amount
description
information/comment
</nowiki></pre>

==== Digital product purchase receipts ====
===== Example 1 : Software =====
<pre><nowiki>
receipt title/type
order/receipt number
seller's details
sold by (hCard candidate)
org
adr
tax number (VAT in this example)
tax id (Federal Tax ID)
buyer's details
buyer (hCard candidate)
name
org
street-address
locality
region
postal-code
country-name
tel
email
credit card number (PAN truncated - with type)
item list
product code
name
comments
price
delivery method
quantity
total in selected currency
total in sellers currency
total (sum of item list totals)
processing fee
grand total (final amount charged)
information (caveats and tax info)
permalink
</nowiki></pre>

===== Example 2 : SSL certificate =====
<pre><nowiki>
receipt title/type
seller (hCard candidate)
org
street-address
locality
region
postal-code
purchase information
order id
product name
domain name
validity period
number of licenses
card number (PAN truncated)
amount (with selected currency)
</nowiki></pre>

==== Physical product purchase receipts ====
===== Example 1 : Computer hardware =====
<pre><nowiki>
receipt title/type
seller's name (hCard candidate)
seller's URL (hCard candidate)
invoice id
org govt reference (ABN - Australian Business Number)
date
seller details (hCard candidate)
street-address
locality
region
postal-code
buyer (hCard candidate)
fn
billing address
street-address
locality
region
postal-code
delivery address
street-address
locality
region
postal-code
phone
item list
item
description
amount
quantity
product url
total
delivery cost
total excluding tax
tax (GST - Goods and Service Tax)
total including tax
</nowiki></pre>

==== Service purchase receipts ====
===== Example 1 : Online subscription =====
<pre><nowiki>
seller's details (hCard candidate)
org
street-address
locality
region
postal-code
country-name
buyer's details (hCard candidate)
fn
street-address
locality
region
postal-code
phone
date
receipt id
item list
product description
quantity
rate (per unit)
price
sub total
amount paid
balance due
information
transaction id
</nowiki></pre>

===== Example 2 : Co-location =====
<pre><nowiki>
receipt title/type
sellers details (hCard candidate)
org
url
phone
message
receipt number
date
amount
information
</nowiki></pre>

==== A1Books ====
[http://mobileonlinebusiness.com.au/uf/receipt/A1Books-Sales-Order-anon.htm Example]

*vendor
**name
**fax
*date
*order number
*shipping address
*billing address
*items
**description
**list price
**sale price
**quantity
**amount
*subtotal
*shipping
*total
**quantity
**amount
*account information
**phone
**e-mail
*payment
**method
**last four digits

No semantic HTML.

Notes:
*Supports one seller per item.
*Does not display tax.

==== Barnes&Noble ====
[http://mobileonlinebusiness.com.au/uf/receipt/BarnesAndNoble.com-receipt.anon.tidied.htm Example]

*date
*shipping address
*billing address
*payment
**method
**last 4 digits
**exp. date
**charge
*savings on shipping
*order no.
*delivery option
*items
**description: title, author, ISBN, price
**qty
**gift options: wrap, message
**total price
*shipment subtotal
*shipping cost
*tax
*shipment total (seems to account for orders requiring multiple shipments)
*order total

Semantic HTML:
*receiptOrderNumbers
*receiptOrderPlacedOn
*orderInformation
**shippingAddress
**billingAddress
**paymentInformation
*shippingSelections
*showProducts
**reviewTable
***qtyValuePosition
***reviewGiftOptions
*reviewTotalsDisplay
**reviewTotalsSummary
**reviewTotalsNote
**reviewTotalsBreakdown
*reviewTotalsSummary
**reviewGrandTotal
*reviewCreditCardCharged
*review

The semantic class names found are a good start, although the "review" part appears to be context-specific (reviewing an order). Additionally, the implied hierarchy in names such as "reviewTotalsSummary" and "receiptOrderPlacedOn" is probably unnecessary for our purposes.

==== Facebook ====
[http://mobileonlinebusiness.com.au/uf/receipt/Facebook-gift-receipt.html Example]

*purchase total
*items (informal description of two items, including quantity)
*recipient name
*order id
*billed-to name

No relevant semantic HTML.

==== Google Checkout ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Google-Checkout-e-mail-receipt.tidied.html Example email receipt]
*[http://mobileonlinebusiness.com.au/uf/receipt/Google-Checkout-Order-Receipt_DVD-Empire.tidied.htm Example web receipt]

*vendor address
*shipping address
*date
*order id
*items
**shipping status ("Not yet shipped", etc.)
**qty.
**description
**price
*shipping cost
*tax
*total
*order history (placed, received, charged, shipped) (web receipt only)
*payment info (web receipt only)
**card type
**last 4 digits
**exp. date
**cardholder address
*permalink

Semantic HTML:
*taxRow
**taxIdentifier
**taxAmount
*totalAmount

==== iTunes ====
*[http://mobileonlinebusiness.com.au/uf/receipt/iTunes-receipt-e-mail.html iTunes e-mail receipt]

*billing address
*order no.
*receipt date
*order total
*card
**type
**last 4 digits
*item
**item no.
**description (including link to write a review)
**unit price
*subtotal
*tax

No relevant semantic HTML.

==== Longs/FujiFilm ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Longs-Fujifilm-photo-receipt.html Longs/Fujifilm e-mail receipt]

*order no.
*payment info
**method (COD, credit card, etc.)
*customer address
*pickup address
*items
**name
**qty.
**description
**price
**line item subtotal
*order items total
*tax
*order total

Semantic HTML:
*payment-heading

==== Mobivox/PayPal ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Mobivox-PayPal.htm Mobivox/PayPal receipt]
*[http://mobileonlinebusiness.com.au/uf/receipt/Mobivox-PayPal-printable.htm Mobivox/PayPal printable receipt]

*seller address
*receipt id
*date of order
*items
**description
**item option (not quite sure what this is for)
**unit price
**qty
**total
*subtotal
*tax
*total amount
*payment info
**method
**last 4 digits
**charge
**appears on bill/statement as "MOBIVOXCORP"
*buyer contact

Relevant semantic HTML:
*order-summary
**cart
***(unnamed tr)
****item-name
****item-total
****item-option (not quite sure what this is for)
**subtotal
**totals-value
**totals-currency
**purchase-summary
***summary-total
****price-total
****price-currency
*funding-mix
**payment-type
**amount
**ccStatement
*contact-information (contains hCard microformat)

This semantic HTML is the most complete and well-thought-out I've seen in this analysis. It even makes use of the fieldset element in forms, something I've never seen before.[[User:Lastorset|Lastorset]] 16:21, 25 Jul 2007 (PDT)

Microformats used:
*hCard (non-compliant due to missing formatted name): buyer contact info

==== Symantec ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Symantec-reminder-e-mail.html Symantec e-mail reminder]

*buyer name
*date
*payment method
*last 4 digits
*appears on statement as "DR *Symantec"
*items
**qty
**product name
**platform
**delivery method
**price
*subtotal
*grand total
*permalink

No relevant semantic HTML

=== Analysis ===

==== Analysis of Bills ====

==== Analysis of Receipts ====

== Existing Practices ==

Listed below is an overview of existing patterns and practices found in the wild for bill and receipt data.

===Summary of common patterns discovered===

===Other attempts to solve The Problem===
For paper receipts, [http://www.neatreceipts.com/ NeatReceipts Scanalizer] offers a heuristic-based solution.

== Proposal ==

== See Also ==
* [[receipt]]
* http://en.wikipedia.org/wiki/Receipt

receipt-examples

2007-08-16T22:34:46Z

Lastorset: /* Barnes&Noble */ forgot date

= Receipt =

Overview of Receipt exploratory discussion goes here...

== Authors ==

=== Contributors ===
Rob Manson

== Real-World Examples ==

=== Bill / Invoice ===

Bills or Invoices are "yet to be paid" items.

Question: Perhaps these examples (yet to be provided) should be moved to a separate page as Bill/Invoice is quite different from Receipt.

: With [[hResume]], I've [[hresume-brainstorming|suggested]] that the subtle difference between actively seeking work and just presenting your resume be a case of including [[hlisting]] markup.
: With bills vs invoices, it may turn out that the content found within would be identical, and it might just be a case of putting in a class flag to indicate whether the presented document has been paid for or not.
: [[User:SignpostMarv|SignpostMarv]] 12:55, 21 Jul 2007 (PDT)

::I think a class flag is a great idea, but I don't believe we have any samples for invoices. However, if we look at order review vs. order summary rather than invoices vs. receipts, the payment flag does become relevant in many of the sampled online stores.
::How would such a flag be implemented?
::*<code><nowiki><div class="hreceipt unpaid"/"hreceipt paid">...</nowiki></code>
::*<code><nowiki><div class="hreceipt" title="paid">...</div></nowiki></code>
::[[User:Lastorset|Lastorset]] 14:55, 16 Aug 2007 (PDT)

=== Receipts ===

Receipts are post-purchase items.

==== Amazon ====
* [http://mobileonlinebusiness.com.au/uf/receipt/Amazon.com-Vieworder-anon.htm Example]
* contains:
**<del>email address</del> (could not find in examples)
**date of order
**order id
**shipments
***shipping estimate
***delivery estimate
***shipping address
***shipping speed
***shipping preference (item grouping)
***items
****quantity
****seller
****price
****item information
**payment
***card type
***last 5 digits
***expiration date
***billing address
***subtotal
***shipping and handling price
***total before tax
***tax
***grand total
**<del>discount price</del> (could not find in examples)
* Little semantic HTML of interest, except an anchor with id "payment-info"

==== Skype ====

===== Skype Phone =====
*[[receipt-example-skype-phone|example source code]]
*[http://mobileonlinebusiness.com.au/uf/receipt/Skype-order-history.html Skype order history]

* Shipping Address
* date in dd/mm/yyyy format
* Order number in nnnn-nnnnnnn-nnn format
* Reference (was blank in example, presumed to appear on bank statement for this transaction)
* Items
** Quantity
** Description
** Price
** Total
** VAT (tax) %
* Payment
** subtotal ("total")
** shipping cost
** grand total ("total (gross)")
** total (VAT excluded)
** VAT (amount)
* Chosen payment method: "Your payment method is: Credit card"
* Legal blurb

Semantic HTML:
* Order resume class="order-listing"
* Each item class="row"
* All totals rows class="totals-row" except grand total class="grandtotal-row"

==== Internet banking transaction receipts ====
===== Example 1 =====
<pre><nowiki>
receipt number
date
time
receipt type (e.g. TRANSFER BETWEEN MY ACCOUNTS)
transfer from
transfer to
amount
description
information/comment
</nowiki></pre>

==== Digital product purchase receipts ====
===== Example 1 : Software =====
<pre><nowiki>
receipt title/type
order/receipt number
seller's details
sold by (hCard candidate)
org
adr
tax number (VAT in this example)
tax id (Federal Tax ID)
buyer's details
buyer (hCard candidate)
name
org
street-address
locality
region
postal-code
country-name
tel
email
credit card number (PAN truncated - with type)
item list
product code
name
comments
price
delivery method
quantity
total in selected currency
total in sellers currency
total (sum of item list totals)
processing fee
grand total (final amount charged)
information (caveats and tax info)
permalink
</nowiki></pre>

===== Example 2 : SSL certificate =====
<pre><nowiki>
receipt title/type
seller (hCard candidate)
org
street-address
locality
region
postal-code
purchase information
order id
product name
domain name
validity period
number of licenses
card number (PAN truncated)
amount (with selected currency)
</nowiki></pre>

==== Physical product purchase receipts ====
===== Example 1 : Computer hardware =====
<pre><nowiki>
receipt title/type
seller's name (hCard candidate)
seller's URL (hCard candidate)
invoice id
org govt reference (ABN - Australian Business Number)
date
seller details (hCard candidate)
street-address
locality
region
postal-code
buyer (hCard candidate)
fn
billing address
street-address
locality
region
postal-code
delivery address
street-address
locality
region
postal-code
phone
item list
item
description
amount
quantity
product url
total
delivery cost
total excluding tax
tax (GST - Goods and Service Tax)
total including tax
</nowiki></pre>

==== Service purchase receipts ====
===== Example 1 : Online subscription =====
<pre><nowiki>
seller's details (hCard candidate)
org
street-address
locality
region
postal-code
country-name
buyer's details (hCard candidate)
fn
street-address
locality
region
postal-code
phone
date
receipt id
item list
product description
quantity
rate (per unit)
price
sub total
amount paid
balance due
information
transaction id
</nowiki></pre>

===== Example 2 : Co-location =====
<pre><nowiki>
receipt title/type
sellers details (hCard candidate)
org
url
phone
message
receipt number
date
amount
information
</nowiki></pre>

==== A1Books ====
[http://mobileonlinebusiness.com.au/uf/receipt/A1Books-Sales-Order-anon.htm Example]

*vendor
**name
**fax
*date
*order number
*shipping address
*billing address
*items
**description
**list price
**sale price
**quantity
**amount
*subtotal
*shipping
*total
**quantity
**amount
*account information
**phone
**e-mail
*payment
**method
**last four digits

No semantic HTML.

==== Barnes&Noble ====
[http://mobileonlinebusiness.com.au/uf/receipt/BarnesAndNoble.com-receipt.anon.tidied.htm Example]

*date
*shipping address
*billing address
*payment
**method
**last 4 digits
**exp. date
**charge
*savings on shipping
*order no.
*delivery option
*items
**description: title, author, ISBN, price
**qty
**gift options: wrap, message
**total price
*shipment subtotal
*shipping cost
*tax
*shipment total (seems to account for orders requiring multiple shipments)
*order total

Semantic HTML:
*receiptOrderNumbers
*receiptOrderPlacedOn
*orderInformation
**shippingAddress
**billingAddress
**paymentInformation
*shippingSelections
*showProducts
**reviewTable
***qtyValuePosition
***reviewGiftOptions
*reviewTotalsDisplay
**reviewTotalsSummary
**reviewTotalsNote
**reviewTotalsBreakdown
*reviewTotalsSummary
**reviewGrandTotal
*reviewCreditCardCharged
*review

The semantic class names found are a good start, although the "review" part appears to be context-specific (reviewing an order). Additionally, the implied hierarchy in names such as "reviewTotalsSummary" and "receiptOrderPlacedOn" is probably unnecessary for our purposes.

==== Facebook ====
[http://mobileonlinebusiness.com.au/uf/receipt/Facebook-gift-receipt.html Example]

*purchase total
*items (informal description of two items, including quantity)
*recipient name
*order id
*billed-to name

No relevant semantic HTML.

==== Google Checkout ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Google-Checkout-e-mail-receipt.tidied.html Example email receipt]
*[http://mobileonlinebusiness.com.au/uf/receipt/Google-Checkout-Order-Receipt_DVD-Empire.tidied.htm Example web receipt]

*vendor address
*shipping address
*date
*order id
*items
**shipping status ("Not yet shipped", etc.)
**qty.
**description
**price
*shipping cost
*tax
*total
*order history (placed, received, charged, shipped) (web receipt only)
*payment info (web receipt only)
**card type
**last 4 digits
**exp. date
**cardholder address
*permalink

Semantic HTML:
*taxRow
**taxIdentifier
**taxAmount
*totalAmount

==== iTunes ====
*[http://mobileonlinebusiness.com.au/uf/receipt/iTunes-receipt-e-mail.html iTunes e-mail receipt]

*billing address
*order no.
*receipt date
*order total
*card
**type
**last 4 digits
*item
**item no.
**description (including link to write a review)
**unit price
*subtotal
*tax

No relevant semantic HTML.

==== Longs/FujiFilm ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Longs-Fujifilm-photo-receipt.html Longs/Fujifilm e-mail receipt]

*order no.
*payment info
**method (COD, credit card, etc.)
*customer address
*pickup address
*items
**name
**qty.
**description
**price
**line item subtotal
*order items total
*tax
*order total

Semantic HTML:
*payment-heading

==== Mobivox/PayPal ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Mobivox-PayPal.htm Mobivox/PayPal receipt]
*[http://mobileonlinebusiness.com.au/uf/receipt/Mobivox-PayPal-printable.htm Mobivox/PayPal printable receipt]

*seller address
*receipt id
*date of order
*items
**description
**item option (not quite sure what this is for)
**unit price
**qty
**total
*subtotal
*tax
*total amount
*payment info
**method
**last 4 digits
**charge
**appears on bill/statement as "MOBIVOXCORP"
*buyer contact

Relevant semantic HTML:
*order-summary
**cart
***(unnamed tr)
****item-name
****item-total
****item-option (not quite sure what this is for)
**subtotal
**totals-value
**totals-currency
**purchase-summary
***summary-total
****price-total
****price-currency
*funding-mix
**payment-type
**amount
**ccStatement
*contact-information (contains hCard microformat)

This semantic HTML is the most complete and well-thought-out I've seen in this analysis. It even makes use of the fieldset element in forms, something I've never seen before.[[User:Lastorset|Lastorset]] 16:21, 25 Jul 2007 (PDT)

Microformats used:
*hCard (non-compliant due to missing formatted name): buyer contact info

==== Symantec ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Symantec-reminder-e-mail.html Symantec e-mail reminder]

*buyer name
*date
*payment method
*last 4 digits
*appears on statement as "DR *Symantec"
*items
**qty
**product name
**platform
**delivery method
**price
*subtotal
*grand total
*permalink

No relevant semantic HTML

=== Analysis ===

==== Analysis of Bills ====

==== Analysis of Receipts ====

== Existing Practices ==

Listed below is an overview of existing patterns and practices found in the wild for bill and receipt data.

===Summary of common patterns discovered===

===Other attempts to solve The Problem===
For paper receipts, [http://www.neatreceipts.com/ NeatReceipts Scanalizer] offers a heuristic-based solution.

== Proposal ==

== See Also ==
* [[receipt]]
* http://en.wikipedia.org/wiki/Receipt

receipt-examples

2007-08-16T22:25:29Z

Lastorset: /* A1Books */ forgot method

= Receipt =

Overview of Receipt exploratory discussion goes here...

== Authors ==

=== Contributors ===
Rob Manson

== Real-World Examples ==

=== Bill / Invoice ===

Bills or Invoices are "yet to be paid" items.

Question: Perhaps these examples (yet to be provided) should be moved to a separate page as Bill/Invoice is quite different from Receipt.

: With [[hResume]], I've [[hresume-brainstorming|suggested]] that the subtle difference between actively seeking work and just presenting your resume be a case of including [[hlisting]] markup.
: With bills vs invoices, it may turn out that the content found within would be identical, and it might just be a case of putting in a class flag to indicate whether the presented document has been paid for or not.
: [[User:SignpostMarv|SignpostMarv]] 12:55, 21 Jul 2007 (PDT)

::I think a class flag is a great idea, but I don't believe we have any samples for invoices. However, if we look at order review vs. order summary rather than invoices vs. receipts, the payment flag does become relevant in many of the sampled online stores.
::How would such a flag be implemented?
::*<code><nowiki><div class="hreceipt unpaid"/"hreceipt paid">...</nowiki></code>
::*<code><nowiki><div class="hreceipt" title="paid">...</div></nowiki></code>
::[[User:Lastorset|Lastorset]] 14:55, 16 Aug 2007 (PDT)

=== Receipts ===

Receipts are post-purchase items.

==== Amazon ====
* [http://mobileonlinebusiness.com.au/uf/receipt/Amazon.com-Vieworder-anon.htm Example]
* contains:
**<del>email address</del> (could not find in examples)
**date of order
**order id
**shipments
***shipping estimate
***delivery estimate
***shipping address
***shipping speed
***shipping preference (item grouping)
***items
****quantity
****seller
****price
****item information
**payment
***card type
***last 5 digits
***expiration date
***billing address
***subtotal
***shipping and handling price
***total before tax
***tax
***grand total
**<del>discount price</del> (could not find in examples)
* Little semantic HTML of interest, except an anchor with id "payment-info"

==== Skype ====

===== Skype Phone =====
*[[receipt-example-skype-phone|example source code]]
*[http://mobileonlinebusiness.com.au/uf/receipt/Skype-order-history.html Skype order history]

* Shipping Address
* date in dd/mm/yyyy format
* Order number in nnnn-nnnnnnn-nnn format
* Reference (was blank in example, presumed to appear on bank statement for this transaction)
* Items
** Quantity
** Description
** Price
** Total
** VAT (tax) %
* Payment
** subtotal ("total")
** shipping cost
** grand total ("total (gross)")
** total (VAT excluded)
** VAT (amount)
* Chosen payment method: "Your payment method is: Credit card"
* Legal blurb

Semantic HTML:
* Order resume class="order-listing"
* Each item class="row"
* All totals rows class="totals-row" except grand total class="grandtotal-row"

==== Internet banking transaction receipts ====
===== Example 1 =====
<pre><nowiki>
receipt number
date
time
receipt type (e.g. TRANSFER BETWEEN MY ACCOUNTS)
transfer from
transfer to
amount
description
information/comment
</nowiki></pre>

==== Digital product purchase receipts ====
===== Example 1 : Software =====
<pre><nowiki>
receipt title/type
order/receipt number
seller's details
sold by (hCard candidate)
org
adr
tax number (VAT in this example)
tax id (Federal Tax ID)
buyer's details
buyer (hCard candidate)
name
org
street-address
locality
region
postal-code
country-name
tel
email
credit card number (PAN truncated - with type)
item list
product code
name
comments
price
delivery method
quantity
total in selected currency
total in sellers currency
total (sum of item list totals)
processing fee
grand total (final amount charged)
information (caveats and tax info)
permalink
</nowiki></pre>

===== Example 2 : SSL certificate =====
<pre><nowiki>
receipt title/type
seller (hCard candidate)
org
street-address
locality
region
postal-code
purchase information
order id
product name
domain name
validity period
number of licenses
card number (PAN truncated)
amount (with selected currency)
</nowiki></pre>

==== Physical product purchase receipts ====
===== Example 1 : Computer hardware =====
<pre><nowiki>
receipt title/type
seller's name (hCard candidate)
seller's URL (hCard candidate)
invoice id
org govt reference (ABN - Australian Business Number)
date
seller details (hCard candidate)
street-address
locality
region
postal-code
buyer (hCard candidate)
fn
billing address
street-address
locality
region
postal-code
delivery address
street-address
locality
region
postal-code
phone
item list
item
description
amount
quantity
product url
total
delivery cost
total excluding tax
tax (GST - Goods and Service Tax)
total including tax
</nowiki></pre>

==== Service purchase receipts ====
===== Example 1 : Online subscription =====
<pre><nowiki>
seller's details (hCard candidate)
org
street-address
locality
region
postal-code
country-name
buyer's details (hCard candidate)
fn
street-address
locality
region
postal-code
phone
date
receipt id
item list
product description
quantity
rate (per unit)
price
sub total
amount paid
balance due
information
transaction id
</nowiki></pre>

===== Example 2 : Co-location =====
<pre><nowiki>
receipt title/type
sellers details (hCard candidate)
org
url
phone
message
receipt number
date
amount
information
</nowiki></pre>

==== A1Books ====
[http://mobileonlinebusiness.com.au/uf/receipt/A1Books-Sales-Order-anon.htm Example]

*vendor
**name
**fax
*date
*order number
*shipping address
*billing address
*items
**description
**list price
**sale price
**quantity
**amount
*subtotal
*shipping
*total
**quantity
**amount
*account information
**phone
**e-mail
*payment
**method
**last four digits

No semantic HTML.

==== Barnes&Noble ====
[http://mobileonlinebusiness.com.au/uf/receipt/BarnesAndNoble.com-receipt.anon.tidied.htm Example]

*shipping address
*billing address
*payment
**method
**last 4 digits
**exp. date
**charge
*savings on shipping
*order no.
*delivery option
*items
**description: title, author, ISBN, price
**qty
**gift options: wrap, message
**total price
*shipment subtotal
*shipping cost
*tax
*shipment total (seems to account for orders requiring multiple shipments)
*order total

Semantic HTML:
*receiptOrderNumbers
*receiptOrderPlacedOn
*orderInformation
**shippingAddress
**billingAddress
**paymentInformation
*shippingSelections
*showProducts
**reviewTable
***qtyValuePosition
***reviewGiftOptions
*reviewTotalsDisplay
**reviewTotalsSummary
**reviewTotalsNote
**reviewTotalsBreakdown
*reviewTotalsSummary
**reviewGrandTotal
*reviewCreditCardCharged
*review

The semantic class names found are a good start, although the "review" part appears to be context-specific (reviewing an order). Additionally, the implied hierarchy in names such as "reviewTotalsSummary" and "receiptOrderPlacedOn" is probably unnecessary for our purposes.

==== Facebook ====
[http://mobileonlinebusiness.com.au/uf/receipt/Facebook-gift-receipt.html Example]

*purchase total
*items (informal description of two items, including quantity)
*recipient name
*order id
*billed-to name

No relevant semantic HTML.

==== Google Checkout ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Google-Checkout-e-mail-receipt.tidied.html Example email receipt]
*[http://mobileonlinebusiness.com.au/uf/receipt/Google-Checkout-Order-Receipt_DVD-Empire.tidied.htm Example web receipt]

*vendor address
*shipping address
*date
*order id
*items
**shipping status ("Not yet shipped", etc.)
**qty.
**description
**price
*shipping cost
*tax
*total
*order history (placed, received, charged, shipped) (web receipt only)
*payment info (web receipt only)
**card type
**last 4 digits
**exp. date
**cardholder address
*permalink

Semantic HTML:
*taxRow
**taxIdentifier
**taxAmount
*totalAmount

==== iTunes ====
*[http://mobileonlinebusiness.com.au/uf/receipt/iTunes-receipt-e-mail.html iTunes e-mail receipt]

*billing address
*order no.
*receipt date
*order total
*card
**type
**last 4 digits
*item
**item no.
**description (including link to write a review)
**unit price
*subtotal
*tax

No relevant semantic HTML.

==== Longs/FujiFilm ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Longs-Fujifilm-photo-receipt.html Longs/Fujifilm e-mail receipt]

*order no.
*payment info
**method (COD, credit card, etc.)
*customer address
*pickup address
*items
**name
**qty.
**description
**price
**line item subtotal
*order items total
*tax
*order total

Semantic HTML:
*payment-heading

==== Mobivox/PayPal ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Mobivox-PayPal.htm Mobivox/PayPal receipt]
*[http://mobileonlinebusiness.com.au/uf/receipt/Mobivox-PayPal-printable.htm Mobivox/PayPal printable receipt]

*seller address
*receipt id
*date of order
*items
**description
**item option (not quite sure what this is for)
**unit price
**qty
**total
*subtotal
*tax
*total amount
*payment info
**method
**last 4 digits
**charge
**appears on bill/statement as "MOBIVOXCORP"
*buyer contact

Relevant semantic HTML:
*order-summary
**cart
***(unnamed tr)
****item-name
****item-total
****item-option (not quite sure what this is for)
**subtotal
**totals-value
**totals-currency
**purchase-summary
***summary-total
****price-total
****price-currency
*funding-mix
**payment-type
**amount
**ccStatement
*contact-information (contains hCard microformat)

This semantic HTML is the most complete and well-thought-out I've seen in this analysis. It even makes use of the fieldset element in forms, something I've never seen before.[[User:Lastorset|Lastorset]] 16:21, 25 Jul 2007 (PDT)

Microformats used:
*hCard (non-compliant due to missing formatted name): buyer contact info

==== Symantec ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Symantec-reminder-e-mail.html Symantec e-mail reminder]

*buyer name
*date
*payment method
*last 4 digits
*appears on statement as "DR *Symantec"
*items
**qty
**product name
**platform
**delivery method
**price
*subtotal
*grand total
*permalink

No relevant semantic HTML

=== Analysis ===

==== Analysis of Bills ====

==== Analysis of Receipts ====

== Existing Practices ==

Listed below is an overview of existing patterns and practices found in the wild for bill and receipt data.

===Summary of common patterns discovered===

===Other attempts to solve The Problem===
For paper receipts, [http://www.neatreceipts.com/ NeatReceipts Scanalizer] offers a heuristic-based solution.

== Proposal ==

== See Also ==
* [[receipt]]
* http://en.wikipedia.org/wiki/Receipt

receipt-examples

2007-08-16T22:24:47Z

Lastorset: /* Barnes&Noble */ forgot method

= Receipt =

Overview of Receipt exploratory discussion goes here...

== Authors ==

=== Contributors ===
Rob Manson

== Real-World Examples ==

=== Bill / Invoice ===

Bills or Invoices are "yet to be paid" items.

Question: Perhaps these examples (yet to be provided) should be moved to a separate page as Bill/Invoice is quite different from Receipt.

: With [[hResume]], I've [[hresume-brainstorming|suggested]] that the subtle difference between actively seeking work and just presenting your resume be a case of including [[hlisting]] markup.
: With bills vs invoices, it may turn out that the content found within would be identical, and it might just be a case of putting in a class flag to indicate whether the presented document has been paid for or not.
: [[User:SignpostMarv|SignpostMarv]] 12:55, 21 Jul 2007 (PDT)

::I think a class flag is a great idea, but I don't believe we have any samples for invoices. However, if we look at order review vs. order summary rather than invoices vs. receipts, the payment flag does become relevant in many of the sampled online stores.
::How would such a flag be implemented?
::*<code><nowiki><div class="hreceipt unpaid"/"hreceipt paid">...</nowiki></code>
::*<code><nowiki><div class="hreceipt" title="paid">...</div></nowiki></code>
::[[User:Lastorset|Lastorset]] 14:55, 16 Aug 2007 (PDT)

=== Receipts ===

Receipts are post-purchase items.

==== Amazon ====
* [http://mobileonlinebusiness.com.au/uf/receipt/Amazon.com-Vieworder-anon.htm Example]
* contains:
**<del>email address</del> (could not find in examples)
**date of order
**order id
**shipments
***shipping estimate
***delivery estimate
***shipping address
***shipping speed
***shipping preference (item grouping)
***items
****quantity
****seller
****price
****item information
**payment
***card type
***last 5 digits
***expiration date
***billing address
***subtotal
***shipping and handling price
***total before tax
***tax
***grand total
**<del>discount price</del> (could not find in examples)
* Little semantic HTML of interest, except an anchor with id "payment-info"

==== Skype ====

===== Skype Phone =====
*[[receipt-example-skype-phone|example source code]]
*[http://mobileonlinebusiness.com.au/uf/receipt/Skype-order-history.html Skype order history]

* Shipping Address
* date in dd/mm/yyyy format
* Order number in nnnn-nnnnnnn-nnn format
* Reference (was blank in example, presumed to appear on bank statement for this transaction)
* Items
** Quantity
** Description
** Price
** Total
** VAT (tax) %
* Payment
** subtotal ("total")
** shipping cost
** grand total ("total (gross)")
** total (VAT excluded)
** VAT (amount)
* Chosen payment method: "Your payment method is: Credit card"
* Legal blurb

Semantic HTML:
* Order resume class="order-listing"
* Each item class="row"
* All totals rows class="totals-row" except grand total class="grandtotal-row"

==== Internet banking transaction receipts ====
===== Example 1 =====
<pre><nowiki>
receipt number
date
time
receipt type (e.g. TRANSFER BETWEEN MY ACCOUNTS)
transfer from
transfer to
amount
description
information/comment
</nowiki></pre>

==== Digital product purchase receipts ====
===== Example 1 : Software =====
<pre><nowiki>
receipt title/type
order/receipt number
seller's details
sold by (hCard candidate)
org
adr
tax number (VAT in this example)
tax id (Federal Tax ID)
buyer's details
buyer (hCard candidate)
name
org
street-address
locality
region
postal-code
country-name
tel
email
credit card number (PAN truncated - with type)
item list
product code
name
comments
price
delivery method
quantity
total in selected currency
total in sellers currency
total (sum of item list totals)
processing fee
grand total (final amount charged)
information (caveats and tax info)
permalink
</nowiki></pre>

===== Example 2 : SSL certificate =====
<pre><nowiki>
receipt title/type
seller (hCard candidate)
org
street-address
locality
region
postal-code
purchase information
order id
product name
domain name
validity period
number of licenses
card number (PAN truncated)
amount (with selected currency)
</nowiki></pre>

==== Physical product purchase receipts ====
===== Example 1 : Computer hardware =====
<pre><nowiki>
receipt title/type
seller's name (hCard candidate)
seller's URL (hCard candidate)
invoice id
org govt reference (ABN - Australian Business Number)
date
seller details (hCard candidate)
street-address
locality
region
postal-code
buyer (hCard candidate)
fn
billing address
street-address
locality
region
postal-code
delivery address
street-address
locality
region
postal-code
phone
item list
item
description
amount
quantity
product url
total
delivery cost
total excluding tax
tax (GST - Goods and Service Tax)
total including tax
</nowiki></pre>

==== Service purchase receipts ====
===== Example 1 : Online subscription =====
<pre><nowiki>
seller's details (hCard candidate)
org
street-address
locality
region
postal-code
country-name
buyer's details (hCard candidate)
fn
street-address
locality
region
postal-code
phone
date
receipt id
item list
product description
quantity
rate (per unit)
price
sub total
amount paid
balance due
information
transaction id
</nowiki></pre>

===== Example 2 : Co-location =====
<pre><nowiki>
receipt title/type
sellers details (hCard candidate)
org
url
phone
message
receipt number
date
amount
information
</nowiki></pre>

==== A1Books ====
[http://mobileonlinebusiness.com.au/uf/receipt/A1Books-Sales-Order-anon.htm Example]

*vendor
**name
**fax
*date
*order number
*shipping address
*billing address
*items
**description
**list price
**sale price
**quantity
**amount
*subtotal
*shipping
*total
**quantity
**amount
*account information
**phone
**e-mail
*credit card last four digits

No semantic HTML.

==== Barnes&Noble ====
[http://mobileonlinebusiness.com.au/uf/receipt/BarnesAndNoble.com-receipt.anon.tidied.htm Example]

*shipping address
*billing address
*payment
**method
**last 4 digits
**exp. date
**charge
*savings on shipping
*order no.
*delivery option
*items
**description: title, author, ISBN, price
**qty
**gift options: wrap, message
**total price
*shipment subtotal
*shipping cost
*tax
*shipment total (seems to account for orders requiring multiple shipments)
*order total

Semantic HTML:
*receiptOrderNumbers
*receiptOrderPlacedOn
*orderInformation
**shippingAddress
**billingAddress
**paymentInformation
*shippingSelections
*showProducts
**reviewTable
***qtyValuePosition
***reviewGiftOptions
*reviewTotalsDisplay
**reviewTotalsSummary
**reviewTotalsNote
**reviewTotalsBreakdown
*reviewTotalsSummary
**reviewGrandTotal
*reviewCreditCardCharged
*review

The semantic class names found are a good start, although the "review" part appears to be context-specific (reviewing an order). Additionally, the implied hierarchy in names such as "reviewTotalsSummary" and "receiptOrderPlacedOn" is probably unnecessary for our purposes.

==== Facebook ====
[http://mobileonlinebusiness.com.au/uf/receipt/Facebook-gift-receipt.html Example]

*purchase total
*items (informal description of two items, including quantity)
*recipient name
*order id
*billed-to name

No relevant semantic HTML.

==== Google Checkout ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Google-Checkout-e-mail-receipt.tidied.html Example email receipt]
*[http://mobileonlinebusiness.com.au/uf/receipt/Google-Checkout-Order-Receipt_DVD-Empire.tidied.htm Example web receipt]

*vendor address
*shipping address
*date
*order id
*items
**shipping status ("Not yet shipped", etc.)
**qty.
**description
**price
*shipping cost
*tax
*total
*order history (placed, received, charged, shipped) (web receipt only)
*payment info (web receipt only)
**card type
**last 4 digits
**exp. date
**cardholder address
*permalink

Semantic HTML:
*taxRow
**taxIdentifier
**taxAmount
*totalAmount

==== iTunes ====
*[http://mobileonlinebusiness.com.au/uf/receipt/iTunes-receipt-e-mail.html iTunes e-mail receipt]

*billing address
*order no.
*receipt date
*order total
*card
**type
**last 4 digits
*item
**item no.
**description (including link to write a review)
**unit price
*subtotal
*tax

No relevant semantic HTML.

==== Longs/FujiFilm ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Longs-Fujifilm-photo-receipt.html Longs/Fujifilm e-mail receipt]

*order no.
*payment info
**method (COD, credit card, etc.)
*customer address
*pickup address
*items
**name
**qty.
**description
**price
**line item subtotal
*order items total
*tax
*order total

Semantic HTML:
*payment-heading

==== Mobivox/PayPal ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Mobivox-PayPal.htm Mobivox/PayPal receipt]
*[http://mobileonlinebusiness.com.au/uf/receipt/Mobivox-PayPal-printable.htm Mobivox/PayPal printable receipt]

*seller address
*receipt id
*date of order
*items
**description
**item option (not quite sure what this is for)
**unit price
**qty
**total
*subtotal
*tax
*total amount
*payment info
**method
**last 4 digits
**charge
**appears on bill/statement as "MOBIVOXCORP"
*buyer contact

Relevant semantic HTML:
*order-summary
**cart
***(unnamed tr)
****item-name
****item-total
****item-option (not quite sure what this is for)
**subtotal
**totals-value
**totals-currency
**purchase-summary
***summary-total
****price-total
****price-currency
*funding-mix
**payment-type
**amount
**ccStatement
*contact-information (contains hCard microformat)

This semantic HTML is the most complete and well-thought-out I've seen in this analysis. It even makes use of the fieldset element in forms, something I've never seen before.[[User:Lastorset|Lastorset]] 16:21, 25 Jul 2007 (PDT)

Microformats used:
*hCard (non-compliant due to missing formatted name): buyer contact info

==== Symantec ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Symantec-reminder-e-mail.html Symantec e-mail reminder]

*buyer name
*date
*payment method
*last 4 digits
*appears on statement as "DR *Symantec"
*items
**qty
**product name
**platform
**delivery method
**price
*subtotal
*grand total
*permalink

No relevant semantic HTML

=== Analysis ===

==== Analysis of Bills ====

==== Analysis of Receipts ====

== Existing Practices ==

Listed below is an overview of existing patterns and practices found in the wild for bill and receipt data.

===Summary of common patterns discovered===

===Other attempts to solve The Problem===
For paper receipts, [http://www.neatreceipts.com/ NeatReceipts Scanalizer] offers a heuristic-based solution.

== Proposal ==

== See Also ==
* [[receipt]]
* http://en.wikipedia.org/wiki/Receipt

receipt-examples

2007-08-16T22:09:12Z

Lastorset: /* Skype Phone */ adjusted to more closely reflect sample

= Receipt =

Overview of Receipt exploratory discussion goes here...

== Authors ==

=== Contributors ===
Rob Manson

== Real-World Examples ==

=== Bill / Invoice ===

Bills or Invoices are "yet to be paid" items.

Question: Perhaps these examples (yet to be provided) should be moved to a separate page as Bill/Invoice is quite different from Receipt.

: With [[hResume]], I've [[hresume-brainstorming|suggested]] that the subtle difference between actively seeking work and just presenting your resume be a case of including [[hlisting]] markup.
: With bills vs invoices, it may turn out that the content found within would be identical, and it might just be a case of putting in a class flag to indicate whether the presented document has been paid for or not.
: [[User:SignpostMarv|SignpostMarv]] 12:55, 21 Jul 2007 (PDT)

::I think a class flag is a great idea, but I don't believe we have any samples for invoices. However, if we look at order review vs. order summary rather than invoices vs. receipts, the payment flag does become relevant in many of the sampled online stores.
::How would such a flag be implemented?
::*<code><nowiki><div class="hreceipt unpaid"/"hreceipt paid">...</nowiki></code>
::*<code><nowiki><div class="hreceipt" title="paid">...</div></nowiki></code>
::[[User:Lastorset|Lastorset]] 14:55, 16 Aug 2007 (PDT)

=== Receipts ===

Receipts are post-purchase items.

==== Amazon ====
* [http://mobileonlinebusiness.com.au/uf/receipt/Amazon.com-Vieworder-anon.htm Example]
* contains:
**<del>email address</del> (could not find in examples)
**date of order
**order id
**shipments
***shipping estimate
***delivery estimate
***shipping address
***shipping speed
***shipping preference (item grouping)
***items
****quantity
****seller
****price
****item information
**payment
***card type
***last 5 digits
***expiration date
***billing address
***subtotal
***shipping and handling price
***total before tax
***tax
***grand total
**<del>discount price</del> (could not find in examples)
* Little semantic HTML of interest, except an anchor with id "payment-info"

==== Skype ====

===== Skype Phone =====
*[[receipt-example-skype-phone|example source code]]
*[http://mobileonlinebusiness.com.au/uf/receipt/Skype-order-history.html Skype order history]

* Shipping Address
* date in dd/mm/yyyy format
* Order number in nnnn-nnnnnnn-nnn format
* Reference (was blank in example, presumed to appear on bank statement for this transaction)
* Items
** Quantity
** Description
** Price
** Total
** VAT (tax) %
* Payment
** subtotal ("total")
** shipping cost
** grand total ("total (gross)")
** total (VAT excluded)
** VAT (amount)
* Chosen payment method: "Your payment method is: Credit card"
* Legal blurb

Semantic HTML:
* Order resume class="order-listing"
* Each item class="row"
* All totals rows class="totals-row" except grand total class="grandtotal-row"

==== Internet banking transaction receipts ====
===== Example 1 =====
<pre><nowiki>
receipt number
date
time
receipt type (e.g. TRANSFER BETWEEN MY ACCOUNTS)
transfer from
transfer to
amount
description
information/comment
</nowiki></pre>

==== Digital product purchase receipts ====
===== Example 1 : Software =====
<pre><nowiki>
receipt title/type
order/receipt number
seller's details
sold by (hCard candidate)
org
adr
tax number (VAT in this example)
tax id (Federal Tax ID)
buyer's details
buyer (hCard candidate)
name
org
street-address
locality
region
postal-code
country-name
tel
email
credit card number (PAN truncated - with type)
item list
product code
name
comments
price
delivery method
quantity
total in selected currency
total in sellers currency
total (sum of item list totals)
processing fee
grand total (final amount charged)
information (caveats and tax info)
permalink
</nowiki></pre>

===== Example 2 : SSL certificate =====
<pre><nowiki>
receipt title/type
seller (hCard candidate)
org
street-address
locality
region
postal-code
purchase information
order id
product name
domain name
validity period
number of licenses
card number (PAN truncated)
amount (with selected currency)
</nowiki></pre>

==== Physical product purchase receipts ====
===== Example 1 : Computer hardware =====
<pre><nowiki>
receipt title/type
seller's name (hCard candidate)
seller's URL (hCard candidate)
invoice id
org govt reference (ABN - Australian Business Number)
date
seller details (hCard candidate)
street-address
locality
region
postal-code
buyer (hCard candidate)
fn
billing address
street-address
locality
region
postal-code
delivery address
street-address
locality
region
postal-code
phone
item list
item
description
amount
quantity
product url
total
delivery cost
total excluding tax
tax (GST - Goods and Service Tax)
total including tax
</nowiki></pre>

==== Service purchase receipts ====
===== Example 1 : Online subscription =====
<pre><nowiki>
seller's details (hCard candidate)
org
street-address
locality
region
postal-code
country-name
buyer's details (hCard candidate)
fn
street-address
locality
region
postal-code
phone
date
receipt id
item list
product description
quantity
rate (per unit)
price
sub total
amount paid
balance due
information
transaction id
</nowiki></pre>

===== Example 2 : Co-location =====
<pre><nowiki>
receipt title/type
sellers details (hCard candidate)
org
url
phone
message
receipt number
date
amount
information
</nowiki></pre>

==== A1Books ====
[http://mobileonlinebusiness.com.au/uf/receipt/A1Books-Sales-Order-anon.htm Example]

*vendor
**name
**fax
*date
*order number
*shipping address
*billing address
*items
**description
**list price
**sale price
**quantity
**amount
*subtotal
*shipping
*total
**quantity
**amount
*account information
**phone
**e-mail
*credit card last four digits

No semantic HTML.

==== Barnes&Noble ====
[http://mobileonlinebusiness.com.au/uf/receipt/BarnesAndNoble.com-receipt.anon.tidied.htm Example]

*shipping address
*billing address
*payment
**last 4 digits
**exp. date
**charge
*savings on shipping
*order no.
*delivery option
*items
**description: title, author, ISBN, price
**qty
**gift options: wrap, message
**total price
*shipment subtotal
*shipping cost
*tax
*shipment total (seems to account for orders requiring multiple shipments)
*order total

Semantic HTML:
*receiptOrderNumbers
*receiptOrderPlacedOn
*orderInformation
**shippingAddress
**billingAddress
**paymentInformation
*shippingSelections
*showProducts
**reviewTable
***qtyValuePosition
***reviewGiftOptions
*reviewTotalsDisplay
**reviewTotalsSummary
**reviewTotalsNote
**reviewTotalsBreakdown
*reviewTotalsSummary
**reviewGrandTotal
*reviewCreditCardCharged
*review

The semantic class names found are a good start, although the "review" part appears to be context-specific (reviewing an order). Additionally, the implied hierarchy in names such as "reviewTotalsSummary" and "receiptOrderPlacedOn" is probably unnecessary for our purposes.

==== Facebook ====
[http://mobileonlinebusiness.com.au/uf/receipt/Facebook-gift-receipt.html Example]

*purchase total
*items (informal description of two items, including quantity)
*recipient name
*order id
*billed-to name

No relevant semantic HTML.

==== Google Checkout ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Google-Checkout-e-mail-receipt.tidied.html Example email receipt]
*[http://mobileonlinebusiness.com.au/uf/receipt/Google-Checkout-Order-Receipt_DVD-Empire.tidied.htm Example web receipt]

*vendor address
*shipping address
*date
*order id
*items
**shipping status ("Not yet shipped", etc.)
**qty.
**description
**price
*shipping cost
*tax
*total
*order history (placed, received, charged, shipped) (web receipt only)
*payment info (web receipt only)
**card type
**last 4 digits
**exp. date
**cardholder address
*permalink

Semantic HTML:
*taxRow
**taxIdentifier
**taxAmount
*totalAmount

==== iTunes ====
*[http://mobileonlinebusiness.com.au/uf/receipt/iTunes-receipt-e-mail.html iTunes e-mail receipt]

*billing address
*order no.
*receipt date
*order total
*card
**type
**last 4 digits
*item
**item no.
**description (including link to write a review)
**unit price
*subtotal
*tax

No relevant semantic HTML.

==== Longs/FujiFilm ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Longs-Fujifilm-photo-receipt.html Longs/Fujifilm e-mail receipt]

*order no.
*payment info
**method (COD, credit card, etc.)
*customer address
*pickup address
*items
**name
**qty.
**description
**price
**line item subtotal
*order items total
*tax
*order total

Semantic HTML:
*payment-heading

==== Mobivox/PayPal ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Mobivox-PayPal.htm Mobivox/PayPal receipt]
*[http://mobileonlinebusiness.com.au/uf/receipt/Mobivox-PayPal-printable.htm Mobivox/PayPal printable receipt]

*seller address
*receipt id
*date of order
*items
**description
**item option (not quite sure what this is for)
**unit price
**qty
**total
*subtotal
*tax
*total amount
*payment info
**method
**last 4 digits
**charge
**appears on bill/statement as "MOBIVOXCORP"
*buyer contact

Relevant semantic HTML:
*order-summary
**cart
***(unnamed tr)
****item-name
****item-total
****item-option (not quite sure what this is for)
**subtotal
**totals-value
**totals-currency
**purchase-summary
***summary-total
****price-total
****price-currency
*funding-mix
**payment-type
**amount
**ccStatement
*contact-information (contains hCard microformat)

This semantic HTML is the most complete and well-thought-out I've seen in this analysis. It even makes use of the fieldset element in forms, something I've never seen before.[[User:Lastorset|Lastorset]] 16:21, 25 Jul 2007 (PDT)

Microformats used:
*hCard (non-compliant due to missing formatted name): buyer contact info

==== Symantec ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Symantec-reminder-e-mail.html Symantec e-mail reminder]

*buyer name
*date
*payment method
*last 4 digits
*appears on statement as "DR *Symantec"
*items
**qty
**product name
**platform
**delivery method
**price
*subtotal
*grand total
*permalink

No relevant semantic HTML

=== Analysis ===

==== Analysis of Bills ====

==== Analysis of Receipts ====

== Existing Practices ==

Listed below is an overview of existing patterns and practices found in the wild for bill and receipt data.

===Summary of common patterns discovered===

===Other attempts to solve The Problem===
For paper receipts, [http://www.neatreceipts.com/ NeatReceipts Scanalizer] offers a heuristic-based solution.

== Proposal ==

== See Also ==
* [[receipt]]
* http://en.wikipedia.org/wiki/Receipt

User:Lastorset

2007-08-16T21:58:00Z

Lastorset: thanks

Lastorset, you may want to change your User page code to (remove the nowiki tags in the source to have it mean something) :

<nowiki>{{public-domain-release}}</nowiki>

[[User:Tantek|Tantek]] 17:58, 17 Jul 2007 (PDT)
:Thanks, Tantek![[User:Lastorset| Leif Arne Storset]] 14:58, 16 Aug 2007 (PDT)

{{public-domain-release}}

receipt-examples

2007-08-16T21:55:12Z

Lastorset: /* Bill / Invoice */ comment

= Receipt =

Overview of Receipt exploratory discussion goes here...

== Authors ==

=== Contributors ===
Rob Manson

== Real-World Examples ==

=== Bill / Invoice ===

Bills or Invoices are "yet to be paid" items.

Question: Perhaps these examples (yet to be provided) should be moved to a separate page as Bill/Invoice is quite different from Receipt.

: With [[hResume]], I've [[hresume-brainstorming|suggested]] that the subtle difference between actively seeking work and just presenting your resume be a case of including [[hlisting]] markup.
: With bills vs invoices, it may turn out that the content found within would be identical, and it might just be a case of putting in a class flag to indicate whether the presented document has been paid for or not.
: [[User:SignpostMarv|SignpostMarv]] 12:55, 21 Jul 2007 (PDT)

::I think a class flag is a great idea, but I don't believe we have any samples for invoices. However, if we look at order review vs. order summary rather than invoices vs. receipts, the payment flag does become relevant in many of the sampled online stores.
::How would such a flag be implemented?
::*<code><nowiki><div class="hreceipt unpaid"/"hreceipt paid">...</nowiki></code>
::*<code><nowiki><div class="hreceipt" title="paid">...</div></nowiki></code>
::[[User:Lastorset|Lastorset]] 14:55, 16 Aug 2007 (PDT)

=== Receipts ===

Receipts are post-purchase items.

==== Amazon ====
* [http://mobileonlinebusiness.com.au/uf/receipt/Amazon.com-Vieworder-anon.htm Example]
* contains:
**<del>email address</del> (could not find in examples)
**date of order
**order id
**shipments
***shipping estimate
***delivery estimate
***shipping address
***shipping speed
***shipping preference (item grouping)
***items
****quantity
****seller
****price
****item information
**payment
***card type
***last 5 digits
***expiration date
***billing address
***subtotal
***shipping and handling price
***total before tax
***tax
***grand total
**<del>discount price</del> (could not find in examples)
* Little semantic HTML of interest, except an anchor with id "payment-info"

==== Skype ====

===== Skype Phone =====
*[[receipt-example-skype-phone|example source code]]
*[http://mobileonlinebusiness.com.au/uf/receipt/Skype-order-history.html Skype order history]

* Name
* Shipping Address
* Order blurb "Confirmation of incoming order"
** date in dd/mm/yyyy format
* Order number in nnnn-nnnnnnn-nnn format
* Reference (was blank in example, presumed to appear on bank statement for this transaction)
* Order resume
** Quantity
** Description
** Price
** Total
** VAT (tax) %
* Payment
** subtotal
** shipping cost
** VAT (percentage)
** grand total
** total (VAT excluded)
** VAT (amount)
* Notification of chosen payment method blurb: "Your payment method is: Credit card"
* Legal blurb

Semantic HTML:
* Order resume class="order-listing"
* Each item class="row"
* All totals rows class="totals-row" except grand total class="grandtotal-row"

==== Internet banking transaction receipts ====
===== Example 1 =====
<pre><nowiki>
receipt number
date
time
receipt type (e.g. TRANSFER BETWEEN MY ACCOUNTS)
transfer from
transfer to
amount
description
information/comment
</nowiki></pre>

==== Digital product purchase receipts ====
===== Example 1 : Software =====
<pre><nowiki>
receipt title/type
order/receipt number
seller's details
sold by (hCard candidate)
org
adr
tax number (VAT in this example)
tax id (Federal Tax ID)
buyer's details
buyer (hCard candidate)
name
org
street-address
locality
region
postal-code
country-name
tel
email
credit card number (PAN truncated - with type)
item list
product code
name
comments
price
delivery method
quantity
total in selected currency
total in sellers currency
total (sum of item list totals)
processing fee
grand total (final amount charged)
information (caveats and tax info)
permalink
</nowiki></pre>

===== Example 2 : SSL certificate =====
<pre><nowiki>
receipt title/type
seller (hCard candidate)
org
street-address
locality
region
postal-code
purchase information
order id
product name
domain name
validity period
number of licenses
card number (PAN truncated)
amount (with selected currency)
</nowiki></pre>

==== Physical product purchase receipts ====
===== Example 1 : Computer hardware =====
<pre><nowiki>
receipt title/type
seller's name (hCard candidate)
seller's URL (hCard candidate)
invoice id
org govt reference (ABN - Australian Business Number)
date
seller details (hCard candidate)
street-address
locality
region
postal-code
buyer (hCard candidate)
fn
billing address
street-address
locality
region
postal-code
delivery address
street-address
locality
region
postal-code
phone
item list
item
description
amount
quantity
product url
total
delivery cost
total excluding tax
tax (GST - Goods and Service Tax)
total including tax
</nowiki></pre>

==== Service purchase receipts ====
===== Example 1 : Online subscription =====
<pre><nowiki>
seller's details (hCard candidate)
org
street-address
locality
region
postal-code
country-name
buyer's details (hCard candidate)
fn
street-address
locality
region
postal-code
phone
date
receipt id
item list
product description
quantity
rate (per unit)
price
sub total
amount paid
balance due
information
transaction id
</nowiki></pre>

===== Example 2 : Co-location =====
<pre><nowiki>
receipt title/type
sellers details (hCard candidate)
org
url
phone
message
receipt number
date
amount
information
</nowiki></pre>

==== A1Books ====
[http://mobileonlinebusiness.com.au/uf/receipt/A1Books-Sales-Order-anon.htm Example]

*vendor
**name
**fax
*date
*order number
*shipping address
*billing address
*items
**description
**list price
**sale price
**quantity
**amount
*subtotal
*shipping
*total
**quantity
**amount
*account information
**phone
**e-mail
*credit card last four digits

No semantic HTML.

==== Barnes&Noble ====
[http://mobileonlinebusiness.com.au/uf/receipt/BarnesAndNoble.com-receipt.anon.tidied.htm Example]

*shipping address
*billing address
*payment
**last 4 digits
**exp. date
**charge
*savings on shipping
*order no.
*delivery option
*items
**description: title, author, ISBN, price
**qty
**gift options: wrap, message
**total price
*shipment subtotal
*shipping cost
*tax
*shipment total (seems to account for orders requiring multiple shipments)
*order total

Semantic HTML:
*receiptOrderNumbers
*receiptOrderPlacedOn
*orderInformation
**shippingAddress
**billingAddress
**paymentInformation
*shippingSelections
*showProducts
**reviewTable
***qtyValuePosition
***reviewGiftOptions
*reviewTotalsDisplay
**reviewTotalsSummary
**reviewTotalsNote
**reviewTotalsBreakdown
*reviewTotalsSummary
**reviewGrandTotal
*reviewCreditCardCharged
*review

The semantic class names found are a good start, although the "review" part appears to be context-specific (reviewing an order). Additionally, the implied hierarchy in names such as "reviewTotalsSummary" and "receiptOrderPlacedOn" is probably unnecessary for our purposes.

==== Facebook ====
[http://mobileonlinebusiness.com.au/uf/receipt/Facebook-gift-receipt.html Example]

*purchase total
*items (informal description of two items, including quantity)
*recipient name
*order id
*billed-to name

No relevant semantic HTML.

==== Google Checkout ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Google-Checkout-e-mail-receipt.tidied.html Example email receipt]
*[http://mobileonlinebusiness.com.au/uf/receipt/Google-Checkout-Order-Receipt_DVD-Empire.tidied.htm Example web receipt]

*vendor address
*shipping address
*date
*order id
*items
**shipping status ("Not yet shipped", etc.)
**qty.
**description
**price
*shipping cost
*tax
*total
*order history (placed, received, charged, shipped) (web receipt only)
*payment info (web receipt only)
**card type
**last 4 digits
**exp. date
**cardholder address
*permalink

Semantic HTML:
*taxRow
**taxIdentifier
**taxAmount
*totalAmount

==== iTunes ====
*[http://mobileonlinebusiness.com.au/uf/receipt/iTunes-receipt-e-mail.html iTunes e-mail receipt]

*billing address
*order no.
*receipt date
*order total
*card
**type
**last 4 digits
*item
**item no.
**description (including link to write a review)
**unit price
*subtotal
*tax

No relevant semantic HTML.

==== Longs/FujiFilm ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Longs-Fujifilm-photo-receipt.html Longs/Fujifilm e-mail receipt]

*order no.
*payment info
**method (COD, credit card, etc.)
*customer address
*pickup address
*items
**name
**qty.
**description
**price
**line item subtotal
*order items total
*tax
*order total

Semantic HTML:
*payment-heading

==== Mobivox/PayPal ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Mobivox-PayPal.htm Mobivox/PayPal receipt]
*[http://mobileonlinebusiness.com.au/uf/receipt/Mobivox-PayPal-printable.htm Mobivox/PayPal printable receipt]

*seller address
*receipt id
*date of order
*items
**description
**item option (not quite sure what this is for)
**unit price
**qty
**total
*subtotal
*tax
*total amount
*payment info
**method
**last 4 digits
**charge
**appears on bill/statement as "MOBIVOXCORP"
*buyer contact

Relevant semantic HTML:
*order-summary
**cart
***(unnamed tr)
****item-name
****item-total
****item-option (not quite sure what this is for)
**subtotal
**totals-value
**totals-currency
**purchase-summary
***summary-total
****price-total
****price-currency
*funding-mix
**payment-type
**amount
**ccStatement
*contact-information (contains hCard microformat)

This semantic HTML is the most complete and well-thought-out I've seen in this analysis. It even makes use of the fieldset element in forms, something I've never seen before.[[User:Lastorset|Lastorset]] 16:21, 25 Jul 2007 (PDT)

Microformats used:
*hCard (non-compliant due to missing formatted name): buyer contact info

==== Symantec ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Symantec-reminder-e-mail.html Symantec e-mail reminder]

*buyer name
*date
*payment method
*last 4 digits
*appears on statement as "DR *Symantec"
*items
**qty
**product name
**platform
**delivery method
**price
*subtotal
*grand total
*permalink

No relevant semantic HTML

=== Analysis ===

==== Analysis of Bills ====

==== Analysis of Receipts ====

== Existing Practices ==

Listed below is an overview of existing patterns and practices found in the wild for bill and receipt data.

===Summary of common patterns discovered===

===Other attempts to solve The Problem===
For paper receipts, [http://www.neatreceipts.com/ NeatReceipts Scanalizer] offers a heuristic-based solution.

== Proposal ==

== See Also ==
* [[receipt]]
* http://en.wikipedia.org/wiki/Receipt

receipt-examples

2007-08-16T21:39:56Z

Lastorset: /* Barnes&Noble */ POSH analysis

= Receipt =

Overview of Receipt exploratory discussion goes here...

== Authors ==

=== Contributors ===
Rob Manson

== Real-World Examples ==

=== Bill / Invoice ===

Bills or Invoices are "yet to be paid" items.

Question: Perhaps these examples (yet to be provided) should be moved to a separate page as Bill/Invoice is quite different from Receipt.

: With [[hResume]], I've [[hresume-brainstorming|suggested]] that the subtle difference between actively seeking work and just presenting your resume be a case of including [[hlisting]] markup.
: With bills vs invoices, it may turn out that the content found within would be identical, and it might just be a case of putting in a class flag to indicate whether the presented document has been paid for or not.
: [[User:SignpostMarv|SignpostMarv]] 12:55, 21 Jul 2007 (PDT)

=== Receipts ===

Receipts are post-purchase items.

==== Amazon ====
* [http://mobileonlinebusiness.com.au/uf/receipt/Amazon.com-Vieworder-anon.htm Example]
* contains:
**<del>email address</del> (could not find in examples)
**date of order
**order id
**shipments
***shipping estimate
***delivery estimate
***shipping address
***shipping speed
***shipping preference (item grouping)
***items
****quantity
****seller
****price
****item information
**payment
***card type
***last 5 digits
***expiration date
***billing address
***subtotal
***shipping and handling price
***total before tax
***tax
***grand total
**<del>discount price</del> (could not find in examples)
* Little semantic HTML of interest, except an anchor with id "payment-info"

==== Skype ====

===== Skype Phone =====
*[[receipt-example-skype-phone|example source code]]
*[http://mobileonlinebusiness.com.au/uf/receipt/Skype-order-history.html Skype order history]

* Name
* Shipping Address
* Order blurb "Confirmation of incoming order"
** date in dd/mm/yyyy format
* Order number in nnnn-nnnnnnn-nnn format
* Reference (was blank in example, presumed to appear on bank statement for this transaction)
* Order resume
** Quantity
** Description
** Price
** Total
** VAT (tax) %
* Payment
** subtotal
** shipping cost
** VAT (percentage)
** grand total
** total (VAT excluded)
** VAT (amount)
* Notification of chosen payment method blurb: "Your payment method is: Credit card"
* Legal blurb

Semantic HTML:
* Order resume class="order-listing"
* Each item class="row"
* All totals rows class="totals-row" except grand total class="grandtotal-row"

==== Internet banking transaction receipts ====
===== Example 1 =====
<pre><nowiki>
receipt number
date
time
receipt type (e.g. TRANSFER BETWEEN MY ACCOUNTS)
transfer from
transfer to
amount
description
information/comment
</nowiki></pre>

==== Digital product purchase receipts ====
===== Example 1 : Software =====
<pre><nowiki>
receipt title/type
order/receipt number
seller's details
sold by (hCard candidate)
org
adr
tax number (VAT in this example)
tax id (Federal Tax ID)
buyer's details
buyer (hCard candidate)
name
org
street-address
locality
region
postal-code
country-name
tel
email
credit card number (PAN truncated - with type)
item list
product code
name
comments
price
delivery method
quantity
total in selected currency
total in sellers currency
total (sum of item list totals)
processing fee
grand total (final amount charged)
information (caveats and tax info)
permalink
</nowiki></pre>

===== Example 2 : SSL certificate =====
<pre><nowiki>
receipt title/type
seller (hCard candidate)
org
street-address
locality
region
postal-code
purchase information
order id
product name
domain name
validity period
number of licenses
card number (PAN truncated)
amount (with selected currency)
</nowiki></pre>

==== Physical product purchase receipts ====
===== Example 1 : Computer hardware =====
<pre><nowiki>
receipt title/type
seller's name (hCard candidate)
seller's URL (hCard candidate)
invoice id
org govt reference (ABN - Australian Business Number)
date
seller details (hCard candidate)
street-address
locality
region
postal-code
buyer (hCard candidate)
fn
billing address
street-address
locality
region
postal-code
delivery address
street-address
locality
region
postal-code
phone
item list
item
description
amount
quantity
product url
total
delivery cost
total excluding tax
tax (GST - Goods and Service Tax)
total including tax
</nowiki></pre>

==== Service purchase receipts ====
===== Example 1 : Online subscription =====
<pre><nowiki>
seller's details (hCard candidate)
org
street-address
locality
region
postal-code
country-name
buyer's details (hCard candidate)
fn
street-address
locality
region
postal-code
phone
date
receipt id
item list
product description
quantity
rate (per unit)
price
sub total
amount paid
balance due
information
transaction id
</nowiki></pre>

===== Example 2 : Co-location =====
<pre><nowiki>
receipt title/type
sellers details (hCard candidate)
org
url
phone
message
receipt number
date
amount
information
</nowiki></pre>

==== A1Books ====
[http://mobileonlinebusiness.com.au/uf/receipt/A1Books-Sales-Order-anon.htm Example]

*vendor
**name
**fax
*date
*order number
*shipping address
*billing address
*items
**description
**list price
**sale price
**quantity
**amount
*subtotal
*shipping
*total
**quantity
**amount
*account information
**phone
**e-mail
*credit card last four digits

No semantic HTML.

==== Barnes&Noble ====
[http://mobileonlinebusiness.com.au/uf/receipt/BarnesAndNoble.com-receipt.anon.tidied.htm Example]

*shipping address
*billing address
*payment
**last 4 digits
**exp. date
**charge
*savings on shipping
*order no.
*delivery option
*items
**description: title, author, ISBN, price
**qty
**gift options: wrap, message
**total price
*shipment subtotal
*shipping cost
*tax
*shipment total (seems to account for orders requiring multiple shipments)
*order total

Semantic HTML:
*receiptOrderNumbers
*receiptOrderPlacedOn
*orderInformation
**shippingAddress
**billingAddress
**paymentInformation
*shippingSelections
*showProducts
**reviewTable
***qtyValuePosition
***reviewGiftOptions
*reviewTotalsDisplay
**reviewTotalsSummary
**reviewTotalsNote
**reviewTotalsBreakdown
*reviewTotalsSummary
**reviewGrandTotal
*reviewCreditCardCharged
*review

The semantic class names found are a good start, although the "review" part appears to be context-specific (reviewing an order). Additionally, the implied hierarchy in names such as "reviewTotalsSummary" and "receiptOrderPlacedOn" is probably unnecessary for our purposes.

==== Facebook ====
[http://mobileonlinebusiness.com.au/uf/receipt/Facebook-gift-receipt.html Example]

*purchase total
*items (informal description of two items, including quantity)
*recipient name
*order id
*billed-to name

No relevant semantic HTML.

==== Google Checkout ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Google-Checkout-e-mail-receipt.tidied.html Example email receipt]
*[http://mobileonlinebusiness.com.au/uf/receipt/Google-Checkout-Order-Receipt_DVD-Empire.tidied.htm Example web receipt]

*vendor address
*shipping address
*date
*order id
*items
**shipping status ("Not yet shipped", etc.)
**qty.
**description
**price
*shipping cost
*tax
*total
*order history (placed, received, charged, shipped) (web receipt only)
*payment info (web receipt only)
**card type
**last 4 digits
**exp. date
**cardholder address
*permalink

Semantic HTML:
*taxRow
**taxIdentifier
**taxAmount
*totalAmount

==== iTunes ====
*[http://mobileonlinebusiness.com.au/uf/receipt/iTunes-receipt-e-mail.html iTunes e-mail receipt]

*billing address
*order no.
*receipt date
*order total
*card
**type
**last 4 digits
*item
**item no.
**description (including link to write a review)
**unit price
*subtotal
*tax

No relevant semantic HTML.

==== Longs/FujiFilm ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Longs-Fujifilm-photo-receipt.html Longs/Fujifilm e-mail receipt]

*order no.
*payment info
**method (COD, credit card, etc.)
*customer address
*pickup address
*items
**name
**qty.
**description
**price
**line item subtotal
*order items total
*tax
*order total

Semantic HTML:
*payment-heading

==== Mobivox/PayPal ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Mobivox-PayPal.htm Mobivox/PayPal receipt]
*[http://mobileonlinebusiness.com.au/uf/receipt/Mobivox-PayPal-printable.htm Mobivox/PayPal printable receipt]

*seller address
*receipt id
*date of order
*items
**description
**item option (not quite sure what this is for)
**unit price
**qty
**total
*subtotal
*tax
*total amount
*payment info
**method
**last 4 digits
**charge
**appears on bill/statement as "MOBIVOXCORP"
*buyer contact

Relevant semantic HTML:
*order-summary
**cart
***(unnamed tr)
****item-name
****item-total
****item-option (not quite sure what this is for)
**subtotal
**totals-value
**totals-currency
**purchase-summary
***summary-total
****price-total
****price-currency
*funding-mix
**payment-type
**amount
**ccStatement
*contact-information (contains hCard microformat)

This semantic HTML is the most complete and well-thought-out I've seen in this analysis. It even makes use of the fieldset element in forms, something I've never seen before.[[User:Lastorset|Lastorset]] 16:21, 25 Jul 2007 (PDT)

Microformats used:
*hCard (non-compliant due to missing formatted name): buyer contact info

==== Symantec ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Symantec-reminder-e-mail.html Symantec e-mail reminder]

*buyer name
*date
*payment method
*last 4 digits
*appears on statement as "DR *Symantec"
*items
**qty
**product name
**platform
**delivery method
**price
*subtotal
*grand total
*permalink

No relevant semantic HTML

=== Analysis ===

==== Analysis of Bills ====

==== Analysis of Receipts ====

== Existing Practices ==

Listed below is an overview of existing patterns and practices found in the wild for bill and receipt data.

===Summary of common patterns discovered===

===Other attempts to solve The Problem===
For paper receipts, [http://www.neatreceipts.com/ NeatReceipts Scanalizer] offers a heuristic-based solution.

== Proposal ==

== See Also ==
* [[receipt]]
* http://en.wikipedia.org/wiki/Receipt

testimonials

2007-08-10T21:55:23Z

Lastorset: /* Custom application format */ fix accidental formatting

= Testimonals =

These are stories from the [http://microformats.org/discuss/mail/microformats-discuss micformats-discuss mailing list], where users characterize why exactly they find microformats so useful and compelling.

== [http://www.lizcoworldwide.com/wordpress/index.php?p=92 Liz Dunn] ==
I wrote a little essay on my personal blog about why I like, nay, LOVE, microformats. The goal of this essay was to get my friends, who aren't super extra into web formats, excited about the possibilities of microformats. I'm not sure it worked, since one friend commented that she didn't think she was the audience for my blog anymore. But I'm not going to stop writing about microformats!

== [http://microformats.org/discuss/mail/microformats-discuss/2005-October/001253.html Kevin Lawver] ==

My personal interest in microformats stems from my general laziness and love of conformity. I don't want to have to think about how to mark something up all the time. I think Microformats can go a long way towards standardizing how we mark up particular pieces of data... I work at a company that has a huge collection of developers spread all over the world. If I can tell all of them, "Hey, you should mark a review or search result or list of blog posts this way, and heres' the documentation," they'll be more likely to do that, and we'll have an easier time maintaining and "discovering" that content.

== [http://microformats.org/discuss/mail/microformats-discuss/2005-October/001181.html Ernest Prabhakar] ==

=== Organization web page ===

I'm responsible for the website for an informal group at work. The
HTML I inherited was a horrible mess, and painful to maintain. I
realized that it was pretty much just a list of events, people, and
resources. So, just to avoid having to think about HTML design, I
turned the whole thing into a bunch of XOXO, hCards, and hEvents.
Then, in order to make it look the way I wanted, I just added (or
often, stole:-) appropriate style declarations.

Could I have done this without microformats? Actually, no. ''You''
might, but '''I''' couldn't. Microformat was the crutch to help me think
intelligently about CSS. As a bonus, I can now use all these funky
tools to extract vCards -- and show the entire site as a
presentation. Cool!

=== Custom application format ===

One of my side projects is working on a program to display lyrics for
sing-a-longs (i.e., church worship services). I was experimenting
with a bunch of different XML schemas, but a) I wasn't sure I had it
right, and b) there was no way I could imagine getting a lot of
people to adopt it.

Then I discovered [http://www.meyerweb.com/eric/tools/s5 S5].
I suddenly realized that XOXO was the perfect format for encoding lyrics (stanzas, lines, etc.).
It is so obviously *right* that it is trivial to evangelize, rather
than arguing over every last tag. It is flexible, so people can add
their own metadata if needed, and socialize them informally rather
than having to push them through a central standard (which I'd have
to maintain, ugh). It is also non-intimidating, so people who know
HTML but not XML (believe me, there's a lot of them) are comfortable
adopting it.

Not bad. But wait, there's more! This also means:
# There's a trivial way to view every file (browser), even without my app
# Design can be done using CSS, meanings trivial to customize -- I don't need to provide a tool
# I can reuse the existing HTML viewing tools on my platform

At this point, I literally cannot imagine tackling any web site or
application format problem withOUT leveraging existing
microformats. It is the shortest route to success for the kinds of
things *I* care about. Where getting an 80% solution out - now- is
the most important thing. If you slice the 80/20 correctly, it is
actually only the top 5% of customers who ever actually run into the
tough edge cases. The long tail rarely cares -- certainly not enough
to pay the added cost.

Its kinda like optimizing source code. Its better to write it first
then optimize the hotspots, than try to pre-optimized what you *think*
the problems will be.

receipt-examples

2007-07-25T23:48:32Z

Lastorset: /* Existing Practices */ OCR for the paper version of the problem

= Receipt =

Overview of Receipt exploratory discussion goes here...

== Authors ==

=== Contributors ===
Rob Manson

== Real-World Examples ==

=== Bill / Invoice ===

Bills or Invoices are "yet to be paid" items.

Question: Perhaps these examples (yet to be provided) should be moved to a separate page as Bill/Invoice is quite different from Receipt.

: With [[hResume]], I've [[hresume-brainstorming|suggested]] that the subtle difference between actively seeking work and just presenting your resume be a case of including [[hlisting]] markup.
: With bills vs invoices, it may turn out that the content found within would be identical, and it might just be a case of putting in a class flag to indicate whether the presented document has been paid for or not.
: [[User:SignpostMarv|SignpostMarv]] 12:55, 21 Jul 2007 (PDT)

=== Receipts ===

Receipts are post-purchase items.

==== Amazon ====
* [http://mobileonlinebusiness.com.au/uf/receipt/Amazon.com-Vieworder-anon.htm Example]
* contains:
**<del>email address</del> (could not find in examples)
**date of order
**order id
**shipments
***shipping estimate
***delivery estimate
***shipping address
***shipping speed
***shipping preference (item grouping)
***items
****quantity
****seller
****price
****item information
**payment
***card type
***last 5 digits
***expiration date
***billing address
***subtotal
***shipping and handling price
***total before tax
***tax
***grand total
**<del>discount price</del> (could not find in examples)
* Little semantic HTML of interest, except an anchor with id "payment-info"

==== Skype ====

===== Skype Phone =====
*[[receipt-example-skype-phone|example source code]]
*[http://mobileonlinebusiness.com.au/uf/receipt/Skype-order-history.html Skype order history]

* Name
* Shipping Address
* Order blurb "Confirmation of incoming order"
** date in dd/mm/yyyy format
* Order number in nnnn-nnnnnnn-nnn format
* Reference (was blank in example, presumed to appear on bank statement for this transaction)
* Order resume
** Quantity
** Description
** Price
** Total
** VAT (tax) %
* Payment
** subtotal
** shipping cost
** VAT (percentage)
** grand total
** total (VAT excluded)
** VAT (amount)
* Notification of chosen payment method blurb: "Your payment method is: Credit card"
* Legal blurb

Semantic HTML:
* Order resume class="order-listing"
* Each item class="row"
* All totals rows class="totals-row" except grand total class="grandtotal-row"

==== Internet banking transaction receipts ====
===== Example 1 =====
<pre><nowiki>
receipt number
date
time
receipt type (e.g. TRANSFER BETWEEN MY ACCOUNTS)
transfer from
transfer to
amount
description
information/comment
</nowiki></pre>

==== Digital product purchase receipts ====
===== Example 1 : Software =====
<pre><nowiki>
receipt title/type
order/receipt number
seller's details
sold by (hCard candidate)
org
adr
tax number (VAT in this example)
tax id (Federal Tax ID)
buyer's details
buyer (hCard candidate)
name
org
street-address
locality
region
postal-code
country-name
tel
email
credit card number (PAN truncated - with type)
item list
product code
name
comments
price
delivery method
quantity
total in selected currency
total in sellers currency
total (sum of item list totals)
processing fee
grand total (final amount charged)
information (caveats and tax info)
permalink
</nowiki></pre>

===== Example 2 : SSL certificate =====
<pre><nowiki>
receipt title/type
seller (hCard candidate)
org
street-address
locality
region
postal-code
purchase information
order id
product name
domain name
validity period
number of licenses
card number (PAN truncated)
amount (with selected currency)
</nowiki></pre>

==== Physical product purchase receipts ====
===== Example 1 : Computer hardware =====
<pre><nowiki>
receipt title/type
seller's name (hCard candidate)
seller's URL (hCard candidate)
invoice id
org govt reference (ABN - Australian Business Number)
date
seller details (hCard candidate)
street-address
locality
region
postal-code
buyer (hCard candidate)
fn
billing address
street-address
locality
region
postal-code
delivery address
street-address
locality
region
postal-code
phone
item list
item
description
amount
quantity
product url
total
delivery cost
total excluding tax
tax (GST - Goods and Service Tax)
total including tax
</nowiki></pre>

==== Service purchase receipts ====
===== Example 1 : Online subscription =====
<pre><nowiki>
seller's details (hCard candidate)
org
street-address
locality
region
postal-code
country-name
buyer's details (hCard candidate)
fn
street-address
locality
region
postal-code
phone
date
receipt id
item list
product description
quantity
rate (per unit)
price
sub total
amount paid
balance due
information
transaction id
</nowiki></pre>

===== Example 2 : Co-location =====
<pre><nowiki>
receipt title/type
sellers details (hCard candidate)
org
url
phone
message
receipt number
date
amount
information
</nowiki></pre>

==== A1Books ====
[http://mobileonlinebusiness.com.au/uf/receipt/A1Books-Sales-Order-anon.htm Example]

*vendor
**name
**fax
*date
*order number
*shipping address
*billing address
*items
**description
**list price
**sale price
**quantity
**amount
*subtotal
*shipping
*total
**quantity
**amount
*account information
**phone
**e-mail
*credit card last four digits

No semantic HTML.

==== Barnes&Noble ====
[http://mobileonlinebusiness.com.au/uf/receipt/BarnesAndNoble.com-receipt.anon.tidied.htm Example]

*shipping address
*billing address
*payment
**last 4 digits
**exp. date
**charge
*savings on shipping
*order no.
*delivery option
*items
**description: title, author, ISBN, price
**qty
**gift options: wrap, message
**total price
*shipment subtotal
*shipping cost
*tax
*shipment total (seems to account for orders requiring multiple shipments)
*order total

Semantic HTML:
*receiptOrderNumbers
*receiptOrderPlacedOn
*orderInformation
**shippingAddress
**billingAddress
**paymentInformation
*shippingSelections
*showProducts
**reviewTable
***qtyValuePosition
***reviewGiftOptions
*reviewTotalsDisplay
**reviewTotalsSummary
**reviewTotalsNote
**reviewTotalsBreakdown
*reviewTotalsSummary
**reviewGrandTotal
*reviewCreditCardCharged
*review

==== Facebook ====
[http://mobileonlinebusiness.com.au/uf/receipt/Facebook-gift-receipt.html Example]

*purchase total
*items (informal description of two items, including quantity)
*recipient name
*order id
*billed-to name

No relevant semantic HTML.

==== Google Checkout ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Google-Checkout-e-mail-receipt.tidied.html Example email receipt]
*[http://mobileonlinebusiness.com.au/uf/receipt/Google-Checkout-Order-Receipt_DVD-Empire.tidied.htm Example web receipt]

*vendor address
*shipping address
*date
*order id
*items
**shipping status ("Not yet shipped", etc.)
**qty.
**description
**price
*shipping cost
*tax
*total
*order history (placed, received, charged, shipped) (web receipt only)
*payment info (web receipt only)
**card type
**last 4 digits
**exp. date
**cardholder address
*permalink

Semantic HTML:
*taxRow
**taxIdentifier
**taxAmount
*totalAmount

==== iTunes ====
*[http://mobileonlinebusiness.com.au/uf/receipt/iTunes-receipt-e-mail.html iTunes e-mail receipt]

*billing address
*order no.
*receipt date
*order total
*card
**type
**last 4 digits
*item
**item no.
**description (including link to write a review)
**unit price
*subtotal
*tax

No relevant semantic HTML.

==== Longs/FujiFilm ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Longs-Fujifilm-photo-receipt.html Longs/Fujifilm e-mail receipt]

*order no.
*payment info
**method (COD, credit card, etc.)
*customer address
*pickup address
*items
**name
**qty.
**description
**price
**line item subtotal
*order items total
*tax
*order total

Semantic HTML:
*payment-heading

==== Mobivox/PayPal ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Mobivox-PayPal.htm Mobivox/PayPal receipt]
*[http://mobileonlinebusiness.com.au/uf/receipt/Mobivox-PayPal-printable.htm Mobivox/PayPal printable receipt]

*seller address
*receipt id
*date of order
*items
**description
**item option (not quite sure what this is for)
**unit price
**qty
**total
*subtotal
*tax
*total amount
*payment info
**method
**last 4 digits
**charge
**appears on bill/statement as "MOBIVOXCORP"
*buyer contact

Relevant semantic HTML:
*order-summary
**cart
***(unnamed tr)
****item-name
****item-total
****item-option (not quite sure what this is for)
**subtotal
**totals-value
**totals-currency
**purchase-summary
***summary-total
****price-total
****price-currency
*funding-mix
**payment-type
**amount
**ccStatement
*contact-information (contains hCard microformat)

This semantic HTML is the most complete and well-thought-out I've seen in this analysis. It even makes use of the fieldset element in forms, something I've never seen before.[[User:Lastorset|Lastorset]] 16:21, 25 Jul 2007 (PDT)

Microformats used:
*hCard (non-compliant due to missing formatted name): buyer contact info

==== Symantec ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Symantec-reminder-e-mail.html Symantec e-mail reminder]

*buyer name
*date
*payment method
*last 4 digits
*appears on statement as "DR *Symantec"
*items
**qty
**product name
**platform
**delivery method
**price
*subtotal
*grand total
*permalink

No relevant semantic HTML

=== Analysis ===

==== Analysis of Bills ====

==== Analysis of Receipts ====

== Existing Practices ==

Listed below is an overview of existing patterns and practices found in the wild for bill and receipt data.

===Summary of common patterns discovered===

===Other attempts to solve The Problem===
For paper receipts, [http://www.neatreceipts.com/ NeatReceipts Scanalizer] offers a heuristic-based solution.

== Proposal ==

== See Also ==
* [[receipt]]
* http://en.wikipedia.org/wiki/Receipt

receipt-examples

2007-07-25T23:26:22Z

Lastorset: /* Google Checkout */ forgot permalink

= Receipt =

Overview of Receipt exploratory discussion goes here...

== Authors ==

=== Contributors ===
Rob Manson

== Real-World Examples ==

=== Bill / Invoice ===

Bills or Invoices are "yet to be paid" items.

Question: Perhaps these examples (yet to be provided) should be moved to a separate page as Bill/Invoice is quite different from Receipt.

: With [[hResume]], I've [[hresume-brainstorming|suggested]] that the subtle difference between actively seeking work and just presenting your resume be a case of including [[hlisting]] markup.
: With bills vs invoices, it may turn out that the content found within would be identical, and it might just be a case of putting in a class flag to indicate whether the presented document has been paid for or not.
: [[User:SignpostMarv|SignpostMarv]] 12:55, 21 Jul 2007 (PDT)

=== Receipts ===

Receipts are post-purchase items.

==== Amazon ====
* [http://mobileonlinebusiness.com.au/uf/receipt/Amazon.com-Vieworder-anon.htm Example]
* contains:
**<del>email address</del> (could not find in examples)
**date of order
**order id
**shipments
***shipping estimate
***delivery estimate
***shipping address
***shipping speed
***shipping preference (item grouping)
***items
****quantity
****seller
****price
****item information
**payment
***card type
***last 5 digits
***expiration date
***billing address
***subtotal
***shipping and handling price
***total before tax
***tax
***grand total
**<del>discount price</del> (could not find in examples)
* Little semantic HTML of interest, except an anchor with id "payment-info"

==== Skype ====

===== Skype Phone =====
*[[receipt-example-skype-phone|example source code]]
*[http://mobileonlinebusiness.com.au/uf/receipt/Skype-order-history.html Skype order history]

* Name
* Shipping Address
* Order blurb "Confirmation of incoming order"
** date in dd/mm/yyyy format
* Order number in nnnn-nnnnnnn-nnn format
* Reference (was blank in example, presumed to appear on bank statement for this transaction)
* Order resume
** Quantity
** Description
** Price
** Total
** VAT (tax) %
* Payment
** subtotal
** shipping cost
** VAT (percentage)
** grand total
** total (VAT excluded)
** VAT (amount)
* Notification of chosen payment method blurb: "Your payment method is: Credit card"
* Legal blurb

Semantic HTML:
* Order resume class="order-listing"
* Each item class="row"
* All totals rows class="totals-row" except grand total class="grandtotal-row"

==== Internet banking transaction receipts ====
===== Example 1 =====
<pre><nowiki>
receipt number
date
time
receipt type (e.g. TRANSFER BETWEEN MY ACCOUNTS)
transfer from
transfer to
amount
description
information/comment
</nowiki></pre>

==== Digital product purchase receipts ====
===== Example 1 : Software =====
<pre><nowiki>
receipt title/type
order/receipt number
seller's details
sold by (hCard candidate)
org
adr
tax number (VAT in this example)
tax id (Federal Tax ID)
buyer's details
buyer (hCard candidate)
name
org
street-address
locality
region
postal-code
country-name
tel
email
credit card number (PAN truncated - with type)
item list
product code
name
comments
price
delivery method
quantity
total in selected currency
total in sellers currency
total (sum of item list totals)
processing fee
grand total (final amount charged)
information (caveats and tax info)
permalink
</nowiki></pre>

===== Example 2 : SSL certificate =====
<pre><nowiki>
receipt title/type
seller (hCard candidate)
org
street-address
locality
region
postal-code
purchase information
order id
product name
domain name
validity period
number of licenses
card number (PAN truncated)
amount (with selected currency)
</nowiki></pre>

==== Physical product purchase receipts ====
===== Example 1 : Computer hardware =====
<pre><nowiki>
receipt title/type
seller's name (hCard candidate)
seller's URL (hCard candidate)
invoice id
org govt reference (ABN - Australian Business Number)
date
seller details (hCard candidate)
street-address
locality
region
postal-code
buyer (hCard candidate)
fn
billing address
street-address
locality
region
postal-code
delivery address
street-address
locality
region
postal-code
phone
item list
item
description
amount
quantity
product url
total
delivery cost
total excluding tax
tax (GST - Goods and Service Tax)
total including tax
</nowiki></pre>

==== Service purchase receipts ====
===== Example 1 : Online subscription =====
<pre><nowiki>
seller's details (hCard candidate)
org
street-address
locality
region
postal-code
country-name
buyer's details (hCard candidate)
fn
street-address
locality
region
postal-code
phone
date
receipt id
item list
product description
quantity
rate (per unit)
price
sub total
amount paid
balance due
information
transaction id
</nowiki></pre>

===== Example 2 : Co-location =====
<pre><nowiki>
receipt title/type
sellers details (hCard candidate)
org
url
phone
message
receipt number
date
amount
information
</nowiki></pre>

==== A1Books ====
[http://mobileonlinebusiness.com.au/uf/receipt/A1Books-Sales-Order-anon.htm Example]

*vendor
**name
**fax
*date
*order number
*shipping address
*billing address
*items
**description
**list price
**sale price
**quantity
**amount
*subtotal
*shipping
*total
**quantity
**amount
*account information
**phone
**e-mail
*credit card last four digits

No semantic HTML.

==== Barnes&Noble ====
[http://mobileonlinebusiness.com.au/uf/receipt/BarnesAndNoble.com-receipt.anon.tidied.htm Example]

*shipping address
*billing address
*payment
**last 4 digits
**exp. date
**charge
*savings on shipping
*order no.
*delivery option
*items
**description: title, author, ISBN, price
**qty
**gift options: wrap, message
**total price
*shipment subtotal
*shipping cost
*tax
*shipment total (seems to account for orders requiring multiple shipments)
*order total

Semantic HTML:
*receiptOrderNumbers
*receiptOrderPlacedOn
*orderInformation
**shippingAddress
**billingAddress
**paymentInformation
*shippingSelections
*showProducts
**reviewTable
***qtyValuePosition
***reviewGiftOptions
*reviewTotalsDisplay
**reviewTotalsSummary
**reviewTotalsNote
**reviewTotalsBreakdown
*reviewTotalsSummary
**reviewGrandTotal
*reviewCreditCardCharged
*review

==== Facebook ====
[http://mobileonlinebusiness.com.au/uf/receipt/Facebook-gift-receipt.html Example]

*purchase total
*items (informal description of two items, including quantity)
*recipient name
*order id
*billed-to name

No relevant semantic HTML.

==== Google Checkout ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Google-Checkout-e-mail-receipt.tidied.html Example email receipt]
*[http://mobileonlinebusiness.com.au/uf/receipt/Google-Checkout-Order-Receipt_DVD-Empire.tidied.htm Example web receipt]

*vendor address
*shipping address
*date
*order id
*items
**shipping status ("Not yet shipped", etc.)
**qty.
**description
**price
*shipping cost
*tax
*total
*order history (placed, received, charged, shipped) (web receipt only)
*payment info (web receipt only)
**card type
**last 4 digits
**exp. date
**cardholder address
*permalink

Semantic HTML:
*taxRow
**taxIdentifier
**taxAmount
*totalAmount

==== iTunes ====
*[http://mobileonlinebusiness.com.au/uf/receipt/iTunes-receipt-e-mail.html iTunes e-mail receipt]

*billing address
*order no.
*receipt date
*order total
*card
**type
**last 4 digits
*item
**item no.
**description (including link to write a review)
**unit price
*subtotal
*tax

No relevant semantic HTML.

==== Longs/FujiFilm ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Longs-Fujifilm-photo-receipt.html Longs/Fujifilm e-mail receipt]

*order no.
*payment info
**method (COD, credit card, etc.)
*customer address
*pickup address
*items
**name
**qty.
**description
**price
**line item subtotal
*order items total
*tax
*order total

Semantic HTML:
*payment-heading

==== Mobivox/PayPal ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Mobivox-PayPal.htm Mobivox/PayPal receipt]
*[http://mobileonlinebusiness.com.au/uf/receipt/Mobivox-PayPal-printable.htm Mobivox/PayPal printable receipt]

*seller address
*receipt id
*date of order
*items
**description
**item option (not quite sure what this is for)
**unit price
**qty
**total
*subtotal
*tax
*total amount
*payment info
**method
**last 4 digits
**charge
**appears on bill/statement as "MOBIVOXCORP"
*buyer contact

Relevant semantic HTML:
*order-summary
**cart
***(unnamed tr)
****item-name
****item-total
****item-option (not quite sure what this is for)
**subtotal
**totals-value
**totals-currency
**purchase-summary
***summary-total
****price-total
****price-currency
*funding-mix
**payment-type
**amount
**ccStatement
*contact-information (contains hCard microformat)

This semantic HTML is the most complete and well-thought-out I've seen in this analysis. It even makes use of the fieldset element in forms, something I've never seen before.[[User:Lastorset|Lastorset]] 16:21, 25 Jul 2007 (PDT)

Microformats used:
*hCard (non-compliant due to missing formatted name): buyer contact info

==== Symantec ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Symantec-reminder-e-mail.html Symantec e-mail reminder]

*buyer name
*date
*payment method
*last 4 digits
*appears on statement as "DR *Symantec"
*items
**qty
**product name
**platform
**delivery method
**price
*subtotal
*grand total
*permalink

No relevant semantic HTML

=== Analysis ===

==== Analysis of Bills ====

==== Analysis of Receipts ====

== Existing Practices ==

Listed below is an overview of existing patterns and practices found in the wild for bill and receipt data.

===Summary of common patterns discovered===

===Other attempts to solve The Problem===

== Proposal ==

== See Also ==
* [[receipt]]
* http://en.wikipedia.org/wiki/Receipt

receipt-examples

2007-07-25T23:24:23Z

Lastorset: /* Symantec */ analysis

= Receipt =

Overview of Receipt exploratory discussion goes here...

== Authors ==

=== Contributors ===
Rob Manson

== Real-World Examples ==

=== Bill / Invoice ===

Bills or Invoices are "yet to be paid" items.

Question: Perhaps these examples (yet to be provided) should be moved to a separate page as Bill/Invoice is quite different from Receipt.

: With [[hResume]], I've [[hresume-brainstorming|suggested]] that the subtle difference between actively seeking work and just presenting your resume be a case of including [[hlisting]] markup.
: With bills vs invoices, it may turn out that the content found within would be identical, and it might just be a case of putting in a class flag to indicate whether the presented document has been paid for or not.
: [[User:SignpostMarv|SignpostMarv]] 12:55, 21 Jul 2007 (PDT)

=== Receipts ===

Receipts are post-purchase items.

==== Amazon ====
* [http://mobileonlinebusiness.com.au/uf/receipt/Amazon.com-Vieworder-anon.htm Example]
* contains:
**<del>email address</del> (could not find in examples)
**date of order
**order id
**shipments
***shipping estimate
***delivery estimate
***shipping address
***shipping speed
***shipping preference (item grouping)
***items
****quantity
****seller
****price
****item information
**payment
***card type
***last 5 digits
***expiration date
***billing address
***subtotal
***shipping and handling price
***total before tax
***tax
***grand total
**<del>discount price</del> (could not find in examples)
* Little semantic HTML of interest, except an anchor with id "payment-info"

==== Skype ====

===== Skype Phone =====
*[[receipt-example-skype-phone|example source code]]
*[http://mobileonlinebusiness.com.au/uf/receipt/Skype-order-history.html Skype order history]

* Name
* Shipping Address
* Order blurb "Confirmation of incoming order"
** date in dd/mm/yyyy format
* Order number in nnnn-nnnnnnn-nnn format
* Reference (was blank in example, presumed to appear on bank statement for this transaction)
* Order resume
** Quantity
** Description
** Price
** Total
** VAT (tax) %
* Payment
** subtotal
** shipping cost
** VAT (percentage)
** grand total
** total (VAT excluded)
** VAT (amount)
* Notification of chosen payment method blurb: "Your payment method is: Credit card"
* Legal blurb

Semantic HTML:
* Order resume class="order-listing"
* Each item class="row"
* All totals rows class="totals-row" except grand total class="grandtotal-row"

==== Internet banking transaction receipts ====
===== Example 1 =====
<pre><nowiki>
receipt number
date
time
receipt type (e.g. TRANSFER BETWEEN MY ACCOUNTS)
transfer from
transfer to
amount
description
information/comment
</nowiki></pre>

==== Digital product purchase receipts ====
===== Example 1 : Software =====
<pre><nowiki>
receipt title/type
order/receipt number
seller's details
sold by (hCard candidate)
org
adr
tax number (VAT in this example)
tax id (Federal Tax ID)
buyer's details
buyer (hCard candidate)
name
org
street-address
locality
region
postal-code
country-name
tel
email
credit card number (PAN truncated - with type)
item list
product code
name
comments
price
delivery method
quantity
total in selected currency
total in sellers currency
total (sum of item list totals)
processing fee
grand total (final amount charged)
information (caveats and tax info)
permalink
</nowiki></pre>

===== Example 2 : SSL certificate =====
<pre><nowiki>
receipt title/type
seller (hCard candidate)
org
street-address
locality
region
postal-code
purchase information
order id
product name
domain name
validity period
number of licenses
card number (PAN truncated)
amount (with selected currency)
</nowiki></pre>

==== Physical product purchase receipts ====
===== Example 1 : Computer hardware =====
<pre><nowiki>
receipt title/type
seller's name (hCard candidate)
seller's URL (hCard candidate)
invoice id
org govt reference (ABN - Australian Business Number)
date
seller details (hCard candidate)
street-address
locality
region
postal-code
buyer (hCard candidate)
fn
billing address
street-address
locality
region
postal-code
delivery address
street-address
locality
region
postal-code
phone
item list
item
description
amount
quantity
product url
total
delivery cost
total excluding tax
tax (GST - Goods and Service Tax)
total including tax
</nowiki></pre>

==== Service purchase receipts ====
===== Example 1 : Online subscription =====
<pre><nowiki>
seller's details (hCard candidate)
org
street-address
locality
region
postal-code
country-name
buyer's details (hCard candidate)
fn
street-address
locality
region
postal-code
phone
date
receipt id
item list
product description
quantity
rate (per unit)
price
sub total
amount paid
balance due
information
transaction id
</nowiki></pre>

===== Example 2 : Co-location =====
<pre><nowiki>
receipt title/type
sellers details (hCard candidate)
org
url
phone
message
receipt number
date
amount
information
</nowiki></pre>

==== A1Books ====
[http://mobileonlinebusiness.com.au/uf/receipt/A1Books-Sales-Order-anon.htm Example]

*vendor
**name
**fax
*date
*order number
*shipping address
*billing address
*items
**description
**list price
**sale price
**quantity
**amount
*subtotal
*shipping
*total
**quantity
**amount
*account information
**phone
**e-mail
*credit card last four digits

No semantic HTML.

==== Barnes&Noble ====
[http://mobileonlinebusiness.com.au/uf/receipt/BarnesAndNoble.com-receipt.anon.tidied.htm Example]

*shipping address
*billing address
*payment
**last 4 digits
**exp. date
**charge
*savings on shipping
*order no.
*delivery option
*items
**description: title, author, ISBN, price
**qty
**gift options: wrap, message
**total price
*shipment subtotal
*shipping cost
*tax
*shipment total (seems to account for orders requiring multiple shipments)
*order total

Semantic HTML:
*receiptOrderNumbers
*receiptOrderPlacedOn
*orderInformation
**shippingAddress
**billingAddress
**paymentInformation
*shippingSelections
*showProducts
**reviewTable
***qtyValuePosition
***reviewGiftOptions
*reviewTotalsDisplay
**reviewTotalsSummary
**reviewTotalsNote
**reviewTotalsBreakdown
*reviewTotalsSummary
**reviewGrandTotal
*reviewCreditCardCharged
*review

==== Facebook ====
[http://mobileonlinebusiness.com.au/uf/receipt/Facebook-gift-receipt.html Example]

*purchase total
*items (informal description of two items, including quantity)
*recipient name
*order id
*billed-to name

No relevant semantic HTML.

==== Google Checkout ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Google-Checkout-e-mail-receipt.tidied.html Example email receipt]
*[http://mobileonlinebusiness.com.au/uf/receipt/Google-Checkout-Order-Receipt_DVD-Empire.tidied.htm Example web receipt]

*vendor address
*shipping address
*date
*order id
*items
**shipping status ("Not yet shipped", etc.)
**qty.
**description
**price
*shipping cost
*tax
*total
*order history (placed, received, charged, shipped) (web receipt only)
*payment info (web receipt only)
**card type
**last 4 digits
**exp. date
**cardholder address

Semantic HTML:
*taxRow
**taxIdentifier
**taxAmount
*totalAmount

==== iTunes ====
*[http://mobileonlinebusiness.com.au/uf/receipt/iTunes-receipt-e-mail.html iTunes e-mail receipt]

*billing address
*order no.
*receipt date
*order total
*card
**type
**last 4 digits
*item
**item no.
**description (including link to write a review)
**unit price
*subtotal
*tax

No relevant semantic HTML.

==== Longs/FujiFilm ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Longs-Fujifilm-photo-receipt.html Longs/Fujifilm e-mail receipt]

*order no.
*payment info
**method (COD, credit card, etc.)
*customer address
*pickup address
*items
**name
**qty.
**description
**price
**line item subtotal
*order items total
*tax
*order total

Semantic HTML:
*payment-heading

==== Mobivox/PayPal ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Mobivox-PayPal.htm Mobivox/PayPal receipt]
*[http://mobileonlinebusiness.com.au/uf/receipt/Mobivox-PayPal-printable.htm Mobivox/PayPal printable receipt]

*seller address
*receipt id
*date of order
*items
**description
**item option (not quite sure what this is for)
**unit price
**qty
**total
*subtotal
*tax
*total amount
*payment info
**method
**last 4 digits
**charge
**appears on bill/statement as "MOBIVOXCORP"
*buyer contact

Relevant semantic HTML:
*order-summary
**cart
***(unnamed tr)
****item-name
****item-total
****item-option (not quite sure what this is for)
**subtotal
**totals-value
**totals-currency
**purchase-summary
***summary-total
****price-total
****price-currency
*funding-mix
**payment-type
**amount
**ccStatement
*contact-information (contains hCard microformat)

This semantic HTML is the most complete and well-thought-out I've seen in this analysis. It even makes use of the fieldset element in forms, something I've never seen before.[[User:Lastorset|Lastorset]] 16:21, 25 Jul 2007 (PDT)

Microformats used:
*hCard (non-compliant due to missing formatted name): buyer contact info

==== Symantec ====
*[http://mobileonlinebusiness.com.au/uf/receipt/Symantec-reminder-e-mail.html Symantec e-mail reminder]

*buyer name
*date
*payment method
*last 4 digits
*appears on statement as "DR *Symantec"
*items
**qty
**product name
**platform
**delivery method
**price
*subtotal
*grand total
*permalink

No relevant semantic HTML

=== Analysis ===

==== Analysis of Bills ====

==== Analysis of Receipts ====

== Existing Practices ==

Listed below is an overview of existing patterns and practices found in the wild for bill and receipt data.

===Summary of common patterns discovered===

===Other attempts to solve The Problem===

== Proposal ==

== See Also ==
* [[receipt]]
* http://en.wikipedia.org/wiki/Receipt

receipt-examples

2007-07-25T23:21:43Z

Lastorset: /* Mobivox/PayPal */ analysis

receipt-examples

2007-07-25T22:51:55Z

Lastorset: /* Google Checkout */ semantic HTML

receipt-examples

2007-07-25T22:50:34Z

Lastorset: /* Longs/FujiFilm */ analysis

receipt-examples

2007-07-25T22:39:54Z

Lastorset: /* iTunes */ added e-mail field

receipt-examples

2007-07-25T22:37:05Z

Lastorset: /* iTunes */ analysis

receipt-examples

2007-07-25T22:09:44Z

Lastorset: /* Google Checkout */ analysis

receipt-examples

2007-07-25T21:12:02Z

Lastorset: /* Facebook */ analysis

receipt-examples

2007-07-24T23:39:25Z

Lastorset: /* Barnes&Noble */ analysis

receipt-examples

2007-07-24T23:26:38Z

Lastorset: /* A1Books */ analysis

receipt-examples

2007-07-24T22:45:27Z

Lastorset: /* Receipts */ Expanded Skype analysis and added semantics

receipt-examples

2007-07-24T22:05:52Z

Lastorset: /* Receipts */ merged two skype sections; removed incorrect statement about PDFs