Case studies / Interlix
From messy income statementsto curated insights in minutes.
Interlix places Latin American talent with US companies. It bills on the 28th, collects one to two weeks later, and pays talent around the 2nd of the following month. Standard QuickBooks reports told a different story every month-end.
The situation
The books were correct. The reports were not useful. Because revenue is recognized on the 28th, cash arrives in the next month and payroll follows a few days later, a P&L by calendar month split every cycle in half. Receivables never showed what was billed against what had actually been collected. The owner exported to spreadsheets and re-dated by hand.
The brief was explicit: no new data entry. QuickBooks stays the system of record. Just show the same data ordered the way the business actually breathes.
What we built
- A production OAuth connection to QuickBooks Online. Authorized once by the owner; tokens encrypted at rest and refreshed automatically.
- Automation end to end. A daily sync at 09:00 UTC pulls the books, applies the rules and refreshes every view; every pull is logged, and a manual sync is one click away when a period is being closed. Nobody exports anything.
- Re-dating rules per account. The owner defines how each account should be shifted (billing, collection, payroll). The engine applies them to build the statements; the rules are visible and editable, never hidden in code.
- Three statements, built as BI views rather than exports. P&L on the re-dated basis, receivables as billed versus collected with open A/R by customer, and a month-end balance sheet on an accrual basis, cached for speed. Each is a page the owner reads, not a file the owner assembles.
- A password-protected portal on infrastructure Arlem operates, with Postgres, backups and monitoring. Nothing to install, nothing to export.
The next phase under discussion connects worked hours (from the time-tracking tool) to a signed approval flow and then to invoices in QuickBooks, closing the loop from hours to cash.
How it runs today
The owner opens the portal and sees the month as the business experienced it. Month-end no longer starts with an export. When the accountant asks a question, the answer and the rule behind it are on the same screen.
| Before | After |
|---|---|
| Calendar-month P&L split every billing cycle | P&L re-dated by per-account rules the owner controls |
| Receivables read from invoice lists | Billed vs collected, open A/R by customer |
| Manual exports and spreadsheet re-dating | Daily automatic sync, manual sync on demand |
| Balance sheet requested from the accountant | Month-end accrual balance sheet, cached in the portal |
Stack: QuickBooks Online API (OAuth 2.0), FastAPI, Postgres, server-rendered BI views, scheduled sync, Caddy and pm2 on Hetzner.