Split payment and ERP: integration, reconciliation and tests
Connect invoices, payments and settlement in the ERP, with traceable identifiers, exception handling and acceptance tests for split payment.
Updated:

Direct answer: integrating split payment into an ERP requires a transaction chain, not just a payment API. Invoice, receivable, payment order, settlement, segregated amount, tax liability, clearing and reversal must share identifiers and states without losing history.
Reference design to discuss with your supplier
Confirm the arrangements, implementation stages and official interfaces available for your operation before contracting or configuring an integration. This flow is a control recommendation, not an officially approved specification. For CBS, see Decree 12,955/2026, arts. 28–35.
order → tax document → receivable → payment instruction → settlement response → tax/accounting reconciliation
Record identifier, date, amount, version and status at each step. The ERP records the business event; the issuer proves the document; the financial provider proves settlement; reconciliation explains differences.
Design requirements
- Idempotency: duplicate responses update a transaction without duplicating clearing or entries.
- Granularity: one invoice may have several installments; one payment may cover several invoices. Do not assume a one-to-one relationship.
- Versioning: reconstruct historical transactions with the tax rule, layout and integration version actually used.
- Observability: failures need contextual alerts, not just technical log lines.
- Reversal: cancellation, returns, chargebacks and overpayment need their own states and approval trail.
Three integration decisions
Synchronous or asynchronous: authorization may be immediate, while financial responses arrive later. A pending state is not necessarily a final error.
Internal or external tax engine: document who calculates, who maintains versions and which value prevails in a discrepancy.
ERP or dedicated reconciliation layer: choose based on preservation of identifiers, exceptions and entries, not the convenience of the first screen.
Acceptance-testing sequence
- Prepare relevant regimes, destinations and payment methods.
- Calculate expected results independently of the integration.
- Transmit and capture payloads without unnecessary personal data.
- Check documents, settlement, segregation and accounting.
- Resend responses to test idempotency.
- Interrupt a step and validate recovery.
- Reverse the transaction and prove the reverse chain.
Ask the supplier which identifier links invoice and transaction; how partial payments, batches, delays and duplicates are handled; how long responses and versions remain available; whether the test environment reproduces production states; who corrects rejected data and within what period; and how the audit trail can be exported.
For business criteria, see the split-payment checklist.
Official sources
- Decreto 12.955/2026
- Lei Complementar nº 214/2025 — arts. 31 a 35, texto compilado
- Receita Federal — Programa da Reforma Tributária do Consumo
Editorial update: 14 October 2026. Confirm the official rules and technical versions applicable to your operation.
Sources and references
Accounting, tax and legal analysis for business decisions.
VMAHUB connects accounting, tax and legal work with business risk analysis and decisions. The next step is to understand how this topic applies to your operation and which documents support the assessment.