How Tally settles transfers and card payments

Tally confirms matched pairs, rejects false matches, and chases card payments with no visible funding side.

How A Pair Is Judged

Money moving between the company's own accounts is one movement with two bank rows. Tally verifies those pairs and posts the confirmed ones, so most transfers and card payments never need your attention.

For each suggested pair, Tally builds a dossier and reaches one of three verdicts.

Confirmed — the evidence bar is met and the two legs are within three days of each other. Tally posts the pair on both sides.

Rejected — something contradicts a transfer reading despite the mirrored amounts. The rows go back to ordinary coding.

Needs a human eye — Tally names exactly what is missing:

competing candidates mirror the same amount in the window;
no corroborating signal — no pair history, payment wording, or statement match;
the date gap exceeds the three-day autonomous limit.

A pair settlement run showing confirmed, rejected, and review verdicts

A three-day gap is the automatic limit, not an accounting limit. A real transfer that took five days to land is still a real transfer — it just needs you to confirm it.

Pairs Waiting On The Bank

If either leg is inside the 72-hour pending hold, Tally skips the pair and picks it up once both sides settle. Nothing is lost. See Understand pending bank transactions.

Card Payments With No Funding Side

A card payment whose matching withdrawal never appears is the common real problem. Tally watches it for a waiting period first, because the other side is often just late.

Past that window, Tally checks whether any pending or funding candidate exists. If none does, it drafts a question to the company owner:

Your Evergreen Card shows a $1,250.40 payment on June 18 ("PAYMENT THANK YOU") — which account did that payment come from? We don't see a matching withdrawal in the accounts we have connected.

A drafted client question about a card payment with no funding side

Usually the answer is an account nobody connected yet. Connect it and the pair settles on the next run — see Connect a bank or credit card.

Confirm Or Clear A Pair Yourself

Anything Tally leaves is yours to decide:

In Bank Feeds, a suspected pair carries a transfer match badge with Record and Reject. A pair you rejected earlier offers Reopen match.
In Fast Coding, the same action is Post pair.

Full procedures: Code an internal transfer and Code a credit-card payment.

Never post the two legs separately as income and expense. That invents an expense, overstates revenue, and leaves both registers wrong.

When A Pair Fails To Post

If a confirmed pair bounces off the posting guards, Tally reports it rather than retrying blindly. The usual causes are a locked period, an already-posted leg, or a warning that needs a person.

If a pair posted incorrectly, use Undo a posted bank transaction and check both registers afterwards. Do not offset a wrong transfer with a manual journal entry.