Month-end preparation vs month-end reconciliation: choosing the right workflow
Compare month-end preparation and month-end reconciliation using the same inputs, distinct worked outputs, complete briefs, and a practical decision test.
Quick answer
Month-end preparation assembles the material needed for review; month-end reconciliation compares records and explains differences. Use the same source slice, but keep a ready packet distinct from an accepted accounting conclusion.
Two outputs from the same inputs
Month-end preparation: A completeness register of statements, transaction exports, supporting documents, owners, and missing items.
month-end reconciliation: A draft comparison that pairs records, preserves unresolved differences, and routes them to the accounting reviewer.
Both start from the same approved bank statement extract, ledger export, and receipt register. Choose the purpose before asking Righthand to prepare the result; otherwise a polished draft can answer the wrong question.
Worked comparison
The following records are synthetic examples. They illustrate output differences, not product test results or customer outcomes.
| Shared input | Month-end preparation output | month-end reconciliation output |
|---|---|---|
| B1: statement charge has no receipt | List receipt as missing with its collection owner | Identify statement-to-ledger match separately from missing support |
| B2: transfer appears once in the ledger | Include both account statements in the review packet | Flag unmatched side for accountant review; do not create an entry |
| B3: late posting falls outside October | Label source period and preserve the later record | Show timing difference without forcing it into the October match |
Brief A: prepare the first workflow
Use the approved bank statement extract, ledger export, and receipt register for October 12–16, 2026. Source fields: account reference, transaction ID, posting date, amount, ledger reference, statement period, receipt ID, reviewer. At Monday 9 AM America/Los_Angeles, prepare the month-end preparation output shown above as source-linked Markdown in my private review thread. Preserve original record IDs and mark uncertainty. I review the draft against the first table column’s purpose. Do not post entries, change financial records, move money, file returns, or mark accounts reconciled. Result check: each entry matches its source and the intended first-workflow output.
Brief B: prepare the second workflow
Use exactly the same input slice, fields, date window, and timezone. Prepare the month-end reconciliation output shown above instead. Keep the underlying observations separate from interpretation, with a named owner for unresolved questions. Return the draft to the same review thread for my approval. Apply the same action boundaries. Result check: compare each output with the third table column; do not merely relabel Brief A’s artifact.
Righthand can help with both preparation jobs when the sources are supplied or accessible through verified assigned connections. An explicit export is a valid input route; it does not promise a native connector or continuous synchronization. See the Righthand documentation for setup and Features for task fit.
Choose by the decision ahead
Choose preparation when the reviewer is waiting on complete sources and ownership. Choose a reconciliation draft when the inputs are present and the next task is to explain differences. A packet can be complete while balances remain unresolved. A draft match does not establish correct classification or authorize a journal entry.
Failure checks and a first-run test
A missing receipt can be confused with a missing transaction, and matching amounts can hide different transactions. Check IDs, dates, account references, and support separately. Keep proposed explanations distinct from accepted accounting treatment. Righthand can organize supplied evidence; a responsible accounting professional must evaluate consequential conclusions.
Have the reviewer inspect B2 using both account references. The preparation output should reveal whether a statement is missing, while the comparison should preserve the unmatched side. Accept neither artifact if it describes the accounts as reconciled before the accountant’s review. Keep the accepted source system authoritative, and record any approved change there through its supported process. A comparison draft is evidence for your decision, not permission to alter the workflow on its own.
Review Pricing against the actual preparation and review workload. The useful evaluation is whether the accepted artifact reduces work for its intended reader, including correction effort.