V
Vendly
Getting started

Getting started

How the modules connect to each other

Sales feeds Accounting feeds Banking. Inventory talks to Purchasing. Payroll posts to the ledger. Here's the full diagram in words.

How the modules connect to each other

Sales feeds Accounting feeds Banking. Inventory talks to Purchasing. Payroll posts to the ledger. Here's the full diagram in words.

Vendly is one product, not nine separate apps glued together. Every module posts to the same chart of accounts; every customer in CRM is the same record as the client on the invoice; every payroll run hits the same Bank account as a manual payment. Understanding what flows where is the difference between using Vendly and TRUSTING Vendly.

The four data spines

  • PEOPLE — Clients, Suppliers (Vendors), Employees, Users. Each module references one of these.
  • PRODUCTS / SERVICES — One catalogue used by Sales, Inventory and Purchasing.
  • CHART OF ACCOUNTS — One ledger used by every transaction that posts a journal.
  • PERIODS — One financial calendar. Closed months stay closed across all modules.

What flows where (sales side)

When you…Vendly also…
Convert a CRM lead to a ClientCreates the Client record visible in Sales
Issue an InvoicePosts Dr AR / Cr Sales + Output VAT to the ledger
Invoice a stocked productDecreases on-hand at the chosen warehouse
Mark an invoice PAID via M-PesaRecords a Bank Transaction in the M-Pesa account; clears AR
Issue a Credit NoteReverses (partially) the original invoice's ledger lines + restores stock

What flows where (purchases side)

When you…Vendly also…
Approve a Purchase OrderReserves expected stock at the warehouse
GRN against the POIncreases stock, posts Dr Inventory / Cr GRN Clearing
Record the Purchase InvoicePosts Dr GRN Clearing + Input VAT / Cr AP
Pay the supplierRecords a Bank Transaction; clears AP

What flows where (payroll side)

When you…Vendly also…
Add an Employee with KRA PIN + bank detailsAvailable on the next payroll run
Process a Payroll RunComputes statutory deductions (NSSF Tier I/II, SHIF, AHL, PAYE)
Approve the runPosts the salary journal: Dr Salaries / Cr Net Pay + statutory payables
Mark the run PAIDPosts the disbursement: Dr Net Pay Payable / Cr Bank
Generate the P10 / SHA / NSSF / AHL exportsBuilds CSVs from the same PayrollRecord history

Reports tie it all together

Because every transactional event posts a journal entry, the P&L / Balance Sheet / Cash Flow / Trial Balance are always reading the SAME ledger that the invoices, GRNs, payroll runs and bank transactions all post into. Click a number on a report → drill into the underlying journal → drill into the source document. No data lives in a silo.

If a report doesn't match a module's list — say, the Aged AR total doesn't match the Outstanding Invoices on the Invoices page — it's almost always a manual journal that bypassed an invoice, or a missing payment receipt. Fix at the source, never patch the report.

Module index

  • Sales — invoices, quotations, proforma, sales orders, credit notes, payment receipts, clients.
  • Purchases — purchase orders, GRN, purchase invoices, debit notes, payout receipts, vendors.
  • Inventory — products, services, categories, warehouses, stock takes, transfers, GRN, forecast.
  • Accounting — chart of accounts, journal entries, recurring journals, taxes, reconciliation, exchange rates.
  • Banking — bank accounts, M-Pesa, transactions, reconciliation.
  • Payroll — employees, salary components, payroll runs, payslips, statutory exports.
  • CRM — leads, pipelines, forms, automations, templates, reports.
  • HR — branches, departments, designations, attendance, leave, contracts, performance, training.
  • Reports — P&L, Balance Sheet, Cash Flow, Trial Balance, sales / inventory / payroll reports.