# accounts-payable: context > Larkspur Garden Co. is a fictional company. Every vendor, invoice and person in this record is > generated from a seed; none of it describes a real organization. ## What this system is Accounts payable at Larkspur Garden Co., a fictional chain of nine garden centres, one greenhouse and a small delivery fleet. Every supplier invoice lands here: nursery stock, irrigation parts, store supplies, truck parts, cleaning and IT services, and the occasional design contract. The desk decides, invoice by invoice, whether to pay it, hold it, or send it to a person. If it stopped, growers stop shipping within a fortnight, which in spring means empty benches in every store. ## How it runs Invoices arrive by email and post, are keyed against the purchase order and the store's receiving record, and are paid in two runs a week. One AP lead and two clerks work the desk. The ERP holds the vendor master, purchase orders and receiving; this record holds the judgment about them. ## What must never be assumed - The same amount from the same vendor inside two weeks is not always a duplicate. Northgate cleans the stores and the greenhouse every two weeks for the same fee, on one PO. - A vendor asking to change bank details is the most common fraud attempt this desk sees. The callback goes to a number already on file, never to one on the invoice or in the email. - Spring is 40% of the year's nursery-stock invoices in eight weeks. The queue is not a backlog problem in April; it is the season. ## Who owns it on the business side Priya, Controller. The Controller says what correct means for a payment; the AP lead (Dana, AP lead) keeps this record and signs what the machine may not decide alone. ## What not to touch - `thresholds.yaml`: what the machine may do alone. Every change is a reviewed diff the Controller signs. - The vendor-change rule. No confidence score moves money to a changed account.