Known and unknown vendors, missing data, amount differences, a duplicate, and one temporary posting failure.
AI-BUILT // DEVELOPER-DIRECTED
Built end-to-end with AI. A developer directed the requirements, information design, safeguards, refinement, and verification.
AI + AUTOMATION BUILD RECEIPT RPA orchestration
Invoice Exception
Control Room.
A fictional invoice queue demonstrates routine posting, exception routing, one controlled retry, and duplicate protection.
01 WHAT THE SYSTEM DOES
From invoice to a safe next step.
The automation handles routine matches and makes every exception visible instead of guessing.
Check duplicate, vendor, PO, and variance. Retry a temporary failure once.
Illustrative review load: 12 → 3 (−75%).
SYNTHETIC AUTOMATION // READY
Run the 12-invoice model
Press Start and follow one numbered invoice through the workflow. Open the records only when you want the detail.
Completed static result: 8 posted, 3 in human review, 1 quarantined.
01Queued0 invoices
02 // DETERMINISTIC RULESValidating0 invoices
03 // RULES PASSEDMatched0 invoices
04A // WARNINGRetrying0 invoices
05 // VERIFIEDPosted8 invoices
03B // HUMANHuman review3 invoices
03C // PROTECTEDQuarantined1 invoices
Posted8 / 12
Human review3 / 12
Retried1 / 12
Quarantined1 / 12
Inspect the 12 invoice recordsTABLE + DECISION PATH
DATASET // 12 FIXTURES
Invoice queue
Select a row to inspect its deterministic decision path.
| Invoice | Vendor | PO | Invoice amount | PO amount | Validation decision | Current state |
|---|---|---|---|---|---|---|
| Northstar SuppliesKNOWN VENDOR | PO-4101 | €1,280.00 | €1,280.00 | Validation passed | Posted | |
| Acme ServicesKNOWN VENDOR | PO-4102 | €2,460.00 | €2,424.00 | Validation passed | Posted | |
| Blue Oak LogisticsKNOWN VENDOR | PO-4103 | €780.00 | €780.00 | Validation passed | Posted | |
| Northstar SuppliesKNOWN VENDOR | PO-4104 | €3,150.00 | €3,120.00 | Validation passed | Posted | |
| Acme ServicesKNOWN VENDOR | PO-4105 | €940.00 | €940.00 | Validation passed | Posted | |
| Blue Oak LogisticsKNOWN VENDOR | PO-4106 | €1,765.00 | €1,750.00 | Validation passed | Posted | |
| Northstar SuppliesKNOWN VENDOR | PO-4107 | €520.00 | €520.00 | Validation passed | Posted | |
| Acme ServicesKNOWN VENDOR | PO-4108 | €2,290.00 | €2,290.00 | Matched; transient failure recovered | Posted | |
| Blue Oak LogisticsKNOWN VENDOR | Missing | €680.00 | — | Missing purchase order | Human review | |
| Northstar SuppliesKNOWN VENDOR | PO-4110 | €1,060.00 | €1,000.00 | Amount variance above 2% | Human review | |
| Unregistered VendorUNKNOWN VENDOR | PO-4111 | €840.00 | €840.00 | Unknown vendor | Human review | |
| Acme ServicesKNOWN VENDOR | PO-4112 | €1,550.00 | €1,550.00 | Duplicate detected | Quarantined |
Audit log45 deterministic events recorded.
Exact outcome values
| Outcome | Current value | Denominator | Relationship |
|---|---|---|---|
| Posted | 8 | 12 | Terminal outcome; includes retry success |
| Human review | 3 | 12 | Terminal outcome requiring human judgment |
| Retried | 1 | 12 | Posting path; overlaps with posted |
| Quarantined | 1 | 12 | Terminal duplicate-protection outcome |
Inspect exact rule order6 deterministic rules
| Priority | Rule | Condition | Result | Purpose |
|---|---|---|---|---|
| 01 | Duplicate protection | An invoice is already recorded as received. | quarantined | Stop processing and quarantine the duplicate before any posting attempt. |
| 02 | Vendor validation | The vendor is not present in the synthetic approved-vendor register. | human review | Route the invoice to a person instead of guessing vendor identity or payment details. |
| 03 | Purchase-order presence | No purchase-order number or comparable purchase-order amount is available. | human review | Ask a person to resolve the missing business reference. |
| 04 | Amount variance threshold | Absolute invoice-to-PO variance is greater than 2% of the PO amount. | human review | Values at or below 2% may continue; values above the threshold require human judgment. |
| 05 | Matched posting | The invoice passes duplicate, vendor, PO, and variance validation and posting succeeds. | direct post | Mark the invoice matched and post it once. |
| 06 | Controlled transient retry | A validated invoice encounters its configured transient posting failure. | retry success | Retry exactly once; the deterministic second posting attempt succeeds. |
AI BUILD RECEIPT // PROMPT STRATEGY
One thought. Several skilled prompts.
This result took several skilled prompt passes—not one magic instruction. The copy-ready prompt below carries the current source revision.
Starting thought for the invoice automation
Show how an AI-assisted invoice automation can validate routine work, expose exceptions, involve people where judgment is needed, and publish enough of the build method that another developer can learn from it.
Reduced to the durable product intent. Personal phrasing, hidden instructions, tool traces, and unrelated editor context are not published.
Each pass resolves a different kind of decision.
- 01Model the systemRules + outcomes
Define fictional invoice inputs, rule precedence, exception reasons, one bounded retry, and exact expected totals before designing the interface.
- 02Design the explanationUX + accessibility
Make input, decision, and output understandable at a glance. Keep deeper tables and evidence available without placing everything on screen at once.
- 03Build the interactionAstro + deterministic state
Connect Start, Pause, Reset, replay, diagram, rows, audit events, and metrics to one pure evaluator with static and reduced-motion fallbacks.
- 04Review and refineHuman direction + verification
Test the real page, fix replay so invoice 01 visibly returns, reduce visual density, verify the claims, and publish only the prompt material safe for visitors.
03 // CURRENT PAGE PROMPTReady-to-copy prompt for the current page
PROVENANCEGenerated at build time from current content and page sources. Revision a7939ae98b2e.
UPDATED
AUTO-SYNCED PAGE PROMPT // REVISION a7939ae98b2e. The revision changes when this case page, its control room, prompt receipt, layout, global styling, or schema-backed content changes.
Update the AI-built, developer-directed Invoice Exception Control Room at /work/invoice-exception-control-room/
CURRENT SOURCE REVISION: a7939ae98b2e
PURPOSE
Present a fictional sample of what an invoice automation could look like. Do not imply that the developer delivered or operated the underlying invoice system. Explain the model clearly enough for a potential client to understand the design judgment and the role AI played in creating the demonstration.
OPENING
State near the beginning that the page was created end-to-end with AI assistance while a developer directed the requirements, information design, safeguards, refinement, and verification. Keep the hero concise and label all results synthetic.
SYSTEM STORY
Explain three things before the interactive control room:
1. Input: 12 fictional invoices.
2. Decision: deterministic duplicate, vendor, purchase-order, variance, and retry rules.
3. Output: 8 posted, 3 sent to human review, and 1 quarantined.
INTERACTION
Provide Start, Pause, and Reset. Replay must visibly restore INV-2601 and the queued state before advancing. Keep the workflow map and live outcomes visible; place the invoice table, audit log, exact metrics, and full rule order in accessible disclosures. Preserve keyboard focus, semantic tables, no-JavaScript content, and reduced-motion behavior.
AI BUILD RECEIPT
Do not publish the user's original wording. Show a clearly labeled condensed starting thought, then four skilled prompt passes: system model, explanation design, interaction build, and human review/verification. Finish with this copy-ready prompt and its source revision. Exclude hidden instructions, private traces, company data, and unrelated editor content.
TRUTHFULNESS
State that this is not a client or production implementation. Use only the deterministic synthetic fixture. Preserve seven direct posts, one retry success, three human reviews, one quarantine, and the illustrative 12-to-3 manual-review comparison. Make no production, ROI, savings, speed, or accuracy claim.
IMPLEMENTATION
Use the existing Astro content collection, pure invoice evaluator, scoped components, native scripts, CSS, and inline SVG. Add no backend, live AI call, framework, or chart dependency. Verify tests, Astro diagnostics/build, replay, disclosures, prompt copying, responsive layouts, reduced motion, no-JavaScript rendering, and formatting before updating the public receipt.03 // BOUNDARIESWhat this demonstration does not prove
All invoice identifiers, vendors, purchase orders, and amounts are fictional and exist only to exercise deterministic workflow branches.
- This is a deterministic portfolio simulation, not a production deployment or benchmark.
- The vendor register, PO matching, duplicate flag, transient error, and second-attempt success are explicit fixtures rather than integrations with finance systems.
- The example does not estimate staff time, processing duration, financial return, accuracy, or employer outcomes.
- Real automation would require authentication, authorization, audit retention, integration contracts, operational monitoring, and organization-specific approval policy.
OPEN CHANNEL YOUR PROCESS, YOUR CONTROLS