Push receipts and recover safely from errors

Send verified drafts to Reckon Accounts Hosted and handle duplicates, retries and history cleanup.

Last reviewed 29-09-2026

Push records a cheque or credit-card charge in a connected Reckon Accounts Hosted company file. It does not transfer funds. Receipt push to Reckon One is not available. You need full Receipts access, a connected destination, the exact intended company file, a valid payee/date/total/payment account and coded expense lines. Check the source document before posting.

Push one or several

On Enter Receipt, validate a Ready card then select Push; Push All submits valid Ready cards. The Push Receipts to Reckon dialog shows saving, pushing, success and errors per receipt. The entry flow may first create a supplier if you explicitly selected Add as new supplier.
Alternatively open Receipts → Receipt History, choose a company file and expand a draft/error row. Select Push. To send eligible unpushed receipts, tick rows and choose Push selected (n), or choose Push All Unpushed (n) for the file's eligible records. These history batch actions allow at most 100 receipts per run and show individual progress and failures. Cancel stops remaining work; it does not undo transactions already sent.
Confirm Pushed and the displayed Reckon Sync Details after completion. In history, refresh if the list has not updated yet. Failed bulk saves are skipped from pushes until corrected.

Example: a fictional receipt for AUD 55.00 dated 24-09-2026 is coded to the correct bank and expense account. After selecting Push, look for Pushed and its Reckon sync details. If a browser connection drops at the end of the request, inspect Reckon and refresh history before attempting another push.

Resolve warnings, failures and copies

Possible duplicate: the entry-page progress dialog offers Push anyway and Skip for a detected similar prior receipt. Push anyway intentionally overrides the warning and can create a second Reckon transaction; inspect the existing transaction first. History's ordinary Push blocks a detected duplicate and displays an error instead of silently forcing it.
Error: open the row to read Push Error. Reset to draft (or More receipt actions → Reset to draft) clears a recorded push error; it does not prove a timed-out Reckon write failed. Fix coding or connection problems before trying again.
Uncertain timeout: Reckon may finish a write after the app loses confirmation. The server attempts reconciliation and can ask you to wait before retrying. Check Reckon and the receipt's history; never blindly resend or use a forced copy to resolve uncertainty. See Reckon troubleshooting.
Pushed receipt: Repush deliberately creates and pushes a new copy, not an update to the original. Read the duplicate-risk confirmation carefully; use only when a second accounting transaction is genuinely intended.

Delete BookFlo history

From a row's More receipt actions, Delete asks for confirmation. Clear pushed at the top of Receipt History asks for confirmation and applies to pushed receipts in the selected company group and exact company file, leaving drafts/errors. Both remove BookFlo history, not the Reckon transaction; neither is a reversal. Keep any records your organisation needs before cleanup.