Real Projects
by Rameez Scripts

Every week, someone at a school in Mumbai spent 20+ hours in Google Sheets — checking who had paid the fee, who hadn't, and who to chase. Hundreds of students, one person, all by hand.

So we kept the same Google Sheet and put Apps Script behind it. It records each payment, reminds parents when a fee is due, makes the receipt, and builds the monthly collection report on its own. The staff kept working in the sheet they already knew — it just started doing the work for them.

Those 20+ hours a week are gone. A job that took a full staff member's time now runs by itself.

1. Payment logged
2. Reminder to parents
3. Receipt generated
4. Monthly report

An operations team in Texas was running stock for 3 states out of spreadsheets. And spreadsheets don't check each other — so one file stopped matching the next, and nobody knew which number was right.

So we moved it to a proper PHP and MySQL system. Every location sees live stock levels, purchase orders are tracked in one place, and a low-stock alert goes out before a shelf runs empty. Role-based access means each person sees only what their job needs.

Teams in all 3 states use it every day, and the stock mismatches are gone. Clean code, solid security.

1. Stock in / out
2. Live levels per state
3. Low-stock alert
4. Purchase order

A retail owner in Toronto had 5 stores and a separate sheet for each one. So seeing how the week went meant opening every file — and there was no weekly report at all.

So we left each store's sheet where it was and pulled all of them into one Google Sheets dashboard. Clean charts put the stores side by side, and Apps Script emails the report every week without anyone pressing a button.

All 5 stores in a single view, and the weekly report lands in the inbox by itself. In the owner's words: “Worth every dollar.”

1. 5 store sheets
2. Auto sync
3. One dashboard
4. Weekly email

A logistics company in London kept one spreadsheet per warehouse. So the only way to know the real stock was to open every file — and low stock was usually found out after the item had already run out.

We joined the warehouse sheets into one Google Sheets dashboard. Apps Script watches the levels, emails a low-stock alert, builds the purchase order, and gives the team a small web app to look up stock by warehouse.

Live stock for every location in one dashboard. Alerts go out before an item runs out, not after. And a purchase order is one click, from the same sheet.

1. Warehouse sheets
2. One dashboard
3. Low-stock alert
4. PO in one click

Every term, a school administrator in Lagos made report cards for 500+ students by hand. Hours of copy-paste — and one wrong paste puts a wrong grade on a child's report.

So we built it in Apps Script. Grades go in once, each student's marks turn into a PDF report card, and parents get an email the moment it is ready. And it handles 500+ students without slowing down.

Report cards went from hours of manual work to one click, and parents are told by email automatically.

1. Grades entered
2. PDF report card
3. Email to parents

A company in Dubai typed every invoice in Word and tracked payments in a separate sheet. So invoice numbers followed no order, overdue payments slipped through, and nobody could say what the month's revenue really was.

We built the whole thing inside Google Sheets with Apps Script. Invoices are numbered automatically from one template, every payment's status is colour-coded, overdue reminders email themselves, and a revenue dashboard shows each month and each client.

An invoice now takes 30 seconds. Overdue reminders go out on their own, and the CEO sees monthly revenue at a glance without asking anyone. “Delivered exactly what we needed.”

1. Invoice from template
2. Status tracked
3. Overdue reminder
4. Revenue dashboard

A company in Qatar still used paper sign-in sheets. So HR couldn't see who came in late, couldn't total working hours, and every monthly report meant going through stacks of paper — half a day, every month.

We gave them an Apps Script web app for check-in and check-out, backed by Google Sheets. It saves the exact time, flags late arrivals, adds up daily and monthly hours, and every Monday the manager gets the summary by email.

The paper is gone. HR sees attendance live, and the monthly report that took half a day now builds itself.

1. Check in / out
2. Late flag
3. Hours calculated
4. Monday summary

An import-export company in Saudi Arabia had shipments, suppliers and customs papers spread across sheets and email threads. And when nobody can quickly see which document is missing for which container, the container waits — so shipments were getting delayed.

So every shipment became one row in a Google Sheet: supplier, status, a customs document checklist with tick boxes, and the profit or loss. Apps Script emails an alert when a shipment's documents are incomplete or a clearance deadline is close.

Everything in one sheet. Missing documents are flagged before they cause a delay, and the owner sees the profit on each shipment without asking the accountant.

1. One row per shipment
2. Document checklist
3. Deadline alert
4. Profit per shipment

A small business owner in Bangladesh logged expenses in a plain sheet with no structure. No budget, no categories — so at the end of every month, nobody knew where the money had gone.

We added a simple sidebar form in Google Sheets: category, amount, date, done. Behind it, the dashboard compares budget against actual spending for every category, the charts update as entries come in, and Apps Script sends a weekly summary by email.

The owner now sees exactly where the money goes — by category, by week, by month. And overspending is caught early, because the weekly email flags any category that has used more than 80% of its budget.

1. Sidebar form
2. Budget vs actual
3. Weekly email
4. 80% warning

A consulting firm in France kept clients, project milestones and billing in separate Google Sheets that didn't talk to each other. So finding one client's project history meant opening 4 different files.

We put one Apps Script web app on top of a single Google Sheets data store. The team adds clients and projects through clean forms, filters by client or status from dropdowns, client and project records link to each other automatically, and any report exports to CSV or PDF in one click.

All client and project data in one place. The team fills a form instead of editing cells by hand, and a client's full history is one search away.

1. Add via form
2. Linked records
3. Filter & search
4. CSV / PDF export

A training institute in Sri Lanka ran quizzes on Google Forms, then graded them by hand. Scores were added up manually, every certificate was made one by one, and students waited days for their result.

So Apps Script now grades each response the moment it arrives and writes the score to a Google Sheet. If the student passes, a PDF certificate with their name and score is made from a template and emailed straight to them. And the teacher dashboard shows the pass rate, the average score and the weakest topics.

Grading is instant, with zero manual work. Students get their result and certificate by email within seconds of submitting, and teachers can see which topics need more time.

1. Form submitted
2. Auto-graded
3. PDF certificate
4. Teacher analytics

A company in Jordan ran HR on a mix of Excel files and paper forms — employee records, attendance, leave and payroll. So every pay cycle, the HR team lost hours to data entry and manual calculations.

We built a complete HR system in PHP and MySQL: employee profiles, check-in and check-out, leave requests with an approval workflow, and payroll with deductions and allowances worked out by the system. Department-level access means each manager sees only their own team.

Payroll went from 2 days of manual work to a few clicks. Leave requests follow a proper approval chain instead of paper, and HR finally has clean data to work with.

1. Attendance
2. Leave approval
3. Payroll run
4. Manager view

A sales team in Morocco tracked leads and conversations in spreadsheets. So follow-ups were missed, nobody was sure what stage a deal was at, and the manager couldn't see the pipeline at all.

We built a CRM in PHP and MySQL: lead capture forms, a drag-and-drop sales pipeline, contacts and companies, automatic follow-up reminders by email, a log of every interaction, and a manager dashboard with each rep's numbers.

No more missed follow-ups, because the system reminds people on its own. The manager sees the whole pipeline at a glance, and in the first month the team closed more deals because nothing fell through the cracks.

1. Lead captured
2. Pipeline stage
3. Follow-up reminder
4. Manager dashboard

A non-profit in the USA runs community events for families, and sign-ups came in through a multi-step form built on Google Sheets. Payments are sent person to person, so matching each one to a family — and checking everyone in at the door — was work done by hand.

So we rebuilt it in PHP and MySQL as a full event system. Each event gets its own form builder, age-based prices and add-ons, and families register on a public step-by-step form with a live running total, then upload their proof of payment through a private link. A Treasurer checks each amount against the bank record, and once the balance is zero the family is emailed a QR pass that Volunteers scan at the door, ticking in each person.

Every registration now has a reference number, a running balance and an email trail, and the QR pass only goes out when the money is in. At the door, one scan shows who has arrived and who is still expected.

1. Family registers
2. Proof uploaded
3. Treasurer verifies
4. QR scanned at door

A bulk apparel supplier in India took wholesale orders through a storefront built on Google Sheets and Apps Script. Colour and size grids, tier prices, GST invoices, quotes and returns all lived in spreadsheet rows, and the owner wanted the same store on a real database with its own admin.

So we rebuilt it in PHP and MySQL: a public storefront with a colour-by-size order grid, wholesale price tiers and guest checkout, plus a customer area for orders, quotes, addresses and statements. Behind it, staff run orders and dispatch, GST tax invoices with financial-year numbering, payments, quotations, returns, credit notes, stock and print jobs, with 80 mm or A4 receipts and an AI chat on the storefront.

Prices, shipping, GST and totals are now worked out on the server for every order, and each invoice keeps a number that never changes once issued. Customers see their own orders, quotes and statement in their account.

1. Order placed
2. Invoice issued
3. Payment recorded
4. Order dispatched

A shop in Pakistan sells phones, bikes and home appliances on installment (qist): an advance at the counter, then a fixed amount every month. Keeping customers, guarantors, monthly schedules and every payment straight by hand makes it hard to see who is late, and by how much.

So we built an installment system in PHP and MySQL. Each sale records the customer with photo and CNIC copies, two guarantors, the IMEI or engine and chassis number, and a monthly schedule worked out from the cash price, markup and advance. Payments go to the oldest unpaid month first, with numbered receipts on a thermal printer or A4, and a Due List with one-tap WhatsApp reminders for staff on recovery.

Every installment now has its due date and its receipt, and the Due List shows who is due today and how many days each late customer is behind. The owner sees collections and profit, while counter staff never see cost or profit.

1. Sale with advance
2. Monthly schedule
3. Payment received
4. Due list follow-up

A visa consultancy in Pakistan handles study, visit, work and family visas for walk-in clients. The owner wanted one place to reach every client's files from a desk, an iPad or a phone, instead of tracking cases, deadlines and fees by hand.

So we built a private case system in PHP and MySQL: client profiles with passport details, visa cases moving through a stage pipeline, a protected document store with a checklist for each visa type, and reminders that create themselves for passport expiry, biometrics and overdue installments. Fees are split into service and government fees, with installment plans, numbered receipts, quotations and signed agreements, and each consultant sees only their own clients.

A case can't move to Submitted while a required document is missing, and every view or download of a document is logged. Each client's cases, documents, payments and notes now open on one screen.

1. Client registered
2. Case opened
3. Documents verified
4. Decision recorded

An industrial contracting company in Saudi Arabia prices jobs from customer RFQs, then has to run the project, buy materials, bill the client and stay ZATCA-compliant. Done by hand, the estimate, the real cost and the invoices quickly drift apart.

So we built one system in PHP and MySQL that follows their own process map: leads and RFQs, a cost estimate built from materials, machine time, labour and overhead, a quote health check before pricing goes out, then the project with its BOQ, budget and variations. Work orders, hours, purchase orders, goods receipts, stock and subcontracts feed the actual cost, and progress claims turn into bilingual Arabic and English tax invoices cleared through ZATCA Phase 2.

Every project now shows budget against actual, committed cost and forecast profit, with retention and VAT tracked by period. Estimators, project managers, procurement, workshop and accounts each land on their own starting page.

1. RFQ received
2. Estimate checked
3. Project executed
4. Claim invoiced

A trader in Pakistan kept cash in and cash out in an old daily book app, and a khata of who owed what. Credit sales had to go on the customer's name without touching the day's cash, and at day end it was hard to know the real cash in hand.

So we built a Daily Cash Book in PHP and MySQL. Every entry is Income, Expense, Receipt or Payment, and one switch — Include in Daily Cash — decides whether it moves the cash or only the party's khata. Party statements with a running balance, a day-close cash report and a dashboard with receivable and payable totals sit on top, all ready for CSV, PDF and print.

Cash in hand is now known for any date, and every party's balance is one statement away. Udhar stays on the khata and never mixes with the day's cash.

1. Entry recorded
2. Cash or khata only
3. Party balance updated
4. Day close report

A training company in India places freelance trainers with colleges and companies. Every project meant matching trainers to dates, collecting attendance proof and daily updates, gathering student feedback, issuing certificates, paying trainers and invoicing clients — a lot of moving parts to track by hand.

So we built one training operations portal in PHP and MySQL with 8 roles, from HR and finance to trainers and clients. Trainers accept or reject assignments, check in with a selfie and GPS, post daily updates with photos, and students give feedback by scanning a QR code. Certificates carry a QR anyone can verify, and finance runs trainer payment slips and client invoices with GST and TDS.

Each project now runs from assignment to invoice in one place. A trainer can't be double-booked, ratings come only from validated feedback, and every certificate can be checked online.

1. Trainer assigned
2. Selfie GPS attendance
3. QR student feedback
4. Certificate and invoice

An EV rental company in India rents out its own electric scooters and cars, and also lists vehicles from partner vendors. Bookings, KYC, handovers, deposits, GST invoices and vendor payouts all had to work together — with the money split one way for its own fleet and another way for partner vehicles.

So we built one booking engine with a public storefront and a back office in PHP and MySQL. Customers search by city and hub, complete KYC once and pay online with UPI, while hub and field staff do handovers and returns on a phone with checklists and photos. The back office runs deposits and refunds, GST invoices on the vendor's behalf, TCS and TDS settlements, maintenance, charging, subscriptions with km allowances, rewards and support tickets.

One engine now books both own and partner vehicles, keeps the commission on vendor bookings and settles each vendor with a statement. Every role, from hub staff to finance, opens to its own dashboard and queue.

1. Customer books online
2. KYC and payment
3. Handover at hub
4. Vendor settlement

A clothing shop in Pakistan sells the same design in many sizes and colours. Keeping that stock straight, printing barcodes, buying from suppliers and handling returns at the counter is hard to do by hand.

So we built a Garment Store POS in PHP and MySQL with 4 roles: owner, manager, cashier and storekeeper. The counter screen shows products as tiles, scans barcodes, takes split payments and prints a thermal or A4 receipt, while stock is kept per size and colour with printed barcode labels. Purchase orders, goods receipts, returns with credit notes, cash shifts with a blind count, salesman commission and 11 report tabs complete it.

Every piece now has its own size, colour, barcode and stock count. The owner sees net sales, gross profit, stock value and supplier payables on one dashboard.

1. Stock received
2. Barcode labels printed
3. Sale at counter
4. Profit report

A university in South Sudan prints student and staff ID cards every year. A card should only go out once fees are paid, and lost or damaged cards need reprinting — all hard to track across many schools and departments.

So we built an ID card system in PHP and MySQL with three roles: super admin, printing staff and clerks who see only their own schools and departments. Clerks add students and staff, enrol them for the academic year and log fee payments, and the card colour follows what has been paid. Cards print in batches that move from pending to approved to printed, with a QR code on the front and back, and lost or damaged cards go to a reprint queue.

Each card now prints in the university's own design, only for the fees paid, and every reprint is on record.

1. Record added
2. Fee payment logged
3. Batch approved
4. Card printed

A phone shop in Colombia was running its sales, repairs and stock on a Google Apps Script app we had built for it earlier. It wanted the same shop moved to a full web app with its own database.

So we rebuilt it in PHP and MySQL, feature for feature: a POS where every phone is sold by its IMEI, a repair desk with a public tracking page, used-phone buying and trade-ins, installment plans, a cash drawer, expenses and profit reports. Staff work in Spanish or English, and sales print as thermal tickets or A4 delivery notes. A public catalogue page lets buyers ask about any phone on WhatsApp.

Any phone can now be traced by its IMEI from the day it came in to the day it was sold, returned or repaired, and every installment and cash day sits in one place.

1. Phone stocked by IMEI
2. Sold at POS
3. Installments tracked
4. Cash drawer closed

An optical shop in Pakistan sells prescription glasses, sunglasses, contact lenses, eye drops and repairs, each in several quality grades. Keeping eye numbers, lens stock by power, lab jobs and the customer khata in registers is slow, and the staff are not technical.

So we built an optical store POS in PHP and MySQL, with pictures and icons on every screen. Eye tests are saved on a slip-shaped right/left grid, a glasses order walks through customer, eye numbers, frame and lenses — matching lens stock for each eye — and lab jobs and repairs move across a job board. The POS scans barcodes, splits payments and prints thermal or A4 receipts, and a khata ledger tracks what customers owe and what is due to suppliers, with WhatsApp reminders.

Every pair of glasses can be followed from the eye test to the lab to pick-up, and the owner sees cash, khata balances and profit on one dashboard.

1. Eye test recorded
2. Frame & lenses ordered
3. Lab job tracked
4. Collected & paid

A school group in Pakistan runs several campuses under one head office. Each campus handles its own admissions, attendance, exams and fees, so head office had no single, up-to-date view across them.

So we built a multi-campus school ERP in PHP and MySQL, with each campus scoped to its own data and head office above them all. It covers admissions from enquiry to offer, one family account across campuses, fee challans with bank statement matching and a cashier day close, attendance with same-day absence alerts to parents, and a marks workflow from entry to approval to published report card. HR and payroll, transport, hostel, library, clinic, gate passes and SMS/WhatsApp messaging sit in the same system, in English or Urdu.

Head office can compare every campus on one dashboard and drill down, while each campus runs its own day. A family's children, fees and messages follow them from one campus to another.

1. Admission enquiry
2. Fee challan paid
3. Marks approved
4. Report card published

A facilities company in India supplies staff to its clients and also runs healthcare sample collection. Turning who worked where, overtime and fuel claims into salaries and client bills by hand is slow — and one missed day means a wrong salary or a wrong invoice.

So we built a CRM and HR system in PHP and MySQL with six roles and 19 modules: clients and contracts, employees and their documents, deployments, attendance, overtime, fuel claims, salary structures, payroll, offer and appointment letters, sample collections, invoices, payments and compliance alerts. Payroll works out PF, ESI, professional tax and TDS, and each client invoice is built from approved attendance, overtime, fuel and sample records.

Salaries and client invoices now come from the same approved records. And a record that has already been billed can never be billed twice.

1. Employee deployed
2. Attendance approved
3. Payroll processed
4. Client invoiced

A fuel-station network trains staff across many stations — new hires, yearly refreshers, specialised courses and retraining. Without one system, nobody could say on the spot whether an employee was trained and cleared to work, and an expired certificate was only found once it was too late.

So we built a training management system in PHP and MySQL that runs the full cycle: stations, employees, training rules, courses, trainers, sessions with attendance and evaluation, and certificates. Each certificate prints with a QR code an inspector can scan to check it, and expiry alerts go out at 60, 30 and 7 days. Three roles: administrator, executive management (view-only) and trainers, who see only their own sessions.

For any employee or station, the system now answers one question on demand: is this person trained and cleared to do the job? Certificates are flagged before they expire, not after.

1. Training rule set
2. Session delivered
3. Certificate issued
4. Expiry alert sent

A cashew trading company in Ivory Coast buys raw nuts from many suppliers each season, often paying cash advances before the goods arrive, then sells and ships to customers. Keeping track of who was advanced what, what was delivered against it, and what each bag and truck cost is hard to keep straight by hand.

So we built a trade and supply chain system in PHP and MySQL, in English and French: supplier and customer masters, purchases, sales, deliveries, warehouse inventory, a bags log, fleet and drivers, expenses, bank financing and payments. A supplier reconciler keeps every supplier's balance and advance status right after each payment or delivery. Profit analysis with a simulation tab, supplier ranking and Gemini-powered AI reports sit on top.

Each supplier now has one live balance — what they were advanced, what they delivered and what is still open. And the dashboard tracks stock bought against each season's goal.

1. Supplier advance paid
2. Purchase delivered
3. Stock sold
4. Profit analysed

A water softener and RO business in Pakistan sells units over the counter, installs systems on quoted projects and sends field workers out on service visits. Sales, stock, vendor bills, worker pay and daily cash all had to be tied together by hand.

So we built a business system in PHP and MySQL with four roles — admin, manager, field worker and accountant. It covers clients, office sales, returns, quotations that turn into install projects with assigned workers, service visits, purchase bills, inventory with a stock log, payroll and an employee ledger. Every sale and purchase posts itself to stock, the party ledger and the cash book, with bank and JazzCash accounts kept apart.

Each client and vendor now has a running balance and each product a live stock count. Each day's cash lands in the cash book without anyone retyping it.

1. Quotation sent
2. Project installed
3. Service visit logged
4. Ledger updated

A publishing business in India works with young authors across the whole life of a book — writing, design, printing, selling and paying the author. That work was spread over separate tools.

So we built one platform in PHP and MySQL with nine roles, from super admin and authors to collaborators and customers. Authors write chapters and design pages in a Canva-style editor, pick a print or e-book publishing plan and see the full price split before they publish; the bookstore takes orders paid by UPI, bank transfer or PhonePe and tracks delivery. Author earnings run on a points ledger with withdrawals and donations, alongside team projects, real-time chat, CRM, events, a public website and ChatGPT and Gemini writing tools.

A book can now go from first draft to delivered order in one place, and authors see every point earned, withdrawn or donated. And no book can be published at a price that does not cover its costs.

1. Book written
2. Plan and price set
3. Order paid
4. Author earns points

A mobile repair and sales shop in India needed one place for the whole counter: phone and accessory sales, repair jobs, second-hand phones bought from customers, and udhaar owed by regulars. Tracking all of that by hand makes it hard to see who owes what and which repair is ready.

So we built a shop system on Google Sheets with three logins — owner, manager and employee. It has a POS and a Quick Bill page, repair job sheets with photos and a private link the customer gets on WhatsApp, used-phone buying with IMEI lookup, installments, a cash drawer and an owner-only udhaar ledger. Every bill can carry a UPI QR code for the balance due.

Sales, repairs, used phones and credit now run from one app, and customers get their job sheet as a WhatsApp link they can open any time.

1. Repair job booked
2. Job sheet on WhatsApp
3. Bill with UPI QR
4. Udhaar settled

A truck dealer network in Peru keeps spare parts across several branches and warehouses, with its parts master in one big 16-column spreadsheet. Matching parts to vehicles, holding them for workshop jobs and knowing what is really free on the shelf is hard to do from one sheet.

So we are building a multi-branch parts system on Google Sheets in 14 phases, and the first 8 are done: the parts master with bulk import of the client's own sheet, vehicle fitment and replaced part numbers, warehouses and bins, a stock engine with transfers and a kardex, workshop work orders, part requests and reservations, issue vouchers, returns, and counter sales with IGV. Seven roles — from Parts Manager to Technician — each see only their own branches, and costs stay hidden from the workshop.

Every part movement goes through one stock engine, so on-hand, reserved and committed stock stay in step across branches. Purchasing, forecasting and stock counts come next.

1. Work order opened
2. Parts reserved
3. Issue voucher posted
4. Stock updated

A yogurt drink shop in Taiwan sells from trucks at different stops. Orders came in through a Google Form, and the only way to stop orders before a pickup day was to shut the form link.

So we built an online ordering site and an admin dashboard on Google Sheets. Customers pick drinks with sugar, ice and add-ons, pay by QR or bank transfer and upload the receipt, then choose a day, a truck stop and a 30-minute pickup time — in English or Chinese. The owner approves each payment and moves orders from preparing to ready to picked up, while each truck crew logs in to see only its own truck's orders and a printable crew sheet of what to bring.

One link now takes orders for all three trucks, each stop closes on its own deadline, and customers can change or cancel until then. Reports by day, truck and payment method come straight from the orders.

1. Drink ordered online
2. Payment receipt approved
3. Crew sheet prepared
4. Picked up at truck

A plant in India buys plastic scrap, runs it through machines on day and night shifts, and sells the granules by the bag. It kept 11 tabs in a Google Sheet for purchases, production, sales and ledgers, so stock and what each vendor or customer owed had to be worked out by hand.

So we built a manufacturing CRM on the same Google Sheet, keeping the client's own tab names. Purchases are entered per scrap quality with the bag or 1% weight deduction, production is logged per machine and shift with the process loss shown, and sales go out with a WhatsApp invoice. Vendor payments, customer receipts, stock counts and wastage, a daily report and a month-end close all sit in one app, with five roles from Admin to Supervisor.

Raw stock, finished stock and every party balance are worked out from the registers on each save, never typed in, and overdue customers show up on their own.

1. Scrap purchased
2. Production per shift
3. Granules sold
4. Payments and ledgers

A contract-labour firm in Kolkata ran its monthly pay from an Excel salary sheet, with worker papers like gate passes, police checks and safety training tracked on the side. Every month meant working out attendance, overtime, PF and ESI by hand for each worker.

So we built an HRMS and payroll app on Google Sheets that follows the client's own salary sheet. It covers worker registration, service documents with expiry colours and email alerts, daily attendance with overtime, the monthly muster roll, a pay run with wage slips, the bank and cash payment split, salary advances, and PF, ESI and P.Tax with the ECR and ESIC files and the CLRA registers. Ten office logins each get their own access, and only one director can change a worker's personal details.

The pay run, wage slips and statutory files now come out of the same attendance data, and Aadhaar and bank numbers stay masked for every other login.

1. Worker registered
2. Daily attendance
3. Monthly pay run
4. Wage slips and ECR

A tyre retreading plant in India takes tyres in at the counter, moves them through workshop stages, and then has to bill with GST. Tracking each tyre, the quotes, the invoices and who still owes money by hand is slow and easy to get wrong.

So we built one workshop app on Google Sheets: tyre job cards that move through each stage, quotations that turn into GST tax invoices with Original, Duplicate and Office copies, receipts and party ledgers, purchases, material stock and expenses. It also gives outstanding lists, job profit, P&L, GSTR-1 and GSTR-3B summaries, a year-end close with carry-forward, daily Drive backups, thermal printing and a WhatsApp invoice PDF, with four roles from Admin to Workshop.

Every tyre keeps its own history from counter to invoice, and workshop staff never see rates or costs. Each year closes with balances carried forward on their own.

1. Tyre received
2. Workshop stages
3. Quote to GST invoice
4. Payment and ledger

A business in India had an older billing and inventory app on Google Sheets, and a long list of what it was missing: GSTIN and credit limits on customers, purchase orders that turn into stock, credit and debit notes, more payment methods and proper accounts.

So we rebuilt it as one GST billing, inventory and accounts app. Sales run from quotation to invoice with CGST, SGST or IGST worked out by state, purchases run from PO to bill to stock across several warehouses, and every document posts its own double-entry lines to the ledger. It adds credit and debit notes, expenses with approval and repeats, 25 reports, daily alerts, and eight roles from Super Admin to Viewer.

Stock, customer dues and the ledger all move together from each document, so there is no second place to update. Salesmen can bill without ever seeing cost prices.

1. Quotation to invoice
2. Stock leaves warehouse
3. Payment received
4. Ledger and GST reports

A survey team in Assam, India collects household data for a rural housing scheme. Many field staff work the same household list, so it is hard to stop two people updating one house, catch duplicates, or see who changed what — and in villages the signal drops halfway through a form.

So we built a Google Sheets web app where the admin builds the survey forms, loads the household list and assigns forms to field users. A user updates a pending household on the phone with a geo-stamped live photo, GPS and signature, and the record moves to that user's My Data. After 2 updates it locks until the admin unlocks it. Gaon Panchayat and Village pickers, duplicate warnings, masked Aadhaar numbers, a draft saved on the phone, a User Wise report and Excel or PDF downloads are all built in.

Every household has one owner, a full edit history and a stamped photo, and possible duplicates are flagged before they are saved. It runs on the team's own Google Sheet, so there is no server to pay for.

1. Admin builds form
2. Household assigned
3. Updated on phone
4. Locked after 2 updates

A company in Pakistan made its monthly salary slips by hand. Every month someone had to work out each employee's gross pay, income tax and deductions, then make and send every slip one by one — and a typed total can quietly disagree with itself.

So we built a payroll system on Google Sheets with two logins, Admin and Employee. Each employee keeps a standing salary package, so a month's slips are generated in one go, with income tax worked out from the tax slabs kept in Settings and EOBI only for staff it applies to. Slips move from draft to finalized to sent, print as an A4 statement with the net pay in words, and go out to every employee in one bulk email.

Every total on a slip is calculated, never typed, and a slip that has been issued never changes when next year's tax slabs do. Employees sign in and see only their own slips, and paying is recorded separately in a payments ledger.

1. Employee registered
2. Monthly slips generated
3. Finalized and paid
4. Slips emailed

A livestock owner in Pakistan buys buffaloes, cows, goats and sheep and hands each one to a caretaker who feeds and looks after it. When the animal is sold, the profit is split with the caretaker — and working that split out by hand, after advances and shared feed bills, is where the arguments start.

So we built one complete account per animal on Google Sheets: photos, which caretaker had it and where, every expense and advance, the sale or death, and a settlement worked out by one engine. Each expense records who paid it and who bears it, so the caretaker's share and the owner's true profit always add up. It also makes PDF account statements, reports, health and vaccine reminders and a nightly backup, with Admin and Viewer logins.

Every animal has one account from purchase to sale that never disappears, and the settlement comes out the same way every time. The Sheet itself stays readable as the permanent record, with no outside server.

1. Animal bought
2. Handed to caretaker
3. Expenses recorded
4. Sold and settled

A school in Saudi Arabia with separate boys' and girls' branches ran its stores and print room through a WhatsApp group and stock lists. Books, uniforms in every size, copy books and stationery sat in different branches, and keeping track of which student had paid for and received which items was all done by hand.

So we built one app on Google Sheets for every branch. Each branch keeps its own stock, the main branch sends stock by transfer and the receiving branch confirms it. Accounts ticks the items each student has paid for, the branch hands them over and prints the Delivery Form, and lockers are assigned with a key. Print requests run from Pending to Printing to Control to a signed hand-over to the teacher, across 6 roles with Excel reports.

Each branch sees its own stock, Accounts sees who has paid, and the Pending Items page shows which student still waits for what. Every stock movement is logged and can be traced back.

1. Stock sent to branch
2. Accounts marks paid
3. Items handed over
4. Delivery Form printed

A mobile phone and electronics shop in Canada buys and sells new and used phones, repairs devices and refurbishes trade-ins. Keeping each phone's story straight by IMEI — bought, repaired, sold, at what profit — is hard to do on paper or a plain spreadsheet.

So we set up our mobile shop system on Google Sheets for them, with owner, manager and employee logins and an editable permission matrix. It covers a POS with receipts, repair jobs with parts taken from stock, buying used phones where the battery % sets the grade and resale price, new phone purchases and sales with profit per unit, in-house refurb jobs, installments, a cash drawer, returns and expenses. Prices are in dollars with a 13% tax line and the shop's own categories.

Every phone has its own IMEI history from purchase through repair to sale, and each new phone sold shows its own profit.

1. Phone bought in
2. Repair or refurb
3. Sold at the POS
4. Receipt printed

A networking hardware distributor in India keeps its price list in Google Sheets and again in Zoho Books, and the two kept drifting apart — updating dozens of items by hand was slow and wrong. Sales passed orders to accounts over WhatsApp or by phone, so typos, old rates and wrong models slipped through.

So we built Apps Script right inside their own price-list spreadsheet. A Zoho Sync menu turns any price tab into Zoho Books' price-book format as CSV or Excel, with a mismatch report first. And a web app lets sales build orders whose rates come from the sheet, never from typing, then sends each order to accounts by WhatsApp and email. Four roles — Super Admin, Admin, Accounts and Sales — with sales seeing only their own orders.

The Zoho price list can be updated from the sheet in one file, and an order's rate always matches the price list because the server reads it again on every save.

1. Price updated in sheet
2. Zoho file exported
3. Sales builds order
4. Accounts notified

An international freight company in Chile runs trucks between Chile and Argentina — trips, customs papers, fuel, workshop repairs, drivers and fines, all in two currencies. Tracking that much by hand makes it easy to lose sight of a trip's full cost, or of a licence that is about to expire.

So we built a transport ERP in PHP and MySQL from their 18-section requirements document: a trips hub with stops, assignments and a timeline, a central document store with expiry dates, expense claims and fuel logs, workshop orders with parts stock and tires, safety checklists and incidents, HR contracts, fines, invoices and treasury in Chilean and Argentine pesos, and a GPS fleet map with geofences. Ten roles — from operations and finance to drivers, customers and providers — each see only their own pages.

Every trip now carries its own documents, costs and status history, and expiring licences and vehicle papers are flagged 30 days ahead. A KPI dashboard and a report runner pull the numbers from every module into one place.

1. Trip planned
2. Documents checked
3. Costs logged
4. Customer invoiced

A manufacturer in Pakistan makes straps, threads, ribbons and elastics for bag, footwear and garment makers. Stock, sales orders, delivery challans, purchases, payroll and production all had to stay in step — and done by hand, stock counts drift and nobody is sure who owes what.

So we built a modular ERP in PHP and MySQL: products and warehouses with stock movements, sales orders that flow into delivery challans and invoices, purchases from vendors, expenses, payments with customer and vendor ledgers, attendance and monthly payroll, and production runs built on bills of materials. Six roles — from Inventory Manager to Production Supervisor — see only their part, and stock adjustments, expenses, payroll and production wait in one approvals queue.

When a production run is approved, the raw materials leave stock and the finished goods come in, in one step. Every payment updates the balance of the invoice or purchase it belongs to, and 15 reports cover sales, purchases, stock, finance, HR and production.

1. Sales order
2. Delivery challan
3. Invoice raised
4. Payment recorded

A church community in Singapore needed one place for its members, its pastoral visits and its attendance. New members had to be approved and given a card, visiting teams had to log each visit, and a member who stopped coming could go weeks without anyone noticing.

So we built a membership platform in PHP and MySQL with three modules on one member list. Membership takes each new member from pending to approved, with a four-eyes check and QR member cards printed 10 to an A4 sheet; Visitation records visits by named teams, and each staff group sees only the visit fields it is allowed to; Attendance scans member cards at the door from an iPhone Shortcut. Staff sign in with Google Workspace, and what each person can do comes from their Google groups.

Every member now has a permanent code and a QR card, and the Last Visited view shows who has gone longest without a visit and whose follow-up is due. Attendance shows live at the door, with an absent filter for members who have missed recent events.

1. Member submitted
2. Office approves
3. QR card printed
4. Scanned at events

An e-commerce agency in Pakistan manages seller accounts for its clients on Amazon US, UK, Canada and UAE, plus Walmart, eBay and Shopify. Products, reorders, prices, FBA shipments, cases and the team's own tasks and salaries all had to be tracked across many accounts at once.

So we built an operations portal in PHP and MySQL with a client side and a team side. Clients onboard through a form, then see only the accounts assigned to them: products, orders, shipments and cases. The team works products, reorders, pricing, out-of-stock, ungated and seasonal lists, packs FBA shipments box by box, and runs projects, tasks, attendance, salaries and payments — with Amazon SP-API connected for live inventory, sales and prices.

Price changes now push straight to Seller Central for connected accounts, and the reorder page shows real daily sales pulled from SP-API. Each client and each staff member sees only the accounts they are assigned to.

1. Client onboarded
2. Products listed
3. Stock reordered
4. FBA shipment packed

A church in Trinidad and Tobago runs membership, attendance, events, worship planning and pastoral care through many hands — pastors, elders, deacons, ushers, media and sound teams. Keeping one picture of the congregation by hand is slow, and private counselling notes need tight control.

So we built a church platform in PHP and MySQL that installs as a phone app: members and households, attendance with a check-in scanner and QR membership cards, events, worship planning, groups, celebrations, announcements, counselling and prayer requests, sermons, live stream, a Bible quiz, chat and a form builder. Fifteen church roles, from Super Admin to Guest, get their permissions from one editable matrix.

Members, families and attendance now live in one hub, and counselling notes are stored encrypted. The congregation can follow events and announcements from their phones.

1. Member registered
2. QR card issued
3. Check-in scanned
4. Pastoral follow-up

A construction company in Pakistan handed petty cash to site supervisors and then tried to work out where it went. Bills came back late or not at all, and labour, diesel and hired machines were counted by hand — so nobody could say how much cash was with whom, or what each site really cost.

So we built a site-wise cash system in PHP and MySQL with four roles: owner, accountant, project manager and site supervisor. Every cash holder gets a wallet, money sent to a site stays in transit until the supervisor confirms it, and spends above a limit wait for approval with a bill photo. Day close counts the cash, while labour attendance, equipment meter logs and a diesel register feed each site's cost and 9 A4 reports.

Every rupee now has a holder, a voucher and a site. A closed day locks its entries, and the dashboard shows cash in hand, pending approvals and budget against actual cost for every site.

1. Funds sent to site
2. Supervisor confirms receipt
3. Spend approved
4. Day close count

A studio group in India runs several brands under one name — a creative studio, a cloud services company and a publishing arm. They needed one website to show all of it, and one place to run client projects, invoices and change requests.

So we built three parts on one PHP and MySQL base. A public website with projects, books, products, services, blog and portfolio pages; an admin CMS where editors manage 12 content types with SEO for every page; and a client portal where each client follows their project timeline and progress, downloads files, sees invoices and raises change requests.

Every brand now lives on one site, every website enquiry lands in a leads pipeline that converts to a client, and each client sees only their own projects, files and invoices.

1. Website enquiry
2. Converted to client
3. Milestones tracked
4. Invoices in portal

A gym in Pakistan needed one place for its front desk: members, plans, renewals, part payments, personal training and daily check-ins. Done by hand, renewals slip and unpaid balances are easy to miss.

So we built a gym system in PHP and MySQL for three roles: owner, receptionist and trainer. Members get a QR card and check in by member number, phone or QR, and plans are sold or renewed with invoices and part payments by cash, bank, JazzCash, EasyPaisa or card. Personal training with trainer commission, body measurements, enquiries, follow-ups with WhatsApp links and a day close of counted against expected cash are all built in.

Every member now has a status, a ledger and a visit history in one view. Renewal reminders, at-risk members and unpaid balances turn up as follow-ups on their own.

1. Member enquiry
2. Plan sold
3. QR check-in
4. Renewal follow-up

A distribution company sells through salespersons who visit kiosks and stores, with a different price for each region. Stock held by each salesperson, credit sales, cash and cheques collected on the road, and what each salesperson still had to hand in were hard to keep track of.

So we built a Distribution Management System in PHP and MySQL with admin, manager, supervisor and salesperson roles. Products carry 10 regional price levels, stock moves from the warehouse to each salesperson, and salespersons register clients with credit limits, raise invoices and record collections. Settlements, supplier purchases and payments, cheques, bank and cash reconciliations, a chart of accounts, an IVA report and an income statement close the loop.

Every sale, collection and cheque now traces back to a salesperson and a client. Collections stay open until the salesperson settles them with the office.

1. Stock to salesperson
2. Invoice at store
3. Collection recorded
4. Settlement approved

A government investment office handled investor registration, certificates, permits, incentives and fees through separate desks. So an investor had no single place to apply, and nobody could see at a glance where a case stood.

So we built one portal in PHP and MySQL with three sides: a public site with the project pipeline and appointment booking, a self-service area where investors register and apply, and an officer area where every case moves through configurable workflow stages with SLA deadlines. It handles fee schedules, invoices and payment checks, then issues certificates and receipts that anyone can verify by QR code. Six roles — from intake officer and finance desk to director — each see only their part.

Every application now has a timestamped trail from submission to issued certificate, and directors get reports on processing times, fees collected and capital committed. Renewals and aftercare tickets are tracked in the same place.

1. Investor registers
2. Application submitted
3. Stage-by-stage review
4. Certificate issued

A pharmacy business needed one system for the counter, the stockroom and the books. Medicines arrive in batches with expiry dates and sit in more than one location, and tracking that by hand makes it easy to sell the wrong batch or find stock expired on the shelf.

So we built a pharmacy ERP in PHP and MySQL. The POS sells from a chosen stock location and always picks the batch that expires first, while purchases, purchase returns and stock adjustments keep every batch count right. Sales run from inquiry to quotation to sales order to invoice, and payments received and made, expenses, a chart of accounts and journal entries sit alongside — with eight roles, from pharmacist and cashier to accountant and warehouse manager.

Every unit sold now comes from a known batch and location, and stock, sales, supplier bills and payments are kept in one place instead of separate registers.

1. Purchase received
2. Batch stocked
3. Sold at POS
4. Payment recorded

A mobile phone shop in the Netherlands sells new phones and accessories, repairs phones, and buys used phones from the public. Buying second-hand legally means an ID, a stolen-phone check and a signed contract for every device — hard to keep straight on paper next to the till and the repair desk.

So we built a touch-first POS in PHP and MySQL for tablets and shop terminals: barcode sales with printed receipts and 21% VAT, a phones-and-accessories catalogue with suppliers and live stock, and a repair desk that takes each job from intake to repaired to delivered, with its own parts stock. The used-phone register records the seller's ID, a touch-screen signature and the IMEI check against the police stolen-goods register, then prints the purchase contract. Staff switch between Dutch and English, and three roles keep owner-only figures like profit and loss private.

A phone flagged as stolen can't be bought, every buy-in has its signed contract on file, and the owner sees profit and loss on one screen.

1. Seller ID captured
2. IMEI checked
3. Contract signed
4. Phone stocked

A school wanted its class tests to move online. On paper, every test has to be typed, printed, sat, marked script by script and then reported to each parent.

So we built an online exam platform in PHP and MySQL. Teachers keep a question bank by subject and topic — typed in, imported from CSV, or drafted by AI and approved by a teacher — and build timed exams for each class; students sit them in an exam room that saves every answer on the server and picks up again after a dropped connection. Objective questions mark themselves, short answers go to a grading queue, and a coordinator can watch exams live.

Results reach students and parents as soon as a teacher publishes them, and every exam ends with item analysis and a topic-weakness report.

1. Question bank built
2. Timed exam sat
3. Answers auto-graded
4. Results published

A restaurant needed one system behind the counter, the kitchen and the delivery riders. Running orders, kitchen tickets, riders, stock and the cash drawer by hand means a lot of paper and no clear picture at the end of the day.

So we built a restaurant POS in PHP and MySQL: counter and table orders, a kitchen display split by station, delivery riders and zones, and a public online menu where guests order for delivery or pick-up, or scan a QR code at their table. Behind it sit recipe-based stock deduction and recipe costing, purchasing, promotions and loyalty, reservations with a waitlist, and staff attendance with a selfie and GPS check-in, shifts, leave and payroll. Six roles — owner, manager, supervisor, cashier, storekeeper and procurement — each see their own part.

Online and table orders land straight in the POS and on the kitchen screen, every dish sold takes its ingredients out of stock, and each day ends with a cash drawer count and a day close.

1. Order placed
2. Kitchen display
3. Rider dispatched
4. Day closed

A support team needed one place for every customer request. Without it, tickets sat unassigned, replies slipped past their deadline, and nobody could see who was waiting on whom.

So we built a helpdesk in PHP and MySQL with five roles, from Super Admin down to Customer. Customers open tickets from a self-service portal after checking the Knowledge Base; each ticket routes to a department, goes to an available agent and runs on a per-priority SLA clock with warnings and escalation. Canned replies, automation rules, ticket merge, satisfaction ratings and alerts by email, WhatsApp, SMS and browser push are built in.

Every ticket now has an owner, a due time and a full timeline of who did what. Managers see SLA compliance and customer ratings per agent, department and period.

1. Ticket opened
2. Assigned to agent
3. SLA clock runs
4. Resolved and rated

A transfer business in Spain gets its bookings from partner providers as text messages. Each one had to be typed in by hand, and at month end someone had to work out what every provider owed and what every driver was due.

So we built a PHP and MySQL dashboard where a pasted booking message goes through a text parser and becomes a service — date, pickup time, origin, destination, passenger and flight number. Each service links a provider and a driver, shows the margin between the provider price and the driver pay, and syncs to Google Calendar. Bulk payments settle a provider's or a driver's whole month in one go, and route sheets and provider reports are saved as PDF versions.

Every transfer now carries its price, its driver payment and its margin, and every change to it is kept in an audit log. Month-end collections and driver payouts are one batch each, and a wrong batch can be reverted.

1. Booking text pasted
2. Service created
3. Driver assigned
4. Monthly payment batch

Vehicle owners in India have to keep their RC, insurance, pollution, fitness, permit and tax papers valid, and every renewal or ownership transfer means paperwork and chasing an advocate. A transport services business wanted to handle all of that for its clients from one place.

So we built a portal in PHP and MySQL with six roles — super admin, admin, advocate, agent, support staff and client. Clients add their vehicles and documents with expiry tracking, raise service requests for registration, renewal, ownership transfer, insurance or legal advice, book appointments and open helpdesk tickets, while advocates take the jobs, quote and ask for documents. Authorization letters are priced per state with notary charges and GST and carry a QR code, and subscriptions, invoices, wallets and built-in chat handle the rest.

Every vehicle's papers now have an expiry date the system watches. And every job has an advocate, a quote and a status the client can follow from their own login.

1. Client adds vehicle
2. Service request raised
3. Advocate quotes job
4. Wallet payment settled

A shop owner in India sells on credit (udhaar) every day. Keeping track of who owes what, who has paid and who to remind, by hand, means missed collections and arguments over balances.

So we built an online app in PHP and MySQL that works on phone, tablet and PC, in Hinglish, Urdu-English or English. It keeps each customer's udhaar ledger with a QR customer card, a credit grade and a credit limit, sends reminders and receipts over WhatsApp, and tracks cheques, aging and risky customers. Around it sit a POS for sales, items and stock movement, suppliers, employee attendance and salary, expenses, a cash book and profit & loss.

The dashboard now shows today's total outstanding, today's new credit and today's collections at a glance. Every customer's balance and history is one tap away.

1. Credit sale recorded
2. Balance updated
3. WhatsApp reminder sent
4. Payment collected

A warehouse business in Mexico brings in product loads bought in US dollars, with investors putting money into each load. Landed costs, sales, cash, payroll and each investor's share were spread across separate spreadsheets and papers.

So we built a warehouse system in PHP and MySQL with five roles — Owner, Admin, Warehouse Manager, Salesperson and Support. Each load records its dollar cost, exchange rate and shipping to give a peso cost per piece, and its stock flows into POS sales, orders, client credits and returns. Investors are linked to loads by capital and ownership share, next to the cash register, box closures, bank reconciliation, sales commissions, payroll with incidents and WhatsApp leads.

Each load now shows what it cost, what it sold and what it earned, and each investor sees their share of it. Every cash box is counted and closed at day end, and every action is logged.

1. Load arrives
2. Stock received
3. Sale at POS
4. Investor profit shared

A brick maker in India needed its GST billing and its stock in one place. Every batch of bricks made uses up raw materials, and every bill has to carry the right GST split — keeping both right by hand, bill after bill, is slow and easy to get wrong.

So we built a billing and inventory system on Google Sheets with a Production module: one entry adds the finished bricks to stock and takes each raw material out, and it refuses the entry if a material is short. Tax invoices print in a clean A4 layout with CGST, SGST or IGST picked from the customer's state, HSN codes, the vehicle number and e-invoice details with a QR block. Purchase orders, payments, returns, expenses, a stock ledger, a customer ledger, statements and low-stock alerts sit in the same app.

One production entry moves both the bricks and the raw materials, and each invoice comes out with the right GST split. It all runs on a Google Sheet, with no server to pay for.

1. Production logged
2. Stock updated
3. GST tax invoice
4. Payment and ledger

Running a busy salon means bookings, bills, product stock and staff pay all at once, and by hand they slip. This salon in Pakistan also wanted a before-and-after photo of every client's service, kept with the visit.

So we built a full salon system on Google Sheets: customers with a 360 view, appointments on a slot board with clash checks and a waitlist, online booking, POS invoices with payments, refunds and voids, product stock and purchase orders, staff attendance, leave, payroll and commission, a cash drawer with day close, and memberships and package cards. Each appointment now carries a before and an after photo, saved to Google Drive with a clear file name and shown side by side to compare.

Each client's visit keeps its before and after photos next to the booking and the bill, and customers are archived, never deleted. It runs as a live web app on the salon's Google Sheet.

1. Booking made
2. Client checked in
3. Before and after photos
4. Invoice and payment

A rent-a-car business in Pakistan sends cars out self-drive or with a driver, inside the city and outstation, and some of its cars belong to outside owners who take a share. Working out each return bill, the deposit, traffic fines and every owner's cut by hand is slow and easy to get wrong.

So we built a rental desk in PHP and MySQL with a Today board for pickups and returns, bookings with a live quote and clash checks, and a check-out and check-in wizard with readings, photos, a damage diagram, deposit and signature. When a car comes back the return bill is worked out on its own — rent, late hours, extra kilometres — alongside workshop jobs, traffic fines, car-owner statements with a read-only owner portal, and a public website that takes booking requests.

Every car's rent, costs and owner share are now on record, and owner statements are built from the same bill lines. Deposits are held for late e-challans before they are refunded.

1. Booking confirmed
2. Car checked out
3. Car checked in
4. Bill closed

A laundry business in Pakistan with several stores was running on a basic order system. It could take an order and a payment, but had no customer khata, no daily cash register, no garment tags, no delivery tracking and no quality checks.

So we built a full laundry system in PHP and MySQL: orders with services, add-ons, coupons and package deals, a tag for every garment, a quality checklist before release, and delivery management. Money is covered by a customer ledger, a cash register for each store and expense tracking, next to inventory, staff attendance, complaints and recurring orders. Four roles — admin, manager, cashier and staff — with each user tied to a store.

Every garment can be followed from drop-off to delivery, and each customer's balance and each store's daily cash are kept in the system. Customers can check their order status online without logging in.

1. Order booked
2. Garments tagged
3. Quality checked
4. Delivered & paid

A business in Pakistan kept its sales, bills and bank records in separate places. So profit, what customers owed and what was due to suppliers only became clear after someone pieced the numbers together by hand.

So we built a double-entry accounting system in PHP and MySQL: customers, estimates, invoices, sales receipts, payments and credit notes on one side; vendors, bills, bill payments and expenses on the other. Bank statements are imported from CSV and each line is matched or categorised, with journal entries, projects with time tracking, taxes and foreign-currency documents covered too. Every posting writes balanced debit and credit lines to one general ledger, under four roles: admin, accountant, sales and employee.

Profit and loss, balance sheet, cash flow, aging and tax reports are all worked out from that one ledger, so they always agree with each other.

1. Invoice raised
2. Payment received
3. Bank line matched
4. Reports from ledger