Diagnose and Resolve Payment Differences in ZoneReconcile

Use this guide to identify the cause of a payment difference before applying automation. ZoneReconcile supports automated payment difference handling, but only after the variance has been correctly diagnosed — this guide walks you through each diagnostic step in order.

Problem

A bank statement line does not exactly match the expected transaction amount in ZoneReconcile. You need to determine whether the difference is a valid business variance, a matching issue, a currency issue, a timing issue, or a case that should not be automated.

Symptoms

• The matched amount is slightly higher or lower than the transaction amount.
• A line saves only after manual review, or does not save as expected.
• A journal entry, payment, refund, or related record is not created.
• The statement line appears matched, but the outcome is incomplete or incorrect.
• A user is unsure whether to use a payment difference reason, adjust matching, or leave the line for review.

Prerequisites

• Access to the bank statement and related transaction record in NetSuite.
• Permission to review Bank Account Configuration and matching behavior.
• Statement details including amount, date, currency, counterparty/reference information, and any fees or deductions shown by the bank.

Solution

Step 1: Confirm the exact variance

Compare the bank statement line amount to the intended matched transaction amount and calculate the difference exactly. Check whether the variance is a small rounding amount, a bank fee, a partial settlement, an exchange-related variance, or a larger business exception.

Expected result

You know the direction and size of the variance and can describe it clearly — for example, "underpayment by 0.04" or "overpayment by 20.00."

Step 2: Verify that the correct transaction was matched

Review the selected match and confirm that the statement line is linked to the intended invoice, payment, vendor bill, refund, or other transaction. Pay close attention to similar document numbers, duplicated counterparties, and lines that may have been matched by counterparty or parameter rather than by an exact business reference.

Important: Do not treat a difference as a payment difference scenario until you have ruled out an incorrect or incomplete match.

Expected result

You can confirm the line is matched to the correct business transaction, not just the most likely-looking result.

Step 3: Check for foreign exchange or currency rounding effects

If the bank statement, transaction, or subsidiary involves foreign currency, review the transaction currency and bank statement currency. Small differences may come from exchange-rate conversion or rounded imported amounts rather than from a genuine customer or vendor short-pay/overpay event.

1. Check whether the statement amount was converted before import.
2. Check whether the transaction and bank account use the same currency.
3. Check whether the difference is limited to a minor decimal variance.

Important: Payment difference reasons for transactions in foreign currency are not currently supported.

Expected result

You can determine whether currency handling is the likely driver of the variance.

Step 4: Check for timing differences

Decide whether the bank line and the expected transaction belong to the same business event at the same point in time. A payment may have been posted before discounts, reversals, settlement adjustments, or related transactions were fully recorded. Timing differences can make an otherwise valid payment appear short or over by the time it reaches reconciliation.

1. Review posting dates and bank dates.
2. Check whether related transactions were created after the payment was imported.
3. Confirm whether the line should be processed now or held for later review.

Expected result

You know whether the issue is caused by processing sequence rather than by a true difference reason.

Step 5: Check for partially matched or incomplete settlement scenarios

If a line appears only partly explained, verify whether the bank amount should cover multiple transactions, a split settlement, or a line that was only partially matched. This is especially important when matching by counterparty, broad parameters, or manual popup selection.

1. Check whether more than 1 open or closed transaction should be involved.
2. Check whether part of the amount belongs to another document.
3. Check whether the selected line reflects the full intended settlement.

Expected result

You can determine whether the variance comes from an incomplete matching outcome rather than a payment difference reason case.

Step 6: Decide whether the variance is a valid write-off or difference-reason scenario

Once matching, currency, and timing have been reviewed, decide whether the remaining variance is a legitimate business difference that your team intentionally handles through payment difference reasons or write-off-style treatment. Typical examples include small rounding differences or approved underpayments/overpayments within policy.

Expected result

You can classify the case as either a supported difference-reason scenario or a case that needs manual correction, rematching, or further investigation. If the variance is valid and supported, the next step is configuration and controlled automation — not further diagnosis.

Step 7: Move to automation only after diagnosis is complete

If you have confirmed that the variance is legitimate and suitable for automatic handling, use the following customer-facing configuration references to continue setup. Review related permissions, Bank Account Configuration, matching rules, and payment difference reason guidance.

• Payment Difference Handling
• Payment Difference Reason Automation
• Create Payment Difference Reasons

Expected result

You move into automation with a clear understanding of what is being automated and why.