Where every peso is traced
from member to ledger.
A custom-built core banking platform for LKBP — integrating Loan, Tellering, and Accounting into one system of record. Owned by LKBP. Hosted on Amazon Web Services under your account. Engineered to the gravitas required of a Philippine financial cooperative.
Sandigan sa Kagipitan,
Katuwang sa Kabuhayan.
LKBP is a 10-branch cooperative serving members across Bulacan, Pampanga, Nueva Ecija, and Bataan — through four core products and a network of allied services. This proposal extends that mission into a digital backbone worthy of it.
Loans
Deposits
Share Capital
Insurance
What we've heard from cooperatives like LKBP
- › Branches operate semi-independently — head office sees consolidated reports days late.
- › Loan applications take days; collectors carry paper ledgers from house to house.
- › Tellers reconcile by hand at end-of-day; month-end close stretches into weeks.
- › Members travel to branches just to check a balance or apply for a small loan.
Your current system was built
for a different decade.
The present operational environment of LKBP exhibits limitations across two layers. The first is infrastructural — the underlying software was not engineered to be extended, integrated, or aligned to LKBP's evolving reporting requirements. The second is operational — daily work is impeded by these limitations, and the combination produces a residual risk of legal exposure arising from incorrect entries and report inconsistencies, which the proposed system is engineered to eliminate.
Legacy infrastructure that's hit its ceiling
The current system was built years ago and can no longer be extended, ported, or scaled. Every limitation below is costing LKBP money or members right now.
Microsoft officially retired IE in June 2022. There are no more security patches, no modern browser support, and every workstation has to keep a deprecated browser alive just to log in.
No way to build a member mobile app, an ATM/remittance tie-up, or feed data to a regulator. The current vendor's stack is a black box.
The system is too old to migrate or expand. Adding a feature means waiting for the original vendor — or starting over entirely.
Officers and managers are tied to a single workstation. Operations on the branch floor and within meeting rooms cannot benefit from a portable interface.
Aging, portfolio at risk, branch consolidations, BIR / CDA filings — assembled by hand from exports and spreadsheets. Hours per report, days per month-end.
The present software produces output in a generic format that does not align with what LKBP must publish for the Board, the General Assembly, the CDA, and the BIR. The Cooperative is therefore obliged to reassemble reports manually each period — introducing transcription error and a window for inconsistency between source data and published figures.
End-users may select an incorrect loan type at entry. For example: a Personal Loan (₱4,000–₱300,000, up to 36 months) recorded as a Petty Cash Loan (₱1,000–₱5,000, 2 months). Different rules, different amortization, different income recognition — the misclassification propagates into the ledger, the SOA, and the financial statements.
A modern web-based system that scales with you
Every limitation above becomes a non-issue under our stack. The system is the website — log in, do your work, log out. That's it.
Chrome, Safari, Edge, Firefox — even on a phone. Auto-updates with the browser. No special software, no installer, no IE.
Mobile app, ATM tie-up, GCash/remittance partners, BSP/CDA connector — all already possible. Auto-generated OpenAPI docs included.
Laravel 13 + Vue 3 + PostgreSQL — the same stack thousands of teams worldwide use. If anything ever happens to us, any competent Laravel team can pick up where we left off.
Operates on desktop, tablet, or mobile, with the same authentication, authorization, and audit applied identically on every device. Access is governed by RBAC, MFA, and the network controls LKBP elects to enforce.
Aging, PAR, branch consolidations — refreshed in real-time. Export to Excel, PDF, or BIR-ready format with one click. Month-end becomes minutes, not days.
All reports and statutory documents — Balance Sheet, Income Statement, Trial Balance, GL/SL, BIR forms, CDA Annual Report, internal management reports — are built to LKBP's exact required format. Templates are finalised during discovery and may be added or amended thereafter without code changes.
Each LKBP loan product (Agricultural, Negosyo, Enterprise, Asset Acquisition, Emergency, Back-to-Back, Petty Cash, Housing, Memorial Lot, Personal, Vehicle, Educational, Agricultural Fixed Assets) carries its own validated amount range, term, repayment frequency, and amortization formula. An incorrect classification cannot be saved. Every entry and every amendment is captured in an immutable audit log.
HTTPS over your current VPN layer — your existing network security remains in place. The new system adds modernisation; it does not displace protection.
IE-only PC maintenance across 10 branches, hours of manual report compilation every month-end, and the long-term cost of not being able to build a member app or accept partner integrations — adds up to a recurring overhead the new system eliminates.
API-first. LKBP-format reports.
Manual Loan Processing
Paper CIF, hand-computed amortization, no disclosure statements on file. Slow approvals, lost documents.
Tellering Friction
Manual blotter, spreadsheet reconciliation, error correction is painful, no real-time cash position.
Accounting Bottleneck
Month-end close takes weeks. TB, GL/SL, financial statements assembled by hand from teller logs.
Member Experience Gap
Members travel to branches just to check balances, apply for loans, or pay amortizations.
Multi-Branch Visibility
Bulacan, Pampanga, NE, Bataan operate semi-independently. Head office struggles to consolidate.
Compliance & Audit Risk
CDA reporting, BIR withholding, audit trails — reconstructed after the fact instead of recorded as you go.
Past-Due Blind Spot
Collectors lack real-time aging. Portfolio-at-risk visibility is days delayed.
No Foundation for What's Next
Without clean digital records, you can't launch a member app, ATM tie-up, or mobile collection later.
Three connected modules.
One system of record.
Built for the way cooperatives actually run — and engineered so a teller's receipt automatically becomes a loan ledger entry and a journal voucher, all in the same transaction.
- CIF / Member profile
- Application & approval workflow
- Loan-type rules enforced at entry
- Auto-computed amortization per product
- Disclosure statement & voucher
- Portfolio aging & Portfolio-at-Risk
- Collector daily list
- Restructuring & waivers
- Immutable audit log
- AR payment per collector
- Savings deposit & withdrawal
- Cash payout / disbursement
- Cash position (Hand / Bank / Vault)
- End-of-Day report & blotter
- Maker-Checker on disbursements
- Error correction with audit trail
- Multi-branch consolidated view
- Reports built to LKBP's preference
- Configurable Balance Sheet & Income Statement
- Trial Balance with drill-down
- General & Subsidiary Ledgers
- JV / CV entry (double-entry validated)
- BIR forms & CDA Annual Report
- Period close-and-lock controls
- Custom report builder
An in-house custom build —
owned by LKBP from day one.
NQB8 is engaged as an independent technology consultant to design, build, document, and hand over a complete information system. The system is yours; the source code is yours; the documentation is yours. NQB8's role concludes at handover, and the LKBP IT Department operates the platform thereafter.
- A consultancy engagement to design, build, document, and deliver a custom information system owned by LKBP
- A milestone-based engagement with an 8-month MVP delivery target
- A transfer of full source code, schemas, and documentation to LKBP at conclusion
- Custom-fit to LKBP's specific operational, reporting, and governance requirements
- Designed to be operated by the LKBP IT Department following handover
- Deployed on AWS Philippine-region infrastructure under LKBP's own AWS account
- A subscription to a third-party software product
- An open-ended retainer or perpetual managed service
- A licensing arrangement that retains intellectual property with NQB8
- A generic banking package adapted superficially
- A system that requires NQB8's perpetual involvement to function
- Hosted on infrastructure controlled by NQB8
All source code, database schemas, design assets, documentation, and ancillary deliverables shall be assigned to LKBP upon final payment. NQB8 retains no licensing fees, no ongoing access rights, and no claim to derivative works developed by LKBP after handover.
Validated entries, computed correctly,
traced to maturity.
| # | Due | Principal | Interest | Amort | Balance |
|---|---|---|---|---|---|
Maria Clara Santos
| # | Due Date | Principal | Interest | Amort | Balance |
|---|---|---|---|---|---|
| 1 | May 30, 2026 | 8,333.33 | 1,500.00 | 9,833.33 | 91,666.67 |
| 2 | Jun 30, 2026 | 8,333.33 | 1,500.00 | 9,833.33 | 83,333.34 |
| 3 | Jul 30, 2026 | 8,333.33 | 1,500.00 | 9,833.33 | 75,000.01 |
| 4 | Aug 30, 2026 | 8,333.33 | 1,500.00 | 9,833.33 | 66,666.68 |
| 5 | Sep 30, 2026 | 8,333.33 | 1,500.00 | 9,833.33 | 58,333.35 |
| 6 | Oct 30, 2026 | 8,333.33 | 1,500.00 | 9,833.33 | 50,000.02 |
| Member | Barangay | Due | Status |
|---|---|---|---|
| Maria Clara Santos | San Agustin | ₱4,250 | Pending |
| Carlito Mendoza Lim | Kaliwanagan | ₱6,750 | ✓ Paid |
| Lorna Diaz Buenaventura | Sipat | ₱3,200 | Pending |
| Rico Tolentino Cruz | Iba | ₱8,500 | Partial |
| Gloria Sandoval Reyes | Bulihan | ₱2,100 | ✓ Paid |
| Felipe Ocampo Robles | San Vicente | ₱12,400 | Pending |
| Angelica Ramos Salonga | Sta. Peregrina | ₱5,600 | Pending |
Record a transaction. The cash position
updates automatically — no manual reconciliation.
Reports built to LKBP's preference —
and traced from statement to source entry.
- Date
- Preparer
- Approver
LIGAS KOOPERATIBA NG BAYAN SA PAGPAPAUNLAD
Bookkeeper
Accounting Officer
General Manager
| Account | Debit | Credit |
|---|---|---|
| 1110 · Loans Receivable | 85,000.00 | — |
| 1010 · Cash on Hand | — | 85,000.00 |
| Payee | ATC | Amount | EWT |
|---|---|---|---|
| SBC Services Inc. | WC158 | 120,000 | 2,400 |
| Pampanga Power Corp. | WC020 | 85,000 | 1,700 |
| R. Cruz Office Supplies | WC158 | 42,500 | 850 |
| NetWorth IT Services | WC100 | 200,000 | 10,000 |
Built to the security expectations
of a Philippine financial cooperative.
The system is designed, built, and operated in alignment with the Philippine regulatory framework for financial-services information systems, supported by international best-practice standards. Security is led by NQB8's in-house cybersecurity specialist throughout the engagement.
Security architecture, configuration, and pre-launch verification are owned by a dedicated specialist on every NQB8 engagement — not delegated, not outsourced.
- Role-Based Access Control (RBAC) with least privilege
- Multi-Factor Authentication (MFA) mandatory for officers/admins
- NIST 800-63B password policy
- Maker-Checker on disbursements, JV/CV postings, period close
- Branch-level data isolation
- TLS 1.3 in transit · HSTS · Perfect Forward Secrecy
- AES-256 at rest · column-level encryption for PII
- AWS KMS-managed keys · separate backup key custody
- AWS Secrets Manager (no secrets in code)
- Immutable, append-only audit trail (user / timestamp / IP / before-after)
- Five (5) year retention — meets BSP & CDA requirements
- Centralised logs via AWS CloudWatch
- Alerting on failed logins, off-hours admin activity, anomalous transactions
- OWASP Top 10 (2021) mitigations implemented & documented
- Server-side input validation throughout
- SAST integrated into CI/CD pipeline
- Independent third-party penetration test prior to go-live
- Data subject rights workflows (information, access, correction, erasure)
- Privacy notices and consent management
- Personal data inventory documented
- 72-hour breach notification readiness playbook
- AWS VPC with public, private, and database subnets
- AWS WAF at the perimeter · AWS Shield for DDoS
- Rate limiting per source IP and per token
- Compatible with LKBP's existing VPN security layer
- Daily full + hourly incremental backups
- Cross-region replication within AWS Asia Pacific
- Documented RTO & RPO agreed during discovery
- Quarterly restore testing
- Documented incident response procedure
- Critical-severity acknowledgment within 1 hour during warranty
- Post-incident root-cause analysis report
- National Privacy Commission notification support
- Identity-verification at member onboarding (KYC)
- Configurable transaction-monitoring thresholds
- Suspicious Transaction Report (STR) generation
- PEP screening list integration available
- Implementation of all security controls listed above
- AWS infrastructure architecture & deployment under LKBP's account
- Independent third-party penetration test prior to go-live
- Data Privacy Act compliance operationalisation
- BSP Circular 982 control alignment
- Complete security documentation set
- ISO/IEC 27001 formal certification (alignment only)
- PCI DSS certification (not required unless cards processed)
- 24/7 Security Operations Centre (SOC) operation
- Recurring penetration testing (recommended annually)
- Production-environment day-to-day operations after handover
Documentation as a deliverable —
not retrofitted at the end.
The LKBP IT Manager and team receive a complete documentation set produced during development, in editable formats, in LKBP's perpetual ownership. The objective: any competent technical team — your IT department, or a successor — can operate, maintain, and extend the system from the documentation alone.
A complete knowledge transfer —
so LKBP runs the system independently.
Structured training is built into the engagement. The LKBP IT Manager and team are trained to operate, configure, and support the platform. End-users in every role are trained to use it confidently in daily operations.
A teller's receipt becomes a loan ledger entry
becomes a journal voucher —
in a single operation.
This is the difference between three apps duct-taped together and one system of record. Every peso flows through one transaction engine.
Teller posts
Loan Ledger updates
GL posts
Handover to LKBP — and a path forward
for the capabilities that come next.
At the conclusion of the engagement, NQB8 transfers full ownership of the system to LKBP and the operations of the platform pass to the LKBP IT Department. The system is engineered to function fully without NQB8's continued involvement. Should the Cooperative wish to extend our work to the next phase of capability, an optional consultancy retainer is available on terms acceptable to the CEO, the Management Team, and the Honorable Board.
One full month following operational acceptance, NQB8 remains available for defect remediation, configuration adjustments, and weekly post-launch office hours. Critical-severity issues are acknowledged within one (1) hour. The complete documentation set, source code, and training materials are formally handed over to the LKBP IT Manager during this period.
Should LKBP wish to extend the system's capability after the warranty concludes, NQB8 is pleased to continue under a consultancy retainer. Common Phase 2 directions:
- Member-facing mobile application — view balances, pay loans, deposit, view statements (iOS & Android)
- Payment partner integrations — GCash, Maya, BPI, Land Bank, partner remittance channels
- ATM & cash-agent tie-up — cardless deposits and withdrawals at partner locations
- Additional reports & analytics — branch performance, member behaviour, board dashboards
- BSP / CDA submission connectors — direct regulator filing where supported
- Performance & capacity enhancements as the membership grows
Twelve (12) months from contract execution
to go-live across all 10 branches.
The schedule is structured as eight (8) months of feature build, followed by three (3) months of dedicated data migration — the latter is given a full quarter because legacy-system data extraction, transformation, validation, and the end-user training required to assure data integrity demand more time than a typical migration, particularly given the present skill levels of staff working with the legacy software. A final one (1) month of stabilisation handles edge cases, customisation based on real-use feedback, and the formal go-live across all ten branches. Documentation is produced alongside every phase, not retrofitted at conclusion. AWS infrastructure is provisioned in M1 under LKBP's account.
Commercial particulars,
presented separately to the CEO and Honorable Board.
Investment & Contractual Particulars
Investment, payment milestones, and contractual particulars shall be presented to the CEO, the Management Team, and the Honorable Board of Directors in a separate engagement document, issued under cover of a Letter of Intent. Progress updates throughout the engagement are addressed to the CEO and Management Team at the cadence the Cooperative prefers. NQB8 shall be pleased to discuss any commercial question at a time and in a manner of the Board's choosing.
The same stack that powers
a national tour marketplace.
Battle-tested in production: multi-tenant, transactional, role-based, audit-logged. The exact shape of LKBP's needs.
A few items from the LKBP side
to enable a precise build.
A workshop team for discovery
A representative from each operational area — Loans, Tellering, Accounting — together with a single point of authority for sign-off. The workshop runs for one (1) week at the Head Office.
Required report templates
Samples of any reports already in use — Balance Sheet, Income Statement, management reports — in the format LKBP wishes the system to produce. Where no current template exists, formats will be co-designed during discovery.
Loan-product business rules
Confirmation of the current rules for each LKBP loan product — interest, service charge, amortization basis, term limits, collateral requirements. To be encoded as enforced validations.
Sample of existing data
Member CIF data, current loan ledger, sample teller blotter, last period's trial balance. Used to validate migration design early.
Coordination with the LKBP IT Manager
For AWS account setup, security configuration alignment, infrastructure decisions, and ongoing handover planning throughout the engagement.
Existing security & governance practices
Any policies, standards, or practices the Cooperative already observes — so the new system aligns from the outset rather than retrofitting them later.
Pilot branch nomination
One branch (we suggest Malolos HO) to go live first, ahead of the full network roll-out. Permits operational tuning before the broader deployment.
Sign-off authority for UAT milestones
A designated approver per module who is available to sign off acceptance within five (5) business days of delivery. Maintains schedule discipline.
To the CEO, the Management Team,
and the Honorable Board of Directors.
Upon receipt of a signed Letter of Intent, NQB8 shall commence the discovery workshop at LKBP's Head Office in Malolos. The workshop will produce the finalised functional specification, the agreed reporting templates, the validated loan-product catalog with business rules, the AWS deployment architecture, the legacy-system data migration plan, and a confirmed go-live date. Full delivery across all ten (10) branches is targeted within twelve (12) months of contract execution — eight (8) months of feature build, three (3) months of supported data migration with end-user training, and one (1) month of stabilisation before full go-live. Progress reviews and milestone sign-offs shall be presented to the CEO and Management Team throughout the engagement. The system passes into the ownership of LKBP at conclusion of the engagement, with one (1) month of warranty support included after go-live. Should the Cooperative wish to extend the engagement for a member-facing mobile application or other Phase 2 capability, an optional consultancy retainer may be arranged on terms acceptable to the Board.
Maraming salamat po.