Invoice payments no longer need to sit separately from the systems a business uses to manage customers, orders and accounts receivable.
A modern invoice-payment setup can connect the invoice itself with:
- credit and debit card payments;
- payment links;
- Open Banking or Pay by Bank;
- recurring payments;
- payment gateways;
- CRM systems;
- accounting software;
- ERP platforms;
- accounts-receivable automation;
- settlement reporting; and
- payment reconciliation.
For a small business, this might simply mean adding a secure card-payment link to an invoice.
For a larger organisation, the payment process can be embedded much more deeply into the finance workflow.
For example:
invoice raised → payment request created → customer pays → transaction confirmed → invoice marked paid → payment reconciled against settlement
The right setup therefore depends on much more than finding a merchant account that can accept a card.
What is invoice payment processing?
Invoice payment processing is the way a business collects and records payment against an issued invoice.
Traditionally, that may have involved:
- sending an invoice;
- asking the customer to make a bank transfer;
- waiting for the payment to arrive;
- checking the bank account;
- matching the payment reference; and
- manually marking the invoice as paid.
Payment technology can automate much more of this process.
A payment gateway, accounting platform or connected payment provider may allow a customer to pay directly from the invoice or payment request.
The resulting transaction data can then flow back into the business's finance systems.
The payment should connect back to the invoice
Accepting the transaction is only part of the process.
A useful invoice-payment setup should ideally make it easy to identify:
- which customer paid;
- which invoice was paid;
- how much was paid;
- which payment method was used;
- whether the payment succeeded;
- whether a refund was later issued;
- which settlement batch contains the transaction; and
- what fees were deducted.
At scale, this integration can be considerably more important than the difference between two headline transaction rates.
Taking card payments from an invoice
A business can allow customers to pay an invoice by debit or credit card without building a conventional ecommerce store.
One common approach is to include a secure payment link within:
- the invoice;
- invoice email;
- customer portal;
- SMS reminder;
- CRM communication; or
- accounts-receivable workflow.
The customer opens the link and completes the transaction through a secure online payment page.
The payment request can potentially contain information such as:
- invoice number;
- customer ID;
- account number;
- order reference;
- amount due;
- currency; and
- description.
For the payment-link process itself, see our dedicated Pay by Link guide .
Invoice payment integration
The biggest opportunity is to connect payment acceptance directly with the software already controlling the invoice.
That could be:
- accounting software;
- ERP;
- CRM;
- order-management software;
- case-management software;
- property-management software;
- practice-management software;
- billing software;
- accounts-receivable platforms; or
- a bespoke internal system.
The integration may be provided through:
- a native software integration;
- a payment-provider plugin;
- an API;
- webhooks;
- middleware;
- an automation platform; or
- a custom development project.
Businesses with wider software requirements can read our guide to integrated payments .
What does an integrated invoice-payment workflow look like?
A more connected workflow might look like this:
- An invoice is generated in the accounting or ERP system.
- A unique payment request is created automatically.
- The customer receives the invoice with a payment option.
- The customer chooses how to pay.
- The payment provider processes the transaction.
- The provider returns the payment status.
- The invoice is automatically updated.
- The finance system records the payment reference.
- Settlement information is received from the provider.
- The transaction is reconciled against the corresponding settlement.
The exact workflow varies by software and provider, but the principle is the same:
payment data moves with the transaction rather than needing to be reconstructed manually afterwards.
Invoice payments and ERP systems
ERP integration becomes particularly important for organisations processing large numbers of invoices.
The ERP may already control:
- customer accounts;
- sales orders;
- invoices;
- credit limits;
- outstanding balances;
- cash allocation;
- general ledger entries; and
- management reporting.
A disconnected payment process can create additional work because the finance team then has to match payment-provider information back to ERP records.
A more integrated setup can use invoice and customer references throughout the payment journey.
For larger accounts-receivable environments, see our guide to ERP and accounts-receivable payment automation .
Integrated payments vs embedded invoice payments
There is an important distinction.
Integrated invoice payments normally describe a merchant connecting payments to its existing accounting, CRM, ERP or billing workflow.
Embedded payments can go further, with a software company making payment acceptance part of its own platform or product.
For example:
Merchant: a wholesaler connects its ERP invoices to a payment gateway.
Software platform: an invoicing SaaS business embeds payment acceptance so that thousands of its customers can accept invoice payments directly inside the platform.
Software companies building payments into their own product should read our Embedded Payments guide .
Embedded invoice payments for software platforms
For accounting, invoicing, ERP, CRM and vertical SaaS providers, invoice payments can become part of the software proposition itself.
Instead of telling software users to find their own gateway and then connect it manually, the platform may integrate with one or more payment partners.
This can allow users to:
- activate payment acceptance inside the software;
- add payment options to invoices;
- create payment links;
- accept cards or other payment methods;
- view transaction status;
- issue refunds;
- automatically update invoice status;
- reconcile payments;
- manage recurring payments; and
- access payment reporting within the platform.
Depending on the partnership model, the software business may also have commercial objectives around payment revenue.
At that point, provider selection involves more than technical compatibility.
The platform may also need to consider:
- merchant onboarding;
- underwriting;
- supported sectors;
- pricing;
- revenue share;
- API capability;
- white labelling;
- merchant support;
- reporting;
- regulatory responsibilities; and
- how much of the payment relationship the platform wants to control.
Need payments to connect with your invoicing or finance software?
Tell us which accounting, ERP, CRM or billing system you use and how you want customers to pay.
Merchant Advice Service can help you understand the gateway and integration requirement before identifying providers that may be suitable.
Find suitable payment providers
Payment links inside invoices
Payment links are one of the simplest ways to connect an invoice with online payment acceptance.
A link can potentially be generated automatically when the invoice is created.
The customer could then receive:
Invoice INV-29821 → £3,850 due → Pay securely online
The underlying link can contain or reference the invoice information needed to match the transaction later.
For low volumes, a business may create these links manually.
At higher volumes, API-based or native integration becomes much more important.
Using APIs for invoice payment integration
Payment APIs allow business software and payment platforms to exchange information programmatically.
An API integration could allow a business system to:
- create a payment request;
- send the invoice amount;
- pass a customer reference;
- generate a hosted checkout;
- request payment authorisation;
- check payment status;
- issue refunds;
- retrieve transaction information; and
- update the internal customer record.
Webhooks can then allow the payment provider to notify the business system when an event occurs.
For example:
payment successful → webhook sent → invoice automatically marked paid
Businesses planning custom development can read our Payment API Integration guide .
Card payments are not the only option
An invoice-payment integration does not have to be limited to debit and credit cards.
Depending on the provider, the payment journey might support:
- cards;
- Apple Pay;
- Google Pay;
- Open Banking or Pay by Bank;
- Direct Debit;
- BNPL where appropriate; and
- other alternative payment methods.
The most appropriate method can depend on the invoice value, customer type and payment frequency.
For example, a £30 consumer invoice may have very different requirements from a £25,000 B2B invoice.
See our Alternative Payment Methods guide for the wider payment-method decision.
Open Banking and Pay by Bank for invoices
Open Banking can give customers an account-to-account payment route rather than requiring card details.
This can be particularly relevant where businesses collect:
- B2B invoices;
- higher-value payments;
- professional-service fees;
- account balances;
- property-related payments;
- education fees; or
- other payments traditionally made by manual bank transfer.
A payment-initiation journey can potentially pre-populate the payment information and return useful transaction status to the merchant.
Read our Open Banking payments guide for the wider account-to-account model.
Recurring invoice payments
Not every invoice needs to be paid individually.
Where a customer has an ongoing commercial relationship, the business may use:
- recurring card payments;
- Direct Debit;
- Variable Recurring Payments where supported;
- stored credentials;
- subscription billing; or
- another agreed recurring-payment structure.
The invoice may still be generated for accounting purposes while payment takes place automatically under the customer's existing payment authority.
The business then needs the recurring transaction to match correctly against the invoice or account balance.
Invoice reminders and accounts-receivable automation
A connected payment setup can also form part of the wider accounts-receivable process.
For example:
invoice issued → reminder due → automated email or SMS sent → customer opens payment request → payment completes → AR system updates
The system may be able to trigger different customer journeys depending on:
- invoice due date;
- invoice value;
- customer type;
- payment status;
- days overdue;
- previous reminders; and
- agreed credit terms.
Businesses should still make sure customer communications and collection practices are appropriate for the type of debt being collected.
Payment reconciliation is part of the integration
A successful card authorisation does not complete the finance workflow.
The business also needs to identify the transaction when funds are settled by the payment provider.
This becomes more difficult because a settlement amount may contain:
- many transactions;
- processing fees;
- refunds;
- chargebacks;
- reserves;
- currency conversion; and
- other adjustments.
An integrated setup should therefore consider both:
invoice → transaction
and
transaction → settlement
For more detail, see our Payment Reconciliation guide .
Tokenisation and stored customer payment details
Some businesses need customers to make repeat payments against multiple invoices.
Payment tokenisation can allow a payment provider to replace sensitive card credentials with a token that can be referenced in later authorised payment journeys.
This can support use cases such as:
- repeat customers;
- subscriptions;
- account customers;
- scheduled payments;
- instalments; and
- merchant-initiated transactions where permitted.
Businesses should not simply store card numbers inside their CRM, ERP or accounting software.
The payment architecture should be designed around the payment provider's secure tokenisation and PCI DSS arrangements.
PCI DSS and invoice payment integration
Taking invoice payments by card does not remove PCI DSS responsibilities.
The merchant's responsibilities depend on how cardholder data flows through the payment environment.
A hosted payment page, tokenised integration or provider-controlled checkout can have a different PCI DSS impact from a business collecting or transmitting payment-card data directly through its own systems.
Businesses should confirm the appropriate PCI DSS requirements for the complete integration with their payment provider or qualified security adviser.
Invoice payments for B2B businesses
B2B merchants are particularly relevant to integrated invoice payments because many do not operate conventional ecommerce checkouts.
Examples include:
- wholesalers;
- manufacturers;
- distributors;
- professional services;
- legal firms;
- recruitment businesses;
- construction suppliers;
- commercial property services;
- IT and software businesses; and
- other account-based suppliers.
The customer may place an order through a salesperson or account manager and receive an invoice later.
Embedding payment into that invoice journey allows the business to modernise payment collection without forcing the entire sales process into an ecommerce model.
Invoice payments for wholesalers and distributors
Wholesale and distribution businesses often have particularly complex order-to-cash workflows.
A typical journey might involve:
sales order → stock allocation → dispatch → invoice → payment → settlement → reconciliation
The payment provider may therefore need to work with:
- distribution ERP;
- customer accounts;
- credit terms;
- sales orders;
- warehouse systems;
- accounting;
- CRM; and
- existing merchant acquiring.
Businesses in this sector can also read our guide to Distribution ERP Payment Integration .
What should businesses compare between invoice-payment providers?
Existing software
Can the provider work with the accounting, ERP, CRM or billing platform already in use?
Integration method
Is there a native integration, plugin, API, webhook or other supported connection?
Payment methods
Can customers pay using the methods appropriate for the business?
Invoice references
Can payment requests carry the information needed to match transactions automatically?
Merchant acquiring
Does the provider require a particular acquirer or can it work with existing acquiring relationships?
Recurring payments
Can the setup support repeat customers, subscriptions or account-based billing where required?
Refunds
Can refunds be linked back to the original invoice and transaction?
Settlement
When are funds received and what settlement data is provided?
Reconciliation
Can transaction-level data be matched against settlement and accounting records?
API capability
Can the business automate payment requests and status updates at the required volume?
Reporting
Can the finance team report by invoice, customer, payment method, business unit or legal entity where required?
Pricing
What is the total cost across acquiring, gateway, integration and platform fees?
Build the payment around the invoice workflow
Start with the systems your business already uses and the information finance teams need after the customer pays.
Merchant Advice Service can help map the requirement across the payment gateway, merchant account, software integration and reconciliation process before identifying providers that may be suitable.
Discuss your integration requirements Explore payment gateway providers
How Merchant Advice Service helps with integrated invoice payments
Merchant Advice Service helps businesses understand payment requirements before identifying providers that may be suitable.
For invoice-payment projects, that can include:
- payment gateways;
- merchant acquiring;
- payment links;
- Open Banking;
- recurring payments;
- accounting integrations;
- CRM integration;
- ERP integration;
- AR automation;
- API requirements;
- tokenisation;
- multiple merchant IDs;
- currencies;
- settlement;
- reporting; and
- payment reconciliation.
Software companies wanting to build payment acceptance into their own invoicing, accounting or ERP product have a different requirement.
For that use case, see our Embedded Payments guide .
Editorial & Commercial Disclosure
This guide provides general information about invoice payments, payment gateways, merchant accounts and software integration.
The functionality available depends on the payment provider, acquiring arrangement, accounting or ERP platform and the particular integration being used.
Merchant Advice Service does not develop accounting, ERP or payment software and does not process or settle transactions.
MAS is an independent payments information and provider-matching service. MAS may receive a referral fee or commission from some payment providers where a business proceeds following an introduction. Commercial relationships do not determine the factual information or provider-selection principles contained within this guide.
Software platforms considering embedded-payment models may have additional contractual, operational and regulatory responsibilities depending on how the payment service is structured.
Businesses should confirm technical compatibility, PCI DSS requirements, pricing, underwriting and contractual terms directly with the relevant providers.
Information is provided for general guidance and should not be treated as legal, regulatory, accounting or information-security advice.