When one work has several technicians, each has their own work sheet. Office marks one as lead (Lead). The lead is the main person on site (customer signature, default time frame), but every technician can check in themselves and end early if needed. How to open a sheet: Worker terminal → My works → open your row Full terminal guide: Worker terminal. How the process works 1. Office plans Office adds technicians, ticks one Lead, and saves. Sheets are created. Planned clock times are a draft frame (e.g. 09:00–17:00) — they are not yet a real check-in. 2. On site — who taps I am on site | Situation | What happens | |-----------|----------------| | Each technician opens their sheet | I am on site is on their sheet if they have not checked in yet. | | Technician taps I am on site | Their start time is saved. The lead will not overwrite it later. | | Lead taps I am on site | Fills the lead’s own time and the frame for others who do not yet have their own check-in or end time. | | Technician already checked in or already ended | The lead’s button does not change that person’s times. | If I am on site is missing, you already checked in or the sheet is already In progress / finished — then use End work / Continue work. 3. During the job Everyone fills description, materials and photos on their own sheet. The customer signature is usually on the lead’s sheet. 4. Someone leaves early The technician who must leave: 1. Opens their sheet. 2. Taps End work (or sets their own end time). 3. Their end time stays — a later lead I am on site or crew-wide finish does not overwrite it. Others can keep working on site. 5. Continue or finish the whole crew - Continue work — if you ended your own time but come back to the same site. - When the whole crew finishes, empty end times can be filled for people who do not yet have their own. Anyone who already has an end time keeps it. Finally each person Submit work sheet. Who owns which times | Data | Belongs to | |------|------------| | Check-in (I am on site) | Each technician’s own sheet | | End time (End work) | Each technician’s own sheet | | Frame for others who have not marked themselves | Lead’s I am on site | | Customer signature | Usually the lead’s sheet | Example Ander is lead, Marko is the second technician. Marko was planned 09:00–13:00. 1. Ander arrives and taps I am on site. Marko’s times are filled only if Marko has not already checked in or ended. 2. Marko arrives and taps I am on site — Marko’s real arrival is stored. 3. Marko leaves at 13:00: End work. Ander can stay until evening; Marko’s 13:00 stays. What office needs to know - You still need a Lead: signature, responsibility, default frame for people who do not tap the button themselves. - A wrong lead no longer blocks others from I am on site. A wrong lead mainly means the customer signature is on the wrong sheet — fix Lead on the work and ask technicians to reopen their sheets. - Single technician: they are the lead; check-in and signature are on the same sheet. Related guides - Worker terminal - Work sheets - Works

API Integrations

Venipak

Activate Venipak Flowbyte creates Venipak shipments directly. You need Venipak API username and password. 1. Settings → API interfaces → Venipak 2. Enable → enter username and password 3. Save → Test connection 4. Shipments → Venipak; for pickup points use code Contract: your company contract with Venipak. Support - Flowbyte: support@flowbyte.ee

API Integrations

SmartPost / Itella

Activate SmartPost / Itella Flowbyte creates SmartPost shipments directly. You need an API key from SmartPost Self-Service. 1. Settings → API interfaces → SmartPost 2. Enable → enter API key 3. Save → Test connection 4. Shipments → SmartPost; for lockers use place_id Contract: your company contract with SmartPost / Itella. Support - Flowbyte: support@flowbyte.ee

API Integrations

QuickBooks Online

QuickBooks Online (Intuit) — full guide Flowbyte connects to Intuit QuickBooks Online (QBO) via the Accounting API. Flowbyte stays the ERP; QBO receives bookkeeping documents (US / international companies). What it can do Push (Flowbyte → QBO) - Customers (name, email, address) - Sales invoices (DocNumber = Flowbyte invoice #) and credit notes - Payments (linked to the QBO invoice) - Products → Items (SKU) - Inventory QtyOnHand (optional) - Journal entries (optional; needs account mapping) - Vendors from suppliers (optional) - Bills from purchase invoices (optional) Pull / webhook - Tax catalog (TaxCode) on connect / Test - Chart of accounts + Flowbyte ↔ QBO mapping - Webhooks: Customer, Invoice, Payment, JournalEntry (e.g. mark invoice paid when QBO balance is 0) Tax - US: TAX / NON; AST when enabled (+ ship-to address) - EU / Global: TaxExcluded + VAT% → TaxCode map - For Estonian VAT prefer a non-US QBO company Automation - Daily ~05:40 - Immediate push when a sales invoice is finalized - Multi-realm — switch / connect another QBO company Quick start 1. Settings → API interfaces → QuickBooks Online 2. Connect → authorize at Intuit 3. Test connection 4. Enable sync toggles → Save 5. Optionally pull chart of accounts and map accounts 6. Optionally Push customers / invoices / payments 7. Verify in QBO: Sales → Customers / Invoices Sync toggles | Toggle | Default | |--------|---------| | Customers / Invoices / Payments / Products / Chart of accounts | on | | Journals, Inventory, Vendors, Bills | off | FAQ Why “Sales tax: US”? Connected QBO company is US — reconnect a non-US company for EU VAT. Can QBO change Flowbyte data? Webhooks can mark an invoice paid. Full two-way line sync is not claimed. Journals / inventory fail? Map the chart of accounts first. Support - Flowbyte: support@flowbyte.ee - On failure: error text + intuit_tid + QBO company country

API Integrations

Finbite API

Activate the Finbite e-invoicing API Finbite connects Flowbyte for sending and receiving e-invoices (including Peppol). 1. In Finbite: enable ERP interface and copy the auth code (COMPANY_ID:TOKEN). 2. In Flowbyte: Settings → Company → E-invoicing (or API interfaces). 3. Paste auth code → enable e-invoicing → choose test/production → Test connection. 4. Send sales invoices with Send e-invoice; receive under Incoming purchase invoices. Support - Finbite: https://app.finbite.eu - Flowbyte: support@flowbyte.ee

API Integrations

LHV Connect

Activate the LHV Connect API integration Flowbyte is an LHV Connect service provider. Most clients do not upload certificates — activation goes through an LHV Connect contract via Flowbyte. 1. Open Payments → Bank. 2. Add an LHV bank account if needed (IBAN is enough; LHV IBANs include bank code 77). 3. Open account Settings → Request LHV Connect (via Flowbyte). 4. Sign the downloaded BDOC (ID-card / Smart-ID). 5. After LHV approval, enable Allow bank connection (gateway). 6. Optionally enable automatic morning import and auto-confirm receipts. 7. Click Fetch statement to verify. Support - Flowbyte: support@flowbyte.ee - LHV: your relationship manager