yukesh4349/finora-ai

Purpose and entry points

Finora AI is a retail-finance platform combining POS checkout, inventory, vendor invoice processing, fraud checks, reporting, and role-specific operations. The React/Vite client starts at frontend/src/main.jsx and routes through frontend/src/App.jsx. The Express REST API starts at backend/index.js; root scripts orchestrate both runtimes via package.json.

Client application and user workflows

The frontend provides public/authentication views plus focused operational screens for owners and staff. Dashboard composition is centered on business-owner analytics, invoice upload, invoice creation/POS, and specialized embedded modules.

• frontend/src/pages/BusinessOwnerDashboard.jsx

• frontend/src/pages/UploadInvoiceFullPage.jsx

• frontend/src/pages/CreateInvoiceFullPage.jsx

• frontend/src/components/dashboard/PosBillingModule.jsx

• frontend/src/components/dashboard/AiAssistantModule.jsx

Client-side service boundaries separate REST calls and direct Supabase access/configuration:

• frontend/src/services/api.js

• frontend/src/services/supabaseClient.js

• frontend/src/services/postgresDb.js

API composition and authorization

backend/index.js is the API composition root, mounting domain route modules. Authentication and role enforcement form the security boundary before protected financial, inventory, and employee operations.

• backend/routes/auth.js

• backend/middleware/rbac.js

• backend/routes/dashboard.js

• backend/routes/settings.js

Primary route domains split responsibilities across vendors, expenses, payments, transactions, employee/payroll, analytics, and reporting:

• backend/routes/vendors.js

• backend/routes/expenses.js

• backend/routes/payments.js

• backend/routes/reports.js

Invoice intelligence and fraud-control pipeline

Vendor invoice ingestion is a core write path: uploaded document data is scanned through NVIDIA Nemotron Vision with Tesseract fallback, converted into structured invoice/items data, then evaluated for duplicate/anomalous bills before downstream storage and inventory updates. AI assistant requests are exposed separately from document OCR.

• backend/routes/invoices.js

• backend/routes/ai.js

• frontend/src/pages/UploadInvoiceFullPage.jsx

This boundary depends on file upload handling, NVIDIA AI credentials, and potentially outbound webhook processing; document extraction should remain server-side because it uses privileged external AI credentials.

POS, sales, and inventory synchronization

Checkout flows originate in the POS UI, submit customer bills/sales through the API, and deduct stock. Vendor-invoice saves move in the opposite direction by increasing or updating inventory, supplier pricing, MRP, and low-stock state.

• frontend/src/components/dashboard/PosBillingModule.jsx

• backend/routes/customer_bills.js

• backend/routes/inventory.js

• backend/routes/invoices.js

Financial effects are represented through dedicated transaction and payment interfaces rather than being confined to UI state:

• backend/routes/transactions.js

• backend/routes/payments.js

Persistence, runtimes, and external services

Node.js/Express is the backend runtime; React 18/Vite is the browser runtime. PostgreSQL is the system of record through Supabase, with a dual database adapter and SQL schemas defining relational persistence. Supabase credentials include an elevated service-role path, so backend-only usage is a material trust boundary.

• backend/db.js

• backend/supabase_schema.sql

• backend/schema.sql

External dependencies include Supabase PostgreSQL, NVIDIA Nemotron Vision, Tesseract OCR, and configured webhook endpoints. A local fallback dataset exists at backend/data.json, likely supporting development or degraded persistence.