Supporting Documentation · Nov 4, 2026
293-26 Corrective Action Plan.pdf
3aab4009b7115ff5b35656526457280a89c7b2057930dcb75086e61b68bc3e0fIndexed text · page 10
Show all pagesAn example transacƟon is shown below: The AdministraƟon Department accepts a check for Bid SpecificaƟons in the amount of $100.00. A representaƟve of AdministraƟon will record the transacƟon in Community Pass with the Appropriate Point of Sale code. A summary report along with the check will then be turned over to the Tax Office. The Finance Department then has the responsibility to export the previous day’s Community Pass TransacƟons to a csv. File, load that file into Cloud Munidex, confirm the debit and credit posƟng, and then post the entry. The entry for the example above would post as follows: Debit – Departmental Deposit in Transit – AdministraƟon - $100.00 Credit – Miscellaneous Revenues Not AnƟcipated – Bid Specs - $100.00 The Tax Office will then record the check in the Legacy Munidex Tax system and deposit the check into the bank. Through an overnight, automated process, the Legacy Tax entry will post to cloud Munidex and create the following entry: Debit – Cash – Current Fund - $100.00 Credit – Departmental Deposit in Transit – AdministraƟon - $100.00 A mulƟ-step, mulƟ-system process adds unnecessary complexity and requires oversight beyond the staffing limitaƟons of the Department. The Finance Department is in the final stage of implemenƟng a unified cash receipƟng/revenue recording with Edmunds GovTech. Tax and UƟlity was converted on 7/1/2026 and the rest of the operaƟon goes live on 1/1/2027. 4. ImplementaƟon Date: 7/1/2026 and 1/1/2027
File revisions (1)
- Oct 31, 2026
3aab4009b711260,898 bytes