Escriba Finanzas
Commercial product in active in-house development: SvelteKit + PostgreSQL RLS, Drizzle, multi-tenant credits, payments, and legal case files—migration from Classic ASP. Targeting publication and later commercialization (no customer-facing URL yet).
Desktop
Mobile
Summary
Escriba Finanzas is a commercial product in active development at Infomerx: an in-house multi-tenant application for credit operations, debtor tracking, payments, and workflows for legal case files, replacing a legacy Classic ASP system. The roadmap is publication first—a stable release people can adopt—then commercialization (pricing, packaging, and go-to-market) as the product matures. The focus here is architecture and delivery mechanics—sanitized UI captures below, not live financial data. There is no customer-facing URL linked yet; this page describes intent and stack only.
Technical notes
SvelteKit 2 with TypeScript, PostgreSQL with row-level security and team_id tenancy, Drizzle ORM, Vitest and Playwright for automated checks—business logic primarily in the SvelteKit / Node layer.
Challenge
Legacy stacks accrete rules and screens that staff depend on daily. A replacement must honour multi-tenant isolation, preserve audit-friendly flows, and make batch and transactional work faster and safer—without a risky big-bang cutover that freezes the business.
Technical notes
Migration work is documented alongside the codebase (database diagrams, old vs new system notes, staged rollout). Public portfolio copy stays at the pattern level: RLS, invitations, roles, and reporting surfaces—without exposing business identifiers or case narratives.
Approach
Single database, tenant-scoped data with RLS as the backstop; explicit team membership and roles; incremental delivery of modules (credits, debtors, payments, legal case files, reporting, expenses) so each slice can be validated before the next lands.
Technical notes
Application code ships with automated checks at multiple levels (unit, integration, and end-to-end). Database design and migration plans are maintained next to the product so the cutover from the legacy system stays traceable and reviewable.
Current build focus
- Multi-tenant core — Teams, invitations, ownership, and RLS-backed queries so tenant boundaries are enforced in the database—not only in UI guards.
- Operational domains — Credits, debtors, payment allocation and verification, daily expenses, and legal proceeding tracking—implemented as cohesive transactional flows rather than disconnected forms.
- Reporting slices — Payment and credit summaries and related exports where the legacy system relied on ad hoc spreadsheets.
- Migration runway — Documentation and staged strategy so Classic ASP behaviour can be mapped, retired, and verified systematically.
Technical notes
Development is in-house at Infomerx toward a shippable commercial offering; public portfolio language stays at the pattern level—no outcome claims about debt recovery or legal results and no sensitive financial-process detail.
Outcomes
Near term, success reads as safer operations and lower friction for early adopters: fewer inconsistent states, clearer team boundaries, and a codebase that can evolve with new regulatory or business rules. Longer term, the same foundation has to support publication-quality reliability and a path to commercial packaging. Quantitative impact stays internal until the product is live and metrics are stable enough to summarise responsibly.
Public access
Not published yet. Escriba is still in pre-release development; no customer-facing URL is linked from this case study while engineering and migration work continue toward a first public release.