Pull both records at the same cutoff

Choose one cutoff time and export both the customer portal activity and the ERP ledger as of that moment. If the portal is pulled at noon and the ledger at four, every difference includes four hours of ordinary activity. State the cutoff in the reconciliation file so a later reviewer does not compare the result with a different export. Consistency matters more than the specific time chosen.

Save the raw exports before making any adjustments. The reconciliation should be reproducible from the source files, not from a worksheet that has already been edited. Name the files with the date, time, and source system. If a portal export changes format, keep the old file and document the change rather than overwriting the evidence.

Compare identifiers, not just totals

Match on payment reference, invoice number, customer identifier, and amount before comparing the grand total. A total that agrees can still hide a payment applied to the wrong customer. Build the comparison in layers so the first layer is identity and the second is amount. The layered view makes it obvious where a difference begins.

When an identifier is missing, record it as missing rather than substituting a similar one. A portal reference that differs by one character may be a typo or a different transaction. Check the surrounding dates and amounts before deciding. The reconciliation should show which records could not be matched on identity and why.

Explain timing differences in writing

A payment can be recorded in the portal on Friday and in the ERP on Monday without either system being wrong. Write the expected settlement window beside each timing difference so the reviewer knows when to look again. Do not force a match by changing the date. A dated explanation is more useful than a silent adjustment.

Separate timing differences from real discrepancies in the worksheet. Timing items normally clear on their own, while real discrepancies need an owner and a next step. If a timing item persists beyond the stated window, move it into the discrepancy group. The distinction keeps the reconciliation from becoming a list of unexplained items.

Explore the related specialist service to define scope, ownership, and evidence.

Treat portal credits as their own item

Portal credits, refunds, and chargebacks are not payments and should not be netted against receipts without evidence. Record each credit with its reference, reason, and approval status. If the credit reduces an invoice, show the before and after balance. If it does not, keep it in a separate clearing account until the treatment is confirmed.

Review credits that remain open across two cycles. A credit that never resolves may indicate a missing approval, a customer dispute, or a portal feature that finance does not control. Assign the review to the owner of the credit, not to the person running the reconciliation. The reconciliation can surface the item, but it cannot decide the accounting treatment.

Resolve duplicates before they compound

Duplicate payments are easiest to fix on the day they appear. Compare the portal reference, the bank reference, and the ERP receipt before recording a second payment. If two records describe the same transfer, mark one as the duplicate and link it to the original. Do not delete either record until the refund or reallocation is approved.

Keep a duplicate log with the customer, amount, date, and resolution status. The log helps the team spot a portal retry or a customer double-click that affects several accounts. Review the log weekly and look for a repeated cause. A duplicate that recurs is a process signal, not just a one-off correction.

Financial Accounting Standards Board provides public guidance that can inform a documented review.

Document the reconciliation for month end

The month-end file should show the opening difference, the items cleared during the period, the items added, and the closing difference. Each line needs a reference and a short explanation. A closing balance without the movement behind it is hard to defend. The file should let a reviewer follow one item from the portal through the ledger.

Include the preparer, the reviewer, and the date of review. If an item is still open, name the owner and the expected resolution date. Do not mark the reconciliation complete while a material item has no owner. An honest open item is better than a forced zero difference.

Set a repeatable weekly rhythm

Run the comparison on the same day each week and use the same cutoff. A predictable rhythm makes it easier to distinguish a new difference from an old one. Keep the prior week's file open while preparing the current one so carried items are not lost. The routine should take less time as the team learns the common causes.

Every month, review the differences that took the longest to resolve. Ask whether the cause was a portal setting, an ERP rule, or a missing customer instruction. Fix the most frequent cause first. A reconciliation that only reports differences will keep producing the same work; one that feeds corrections back into the process will shrink over time.

Continue with a related workflow guide.

Common questions answered

Why pull both systems at the same cutoff?

A shared cutoff removes ordinary timing noise and makes the remaining differences meaningful.

How should portal credits be handled?

As separate items with their own reference and approval status, not netted against receipts without evidence.

What belongs in the month-end reconciliation file?

Opening difference, cleared items, new items, closing difference, references, owners, and reviewer sign-off.

Trace a partial customer short-pay to the deduction codeReconcile an unapplied cash suspense balance at week endAudit a customer credit limit override before order release

Define one reviewable receivables workflow.

Bring the queue, owner, source records, and exceptions you need to make visible.

Book a free consultation