catch up on books about finances HOT 23 OPEN

If feasible, I prefer to tackle 2017-01 first, hopefully keep book-keeping in future months, and going backwards when time allows.

from finances.

Think I should start working on #2 once gratipay/gratipay.com#4128 is merged since is working on the present month.

from finances.

@kaguillera and I are thinking that we should do a review/audit after each year, rather than waiting until we're totally caught up and reviewing four years at once.

from finances.

to: CPA

Thanks for putting us on the right track this morning, Peter. Good to be able to proceed with confidence. For the record, here are our meeting notes. We may have a question or two as we implement our plan, I'll follow up as necessary.

One immediate question: Kwesi and I were thinking we should review or audit a year at a time rather than waiting to audit all four years of backlog at once. Does that sound right to you?

from finances.

from finances.

Are we talking about a CPA review/audit per year? If so, I would rather you save on the charges if not necessary. Any third party will inquire only for most recent audit/review as opposed to historical. Unless you must do this to satisfy a grant or other need, then let’s discuss having to do this.

Thanks for the recommendation. We have two main goals here:

1. To assure ourselves that we haven't mismanaged our escrow.
2. To demonstrate our soundness to current and potential customers.

I'm open to the idea that we don't need an audit for past years in order to accomplish our goals, though we'd need an estimate in order to look at the cost/benefit.

Of course, at our current pace, we may have FY2016 or even FY2017 under our belts before we finish reconciling FY2013 (by the way, we decided to go with a June 1 fiscal year, to sync with the start of our books and set us up for an off-season audit). In that case, it'd be easy to decide to start with the later year.

Perhaps we can revisit the question when we get closer to having our first full year reconciled one way or another?

from finances.

Sounds good Chad. Thanks

from finances.

We gotta get this done, sooner rather than later. We want to run an audit for FY2016 mid-year. We have to be caught up by then. @kaguillera and I are now thinking that we should not try to start on January 2016 until we've caught up with the rest first. Otherwise we're going to be bouncing back and forth. I think it's going to be more efficient to make a straight run through. Over at gratipay/inside.gratipay.com#308 (comment) we collected most of the CSVs we need. Now we're working on getting them into a standard format in the logs repo, and then we can start writing scripts to convert raw CSVs from banks and processors into dat ledgers.

from finances.

Paris (gratipay/inside.gratipay.com#314) is just before the end of our fiscal year (May 31). Let's make that our target to get this done, so that we can schedule our first audit for June/July. That gives us 15 weeks to get ((13 * 4) - 1) = 51 PRs landed: three or four PRs per week.

from finances.

New Alliance CSVs updated in https://github.com/gratipay/logs/commit/d26ee72b2381490f3772890529b6c3cc248e0890.

from finances.

Last link is 404.

from finances.

@techtonik That's because you don't have perms on the logs repo.

from finances.

Seems there was a lot progress in #308. Beside doing catchup, is there plan to start book-keeping for current transactions? Or is it already setup?

from finances.

Yeah, we made a big push on this earlier, but then got side-tracked before really landing it. We really should get back to this. Perhaps you and I could meet up on Saturday or Sunday afternoon (November 12 or 13) to come up with a plan? There is a lot going on here ...

from finances.

Could I start working on this month's booking (1/2017)? Even with #35 not finished yet, I can still start getting familiar into the new transactions. I'll still work on pre-2017 booking, but IMO the latest is the most critical.

I will need the cleaned-up (masked account #, etc) bank statements or other material.

from finances.

@whit537 as mentioned in #3 (comment), shall I start with log or maybe it's simpler for you to export csv from bank statements?

from finances.

@whit537 now that I think of it, is it even practical to skip all the previous months and work on 01/2017? Even with the starting balance of New Alliance?

from finances.

We would have to enter starting balances for any accounts in use in 2017-01, yes. Which month would you like to tackle next? 2012-07 (#2) or 2017-01?

from finances.

@whit537 as I've setup freshdesk access through gratipay/inside.gratipay.com#878 (comment) (thanks!), may I confirm if below are the steps to tackle 2017-01:

1. search for all the receipts within 2017-01 in freshdesk
2. put starting balances (you will provide?) in FY2017/FY2017.beancount, like https://github.com/gratipay/finances/blob/master/FY2013/FY2013.beancount#L7
3. create FY2017/2017-01.beancount based on (1) and statements in logs

Is there necessary to pull some numbers from database?

from finances.

Yes, though for (2) you should be able to get opening balances from the logs repo, no?

Is there necessary to pull some numbers from database?

Oh, probably. :-) I think we may need to bring back the detailed part of the reconciliation dashboard in order to do paydays.

from finances.

Yes, though for (2) you should be able to get opening balances from the logs repo, no?

Yes for PNC, no for New Alliance. BTW new-alliance.csv has a empty line after header, otherwise github can render the file in table format.

Oh, probably. :-) I think we may need to bring back the detailed part of the reconciliation dashboard in order to do paydays.

If that's a blocker, is there an issue for this already? If not could you open one with some context please?

from finances.

To track paypal activities, I suppose opening balance for paypal 2017-01 is also needed?

from finances.

I guess this and subordinate PRs are now blocking on #43. 😩

from finances.