Comparing Direct ACH with NACHA file payments?
Read Understanding Direct ACH and NACHA file payments to choose the workflow that applies to your company. This article explains how to create a payment batch and release a Direct ACH vendor payment.
Before you begin
Before you process AP invoices for Direct ACH vendor payments in Wrapbook:
Your company must have Wrapbook's Production Accounting Suite (PAS) enabled
The Direct ACH vendor payments feature specifically must be enabled for your company by Wrapbook
Your Direct ACH vendor payments settings have been configured
The AP invoice for the Direct ACH vendor payment has been created and posted
Required permissions
Access to Direct ACH vendor payments in Wrapbook is permission based. In order to use this feature you'll need to be assigned one of the following roles:
Role | What this role can do |
|---|---|
Company Admin | Complete KYC, enable bank accounts at the company level, create approval workflows |
Assigned Project Coordinator or Project Assistant | Add bank accounts at the project level, add vendor banking info, create invoices, process payments |
How to process Direct ACH vendor payments
When you're ready to pay one or more posted AP invoices for vendors you'll need to add the invoice(s) to a payment batch from the Posted & unpaid tab of the project's Accounts payable dashboard.
Create payment batches from the Posted & unpaid tab
When you’re ready to pay posted AP invoices, select the invoices from the Posted & unpaid tab of the project’s Accounts payable dashboard.
On the project’s Accounts payable dashboard, click the Posted & unpaid tab
Review the Bank and Payment type columns, then select the checkbox next to each invoice you want to include
You can select posted and unpaid invoices across accounting banks and payment types. Invoices that are already in a payment batch aren’t eligible for selection
Click the Create payment batch button. The button shows how many batches Wrapbook will create
Wrapbook creates separate payment batches based on the accounting bank, payment type, and payment date for the selected invoices
Open each payment batch and review Payment date, Bank, and Payment type. If a batch does not have a payment type, select one before you continue
Complete any required approval steps, then click Approve and Pay
Add invoices to an existing payment batch
You can add eligible invoices from the payment batch.
Open the payment batch
Click Add existing invoice
Select the posted and unpaid invoices you want to add
Review any warning when an invoice’s bank or payment type differs from the batch
Save the batch, then review the batch details before approval
Only eligible, unbatched invoices can be added. When the batch is paid, the batch’s bank and payment type are applied to the invoice. If no eligible invoices are available, you can’t add an invoice to the batch
How payment batches work
A vendor payment batch is how Wrapbook groups and executes Direct ACH vendor payments. Understanding how batches work will help you plan your payment runs and reconcile your bank statements accurately.
What is a Direct ACH vendor payment batch?
A Direct ACH vendor payment batch is a collection of posted AP invoices that you've selected to pay together in a single run. Batches are project-specific — each batch is scoped to a single project, bank account, and payment type. You cannot combine invoices from multiple projects in one batch.
Payment-batch permissions
Your Vendor Payment access level determines what you can do with payment batches and payments:
View: See batches and payments, and approve a batch when you’re assigned as an approver
Manage: Do everything in View, build and edit batches, and post manual checks and wire transfers
Full: Do everything in Manage, plus print checks, pay now by direct ACH, generate or transmit NACHA files, transmit to CashetPay, and cancel ACH
Additional approval workflow and accounting-period rules can limit what you can change:
Before a batch is submitted, someone with Manage or Full can build and edit it, and Payment type can remain To be determined
After a batch is submitted and while it is waiting for approval, the person who submitted it and the approver whose turn it is can edit the payment date, check starting number, invoice-combination setting, payment reference, bank, and payment type
The last approver and anyone who can override the approval workflow can also change the vendor, mailing address, and invoices on the batch. The last approver must set Payment type, Bank, and Payment date before approving and paying
Any reviewer assigned to the approval workflow can add or remove invoices while the batch is in review
After a batch is approved or paid, no one can edit it
A locked or closed accounting period can prevent a user from changing an invoice’s bank or paying the batch. A Company Admin, or a company team member with permission to create distribution changes may need to make the change, depending on the period and invoice.
How invoices are grouped within a Direct ACH vendor payment batch
When you create a Direct ACH vendor payment batch and select multiple invoices, Wrapbook automatically groups invoices by vendor. This means:
You have the option to select a toggle to either combine invoices into a single Direct ACH vendor payment or split invoices into multiple Direct ACH vendor payments
Your bank account is not debited as a single lump sum. Each Direct ACH vendor payment is a separate ACH debit, each with its own auto-assigned Payment ID
The Payment ID appears in your bank statement's transaction description, making it straightforward to reconcile each payment back to the vendor and invoices it covers
Reviewing a Direct ACH vendor payment batch before approval
Before you approve and release a payment, review the batch details, including Payment date, Bank, Payment type, vendor information, and invoice details. Confirm that the batch payment details are correct for every invoice before you click Approve and Pay
Notes:
Invoice PDFs: If invoice files are attached to your AP invoices, they're visible directly within the batch for side-by-side review — no need to navigate away
Vendor banking warning: If a vendor's banking information is missing, was recently added, or was recently changed, a warning banner will appear in the batch. This is designed to catch potential errors before funds are released.
Blocked vendor bank account: If a vendor’s bank account is blocked, one or more payments in the batch might not be processed. The batch shows Some payments in this batch can't be processed, and the affected payment shows We weren't able to process this payment. Please contact Wrapbook support for assistance. Contact Wrapbook Support for help before continuing with the payment.
Urgent invoices: Invoices marked as urgent are flagged with a red badge inside the batch so they're easy to identify
Remove or add invoices: You can remove invoices from the batch before approval, or add invoices back if needed, without restarting the entire batch.
To remove an invoice, click the X next to it on the batch page
To add an invoice, go to the Posted & unpaid tab in the project's Accounts payable dashboard and click to select the invoices you want to add, then click Add to existing batch
Approval and fund release
If your project has a vendor payment approval workflow assigned:
When you submit the batch, each approver receives an email notification with a direct link to the batch
Approvers review the batch, verify invoice and vendor details, and click Approve to advance to the next step
If no approval workflow is assigned to the project, the person creating the batch can release payment directly after confirming.
Direct ACH delivery timing
Direct ACH transfers take time to settle between banks.
The timeline is:
Two business days if released before 6PM PST/9PM EST on a business day
Three business days if released on a weekend, a bank holiday, or after 6PM PST/9PM EST on a business day
Audit trail
Every action taken on a payment batch — including invoice additions or removals, approval steps, and fund release — is recorded in the activity feed at the bottom of the batch page and includes:
The user
The action
The timestamp
This gives you a complete audit trail for each payment run.