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 1–40 of 44 in this first collection.
One-off outcome
Stop a retried automation from creating a second invoice in Xero or QuickBooks Online
Replaying, retrying or double-running one named invoice automation leaves exactly one invoice per source order in a test accounting file, and an unknown outcome is held for a person.
From £395 · untested offer price
One-off outcome
Map a supplier's category names onto your store categories, with no silent defaults
Every category value in a named supplier feed maps to exactly one of your store categories, or lands in a visible unmapped list. Nothing falls silently into a default category.
From £395 · untested offer price
One-off outcome
Make every Stripe payout match one bank deposit line in Xero or QuickBooks Online
Each automatic Stripe payout in an agreed test period becomes one ledger entry equal to the bank deposit, with its gross, fees and refunds explained and a clearing balance that returns to zero.
From £495 · untested offer price
One-off outcome
Make a customer sync reuse the right Xero contact instead of creating near-duplicates
Replaying a synthetic customer list through one named sync creates each customer once in a Xero demo organisation, and a changed email or name updates the same contact.
From £345 · untested offer price
One-off outcome
Read every item in a supplier XML feed, and reject a broken file cleanly
A named supplier XML sample imports every well-formed item, with namespaces, CDATA and escapes read correctly; a broken copy is rejected with its line and column and changes nothing.
£295 · untested offer price
One-off outcome
Send every mapped Google Sheets invoice field to Xero
One disposable row with the agreed columns makes one draft Xero invoice containing every agreed line item and amount.
£145 · untested offer price
Buyer collection
For a finance manager: make an invoice integration complete and safe to repeat
Define authoritative fields, duplicate rules and reconciliation before repairing a spreadsheet-to-accounting automation.
Troubleshooting guide
A Zap runs, but fields are missing: trace the value from trigger to destination
Inspect one synthetic record through each step and separate missing input, transformation, permissions and destination validation.
Troubleshooting guide
One Sheets row becomes one Xero invoice line: check the line-item shape
Distinguish missing spreadsheet headers from multiple products mapped into one invoice line, using a disposable two-product acceptance case.
Free tool
Workflow time-value calculator: show the assumptions behind automation payback
Use your own time, volume, cost and running-cost inputs to calculate simple monthly value and payback; not a quote or guaranteed saving.
Platform
Zapier automations: what repeats, what stops and who is told
The documented behaviours behind duplicate records, switched-off Zaps, late alerts and scheduled runs, and which outcome fits each problem.
Inspectable example
Synthetic XML feed cases: five first errors a parser reports and one well-formed file that loses fields
Invented XML snippets with the first error a standard parser reports for each, plus a well-formed namespaced item with CDATA that a text-matching importer misreads.
Troubleshooting guide
Supplier categories end up in Uncategorised: use a mapping table with an unmapped list, not loose matching
How to map a supplier's category names to your store categories with one reviewed row per value, an explicit unmapped state, exact matching and a report of new or changed values.
Platform
CSV supplier files: find the first failing layer before changing the importer
For distributors and merchants who import product, stock and price data from CSV: a map of the layers a file passes through, where each fault shows up and which guide or job fits.
Platform
XML product feeds: well-formed first, then namespaces, then meaning
For distributors and merchants who receive or send product data as XML: why a broken file stops everything, where namespaces and escaping cause quiet loss, and which guide or job fits.
Buyer collection
For an operations manager: make supplier files arrive complete, readable and only once
A page for the person who owns how supplier files are fetched, decoded and imported: what to document, how to describe a failure and which small fixed job or standing check fits.
Inspectable example
Synthetic Stripe payout: five charges, two refunds, one deposit and a clearing balance that returns to zero
A worked, invented payout shows how gross charges, fees and refunds add up to the single bank deposit and what ledger entries make the bank line match.
Inspectable example
Synthetic foreign-currency check: the same 100.00 USD order with Xero-style and QuickBooks-style rates
Invented arithmetic shows how a copied, inverted or default rate changes the base total, and how treating minor units as whole units shrinks a yen amount a hundredfold.
Platform
Xero integrations: identity, limits, accounts and currency decide whether a sync can be trusted
What Xero documents for integration builders (contacts, invoice numbers, idempotency, paging, limits, accounts, lock dates, demo company) and which failures map to which guide or outcome.
Buyer collection
For a bookkeeper: make payment-processor activity reconcile to the ledger without rebuilding it every month
Questions, evidence and decisions for a bookkeeper who inherits a processor-to-ledger integration that never quite agrees with the bank.
Buyer collection
For an operations lead: know when a finance sync has stopped, duplicated work or dropped orders
Three counts, three owners and four questions that tell an operations lead whether a sync into the accounting system can be trusted this month.
Collection
Processor to ledger to bank: diagnose a month that does not reconcile, in this order
An ordered process map: confirm scope, payout type, payout entries, refunds and fees, duplicates, timing and report completeness before asking anyone to change an integration.
Collection
A finance sync that cannot be trusted: check these in order before re-running anything
An ordered process map for a broken invoice sync: connection, completeness, accounts, contact identity, retries and duplicates, updates and currency, then re-count.
Free tool
Invoice rounding bench: compare per-line and total rounding, half-up and half-even
Enter invoice lines and see net, tax and gross under four rounding rules side by side, in exact whole-number minor units, with the difference between summing lines and rounding the total. Not tax or accounting advice.
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 USD 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.