Find the outcome you need.
Start with a symptom, a platform or the thing you want working.
With JavaScript, search filters the whole collection in your browser. Without it, use the linked pages and section navigation below; query filters need JavaScript.
Showing entries 161–192 of 192 in this first collection.
Buyer collection
For a bookkeeper: check supplier statements and payment runs before the money moves
Check statements against the ledger by closing balance and reference, and put a second pair of eyes on every payment run for duplicates and changed bank details.
Buyer collection
For an office manager: get the accounts mailbox sorted and the receipts matched to the card statement
Decide where each kind of mail should go, measure the misroutes that matter, and pair receipts to card lines so missing ones show up as two lists.
Buyer collection
For a finance manager: draft the month-end variance commentary with every figure traced, and know where AI tools send your data
Trace each variance against budget or last month to the ledger lines, ask for the reason from a named person, and write down what each AI tool does with the data you put in.
Buyer collection
For sales admin: turn customers' parts-list requests into quote drafts priced only from your list
Match each requested line to a catalogue code, take the price only from the approved list, flag look-alike codes and units, and let a person send the quote.
Collection
Finance admin checks with AI, in order: start with a file and no access, end with a monthly service
An ordered path through the finance-admin jobs: files only first, then document reading with tie-outs, checks before money moves, drafts for a person, workflows in your own account, then monthly care.
Troubleshooting guide
AI document reading: why a high field accuracy still leaves many documents with an error
A field rate is not a document rate. Count documents, state the sample size and pass mark, and see what a pass actually shows before you rely on a reading tool.
Troubleshooting guide
Checking a supplier statement against your ledger by hand: six kinds of difference
Start with the closing balance, match each line by reference, and classify every difference as missing, extra, amount, date, reference or an unapplied credit.
Troubleshooting guide
Hostile text in invoices, emails and receipts: what prompt injection means for finance automation
Any document an automated reader opens can carry instructions. Limit what the reader may do, check its output with code, and test with planted hostile documents, run more than once.
Troubleshooting guide
Before you pay a batch: duplicates, changed bank details and why the builder should not be the only checker
Duplicates survive an exact-match check when the number is reformatted, and changed bank details look like any other row. Add a second checker, a call-back and a list of things noticed.
Troubleshooting guide
Overdue invoice reminders to business customers: interest, fixed costs and who must not be chased
GOV.UK sets optional interest and fixed recovery costs for late business payments. Build a do-not-chase list before drafting, and have a person read every reminder.
Collection
Revenue operations: eight checks in order, before anything is merged or sent
An ordered path through lead flow, junk leads, CRM data, stale deals, email sending, reports, enquiries and quotes, with the test for each and the job that fits.
Buyer collection
For a marketer: find the pages losing traffic, link your pages, and hear when ad spend jumps
Search Console analysis with the queries behind each fall, internal links from a list you tick, briefs for a human writer and read-only alerts on ad spend.
Inspectable example
Synthetic invoice reconciliation: identical net lines, two different tax totals
Three invented small-value lines show how line-level and invoice-level tax rounding can disagree even when net values and line counts match.
Inspectable example
Synthetic invoice retry matrix: source operation, attempt and target draft are different IDs
Concrete made-up references specify when a retry retains one target draft and when changed contents, a second organisation or multiple matches need a separate decision.
Collection
Invoice integration review: verify shape, representation, tax basis and repeat safety
An ordered review worksheet helps a finance owner stop at the first broken contract before requesting a bounded existing mapping repair.
Troubleshooting guide
Invoice values look right in Sheets but arrive as currency text or a date number
Separate a spreadsheet's displayed currency and date from the values a connector reads, then agree the destination types before repairing a mapping.
Troubleshooting guide
An invoice integration adds tax twice: agree whether each amount is net or gross
Name the tax basis of each mapped line and the approved tax treatment before mistaking a populated amount field for a correct invoice.
Troubleshooting guide
Invoice creation timed out: reconcile the unknown result before retrying
Distinguish a confirmed rejected creation from a lost response after a possible write, and define zero, one and conflicting-match dispositions before a replay.
Inspectable example
Synthetic supplier-key matrix: zeros, long codes, reused SKUs and an unmapped item
Four invented product mappings expose numeric coercion and cross-supplier collisions; an unknown key stays unassigned instead of becoming a guessed product.
Inspectable example
Synthetic supplier-update contract: blank price, absent field and missing product
A worked decision matrix separates a field omitted from a partial update from a product absent from a complete snapshot, with explicit hold and no-change results.
Inspectable example
Worked pack-price example: why 36 items cost 59.97, not the rounded display total
An invented US$19.99 pack of 12 distinguishes the purchase basis from a rounded per-item comparison and shows exactly where a misleading total arises.
Inspectable example
Synthetic feed-disposition sequence: newer, late, repeated and conflicting updates
Starting at supplier version 41, a six-step expected-state sequence shows when a feed changes the accepted version and when the previous state must remain intact.
Troubleshooting guide
Supplier SKUs lose leading zeros: preserve the identifier before importing
Keep supplier identifiers textual and compare exact keys before a stock or price feed creates a second product or updates the wrong one.
Troubleshooting guide
Two suppliers use the same SKU: match the supplier and code together
Prevent one supplier's stock or price from landing on another supplier's item, and keep unapproved cross-supplier mappings out of an automatic update.
Troubleshooting guide
A supplier feed repeats one key with different prices: reject the conflict before updating
Distinguish an identical duplicate from conflicting rows and choose a documented disposition instead of allowing file order to decide a business value.
Troubleshooting guide
Blank supplier price clears a good value: distinguish unchanged, empty and explicit removal
Give missing fields and blank cells different update meanings before a partial supplier feed erases a price or silently substitutes zero.
Troubleshooting guide
An item disappears from a supplier feed: is it a full snapshot or just a delta?
Do not turn an omitted SKU into zero stock or discontinued status until the source defines completeness, coverage and deletion semantics.
Troubleshooting guide
Supplier quotes per pack, your app compares per item: make the units explicit
Keep pack size, stock units and price basis separate so an apparently cheaper supplier is not selected using incomparable values or rounded display prices.
Troubleshooting guide
Yesterday's supplier feed finishes last: keep older data from replacing a newer version
Compare source-issued versions at the publication boundary and distinguish a late old feed from an authorised correction to the current one.
Troubleshooting guide
Supplier adds a CSV column: reject header drift before fields shift into the wrong place
Validate the declared header and every row's shape before mapping a supplier stock or price update, rather than accepting a successfully parsed but misaligned record.
Buyer collection
For a distributor's operations owner: stop supplier-feed mistakes without a new inventory system
Name who approves product matching, units and feed exceptions, then request one testable local repair or one small review interaction in the application you already use.
Collection
Supplier stock and price import checks: choose the first failing boundary
A distributor-focused sequence from CSV shape through identity, field meaning, units and feed publication, linked to worked synthetic cases and narrowly eligible paid enquiries.