ERPNext: bank row imported but Payment Entry is missing

A Bank Transaction imported into ERPNext is a statement line, not proof that a Payment Entry exists or has affected the General Ledger. Before creating a missing payment, look for an existing submitted voucher that represents the same event.

LocalExtract can prepare a local CSV from a PDF statement. It does not create Payment Entries, submit vouchers or synchronize ERPNext. The CSV columns are date,description,amount.

Identify the bank-side record and the accounting-side record

The official banking overview and Bank Reconciliation workflow distinguish imported Bank Transactions from accounting vouchers. Select the Company Bank Account, currency and statement date range. Confirm which Bank-type General Ledger account it represents.

For the particular statement movement, retain amount, date, reference and account. Search existing Payment Entries and Journal Entries before creating another payment. The same bank reference on an import and a submitted voucher can support a match; their mere existence does not prove that they have been linked.

When the Payment Entry is absent from the match list

Check the documented eligibility conditions in order:

1. Does the voucher post to this bank ledger account? Review Paid From and Paid To, not just the company name.
2. Is its posting date inside the matching range? Bank settlement and posting can occur on different dates.
3. Is it submitted, rather than a saved draft? A draft does not affect the ledger.
4. Has it already been cleared? An unavailable existing voucher is not automatically a missing payment.

Only expand the range enough to investigate an evidenced date difference. Do not select a similarly valued voucher from another account to make the line disappear. Match a real existing voucher first; create a missing accounting entry only after establishing that it is absent.

Read the three dates and statuses separately

In a synthetic review, statement movement B-1 is an outgoing 72 on October 8. Voucher V-1 posts 72 to the correct bank account on October 7 and is submitted, but the initial match range begins October 8. The range explains why the candidate may be absent; it does not justify a second Payment Entry.

Our synthetic record-state worksheet also contains a draft and a voucher posting to a different bank account. These are eligibility controls, not an ERPNext execution. The authorized user must confirm the actual candidate and result.

After reconciliation, review General Ledger, party ledger and the source voucher status. Clearance Date records when the bank cleared the item; it does not move the original GL posting date. A zero reconciliation difference alone does not prove that the party invoice allocation is correct.

Use the period-reconciliation guide for a wider statement/ledger checklist. This page isolates imported bank rows versus submitted accounting vouchers. Extract a PDF source locally, then verify the destination records independently.

Official ERPNext documentation checked October 16, 2026; no voucher created or submitted.