Payment posting and synchronization
Learn how Zuora posts matched payments and adjustments automatically or manually to ERPs like NetSuite, Dynamics 365, or SAP.
Once payments are matched to invoices in Zuora, you can post the payments and related adjustments to your ERP automatically through an application programming interface (API) or manually.
The posting process provides the following outcomes:
-
Each payment, invoice, and adjustment is reflected correctly in the ERP.
-
Accounting integrity is maintained across Bank, Receivables, and Adjustment accounts.
-
Posting rules follow your organization's Chart of Accounts and currency preferences.
Posting flow summary
-
Match and review payments: Use Smart Match AI to match payments to invoices and validate the matches.
-
Trigger posting: Start posting automatically through a scheduler or manually in Zuora when the payment is ready.
-
Create a payment entry: Zuora creates a customer payment entry in the ERP for the total applicable amount, including the received amount and payment adjustments.
-
Apply invoices: Apply the matched invoices to clear accounts receivable balances.
-
Record adjustments: Post adjustments such as bank charges, tax deducted at source (TDS), and write-offs as separate ledger lines.
-
Confirm posting status: Zuora receives a success or failure response from the ERP and updates the posting log.
Adjustment types
-
Payment Adjustments: Affect payment total but not invoice (e.g., bank charges, forex loss). Booked as separate journal lines, usually under Expense or Bank Fee accounts.
-
Invoice Adjustments: Affect invoice balance (e.g., TDS, write-offs, discounts). Included in invoice clearing; mapped under Adjustment or Receivable Write-off accounts.
Scenario:
Received Payment = $265
Bank Charges = $5
Write-offs = $30 (across two invoices)
Applicable Payment = $270 (265 + 5)
ERP configuration and onboarding
-
Bank Account Mapping: Links Zuora bank to ERP bank GL account.
-
Adjustment Chart of Accounts: Defines ledgers for bank charge, write-off, TDS, etc.
-
Currency Handling: Determines if posting occurs in payment or invoice currency.
-
Tolerance Limits: Sets auto-apply rules for minor mismatches.
-
Subsidiary Mapping: Ensures correct entity tagging for intercompany accounts.
-
Deposit Workflow (NetSuite): Configurable as enabled/disabled.
Supported ERPs and connectors
Zuora supports both standard (default) and custom ERP integrations for posting payments, adjustments, and journals.
-
NetSuite(Standard): Native connector supporting Customer Payment, Journal Entry, and Deposit workflows.
-
QuickBooks(Standard): Standard integration for Customer Payment posting and invoice settlement.
-
Zoho Books(Standard): Standard integration for Customer Payment posting and invoice settlement.
-
Zoho Invoices(Standard): Standard integration for Customer Payment posting and invoice settlement.
-
Sage X3(Standard): Supported via standard API; Certain complex Parent–Child workflows and Adjustments can vary.
-
Microsoft Dynamics 365 Finance & Operations (Custom): Full posting flow for Customer Payment and Journal creation.
-
Microsoft Dynamics 365 Business Central(Custom): Full posting flow for Customer Payment and Journal creation.
-
SAP Business One (SAP B1) (Custom): Full posting flow for Customer Payment and Journal creation.
Intercompany posting (NetSuite)
When a split payment applies to invoices that belong to different subsidiaries, Zuora posts it so each subsidiary's books stay balanced, rather than posting the whole amount against the paying subsidiary.
The paying (primary) subsidiary posts a deposit for its own share, plus a consolidated "due to" line for each other subsidiary involved.
Each other (secondary) subsidiary posts its share as a zero-balance deposit, offset by a "due from" line — netting that subsidiary's entry to zero while recording what it owes the primary.
This keeps an audit trail of inter-subsidiary balances and ensures each subsidiary's ledger reconciles.
Availability & prerequisites:
NetSuite only; applies to non-lockbox split payments in this release.
Requires Split Payment with subsidiary splitting enabled, and a per-subsidiary configuration of the deposit account and the due-from / due-to accounts.
Single-subsidiary splits and other ERPs are unaffected.