If you were routing the document each time using the "moving it" above, it will move it into each folder path (thereby creating the path). But then when it goes to the next value in the list it move that entry to that folder. So if here's 4 things in the list the actual document is sitting in item #4. 

If you route a shortcut to the folder it puts a shortcut to the original document there. In cases where I build something like this I usually have a central spot I store these types of documents then put shortcuts pointing to those elsewhere.

A real world example of this might be an order process that involves a bill of lading. 

The orders might live inside a folder for all of the orders, or they might live in the customer's folder. A bill of lading however might be assigned to more than one order. 

So I might have something like this: 

/Orders
   /[year]
       /[## - Month]
 

/Customer
      /Orders
            /[Year]

/Shipping
      /Bills of Lading
          /[year]
               /[## - Month]


Obviously I'm missing some folders above but you can get the point.

So when an order comes in, it goes into the Orders folder, under the year and month by the order #. Most of the time this is a folder so it can also hold any paperwork that goes with it.  

Under the customer orders, I place a shortcut folder for each order under the appropriate year pointing at the folder under Orders. 

The BoL docs go under the bill of lading folder by year and month, and a shortcut to those go into the order folder. One BoL might have multiple orders on it, or just parts of one order. These shortcuts go to any order # that is on the BoL. These are usually named with a unique BoL number or something. 
 

Now everyone can find everything about a customer order in one place under the customers, but order fulfillment and shipping can find everything in a place that makes it easy for them since they are not as customer centric, they just case about fulfilling whatever is on those orders and BoL's.

BTW  -- as an extra bonus -- why the [## Month] name? I get this by formatting a token like so:

You click that little > symbol next to your destination. If you use a token (i.e. field) that is a date as part of your path, you can use the apply format to change the name.

So I use 'yyyy' as the format of the year to make 6/23/2016 into just '2016', and 'MM MMMM' to make 6/23/2016 into '06 June'.

This way the months are in numerical order!