Chapter 54 - The Audit that Worked
The nonprofit's external audit found one significant weakness in our expansion accounting. A partner organization had been late submitting documentation, making it difficult to verify several expenses in the quarter when they occurred. The money had been spent for approved purposes, but the reporting process was not strong enough.
I felt embarrassed. We had built careful systems precisely to avoid this kind of problem. My first instinct was to defend the staff and explain why the deadlines were difficult. The auditor listened, then asked whether the board could see the problem clearly in our records.
"Not clearly enough," I admitted.
We wrote a corrective plan. The partner would submit monthly documentation, our finance team would review it promptly, and unresolved items would appear on a board dashboard rather than vanish inside email chains. The changes required work but did not demand that anyone be treated as dishonest.
At the next board meeting, I explained the finding without minimizing it. One member asked whether the issue meant the expansion had been a mistake. I said no. It meant a control hadn't kept pace with our growth and needed to change.
Teresa smiled from the end of the table.
Afterward, she told me the organization was fortunate to have a director who could admit a weakness without turning the admission into personal failure.
"That took me years," I said.
"I know. I was here for most of them."
Noah was having a similar experience. A researcher in his group found an error in a preliminary calculation that affected part of a paper draft. Nobody had published the result, and the correction could be made before submission. Still, Noah felt ashamed.
I told him about the audit. He laughed at the timing.
"So we're both being professionally humbled."
"Apparently."
He corrected the calculation, documented the change, and informed the group. His adviser thanked him for handling the issue directly. The project continued.
Vincent heard about the incident because Noah mentioned it in conversation. He told his son that businesses could survive errors if people addressed them quickly, but secrecy made them dangerous. Noah laughed and said the advice might have arrived a little late in the Moretti family.
Vincent accepted the joke.
The audit corrective plan was completed by the next quarter. The outside reviewer confirmed the documentation was sufficient. We did not erase the original finding from the file. It remained part of the record, followed by the actions we'd taken.
We invited the partner organization's finance coordinator to join the corrective review rather than treating the findings as a verdict from our office. She explained that her team had been understaffed and had relied on a spreadsheet that obscured which receipts were still missing. We redesigned the reporting schedule and arranged temporary training. The improvement took several weeks but made the system easier to use.
One board member asked whether we should end the partnership because the audit found a weakness. I reminded her that the partner provided valuable services and had cooperated fully once the issue was identified. Accountability required correction and reasonable consequences, not reflexive abandonment.
At home, Noah told me about a graduate student who had admitted an error in a shared computation before publication. The group had thanked the student and corrected the work. He said the experience made him less afraid of discovering his own mistakes. I understood. A trustworthy system wasn't one in which everyone pretended to be flawless. It was one where the truth could appear early enough to matter.
The corrective work also became an opportunity to train a younger finance coordinator. She had been nervous about discussing errors with program leaders because she feared sounding accusatory. I showed her how to describe a discrepancy as a question about records rather than a verdict on a person's honesty. We practiced together, then held the meeting. The program staff appreciated the clarity.
At the next review, she presented the dashboard herself. I watched her explain which documents had arrived, which remained outstanding, and who was responsible for each follow-up. The board asked questions. She answered confidently and admitted when she needed to verify a detail. I was proud of her willingness to be accurate without pretending she knew everything.
Later, she thanked me for allowing her to take the lead. I told her it was her work, and that the organization would be stronger if more people could explain its systems. The sentence reminded me of Noah learning to teach. Competence became more valuable when it could be shared.
That evening, I left the office on time and went to pottery. The bowl I started was uneven, but I kept shaping it. Nobody depended on it being perfect. It felt wonderful.
The following month, the partner finance coordinator reported that all required documentation had arrived on time. There were still small questions, but the system made them visible early. I thanked her team for the improvement and included the result in the board report. Nobody needed a dramatic announcement. The ordinary evidence of better work was enough. I was proud that the corrective plan had become a routine rather than a temporary performance for auditors.
At the annual staff meeting, we shared the audit lesson with new employees. I asked them to treat missing information as a question to investigate, not an accusation to make. One coordinator said the guidance made her less afraid of reporting errors. I told her that was the purpose. Records should help people act responsibly while problems were still small. The work would never be flawless, but it could be honest and correctable. I wanted the people who came after me to understand that distinction without needing a family disaster to teach it.
May you like
I liked that sequence. Mistake, acknowledgment, correction. No mythology. No need to declare someone permanently good or bad.
When I came home, I placed the final audit letter in my office file and went to the pottery class. My bowl collapsed almost immediately. I laughed, reshaped the clay, and started again.
