Yardi Breeze: Fix Online Payments Not Syncing to General Ledger

Online payments usually fail to sync to the General Ledger in Yardi Breeze because the payment is not posted, the cash account mapping is wrong, the payment is sitting in an undeposited/batch state, or the integration/export step did not run. Check posting status, bank/deposit workflow, GL account mapping, and whether the payment is tied to the correct property/unit and charge code. If all settings look correct, re-run the sync/export, confirm the payment batch is closed, and compare the payment register to the GL to find the exact break point.

 

Fast checks that fix most cases

 

• Confirm the payment is actually posted (not just “received”). Unposted items will show in payment activity but won’t hit the GL.
• Check deposit/batch status. Many setups only create GL entries when the payment is included in a deposit or batch that is closed.
• Verify the cash/bank GL account mapping for online payments. If the system doesn’t know which bank account to debit, it may hold the entry or send it to a default/clearing account.
• Look for a clearing/undeposited funds account. Online payments often post to a clearing account first, then move to the bank account when deposited.

 

What to check inside the configuration

 

• Payment method mapping: Online ACH vs card can map to different GL accounts and fees. Make sure each method has a defined GL path.
• Charge code / income account mapping: The payment must apply to a charge (dues, assessment, late fee) that is mapped to an income GL account. If it’s applied to an unmapped charge code, posting can fail or go to “misc/unknown.”
• Property-level settings: If multiple properties exist, confirm the payment was made under the correct property and that property has the correct bank account and GL accounts assigned.
• Posting period: If the accounting period is closed, Breeze may block posting or hold it for the next open period.

 

How to validate where the sync broke

 

• Start from the payment record: confirm payer, unit, amount, date, method, and what charges it applied to.
• Check the deposit register: verify the payment is included in a deposit and the deposit is finalized.
• Check the GL detail: search the date and amount. If missing, it’s not posted. If present but wrong account, it’s a mapping issue.
• Compare totals: payment register total for the day vs GL cash activity for the day. The difference usually points to one batch or one property.

 

If everything is correct but it still won’t sync

 

• Re-run the sync/export step (if your workflow uses an export to accounting). Some entries do not push until the export is triggered.
• Check for duplicate/void/reversal: a payment can be received, then reversed by a failed settlement, chargeback, or void, leaving no net GL entry.
• Look for fee handling: processing fees may post separately. If fees are unmapped, the whole journal can fail.
• Browser/VPN issues: if staff used a VPN or had session timeouts, the payment may be recorded but the posting step didn’t complete. Re-open the transaction and confirm status.

 

When to contact Yardi Breeze support

 

• Payments show “settled” with the processor but never create GL entries after posting/deposit is confirmed.
• Error messages about accounting export, journal creation, or permissions.
• Only one payment method fails (ACH works, cards don’t, or vice versa), suggesting a processor or method mapping issue.