Biloh documentation

A first run through Biloh's books: register three accounts, import a statement, reconcile in and out, check the envelopes, close the month and read the BAS.

A sent proposal is immutable. Supersede it with an amended copy that keeps the audit trail and redirects the client's original signing link to the new one.

Add an extra service you performed on the day with add_adhoc_service — it routes into the client's existing invoicing cadence automatically.

What happens to booked visits when you change a series' day or cadence: pending contractor confirmation, the hold badge, and the period guard.

Prove the bank feed is complete, lock the month's cash figures, roll the quarter up, and reopen with a reason when a late payment arrives.

Dispatch a job to a contractor, act on it from the Job Command Sheet, and clear what needs attention — overdue, missed, and unassigned work.

Move live clients off an old CRM one at a time — verify the entity, stand up the service, backfill completed work, and bill it without losing history.

Describe a client in plain words on the onboarding page and review a complete draft — nothing is created until you confirm.

Write a one-off note into an invoice, proposal or statement email, and read the byte-for-byte preview before the send is approved.

Read the quarter's BAS figures on the ATO labels, generate the one-ZIP pack for your accountant, and keep the compliance calendar lodged.

Match each deposit in the bank feed to the invoice it pays, handle the ones that are not invoice income, and teach Biloh the payer for next time.

Settle contractor bills against bank debits, code supplier spend with its GST evidence, pair receipts from the shoebox, and split mixed lines.

You printed the invoice, handed it over and were paid in cash. How to get that into the books correctly, dated when the money actually moved.

Set up the everyday, tax set-aside and contractor buffer accounts once, then bring each week's bank export into Biloh so nothing is missed.

Set day_of_week, week_of_month and an anchor date so a recurring visit lands on the second Tuesday, the last Friday, or any nth weekday.

Turn off the activation gate to schedule and dispatch recurring work on a verbal agreement, keeping the proposal ready but unsent.

Build a proposal in biloh, preview the investment summary, and send it to your client for a legally-binding portal acceptance — by chat or in the app.

Put a laptop, a mower or a trailer on the asset register from the bank debit that bought it, choose the method, and read the year's schedule.

Pick up a request a client sent from their portal, decide whether to quote or decline it, and turn it into a priced proposal.

Stop a migration from looking like double-billing: sort the draft queue by evidence, then send each invoice with the note it actually needs.

Check per-recipient delivery evidence for any send — and tell a mail-app display problem from a genuinely empty or missing email.

Read the whole receivables position from one feed — who owes, how late, which drafts are stuck — then record a payment in place.

Reference for get_attention_digest — the MCP tool that carries the operator's outstanding-attention queue into every agent conversation.

Every code the finance engine refuses with, what it means, what figures come with it, and what to do next. A refusal is the product working.

The finance engine's tool surface by stage: bank feed, money in, money out, transfers and envelopes, close ladder, BAS, reports, assets, calendar and pack.

Every tunable that shapes the finance engine per business: bank feed guards, GST evidence thresholds, envelopes, obligations, assets and the pack.

Reference for the fields list_invoices returns — client identity, live overdue position and pre-computed ageing — and which one to read for which question.

The three-leg send chain, the tax-compliance validator that runs at approval, and the duplicate-invoice guard — what each blocks and why.

How to connect a Biloh tenant to an AI assistant over the Model Context Protocol — the endpoint, authentication, personas, and the operator toolset.

Runs group a day's stops in Biloh. Ordering them by hand is free; an optional paid solver sequences them and hands the route to your maps app.

The five MCP tools that let an assistant work a client's inbound request queue: list, read, review, decline and quote.

Two guard rails that make a misrouted write fail loudly instead of landing in the wrong tenant, and the exact errors they raise.

Record completed visits from before a migration at their original price, decide whether a contractor gets paid, and let the billing cadence bill them.

How Biloh turns matched deposits and coded debits into G1, 1A, 1B and the net GST position, and why 1B is the claimable figure.

Once a client is onboarded their portal becomes the channel they send new work through, and every request lands in your queue as actionable work.

Photo and note requirements on completion resolve through four levels — job, series, client and contractor, then your default — with the strictest rule winning.

One delivery-model setting adapts Biloh to operators who subcontract every job and to owner-operators who do the work, without splitting into two products.

How Biloh tells you what should be sitting in your tax and contractor accounts right now, measures what is, and pairs the sweeps between them.

A multi-site proposal prices each premises on its own line, subtotals per site, and stands up a separate service line at every site when the client accepts.

Why a field-service schedule models jobs at day granularity, and how editing a recurring series splits into this-occurrence and all-future changes.

When an accepted proposal contains a visit dated in the past, biloh raises a decision card instead of silently never scheduling it.

Why every imported bank line is tied by the bank's own running balance, and what the chain guard refuses on import and at close.

One service speaks three ways: a sales pitch for customers, a legal scope for contracts, and an operational scope for the crew doing the work.

How Biloh separates platform subscription billing from each business charging its own customers — two independent Stripe tills.

Field-service billing cadence is per-client: invoice each job on completion, consolidate a period, bill on the period's last job, or invoice by hand.

The compliance gate checks capability, agreement, insurance and availability before any assignment — and names the exact reason each contractor failed.

Why a company name is never used as a greeting, how the fallback ladder works, and how your own note suppresses a duplicate greeting or sign-off.

How Biloh's Brand Pack keeps finished files AND editable source masters with your business, so any designer can continue the work.

What actually happens when an operator tells an AI assistant to reconcile the bank, close the month and produce the BAS in Biloh.

Bank feed, reconciliation, month and quarter close, BAS, P&L, balance sheet and the accountant pack, all driveable by natural language.

The cascade from client to business default, why a due date is not a payment term, and the rule that an invoice never overstates the credit given.

The integrity invariant behind biloh scheduling: the calendar equals the contract, and when it can't, a human is told — never silently.

Residential and commercial clients run on one engine. What changes is client type, service audience, payment defaults and price presentation.

Operator screens name a business the way you know it. Tax invoices, statements and the accounting mirror carry the registered entity — and a test enforces both.

The recurring-work patterns real service contracts contain, and how biloh represents each one — including the ones most tools can't.

Biloh is an AI-native operating system for service businesses: quoting, scheduling, dispatch, invoicing and the books, by chat or any AI agent.

A committed failure ceiling, calibrated only from CI, that refuses stale or partial evidence — and becomes the zero-failure gate when it reaches zero.

A read-me-first tool that returns 100KB is unreadable inside an agent's context budget. Make the default lean, put the full detail behind an explicit flag.

Show prices from the same source that charges the customer. Copying a price into a second surface invites silent displayed-versus-charged drift.

Drag-and-drop dispatch boards are desktop tools. On touch a press-and-move is a scroll, so the field surface has to be tap-first, not drag-first.

Grouping a list into filters can leave records in no group at all — present in the data, invisible on screen. Make the buckets a partition and assert the union.

Silent-pass patterns found on the road to zero failing tests: vacuous scanners, swallowed errors, invisible todos, and a reporter that never ran.

Convert a never-green check into a frozen offender list that blocks new debt today and only shrinks, with invariants that keep the list honest.

Lessons from building a docs system into a deploy-on-every-push platform: a green local build and a working deployment are different claims.

Lessons from shipping a batch of MCP tools: test the consumer not just the logic, surface what agents need, and watch the build and version traps.

When a provider confirms a payment your system can't record, alert a human and still acknowledge the provider — never fail silently.

How Biloh stops an agent holding several tenant connectors from acting on the wrong one: identity, a per-response stamp, a mismatch guard, confirm-gates.

A display rule and its compliance counterpart point opposite ways. Give each one home, then write the structural test that guards both boundaries.

A case where the UI and the agent tool answered the same question differently, and the correct half was not enough to prevent a false bug report.

Why every mutation should funnel through one core that the UI and the agent both call — and the billing bug that appears when a caller skips it.

A field app's primary action belongs in the thumb zone, pinned and dominant — and the destructive options belong below the content, not above it.

When a failing test asserts ratified-but-unbuilt behaviour, preserve it verbatim in an integrity-locked quarantine its work package must turn green.

When an autonomous worker merges to the same branch you are building on, version numbers collide and edits overlap. Merge, never overwrite.

How an agent finds the right tool among hundreds — a categorised map, intent search, and the zero-result rate as the signal the catalogue works.

A payment webhook must bind each charge to the provider's signed account, not to client-supplied metadata — the pattern that blocks cross-tenant spoofing.

A permission was stored in two places. The form wrote one, the gate read the other — so a user's saved choice was invisible to the system enforcing it.

Governed settings writes wrap the value as {v:...}, so a raw read silently returns the default. The one unwrapper to use, and the lint that enforces it.

A test harness that injects tenant context can't catch a tenant-resolution bug. Only live use on a non-default tenant exposed a 401 the suite couldn't see.

An agent reported a broken send. The send was fine — its own reporting tool was lying to it. How to triage a report written by a confident reader.

A scheduling product that computes today in UTC shows the wrong day to most of the world. Resolve the day in the tenant's timezone and lock it with a test.

An event handler can be unit-tested yet never run in production if nothing subscribes it to its event. Verify the wiring, not just the handler.