diff --git a/UseCases/ReimbursementRequest.mdwn b/UseCases/ReimbursementRequest.mdwn
index 6ba5ac838b7ddf820b4bc27775f5822ec389226e..adc81d1b477ea5793b3515071fbfa728a7384f5b 100644
--- a/UseCases/ReimbursementRequest.mdwn
+++ b/UseCases/ReimbursementRequest.mdwn
@@ -39,3 +39,12 @@ From traveler's/reimbursement-requester's view, they'll need:
   * Updates on the external web interface system about status when the
     expense is moving through the internal system at the organization. 
   * Automatic calculation of any per-diem allowances.
+
+## Reimbursement on Behalf Of
+
+A classic scenario that occurs for non-profits is an employee or a contractor
+buys an item that is actually for someone else.  For example, a volunteer
+needs a plane ticket to go to a conference, so an employee or someone else
+(the "Floater") who can "float" the expense makes the purchase.  The
+reimbursement request comes in from the Floater but the real person who
+received the item should be recorded.