Enter quantities to establish the initial register balance.
Bills
Coins
Total: $0.00
Loading settings data...
Settings & Management
Customer Accounts
Showing 0 of 0 customers
Account
Customer
Property
Status
Amount Due
Codes
Actions
Property Locations
Premise ID
Property
Owner & Resident
Status
Actions
Sewer Charge
Set the default sewer service charge amount
Late Fee
Set the default late fee charge amount
PUC Surcharge
Set the PUC surcharge percentage (applied to all customers)
Tax Codes
Code Name
Type
Amount
Description
Requirements
Actions
System Users
Full Name
User Code
Title
Created
Actions
Data Cleanup
Tools to clean up and fix data issues in customer records
Test Date
Set a test date to simulate how the system behaves on different dates (e.g., when the month changes). Leave empty to use the real current date.
Using real current date:
Data Synchronization
Re-sync past due amounts from imported Excel data
Date Fixes
Fix Excel serial dates that appear as numbers (like 46053) in customer data
Cycle Number Assignment
Split all accounts evenly across cycles 1-10 (for testing purposes)
Credit Management
Reset all accounts with credits so that the credit is removed
Payment History
Reset all customers who have past payments so the data looks like they never paid any past payments
Drawers
Reset all drawers by deleting and recreating them, clearing count history and requiring new SOD counts
Deposit Management
Reset all customers' deposits back to $1000.00
Add Past Due Amount
Add $50.00 past due amount to account CUS-3000500
Payment Application Hierarchy
Define the order in which partial payments are applied to different charges. Drag items to reorder.
How it works: When a customer makes a partial payment, the payment will be applied in the order shown below. For example, if the order is "Past Due, Late Fee, Tax Codes, PUC Surcharge, Current Due", the payment will first go towards Past Due, then Late Fee, and so on.
Drawer Management
Manage cash register drawers. POS users will be prompted to select a drawer when they log in.
Drawer Name
Fund Value
SOD Status
EOD Status
Availability
Created
Actions
System Toggles
Configure system behavior settings
Ask for user code for each transaction
When enabled, POS users will be prompted to enter their user code every time they process a payment.
Skip POS initial register count
When enabled, POS users will skip the initial register count screen and go directly to payment processing. The initial count will be assumed to match the supervisor's start of day count.
After hours log out
When enabled, POS users will not be able to log in during the specified time range. This helps enforce after-hours restrictions.
POS Doesn't Close Out
When enabled, the "Close Out Drawer" button will be hidden for POS users, preventing them from closing out their drawer.
Use username instead of user code
When enabled, supervisors will not be asked to enter their user code when closing out a drawer. Instead, the system will use their logged-in username.
Customer Accounts
Account
Customer
Property
Status
Amount Due
Due Date
Last Payment
Actions
Property Locations
Premise ID
Property
Owner & Resident
Status
Actions
Add New Customer
Add New Location
Add System User
Record Payment
Customer:
Current Balance:
Payment History -
Date
Amount Due
Amount Paid
Remaining Balance
Amount Breakdown
Customer:
Factor1.0
Due Date--/--/----
Billing Cycle--/--/-- - --/--/--
Last Payment DateNever
Last Payment Amount$0.00
Last Amount Due$0.00
Sewer Charge
$0.00
Charge Codes
$0.00
Late Fee
$0.00
Past Due
$0.00
Current Due$0.00
Past Due$0.00
Credit$0.00
Late Fee$0.00
Total Due$0.00
Edit Field
Tip: For status, use "available" or "occupied". For residents, use "Available" to make the property available.
Import Locations
JSON Format: Your file should contain a "locations" array with objects having properties like id, address, propertyType, bedrooms, bathrooms, squareFootage.
Sample: You can use the provided locations.json file as a template.
Import Customer Data
Note: All data from the Excel file will be imported and saved to Firebase. The first row should contain column headers. The system will match customers by account number if they already exist, or create new ones.
