Why a record didn't reach your accounting system

01 · Video

Feature walkthrough

02 · Why

Why do pushes fail?

The failures are almost always about mapping, not about the connection. Fixing them means changing the mapping and pushing again, not reconnecting.

03 · How

Find the reason

1. Go to Settings → Integrations and press Sync Status on the connection.
2. Find the run in Sync History — look for Failed or Partial.
3. Click the row to expand it.
4. Read the reason listed under Failed Records.

04 · Expected result

You get a list of the records that did not make it, with a reason for each.

05 · Troubleshooting

The line has nothing to book against

The message reads "…has neither an item nor an account — cannot build an expense line." The record’s line items are not mapped. Your accounting system will not accept a bill whose lines have nothing to book against.

Fix it in the mapping — either on the workflow’s Push step, or in the sync configuration — by mapping the line’s item or account field. See the line-items warning in Set up a sync configuration.

The record points at something that is not there

The message reads "unresolved_reference". The record points at something that does not exist in your accounting system yet — a supplier that was never synced, or a product code that does not match. Merchaint holds the record back rather than creating a half-formed one.

Fix it by syncing the thing it depends on first. Suppliers and items before invoices and bills.

06 · Notes

Failed records are identified by a long ID, not by invoice number

There is no link and nothing to search with. Match on the timestamp and record type instead, then look in the table for records still showing Local.

"Failed Records (2)" may be one record with two problems

The count is of reasons, not records.

Order matters

Push reference data first — suppliers, customers, items — then the documents that refer to them.

07 · FAQ

Common questions