Chapter 40: Planted
Grace’s second audit day began with a ledger that did not belong in Holt’s records room.
The file appeared on a shared drive under a folder named Route Reconciliation, dated three days before the zoning hearing.
It contained twenty-seven payables, two approval chains, and one note that called Ryan Keller an unreliable controller.
"This file was written for an audience," Grace said, enlarging the metadata, "it explains the crime before anyone asks whether the crime occurred."
"The note points at Keller," Nia replied, "but the upload came through a terminal nobody used for finance."
"That makes the note useful as evidence and useless as a conclusion," Grace said, saving the metadata beside the ledger.
Ryan stood behind them with the operating statement open on paper.
"How much can we pay while the verification remains open?" he asked.
"Nothing connected to the disputed vendors," Grace answered, "pay payroll, safety, and any supplier who can prove a clean delivery."
Operating cash began at thirty-one thousand four hundred dollars before the required payroll release.
The scheduled payroll run required nine thousand six hundred dollars before the next route launch.
The hazard bonus for crews who had entered the dungeon route required four thousand eight hundred more.
[Operating Cash: 31,400]
[Payroll: -9,600]
[Hazard Bonus: -4,800]
[Available Cash: 17,000]
Ryan checked the final bank line twice against the escrow release confirmation.
The accounting display corrected its balance by eleven dollars after the route escrow released a retained fee.
[Operating Cash Verified: 17,011]
"The eleven dollars matters because the ledger must reconcile to the cent," Grace said, recording the adjustment, "small differences become hiding places when people grow tired."
"Then the balance is seventeen thousand eleven," Ryan replied, "we will not spend the eleven to make the statement look round."
Mika entered with a food container and a folder from the guild.
"Keller did not create the planted ledger," she said, setting the folder down, "his access card was logged at the mine entrance when the file appeared."
Nia opened the guild access record beside the warehouse terminal image.
"The card used the same badge number as Keller’s," she said, "but the entry camera shows a shorter person wearing his outer jacket."
"The guild coat again," Ryan said, looking at the image.
Grace paused over the frame while the glare erased the figure’s face.
"A costume can create an alibi if the camera records shape instead of identity," she said, "I want the original video, not the compressed copy."
The guild provided the original after Grace cited the audit clause attached to the route contract.
The figure entered the warehouse at 10:14 p.m., crossed the dispatch floor, and left twelve minutes later.
No face remained inside the camera’s angle after the figure crossed the loading glare.
"The person knew the blind spot," Mika said, leaning over the screen, "they stood where the loading lights created glare."
"The person also knew which account to use," Grace replied, "Invoice 4421 is the hinge."
Invoice 4421 listed a duplicate route survey with no corresponding delivery file.
Its first version carried a correct date, a complete delivery record, and a receiving signature from Dara.
The second version changed the vendor name by one word, split the payment into four entries, and rounded every amount down by ninety-seven cents.
"That rounding leaves a trail," Nia said, comparing both files, "the total difference is small, but the pattern repeats across every ghost payable."
"A person who wants to steal hides the amount," Grace answered, "a person who wants to frame someone hides the method."
Ryan looked toward Keller, who waited outside the glass door with both gloves still on.
"Bring him in," Ryan said, pointing toward the records room.
Keller entered without removing his gloves or looking at the planted ledger.
"I knew the account existed," he said, looking at the planted ledger, "but I never saw the entries."
"Who knew your badge could be borrowed?" Grace asked.
"Any guild supervisor with access to the route floor," Keller said, rubbing his thumb across the badge edge.
"Who knew the finance terminal stayed online after closing?" Grace asked, turning toward Keller.
Keller named three people, then stopped when the fourth name reached his throat.
"The third is a guild-trained compliance framer," he added, "he audits contractors before they receive dungeon permits."
Ryan felt the pressure behind the ledger change shape while the guild access trail narrowed around one credential.
The attack did not begin with Holt.
It began with a person who understood how a clean record could be made to accuse its owner.
"Grace, extend the verification window," Ryan said, turning from Keller to the audit table, "we need every guild connection before we answer the watchdog."
"I already requested the extension," Grace replied, lifting the signed notice, "you have another seventy-two hours."
The notice carried no accusation, yet it carried enough authority to make the guild’s legal office call twice before lunch.
"Do we answer them?" Mika asked.
"Not until the evidence has one shape," Ryan said, closing the ledger, "a partial truth is a weapon for whoever placed it."
The business paid its workers, froze the disputed accounts, and continued loading equipment under ordinary supervision while the guild’s legal office demanded a response.
The public saw a functioning warehouse operating under ordinary supervision.
Inside the records room, Grace built a chain from one false signature to the guild’s most careful gatekeeper.
Mika returned with the original camera file and placed it beside the planted ledger.
"The figure touched the dispatch terminal, but the audit image cannot show which account opened the upload folder," she said, checking the timestamp, "we need the guild credential log before the evidence becomes another argument."
"The guild will say its log is privileged," Nia replied.
"Then the permit contract must decide whether privilege survives a public fraud referral," Grace answered, opening the relevant clause.
Ryan read the clause aloud for the record and sent a formal request through the city portal.
The request asked for credential identifiers, access times, badge substitutions, and every compliance review attached to Holt’s route.
"That request may provoke them," Mika said.
"It should provoke a precise answer," Ryan replied, "silence would be more useful to the person who planted the file."
The guild office responded with a promise to review the request within one business day.
Grace recorded the response without celebrating it.
"A delay is not a refusal," she said, "but it is now part of the timeline."
Keller stood beside the terminal image with his gloves tucked into one pocket.
"If the badge was borrowed, I want the access failure fixed before I return to the route," he said.
"You will not return to a route that can make you the scapegoat," Ryan replied, "we will replace the shared badge process first."
Nia drafted a dual-approval rule requiring a live identity check for every compliance upload.
Grace reviewed the rule and added an emergency override that required a named witness.
The control cost less than one invoice and protected more than the amount under dispute.
Ryan saved the revised rule beside the ledger.
"The new rule needs a backup witness outside finance," Grace said, adding a line to the procedure.
"Mika can witness route uploads when Nia handles the payment file," Ryan replied, "the control should follow the work rather than a title."
"That gives operations a duty they cannot delegate casually," Nia said, reviewing the draft.
"Good," Grace answered, "a control becomes real when it interrupts a convenient shortcut."
The guild’s response arrived before the next shift began.
It provided credential numbers but omitted the badge substitution history requested in the permit clause.
"They answered the easy part," Mika said, opening the response, "the missing history is the part that could identify the operator."
"We request the omission directly," Ryan replied, "the record should show that the guild received the question."
Grace sent the follow-up through the city portal and attached the revised internal control.
Holt now had a visible weakness, a documented remedy, and an unanswered guild request.
"This control will be tested during the next route launch," Grace said, sealing the procedure.
"Our route team will know the witness rule before the first truck moves," Ryan replied, adding the briefing to the dispatch file.
"This audit can now distinguish a mistake from a designed entry," Nia said, saving the final version.
’A planted ledger had failed as a theft,’ Ryan thought, listening to the audit printer, ’but it might still succeed as a reason to remove us.’
"This procedure is worth more than the disputed invoice," Grace said, placing the signed copy in her case.
"Our procedure now has a witness and a receipt," Nia said, saving the control file.
"This control can survive an audit," Ryan replied, closing the records room.
The revised process forced every future upload to carry an identifiable witness, an unchanged receipt, and a reason that a hostile auditor could test without asking Holt to explain its own innocence.
The control changed the business’s risk from an invisible accusation inside one shared terminal into a visible sequence that workers, auditors, lenders, and city officials could each inspect without trusting the owner first.

Comments
Comment Rules
Please read and follow these rules before posting a comment. By submitting a comment, you agree to comply with all applicable rules below.
Site administrators and editors reserve the right to moderate, edit, or remove comments.
The following activities are strictly prohibited in comments and reviews:
Such comments will not make updates arrive faster. If a new chapter is available to us, we will publish it. If it has not been published, it means that we do not have it yet.
Do not flood the comment section by posting multiple consecutive comments. You may edit your previous comment to add more information, or include everything you want to say in a single comment.
Users who violate these rules may receive a warning. Repeated or serious violations may result in a temporary or permanent suspension of commenting privileges.
Commenting Suspended