MOXIE STUDIO / FREE SERVICE DEMONSTRATION / v0.1

Invoice Exception Review

Five fictional invoices. Five work-order records. A traceable review that keeps uncertain pairings uncertain.

Free worked demonstration, not an available paid service. Original AI-assisted fictional content. No real financial records, accounting assurance, payment approval or human testing.

The job this tests

For an owner or authorized invoice administrator already using spreadsheets: conflicting scope, missing completion and repeated references can leave exceptions without a clear next owner. This sample tests source-linked explanations plus reusable tracking, not automatic invoice approval.

One measurable future outcome: lower owner review time than their existing spreadsheet, with no unsupported pairings. No time saving, price acceptance or demand has been measured.

Worked review

Row locators count the header as row 1. Keep immutable source copies so references remain stable. Completion means documentation in this fictional batch, not independent verification. The supported positive control still has a duplicate peer warning.

CASE 01

SYN-I01

Linkage
Supported
Completion evidence
Not recorded
Duplicate review
No duplicate in supplied batch
Sources
synthetic-invoices.csv:row 2; synthetic-work-orders.csv:row 2 [SYN-R01]
Supporting evidence
Reference, vendor, site and service date agree. No completion note supplied
Conflict / missing evidence
Completion documentation absent.
Next action
Request completion evidence; do not infer completion from invoice.
Action owner
Work-order administrator

CASE 02

SYN-I02

Linkage
Reference supported; scope conflict
Completion evidence
Documented
Duplicate review
No duplicate in supplied batch
Sources
synthetic-invoices.csv:row 3; synthetic-work-orders.csv:row 3 [SYN-R02]
Supporting evidence
Reference, vendor, site and service date agree. Fictional completion note CN-02: inspection finished
Conflict / missing evidence
Invoice scope Replace pump / USD450.00; order scope Inspect pump / USD120.00.
Next action
Obtain authorized scope/amount clarification; preserve original rows.
Action owner
Work-order administrator

CASE 03

SYN-I03

Linkage
Ambiguous
Completion evidence
Unresolved linkage
Duplicate review
No duplicate in supplied batch
Sources
synthetic-invoices.csv:row 4; synthetic-work-orders.csv:row 5 [SYN-R04]; synthetic-work-orders.csv:row 6 [SYN-R05]
Supporting evidence
Both candidate rows share reference, vendor, scope, date, amount and currency.
Conflict / missing evidence
Invoice site is not specified; Site-D and Site-E differ. Completion cannot be transferred between candidates.
Next action
Obtain site-specific reference from authorized administrator; do not select either candidate.
Action owner
Invoice administrator

CASE 04

SYN-I04

Linkage
Supported
Completion evidence
Documented
Duplicate review
Possible duplicate
Sources
synthetic-invoices.csv:row 5; synthetic-work-orders.csv:row 4 [SYN-R03]
Supporting evidence
Reference, vendor, site and service date agree. Fictional completion note CN-03: filter replaced
Conflict / missing evidence
No scope or amount conflict in supplied records. Identical supplied service fields also appear on SYN-I05; a duplicate is possible, not proven.
Next action
Retain supported pairing; investigate duplicate peer before closing review.
Action owner
Invoice administrator

CASE 05

SYN-I05

Linkage
Supported
Completion evidence
Documented
Duplicate review
Possible duplicate
Sources
synthetic-invoices.csv:row 6; synthetic-work-orders.csv:row 4 [SYN-R03]
Supporting evidence
Reference, vendor, site and service date agree. Fictional completion note CN-03: filter replaced
Conflict / missing evidence
No scope or amount conflict in supplied records. Identical supplied service fields also appear on SYN-I04; a duplicate is possible, not proven.
Next action
Retain supported pairing; investigate duplicate peer before closing review.
Action owner
Invoice administrator

Use the tracker

  1. Keep original source CSVs unchanged. Import comma-delimited UTF-8 CSV with identifiers as text.
  2. Copy the tracker. Filter by owner or review_state. Keep linkage, completion and duplicate statuses separate.
  3. Record follow-up evidence in resolution_note with a new source locator. Change review_state to Awaiting evidence or Reviewed only when justified. Do not overwrite conflicting evidence.
  4. Export as UTF-8 CSV, reopen it and check identifiers, quoted notes and source locators. This package exercises a quoted-note round trip; native Excel/LibreOffice interaction has not been tested.

The reusable tracker is prefilled with these five synthetic cases. Duplicate it and replace fictional rows for a separately authorized future batch. No formulas or macros are included. Do not paste untrusted formula-leading cells into a spreadsheet.

Scope and limits

Dry run only: at most five invoices and five work-order records in one currency, using supplied structured fields. No OCR, tax checking, ledger reconciliation, integrations, record chasing or client-system access. Similar fields do not prove that two invoices are duplicates. A completion note does not establish payment entitlement.

Customer record intake and paid orders are closed. Before accepting records, verify an authorized handling and deletion route and require consistent pseudonyms; remove names, addresses, banking, tax identifiers and hidden metadata. Keep needed references consistent. Stop for unsafe redaction, unsupported matches, required account access or no incremental usefulness.

Evaluation window: one qualified opt-in comparison or 14 days after this verified publication, whichever comes first. No customer-record comparison begins before the handling route is ready. Record baseline and assisted owner review time, pairing correctness, Moxie handling time, actual exposure and enquiries separately. Iterate once only on an observed weakness; no qualified exposure means a channel decision, not disproved demand. No automatic follow-ups. A possible $49 future price is unvalidated; no paid commitment before seller, payment and fulfillment checks.

Would this clarify your exception queue?

For owners and authorized invoice administrators: tell us your role, usual spreadsheet workaround, and which fictional decision is useful or unclear. A possible $49 USD future sprint is an unvalidated price question, not an order or booking.

To explore a future comparison, explicitly say whether you would opt in after a safe handling route is established. The intended measure is owner review time versus your usual method, with no unsupported pairings. No benefit has been measured.

Send only a general workflow description or feedback on these fictional cases. Do not attach invoices, customer records, names, addresses, banking or tax information. Customer-record intake and paid orders remain closed. Nothing is submitted from this page.

Email: moxie@staticterminal.com
Subject: Invoice exception demo feedback

Optional: open your email app

Email is used to answer your enquiry, not to subscribe you to a newsletter. No automatic campaign follow-ups. No analytics scripts; our host may retain standard request logs.

Return to the studio catalogue