Elavon Business Central Integration

Elavon Business Central Integration

Elavon Business Central Integration helps merchants that already use Elavon connect payment acceptance with invoice, customer-account, point-of-sale, and accounting workflows in Microsoft Dynamics 365 Business Central through the System Solutions LLC payment processing extension.

Solution Overview

The System Solutions LLC extension connects card and eligible ACH activity with Business Central records. Supported solution workflows can include posted sales invoice and credit memo payments, customer-account payments, sales-order preauthorization, tokenized cards on file, automatic payments, receipts, authorized-transaction review, LS Express activity, and reconciliation review. Typical users include accounts receivable teams, counter sales staff, finance personnel, administrators, and implementation partners.

Back to Table of Contents | Back to Top

Elavon Business Central Integration Overview

Elavon Business Central Integration Features

Elavon describes its services across in-person payments, contactless payments, online payments, payment gateways, security and PCI compliance, reporting, and partner solutions. Elavon also states that it is wholly owned by U.S. Bank and provides end-to-end payment processing services to more than two million customers in the United States, Europe, and Canada. These processor-specific facts make Elavon relevant to organizations that want to retain an established merchant relationship while moving transaction entry and accounting workflows into Business Central.

In February 2026, Elavon introduced a new brand identity that emphasizes connection, partnership, and seamless transactions. The logo shown above uses that current brand imaging. Visit the authoritative Elavon merchant services website or read Elavon's announcement of its current brand identity.

Back to Table of Contents | Back to Top

Can I Keep My Existing Processor?

For high-intent buyers, Elavon Business Central Integration answers the central question of whether an established processing relationship can remain in place.

Yes. A business with an existing Elavon merchant account does not automatically need to switch processors. System Solutions LLC can connect supported Elavon processing to integrated Business Central Payment Processing. Before equipment is ordered, the implementation team should review a current merchant statement or processor setup sheet to identify the actual merchant platform, MID, required payment types, and terminal requirements.

The Elavon name on a statement may not by itself identify every technical value required for an integration. Confirming the account details helps avoid ordering a terminal with the wrong application, encryption, key injection, or host configuration.

Back to Table of Contents | Back to Top

Payment Workflow Questions

Evaluate Elavon Business Central Integration against the payment workflows your staff actually performs, not the processor name alone.

Back to Table of Contents | Back to Top

What Payment Terminals Are Supported?

Payment hardware must be matched to both the Elavon host configuration and the integration platform. The current compatible-device directory includes these device families for evaluation:

• PAX: A77, A6630, A6650, A920MAX, A800, A920 Pro, A30, A35, A3700, Aries8, and IM30.
• Ingenico: DX4000, DX8000, EX6000, EX8000, RX5000, RX7000, Desk/3500, Desk/5000, Lane/3600, Lane/3000, Lane/7000, Lane/8000, Self/3000, Link/2500, and Move/5000.
• Verifone: P200, P400, and M400.
• ID TECH: VP3350, VP7200, VP3300, VP8300, Augusta, VP6800, iUC 285, and Minismart II.
• Other form factors: mobile, tablet, kiosk, unattended, and SoftPOS options listed in the current directory.

The device catalog changes as models and certifications change. Review the current compatible payment terminal directory and have System Solutions LLC validate the exact Elavon pairing before ordering hardware.

Back to Table of Contents | Back to Top

Implementation and Compatibility Review

A structured review keeps Elavon Business Central Integration aligned with the exact merchant account, hardware, and Business Central workflow requirements.

1. Provide the Elavon merchant statement and available setup or VAR information.
2. Identify the Elavon processing platform, MID, locations, country, currency, and required payment channels.
3. Document needed workflows, including card present, card not present, invoice payments, refunds, voids, preauthorizations, cards on file, recurring payments, ACH, LS Express, receipts, signature capture, and reconciliation.
4. Verify the required functions against the supported processor and feature matrix.
5. Confirm the exact terminal model, application, encryption, connectivity, and injection requirements before purchase.
6. Configure and test the complete path in a Business Central sandbox before production use.

Back to Table of Contents | Back to Top

Example Business Workflows

Existing Elavon Merchant Moves to Business Central

A merchant supplies the existing account information, has the processor platform and device path verified, and implements the System Solutions extension. Payments can then be initiated from supported Business Central workflows without automatically replacing the established Elavon relationship.

Counter Payment Applied to an Invoice

A counter user selects a posted invoice or customer account, initiates payment, and the customer presents a card at the configured terminal. After authorization, the payment remains associated with the Business Central customer and accounting records for receipt and reconciliation work.

Phone Payment Using a Saved Card

An accounts receivable user selects an authorized tokenized payment method, processes the card-not-present payment, and applies it to the correct open invoice or customer balance without entering stored raw card data into Business Central.

Recurring Balance Collection

A customer authorizes recurring collection. On the scheduled cycle, the configured automatic-payment workflow uses the approved token or ACH method, records the result, and makes the transaction available for Business Central review and application.

LS Express Retail Checkout

A cashier completes an LS Express sale, the customer uses an approved payment terminal, and the authorized tender is connected with the Business Central sale and ledger workflow rather than being re-entered from a separate stand-alone terminal.

Back to Table of Contents | Back to Top

Conclusion

Elavon Business Central Integration gives an existing Elavon merchant a practical path to connect card and eligible ACH activity with invoices, customer accounts, LS Express, stored-payment tokens, recurring collections, and accounting review. The key implementation step is confirming the exact merchant platform and certified device combination before configuration or equipment purchase.

Back to Table of Contents | Back to Top

Related Resources

Back to Table of Contents | Back to Top