Skip to content

FY2013 Financial Report amendment #37

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

hlapp
Copy link
Member

@hlapp hlapp commented Oct 5, 2016

Factors in $16.07 discrepancy between SPI reports. Specifically, the custom-compiled report for OBF's FY2013 shows an ending balance for OBF earmarked funds that differs from the ending balance for OBF in the Nov 2013 SPI Treasurer's Report by $16.07.

Specifically, the custom-compiled report for OBF's FY2013 shows an
ending balance for OBF earmarked funds that differs from the
ending balance for OBF in the Nov 2013 SPI Treasurer's Report by $16.07.
@hlapp hlapp changed the title Factors in $16.07 discrepancy between SPI reports FY2013 Financial Report amendment Oct 5, 2016
@hlapp
Copy link
Member Author

hlapp commented Oct 5, 2016

Folks - I just discovered that I had forgotten to push up this final change to the FY2013 report. It wasn't purely forgetfulness, though - I sent an inquiry to SPI asking for the discrepancy to be explained, and had not heard back by the time of the Oct 4 meeting (and still haven't).

@peterjc
Copy link
Member

peterjc commented Oct 6, 2016

Does this need approval at another public board meeting?

@hlapp
Copy link
Member Author

hlapp commented Oct 6, 2016

Yes. Any changes to Financial Reports need a formal approval from the Board.

That said, the 2014 Financial Report, if you happened to notice, already has the correct carry-forward balance for the SPI funds on it. So waiting for approval until the next public Board meeting has no detrimental effect.

@nlharris
Copy link
Member

This is still sitting here?

@peterjc
Copy link
Member

peterjc commented Aug 13, 2022

Approving this needs to go on the agenda for our forthcoming official board meeting...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants