Invoice HPP-2025-03 is booked to Rent for March 2025 [invoices#15]. Walk me from the invoice to the cash that left the account, and show that it left exactly once.
Northwind Labs, Inc.
- Run
- Northwind Labs FY2025 — walkthrough sample
- Run id
- walkthrough
- Started
- —
- Seed
- —
- Materiality
- —
- Sample size
- —
- Cycles
- —
- Prepared by
- Crossfire — auditor and accountant agents
- Reviewed by
- Controller, Northwind Labs
- Printed
- September 21, 2026
Each workpaper below records one sampled transaction: the procedure it was tested under, the assertion that procedure supports, the auditor's question, the accountant's answer with every row it cites, and how the item was disposed of. Nothing on this page is written by a model: the transcript is quoted, the citations are rows, and the proposed entries come from a fixed table keyed by the kind of gap found.
Harbor Point Properties LLC · HPP-2025-03
- Procedure
- Not recorded
- Assertion tested
- Not recorded
Exchange
- Auditorturn 1
- Accountantturn 2
The invoice itself is clean; the cash side is not. Harbor Point Properties LLC billed $9,200.00 on 2025-03-01 [invoices#15], which is exactly the monthly rate on the contract [contracts#2]. The bank feed then settles reference HPP-2025-03 twice, on 2025-03-24 [bank_transactions#72] and again on 2025-03-27 [bank_transactions#73]. Both settlements are booked, so Cash is credited twice [ledger_entries#314, #326] against a single payable. I can defend the first payment and not the second.
Evidence cited (6)
- 1.[invoices#15] amount = 9200.00 — The invoice being settled, priced at the contract rate. HPP-2025-03.pdf
- 2.[contracts#2] monthly_rate = 9200.00 — Contract rate for Harbor Point rent matches the invoice to the cent. harbor-point-properties-contract.pdf
- 3.[bank_transactions#72] date = 2025-03-24 — First settlement of reference HPP-2025-03.
- 4.[bank_transactions#73] date = 2025-03-27 — Second settlement of the same reference three days later.
- 5.[ledger_entries#314] credit = 9200.00 — Cash credited for the first payment.
- 6.[ledger_entries#326] credit = 9200.00 — Cash credited again for the duplicate payment.
Gaps
- duplicate_paymentBank rows 72 and 73 both settle HPP-2025-03 for $9,200.00, but only one payable exists. No credit note or vendor refund reverses the second.
Disposition
Gap — the accountant admitted the item is not fully supported. Escalated to the controller, not yet ruled.
Proposed adjusting entry
| Account | Debit | Credit |
|---|---|---|
| Accounts receivable — vendor overpayments | $9,200.00 | — |
| Operating expenses | — | $9,200.00 |
Reverse the second settlement of this reference and set up the refund receivable.
Amount is the duplicated payment.
Basis: [invoices#15]
Stratus Compute Inc. · STR-2025-05
- Procedure
- Not recorded
- Assertion tested
- Not recorded
Exchange
- Auditorturn 1
Invoice STR-2025-05 bills $21,275.00 [invoices#5], more than any other Stratus invoice this year. Show me the pricing authority for that amount.
- Accountantturn 2
There is none on file. The contract fixes the Stratus monthly rate at $18,500.00 for all of 2025 [contracts#1], and the January invoice bills exactly that [invoices#1]. This one bills $21,275.00 [invoices#5], fifteen percent over the rate, and it was approved as issued [invoices#5]. The bank settled the billed amount rather than the contracted one on 2025-05-17 [bank_transactions#109], and the expense was recognised at the higher figure [ledger_entries#457]. No amendment or credit note supports the $2,775.00 difference [contracts#1, invoices#5].
Evidence cited (6)
- 1.[contracts#1] monthly_rate = 18500.00 — The contracted monthly rate the invoice should have billed. stratus-compute-contract.pdf
- 2.[invoices#5] amount = 21275.00 — The amount actually billed, 15% above the contract rate. STR-2025-05.pdf
- 3.[invoices#1] amount = 18500.00 — A sibling Stratus invoice billed at the contract rate, showing the norm. STR-2025-01.pdf
- 4.[invoices#5] approved_by = Priya Natarajan — The overbilled amount was approved as issued. STR-2025-05.pdf
- 5.[bank_transactions#109] amount = -21275.00 — The bank settled the billed amount, not the contract amount.
- 6.[ledger_entries#457] debit = 21275.00 — Cloud Infrastructure was expensed at the overbilled amount.
Gaps
- rate_mismatchInvoice 5 exceeds contract 1's monthly rate by $2,775.00 with no amendment on file.
Disposition
Gap — the accountant admitted the item is not fully supported. Escalated to the controller, not yet ruled.
Proposed adjusting entry
| Account | Debit | Credit |
|---|---|---|
| Accounts receivable — vendor overpayments | $2,775.00 | — |
| Operating expenses | — | $2,775.00 |
Reverse the amount billed above the contracted monthly rate.
Amount is the invoice amount less the contracted monthly rate.
Basis: [invoices#5] [contracts#1]
Kestrel Holdings Ltd · WIRE-20250912-4471
- Procedure
- Not recorded
- Assertion tested
- Not recorded
Exchange
- Auditorturn 1
A wire for $7,850.00 left the account on 2025-09-12 [bank_transactions#202]. Who is Kestrel Holdings Ltd [bank_transactions#202], and what authorised the payment?
- Accountantturn 2
I cannot place them. The payee on the wire is Kestrel Holdings Ltd [bank_transactions#202], and no vendor row carries that name. There is no invoice or contract naming them either, so the reference WIRE-20250912-4471 is the only support the payment has [bank_transactions#202]. It was booked straight to Consulting Expense [ledger_entries#1025] against Cash [ledger_entries#1026], with no document behind the classification.
Evidence cited (4)
- 1.[bank_transactions#202] counterparty = Kestrel Holdings Ltd — The payee has no matching row in vendors.
- 2.[bank_transactions#202] amount = -7850.00 — The amount leaving the account, above the $5,000 wire threshold.
- 3.[ledger_entries#1025] account = Consulting Expense — The expense account the wire was booked to without a supporting document.
- 4.[ledger_entries#1026] credit = 7850.00 — Cash credited for the full wire amount.
Gaps
- unknown_counterpartyKestrel Holdings Ltd is not a vendor, payroll recipient, or processor, and no document supports the Consulting Expense classification.
- no_matching_invoiceNo invoice, contract, or statement of work references WIRE-20250912-4471.
Disposition
Gap — the accountant admitted the item is not fully supported. Escalated to the controller, not yet ruled.
Proposed adjusting entry
| Account | Debit | Credit |
|---|---|---|
| Suspense — unidentified counterparty | $7,850.00 | — |
| Operating expenses | — | $7,850.00 |
Park the payment in suspense until the counterparty is identified.
Amount is the payment to the unidentified counterparty.
Basis: [bank_transactions#202]
Dodo refund · ref_nx3ulzfvg9d7
- Procedure
- Not recorded
- Assertion tested
- Not recorded
Exchange
- Auditorturn 1
A refund of $499.00 was processed on 2025-04-12 [dodo_transactions#92]. Show me the journal entry that reverses the revenue.
- Accountantturn 2
There is no such entry. The original payment for $499.00 on 2025-04-01 [dodo_transactions#82] is booked correctly, debiting Dodo Clearing [ledger_entries#355] and crediting Revenue [ledger_entries#356]. The refund of the same amount [dodo_transactions#92] has no ledger row of its own, so April revenue is overstated. The April payout had already deducted the refund, which is why Dodo Clearing does not net to zero for that month [dodo_transactions#92].
Evidence cited (4)
- 1.[dodo_transactions#92] amount = 499.00 — The refund amount that never reached the ledger.
- 2.[dodo_transactions#82] reference = pay_v5wed4ozzxvkyo — The original payment the refund reverses.
- 3.[ledger_entries#355] debit = 499.00 — Dodo Clearing debited when the payment came in.
- 4.[ledger_entries#356] credit = 499.00 — Revenue credited for a payment that was later refunded.
Gaps
- missing_ledger_entryNo ledger row carries source_type dodo and source_id 92, so the $499.00 refund is unbooked.
Disposition
Gap — the accountant admitted the item is not fully supported. Escalated to the controller, not yet ruled.
Proposed adjusting entry
| Account | Debit | Credit |
|---|---|---|
| Operating expenses | $499.00 | — |
| Cash — operating | — | $499.00 |
Post the journal entry for a transaction that never reached the ledger.
Amount is the transaction absent from the ledger.
Basis: [dodo_transactions#92]
Bellhaven Insurance Group · ACH-20250620-BHI
- Procedure
- Not recorded
- Assertion tested
- Not recorded
Exchange
- Auditorturn 1
A payment of $3,120.00 went out on 2025-06-20 under reference ACH-20250620-BHI [bank_transactions#133]. Which invoice does it settle?
- Accountantturn 2
None that I can find. The payee is a known vendor [vendors#5], so this is not an unknown counterparty. Its contract bills $2,350.00 a month [contracts#5], which does not match the amount paid [bank_transactions#133]. The payment was still debited to Accounts Payable [ledger_entries#653] with Cash credited [ledger_entries#654], so it cleared a payable that no invoice created.
- Auditorturn 3
Insurance is often billed annually rather than monthly. Is the amount a multiple of the contracted monthly rate, or a premium adjustment [contracts#5]?
- Accountantturn 4
Neither. The payment is not a whole multiple of the $2,350.00 monthly rate [contracts#5, bank_transactions#133]. The contract terms on file carry no premium adjustment clause [contracts#5], and the contract is still in force on the payment date [contracts#5], so a lapse does not explain it either. Every other payment to this vendor in the feed references an invoice number; this one references an ACH batch the vendor never issued [bank_transactions#133].
Evidence cited (3)
- 1.[contracts#5] terms_text = SERVICES AGREEMENT Contract reference: BHI-CTR-2025-005 Provider: Bellhaven Insurance Group Provider address: 1 Financial Plaza, Hartford, CT 06103 Client: Northwind Labs, Inc. Client address: 400 Summer Street, Floor 4, Boston, MA 02210 1. Services Bellhaven Insurance Group ("Provider") agrees to supply business insurance to Northwind Labs, Inc. ("Client") as described in this agreement: General liability and D&O coverage, monthly premium. 2. Fees Monthly rate: $2,350.00 Client shall pay Provider a fixed monthly fee of $2,350.00, invoiced on the first day of each calendar month for that month. Each month is invoiced exactly once. No other fees, surcharges, or rate changes apply during the term unless agreed in a signed amendment. 3. Term Effective from: January 1, 2025 Effective to: December 31, 2025 This agreement is effective from January 1, 2025 through December 31, 2025 inclusive. Services and billing end on the effective-to date. Any invoice dated after that date is outside this agreement. 4. Payment terms Invoices are due 30 days from the issue date (net 30) by ACH transfer referencing the invoice number. Client's internal policy requires every invoice to be approved by an authorised approver before payment, and invoices above $10,000 must be approved by the CFO. 5. Signatures For Provider: Authorised signatory For Client: Priya Natarajan, CFO — The contract terms as filed, with no premium adjustment provision. bellhaven-insurance-contract.pdf
- 2.[contracts#5] effective_to = 2025-12-31 — The contract is in force on the payment date, so lapse does not explain it. bellhaven-insurance-contract.pdf
- 3.[bank_transactions#133] reference = ACH-20250620-BHI — The reference is an ACH batch id, not an invoice number.
Gaps
- no_matching_invoiceThe amount reconciles to no combination of contract 5's monthly rate, so the payment remains unsupported.
Disposition
Open — still with the accountant when this binder was printed.
Proposed adjusting entry
| Account | Debit | Credit |
|---|---|---|
| Unsupported expenditures — under review | $3,120.00 | — |
| Operating expenses | — | $3,120.00 |
Reclassify the disbursement that has no supporting invoice.
Amount is the payment with no invoice behind it.
Basis: [bank_transactions#133]
Notchwork SaaS Ltd. · NWK-2025-08B
- Procedure
- Not recorded
- Assertion tested
- Not recorded
Exchange
- Auditorturn 1
Notchwork billed twice in August 2025, first NWK-2025-08 [invoices#32] and then NWK-2025-08B [invoices#33]. Justify the second one.
- Accountantturn 2
I can show the paperwork but not the entitlement. The contract is a $1,450.00 monthly subscription [contracts#3], and NWK-2025-08 already covers August at that amount [invoices#32]. The second invoice is dated 2025-08-18 for the same amount [invoices#33] and was approved by Marcus Webb [invoices#33]. It was paid in full on 2025-09-03 [bank_transactions#196] and expensed to Software Subscriptions a second time for the month [ledger_entries#923]. The contract provides for one monthly charge [contracts#3], so unless there is an upgrade order outside the system, August was billed twice.
Evidence cited (6)
- 1.[contracts#3] monthly_rate = 1450.00 — A single monthly charge is all the contract provides for. notchwork-saas-contract.pdf
- 2.[invoices#32] invoice_number = NWK-2025-08 — The first August invoice, which already covers the month. NWK-2025-08.pdf
- 3.[invoices#33] issue_date = 2025-08-18 — The second August invoice, issued mid-month. NWK-2025-08B.pdf
- 4.[invoices#33] approved_by = Marcus Webb — The duplicate month was approved as issued. NWK-2025-08B.pdf
- 5.[bank_transactions#196] amount = -1450.00 — The second invoice was paid in full.
- 6.[ledger_entries#923] debit = 1450.00 — Software Subscriptions expensed twice for August.
Gaps
- duplicate_invoice_monthVendor 3 issued two invoices covering August 2025 under a contract that provides for one monthly charge.
Disposition
Open — still with the accountant when this binder was printed.
Proposed adjusting entry
| Account | Debit | Credit |
|---|---|---|
| Accounts payable | $1,450.00 | — |
| Operating expenses | — | $1,450.00 |
Reverse the second invoice recorded for a month already billed.
Amount is the second invoice for the service month.
Basis: [invoices#33]
Dodo payout · po_202510_vy70ms
- Procedure
- Not recorded
- Assertion tested
- Not recorded
Exchange
- Auditorturn 1
The October payout came to $3,558.80 [dodo_transactions#340], and October is the only month where the clearing account does not net to zero. Explain the difference.
- Accountantturn 2
The payout is right and the books are wrong. Payments less refunds less fees for October come to $3,657.80, but Dodo paid out $3,558.80 [dodo_transactions#340] and the bank received exactly that [bank_transactions#241]. The $99.00 difference is a dispute Dodo records as lost [dodo_transactions#317], raised against a payment taken earlier in the month [dodo_transactions#317]. No ledger row carries that dispute, so clearing was reduced only by the payout received [ledger_entries#1254] and is overstated by the disputed amount.
Evidence cited (5)
- 1.[dodo_transactions#340] amount = 3558.80 — The payout Dodo actually made for October.
- 2.[bank_transactions#241] amount = 3558.80 — The bank confirms the payout amount, so the shortfall is not a timing difference.
- 3.[dodo_transactions#317] reference = dsp_7iu96cuq03kr for pay_8y4ow7qxour0qj (lost) — The lost dispute that accounts for the entire difference.
- 4.[dodo_transactions#317] amount = 99.00 — The dispute amount equals the payout shortfall to the cent.
- 5.[ledger_entries#1254] credit = 3558.80 — Dodo Clearing cleared only by the received payout, leaving the dispute stranded.
Gaps
- payout_mismatchExpected payout of $3,657.80 versus actual $3,558.80 for October 2025.
- missing_ledger_entryNo ledger row carries source_type dodo and source_id 317, the lost dispute.
Disposition
Open — still with the accountant when this binder was printed.
Proposed adjusting entry
| Account | Debit | Credit |
|---|---|---|
| Accounts receivable — Dodo Payments | $3,558.80 | — |
| Payment processing fees | — | $3,558.80 |
Record the unexplained difference between the Dodo payout and payments less refunds less fees.
Amount is the sampled transaction, taken from the sampled row because the citations this rule needs were not on the bundle.
Basis: [dodo_transactions#340]
Stratus Compute Inc. · STR-2025-09
- Procedure
- Not recorded
- Assertion tested
- Not recorded
Exchange
- Auditorturn 1
STR-2025-09 is an $18,500.00 invoice [invoices#9] and it was settled on 2025-09-20 [bank_transactions#209]. Who approved it?
- Accountantturn 2
Nobody did. The approval field on the invoice is empty [invoices#9], and this is the only invoice above the $10,000 threshold in the year without an approver [invoices#9]. The amount is at the contract rate [contracts#1], so the pricing is not in question. The expense was recognised anyway, debiting Cloud Infrastructure [ledger_entries#979] against Accounts Payable [ledger_entries#980], and the bank settled it in full [bank_transactions#209]. I cannot produce an approval that does not exist.
Evidence cited (6)
- 1.[invoices#9] approved_by = (empty) — The approval field is empty on an invoice above the approval threshold. STR-2025-09.pdf
- 2.[invoices#9] amount = 18500.00 — The amount is above the $10,000 approval threshold. STR-2025-09.pdf
- 3.[contracts#1] monthly_rate = 18500.00 — The amount is at the contract rate, so only the approval is missing. stratus-compute-contract.pdf
- 4.[bank_transactions#209] amount = -18500.00 — The unapproved invoice was paid in full.
- 5.[ledger_entries#979] debit = 18500.00 — The expense was recognised despite the missing approval.
- 6.[ledger_entries#980] credit = 18500.00 — Accounts Payable credited for the unapproved invoice.
Gaps
- missing_approvalInvoice 9 is above the approval threshold and carries no approver.
Disposition
Conceded — recorded as a finding by an earlier run.
Proposed adjusting entry
| Account | Debit | Credit |
|---|---|---|
| Unsupported expenditures — under review | $18,500.00 | — |
| Operating expenses | — | $18,500.00 |
Reclassify the unapproved disbursement until approval evidence is produced.
Amount is the unapproved invoice.
Basis: [invoices#9]
Meridian Design Collective · MDC-2025-12
- Procedure
- Not recorded
- Assertion tested
- Not recorded
Exchange
- Auditorturn 1
MDC-2025-12 is dated 2025-12-01 [invoices#49], after the Meridian contract ends [contracts#4], and it was paid on 2025-12-15 [bank_transactions#287]. On what authority?
- Accountantturn 2
None that I can cite. The contract runs to 2025-11-30 [contracts#4] and there is no renewal on file. The invoice is issued 2025-12-01 for $6,800.00 [invoices#49], one day outside the term, and it was approved by Priya Natarajan [invoices#49]. It was paid in full on 2025-12-15 [bank_transactions#287] and booked to Contractors [ledger_entries#1423] against Accounts Payable [ledger_entries#1424]. The work may well have happened; the billing has no agreement behind it.
Evidence cited (7)
- 1.[contracts#4] effective_to = 2025-11-30 — The contract term ends the day before the invoice was issued. meridian-design-collective-contract.pdf
- 2.[invoices#49] issue_date = 2025-12-01 — The invoice date falls outside the contract term. MDC-2025-12.pdf
- 3.[invoices#49] amount = 6800.00 — The amount billed outside the term. MDC-2025-12.pdf
- 4.[invoices#49] approved_by = Priya Natarajan — The out-of-term invoice was approved. MDC-2025-12.pdf
- 5.[bank_transactions#287] amount = -6800.00 — The out-of-term invoice was also paid in full.
- 6.[ledger_entries#1423] debit = 6800.00 — Contractors expensed for a period the contract does not cover.
- 7.[ledger_entries#1424] credit = 6800.00 — Accounts Payable credited for the out-of-term invoice.
Gaps
- outside_contract_termInvoice 49 is issued after contract 4's effective_to date with no renewal on file.
Disposition
Conceded — recorded as a finding by an earlier run.
Proposed adjusting entry
| Account | Debit | Credit |
|---|---|---|
| Prepaid expenses | $6,800.00 | — |
| Operating expenses | — | $6,800.00 |
Defer the charge billed outside the contract's effective dates.
Amount is the invoice dated outside the contract term.
Basis: [invoices#49]
Stratus Compute Inc. · STR-2025-01
- Procedure
- Not recorded
- Assertion tested
- Not recorded
Exchange
- Auditorturn 1
STR-2025-01 is the largest single expense in January 2025 [invoices#1]. Show contract authority, approval, and settlement.
- Accountantturn 2
All three are on file. The contract sets the monthly rate at $18,500.00 from 2025-01-01 through 2025-12-31 [contracts#1], and the invoice bills exactly that on its issue date [invoices#1]. Priya Natarajan approved it [invoices#1]. The bank settled reference STR-2025-01 once, on 2025-01-24, for the same amount [bank_transactions#20]. The journal balances, with the expense debited on issue [ledger_entries#1] and Cash credited on settlement [ledger_entries#86].
Evidence cited (7)
- 1.[contracts#1] monthly_rate = 18500.00 — The contracted rate the invoice bills. stratus-compute-contract.pdf
- 2.[contracts#1] effective_to = 2025-12-31 — The invoice date falls inside the contract term. stratus-compute-contract.pdf
- 3.[invoices#1] amount = 18500.00 — The billed amount equals the contract rate exactly. STR-2025-01.pdf
- 4.[invoices#1] approved_by = Priya Natarajan — The invoice carries a named approver. STR-2025-01.pdf
- 5.[bank_transactions#20] amount = -18500.00 — A single settlement for the full invoice amount.
- 6.[ledger_entries#1] debit = 18500.00 — Expense recognised on the invoice date.
- 7.[ledger_entries#86] credit = 18500.00 — Cash credited once on settlement.
Disposition
Defended — the auditor's follow-up policy accepted the evidence; no controller ruling was required.
Harbor Point Properties LLC · HPP-2025-08
- Procedure
- Not recorded
- Assertion tested
- Not recorded
Exchange
- Auditorturn 1
August rent came to $9,200.00 [invoices#20]. Prove it was owed and that it was paid once.
- Accountantturn 2
The contract fixes rent at $9,200.00 a month through 2025-12-31 [contracts#2], and HPP-2025-08 bills exactly that on 2025-08-01 [invoices#20]. Elena Fischer approved it [invoices#20]. The bank settled it once, on 2025-08-10 [bank_transactions#175]. Rent was debited on issue [ledger_entries#837] and Cash credited on settlement [ledger_entries#886], the same amount on both sides.
Evidence cited (6)
- 1.[contracts#2] monthly_rate = 9200.00 — The contracted rent amount. harbor-point-properties-contract.pdf
- 2.[invoices#20] amount = 9200.00 — The invoice bills the contract rate. HPP-2025-08.pdf
- 3.[invoices#20] approved_by = Elena Fischer — The invoice carries a named approver. HPP-2025-08.pdf
- 4.[bank_transactions#175] amount = -9200.00 — One settlement for the full amount.
- 5.[ledger_entries#837] debit = 9200.00 — Rent expense recognised on the invoice date.
- 6.[ledger_entries#886] credit = 9200.00 — Cash credited on settlement.
Disposition
Defended — the auditor's follow-up policy accepted the evidence; no controller ruling was required.
Meridian Design Collective · MDC-2025-04
- Procedure
- Not recorded
- Assertion tested
- Not recorded
Exchange
- Auditorturn 1
The Meridian contract expires before the year ends [contracts#4]. Confirm MDC-2025-04 is inside the term, approved, and paid once [invoices#41].
- Accountantturn 2
It is all three. The contract runs 2025-01-01 to 2025-11-30 [contracts#4], so an issue date of 2025-04-01 is inside the term [invoices#41]. The $6,800.00 billed equals the contract monthly rate [contracts#4]. Priya Natarajan approved it [invoices#41]. The bank settled it once, on 2025-04-18 [bank_transactions#91], and the debit and credit match [ledger_entries#351, #412].
Evidence cited (7)
- 1.[contracts#4] effective_from = 2025-01-01 — The contract is in force before the invoice date. meridian-design-collective-contract.pdf
- 2.[contracts#4] effective_to = 2025-11-30 — The contract is still in force on the invoice date. meridian-design-collective-contract.pdf
- 3.[invoices#41] amount = 6800.00 — The invoice bills the contract monthly rate. MDC-2025-04.pdf
- 4.[invoices#41] approved_by = Priya Natarajan — The invoice carries a named approver. MDC-2025-04.pdf
- 5.[bank_transactions#91] amount = -6800.00 — A single settlement for the full amount.
- 6.[ledger_entries#351] debit = 6800.00 — Contractors expense recognised on the invoice date.
- 7.[ledger_entries#412] credit = 6800.00 — Cash credited once on settlement.
Disposition
Defended — the auditor's follow-up policy accepted the evidence; no controller ruling was required.
Stratus Compute Inc. · STR-2025-01
- Procedure
- Not recorded
- Assertion tested
- Not recorded
Exchange
- Auditorturn 1
A payment of $18,500.00 left the account on 2025-01-24 [bank_transactions#20]. Tie it to a document.
- Accountantturn 2
The reference on the payment is the invoice number it settles [bank_transactions#20]. That invoice is STR-2025-01 [invoices#1], for the same $18,500.00 [invoices#1], approved by Priya Natarajan [invoices#1]. The payment clears the payable rather than creating an expense, so Accounts Payable is debited [ledger_entries#85] and Cash credited [ledger_entries#86] on the same date.
Evidence cited (5)
- 1.[bank_transactions#20] reference = STR-2025-01 — The payment reference is the invoice number it settles.
- 2.[invoices#1] invoice_number = STR-2025-01 — The invoice named by the payment reference. STR-2025-01.pdf
- 3.[invoices#1] amount = 18500.00 — The invoice amount equals the payment exactly. STR-2025-01.pdf
- 4.[ledger_entries#85] debit = 18500.00 — Accounts Payable cleared by the payment.
- 5.[ledger_entries#86] credit = 18500.00 — Cash credited once for the payment.
Disposition
Defended — the auditor's follow-up policy accepted the evidence; no controller ruling was required.
Dodo payout · po_202503_md1m5s
- Procedure
- Not recorded
- Assertion tested
- Not recorded
Exchange
- Auditorturn 1
Reconcile the March payout to the bank and to the clearing account [dodo_transactions#81].
- Accountantturn 2
March reconciles exactly. Dodo paid out $3,051.84 on 2025-03-31 [dodo_transactions#81] and the bank received the same amount that day [bank_transactions#75]. The month's processing fees of $144.16 are booked against clearing [ledger_entries#343]. The payout then clears the balance, with Cash debited [ledger_entries#335] and Dodo Clearing credited [ledger_entries#336] for the same figure.
Evidence cited (5)
- 1.[dodo_transactions#81] amount = 3051.84 — The payout amount Dodo reports.
- 2.[bank_transactions#75] amount = 3051.84 — The bank received the payout amount unchanged.
- 3.[ledger_entries#343] debit = 144.16 — Processing fees for the month booked against clearing.
- 4.[ledger_entries#335] debit = 3051.84 — Cash debited for the payout.
- 5.[ledger_entries#336] credit = 3051.84 — Dodo Clearing credited so the month nets to zero.
Disposition
Defended — the auditor's follow-up policy accepted the evidence; no controller ruling was required.
Fix list
Every exception the controller ruled on, largest first, with the remedy and the entry that corrects it. Gaps the controller has not ruled on are listed separately: they are outstanding work, not findings.
Exceptions (0)
The controller has not recorded an exception on this run.
Gaps awaiting a ruling (6)$45,624.00
| Ref | Item | Finding | Remedy | Amount |
|---|---|---|---|---|
| W-8 | Stratus Compute Inc. · STR-2025-09 invoice:9 | missing_approval Reclassify the unapproved disbursement until approval evidence is produced. | Not yet ruled | $18,500.00 |
| W-1 | Harbor Point Properties LLC · HPP-2025-03 invoice:15 | duplicate_payment Reverse the second settlement of this reference and set up the refund receivable. | Not yet ruled | $9,200.00 |
| W-3 | Kestrel Holdings Ltd · WIRE-20250912-4471 bank:202 | unknown_counterparty Park the payment in suspense until the counterparty is identified. | Not yet ruled | $7,850.00 |
| W-9 | Meridian Design Collective · MDC-2025-12 invoice:49 | outside_contract_term Defer the charge billed outside the contract's effective dates. | Not yet ruled | $6,800.00 |
| W-2 | Stratus Compute Inc. · STR-2025-05 invoice:5 | rate_mismatch Reverse the amount billed above the contracted monthly rate. | Not yet ruled | $2,775.00 |
| W-4 | Dodo refund · ref_nx3ulzfvg9d7 dodo:92 | missing_ledger_entry Post the journal entry for a transaction that never reached the ledger. | Not yet ruled | $499.00 |
Tickmark legend
- Vouched. Evidence agreed to the supporting document and the ledger.
- Resolved by memory. Closed by a ruling the controller made on this counterparty in an earlier run; the ruling is quoted and cited in the exchange.
- Gap. The accountant could not support the item; escalated to the controller.
- Exception. The controller recorded a finding; see the fix list.
- Open. Still with the accountant at the time this binder was printed.
Bracketed references such as [invoices#15] are table names and row ids in the books this run was drawn from. Documents are served from the same rows at /api/files.