CINC Systems: Recurring Assessment Charges Not Posting Checklist

Most recurring assessment charges in CINC fail to post because the assessment rule is not active for the correct date range, not assigned to the right owners/units, blocked by a posting lock or approval workflow, or the batch job that generates charges did not run or errored. Check the assessment setup, the posting calendar/locks, the owner/unit status, and the posting log; then re-run or manually generate the charges for the missing period.

 

Confirm the assessment rule can actually generate charges

 

• Active status: Verify the recurring assessment is marked active and not ended.
• Start date and frequency: Make sure the start date is on or before the missing month, and the frequency matches (monthly/quarterly/annual).
• Next run / next charge date: If it shows a future date, the system thinks it already posted the missing period or the schedule is misaligned.
• Amount and GL/account mapping: Confirm the charge amount is not zero and it is mapped to the correct income account. Wrong mapping can cause posting errors or send it to an unexpected ledger bucket.

 

Verify it is assigned to the right people and properties

 

• Scope: Confirm the assessment is applied to the correct association, building, unit type, or owner group.
• Owner/unit status: Charges often skip units marked inactive, transferred, or with a move-out/close date before the charge date.
• Ownership effective dates: If a unit changed owners, the charge may have posted to the prior owner or split rules may apply.

 

Check for posting locks, approvals, and “already posted” situations

 

• Accounting period lock: If the month is closed/locked, CINC may block new charges.
• Approval workflow: Some setups generate charges into a pending batch that must be approved/posted.
• Duplicate prevention: If a charge already exists for that period (even reversed), the system may refuse to create another. Search the unit ledger for the assessment code/description and the charge date.

 

Look at the generation/posting log and batch results

 

• Batch job ran: Confirm the recurring charge process executed on schedule.
• Error details: Common errors include missing GL account, invalid date range, locked period, or permission limits.
• User permissions: The user/service account running the process must have rights to create charges and post batches.

 

If everything looks correct but charges still do not post

 

• Test with one unit: Temporarily apply the assessment to a single active unit and run generation for a single date to isolate whether it is scope-related.
• Check time zone and “as of” dates: If the system date is ahead/behind, the run may target the wrong period.
• Integration conflicts: If charges are expected from an external billing tool, confirm the sync is connected and not paused; otherwise CINC will not create them.
• Escalate with evidence: Provide CINC support the association ID, assessment name/code, expected charge date, a unit that should have been charged, and screenshots of the rule plus the batch/log showing no run or an error.