Finance operating platform · multi-entity

The recurring finance work across your entities, already done.

If you run several entities across QuickBooks, a POS, a booking system and a few banks, somebody spends every month moving numbers between them by hand. Flying Ledger reads those systems, does the accounting work they imply, and keeps the group picture current — so the close is shorter and the numbers are already right.

Not a demo — a conversation about where your finance hours actually go. We're taking a small number of paid founding customers with hands-on onboarding and direct access to the founder. There's no self-service signup, by design.

The problem

The complexity isn't the volume. It's the multiplicity.

Several legal entities. A POS in one, a booking system in another, payroll somewhere else, a bank account each. QuickBooks holds the accounting; those systems hold what actually happened; and the two only agree once a person has spent a week making them agree. That person is usually the owner, the controller, or a CFO who was hired to do something else — and the work comes back every single month.

What it does

The recurring work, done before you get to it

Most finance software reports on the accounting after somebody has done it. This is built on the opposite bet: the journals, the reconciliations and the schedules can be prepared from the systems you already run, and the reporting is a by-product of having done it properly.

🔁

Month-end revenue, posted for you

Event and prepaid revenue is read from your booking system, split by sales category through a mapping you control, and posted to QuickBooks as a balanced journal. Debits must equal credits before anything leaves, and a posted journal is recorded so it cannot post twice.

🧭

The group position, current

Cash, debt, revenue, net income and payables across every entity — with drill-through from any headline number to the transactions behind it. The parts always sum to the number you clicked.

🔗

Intercompany that ties out

Who owes whom between your own entities, as at any date, with a variance workbench for the difference. Group-wide net has to reach zero to eliminate cleanly, and the page tells you when it doesn't.

🧾

Payables and vendor reality

Every open bill per entity, aged, with the same supplier spelled five ways across three systems resolved into one. Vendor statements upload and reconcile line by line against your own records.

🏦

Treasury and lender-ready debt

Cash, cards and loans per entity, plus a debt-service coverage calculation documented in writing rather than buried in a formula nobody can audit.

📉

Revenue floor

The revenue level below which you stop covering what you must pay — derived from the obligations that don't care how trading is going, and tracked against actual revenue. Most revenue targets are ambitions. This is the opposite.

Control

Nothing posts to your ledger that you haven't seen

Mapped, not guessed
Every category, account and entity link is a mapping you own and can change. The system doesn't infer where revenue belongs — you tell it once, and it holds.
Approved before it lands
Journals arrive as proposals with an approval step. Balanced before export, recorded once posted so the same journal can't go twice.
Auditable afterwards
Drill from any figure to the documents behind it. Methodologies — how interest accrues, how coverage is calculated — are written down and reviewable, not buried in a formula.

This is the difference between an accounting action and an opaque AI suggestion. In a finance system, being able to show your working is the product.

AI and your data

A straight answer about what leaves your environment

The in-app assistant that answers questions about your figures sends no customer data to an external model. Document reading is different: when you upload a bank, card or vendor statement to be extracted, the document is sent, because reading it is the entire task.

We're building a single controlled gateway so every outbound call is classified and you can see exactly what an external model received. That work isn't finished, and we'd rather tell you that than claim data is anonymous — coded figures aren't anonymous, and a distinctive balance is a fingerprint.

Who it's for

Owner-operated groups, 3–15 entities

A strong fit
Three to fifteen entities, locations or operating units. QuickBooks Online as the ledger. At least one operating system — POS, booking, payroll, ecommerce. An owner, CFO or controller still holding it together in spreadsheets, with recurring intercompany, deferred revenue, accrual or close work.
Where we started
Hospitality and venue groups — built in one, in production daily. The same shape fits multi-site fitness and wellness, medical and clinic groups, and multi-location service businesses. Live integrations today: QuickBooks Online, Toast, Tripleseat and Plaid. New ones get built when a customer needs them, not speculatively.
Probably not for you if…
You're a single company with clean books, you already run an enterprise ERP with a finance and IT department behind it, or you want a plug-and-play app with no implementation. Setup is real work and we'd rather say so now than discover it together in month two.

The Founding Customer Program

Paid from day one, and deliberately small

A 30-minute problem discussion. Your entities, your systems, and where the recurring hours actually go. If it isn't a fit, we'll say so on the call.
Hands-on onboarding. We connect your systems, classify your chart, and map your entities with you. Intentionally manual where it needs to be — this is not a signup flow.
Direct line to the founder. Founding pricing held for twelve months, in exchange for monthly feedback and permission to measure the hours removed.

Indicative pricing while we learn: roughly $2,500–$5,000 to set up depending on entity count, integrations and data cleanup, then $1,500–$3,000 a month per group rather than per seat. We're testing the relationship between implementation effort and finance hours removed — so the number may move, and it will be agreed with you before anything starts.

FAQ

Common questions

Is it live, and can I sign up today?

It's in production daily on a real multi-entity group, and it posts real journals to real books. There's no self-service signup — onboarding is hands-on and by invitation while the customer set is small. The way in is a conversation.

Why is it paid if it's early?

Because a free pilot tells us nothing. We'd rather have three groups who pay and tell us the truth than a hundred free accounts nobody uses. You get founding pricing held for a year and a direct line to the person building it.

We already have QuickBooks — why this?

QuickBooks holds the accounting. It doesn't know what your POS or booking system did, and it won't reconcile your entities against each other. Flying Ledger does that work and posts the result back, so the books are current instead of rebuilt each month.

Does it replace our accountant or CFO?

No. It removes the recurring preparation work — the journals, the reconciliations, the schedules — so the people doing it spend their time on the decisions instead. Every posting still goes through an approval you control.

What if you don't integrate with our systems?

Then say so on the call. Live today: QuickBooks Online, Toast, Tripleseat and Plaid. We build a new integration when a real customer needs it — which means it's a scoping question, not an automatic no.

How much of our time does onboarding take?

More than an app install and less than an ERP. Entities, connections, chart mapping and the historical periods you want loaded. We do the work with you rather than sending a checklist.

Where do your finance hours actually go?

Thirty minutes on your entities, your systems and the work that comes back every month. If we're not a fit, you'll get a straight answer rather than a follow-up sequence.