Guide

When A2X, Bookkeep or Synder is working and exceptions remain

Short answer

Connectors are built to post summarized activity correctly, which they generally do well. Reconstructing a bundled deposit across several independent sources is a different operation, and that is where residual exceptions usually live.

This is not a criticism of connectors

If a connector produces a clean close for a client, that is the correct tool and nothing here applies. Standard connectors are often the right solution for standard workflows, and replacing working software is a bad use of a client's money.

The narrower question is what to do when the connector is configured correctly, posting is accurate, and a recurring exception population still survives every close.

Posting is not reconciling

The distinction matters. Posting means recording summarized activity into the ledger accurately. Reconciling means proving that a bank deposit is fully explained by the components behind it. A tool can be excellent at the first without addressing the second, and most connectors are scoped to the first.

Where residual exceptions concentrate

  • Joins between sources.A connector generally owns one relationship. Nothing owns the join when Shopify, a second gateway, a marketplace, wholesale invoicing and the bank all have to agree.
  • Cross-period adjustments.Refunds and disputes landing in different periods from their original sale.
  • Client-specific rulesthat standard configuration cannot express. This is a scope limit, not a defect.
  • Non-standard channelssuch as retail POS, subscriptions or B2B portals entering the same account structure.

How to tell whether it is worth addressing

Three questions, in order. Does the same exception pattern recur every close? Does resolving it follow a procedure you could write down? Does it consume meaningful staff time, particularly senior staff time?

Three yeses suggest a rule exists and is being executed by a person. Any no, and the honest answer is usually to leave it alone.

When standard software is enough

A handful of exceptions a month, resolved in minutes, with no pattern. Automating that costs more than it returns.

When custom automation may be justified

A recurring population, a repeatable procedure, meaningful time, and ideally several clients sharing the pattern so a core can be reused. The Fit Score weights exactly those factors.

MatchPass Labs is not affiliated with or endorsed by A2X, Bookkeep, Synder or any accounting platform mentioned here.

Published 8 September 2026 · Updated 19 September 2026

General educational information only. Not accounting, tax or legal advice. MatchPass Labs provides reconciliation engineering and is not an accounting firm.

Common questions

Common questions

Usually not. If the connector posts activity correctly, keep it. A custom reconciliation layer addresses only the residual exceptions and sits alongside existing software.
No. MatchPass Labs is not affiliated with or endorsed by any of these providers.

Wondering whether your case is worth automating?

The Fit Score gives a structured answer in a couple of minutes, runs in your browser, and will tell you to keep your current process if that is the right call.