In this article
Use references, roles, dates, and amounts together to resolve apparent conflicts without guessing.
Reconciliation begins with a deceptively simple question: are these records describing the same thing? An invoice, a provider record, a notification, and a bank entry can all relate to one business payment without being interchangeable. If the matching is wrong, even a careful explanation of timing or status will be wrong. This independent method organizes a review; it does not replace accounting policy, bank confirmation, or an authorized investigation of a specific transaction.
Assign every record a role
Label the record before comparing its content. Possible roles include business obligation, payment instruction, movement record, notification, and bank evidence. The role tells you what the record is capable of establishing. An invoice shows a commercial reference and amount, but its presence alone does not establish the outcome of a payment instruction.
Dwolla’s lifecycle documentation describes correlation IDs and resource links as ways to track connected transfers. That is a useful reminder to preserve actual references rather than relying solely on similar-looking amounts and dates. This article does not assume a particular identifier exists in every reader’s application.
Build a matching key from several facts
Use the strongest references available, then compare supporting facts such as amount, currency, date, and source or destination role. No single weak clue should carry the entire match. A common amount and a nearby date may identify a candidate, but they should not be presented as certainty when several candidates exist.
In a fictional coworking business, three members receive equal deposit refunds during one week. Matching solely by value could attach the wrong bank entry to a member’s refund. The reviewer instead preserves the member’s business reference and the provider’s payment reference, then checks the other details. The extra structure prevents an apparently tidy but incorrect reconciliation.
Distinguish unmatched from mismatched
An unmatched record lacks a confirmed counterpart. A mismatched pair has been compared and contains a conflict. Those are different findings. Calling both “missing payment” obscures the next task. The first needs better identification; the second needs an explanation for the conflict or a correction to the proposed match.
Use neutral review labels such as “candidate match,” “confirmed relationship,” and “unresolved discrepancy.” These are your worksheet categories, not official transaction statuses. Keep them visually separate from the exact provider label so a later reader does not mistake a reviewer’s judgment for a system-reported fact.
Explain differences only after confirming the relationship
If two amounts differ, write down the difference but do not automatically call it a fee. If dates differ, do not automatically call it a delay. If descriptions differ, do not automatically call one incorrect. Each conclusion requires information about how the related records were produced and what they represent.
For example, a creation date and a later observation date can differ without contradiction because they measure different events. A notification reference can differ from a movement reference because they identify different objects. The notification timeline guide develops that second distinction. A discrepancy becomes meaningful only after the comparison is made on like terms.
Preserve both the original and the resolution
When a match is corrected, retain a concise note explaining what changed. “Previously linked to invoice A; reference review identified invoice B” is more useful than erasing the earlier association without explanation. The note should be factual and limited to the review, without assigning blame to a person whose actions you have not established.
For shared working copies, include only the details needed to understand the match. Redact unrelated transactions and private financial information. Keep originals in the appropriate authorized record system rather than scattering them across a growing collection of emails. Good reconciliation depends on traceability, but traceability does not require indiscriminate copying.
Close with a supported statement
A useful conclusion says which records were matched, what evidence supports the match, and whether any discrepancy remains. “These records refer to the same payment; the dates describe different events” is much clearer than “Looks fine.” If the review remains open, identify the precise missing item rather than presenting a vague unresolved balance.
For a returned attempt, use the return evidence packet to preserve the reason alongside the matching work. For a multistage movement, use the transfer-leg map. The objective is a defensible relationship between records. Once that relationship is clear, a status or timing explanation has a solid foundation instead of depending on a coincidence of numbers.