Business Central ACH Payments

Business Central ACH Payments

Business Central ACH Payments lets Microsoft Dynamics 365 Business Central users make ACH payments in Business Central for customer invoices, customer account payments, and recurring payment scenarios when the documented Pay API platform and ACH setup are in place. This page is focused on ACH payment workflows, not a separate ACH integration overview, so the emphasis is on how ACH payments are authorized, initiated, applied, emailed, and reviewed inside the payment processing process.

Solution Overview

The System Solutions LLC payment processing extension supports credit card, debit card, ACH, preauthorization, card-on-file, automatic payment, receipt, signature, LS Express, and reconciliation workflows in Business Central. For ACH specifically, the documented functionality is tied to the Datacap Pay API platform, where ACH payments can be enabled after ACH has been set up for the Datacap merchant.

The business problem solved is the ability to collect customer payments from bank account information rather than only through card-present or card-not-present credit card transactions. ACH invoice payments can be applied to posted customer documents, customer account balances, and recurring payment workflows where ACH authorization has been completed and the relevant setup fields are maintained.

Typical users include accounts receivable staff, customer service staff taking payments by phone, implementation consultants configuring payment processing, administrators managing Pay API setup, and finance teams that need recurring ACH payments for customer balances. The page remains evergreen by avoiding extension version numbers, build dates, and release-specific metadata.

Back to Top

Business Central ACH Payments Overview

ACH payments can be made when the Datacap Pay API platform is used. The documented ACH payment process requires the user to input the authorization method, routing number, account number, and other account details, and the authorization acknowledgment must be checked before proceeding. The source documentation also states that ACH payments must be properly authorized.

ACH payment processing differs from device-based card processing because Pay API allows payment details to be entered directly into the payment page, and ACH authorization information becomes part of the payment workflow. The documented payment options also support recurring payments from account information on file, either through automatic payment processing or by using the Account on File option.

Business Central ACH Payments Features

• Make ACH payments through the Datacap Pay API platform when ACH has been set up for the merchant.
• Enter ACH authorization method, routing number, account number, and related account details during the payment workflow.
• Use a prearranged authorization method when the customer has completed an ACH authorization form or authorization has been recorded during a phone call.
• Use a phone authorization method where the customer is read an authorization script and the script appears on the payment page with details filled in.
• Use Account on File for recurring ACH payment scenarios where properly authorized account information is maintained.
• Send ACH email notifications after manual ACH payments and automatic ACH payments when configured.

Back to Top

ACH Payment Setup Considerations for Business Central ACH Payments

The Payment Processing Setup page includes the documented Allow ACH Payments option. For the Pay API platform, when ACH has been set up for the Datacap merchant, this option enables payments to be made with ACH. Pay API setup also includes fields such as Datacap Pay API Public Key and Pay API Setup Code, where applicable to the broader payment configuration.

Emailing is currently documented as configurable only for the Pay API platform. ACH Emailing sends an email after a manual ACH payment, and Automatic ACH Emailing sends an email after an automatic ACH payment. The source documentation states that emailing after ACH payments is a NACHA requirement.

Back to Top

Business Central ACH Payments and ACH Invoice Payments

A payment can be started from the Customer Payment page, from a Customer Card action, or from a Posted Sales Invoice or Posted Sales Credit Memo action. The source documentation states that the Customer Card payment action can make a payment directly to the customer and that the invoice it applies to may be selected if needed. It also states that posted sales invoice and posted sales credit memo actions can make a payment directly to the posted document.

For ACH invoice payments, the user starts the payment from the appropriate Business Central page, enters the ACH payment details through Pay API, acknowledges the authorization, and completes the payment process. After approval, the payment activity can be reviewed through authorized transaction records and related payment processing actions.

Configured sales document posting can also open the payment page when the Payment Method Code on a Sales Order, Sales Invoice, Credit Memo, or Sales Return Order is set to a payment method configured in the payment terminal. If the payment is approved, posting continues. If the payment is canceled or declined, posting stops so corrections can be made and the payment can be attempted again.

Back to Top

Recurring ACH Payments with Business Central ACH Payments

Recurring ACH payments can be performed automatically or by using the Account on File option on the payment page. The source documentation states that recurring ACH payments must be explicitly authorized on the authorization form or in a recorded call. During authorization, limits such as frequency and amount range are specified.

After the recurring ACH authorization form has been completed, the relevant ACH details are entered on the Customer Card under the Payment Processing section. The documented recurring ACH fields include ACH Recurring Payment Start Date, ACH Recurring Payment Frequency, ACH Recurring Payment Minimum, and ACH Recurring Payment Minimum as listed in the source. These fields are checked before a recurring ACH payment is made.

Automatic payments use Business Central Job Queue functionality. The documented job queue entries have parameter strings for monthly, weekly, or daily processing. If reminder emails are enabled, the reminder email jobs use monthly-reminder-email and weekly-reminder-email parameter strings, and daily payments cannot use reminder emails.

If an automatic payment exceeds the maximum amount, the documented behavior is that the payment is made for the maximum. Other limitations prevent the payment from continuing. This makes recurring ACH payments dependent on both authorization details and the configured customer payment schedule.

Back to Top

Authorization and Compliance Details

The ACH workflow depends on proper authorization. A prearranged authorization method means the customer has filled out an ACH authorization form for the payment or the authorization was recorded during a phone call. A phone authorization method means the customer is read an authorization script over the phone, and when that method is selected, the script appears on the page with some details automatically filled in.

The source documentation also lists ACH-specific transaction differences. Returns must have a previous authorization within 45 days selected. Voids must have a previous authorization from the same day selected. Returns cannot be voided. An email is sent after the payment, and the source states that this is a NACHA requirement.

These details are important because ACH payment processing is not only about entering bank information. The payment process must reflect the authorization method, customer acknowledgment, stored recurring payment limitations, and the required email notification behavior documented for Pay API ACH workflows.

Back to Top

Reviewing ACH Payment Activity

Approved payments can be reviewed by searching for Authorized Credit Card Transactions or by opening the payment records through related payment processing actions. The source documentation states that this list can be searched, sorted, or exported to Excel. It also provides actions to view receipts, view emails for Pay API payments with emailing enabled, filter records without a document number, and assign a document number manually.

The Automatic Payments page shows processed invoices that were paid or attempted through automatic payments. A Completed payment status means the payment was successfully charged and posted to Business Central. An Unposted payment status means the customer was charged but posting failed in Business Central, and the Customer Ledger Entry is blocked from being paid through automatic payment again to avoid a duplicate payment.

Back to Top

Source Screenshot

The following preserved source screenshot shows the documented Credit Card Payment page used by the payment processing workflow. ACH-specific entry fields appear when using the Pay API ACH flow, but this screenshot is still useful because it shows the payment page context where options such as Card on File and Save Card are part of the broader payment experience.

Back to Top

Example Business Workflows

Business Central ACH Payments for a Posted Invoice

An accounts receivable user opens a Posted Sales Invoice, starts Payment Processing, enters ACH account information through Pay API, selects the authorization method, checks the authorization acknowledgment, and completes the payment. The payment can then be reviewed through authorized transaction records.

Customer Account ACH Payment

A user opens the Customer Card, chooses the payment action, selects the invoice when needed, and makes an ACH payment directly to the customer account. This workflow supports customers who pay open balances by bank account instead of credit card.

Phone-Authorized ACH Payment

A customer provides authorization by phone. The user selects the phone authorization method, reads the displayed ACH phone authorization script, enters the required ACH account information, checks the acknowledgment, and completes the payment after authorization is captured through the documented process.

Recurring ACH Customer Balance Payment

A customer has explicitly authorized recurring ACH payments with defined frequency and amount limitations. The user maintains the ACH recurring payment details on the Customer Card, and automatic payment processing uses the configured schedule and account information on file.

Automatic ACH Payment Review

Finance staff review the Automatic Payments page after scheduled processing. A Completed status confirms that the charge and posting completed, while an Unposted status identifies a payment that charged the customer but needs posting attention inside Business Central.

Back to Top

Conclusion

Business Central ACH Payments gives companies a documented path to collect bank-account payments through Pay API, apply ACH invoice payments, and support recurring ACH payments when authorization and setup requirements are met. The most important planning points are ACH enablement for the Datacap merchant, Pay API setup, authorization method selection, required acknowledgment, ACH email setup, recurring payment limitations, and review of automatic payment results.

For a buyer or implementation team, this page should be used to understand ACH payment workflows rather than as an ACH integration checklist. The detailed setup and operational procedures remain in the full user guide, while this intent page explains what Business Central users can do with ACH payments in day-to-day invoice and recurring payment processing.

Back to Top