Concepts

The ideas Biloh is built on, explained once so every screen and tool makes sense.

14 pages · last updated 2026-11-03

• The balance chain: how Biloh knows a month is complete

  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.

• Delivery models: dispatch, self-perform, or both

  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.

• One proposal, many sites

  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.

• Signed work never disappears: sold-visit decision cards

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

• Cash-basis BAS from the bank feed

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

• Envelopes: the tax set-aside and the contractor buffer

  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.

• Scheduling jobs by the day, not the minute

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

• How client requests close the loop

  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.

• The three voices of a service

  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.

• Why a contractor can't be assigned to a job

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

• Backfilling work you already did

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

• Who decides whether a job needs photos?

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

• How Biloh handles money: the two Stripe tills

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

• When completing a job bills the client

  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.