week-end report for week 33, 2012

Taking my shot at describing, capturing for future, further access, what I learned this week—whether I really understood it, or not.

week 33, 2012
scaffolding city, shot 36

[1] notes to self

Talking about money and numbers is often uncomfortable.

  • regardless of what they’re saying or how, what your client is saying is that they need help 
  • bookkeepers give their clients detailed information, and clients need time to process
  • communicate in a way that reduces the static between you and the client 
  • it’s business, but more so: it’s personal -- be transparent about the work you’re doing: it’s ultimately not your work, it’s theirs

[2] There isn’t one right way to report. 

You’ll need different tracking for different purposes. And, at the beginning, when you’re starting out, or starting a project, you won’t necessarily see what you’re going to need (or want) later on.


Set it up at the smallest, most granular level: uniformly, consistently enter data—comprehensively: leave nothing out.


When you engage a company to sell your tickets, or gift certificates, or to receive your donations online, include the fees they take in your reporting. 

On the income side, your data is about your company and its interactions with your customers. So, if your customer is paying for a$100 something then that’s the income that goes on your books. 

On the expense side, the fees you pay the service company, they also go on your books, as expenses (probably in Cost of Goods Sold). 

The difference between the two is your profit — which is probably of most interest to you — but it’s not the whole story. Entering both the income and expense tells the whole story.

Which is what you want your reporting to do, to tell your business’ story. Completely.

[3] We’re saving/storing a LOT of paper.


scaffolding city shot 36

scaffolding city shot 36