receipt-examples

(Difference between revisions)

Jump to: navigation, search
m (Analysis of Receipts: subheadings)
Current revision (13:02, 16 January 2008) (view source)
(Other examples)
 
(10 intermediate revisions not shown.)
Line 1: Line 1:
-
= Receipt =
+
= Receipt examples =
-
 
+
-
Overview of Receipt exploratory discussion goes here...
+
-
 
+
-
== Authors ==
+
=== Contributors ===
=== Contributors ===
-
Rob Manson
+
*Rob Manson
 +
*Leif Arne Storset
== Real-World Examples ==
== 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.
 +
* Appears to apply to the USA only. [[User:AndyMabbett|Andy Mabbett]] 13:22, 31 Aug 2007 (PDT)
=== Bill / Invoice ===
=== Bill / Invoice ===
Line 16: Line 15:
Question: Perhaps these examples (yet to be provided) should be moved to a separate page as Bill/Invoice is quite different from Receipt.
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 [[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.
: 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)
: [[User:SignpostMarv|SignpostMarv]] 12:55, 21 Jul 2007 (PDT)
Line 375: Line 374:
*total
*total
*order history (placed, received, charged, shipped) (web receipt only)
*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)
*payment info (web receipt only)
**card type
**card type
Line 393: Line 393:
*E-mail receipt has permalink.
*E-mail receipt has permalink.
*Order history (date placed, received, charged, shipped).
*Order history (date placed, received, charged, shipped).
 +
*Displayed credit-card statement reference only after card was charged.
==== iTunes ====
==== iTunes ====
Line 525: Line 526:
=== Analysis of Receipts ===
=== 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:
 +
 +
<!-- Update the following list when analysis on new items is performed. -->
 +
*[[#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====
====Addresses====
Line 600: Line 616:
**charged
**charged
**shipped
**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 ==
== Existing Practices ==
Line 609: Line 642:
===Other attempts to solve The Problem===
===Other attempts to solve The Problem===
For paper receipts, [http://www.neatreceipts.com/ NeatReceipts Scanalizer] offers a heuristic-based solution.
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 ==
== Proposal ==
 +
 +
==Other examples==
 +
 +
*[[receipt-example-amazon]]
 +
*[[receipt-example-thinkgeek]]
 +
*[[receipt-example-thinkgeek-2]]
 +
*[[receipt-example-thinkgeek-3]]
== See Also ==
== See Also ==
 +
 +
* [[currency]]
* [[receipt]]
* [[receipt]]
* http://en.wikipedia.org/wiki/Receipt
* http://en.wikipedia.org/wiki/Receipt

Current revision

Contents

Receipt examples

Contributors

Real-World Examples

InternetRetailer's 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 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.
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?
  • <div class="hreceipt unpaid"/"hreceipt paid">...
  • <div class="hreceipt" title="paid">...</div>
Lastorset 14:55, 16 Aug 2007 (PDT)

Receipts

Receipts are post-purchase items.

Amazon

Notes:

Skype

Skype Phone

Semantic HTML:

Notes:

Internet banking transaction receipts

Example 1
receipt number
date
time
receipt type (e.g. TRANSFER BETWEEN MY ACCOUNTS)
  transfer from
  transfer to
amount
description
information/comment

Digital product purchase receipts

Example 1 : Software
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
Example 2 : SSL certificate
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)

Physical product purchase receipts

Example 1 : Computer hardware
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

Service purchase receipts

Example 1 : Online subscription
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
Example 2 : Co-location
receipt title/type
sellers details (hCard candidate)
  org
  url
  phone
message
receipt number
date
amount
information

A1Books

Example

No semantic HTML.

Notes:

Barnes&Noble

Example

Semantic HTML:

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:

Facebook

Example

No relevant semantic HTML.

Notes:

Google Checkout

Semantic HTML:

Notes:

iTunes

No relevant semantic HTML.

Notes:

Longs/FujiFilm

Semantic HTML:

Notes:

Mobivox/PayPal

Relevant semantic HTML:

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.Lastorset 16:21, 25 Jul 2007 (PDT)

Microformats used:

Notes:

Symantec

No relevant semantic HTML

Notes:

Analysis

Analysis of Bills

Analysis of Receipts

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

The analysis was performed on the following samples:

Addresses

All receipts have hCard candidates (i. e. name and/or address) of at least one of these types:

Shipping

These vendors supported multiple shipments:

These displayed shipping method/speed:

These displayed gift choices:

For most vendors, each item had the following information:

Google Checkout additionally provided shipping status.

Payment information

Most vendors displayed:

Some also displayed

Totals

Most displayed:

Some also displayed:

Marketplace

Most receipt formats are for one seller only. The following support different sellers:

Other properties

Almost all receipts had

Other interesting items:

Conclusion

Central 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:

The following elements are more rarely seen:

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, NeatReceipts Scanalizer offers a heuristic-based solution.

Open Financial Exchange

Proposal

Other examples

See Also

receipt-examples was last modified: Wednesday, January 16th, 2008

Views