Invoicing & ERP Platform

Overview

A Dominican Republic-based SaaS company built their invoicing and ERP platform on Lovable but needed to decouple from Lovable's managed cloud infrastructure. They wanted full control over their Supabase backend while continuing to develop the frontend through Lovable.

I migrated their entire backend to an external Supabase instance — 81-table PostgreSQL schema with Row Level Security, 17 Edge Functions covering payments, tax compliance, and notifications — and verified end-to-end functionality.

Key Features

• 81-table PostgreSQL schema covering invoicing, inventory, payroll, accounting, and restaurant management
• Supabase Auth with role-based access control (owner, admin, manager, user) and Row Level Security policies
• 17 Edge Functions: payment processing (Azul, PayPal, Stripe), DGII electronic invoicing, RNC taxpayer lookup, email notifications, team management
• Multi-company architecture with subscription tiers and usage tracking
• DGII NCF (fiscal receipt) sequence management for Dominican Republic tax compliance
• Automated journal entries, bank reconciliation, and financial reporting

Technical Challenges

• Lovable project had no existing Supabase connection — schema had to be verified against 66 migration files and validated table-by-table
• Edge Functions required Supabase CLI deployment with proper access token configuration on a remote VPS
• RLS policies with security-definer functions to prevent infinite recursion on role checks
• Environment variable configuration to switch from Lovable Cloud to external Supabase without code changes

Tech Stack

Outcome

Completed the full migration — schema verification, Edge Functions deployment, and build validation — within a single session. The client now has an independent Supabase backend with full control over their data, authentication, and serverless logic, while continuing frontend development on Lovable without cloud lock-in.