Click New Bill Received — see the right decision for the state.

Three live scenarios. Each New Bill Received button below actually triggers the AI parse simulation and opens the correct modal for the state it's in — clean bill, bill with items, or a PO that already has items. No per-row sparkle clutter: provenance sits once, underneath the set AI populated.

A freshly-created Bill with nothing on it. The New Bill Received button parses the supplier invoice and auto-fills every line item, because there's nothing to conflict with. Modal shows the extracted items for a quick sanity-check before confirmation.

Same Bill page, different state — 3 items already entered by the tech. The New Bill Received button won't destructively overwrite. AI asks: merge the new items in, replace the existing ones, or just attach the file without parsing.

Golden rule: drop a document on a PO and it's always a supplier quote — never an invoice, never a new Bill. The drop updates the PO itself (pricing, authorised items, outstanding quantities). If you want to create a Bill from a supplier invoice, click New Bill Received on the Supplier Bills card below — that's an explicit action with a confirmation modal. PO drops default-parse (no modal); supplier-match check runs only when you choose to Parse. Use + Add File to attach without parsing.

Step C created the new Bill and linked it to the PO. This is where the user lands next — a side-by-side diff of the PO and the supplier invoice. AI does the line-item matching; the user confirms. Outstanding items (on the PO but not on this invoice) are flagged in red so they stay visible for the next supplier bill. Pattern borrowed from the real fi-supplier-po reconciliation view.

Real-world case: the user drags multiple PDFs at once, or attaches files over time. Having 3 files on a Bill is a valid state — not an error. Alfred asks the user to pick one to parse into line items; the others stay attached for reference (or to parse later if the right items are in a different file). Each attachment has its own Extract Line Items trigger. Parsing a second file from the same supplier opens a Merge / Replace / Cancel modal (like Case B). Parsing a file from a different supplier opens a stricter warning — a Bill can only reconcile against one supplier, so merging isn't offered; only Replace or Cancel.

A PO is created from a job's materials forecast, but no supplier quote has been accepted yet. Empty PO is a valid transient state. The drop-zone is the star; the Supplier Bills card is greyed out until authorised items exist. Drop a supplier quote to populate the authorised line items for the first time.

Mid-project reality: half the authorised items have been delivered and billed, half haven't. Alfred shows which items are fulfilled (green tick) and which are outstanding (red amber). A Partial chip in the header signals the PO isn't closed yet. Dropping a revised supplier quote here refreshes pricing / adds new line items — it never creates a Bill. Bills still come in through the New Bill Received button on the Supplier Bills card; each billed line ticks off the Rcvd column.

Real-world case: AI parsed 3 items from the supplier invoice, and the tech added 2 more items manually (disposable consumables not itemised on the PDF — e.g. rags, loose screws). Provenance lives at the group level only — the banner below the table reads "AI parsed 3 items from <file> · 2 items added manually" and the totals panel shows the split. No per-row sparkle. No per-row Source chip. The banner + split-totals is enough — per-row markers are just glitter.