Duplicate entry
The same information traveled through messages, files, and spreadsheets.
Residential operations · Product design & development
From scattered payments to clear, 24/7 residential treasury
We designed a platform connecting residents and treasury from payment submission through validation, receipt generation, and future access.
Parque Residencial El Faro · Los Planes de Renderos, El SalvadorResident portal and treasury operations workspace
Residencial El FaroResident portalTF
Welcome to your unitHome 32
Account statusUp to dateNo outstanding balance
My receiptsDemonstration data
REF-2026-020Payment approved
REF-2026-019PDF available
Residencial El FaroDigital receipt
REF-2026-020Payment approvedValidated by treasury
UnitHome 32ConceptResidential dues
PDF availableDemonstration data
9393 connected units
93residential units
24/7resident self-service
48 / 45homes and lots
322 hmodeled annual capacity
* Savings are a capacity estimate based on 84 monthly payments and visible assumptions; they are not an audited measurement.
The context
A 93-unit community needed an operation built to its scale.
Every payment arrived with data from different channels: resident, unit, concept, month, amount, reference, and proof. Treasury had to reconstruct that information before validating it, updating controls, and delivering a receipt.
The administration repeatedly had to answer:
- Which unit does this payment belong to?
- Has the proof been validated?
- What balance is still due?
- Where is the previous receipt?
The challenge
Payment was only the beginning of the administrative work.
Identifying the unit, classifying evidence, updating balances, numbering the receipt, and answering questions formed a manual chain that was difficult to scale.
Scattered documents
Payment evidence and receipts could become separated from the unit history.
Limited self-service
Checking status, balances, or receipts depended on treasury availability.
The solution
Two experiences connected by one financial source of truth.
Residents submit and check; treasury validates and controls. Every payment keeps its unit, concept, proof, status, and receipt throughout the process.
Connect
Residents request access to their home or lot.
Submit
They choose period and concept, then attach evidence.
Validate
Treasury reviews, approves, rejects, or corrects.
Access
The receipt and history remain available 24/7.
The product
Designed for residents and the people looking after the books.
The experience simplifies frequent tasks without losing the controls required for financial information and private documents.
Payment submission
A structured form by unit, concept, period, and payment evidence.
Treasury inbox
Everything needed to validate a payment in one view.
PDF receipts
Numbered, stamped documents available immediately after approval.
Balance by unit
Dues, overdue balances, debt, credits, and fees in one financial profile.
History and exports
A timeline for every unit and data ready for administrative analysis.
Permissions and audit trail
Role-based actions and a record of sensitive operations.
Before and after
From message-based follow-up to continuous resident service.
BeforeWith the portal
Data sent through separate channelsA form connected to each unit
Payment evidence classified manuallyFiles automatically linked to payments
Receipts prepared and sent one by onePDF generated and available on approval
Statements requested from treasurySelf-service available at any time
Audits based on messages or memoryA trail of administrative actions
Treasury time
Central scenario · 84 payments per monthHow much work was hidden inside every payment?
The scenario estimates the time needed to identify the resident, update what they owed, prepare the receipt, and make the document available. These are not audited metrics; they are conservative operating assumptions.
estimated manual process22 min
estimated digital workflow6 min
capacity released16 minfor every payment
Treasury taskBeforeWith the portalTime released
Identify payment, resident, and unit4 min1 min3 min
Record payment and update the balance6 min1 min5 min
Prepare and number the receipt8 min1 min7 min
Deliver or archive the document4 min3 min1 min
Central scenario · 84 payments per month≈ 27 administrative hours per month≈ 322 hours · 40 workdays per year
* Illustrative estimate based on 93 units and approximately 90% monthly adoption. Actual results depend on volume, adoption, and the treasury process.
Technology
An architecture prepared for financial information and private files.
Next.js and React connect the protected experience with portal services. PostgreSQL stores residents, payments, balances, and audit data; Cloudflare R2 keeps evidence and receipts outside the codebase.
Next.jsReactTypeScriptPostgreSQLPrismaClerkCloudflare R2Vercel
Control and traceability
- Authenticated sessions and protected routes
- Separate permissions by role
- Each user can only access their own information, never another user's private data
- Private files with temporary access
- Audit trail for approvals and changes
Orbi Labs
Is your organization still managing payments and documents manually?
We design digital products that turn complex operational processes into simple, secure, measurable experiences.
