Check duplicates and push bank-feed transactions safely

Pushing is the step that attempts to create an accounting transaction in the selected Reckon Accounts Hosted file; Bank Feed transaction pushes to Reckon One are not available. It is distinct from uploading, coding or saving a draft. You need Bank Feeds access and a working connection to the correct company file. Never blindly resend an apparently failed or interrupted push.

1. In Bank Feed → Feed History, review the transaction's Details, saved coding and account. The Possible dupe badge warns that a similar transaction exists; an imported already mapped notice is another possible-match signal, not a conclusive Reckon match.
2. Select Dupe Check to choose the bank or card account under Possible duplicates, then select Check. Compare flagged transactions to the current Reckon file. Delete matches removes possible matches from BookFlo only, after confirmation; it does not delete Reckon transactions. Do not delete merely because dates and amounts look close when genuine repeated charges exist.
3. For one coded draft use More actions → Push to Reckon; for selected eligible rows choose Push selected (N), or choose Push All Coded (N) for coded rows on the current page. Confirm the count and file. The push progress dialog distinguishes success, errors and potential duplicates; do not start another bulk push just because a window was closed.
4. On a genuine Push Error, open Details and read the error. Correct the relevant account, line, supplier or connection, then save before retrying. Retry N errors attempts error rows for the file, not just those visible on this page: review scope before confirming. A selected all-error group can use Clear errors to reset displayed error states, which does not prove the corresponding Reckon action did not occur.
5. If the row says Reckon outcome unconfirmed or the request was interrupted, Reckon may already have accepted it. Check the selected company file directly and refresh Feed History. Resend with warning explicitly consents to a further attempt after checking; it can create a duplicate. Do not treat a timeout as a failed transaction.
6. A pushed row offers More actions → Repush to Reckon. This deliberately creates another Reckon transaction, not a correction to or reversal of the original. Only use it when a second transaction is intended, after checking Reckon.

For example, two AUD 49.00 card charges on 25-09-2026 may be two legitimate purchases or one duplicate. Compare payees and underlying card records before Delete matches or any push. An uncertain push needs Reckon confirmation even if the row still appears among errors.

Expected result: Successful rows show Pushed; errors retain explanations for review. BookFlo deletion or Clear pushed removes local history only, never the Reckon entry. For allocations see Supplier bill payments and Customer payments; for Reckon connection problems see Reckon troubleshooting.