Synthetic Industry

Troubleshooting guide · updated 2026-10-11

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.

Identify which of three different things is missing

If a column is absent from the trigger sample, inspect the header and sample before editing Xero. If the trigger contains both products but the action exposes only one product's values, inspect the transformation and action mapping. If the action receives both products but the draft invoice has one merged description or the wrong amount, inspect how those values are represented as invoice lines. A successful Zap run does not distinguish these cases.

  • Record whether your source is one row with several product columns, several rows for one invoice, or already structured line items.
  • Write down the number of invoices and lines you expect before changing the Zap.
  • Do not assume a comma-separated description is two invoice lines, or that looping over two products should create two invoices.

Use a small example that makes a collapsed line obvious

This is an invented test specification, not a tested integration or accounting advice. In an authorised demo context, use product A with quantity 2 and unit amount 10, and product B with quantity 1 and unit amount 7. With tax excluded solely for this synthetic arithmetic example, the expected line amounts are 20 and 7 and the total is 27. The result should be one unsent draft with two separate lines, not one line worth 27 and not two invoices. Your finance owner specifies actual currency, account and tax rules separately.

  • Use two clearly different descriptions and quantities so misaligned positions are visible.
  • Compare each description with its own quantity, unit amount and resulting line amount; a correct grand total can conceal swapped lines.
  • Use the finance owner's authorised demo or disposable draft route. Test buttons can create records; do not connect this example to real customers.

Keep the line-item attributes aligned

This checklist specifies the business result; it does not establish which current Zapier action or formatter supports your source layout. The authorised implementer must confirm that separately before agreeing the repair. Inspect the proposed output before the invoice step: each description must remain paired with the intended quantity, amount and agreed accounting attributes. A correct total alone cannot show whether two products retained their separate identities.

  • A blank second description paired with a second amount should be caught rather than silently omitted.
  • Variable-length product groups, several source rows per invoice or grouping several customers are larger transformation problems; do not squeeze them into a five-field remapping quote.
  • Do not bulk replay runs to test the transformation. Inspect destination state first and agree how repeated source references are handled.

What a useful enquiry contains

For the existing Sheets-to-Xero mapping service, send synthetic headers, whether one row already triggers the Zap, expected invoice and line counts, and the point where the second product disappears. State who owns the Xero organisation, can approve a disposable draft test and can decide on the posted price. We confirm whether the bounded field-mapping offer fits; variable line-item transformation needs a separate scope, not a hidden extension of that price.

  • Do not send customer names, bank details, invoice exports, credentials or access invitations initially.
  • Keep the expected and actual line counts in the enquiry even if the Zap shows success.
  • After agreement, acceptance also needs the agreed repeated-input and missing-field checks; no live invoice is sent by this diagnostic guide.

Sources and limits