Chapter 75 - THE LEDGER IN THE LIBRARY
The finance review began with numbers printed on pale yellow paper. A line in the Cedar Street reimbursement ledger showed payment for a transportation consultation that appeared, at first glance, to have been claimed by two organizations. One was Harborlight. The other was a local nonprofit whose work had helped residents reach temporary housing. The second organization had a good reputation, and the thought of its name being pulled into public suspicion made me uneasy.
Our center had no authority to examine private payment records. The city's finance team would determine the facts. But we could help residents understand what the review meant for their appointments and ensure that no one was asked to repeat sensitive information unnecessarily. Elena assigned Nia to update our public guidance. I focused on staff training, especially the temptation to treat every questionable number as evidence of a dishonest person.
Mrs. Mercado called from the library, where she was reviewing the publicly available summary. "I understand the two claims," she said. "What I don't understand is whether they paid twice or just recorded the same visit in two places."
"That's exactly what they're checking."
"Then why does the headline say double billing scandal?"
"Because uncertainty doesn't sell many newspapers."
She sighed. "I have never wanted the newspaper to be exciting. I want it to be right."
At lunch I joined her at the library table. She had arranged the public documents in chronological order, using paper clips and a ruler. Beside them lay a paperback mystery novel with a cracked spine. I asked whether she was enjoying it. She said the detective was unbearable because he guessed the solution after meeting only three people.
"You would demand his audit trail," I said.
"And a better editor."
We laughed, then returned to the city summary. It explained that certain appointments had been recorded by the outreach contractor as completed contacts and by a transport provider as delivered trips. Those could be legitimate separate activities, but the billing codes had been mapped incorrectly during data migration. The finance team needed to verify the original invoices, service logs, and contract terms before deciding whether any overpayment had occurred.
The distinction mattered. A duplicate-looking line could arise from an actual duplicate bill, an import error, or two different services grouped under the same description. Residents would not be helped by blaming someone before the underlying work was checked.
Meanwhile wedding planning became the source of cheerful tension in our kitchen. Teresa proposed a menu far more elaborate than the small ceremony we'd imagined. Bianca argued for a dessert table. Mom wanted to know whether she'd be allowed to bring cinnamon bread. Lily insisted on a purple cake but said the adults could choose the rest, provided there were no boring speeches.
"I think the ceremony should last fourteen minutes," she declared.
"Why fourteen?" Luca asked.
"Ten is too short. Twenty is too long. Fourteen is fair."
I agreed it was an excellent starting proposal, subject to further discussion. She was delighted to hear herself quoted in official-sounding language.
At the library, Mrs. Mercado and I were joined by a former bookkeeper named Mrs. Chen, who had lived in the neighborhood for forty years. She brought a pocket calculator and a pencil sharpened to a point. She was careful to say she had no access to private invoices and was simply trying to understand the public summary. Together we reviewed how a single appointment could appear in two categories without being paid twice.
"The description is terrible," Mrs. Chen said. "If I had written that code, my supervisor would have sent it back."
Mrs. Mercado nodded. "Then perhaps the problem begins with a person who wanted a neat number more than a clear description."
"Or with a rushed change in software," I said. "The reviewer will have to establish it."
Mrs. Chen gave me an approving glance. "You don't like guesses either. Good. But you should ask why nobody checked the totals against a sample of actual work."
We added the question to the list for the next public financial briefing. The two women then spent ten minutes discussing the merits of calculators with large buttons. I could barely keep up.
Back at the center, David showed our team a mock audit of the emergency assistance budget. He deliberately inserted one incorrect code and one missing approval into the sample. The exercise wasn't a trap; staff knew there would be problems to find. Nia identified the missing approval quickly. Rosa discovered the code error by comparing the service description to the receipt. David thanked them and explained how the checks protected both visitors and workers from later confusion.
"I used to think an audit meant someone was suspicious of me," Rosa admitted.
"It should mean the organization is willing to test its own records," David said. "A good audit can support you when the facts are right as well as show us when something needs fixing."
That evening I told Luca about the exercise. He suggested we have the same discussion with Lily about her school budget proposal. I said we could, as long as he didn't turn her allowance into a corporate compliance program. He promised to resist, though his smile suggested it would be difficult.
At work the board reviewed our financial controls in light of the city case. We already required documented approval of payments, but one reimbursement category had vague descriptions that made later verification difficult. David proposed revised coding and periodic sample checks. Margaret asked whether the new process would create extra burdens for families receiving assistance. Nia recommended that checks occur internally wherever possible, without repeatedly contacting people to prove they'd needed help. The board approved the changes.
The finance team later invited residents to submit questions for a public explanatory session. One question asked why a billing code mattered when a person had actually received transport. The reviewer explained that codes affected how payments were approved and checked. If two services were grouped together inaccurately, an agency might not know whether it had paid for a ride, a consultation, or both. Clear descriptions protected public funds and made it easier to correct a mistake. Mrs. Chen wrote the explanation in the margin of her paper, then asked for a version that would fit on one page.
A week later the city finance reviewer released a preliminary clarification. Some of the apparent duplicate entries had indeed resulted from mismatched billing codes during migration. A smaller number remained questionable because supporting records were incomplete. Those items were being held for further examination. The reviewer did not allege that the reputable transport nonprofit had intentionally double-billed; its own records had helped identify the mismatch.
I was relieved. Then I noticed a sentence in the report explaining that the problematic coding scheme had been adopted during a transition overseen by CivicBridge's predecessor. I did not leap from the old name to a conclusion about the present staff. I forwarded the public link to Elena and our counsel, asking whether our own grant reporting system had any similar assumptions. The answer came back quickly: our evaluator used a different process with an independent validation step. We documented the confirmation anyway.
That Friday I took a day off to visit the coast with Luca. We walked along the harbor, where gulls perched on the railings and fishing boats rocked against their lines. He'd brought no business papers. I had turned off the center's nonemergency notifications. For once our largest decision concerned whether to eat lunch beside the water or at a small café farther inland.
We chose the café. The owner brought soup and told us about the weather. A woman at the next table was teaching a child to fold a napkin into a boat. Luca watched them, smiling, then turned to me.
"Do you remember the first dinner we had after the center opened?" he asked.
"You were very careful not to offer to buy the restaurant."
"I still think that was a remarkable achievement."
"It was a good dinner because we talked."
He took my hand across the table. "I'm glad we kept talking."
When we returned home, Lily had left a note on the kitchen counter: WEDDING PLANNING COMMITTEE REQUESTS AN UPDATE. I told her the committee would receive a written response after the adults had eaten dessert. She accepted this delay with visible irritation.
May you like
The next morning the city announced a final reconciliation schedule for the outstanding ledger entries and a plan to recover any confirmed improper payments through established procedures. It was neither the sweeping fraud story some people wanted nor the harmless clerical mix-up others had claimed. It was an ongoing accounting and legal process with real consequences.
I folded the newspaper and set it aside. In the library, Mrs. Mercado would be making notes. At Open Door, Nia would be updating training materials. At home, Lily would be campaigning for a purple cake. I liked the fact that all three activities could matter without one being turned into a metaphor for the others.
