BackThe Debt That Wasn't Mine
This chapter is saved on your device for offline reading
Chapter 13

One Bad Tick

Mariam arrived at the old ArchiveLink building at half past eight in the morning, with a bureau envelope in her bag and a photograph of the wedding sample on her phone. The building stood behind the River Road bus station, on a street where shops opened their doors before office workers arrived. A faded sign read **Legacy Records — Closed Operations**.

Jonas had sent her the name of the person who managed verification in 2006: Peter Odhiambo, now retired and a consultant for a small compliance firm. There was no guarantee that Peter would agree to speak. Mariam had not come to trap him. She wanted evidence of the process, not someone to blame.

Halima arrived ten minutes later. She stood beside the gate, holding her file with both hands.

“Have you changed your mind?” Mariam asked.

“No. I have changed how I am coming.”

“What does that mean?”

“I will not bring memories I cannot verify. And I will not say that something I heard is something I saw.”

Mariam smiled tiredly. “That is why I asked you to come.”

The guard let them through to reception. A woman working for the current company looked at Peter's name, then called inside. After a few minutes, she directed them to a meeting room with a plastic table and a window looking over the roofs of the shops.

Peter entered wearing a blue shirt buttoned to the neck. He carried a thin paper, not a large file to hide behind.

“I cannot disclose client information,” he said before they sat.

“And I am not asking for anyone else's information,” Mariam replied. “I am asking you to explain the kind of verification performed on my record, if you can still see it.”

Peter looked at Jonas, who had sent them, and sat down. “Which record?”

Mariam placed a copy of the bureau audit log in front of him, the one with the **ADDRESS MATCH** line from 2006. It contained neither the name Mary N. Njoroge nor suffix 0091.

“The legacy loan connected to my borrower code,” she said. “The bank has not found a disbursement account that matches my profile. The bureau shows an address verification. I was told you were on the verification team.”

Peter picked up the paper but did not touch it for a moment. “Verification was batch work. We handled thousands of records.”

“That is why I don't want a quick conclusion. I want to know the checklist.”

Peter opened his paper. “That year we received files from the lender and a data vendor. Our work was to compare the fields submitted: name, address, date of birth if available, and the exception flag.”

“And the account?”

“The account field belonged to the lender.”

“Wasn't it part of your approval?”

Peter drew a breath. “It was part of the exception review, but not every verifier had access to the ledger.”

Halima asked, “If the account was blank, how could the verification pass?”

Peter looked at her. “Blank did not always mean there was no account. Sometimes it meant the submitted file did not contain that field.”

Mariam took out her notebook. “Under the checklist, a blank account had to be sent back to the source?”

Peter paused. “Normally, yes.”

“Normally is not an answer for this case.”

Mariam turned the page of the audit log. “Here is the address match. There is no account check. And the bureau says the verification response was used to keep carrying the liability. Was a shortcut used?”

Peter did not answer at once. He read the line again, then looked out the window.

“In some batches, the verifier was given a screen with fields already prepared. If the address matched and no exception appeared on the panel, the response went through as a match.”

“And the blank-account exception?”

“It was supposed to appear on the source sheet, not necessarily on the panel.”

Mariam wrote it down. “So the verification screen was not the final source.”

“It was not. It was an intermediate layer.”

“But it was used as final evidence.”

Peter put the paper down. “It appears so.”

Halima opened her file and took out the statement she had signed. “I delivered Mariam's envelope to the student-finance office. I did not receive money. I don't know whether her envelope was ever joined to someone else's file.”

Peter looked at it, then handed it back. “That is separate from the 2006 verification.”

“But it shows that the chain began earlier,” Mariam said. “If the source batch was wrong, the later verification should have checked the source.”

Peter gave a slight shake of his head. “I would agree if I had seen the source batch.”

“You saw it?”

“I cannot remember one record after twenty years.”

“I am not asking you to remember my name. I am asking you to look at the company's checklist.”

Peter stood and went to a cabinet at the side. He took out a thin binder labeled **Verification — Retired Workflow**. He opened the section with old dates. One page had pencil marks; another bore the stamp of the closed company.

He placed the checklist in front of Mariam.

The first step was **Borrower identity fields**. The second was **Address confirmation**. The third was **Source exception review**. The fourth was **Submit response**.

Mariam pointed to the third line. “It says here that a source exception must be opened if an important field is missing.”

“Yes.”

“And my record had a blank account.”

“That is what you say.”

“Then an address-match response alone was not enough.”

Peter did not answer, but his finger stopped over the fourth line.

Halima said, “There is a tick here.”

Peter looked at it. On the copy of the checklist, the **Source exception reviewed** box had one tick. There were no initials. There was no date. Beside it was the batch code **M-14B**.

Mariam felt her stomach tighten. “Whose tick is this?”

“I cannot know without the original log.”

“But does it prove the step was claimed to have been completed?”

“It proves that someone made a mark.”

“Not that they checked the source?”

Peter looked directly at her. “A tick is not proof of an action. It is proof of a mark.”

The words settled in the room like a closed door.

Mariam took a small recorder from her bag but did not turn it on. “I would like an official statement. You can say that the workflow required source review, that an address match alone was not enough, and that the panel could accept a response without an account field. Do not say that I was a victim of fraud. Do not say Halima was involved.”

Peter sat down again. “A statement like that could put my company at risk.”

“And an inaccurate statement has kept my name attached to a debt for years.”

“You want me to write that the system could be wrong?”

“I want you to write what you can verify about the process.”

Halima moved closer to Mariam. “Don't make him say more than he knows.”

Mariam nodded. “I will not make him a witness to something he did not see.”

Peter asked for a few minutes. He wrote the date, the workflow, and his limitation on the company's paper. Then he signed it. He added two sentences: **Address match was not, by workflow design, a substitute for source-account verification. A completed tick in a legacy checklist cannot by itself establish that the underlying source field was reviewed.**

Mariam read every word. There was no name of Mariam, Halima, or Mary. There was no accusation beyond the evidence.

“May I submit this to the bureau?” she asked.

“Yes. But do not say that I have verified your entire case.”

“I won't.”

Peter placed the shadow of his pen beneath the batch-code line. “M-14B moved through because no one went back to the source batch.”

Mariam raised her eyes. “Is that a memory or a conclusion?”

“It is what we were told when the workflow changed. The source batch was behind the vendor; the panel was in front of us. When people saw the tick and the address match, they closed the task.”

“And who approved the second verification?”

Peter closed the binder. “That name is in the approval log, not in this checklist.”

“Can you request the approval log?”

“I can ask. I cannot promise they will release it.”

Mariam secured the statement and photographed the checklist with his permission. Halima placed a hand on her shoulder for a moment, then withdrew it.

When they went outside, Mariam's phone rang. Kendi was at the studio.

“Babu says the balance must arrive today,” Kendi said. “Asha has sent a message confirming the milestone, but the supplier says that is not enough.”

Mariam looked at Peter's statement in the folder.

“We will get the first amount,” she said.

“Do you have proof?”

“I have proof of the process. I do not have the money yet.”

Kendi fell silent. “That is not an answer that makes the supplier happy.”

“I know. But it is the true answer.”

Mariam called Ruth and sent her a photograph of the statement. Ruth replied after a few minutes: *This may support the audit-chain request. Please send the signed original and clarify that it addresses workflow, not borrower ownership.*

Mariam opened Peter's message again. The final line was shorter than everything she had searched for over many days: **No one went back to the source batch.**

She closed the folder, looked at Halima, and said, “Now we can show where the tick hid the gap.”

Halima did not smile. “And we still don't know who made the tick.”

“We will look for the name in the approval log.”

Mariam got into the car. Before starting the engine, she wrote on the evidence map: *Workflow required source review. Address match could pass without account verification. The second verification was approved because no one returned to the source batch.*

Beneath the lines she placed one mark.

Not a person's name.

A question for the approval log.

---

Reading settings
Line spacing
Theme