- Identity. Legal name exactly as registered (it goes on invoices and contracts), a short name for screens, the registered address, the TIN. Contact email and mobile appear in invoice footers and on the portal.
- Payment methods. Add each way tenants can pay: GCash and Maya numbers, bank accounts, cash at reception. Each electronic method becomes a QR code on every PDF with the invoice number as the suggested reference. Order them as you want them shown.
- Numbering. A prefix (your initials, a year — or nothing) and the next number. Numbers never repeat or skip; voided invoices keep theirs. If you are moving from another system, set the next number above your last one so the sequence continues.
- Dates and the nightly run. The day of the month repeating invoices are raised, the days until due, and whether the run sends them or holds them as drafts for you to review. Start with drafts.
- Send a test. Make a test client with your own contact, raise an invoice, send it by both channels, scan every QR with your own wallet. Fix anything here, void the test invoice.
Per place overrides
A workspace with several places can give each its own payment details, logo and footer, so Sunset Villas' dues go to the association's account and Harbour Ridge's rent to yours. Numbering stays one sequence per workspace unless you choose a prefix per place.
Changing things later
Name, address, TIN and payment details apply to invoices sent from then on; sent PDFs are never altered. The next number can only increase. Changing the raising day takes effect from the next run and is logged.
Was this useful?
Thank you — that is what it was written for.
Describes the platform as it is today. Something out of date? Tell us. · help 0.71.0






