Glossary · Payments

Payment file: definition and how it works in accounts payable

The file an ERP produces from a payment run and sends to the bank to make the payments, listing each payee, account and amount.

Definition

The file an ERP produces from a payment run and sends to the bank to make the payments, listing each payee, account and amount.

Also called: bank payment file, NACHA file, positive pay file

What it means

A Payment file is the instruction set for a payment run. Your ERP builds it after the run selects what to pay: invoices, credits and the payee records behind them. The file lists each payee, account and amount. The bank uses that list to move money. The file is not the ledger entry and it is not proof that money moved. It is the instruction you send, so the bank can act.

Teams also call it a bank payment file, a NACHA file or a positive pay file. The names get used loosely. Ask your bank which file it wants for payment instructions and which file it wants for positive pay. Payment run, positive pay and ACH payment each have their own page. The point here is the file that carries the payment instruction.

A Payment file can cover a whole run. The exact format and split depend on your bank, your country and your contract. What should not vary is the link between the file and the run. If the file cannot be tied back to the run that produced it, you have lost the trail before the money leaves.

How it works in practice

The usual path is simple. AP closes the payment run, your ERP produces the Payment file, someone approves and locks it, and the file goes to the bank. The bank returns a confirmation. AP then reconciles that confirmation to the payment run before the run is closed. Each step needs a named owner. The clerk who builds the run should not be the only person who can change or resend the file.

Locking matters because edits between the ERP and the bank are a fraud risk. A file that can be changed after approval is no longer the file the approver saw. Keep the approved file, send that file, and check the bank confirmation against it. If a payee, account or amount changes after approval, stop and re-approve. Do not fix it in transit.

A Payment file sent to the bank twice pays the whole run twice. That sounds obvious until a timeout happens. The clerk sees no confirmation, assumes the file failed, and sends it again. If the bank accepted both, every payee in the run is paid twice. The bank's confirmation should be reconciled to the payment run before the run is closed. Close only after that match.

Where it goes wrong

The common failure is a resend. A clerk sends the Payment file, gets no clear response, and sends the same file again. The bank may accept both. The whole run pays twice. The fix is not a lecture. It is a rule: check with the bank before any resend, and treat a resend as a new event that needs its own confirmation and reconciliation.

The second failure is a manual edit. Someone changes a vendor account in the file because the vendor record looks wrong, or changes an amount to match an invoice. The bank then pays something the ERP did not produce. That breaks the trail and it is a fraud risk. If the vendor record is wrong, fix the vendor record, rebuild the payment run and produce a new Payment file. Do not edit the file between the ERP and the bank.

The third failure is a partial close. AP gets a bank confirmation, checks a few lines, and closes the run. The confirmation should be reconciled to the payment run before close. Missing lines, extra lines and duplicate lines all matter. A file that is locked but never checked is still a file that can pay twice or pay the wrong account.

The fourth failure is name confusion. A team treats every file with a bank name on it as the Payment file. Do not assume a file is the Payment file just because a colleague calls it that. Ask the bank which file does which job. This is one place where country, bank and contract rules differ, so do not copy another company's setup.

What to check

Before release, check that the Payment file matches the payment run. Confirm the payee, account and amount on the file against the run. Confirm the file is the approved version and that it is locked. Confirm who can send it and who can change it. If the same person can do both, you have a gap.

After release, get the bank confirmation and reconcile it to the payment run before the run is closed. Look for missing payments, extra payments and repeats. If a resend happened, reconcile both sends and resolve the duplicate before you close. Keep the approved file and the confirmation together so the next person can follow the trail.

For controllers, check the process, not just the file. Ask who owns the lock, who can resend, and how a timeout is handled. Ask how edits between the ERP and the bank are blocked. Ask for the bank confirmation match before close. These checks cost less than a duplicate run. Rules differ by country, company and contract, so write the local rule down and follow it.

Questions

What is a Payment file in accounts payable?

A Payment file is the file an ERP produces from a payment run and sends to the bank to make the payments. It lists each payee, account and amount. It is the bank instruction, not the ledger entry or proof of payment.

Can a Payment file be sent to the bank twice?

Yes. If the bank accepts both sends, the whole run pays twice. A timeout is not proof of failure. Check with the bank before any resend, then reconcile both sends to the payment run.

How should a Payment file be reconciled before closing the run?

Match the bank confirmation to the payment run line by line. Check payee, account and amount. Resolve missing, extra or repeated payments first. Close the run only after that match.

Updated Nov 14, 2026. Figures on this page are calculated by ERPSav from the definitions shown. The explanatory text is drafted with AI from those figures and checked automatically before it is published. General information only, not legal, tax or financial advice.