Credit Card Preauthorization Business Central

Credit Card Preauthorization Business Central

Credit Card Preauthorization Business Central is a specialized payment workflow for placing a credit card pre-authorization hold on a Sales Order and then capturing that authorization when the order is posted to an invoice. This page focuses on the documented sales order preauthorization functionality in the System Solutions LLC payment processing extension, including setup considerations, sales order actions, capture, void, receipt, and review workflows.

Solution Overview

The payment processing extension allows Microsoft Dynamics 365 Business Central users to perform credit card, debit card, and ACH payments to sales invoices and credit memos. The same source documentation states that the extension also allows Credit Card Preauthorization Holds to be performed on Sales Orders.

For companies that need to hold funds on sales orders before final shipment, fulfillment, or invoice posting, preauthorization separates the authorization step from the later capture step. The documented workflow performs the preauthorization from the Sales Order and captures the payment when the order is posted to an invoice.

Typical users include order entry teams, accounts receivable staff, customer service users, Business Central administrators, and implementation teams configuring payment processing for sales order workflows. This intent page avoids extension version numbers and release metadata so the page can remain focused on evergreen buyer education.

Back to Top

Credit Card Preauthorization Business Central Overview

Preauthorizations can be enabled for sales orders and are subsequently captured for settlement when the invoice is posted. The source documentation states that this is for credit only, not debit. It also states that sales order preauthorizations are currently enabled with the Pay API platform.

The documented workflow is intentionally different from immediate payment at invoice posting. Instead of charging the card as a completed sale immediately, the preauthorization places an authorization on the Sales Order and allows capture when the order becomes an invoice. This is the specialized use case behind pre-auth payment Business Central workflows.

Credit Card Preauthorization Business Central Features

• Enable preauthorizations for Sales Orders through the documented payment processing setup.
• Create a new preauthorization from the Sales Order action menu.
• Track a Preauthorized Amount on the Sales Order payment processing tab.
• Capture the preauthorization when the Sales Order is posted to an invoice.
• Void an existing preauthorization from the Sales Order or the Posted Sales Invoice workflow where documented.
• Print preauthorization and captured preauthorization receipts from the documented actions.

Back to Top

Preauthorization Setup Considerations

The Payment Processing Setup page includes a Preauthorizations area. The documented Allow Sales Order Preauths setting specifies that preauthorizations can be made on sales orders. The source documentation notes that preauthorizations can currently only be enabled with the Pay API platform.

The Max Amount Over Preauth setting specifies the maximum amount that a captured preauthorization can exceed the original preauthorized amount. The Void Preauth Without Capture setting specifies that a preauthorization can be voided without first being captured, and the source documentation states that this is applicable when using First Data.

Back to Top

Sales Order Preauthorization Workflow

The source documentation states that the preauthorization is performed on the Sales Order and the payment is captured when the order is posted to an invoice. From the Sales Order page, the documented action Actions > Payment Processing > Preauthorize creates a new preauthorization for the order total.

The Sales Order page also includes Actions > Payment Processing > Void Preauthorization to void the existing preauthorization. The Payment Processing tab includes a Preauthorized Amount field that specifies the preauthorized payment amount for the order.

This workflow is useful when a company wants to hold funds on sales orders before the final invoice is posted. The user can authorize funds at order time, complete fulfillment or review work, and then rely on the documented capture flow when the order is posted to an invoice.

Back to Top

Capture and Void Workflows

When the sales order is posted to an invoice, the documented workflow captures the preauthorization for settlement. If the invoice has already been posted and a manual action is needed, the Posted Sales Invoice page includes Actions > Payment Processing > Capture Preauthorization to manually capture the preauthorization in case there was an error while posting the invoice.

The Posted Sales Invoice page also includes Actions > Payment Processing > Void Preauthorization to void an existing, uncaptured preauthorization. This provides an operational path for cases where the order should not be captured or when the authorization needs to be canceled according to the documented payment workflow.

Capture and void actions should be treated as controlled finance operations because the source documentation ties them to authorization records, invoice posting, and settlement behavior. The page therefore presents the workflow as an operational feature rather than a simple payment button.

Back to Top

Receipts and Signatures

The source documentation states that receipts can be printed for preauthorizations using two installed report IDs. When a user clicks Print Receipt, the extension checks whether receipt data exists for the authorization. If receipt data exists, the documented report layout uses receipt data with payment header. Otherwise, the documented payment authorization receipt layout is used.

From the Sales Order, the documented action Print Last PreAuthorization Receipt prints a receipt for the preauthorization. From the Posted Sales Invoice, the documented action Print Last Receipt prints a receipt for the captured preauthorization.

If an electronic signature was captured during the preauthorization, the source documentation states that the signature will print on the captured preauthorization receipt. This connects the hold workflow to receipt and signature handling for businesses that require documentation of the authorization.

Back to Top

Reviewing Preauthorization Activity

Approved payments can be reviewed by searching Authorized Credit Card Transactions or through the related actions on the payment processing setup page. The documentation states that the list can be searched, sorted, or exported to Excel, and that users can view receipts, view signatures where enabled, filter records without a document number, and manually assign a document number.

For preauthorizations, review activity should focus on whether the authorization was created, whether the amount was captured when the order posted to an invoice, whether a void was used for an uncaptured preauthorization, and whether receipt or signature records are needed for documentation. These review points are derived from the documented preauthorization, capture, void, receipt, and authorized transaction workflows.

Back to Top

Source Screenshot

The following preserved source screenshot shows the documented Credit Card Payment page used by the payment processing workflow. The page is included for context because sales order preauthorization, capture, void, receipt, and signature features are part of the same Business Central payment processing extension.

Back to Top

Example Business Workflows

Credit Card Preauthorization Business Central for a Large Sales Order

An order entry user creates a Sales Order and runs Actions > Payment Processing > Preauthorize for the order total. The Preauthorized Amount is tracked on the Sales Order, and the payment is captured when the order is posted to an invoice.

Hold Funds Before Fulfillment

A business wants to confirm that funds are available before picking, staging, or fulfilling a customer order. The user preauthorizes the Sales Order, completes the internal order workflow, and later posts the order so the preauthorization is captured for settlement.

Manual Capture After Posting Error

A Sales Order is posted to an invoice, but the preauthorization needs manual attention. The user opens the Posted Sales Invoice and runs Actions > Payment Processing > Capture Preauthorization to manually capture the preauthorization as documented.

Void an Uncaptured Preauthorization

A customer cancels the order before the payment is captured. The user voids the existing preauthorization from the Sales Order or, where applicable, from the Posted Sales Invoice action for an existing uncaptured preauthorization.

Print a Preauthorization Receipt

A user prints the last preauthorization receipt from the Sales Order. After capture, the user can print the last receipt from the Posted Sales Invoice, and if an electronic signature was captured during preauthorization, the signature prints on that captured preauthorization receipt.

Back to Top

Conclusion

Credit Card Preauthorization Business Central is a highly specialized feature for businesses that need to authorize a customer card on a Sales Order and capture the payment later when the order becomes an invoice. The documented feature set centers on Pay API sales order preauthorizations, Preauthorize and Void Preauthorization actions, Preauthorized Amount tracking, invoice capture, manual capture, receipt printing, and signature support.

For implementation planning, confirm the Pay API platform requirements, the Allow Sales Order Preauths setting, capture tolerance through Max Amount Over Preauth, void behavior, receipt expectations, and how staff will review authorized transaction activity. Those items determine whether a pre-auth payment Business Central workflow is a good operational fit for holding funds on sales orders.

Back to Top