Invoice values look right in Sheets but arrive as currency text or a date number

A visible cell is only one representation

With invented data, a numeric 1234.50 may display with a currency symbol and grouping characters. A date can be displayed as calendar text while the underlying value is a serial number. Record the visible cell, the connector's captured value and type, and the action's required type separately. This is not the missing-header problem: the value exists but its representation may not fit the destination.

• Record spreadsheet locale, cell format and the intended invoice currency separately.
• Distinguish a formula such as =A1 from its evaluated result.
• Do not parse an ambiguous date such as 03/04/2026 by guessing its locale.

The API explains the distinction, not your Zap's controls

Google's API offers formatted, unformatted and formula representations. Its values.get method defaults to formatted output, and the date-time option has no effect in that mode. Sheets date serials count from December 30, 1899 and can contain a fractional day. These are documented API behaviours, not a claim that the current Zapier trigger exposes an option with the same name or uses a particular mode. Inspect the actual captured sample through the authorised operator; do not change a live connector based on an API recipe.

• The connector version and selected action must be verified separately.
• A currency symbol does not establish the currency code or an exchange rate.
• If conversion is necessary, agree the exact date and monetary input contract first.

A useful acceptance case changes the display, not the business meaning

Use invented amounts and an unambiguous invoice date on an authorised disposable route. Declare whether changing only cell presentation should leave the destination amount and date unchanged. Compare the mapped amount, date and currency after each agreed presentation variant. If a serial or formatted string is unsupported, require a visible exception rather than silent zero, today's date or a guessed conversion. These are proposed checks; no Sheet, connector or invoice was exercised for this draft.

• Inspect destination types and values, not just a screenshot that looks similar.
• Keep a missing-value case distinct from a wrong-type case.

DIY first, and preserve the £145 boundary

An authorised maintainer may resolve the issue by inspecting the trigger sample and correcting an existing mapping; Google documentation is free to read. The existing £145 Sheets-to-Xero offer concerns an already-working trigger, up to five named fields and one disposable draft. It is a contextual route, not a promise to build a new date parser, currency converter or variable line-item transformation at that price. Tax setup, historical corrections and sending invoices are excluded. Send invented cell values, displayed forms and expected destination types initially, not financial exports, code, credentials or invitations. The price is untested; work requires agreed scope and payment follows passing checks and sign-off.