Every supplier bill on the right job: attribution with a review queue

The bill attribution scenario, about fifty-five modules on a schedule of a few minutes, matches each supplier bill to its project by purchase order, job number and vendor rules. Nested routers carry each bill down four main branches, iterators and aggregators handle bills with many lines, and the match is written to both systems, so the job board and the accounts agree. Error routes keep one bill from stopping the rest.

Once a day a scenario signs in to the supplier's portal API, iterates the company's supplier accounts and fetches the last thirty-five days of invoices. For each it finds the matching monday row with one GraphQL query that also returns the files already attached, and downloads a PDF only where none is attached yet. A failed download or upload is logged to a data store and the run carries on.

A purchase-order name is often a nickname for the job. The linking scenario reads invoices that have a purchase order but no project and no triage decision, and looks each one up in an alias map, using only entries that point to one fixed project. Exactly one match links the invoice. Anything else is flagged for review, which also takes it out of future runs, so an uncertain invoice is neither reprocessed nor quietly linked.

A purchase order that can't be parsed is skipped rather than guessed at. The design is deliberately conservative: an invoice the rules are unsure of costs a person a minute, while one linked to the wrong job costs an investigation.