Day 029 of Daily UI Challenge

What - Design an invoice
Why - An invoice should have the essentials like who is paying, who is being paid, services provided, and how they will be paid for services. I added the vital information of who is paying and who is being paid at the top then working down to the services provided 
ending the amount owed and options to being paid. 
The layout of this invoice has a nice information architecture as you learn who the invoice is for, what it is for and how it is being paid.