Accounting · Connected system
ElliHub Finance
Supabase · PostgreSQL + RLS · partner-built
Everything after the award that turns into money — requisitions, vendor invoices, job cost, retainage — is ElliHub Finance's domain, a dedicated system its own team is building on Supabase. The Hub doesn't rebuild any of it; this page is its front door, alongside estimating and the field.
Wired in the integration phase
ElliHub Finance connects here
The finance team's system renders inside this frame under its own URL once the SSO handshake is wired in the integration phase — one sign-in carries from the Hub into Supabase Auth. Nothing in this viewport is mocked; it stays empty until the real ledgers arrive.
Data exchange
What flows between
A two-way contract: the Hub hands ElliHub Finance the contract paper it bills from, and Finance hands back the money truth every PM tab wants to quote. One schema, co-signed by both teams.
The Hub sends ElliHub Finance Executed COs, Approved pay apps, SOV schedule. ElliHub Finance returns Payment status, Invoice aging, Job-cost rollups to the Hub.
Example payload · pay-app sync
Demo data- revised_contract
- $1,415,200
- current_payment_due
- $373,239REQ-004
- retainage_held
- $93,608
- reference
- BID-1247 · FW #31247
Same figures the SOV and Pay Applications tabs carry — one demo dataset, so both systems already agree by construction. The live contract is field-level and co-signed by both teams before a single row moves.
Inside the system
What lives in ElliHub Finance
Four ledgers the finance team owns outright. The Hub links to them and quotes their rollups — it never re-implements them. Footers show the Tisch figures their ledgers will carry.
- AR / AP
Receivables & payables
Both sides of the money in one ledger — every requisition Ellicorp submits to a GC, and every vendor invoice the shop owes for laminate, hardware, and veneer, aged and matched.
Open receivableREQ-004 · $373,239 - Job cost
Cost against contract
Cost codes posted against the revised contract, so the office sees casework, paneling, and install labor burning against budget while there's still time to steer — not after closeout.
Tisch revised contract$1,415,200 - Retainage
Held-dollar tracking
The 10% the GC holds on every requisition, tracked line by line — with the release math already staged for substantial completion, when those dollars come home.
Held on Tisch to date$93,608 - Payments
Payment status
Where every dollar stands — submitted, approved, funded — reconciled against the GC's payment record, so nobody spends a Friday chasing a check that already cleared.
Paid to date on Tisch$469,233
Integration handoff
Three milestones to live
What stands between this page and live ledgers — each ships in the integration phase, co-owned by the Hub team and the ElliHub Finance team.
- MS-01Pending
SSO handshake
One sign-in. The Hub's session exchanges into Supabase Auth so the embed above opens already authenticated — no second login for Peter or the PMs.
Hub team + ElliHub Finance team · integration phase
- MS-02Pending
Data contract
The field-level schema both teams co-sign: executed COs, approved pay apps, and the SOV schedule flow out; payment status, invoice aging, and job-cost rollups flow back. No row moves before both sides sign.
Co-signed schema · integration phase
- MS-03Pending
Embed
ElliHub Finance renders in the frame at the top of this page under its own URL, full-bleed. Depends on MS-01 and the finance team's frame-ancestors policy; ships with the SSO wiring.
Depends on MS-01 · integration phase
How this connects
Data flows from ELLI HUB (Pay apps, Change orders, SOV) through the co-signed data contract into the Finance sync skill, which posts to ElliHub Finance ledgers.
Demo data — the Finance sync skill ships in the integration phase, behind a data contract co-signed with the ElliHub Finance team. Until both teams sign the field-level schema, no row moves in either direction.