# Welcome to Looped (/) Looped is a suite of small, focused apps for running a service business. The apps are independent — use one or all — but they all share the same workspace, the same teammates, and a single subscription. ## The apps [#the-apps] * **[Looped Track](/track/)** — log time, track projects, run reports. * **[Looped Invoices](/invoices/getting-started)** — clients, quotes, sales orders, invoices and credit notes, sent by email with online payment. * **[Looped Financials](/financials/)** — double-entry books: bank statements, VAT, reports and annual financial statements. * **[Looped Payroll](/payroll/)** — pay runs, payslips and statutory filings for South African employers. * **[Looped Inventory](/inventory/)** — items, stock on hand, purchase orders, stock takes and price lists. * **[Looped Pay](/pay/)** — the page your clients land on to pay an invoice. * **[Public API](/api/)** — read and write your company's data programmatically. * **[Looped CLI](/cli/)** — work with Track, Invoices and Manage from your terminal. You'll do most of the day-to-day in those apps. Everything *about* them — who's on your company, what plan you're on, your branding, your bank details — happens in **Manage**. ## How everything fits together [#how-everything-fits-together] Sign in once at [app.looped.sh](https://app.looped.sh) and you land in Manage — the home for your **company**. From the Manage header you can switch into any app: ``` app.looped.sh/ ← Manage (default) app.looped.sh/track ← Looped Track app.looped.sh/invoices ← Looped Invoices app.looped.sh/financials ← Looped Financials app.looped.sh/payroll ← Looped Payroll app.looped.sh/inventory ← Looped Inventory api.looped.sh ← Public API (interactive reference) pay.looped.sh/ ← Looped Pay (client-facing) ``` A **company** is the unit you collaborate around. It owns your subscription, your members, your invoices, your time entries, and your settings. You can be in multiple companies — switch between them from the company picker in the header. ## What to read next [#what-to-read-next] If you're brand new, the **[Get Started](/creating-a-team)** path walks you through creating a company, inviting your first teammate, and picking a plan. If you're already up and running and want to administer the workspace — billing, members, API keys — head to **[Manage](/manage/roles)**. If you want to use a specific app, jump straight to its overview: * **[Looped Track](/track/)** * **[Looped Invoices](/invoices/getting-started)** * **[Looped Financials](/financials/)** * **[Looped Payroll](/payroll/)** * **[Looped Inventory](/inventory/)** ## Getting help [#getting-help] * 💬 Join our [Discord](https://discord.gg/euwUfRt3nt) * 📧 Email [support@looped.sh](mailto:support@looped.sh) # How Looped is structured (/concepts/platform) Most things in Looped revolve around a few simple ideas. Internalize these and the rest of the docs will read faster. ## Companies own everything [#companies-own-everything] Every piece of data — invoices, time entries, projects, clients, API keys — belongs to a **company**. When you sign in, Looped picks one of your companies as your *current* company and shows you that company's data. You can be in multiple companies (e.g. *Acme Studio* and *Personal*). Switch between them in the top-left company picker. ## Members and roles [#members-and-roles] A company has one or more **members**. Each member is an Owner, an Admin or a Member, and holds a list of roles for the other apps: | Base role | Can do | | ---------- | ----------------------------------------------------------------------------------------------------------------------------------------- | | **Owner** | Everything, including deleting the company and transferring ownership. A company can have several Owners. | | **Admin** | Runs the company account: people, company details, billing, API keys and integrations. Anything in the other apps comes from their roles. | | **Member** | Sees the company and its people. Anything in the other apps comes from their roles, such as Track Member or Bookkeeper. | See [Roles & permissions](/manage/roles). A company always has at least one Owner. The last Owner can't leave. ## One subscription per company [#one-subscription-per-company] Subscriptions are bought per company (a company, in the API). Two parts, bought separately or together: * **Business** — per company. Unlimited invoices, quotes and clients, full Financials, and free bookkeepers and viewers. * **Seats** — per person on Track, beyond the first free one. Every company starts with a 30-day Accounting trial (unlimited invoices and full Financials) and one free person on Track. After the trial, Free means 5 invoices a month and read-only Financials. The seat count must always cover the people on Track; adding one consumes a seat (and adds a new one if you're full). Lower the count by [removing members](/manage/member-management#removing-a-member) first. See [Purchasing a subscription](/purchasing-subscriptions) for prices, the Accounting trial and the founding plan. ## Apps share auth and company context [#apps-share-auth-and-company-context] You sign in once. Everything else inherits that session: * **Manage** is the gateway. It hosts the auth, the company settings, and the navigation that fans out to the other apps. * **Track**, **Invoices**, **Financials**, **Payroll** and **Inventory** live as subpaths under the same domain (`app.looped.sh/track`, `/invoices`, `/financials`, `/payroll`, `/inventory`). Switching between them keeps the same company context — no re-login. * **Pay** is *client-facing*. When you send an invoice by email, your client gets a unique link to a Pay page where they can pay you. They don't sign in. * **The Public API** lives at `api.looped.sh`. Authenticate with an [API key](/manage/api-keys) — no session needed. * **The [CLI](/cli/)** uses the same API from your terminal. You sign in with your own account, so it can do what your roles allow. ## Finding your way around [#finding-your-way-around] A few things work the same in every app: * **⌘K** (Ctrl+K on Windows) opens the command palette. It lists pages from every app you can open, filtered by your roles and your company's modules, so you can jump from Invoices straight to a Financials report. * **Search** on lists and pickers matches every word you type, in any order: "boot 13" finds "Addo Boot stc Size 13". * **Codes in pickers.** Clients, suppliers and sales codes show as "CODE · Name", and you can search by either. * **Page size.** Tables offer Show 25, 50 or 100 rows. The size you pick is remembered in your browser for every table. ## Currency lock [#currency-lock] Each company has a **currency** that's set when you create the company and locked the moment your first invoice is paid. After that point, the currency can't change — it lives on every past invoice. If you need to invoice in two currencies, [create a second company](/creating-a-team). ## What lives where [#what-lives-where] | Thing | Lives in | Visible at | | ----------------------------------------------- | ---------- | ----------------------------- | | Company name, currency, address, logo | Manage | *Settings* → *General* | | Billing & seats | Manage | *Billing* | | People | Manage | *People* | | API keys | Manage | *Settings* → *API Keys* | | Time entries, projects | Track | `/track` | | Invoices, clients | Invoices | `/invoices` | | Ledger, bank statements, VAT, annual statements | Financials | `/financials` | | Employees, pay runs, payslips, filings | Payroll | `/payroll` | | Items, stock, purchase orders, price lists | Inventory | `/inventory` | | Suppliers, supplier invoices | Financials | `/financials` | | Bank details (for invoices) | Manage | *Settings* → *General* → Bank | This model — one company, one subscription, multiple apps sharing the same identity — is what makes the platform feel small even though it does a lot. # Creating a company (/creating-a-team) A company is the workspace your subscription, members, and data sit inside. You can have as many companies as you want — switch between them in the company picker. ## Your first company is automatic [#your-first-company-is-automatic] The first time you sign in to [app.looped.sh](https://app.looped.sh), Looped creates a company for you with your name (or your email's domain) and makes you its Owner. You can rename it later from *Settings* → *General*. If that's the only company you'll ever need, you're done. Skip ahead to [Inviting team members](/inviting-team-members). ## Adding another company [#adding-another-company] Open a second company if you want to: * Keep a personal company and a business company apart * Bill clients in different currencies (currency is per-company and [locks](/concepts/platform#currency-lock) after the first paid invoice) * Run multiple businesses from one Looped account To create one: 1. Click the company picker (top-left, next to the Looped logo). 2. Click **Create company** at the bottom of the dropdown. 3. Pick a name and click *Create*. The new company becomes your current company automatically. Everything you do — invoices, time entries, settings — applies only to it until you switch away. ## Switching companies [#switching-companies] Click the company picker → pick a company. Looped reloads with that company as your current context. Each company's data is fully isolated; nothing leaks across. ## Renaming, currency, address [#renaming-currency-address] Open *Settings* → *General* to update: * **Name** — what shows up in the company picker and on invoices * **Currency** — locks once an invoice is paid (see [Currency lock](/concepts/platform#currency-lock)) * **VAT number** — surfaces on invoices * **Logo** — displayed on invoices and in your company's header * **Address** — used as the "From" address on invoices * **Bank details** — displayed at the bottom of invoices for EFT payments These details aren't required to use Looped, but they *are* required before you can [send an invoice](/invoices/sending-invoices). You fill them in on the **Company** page, and the setup checklist on the dashboard links to each step you still have to do. ## Next steps [#next-steps] 1. [Invite your team members](/inviting-team-members) 2. [Purchase a subscription](/purchasing-subscriptions) to unlock the apps 3. [Configure company settings](/team-settings) so your invoices look right # Inviting team members (/inviting-team-members) When you invite someone, you choose whether they join as an Admin or a Member, and which roles they start with. You can change both at any time on the **People** page. See [Roles & permissions](/manage/roles) for what each one allows. Only people who can log time in Track take a seat. On the Free plan, one person can use Track; to add more, [buy seats](/purchasing-subscriptions) first. Everyone else, such as Admins without a Track role, bookkeepers, auditors and people who only invoice, is free. ## Sending an invite [#sending-an-invite] 1. Open **People** in Manage and click **Invite people**. 2. Type one or more email addresses. Each one becomes a chip. 3. Choose **Member** or **Admin**. A new Member starts with **Track Member** ticked, so they can log their own time; a new Admin starts with no app roles. You can change the ticks. 4. Tick any other roles they need, such as **Invoices Admin** or **Bookkeeper**. To start from someone who already has the right access, use **Copy access from**. **What they'll have in each app** shows what it all adds up to. 5. Check the summary sentence, for example "They'll join as a Member with Track Member and Auditor. That takes a Track seat.", and click **Send invite**. Only an Owner can give Payroll Admin or Financials Admin (it sees the payroll figures), so an Admin sees them greyed out. If something is blocking the invite, such as no Track seats or no plan with Financials, the **Send invite** button says why. Looped emails each person a link. Their invite shows in the People grid as pending until they accept. ## What your teammate sees [#what-your-teammate-sees] The email has a button that opens the invite. After signing in, or signing up, with the address you invited: * **Accept** adds them to the company with the access you chose. * **Reject** declines the invite. You'll need to invite them again if they change their mind. If they sign in with a different email address, Looped asks them to sign out and use the right one. ## Inviting employees to their payslips [#inviting-employees-to-their-payslips] Employees who only need their payslips are invited from **Payroll**: 1. Open the employee's record in Payroll. 2. On the **My pay** card, click **Invite to My pay**. They join the company as a Member with no roles, so no other app opens for them, and they're linked to their employee record. After accepting, they see their payslips, tax working and IRP5s in **My Pay**, on their phone or computer. They don't take a seat. If you're on the payroll yourself and already in the company, open your own employee record and click **This is me**. My Pay then appears in your Payroll sidebar. To take My Pay away from someone, open their page in People and click **Unlink**. ## Resending or revoking [#resending-or-revoking] Each pending invite in the People grid has a menu with: * **Resend:** sends the email again, for example if it went to spam. * **Revoke:** cancels the invite. Invites expire after **7 days**. After that, send a new one. # Purchasing a subscription (/purchasing-subscriptions) Looped is priced in **modules**. You switch on the modules a company needs and pay for each one per company, per month. Track is the exception: it's priced per person. Every company starts with a 30-day trial of everything, then falls back to **Free**, and your accountant never costs anything. For current prices, see [looped.sh/pricing](https://looped.sh/pricing). If you're a bookkeeper or accountant paying for the companies you look after, see [looped.sh/pricing/bookkeepers](https://looped.sh/pricing/bookkeepers). ## Modules [#modules] | Module | Unit | What it covers | | -------------- | ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- | | **Accounting** | per company | The books: bank, supplier invoices, expense receipts, VAT, assets, loans and the general journal. Includes Financials and uncapped Invoices. | | **Financials** | per company | Annual financial statements, notes, tax and monthly reports from an uploaded trial balance. | | **Invoices** | per company | Uncapped invoices and quotes without Accounting. Free up to 5 a month. | | **Inventory** | per company | Items, stock takes and movements. Costs post to the ledger with Accounting. | | **Payroll** | per company, by employees | Pay runs, payslips and SARS returns. South Africa only. Priced in bands: up to 20 employees, 21–50, 51–100, then per employee over 100. | | **Track** | per person | Time tracking. One person is free without a plan. | Every module can be paid monthly, or annually at 11 months for 12. Payroll's band is counted from the company's employees in Payroll, not its people in Looped. You don't need to change anything: when the count crosses into another band, the price updates automatically from the next billing date. Modules are independent: take Invoices on its own, Accounting with Payroll, Track seats without any module, or any mix. A company with Accounting doesn't pay for Financials or Invoices, because Accounting includes them. For now, a company with Accounting also gets **Payroll** and **Inventory** at no extra charge. Bookkeepers and viewers are free and unlimited, and online payments on invoices and Manage are included for everyone. South African companies pay in rand, everyone else in US dollars. No VAT is added at checkout: the price shown is what you pay. Billing is handled by Looped Automation LLC. ## What Free includes [#what-free-includes] * **Track** for one person. * **Invoices**: up to 5 invoices and quotes sent per calendar month, with online payments. * **Manage**: members, settings and billing, always open. * Employees can always open [My pay](/payroll/my-pay). Accounting, Financials, Inventory and Payroll need their module. Without it, they stay closed, or read-only if the company had them before (see below). ## The 30-day trial [#the-30-day-trial] You don't need a card to try Looped. Every new company gets a **30-day trial** that starts the moment the company is created, and the trial gives **every module**. The billing page and the Financials app show how many days are left. Buying a module ends the trial straight away: billing starts, and from then on the company has the modules it pays for. ### After the trial [#after-the-trial] If you don't subscribe before the trial ends, everything the trial gave goes **read-only** until you buy the module: * **Accounting, Financials, Inventory and Payroll** stay visible (statements, journal, reports, everything you entered), but nothing new can be added or changed. * **Invoices** falls back to 5 sends a month, and **Track** to one person. Every invoice and quote you already made stays available. Nothing is deleted. Switching on a module lifts its limit straight away. The same applies later: a module whose subscription ends becomes read-only, and Invoices and Track fall back to their free tier. ## What is a seat? [#what-is-a-seat] A seat is a person with **write access to Track**. One person on Track is free, with or without a subscription. Once a second person is on Track, everyone on it has a seat: two people, two seats. People who never take a seat: * **Invoicing-only members**: invoices are covered by Invoices or Accounting, not by seats. * **Bookkeeper**: full access to the books only. Invite your accountant with this preset. * **Viewer**: read-only everywhere. You choose each person's access when you invite them, and you can change it later on the *People* page. Giving someone Track takes a seat; taking it away frees one. ## Buying [#buying] 1. Sign in to [app.looped.sh](https://app.looped.sh) and switch to the company you want to subscribe. 2. Open *Billing* in Manage (Owners and anyone with Manage Full). 3. Switch on the modules you want, and set the number of **Track seats** if more than one person tracks time. Switching on Accounting marks Financials and Invoices as *Included in Accounting*. The seat count can't go below the people already on Track (minus the free one). 4. Choose **Monthly** or **Annual · 1 month free** (annual is 11 months for 12). 5. Click *Continue to checkout*. You'll be sent to **Stripe Checkout** to enter card details. After paying, you're back in Looped and can invite people straight away. If you already have a subscription, the same page changes it in place: click *Review change*, confirm, and the difference is prorated on your next invoice. Stripe handles all card data. Looped never sees or stores your card number. ## Seats after you subscribe [#seats-after-you-subscribe] * Inviting another person to Track when your seats are full adds a seat automatically (prorated on the next invoice). * Bookkeeper, viewer and invoicing-only invites never change your bill. * To pay for fewer seats, change or remove members first, then lower the count on the billing page. ## If you subscribed before modules [#if-you-subscribed-before-modules] Companies already on the earlier per-company plan keep it. It now shows as **Accounting**, at the same price and with the same access, including Payroll and Inventory. Seats you already pay for carry on as Track seats. You don't need to do anything. ## Founding customers [#founding-customers] Companies that subscribed on the founding **Looped One** price keep it: **every app, unlimited invoices and full Financials at their founding per-user price, for as long as they stay subscribed.** Module prices don't apply to a founding subscription, and the billing page shows it as *Looped One · founding*. ## Companies that manage others [#companies-that-manage-others] A company that manages other companies, such as a bookkeeping practice with its clients or a holding company with its subsidiaries, pays for all of them on one monthly invoice. Turn on *This company manages other companies* in General settings, then choose your plan on its *Billing* page. On *Billing*, the **Companies** list shows each company you manage, this one included, with a switch per module. Switch on what each company needs; the same rules apply as for a single company, so a company with Accounting isn't charged for Financials or Invoices. **Track seats here** sets the paid seats in the managing company itself. **Your bill** adds it all up per module, and *Start subscription* opens Stripe Checkout (or *Review change* updates a plan you already have). Every company pays the module's list price, this one included: one login and one bill, with no volume bands. Payroll goes by each company's employees. Track bills each person on Track in a managed company. It's monthly only. If your plan is billed yearly, switch it to monthly in *Manage subscription* first. Linking or unlinking a company, or switching a module, changes the bill straight away, prorated. A company that pays for its own plan can only be linked once that plan has ended, so nobody pays twice. While a company is managed, it can't buy a plan of its own, and its *Billing* page says who pays for it. Practices that already had a managed-companies plan keep their earlier prices. ### Partner program [#partner-program] Accounting practices and bookkeepers can apply to be **partners** from the *Partner program* card on *Billing*. We approve each application, and there's no minimum number of companies. A partner's own company must be on **Accounting**: it isn't free, and it counts as one of the partner's companies. A partner's whole bill is discounted, every module on every company, by its number of companies: | Companies | Discount | | ---------- | -------- | | 1–9 | 10% | | 10–24 | 20% | | 25–49 | 30% | | 50 or more | 40% | You can apply before or during a subscription. Partner prices start from your next billing date, and the same happens whenever you move into another tier. If the managing company's payment fails, its managed companies keep working through the same 7-day grace period. If the plan ends, each managed company falls back to its own trial, or its modules go read-only until it is subscribed again. ## Managing your subscription [#managing-your-subscription] Once you're subscribed, the billing page shows **Manage subscription**. That opens the **Stripe Customer Portal** where you can: * Switch between monthly and annual * Update your card and billing address * Download past invoices * Cancel at the end of the current period ## Failed payments and cancelling [#failed-payments-and-cancelling] If a payment fails, Stripe retries automatically and the billing page shows a warning. You have a **7-day grace period** to settle the bill. After that, if more than one person is on Track, the company is **paused**: Track is closed until the bill is settled or the people on it are reduced to one. Your other modules and Manage are not affected by the seat pause. If you cancel, the subscription runs to the end of the current period. After that the modules you paid for go read-only and Invoices returns to 5 sends a month; Track pauses if more than one person is still on it. Your company and its data stay intact, and you can re-subscribe at any time. # Company settings (/team-settings) Who your company is gets entered once, in Manage, and every app reads it from there: invoices, financial statements, payslips and SARS filings. Open **Settings** in the Manage sidebar. Two pages hold it: * **General**: the company's name and avatar, company ID and currency. * **Company**: legal details, address, tax and registrations, employer registrations, contacts, bank accounts and the logo. Any member can see these pages. Owners and Admins can change them. ## Quick Start [#quick-start] The fastest way to fill in the basics is **Quick Start** on your dashboard. Paste your business website's URL or upload an existing invoice PDF and Looped extracts the company name, address, currency, VAT number and bank details where it finds them. Review what it found, fix anything that's wrong and save. ## General [#general] | Field | What it's used for | | ------------------- | ------------------------------------------------------------------------------------------------------------------- | | **Name and avatar** | The company picker and the header | | **Company ID** | A short ID used in some shared links and the company picker | | **Currency** | Set on every invoice. Locks once your first invoice is paid (see [Currency lock](/concepts/platform#currency-lock)) | ## Company [#company] ### Details [#details] **Legal name**, **Trading name**, **Entity type**, the registration number (its label follows your country, such as the CIPC number in South Africa), **Incorporation date** and **Country**. The legal name prints on invoices and financial statements. The country decides which tax fields and apps apply; Payroll, for example, only opens for South African companies. ### Address [#address] The physical address, and a postal address unless you tick **Postal address is the same as the physical address**. Addresses use the structure SARS asks for, so payroll filings can use them as they are. The physical address is the "From" address on invoices; you can't [send an invoice](/invoices/sending-invoices) without one. ### Tax & registrations [#tax--registrations] Whether you're registered for VAT (or your country's sales tax), your VAT number and the date you registered from, and your income tax number. The VAT number prints on invoices, and the registration date decides from when Financials charges VAT. ### Employer [#employer] South African companies only. The **PAYE reference**, **UIF reference**, **UIF registration number**, **SDL reference**, **SIC code** and **COIDA registration number** appear on payslips, the EMP201 and the EMP501. See [Setting up Payroll](/payroll/setting-up). ### Contact [#contact] The company's **Email** and **Phone**, printed on invoices. South African companies also have a **SARS contact person**: the person SARS and the Department of Labour contact about your payroll submissions. Payroll puts their name, phone and email on the EMP501 reconciliation file, and their name on the monthly UIF declaration. Nothing else in Looped uses it. It isn't required: leave it blank until you run your first UIF declaration or EMP501. If its phone or email is blank, the EMP501 uses the company's email and phone instead. Nothing on the Company page is required to save it. South African numbers that don't look right get a warning but still save. ### Bank accounts [#bank-accounts] The accounts the company is paid into and pays from. Invoices print one for clients paying by EFT, Payroll pays salaries from one, and Financials can link a ledger account to one. If you'd rather only take card payments, leave them out and the section won't show on invoices. ### Logo [#logo] PNG, JPG or WebP; square images work best. It prints on invoices and other documents. ## Next steps [#next-steps] * Once your details are right, [send your first invoice](/invoices/sending-invoices) * Or [invite teammates](/inviting-team-members) to start working together # Roles & permissions (/manage/roles) Everyone in a company is an **Owner**, an **Admin** or a **Member**. That decides what they can do with the company itself: its people, details, billing and settings. What they can do in Track, Invoices, Financials, Payroll and Inventory comes from the **roles** they hold on top. You set both on the **People** page. ## Owner, Admin and Member [#owner-admin-and-member] | | Owner | Admin | Member | | ------------------------------------------------ | ----- | ----- | ------ | | See the company and their own profile | Yes | Yes | Yes | | See the company's people | Yes | Yes | Yes | | Invite, remove and change people (not Owners) | Yes | Yes | No | | Create and edit custom roles | Yes | Yes | No | | Company details, addresses, bank accounts, VAT | Yes | Yes | No | | API keys and integrations | Yes | Yes | No | | Billing and the company figures on the dashboard | Yes | Yes | No | | Make or change an Owner | Yes | No | No | | Rename or delete the company | Yes | No | No | **Owners** can do everything in every app, salaries included, and you can't narrow that down. A company can have more than one Owner and always keeps at least one. We didn't build a way to step down: an Owner stays an Owner until they leave the company or another Owner removes them, and the last Owner can't leave. **Admins** run the company account. Being an Admin doesn't open any other app by itself, so an Admin who also does the books needs the Financials Admin role as well. **Members** see the company and who's in it. Everything else they can do comes from their roles. ## Roles decide what people do in the apps [#roles-decide-what-people-do-in-the-apps] A role is a named set of permissions. Someone might hold **Track Member** and **Auditor**, and they get everything in both. Roles add up, so giving someone another role only ever adds to what they can do. An app none of their roles cover doesn't show up for them at all. Looped comes with these roles: | App | Role | What they can do | | ---------- | -------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- | | Track | **Track Admin** | Everything in Track: everyone's time, reports, projects, rates and settings | | | **Track Member** | Their own time, todos and reports, and nobody else's time | | Invoices | **Invoices Admin** | Everything in Invoices, settings included | | | **Invoices Member** | Drafts, sends and credits invoices and takes payments, without managing clients or settings | | Financials | **Financials Admin** | Everything in the books, including year end, VAT, paying supplier invoices and the payroll figures | | | **Bookkeeper** | Everyday work: bank lines, supplier invoices and journals, without year end, VAT filing or paying supplier invoices. Sees salary payments in the bank | | | **Auditor** | Sees the books, reports and invoices and changes nothing (Financials and Invoices). Sees salary payments in the bank | | Payroll | **Payroll Admin** | Everything in Payroll, salaries, ID numbers and bank details included | | Inventory | **Inventory Admin** | Everything in Inventory, costs and settings included | | | **Stock Controller** | Items, costs, purchase orders, stock takes and adjustments, without Inventory settings | | | **Stock Counter** | Sees items and counts stock, without costs, and posts nothing | These roles are fixed, and they follow new permissions in their app without anyone editing them. If a role doesn't fit, copy it to a custom role and change the copy. ### Payroll is all or nothing [#payroll-is-all-or-nothing] There's one Payroll role, and it shows everyone's salaries, ID numbers and bank details. Because that's sensitive, only an Owner can give it, and only an Owner can make or change a custom role that includes anything from Payroll. Admins see those roles greyed out with "Only an Owner can give this role". Every grant of salary or bank access is recorded in the person's activity. The same goes for the payroll figures in Financials. At a small company a pay run's gross, PAYE and net pay are someone's salary, so Financials' payroll page needs **See payroll figures**. Financials Admin has it, which makes Financials Admin an Owner's to give too. Bookkeeper and Auditor don't: they still see the Salaries account in the ledger and the salary payments in the bank lines, which bookkeeping needs, but not the payroll page. ## My Pay [#my-pay] Seeing your own payslips isn't something you tick. Anyone linked to their employee record in Payroll gets **My Pay**: their own payslips, tax certificates and tax working. The People page shows it in the Payroll column, and the person's page shows it under their roles with an **Unlink** button. Unlinking takes My Pay away. Ending their employment in Payroll doesn't, so a leaver can still download their payslips and IRP5. My Pay can only ever show someone their own records. See [Inviting team members](/inviting-team-members) for how employees are invited. ## Custom roles [#custom-roles] When the standard roles don't fit, make your own. Open **Settings → Roles** and click **New role**, or click **Copy** on a standard role to start from it. The editor lists every permission in Looped, grouped by app and split into: * **Can see:** what they can view. * **Can do:** what they can change. * **Sensitive:** salaries, bank details, ID numbers, payroll figures and billing rates. Tick what the role should allow, name it and save. A custom role can cover several apps and applies in every app it covers. For example, a "Books and billing" role could do everyday Financials work and draft invoices, and anyone who holds it gets both. When you change a custom role, everyone who holds it gets the new permissions straight away. If you delete one that people hold, Looped asks what to give them instead: nothing, or another role. Their other roles stay as they are. ## Changing someone's access [#changing-someones-access] 1. Open **People** in Manage. 2. To make someone an Admin or a Member, right-click their row and choose **Make Admin** or **Make Member**, or use the switch on their page. 3. To change their roles, click their **Roles** cell, or open their page, and tick or untick roles. Each change saves straight away, and the toast after a role change has **Undo**. Anything you can't choose is greyed out with the reason, such as "Needs a plan with Financials" or "No Track seats free". For more on the People page, see [Managing members](/manage/member-management). ## The assistant [#the-assistant] The Looped assistant, in chat, through MCP or in routines, works with your access minus a few things only a person should do: * finalising a pay run that has changes, or reversing one; * changing bank details; * filing returns; * closing or reopening a financial year. It can still prepare that work for you to review. ## If your company used Looped before these roles [#if-your-company-used-looped-before-these-roles] Everyone kept exactly the access they had when we moved to Owner, Admin and Member. Owners stayed Owners. People who could manage the company became Admins, with Track Admin, Invoices Admin and Financials Admin if that's what they had before. Everyone else became a Member with the roles that matched what they could do, and where no standard role matched, a custom role holding exactly their old access. You can tidy those up whenever you like. Financials' payroll page is the one exception. It now needs See payroll figures, which only Financials Admin has, so someone who could only read Financials no longer sees it. An Owner can give them Financials Admin, or add See payroll figures to their custom role. # Managing members (/manage/member-management) The **People** page in Manage is where Owners and Admins look after who is in the company and what they can do. Open it from the sidebar on [app.looped.sh](https://app.looped.sh). ## The People grid [#the-people-grid] Each person is a row. The **Role** column says whether they're an Owner, an Admin or a Member, and the **Roles** column lists the roles they hold. Then comes a column for each app, in the same order as ⌘K: Track, Invoices, Financials and Payroll. Those cells show what the person's roles add up to in that app (Everything, Some, or a dash for no access), so you can compare people by reading down a column. You change roles, and the app columns follow. * **Owners** show "Everything" in every app, and their rows can't be changed. * **A lock icon** marks anyone who can see salaries or bank details. * **My Pay** in the Payroll column marks people linked to their employee record. * **Pending invites** are rows too, with "Invited 2 days ago" under the email. Owner, Admin, Member and the roles are explained on [Roles & permissions](/manage/roles). ## Making someone an Admin or a Member [#making-someone-an-admin-or-a-member] Right-click a person's row and choose **Make Admin** or **Make Member**, or use the switch at the top of their page. Their roles stay as they are. Only an Owner can make someone an Owner, with **Transfer ownership** on their page. ## Changing someone's roles [#changing-someones-roles] 1. Click the person's **Roles** cell. The Roles picker opens. 2. Tick a role to add it, or untick it to take it off. The roles are grouped by app, with the ones that cover several apps at the end. Each tick saves straight away, and the toast has an **Undo** button. Anything you can't choose is greyed out with the reason beside it. Only an Owner can give Payroll Admin or Financials Admin, and giving either asks you to confirm first, since they show what people are paid. The grid works with the keyboard too: use the arrow keys to move between cells, and press Enter on a Roles cell to open the picker. ## A person's page [#a-persons-page] Click someone's name to open their page. It shows: * **Role in the company:** Admin or Member; * **Roles:** the same picker, to tick and untick their roles, and **My Pay** with an **Unlink** button if they're linked to their employee record; * **In each app:** what their roles add up to, one line per app, with the permissions underneath; * **Activity:** recent changes to their access, and who made them; * **Transfer ownership** (Owners only): the person becomes an Owner too, and you stay one. * **Remove from company.** ### Removing someone [#removing-someone] Removing a person ends their access straight away. Their work stays in the company: time entries, invoices and projects all remain. If they were linked to an employee record, they can no longer open My Pay. Someone with Payroll access can still email them their payslips and IRP5s from the employee's record. A few rules apply: * You can't remove yourself. Use [Leave company](/manage/danger-zone) instead. * The last Owner can't be removed or leave. ## Pending invites [#pending-invites] Invites show in the grid until they're accepted, or until they expire after 7 days. Each invite row's menu has: * **Resend:** sends the email again. * **Revoke:** cancels the invite. The link then shows "this invite is no longer valid". ## Track seats [#track-seats] Anyone who can log time in Track takes a seat. One person on Track is free; from the second, everyone on Track has a seat. Admins without a Track role, and everyone who only uses the other apps, don't take a seat. The page header shows how many seats are in use and links to **Add seats**. Removing someone doesn't free a seat by itself. To pay for fewer seats, [lower the seat count](/manage/billing-details#changing-the-seat-count) on the billing page. # Billing details (/manage/billing-details) The **Billing** page is where you choose and change your company's plan. Open it in Manage. It's for Owners and anyone with Manage Full. For prices and what each plan includes, see [Purchasing a subscription](/purchasing-subscriptions). ## Page layout [#page-layout] The billing page builds your plan from two parts: * **Business** (per company): a switch for Financials. Shows your trial status while the 30-day trial runs, and when it ended. * **Seats** (per person on Track): a counter, with how many people are on Track today. One person is free; from the second, everyone on Track has a seat. You can add seats to a Business subscription at any time. * **Interval**: monthly or annual (11 months for 12), and the total you'll pay. With no subscription, the action is *Continue to checkout* → Stripe Checkout. With a live subscription it's *Update subscription*, which changes it in place, plus *Manage subscription* → Stripe Customer Portal. Founding customers on the original Looped One price see their founding plan instead; see [Founding customers](/purchasing-subscriptions#founding-customers). A company that manages others sees one **Plan** card instead, billed monthly with no annual option. It has two parts: **Companies**, the number you pay for, which counts this company as one of the companies and can't go below the ones in use, with how they fall in the price bands; and **Track seats**. Below them is one monthly total and one button: *Start subscription* without one, *Update* once you have one. Linking or adding a company beyond the number you pay for raises it automatically; no longer managing one doesn't lower it. A managed company's page says which company manages it and pays for it, with no plan to choose; see [Companies that manage others](/purchasing-subscriptions#companies-that-manage-others). ## Changing the seat count [#changing-the-seat-count] 1. On the billing page, use the **Seats** counter. 2. Click *Update subscription*. Stripe prorates immediately — adding seats charges a partial amount now, removing seats credits future invoices. The seat count must cover the people on Track (minus the free one). Looped will refuse to lower it past that. To shrink: [remove members](/manage/member-management#removing-a-member) or take away their Track access first, then update seats. Inviting another person to Track when your seats are full **automatically** adds a seat. So most companies never have to bump it manually. ## Adding or removing Business [#adding-or-removing-business] Turn the **Business** switch on or off and click *Update subscription*. Adding it takes effect immediately, prorated. Without Business, the Financials app is read-only and Invoices is limited to 5 sends a month. ## Switching between monthly and annual [#switching-between-monthly-and-annual] Click *Manage subscription* on the billing page → you're redirected to the Stripe Customer Portal, where you can change the billing cycle and update payment methods. ## Cancelling [#cancelling] Also through the customer portal: 1. Click *Manage subscription* on the billing page. 2. Choose *Cancel subscription*. 3. Cancellation takes effect at the end of the current period — confirm and you're done. After the period ends, your company returns to **Free**: Financials is read-only, Invoices is limited to 5 sends a month, and Track is paused if more than one person is still on it. **Your data stays intact** — invoices, time entries, clients, your accounting records. Re-subscribe at any time to reactivate. You can't [delete a company](/manage/danger-zone#deleting-a-team) while a subscription is active. Cancel first. ## Past invoices and receipts [#past-invoices-and-receipts] The customer portal lists every invoice from your subscription, with a download link for each PDF receipt. Useful at end of financial year. Click *Manage subscription* → *Billing history*. ## Failed payments [#failed-payments] If a charge fails (expired card, insufficient funds), Stripe retries automatically and your subscription enters `past_due`. Track shows a warning banner, and you have **7 days** to settle. Open the customer portal, update your payment method, and Stripe retries. If the grace period ends unpaid and more than one person is on Track, the company is paused: Track is closed until the bill is settled. Invoices, Financials and Manage stay open. ## Why the customer portal instead of an in-app form [#why-the-customer-portal-instead-of-an-in-app-form] Stripe's portal handles the regulatory complexity (3-D Secure for re-auth, regional taxes, mandates, refunds). We trust Stripe to do that better than we'd do it ourselves, and the portal is exactly the same one Stripe shows on its own platform — no surprises. # API keys (/manage/api-keys) API keys let scripts, services, and third-party integrations talk to Looped on behalf of your company. Every key is scoped to a single company and a set of permissions. The API keys page is for Owners and anyone whose Company role includes "Manage API keys" (the Admin role does). Open it from *Settings* → *API Keys*. ## Creating a key [#creating-a-key] 1. Click *Create API Key*. 2. Give it a memorable name — *"Zapier production"*, *"Reporting service"*, *"Joe's laptop"*. The name only matters to you. 3. Pick its [permissions](#permissions): a role in each app the key needs, or specific permissions. 4. Optionally set an **expiration date**. After that date, the key stops working. Leave empty for non-expiring keys. 5. Click *Create*. A success screen appears with the **raw key** — it starts with `looped_`. **Copy it now.** Once you close that screen, the key cannot be retrieved (we only store its hash). If you lose it, [revoke it](#revoking-a-key) and create a new one. Hand the key to the integration that needs it (their dashboard, your company's secrets manager, an `.env` file, whatever). ## Permissions [#permissions] A key holds permissions directly. For each app the API reaches (Company, Track, Invoices, Financials and Inventory) you pick Read-only, Full or *Specific permissions*, and with Specific permissions you tick exactly what the integration needs. A key can't do more than the person who makes it. Roles and permissions your own role doesn't include are greyed out, and the API refuses them too. A key also never gets billing or the right to manage other API keys. On the wire each permission has a name like `track:time.write` ("Log own time") or `invoices:invoices.send` ("Send invoices"). `GET /v1/whoami` lists a key's permissions, and a `403` names the permission that was missing. Keys made before September 2026 held coarse scopes such as `write:time`. They keep working with exactly the access they had: Looped reads each old scope as the permissions it covered, and the key's details show those permissions. Creating a key through the API with the old scope names still works too, but it's deprecated. ## Using a key [#using-a-key] Send the key in the `X-API-Key` header on every request to `https://api.looped.sh`: ```bash curl https://api.looped.sh/v1/invoices \ -H "X-API-Key: looped_..." ``` The key carries the company scope — you don't pass `teamId` separately. The full endpoint reference lives at [api.looped.sh](https://api.looped.sh) (interactive Scalar UI) or [api.looped.sh/openapi.json](https://api.looped.sh/openapi.json) (machine-readable). ## Editing a key [#editing-a-key] To rename a key or adjust its permissions / expiration: 1. Click the **⋯** menu on the key's row → *View Details*. 2. Click *Edit*. 3. Change the name, permissions or expiration. 4. *Save Changes*. The key value itself does not change — your integration keeps working with the same `looped_...` value. ## Revoking a key [#revoking-a-key] Revoking immediately invalidates the key but keeps the row around so you can audit which key did what later. Use this when a key is leaked or rotated. 1. Click the **⋯** menu → *Revoke Key*. 2. Confirm. The badge flips from *Active* to *Revoked* and any further calls return `401`. ## Deleting a key [#deleting-a-key] Deleting removes the row entirely. Use this for keys created in error or that you don't need to keep on record. 1. Click the **⋯** menu → *Delete Key*. 2. Confirm. The key disappears from the table. ## Status badges [#status-badges] | Badge | Means | | ----------- | -------------------------------------------------------------------------------------------------------------------- | | **Active** | Authenticates successfully | | **Expired** | Past its expiration date. Edit it via *View Details* to set a new expiration if you want to reactivate, or delete it | | **Revoked** | Manually revoked. Cannot be reactivated — create a new key | ## Last-used timestamp [#last-used-timestamp] Each key shows a "last used" relative timestamp on the table. Useful for spotting keys that haven't run in months — candidates for cleanup. ## Best practices [#best-practices] * Give each integration its own key. Don't share a single key across services. Easier to rotate and audit. * Give a production key only the permissions its integration uses. Picking specific permissions is usually tighter than a whole role. * Set **expirations** on keys you'll only need temporarily (e.g. a one-off migration script). * Rotate keys periodically — every 90 / 180 days is a sensible default for production integrations. * If you suspect a leak, revoke first, ask questions later. # Notifications (/manage/notifications) Some notifications are the company's to decide: whether they go out, and who hears about them. You choose both in Manage, under *Settings* → *Notifications*. Each kind has its own card: * **Invoice paid**: when a client pays an invoice. * **Filing deadlines**: SARS and CIPC filings coming up or due. This card only shows for South African companies. On each card you can: * switch it on or off * add the people in your company who should be told, one at a time or with **Add everyone with access** * add other email addresses, such as your bookkeeper's or your outside accountant's Save the card when you're done. Switching it off takes effect straight away and tells nobody until you switch it back on. **Add everyone with access** adds the people who have access today; someone who gets access later isn't added until you add them. Which filing deadlines Looped tracks, and how many days ahead the first reminder goes out, are set in Financials under *Settings* → *Reminders*. ## Who can be told [#who-can-be-told] A notification only goes to people who can see what it's about: | Card | Who can be chosen | | ---------------- | ---------------------------------------- | | Invoice paid | People who can see invoices in Invoices | | Filing deadlines | People who can see reports in Financials | Owners can always be chosen. If someone on a card loses that access, they stop being told, and the card shows a badge such as **No Invoices access** next to their name so you can see why. Give them the role again, or take them off the card. People who leave the company stop being told too. ## How each person hears about it [#how-each-person-hears-about-it] The people you add get the notification in the bell in the header. Whether it also arrives as a push notification on their devices or as an email is their own choice, in *Profile* → *Notifications*, under **From your company**. Push is the default. That page also tells each person whether your company tells them about each kind. Turning both push and email off is how someone mutes a notification: it still lands in their bell. To be taken off a card, they ask someone who can change it. The extra addresses you add get an email. ## Who can change it [#who-can-change-it] Owners and Admins can change every card. People who can change an app's settings can also change that app's card: anyone who can change Invoices settings can change **Invoice paid**, and anyone who can change Financials settings, such as an Accountant, can change **Filing deadlines**. They only see the cards they can change. # Danger zone (/manage/danger-zone) The **Danger Zone** is the page that hides two destructive actions: **leaving** a company you're a member of, and **deleting** a company entirely. Both are irreversible. Open it from *Settings* → *Danger Zone* in the company settings nav. ## Leaving a company [#leaving-a-company] Leaving immediately revokes your access. You'll need to be re-invited to rejoin. 1. Click *Leave* in the **Leave company** card. 2. Confirm in the modal. You're redirected to one of your other companies (or to a "no companies" landing page if this was your only company — see below). ### When you can't leave [#when-you-cant-leave] * **You're the only Owner.** Looped shows *"You are the only owner of this company"* and replaces the leave button with a link to *People*. Make someone else an Owner first with **Transfer ownership** on their page, then leave, or [delete the company](#deleting-a-team) if it's no longer needed. * **It's your last company.** Looped requires every account to belong to at least one company. Create another company first. If you're leaving because you no longer want any access at all (e.g. ending a contract relationship), leaving is the right choice — your work stays in the company and the remaining members keep using it. ## Deleting a company [#deleting-a-company] Deleting removes the company and **all of its data, permanently**. Invoices, time entries, clients, projects, members, settings — gone. There is no undo. Only an Owner can do this. 1. Click *Delete* in the **Delete company** card. 2. Type `delete my company` exactly into the confirmation input. 3. Click *Delete Team*. ### When you can't delete [#when-you-cant-delete] * **Active subscription.** Cancel first via [Manage Subscription](/manage/billing-details#cancelling) → wait until the period ends and the company returns to Free. * **Last company.** Same rule as leaving — create another company first. * **Not an Owner.** Everyone else sees an info card on the danger zone page instead of the action button. After delete, all team members lose access immediately. You're returned to the company picker, where another company becomes your current one. ## Use cases [#use-cases] * **Leave**: you've finished a contract / left a company. The company continues without you. * **Delete**: the business is shutting down, or the company was a test you never used. Everything goes. * **Transfer ownership**: don't delete and recreate. Use **Transfer ownership** on the other person's page, which makes them an Owner too. If you no longer want to be involved, leave the company here. ## Recovery [#recovery] If you delete a company by mistake there's no recovery path on the user side. Contact [support@looped.sh](mailto:support@looped.sh) and we'll see what's possible — recent deletes can sometimes be restored from backups, but it's not guaranteed. # Looped Track (/track) Looped Track is the platform's time-tracking app. Open it at [app.looped.sh/track](https://app.looped.sh/track). You'll do most of your tracking from the **time-logger** on the home page — quick task name, hours, project, done. Once entries pile up, [reports](/track/reports) summarize them however you need (date range, project, client). Calendar integrations ([Google](/track/integrations/google-calendar), [Microsoft](/track/integrations/microsoft-calendar)) and [Todoist](/track/integrations/todoist) let you pre-fill entries from places you're already keeping track. ## Logging time [#logging-time] The form on the home page takes: | Field | Format | Notes | | --------- | -------- | ------------------------------------------------------------------ | | Task name | text | What you worked on. Required. | | Duration | hours | Stored internally as seconds; UI shows hours (e.g. `1.5` = 90 min) | | Project | dropdown | Optional. See [Projects](/track/projects) | | Date | picker | Defaults to the current Friday (week-ending date) | Type the task name → press Tab → type the duration → press *Log Time* (or hit Enter). The new entry appears in the list below, grouped by date. Entries from earlier in the week show in the same list — adding back-dated time is just changing the date field. ## Editing & deleting [#editing--deleting] Click any entry to open it in a modal: * Rename the task * Adjust duration * Move it to a different date * Reassign to a different project * Add tags (see [Tags](/track/tags)) Save. Or trash-icon to delete. ## Weekly view [#weekly-view] The home page is fundamentally a weekly view. The **Weekly Total** badge in the corner shows your hours for the visible week. Scroll back/forward through dates to navigate weeks. If you'd rather slice differently, build the view in [Reports](/track/reports). ## Goals [#goals] Set your own goals under **Settings › Goals**, and the dashboard shows how you're doing against them for the week or month you're looking at: * **Workdays.** The days you work. Goals and the reminder to log your time both use them. South African public holidays are skipped when your company is in South Africa. * **Daily hours goal.** The hours you want to record on each workday, 8 to start with. * **Billable time goal.** The share of your recorded time that should be billable, for example `75`%. The dashboard's **Goals** stat shows a pair of rings for each workday. The inner ring fills with the day's hours and closes when you reach your hours goal. The outer ring, there when you have a billable goal, fills with the billable part of those hours. Days still to come are an empty dotted outline, and hovering a day shows its hours and billable share. Under the rings you'll see your billable share for the period against your goal. * **What counts as billable.** You choose: time with a tag (a tag named **Billable** unless you pick others), time on projects or sections you pick, or time on projects where your rate is above zero on the day. Turn a goal off with its switch. Goals are yours alone: nobody else sees them, and the team view leaves them out. Track doesn't know about leave, so a day off counts as a missed workday. You can also ask the assistant "did I hit my goal this week?". ## Roles in Track [#roles-in-track] * **Owners, and people with Track Admin,** see everyone's time entries in reports and across the company. * **Everyone else** sees only their own, for example with the Track Member role. The reports filter for "team member" is locked to themselves. This applies in the home view too — you only see your own entries on `/track`. To see what others are tracking, use [Reports](/track/reports). ## Where the data goes [#where-the-data-goes] Time entries belong to your company. They're available to: * The Track app's home view + reports * The Invoices app's [Import from Track](/invoices/sending-invoices) flow, which converts time entries to invoice line items at your project rates * The [Public API](/api/) at `api.looped.sh/v1/track/time` ## Next steps [#next-steps] * [Set up projects](/track/projects) to group your entries * [Connect Google Calendar](/track/integrations/google-calendar) or [Microsoft Calendar](/track/integrations/microsoft-calendar) for one-click imports * Once you have a few weeks of data, explore [Reports](/track/reports) # Projects (/track/projects) Projects are how Track turns a stream of time entries into something useful — billable hours per client, hours per deliverable, who's worked on what. Open the Projects page at [app.looped.sh/track/projects](https://app.looped.sh/track/projects). ## Anatomy of a project [#anatomy-of-a-project] | Field | Notes | | ------------ | ------------------------------------------------------------------------------------------------ | | **Title** | What it's called. Required. | | **Code** | Optional short identifier (e.g. `ACME-2026`). Unique per company. Useful for reports / invoices. | | **Status** | One of: `PENDING`, `ACTIVE`, `COMPLETED`, `ARCHIVED` | | **Sections** | Sub-groupings within the project (e.g. *"Discovery"*, *"Implementation"*) | | **Members** | Who has access, plus their **rate** for billing | ## Statuses, in practice [#statuses-in-practice] * **ACTIVE** — appears in the project picker on the time-logger. Default. * **PENDING** — useful for projects you're scoping but haven't kicked off yet. * **COMPLETED** — a soft "finished" state. * **ARCHIVED** — hidden from the project picker so you can't accidentally log time against it. Historical entries still show up in reports. Filter the projects list by status using the dropdown at the top. ## Creating a project [#creating-a-project] 1. Open *Projects* in the Track navigation. 2. Click *Add Project*. 3. Enter a title and (optionally) a code. 4. Pick a status — usually `ACTIVE`. 5. Save. The project is immediately available in the time-logger. ## Members and rates [#members-and-rates] Each project has its own member list. Owners, and people with Full access to Track, see every project. **To give anyone else access to a project, add them to it.** Open the project's detail page → *Members* tab. | Field per member | What it does | | ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Role** | `MEMBER` / `MANAGER` / `OWNER` *of the project*. (Separate from their access to Track; see [Roles & permissions](/manage/roles).) | | **Rate** | Billing rate (per hour), dated (see [Rate history](#rate-history)). Used by the dashboard, reports and the [Import from Track](/invoices/sending-invoices) flow when this user's time entries become invoice line items | | **Cost** | Internal cost (per hour) for profitability reporting, dated the same way | ## Rate history [#rate-history] Rates change over the life of a project, and you don't want last year's hours revalued every time someone gets a raise. So each member has a rate history: a list of rates, each with the date it starts from. Every time entry is valued at the rate in force on the entry's own date, and that goes for the dashboard's revenue, reports, CSV exports and the Invoices import alike. To give someone a new rate, open the project, pick *Edit rates* from the member's menu and fill in *New rate from*. It defaults to today, which means everything they've already logged keeps its old rate and only time from today on uses the new one. A report or an invoice that spans the change shows each part at its own rate, and the Invoices import puts each rate on its own line. You can also plug in historical rates. Set *New rate from* to a date in the past, or edit or remove a period in the history list. These changes do revalue time that's already logged, so before saving, Track tells you how many entries move and what their value goes from and to, and asks you to confirm. Cost works the same way, so margins follow the cost history too. A few details worth knowing: * The first rate in the list also covers any time before its date, so an entry can't end up without a rate. * A rate that starts after today shows as *Scheduled* and takes over on its date. * You can't remove someone's only rate. Change it instead. * Invoices you've already issued keep their own amounts. Changing a rate never touches them. The assistant can do the same through `update_project_member_rate` (with an optional `effectiveFrom` date), `list_project_member_rates`, `set_project_member_rate_period` and `delete_project_member_rate_period`. For a past date it previews the repricing and checks with you before saving. ## Sections [#sections] Sections are sub-folders within a project. They're optional — most companies ignore them. They're useful if a project is long-running and you want to break it down (Discovery / Build / Maintenance). Open the project detail page → *Sections* tab → *Add section*. Time entries can be assigned to a section in the same edit modal where you assign them to a project. ## Archiving vs. deleting [#archiving-vs-deleting] * **Archive** = hide from pickers, keep historical entries. Use this 99% of the time. * **Delete** = remove the project record entirely. Looped will refuse to delete a project that has time entries — you have to clear or reassign them first. ## Reporting on projects [#reporting-on-projects] [Reports](/track/reports) can filter by project. The CSV export includes the project title and code per row. If you give projects clear codes, downstream finance/admin tools can join on them. # Reports (/track/reports) Reports turn raw time entries into something you can hand to a client, finance team, or auditor. Two pages live under reports: * **[/track/reports](https://app.looped.sh/track/reports)** — the simple report view. Pick filters, see results, export. * **[/track/reports/builder](https://app.looped.sh/track/reports/builder)** — the report *builder*. Define a saved report you can re-run later or share with the company. ## Quick reports — `/track/reports` [#quick-reports--trackreports] Filters live on the left side; results update as you change them. | Filter | Notes | | --------------------------- | ------------------------------------------------------------------------------------------ | | **Date range** | Start + end. Defaults to the current week ending Friday. | | **Project** | Multi-select. Empty = all projects. | | **Team member** | Owners and people with Track Admin can pick anyone. Everyone else is locked to themselves. | | **Tags** | Multi-select on time-entry tags | | **Billable / Non-billable** | Filter by the billable flag | Results show: * Total hours * Breakdown by project (and by member if applicable) * Breakdown by date * The underlying entries There's no *Run* button — change a filter and the result re-renders. ### CSV export [#csv-export] Click *Export CSV* in the corner of the report. The file contains: ``` Date, Project, Task, Member, Duration (hours), Billable ``` The export honors the filters you've applied — the CSV only contains the rows currently on screen. ## Saved reports — `/track/reports/builder` [#saved-reports--trackreportsbuilder] Where the simple page is good for one-off slices, the builder lets you **save** a configuration to re-run later. Useful for: * Weekly client status reports (filter by client's project, by week) * Monthly billable-hours summaries * Per-member productivity reviews Workflow: 1. Open [Builder](https://app.looped.sh/track/reports/builder) → click *New Report*. 2. Pick a name and description. 3. Configure filters and grouping (same as quick reports, plus pivot options). 4. Save. The saved report appears in the reports list at `/track/reports`. Anyone in the company with permission can run it. ### Permissions on saved reports [#permissions-on-saved-reports] Each saved report has two access controls: * **Allowed roles** — which company roles can view it (default: all) * **Allowed users** — explicit user ids if you want to scope it tighter than role Use this when a report contains sensitive data (e.g. partner-only profitability) and you don't want everyone with Track access to see it. ## Roles & visibility [#roles--visibility] Someone who can only see their own time sees **their own** time entries in a quick report — even if they pick a different name in the team-member filter, the API enforces own-data only. Owners and people with Full access to Track see everything across the company. This applies to CSV exports too: someone who can only see their own time can only export their own data. ## What reports don't do (yet) [#what-reports-dont-do-yet] * Send a scheduled report via email — not built. * Show $ amounts (only hours). Profit/billing summaries live in [Invoices](/invoices/getting-started) once you've imported the time as line items. * Compare periods (this week vs last week). On the roadmap. If any of those would help, ping us on [Discord](https://discord.gg/euwUfRt3nt). # Tags (/track/tags) Tags are short labels you can attach to time entries to slice reports beyond just project and member. Common uses: * *"Billable"* / *"Non-billable"* (though Track has a native billable flag, some companies prefer a tag) * *"Internal"* / *"Client"* * A specific phase: *"Discovery"*, *"QA"*, *"Maintenance"* * A person or pair: *"Pair w/ Alex"* A time entry can have any number of tags. ## Managing the tag list [#managing-the-tag-list] Open *Settings* → *Tags* in the Track navigation. The tags page lists your company's tags. Add new ones, rename, delete. Tags are company-scoped — every member sees the same list. ## Tagging an entry [#tagging-an-entry] Open an entry's edit modal. The **Tags** field is a multi-select with autocomplete. Pick existing tags, or type a new one to create it on the fly. ## Filtering reports by tag [#filtering-reports-by-tag] [Reports](/track/reports) accept a tags filter — multi-select. Useful for billable-vs-internal slicing, phase-based summaries, etc. ## Naming conventions [#naming-conventions] Tags are most useful when they're consistent. A few tips: * **Lowercase** is easier to type and stays uniform. * **Avoid abbreviations** unless your team agrees on them. * **Don't double up with projects** — if you'd find yourself tagging every entry with the same value as the project, just use the project field. ## Cleaning up [#cleaning-up] When a tag stops being useful, delete it from *Settings* → *Tags*. Time entries that referenced it lose the tag, but the entries themselves are untouched. # Google Calendar (/track/integrations/google-calendar) The Google Calendar integration imports events from your **primary** Google Calendar into Track as time entries. Useful when your meetings are already booked and you don't want to re-type them. The connection is **per user** — each teammate connects their own Google account; nobody else on the company sees your events. ## Connecting [#connecting] 1. Open *Settings* → *Integrations* in the Track navigation. 2. Click *Connect* next to **Google Calendar**. 3. Sign in with your Google account. 4. Grant Track **read-only** access on the OAuth consent screen. 5. You'll be redirected back to Looped, with the integration showing as *Connected*. Track stores OAuth tokens server-side and refreshes them automatically. To revoke, click *Disconnect* on the same page (or revoke at [myaccount.google.com/permissions](https://myaccount.google.com/permissions)). ## Importing events [#importing-events] The time-logger gets an *Import from Calendar* button once you're connected: 1. Pick a date range. 2. Track lists events in that range that you haven't already imported. 3. Tick the events you want. Edit task name or assign a project before confirming. 4. Click *Import*. Each ticked event becomes a time entry: | Calendar event field | → Time entry field | | ---------------------- | ------------------ | | Title | Task name | | Start time | Date | | Duration (end − start) | Hours | | Calendar | (not used) | | Attendees | (not used) | ## What's not imported [#whats-not-imported] * **All-day events** — no length to convert into a duration * **Declined invites** — events you didn't accept don't show up * **Events on calendars other than your primary** — only the primary calendar is read ## Deduplication [#deduplication] Track records `(connection, providerEventId)` for every imported event. Re-running the import doesn't duplicate entries you already pulled in. If you delete an imported time entry, the dedup record is removed too — so you can re-import that event later if you change your mind. ## Permissions [#permissions] Track requests **read-only** scope on your calendar (`calendar.readonly`). It cannot create, modify, or delete events. If you change your mind, disconnect from *Settings* → *Integrations* in Looped, or revoke from [myaccount.google.com/permissions](https://myaccount.google.com/permissions). ## Troubleshooting [#troubleshooting] * **"Authorization expired"** — the OAuth refresh token rotated. Disconnect and reconnect. * **No events show up** — confirm the date range is right and that you're using the same Google account that you connected. * **Stale events after I deleted them in Google** — Track caches the event list briefly. Close and reopen the import dialog to refresh. * **Sign-in fails for an enterprise tenant** — your IT team may have blocked third-party app access by policy. They'll need to permit Looped on the admin console. # Microsoft / Outlook Calendar (/track/integrations/microsoft-calendar) The Microsoft Calendar integration imports events from your **primary** Outlook calendar into Track as time entries. Works for personal Microsoft accounts and Microsoft 365 (work / school) accounts alike, subject to your tenant's policy. Like the [Google Calendar integration](/track/integrations/google-calendar), this is **per user** — each teammate connects their own account. ## Connecting [#connecting] 1. Open *Settings* → *Integrations* in Track. 2. Click *Connect* next to **Microsoft Calendar**. 3. Sign in at the Microsoft prompt. 4. Grant Track **read-only** access. 5. You'll land back in Looped with the integration showing *Connected*. Track stores tokens server-side and refreshes them automatically. To revoke, click *Disconnect* in Looped, or revoke from [account.microsoft.com](https://account.microsoft.com) → *Privacy* → *App access*. ## Importing events [#importing-events] The time-logger gets an *Import from Calendar* button once you're connected: 1. Pick a date range. 2. Track lists events in that range you haven't already imported. 3. Tick the events you want. Edit task name or assign a project before confirming. 4. *Import*. Each ticked event becomes a time entry — title becomes task name, length becomes the hours, the start time becomes the date. ## What's not imported [#whats-not-imported] * **All-day events** — no length to convert * **Declined invites** — only events you've accepted appear * **Calendars other than your primary** — only the primary calendar is read today ## Deduplication [#deduplication] Track records `(connection, providerEventId)` for every imported event, so re-running the import on the same range doesn't double up. Deleting an imported time entry also removes the dedup record, so you can re-import the event later if you change your mind. ## Permissions [#permissions] Track requests **read-only** scope (`Calendars.Read`). It cannot create, edit, or delete events. ## Enterprise tenants [#enterprise-tenants] If your organization uses Microsoft 365 with strict tenant policies, your IT admin may need to permit Looped explicitly before the OAuth consent screen will work. Symptoms: * The consent screen says *"Need admin approval"*. * Sign-in completes but no events ever load. In both cases, ask your admin to grant tenant-wide delegated consent for the Looped app from the [Microsoft Entra admin center](https://entra.microsoft.com). If your admin uses a direct admin-consent URL, it should use your tenant ID or `organizations`, not `common`: ```text https://login.microsoftonline.com/{tenant}/v2.0/adminconsent?client_id={client_id}&scope=https://graph.microsoft.com/User.Read%20https://graph.microsoft.com/Calendars.Read%20offline_access&redirect_uri={redirect_uri} ``` After consent is granted, each teammate still connects their own Microsoft account in Track, but non-admin users should not be asked to request permission again for the granted scopes. ## Troubleshooting [#troubleshooting] * **"Authorization expired"** — refresh token rotated. Disconnect and reconnect. * **No events show up** — confirm date range is right; confirm the connected account actually has events (it might be the wrong Microsoft account if you have multiple). * **Sign-in error mentioning the tenant** — see *Enterprise tenants* above. # Todoist integration (/track/integrations/todoist) If you live in Todoist, the Todoist integration imports your **completed** tasks as time entries — so the things you've finished show up in your Track week without re-typing them. Like the calendar integrations ([Google](/track/integrations/google-calendar), [Microsoft](/track/integrations/microsoft-calendar)), this is **per user** — each teammate connects their own Todoist account. ## Connecting [#connecting] 1. Open *Settings* → *Integrations* in Track. 2. Click *Connect* next to **Todoist**. 3. Sign in with Todoist and grant Track read access. Track stores the OAuth tokens server-side and refreshes them automatically. Disconnect from the same page when you no longer need the integration. ## Importing tasks [#importing-tasks] Once connected, the time-logger gets an *Import from Todoist* option: 1. Pick a date range. 2. Track lists Todoist tasks **completed** in that range. 3. Tick the ones you want. Optionally adjust the duration (Todoist has no native duration concept, so each task imports with a sensible default that you should review). 4. *Import*. Each ticked task becomes a time entry — task name from Todoist, date from the completion timestamp, duration from your input. ## Limitations [#limitations] * Only **completed** tasks are pulled. Open tasks aren't. * **No project mapping** — Todoist projects don't auto-map to Track projects. Assign the project manually after import (or before, on the import screen). * **No duration carry-over** — Todoist tasks don't store hours. You enter duration at import time. * **No two-way sync** — closing a task in Todoist doesn't change anything in Track and vice versa. The integration is one-way: Todoist → Track. ## Permissions [#permissions] Track only requests **read** scope. It cannot create, modify, or delete tasks in your Todoist account. To revoke: disconnect in Looped, or remove the app from your [Todoist integrations page](https://app.todoist.com/app/settings/integrations). # Getting started with Invoices (/invoices/getting-started) Looped Invoices is the platform's invoicing app. Open it at [app.looped.sh/invoices](https://app.looped.sh/invoices). The sidebar has two groups. **Invoices** holds the **Dashboard**, **Quotes**, **Sales orders**, **Invoices**, **Credit notes** and **Clients**. **Reporting** holds **Statements**, **Client sales** and **Sales by sales code**. Every page is also in the ⌘K palette. Each document (quote, sales order, invoice or credit note) opens on its own page, where you fill it in, preview it, and send it or take the next step. ## Before your first invoice [#before-your-first-invoice] You need a few things in place before sending an invoice: | What | Where to set it | | ------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------- | | **Company name + address** | *Settings* → *General* ([Company settings](/team-settings)) | | **Logo** | *Settings* → *General* | | **Bank details** *(optional, for EFT)* | *Settings* → *General* | | **Currency** | Set on company creation; locks after first paid invoice | | **At least one client with an email** | [Clients](/invoices/clients) | | **Payment integration** *(optional)* | *Settings* → *Integrations* → [Stripe](/invoices/integrations/stripe), [Yoco](/invoices/integrations/yoco), [PayFast](/invoices/integrations/payfast) | You fill the company details in on the **Company** page in Manage. The setup checklist on the dashboard links to each step you still have to do. ## What an invoice looks like [#what-an-invoice-looks-like] Every invoice has: * A **number**, generated from your [numbering settings](#settings). One sequence per company. * An **issue date** and optional **due date**. * A **client** (the "billed to") — picked from your client list. * A **list of lines**: item code (if it's an Inventory item), description, quantity, unit price, discount and VAT. * Optional **bank details** at the bottom for EFT payment. * A **status**, such as **Pending**, **Partially paid** or **Paid**. See [Statuses](/invoices/sending-invoices#statuses). ## The flow [#the-flow] 1. **[Set up clients](/invoices/clients)** — at minimum a name + email per client. 2. **[Quote](/invoices/quotes-and-sales-orders)** if you like, and turn an accepted quote into a sales order or an invoice. 3. **[Create an invoice](/invoices/sending-invoices)**: pick the client, add lines, preview. 4. **Send it**. Looped emails the client a PDF and a link to a [Pay page](/pay/) where they can pay online. 5. **Get paid**. Once they pay, online or recorded by you, the invoice is marked **Paid**. ## Importing time from Track [#importing-time-from-track] If your company logs hours in [Looped Track](/track/), choose **Import from Track** in the invoice list's ⋮ menu. Pick a date range and Track's time entries become invoice lines, with the per-project rate already applied. See [Creating & sending invoices](/invoices/sending-invoices#importing-time-from-track). ## Settings [#settings] **Settings → General** in Invoices holds: | Setting | What it does | | --------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Invoice numbering** | Prefix, separator, padding, year and the next number to use | | **Terms** | Printed at the foot of every quote, sales order and invoice | | **Client categories** | Trade, Retail and so on, and the [price level](/inventory/prices) each buys at | | **Sales codes** | Your sales reps, with a code and name. Each prints on its quotes and invoices, and [Sales by sales code](/invoices/reporting#sales-by-sales-code) adds up what was sold under it | | **Inventory items** | Whether people can type a line in, or have to pick it from Looped Inventory | ## Where to go next [#where-to-go-next] * **[Creating an account](/invoices/creating-an-account)** — if you haven't yet * **[Completing your profile](/invoices/completing-your-profile)** — fill in business details * **[Clients](/invoices/clients)** — manage who you bill * **[Creating & sending invoices](/invoices/sending-invoices)** — the day-to-day flow * **[Quotes & sales orders](/invoices/quotes-and-sales-orders)** * **[Credit notes](/invoices/credit-notes)** * **[Statements & reports](/invoices/reporting)** * **[Stripe integration](/invoices/integrations/stripe)** — accept card payments online # Clients (/invoices/clients) Clients are the "billed to" side of every invoice. Before you can send an invoice, you need at least one client with an email address. The clients page is at [app.looped.sh/invoices/clients](https://app.looped.sh/invoices/clients). ## Anatomy of a client [#anatomy-of-a-client] | Field | Required? | Used for | | ------------------------------------ | --------- | --------------------------------------------------------------------------------------------------------------------------- | | **Name** | Yes | "Billed to" on documents. Unique per company (case-insensitive) | | **Client code** | optional | Your account code for the client, such as `ABELIA`. Shows in the client list, pickers, statements, reports and on documents | | **Email** | Yes | Sending invoices and quotes by email | | **Phone** | optional | Shown on documents for contact | | **VAT number** | optional | Shown on documents where it's required | | **Address** | Yes | "Billed to" address: line 1 and postal code at least. The client list says **No address** when there isn't one | | **Delivery address** | optional | Ship-to address, if different | | **Category** and **Own price level** | optional | Which [price level](/inventory/prices) the client buys at | | **Sales code** | optional | The sales rep the client's quotes and invoices are credited to | A client can be a person (*Jane Doe*) or a business (*Acme Corp*). Looped doesn't distinguish. ## Creating a client [#creating-a-client] Two ways: ### From the clients page [#from-the-clients-page] 1. Open *Clients* in the Invoices nav. 2. Click *Add Client*. 3. Fill the form and *Save*. ### From a quote or invoice [#from-a-quote-or-invoice] When the client doesn't exist yet, choose **New client** in the client picker on a quote or invoice. A modal opens to create them without leaving the document. The client is saved, becomes the invoice's "billed to", and shows up on the clients page going forward. ## Editing a client [#editing-a-client] Open the client row → *Edit* (or just click on the client). Change anything except the name (which stays unique per company). Changes affect **future** invoices only. An invoice already sent retains the client snapshot it had at send time. ## Deleting a client [#deleting-a-client] If a client has no invoices, *Delete* removes the row. If they have invoices, deletion is blocked — you'll see a warning. Either: * Keep the client around (it doesn't cost anything), or * Delete or void the invoices first, then delete the client This safeguard prevents orphaning invoices that reference a client that no longer exists. ## Searching [#searching] The clients page has a search bar that matches the client code, name, email, phone and VAT number. Every word you type has to match, in any order. Choose 25, 50 or 100 clients a page. Pickers on documents show each client as "CODE · Name" and search by either. ## The client page [#the-client-page] Click a client to open their page: their **Balance** (or **In credit**), their documents, and the prices they pay. ### Prices for a client [#prices-for-a-client] If your company uses [Inventory](/inventory/), **Prices for this client** lists the items the client has their own price for, and **All items** shows every item at the price they pay now and where it comes from: **Their list** (their own price level), **Category list** (their category's level) or **Item price** (the item's own selling price). Search every item by name or code, then type a price under **Their price** for the exceptions. To give the client a printable list of their prices, start a [client price list](/inventory/prices#client-price-lists) from their page. ## Why does each client need an email? [#why-does-each-client-need-an-email] The send action needs somewhere to send the email to. The send button on an invoice is **disabled** if its client has no email — the tooltip explains why. If you only ever invoice in person and don't need email sends, that's fine — leave the email blank, save the invoice, and download the PDF manually. But the bulk of the value comes from email + the [Pay portal](/pay/) which requires the email. ## Importing clients [#importing-clients] Bulk import isn't built yet. Until then: * Add them one at a time, or * Use the [Public API](/api/) (`POST /v1/invoices/clients`) to script imports from your CRM # Creating an Account (/invoices/creating-an-account) ## Overview [#overview] Creating a Looped Invoices account is quick and easy. You can sign up using your existing social media accounts, which means no need to remember another password! ## Sign Up Process [#sign-up-process] ### Step 1: Visit Looped Invoices [#step-1-visit-looped-invoices] To create an account, visit [app.looped.sh](https://app.looped.sh) and click on the **Get Started** button in the top right corner of the page. Screenshot of the login page ### Step 2: Choose Your Sign-In Method [#step-2-choose-your-sign-in-method] Looped Invoices uses secure social authentication to make account creation simple and secure. You can create an account using one of the following providers: * **Google** - Sign in with your Google account * **Apple** - Sign in with your Apple ID * **GitHub** - Sign in with your GitHub account Simply click on your preferred provider and follow the authentication prompts. ### Step 3: Grant Permissions [#step-3-grant-permissions] When you sign in with a social provider, you'll be asked to grant certain permissions: * **Basic profile information** - Your name and email address * **Profile picture** (optional) - Used for your account avatar These permissions are necessary to create and personalize your account. Looped Invoices never posts on your behalf or accesses any information beyond what's needed for authentication. ### Step 4: Account Creation Complete [#step-4-account-creation-complete] Once you've successfully authenticated, your Looped Invoices account will be created automatically. You'll be redirected to the dashboard where you can start setting up your profile. ## Security Features [#security-features] ### Social Authentication Benefits [#social-authentication-benefits] Using social authentication provides several security advantages: * **No password management** - One less password to remember or reset * **Two-factor authentication** - Leverage your provider's 2FA security * **Trusted providers** - Google, Apple, and GitHub have industry-leading security * **Easy account recovery** - Use your social provider's recovery options ### Data Privacy [#data-privacy] We take your privacy seriously: * We only access the minimum information needed (name, email, profile picture) * Your social account credentials are never stored on our servers * Authentication is handled securely through OAuth 2.0 * You can disconnect your social provider at any time ## What's Included [#whats-included] Your free Looped Invoices account includes: * Up to 5 invoices per month * Basic invoice templates * Payment link generation * Email delivery * Payment tracking * Mobile-responsive payment pages Want more? Check out our [subscription plans](/purchasing-subscriptions) for additional features like: * Unlimited invoices * Custom branding * Payment gateway integrations * Advanced reporting * Team collaboration ## Account Setup Checklist [#account-setup-checklist] After creating your account, complete these steps to start invoicing: * [ ] [Add your business address](/invoices/completing-your-profile#adding-your-address) * [ ] [Configure your banking details](/invoices/completing-your-profile#adding-banking-details) * [ ] Upload your logo (optional) * [ ] [Join or create a company](/creating-a-team) (optional) * [ ] [Connect a payment gateway](/invoices/integrations/payfast) (optional) * [ ] Create your first invoice! ## Multiple Accounts [#multiple-accounts] If you need to manage multiple businesses or separate personal and business invoicing: 1. Create a company for each business in [Looped Manage](/creating-a-team) 2. Switch between companies using the company selector in the top navigation 3. Each company can have its own branding, settings, and subscription ## Troubleshooting [#troubleshooting] ### Can't Sign In with Social Provider [#cant-sign-in-with-social-provider] If you're having trouble signing in: * **Check your pop-up blocker** - Some browsers block the authentication window * **Try a different browser** - Clear cache and cookies if issues persist * **Verify your provider account** - Ensure your social account is active and verified * **Check your email** - You may need to verify your email with your provider ### Account Already Exists [#account-already-exists] If you see a message that an account already exists: * You may have previously signed up with a different provider * Try signing in with Google, Apple, or GitHub to see which account you used * Contact support if you need to merge accounts ### Privacy Concerns [#privacy-concerns] If you prefer not to use social authentication: * Contact our support team at [support@looped.sh](mailto:support@looped.sh) * We can discuss alternative authentication options for your use case ## Next Steps [#next-steps] Now that you have an account, let's get you ready to create invoices: 1. [Complete your profile →](/invoices/completing-your-profile) 2. Learn how to [create your first invoice](#) (coming soon) 3. Explore [payment gateway integrations](/invoices/integrations/payfast) ## Need Help? [#need-help] If you encounter any issues during account creation: * 📧 Email: [support@looped.sh](mailto:support@looped.sh) * 💬 Discord: [Join our community](https://discord.gg/TwCrkdCnPS) * 🎫 Support Portal: [support.looped.sh](https://support.looped.sh) # Completing Your Profile (/invoices/completing-your-profile) ## Overview [#overview] To get the best out of Looped Invoices, you'll need to complete your profile. This ensures that you create the best possible impression with your clients and generate invoices that are fully [SARS compliant](https://www.sars.gov.za/businesses-and-employers/government/tax-invoices/). A complete profile includes: * Your business or personal address * Banking details (for EFT payments) * Business information (optional) * Logo and branding (optional) ## Adding Your Address [#adding-your-address] ### Why is an address required? [#why-is-an-address-required] Your address is required to create valid, SARS-compliant invoices. According to South African tax law, all tax invoices must include the supplier's physical address. ### How to add your address [#how-to-add-your-address] 1. [Log into your Looped Invoices account](https://app.looped.sh/login) 2. Navigate to [Settings](https://app.looped.sh/settings) 3. Scroll to the **Address** section 4. Fill in the following fields: * **Street Address** - Your physical street address * **Suburb/City** - Suburb or city name * **Province/State** - Select your province * **Postal Code** - Your area's postal code * **Country** - Select South Africa (or your country) 5. Click **Update** to save your changes The address you enter here will be used as the default address for all your invoices. You can override this on individual invoices if needed. ### Address Tips [#address-tips] * **Use your registered business address** if you're VAT registered * **Ensure accuracy** - Your clients may need this for their records * **Keep it professional** - This appears on all your invoices * **Update when you move** - Remember to update your address if you relocate ## Adding Banking Details [#adding-banking-details] ### Why add banking details? [#why-add-banking-details] Banking details are optional but useful if you want to: * Generate PDF invoices for manual EFT payments * Provide clients with payment alternatives * Accept bank transfers alongside online payments Your banking details will appear on your invoices, making it easy for clients to pay you via electronic funds transfer (EFT). ### How to add banking details [#how-to-add-banking-details] 1. [Log into your account](https://app.looped.sh/login) 2. Navigate to the [Banking Details section of Settings](https://app.looped.sh/settings#banking-details) 3. Enter the following information: * **Bank Name** - Your bank (e.g., FNB, Standard Bank, ABSA) * **Account Holder Name** - Name on the account * **Account Number** - Your account number * **Branch Code** - Your branch code (if required) * **Account Type** - Cheque, Savings, or Business * **Reference Format** (optional) - How clients should reference payments 4. Click **Update** to save Your banking details will be visible on your invoices. Never share sensitive information like your online banking passwords or PINs. ### Banking Details Best Practices [#banking-details-best-practices] * **Double-check your account number** - Mistakes can delay payments * **Use a business account** if you're registered as a business * **Specify a reference format** - e.g., "Invoice number" or "Your name + Invoice #" * **Keep information current** - Update details if you change banks ## Setting Up Payment Gateways [#setting-up-payment-gateways] For automated online payments, you can connect payment gateway accounts instead of (or in addition to) adding banking details. Looped Invoices supports integration with popular South African payment gateways: ### Supported Payment Gateways [#supported-payment-gateways] * **PayFast** - [Setup guide](/invoices/integrations/payfast) * **Yoco** - [Setup guide](/invoices/integrations/yoco) * **More coming soon** - We're constantly adding new integrations ### Benefits of Payment Gateway Integration [#benefits-of-payment-gateway-integration] * **Instant payment notifications** - Know immediately # Creating & sending invoices (/invoices/sending-invoices) The invoice list is at [app.looped.sh/invoices](https://app.looped.sh/invoices). It shows invoices only; credit notes have [their own page](/invoices/credit-notes). ## The invoice list [#the-invoice-list] * Search by client, number or status. Every word you type has to match, in any order. * Filter by status, client and issue date. The filters sit beside search on one line. * The receivables aging card shows what's still owed, by age. Click a bucket to show just those invoices. * Choose 25, 50 or 100 a page. **New invoice** opens the invoice page. The ⋮ menu beside it holds **Import from Track**. ## Creating an invoice [#creating-an-invoice] An invoice is a page of its own, not a pop-up. Fill in: * **Client**: search your [clients](/invoices/clients) by code or name, or create one in a modal without leaving the page. * **Issue date**, **Due date**, **Currency**, **Your reference**, **Delivery date** and **Ship to** as needed. * **Lines**: see below. * A **Note** for the client, and an internal **Description** that isn't shown to them. The number comes from your numbering settings; you can edit it to override. **Preview** shows the PDF as the client will see it. ### Lines [#lines] Each line has a **Description**, **Qty**, **Unit price**, **Disc %** and its VAT treatment (standard, zero-rated or exempt). VAT starts at your company's rate, and a zero-rated client makes their lines zero-rated. Drag a line to reorder it. If your company uses [Inventory](/inventory/), the item picker on a line searches the whole catalogue by code or name as you type. Every word has to match, in any order, so "boot 13" finds "Addo Boot stc Size 13". Arrow keys move through up to 50 results, each showing the item's code, price, name and stock. A picked item puts its code before the description on the line and on the PDF, and its price follows the client's [price level](/invoices/clients#prices-for-a-client). If there isn't enough available stock, a warning icon says how many are available, on hand and reserved. Your company can require that lines are picked from Inventory; see [Settings](/invoices/getting-started#settings). ### Capture from document [#capture-from-document] To bring in an invoice you issued elsewhere, click **Capture from document** beside **Preview** and pick a PDF, image or text file, or drop the file anywhere on the page. The form fills in from it for you to check. ### Importing time from Track [#importing-time-from-track] If your company uses [Looped Track](/track/), choose **Import from Track** in the invoice list's ⋮ menu. Pick a date range and tick the time entries you want. Each becomes a line, with hours as the quantity and the rate set on [project membership](/track/projects#members-and-rates). ## Sending and the next step [#sending-and-the-next-step] The invoice page shows one next step beside **Preview**, and the rest in the ⋮ menu: | When the invoice is | The next step is | | ----------------------- | --------------------------------------------------- | | New or a draft | **Send** (or **Issue without sending** in the menu) | | Sent and not fully paid | **Record payment** | **Send** opens a modal to confirm the recipient and message. Looped emails the PDF and, if you have a [payment integration](/invoices/integrations/stripe), a link to the [Pay page](/pay/) where the client can pay online. Sending again shows **Resend**. **Issue without sending** issues the invoice to the books without emailing it. The menu also has **Download PDF**, **Copy payment link**, **Open payment page**, **History**, **Issue credit note**, **Refund** and **Write off**. ## Recording a payment [#recording-a-payment] For money received outside Looped, such as an EFT, click **Record payment**, then enter the **Date received**, the **Method** and a note. A payment recorded by mistake can be reversed from the invoice's payments. The methods are EFT, Cash, **Card (POS)** for a card machine that isn't Yoco, Stripe, Yoco, PayFast and Other. **Paid into** is the bank account the money landed in, and Financials posts the payment to it. It starts as the account set for the method under **Settings › General › Where payments land**, else the invoice's own bank account, and can be changed for any one payment. ## Cash count [#cash-count] For cash payments, set **Cash** to land in **Cash on hand** under **Settings › General › Where payments land**. Payments recorded as Cash then go into Cash on hand, an account in Financials, instead of a bank account. At the end of the day, open **Cash count**: 1. It lists what was recorded as paid that day by method, and the cash you should have. 2. Enter what you counted and **Confirm count**. Over or short posts the difference to **Cash over/short** in Financials. A day is counted once. 3. When you take the cash to the bank, pick the account and choose **Bank the cash**. That moves it from Cash on hand to the bank. ## Statuses [#statuses] | Status | Means | | ------------------ | ------------------------------------------------------ | | **Draft** | Saved to finish later: no payment link, not owed yet | | **Pending** | Issued and not yet paid | | **Partially paid** | Some of it has been paid | | **Paid** | Fully paid | | **Overdue** | Past its due date and unpaid | | **Credited** | Fully credited by credit notes | | **Written off** | Written off as not collectable | | **Expired** | The payment link has expired; the invoice still exists | ## Deleting an invoice [#deleting-an-invoice] Delete an invoice from the ⋮ menu on its row or its page. You're asked to confirm, and from the list you type the invoice number first. Deletion is permanent, and the number isn't reused. # Quotes & sales orders (/invoices/quotes-and-sales-orders) Quotes and sales orders sit before invoices in the **Invoices** sidebar. They use the same document page as an invoice: client, lines, dates and totals, with one next step beside **Preview** and everything else in the ⋮ menu. ## Quotes [#quotes] **Quotes** lists the estimates you can turn into invoices once accepted. Across the top, stats show your **Open quotes**, what was **Won this month** and what's **Expiring this week**. Search by client, number or status. Click **New quote**, fill it in like an invoice, with a **Valid until** date, and send it. A quote keeps a revision number and a history of every change. Once it has been sent, the next step is **Accept** (or **Reject** in the ⋮ menu). An accepted quote becomes either: * a **sales order**, with **Make sales order**, when the client will take it over time, or * an **invoice**, with **Convert to invoice**, when it's billed in one go. A converted quote links to the sales order or invoice it became. To see two revisions next to each other, open the quote's **History** and choose **Compare**. Pick any two revisions, or a revision and the quote as it stands: header fields and lines show side by side, with changed values in bold and lines marked **Added**, **Removed** or **Changed**. ## Sales orders [#sales-orders] **Sales orders** is what clients have ordered and are waiting on, with what's still to invoice. Make one from an accepted quote, or capture one directly with **New sales order**. Sales orders have their own numbering. Stats across the top show **Open orders**, **Overdue deliveries** and what was **Invoiced this month** from sales orders. Search by number, client or reference, filter by client, status and order date, sort by any column, and choose 25, 50 or 100 a page. A sales order shows each line's **Ordered**, **Invoiced** and **Back order** quantities. Enter what's being delivered under **Invoice now** and click **Create invoice**: invoice some or all of what's left, in as many goes as you need. Each invoice is issued like any other and links back to its sales order; the order shows its quote and its invoices. The sales order prints as the pro forma invoice, with your document terms at the foot. **Cancel order** takes whatever hasn't been invoiced off order; invoices already raised from it stay as they are. If your company uses [Inventory](/inventory/), an open sales order reserves its items, so they show as reserved rather than available until they're invoiced. # Recurring invoices (/invoices/recurring-invoices) A recurring invoice raises an invoice for a client on a schedule: a monthly retainer, a quarterly service fee, an annual licence. Find them under **Recurring invoices** in the Invoices sidebar. ## Setting one up [#setting-one-up] Choose **New recurring invoice** and fill in: | Field | What it does | | -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Client** | Who each invoice is for | | **How often** | Monthly, quarterly, annually, or every N weeks | | **Day of the month** | The day monthly, quarterly and annual invoices are dated. A shorter month uses its last day, so the 31st becomes the 28th in February. Blank uses the start date's day | | **Start date** | The first possible invoice date | | **Ends** | Never, on a date, or after a number of invoices | | **Each invoice** | **Save a draft for review** (the default) or **Issue and email to the client** | | **Payment terms** | Days after the issue date the invoice is due | | **VAT %** | Blank uses the company's rate on each invoice's date | | **Lines** | The description, quantity and unit price on each invoice | The heading shows the next three invoice dates as you edit. ## What happens on the day [#what-happens-on-the-day] Each invoice takes the next number in your normal invoice sequence. * **Draft for review**: the invoice waits in your invoice list as a draft. Check it, then issue or send it as usual. * **Issue and email**: the invoice is issued, posted to Financials like any other invoice and emailed to the client with its PDF. If it can't be sent (the client has no email address, the date is in a closed period, or the month's free sends are used up), it is saved as a draft instead and the list shows why. If invoices were missed (say the schedule started in the past), the next run raises them one per date, oldest first. ## Pause, resume and generate now [#pause-resume-and-generate-now] From the ⋮ menu on a row: * **Pause** stops new invoices. **Resume** picks the next date from today; invoices for the dates it was paused aren't raised. * **Generate now** raises an invoice dated today, after you confirm. If an invoice was due today or earlier, this one takes its place. * **Invoices raised** lists every invoice the schedule has made. Deleting a recurring invoice stops it; the invoices it raised stay. ## From the API and your assistant [#from-the-api-and-your-assistant] The public API has `/v1/invoices/recurring`, and the assistant can list, set up, pause and resume recurring invoices for you. It saves drafts unless you ask for invoices to be sent automatically. # Credit notes (/invoices/credit-notes) A credit note reduces what a client owes on an invoice, for a return, a mistake or a discount after the fact. ## Issuing one [#issuing-one] Credit notes are issued from the invoice they credit. Open the invoice and choose **Issue credit note** in the ⋮ menu. Under **What to credit**, choose the **Full invoice**, **Some lines** (with a **Credit qty** per line), **The rest** or **An amount**, and give a **Reason**, which is printed on the credit note. **Credit and refund** also records the money you paid back. Items tracked in [Inventory](/inventory/) that a client returns come back onto the shelf. Credit that isn't used against the invoice stays with the client as open credit until it's applied or refunded. ## The credit notes page [#the-credit-notes-page] **Credit notes** has its own page in the sidebar; the invoice list shows invoices only. Stats across the top show what was **Credited this month** and the **Open credit**: what's left with clients, not yet applied or refunded. Search by client or number. # Statements & reports (/invoices/reporting) The **Reporting** group in the Invoices sidebar holds **Statements**, **Client sales** and **Sales by sales code**. ## Statements [#statements] A statement is everything on a client's account over a period: invoices, payments, credit notes, refunds and write-offs, with a running balance. Pick the client and the period. The statement opens on the **Opening balance**, and each line folds its type into the **Description**, beside the **Reference**, **Debit**, **Credit** and **Balance**. Preview, print or download it as a PDF. Lines from archived years load when the period reaches them. ## Monthly client sales [#monthly-client-sales] **Client sales** shows each client's net sales, excluding VAT, month by month. Choose **3 months**, **6 months** or **12 months**. The month before the period is added as a comparative, so 12 months shows 13 columns; the **Average** covers the period only. * Search by client code or name, and filter by client category and sales code. * **Hide clients with no sales** is a toggle. * **Choose columns** adds or removes the client's **Code**, **Sales code**, **Price list**, **Outstanding**, **On order** and **Average**. * Sort by any column. The client and info columns stay put while the months scroll. * Click a client to open their page. Totals run across the whole list, not just what's on screen. Export it with **Preview**, **Export CSV** or **Export PDF**; the PDF prints the code, sales code and average rather than every client detail, so all the months fit. ## Sales by sales code [#sales-by-sales-code] Quotes sent and won, and what was invoiced less credit notes, excluding VAT, per sales code (your sales reps). Tick **By client** to split each sales code by client. Pick the period, and export it with **Preview**, **Export CSV** or **Export PDF**. ### Commission by sales code [#commission-by-sales-code] Turn on **Commission by sales code** under **Settings** › **General** and a **Commission** button appears on Sales by sales code. It shows, per sales code and for the period, what was invoiced less credit notes on lines that earn commission and on lines that don't, excluding VAT. A line earns commission when its Inventory item has **Earns commission** ticked (the default); typed lines do too. Looped doesn't work out the commission itself. Sales codes are set up in Invoices settings; see [Settings](/invoices/getting-started#settings). ## Dispatch [#dispatch] **Dispatch** lists the open sales orders to deliver in a date range, grouped by where they're going. Nobody keeps a list of areas: each order's address is looked up and grouped by town and suburb, with neighbouring suburbs next to each other, starting from your company's own address. A new client's suburb shows up by itself. The address an order goes to is the order's own delivery address, else the client's delivery address, else the client's billing address. An address that can't be found shows under **Address not found**, with a link to fix it on the client. Tick the groups that make up a run and choose **Export PDF** to print the driver's sheet, or **Export CSV**. With nothing ticked, the sheet has every group. ## Audit trail [#audit-trail] **Audit trail** in the sidebar lists who created, edited, sent, converted or changed the status of quotes, invoices, credit notes and sales orders, and who added, edited or deleted clients, newest first. An edit shows each change in words, such as `Email: old → new` for a client. Filter by what it was (invoice, quote, credit note, sales order or client), by person and by date, or search by number or client name. **Download CSV** downloads every matching event. Quotes and sales orders only show for people who can see quotes, and clients for people who can see clients. The assistant reads the same trail with `list_invoices_history`. # PayFast (South Africa) (/invoices/integrations/payfast) PayFast is a South African payment provider. Connecting it to Looped Invoices lets your clients pay invoices via card, EFT, or any of PayFast's other supported methods (Mukuro, Zapper, etc.). The integration is **per company** — connect a different PayFast merchant account per company if you want. ## Prerequisites [#prerequisites] * A PayFast merchant account. Sign up at [registration.payfast.io](https://registration.payfast.io/) if you don't have one. * An Owner, or someone with Manage Full, in the Looped company. ## Get your PayFast credentials [#get-your-payfast-credentials] 1. Log in to PayFast at [login.payfast.io](https://login.payfast.io). Pick **Aggregation** at sign-in. 2. In the sidebar, click *Settings* → *Developer Settings*. 3. Take note of three values from the top of the page: * **Merchant ID** * **Merchant Key** * **Security Passphrase** (just below) We strongly recommend leaving **"require signature"** turned on in PayFast — this enables the passphrase-based signature verification that Looped uses to confirm payment authenticity. Don't disable it. ## Connect PayFast in Looped [#connect-payfast-in-looped] 1. Open *Settings* → *Integrations* in Looped Invoices. 2. Click *Connect* next to **PayFast**. 3. Paste the three values from above. 4. Click *Save*. The badge flips to *Connected* and PayFast becomes a payment option on every invoice you send going forward. ## What clients see [#what-clients-see] When you send an invoice, the email and the [Pay portal](/pay/) show a *"Pay with PayFast"* button. Clicking it submits a form to PayFast's hosted checkout where your client picks their payment method (card, EFT, etc.) and pays. After payment: 1. PayFast posts a notification to Looped at `app.looped.sh/invoices/api/payfast/notify/`. 2. Looped verifies: * The HMAC **signature** using your passphrase * The originating IP is a known PayFast IP * A **server confirmation** call back to PayFast (defense-in-depth) 3. If all three checks pass, the invoice flips to `PAID`. 4. Funds settle into your PayFast wallet on PayFast's standard schedule. If the payment fails, the invoice stays `PENDING` and the client can retry from the same Pay link. ## Fees [#fees] Looped doesn't take a cut. Standard PayFast transaction fees apply — see [payfast.io/fees](https://www.payfast.io/fees/) for current rates. ## Disconnecting [#disconnecting] Open *Settings* → *Integrations* in Looped → click *Disconnect* next to PayFast. Past invoices already paid stay marked paid. New invoices stop offering PayFast as a method. ## Multiple payment integrations [#multiple-payment-integrations] You can have PayFast alongside Stripe, Yoco — the client picks one on the Pay portal. Many SA companies enable both PayFast and Yoco for redundancy + payment-method coverage. ## Testing the integration [#testing-the-integration] PayFast has a **sandbox** for testing without real money. To use it, set up a separate sandbox account at [sandbox.payfast.io](https://sandbox.payfast.io) and connect those credentials to a *test* Looped company. You can then send test invoices and pay them with PayFast's test cards. For full production confidence, send yourself a small live invoice and pay it for real — easy to refund afterwards from the PayFast dashboard. ## Troubleshooting [#troubleshooting] * **Payment succeeds but Looped doesn't flip to PAID** — most often signature verification failure. Check that the **Security Passphrase** in Looped exactly matches what's set in PayFast (no leading/trailing spaces, copy carefully). If it does, drop us a line at [support@looped.sh](mailto:support@looped.sh) — there may be an IP-allowlist issue. * **Pay button isn't showing** — the invoice might have been sent before you connected the integration. Re-send the invoice; the new Pay link will include PayFast. * **Sandbox payments aren't going through** — make sure the credentials in Looped are the sandbox credentials, not the production ones. The two are separate. # Stripe (accept card payments) (/invoices/integrations/stripe) Connect a Stripe account to Looped Invoices and the **Pay** link in your invoice emails accepts credit / debit cards. Funds settle into your Stripe account on Stripe's normal payout schedule — Looped never touches the money. This Stripe account is **separate** from the one Looped uses for your subscription billing. They can be the same account or different ones; they aren't linked. ## Prerequisites [#prerequisites] * A Stripe account with payouts enabled. Sign up at [stripe.com](https://stripe.com) if you don't have one. * An Owner, or someone with Manage Full, in the Looped company. ## Connecting [#connecting] 1. Open *Settings* → *Integrations* in Looped Invoices. 2. Click *Connect* next to **Stripe**. 3. Stripe opens. Sign in and grant Looped access. 4. Stripe redirects back to Looped. The integration's badge now shows *Connected*. Looped stores your Stripe **account id**. Your Stripe **secret key** stays on Stripe; we never see it. The first time a client clicks *Pay now*, Looped registers one webhook endpoint at `app.looped.sh/invoices/api/stripe/notify/` so Stripe can notify Looped when payments succeed. It stays in place for every later payment. ## What clients see [#what-clients-see] When you send an invoice, the email and the [Pay portal](/pay/) include a *"Pay now"* button. Clicking it opens **Stripe Checkout** — Stripe's hosted payment page — where the client enters their card details. After they pay: 1. Stripe sends a webhook to Looped. 2. Looped marks the invoice as `PAID` with the timestamp Stripe confirmed the charge. 3. Funds settle into your Stripe account. If the payment fails, the invoice stays `PENDING` and the client can retry from the same Pay link. ## Fees [#fees] Looped doesn't take a cut of the payment. Standard Stripe processing fees apply — see [stripe.com/pricing](https://stripe.com/pricing) for your region. ## Disconnecting [#disconnecting] Open *Settings* → *Integrations* → click *Disconnect* next to Stripe. Past invoices that were already paid through Stripe stay marked paid. Disconnection only stops new invoices from offering Stripe as a payment method. If you reconnect a *different* Stripe account, future invoices route to the new account; past invoices are unchanged. ## Why it's per-company [#why-its-per-company] The Stripe connection is scoped to a Looped company — different companies in your account can have different Stripe accounts (or one of them can be Stripe-less). This makes sense if you run multiple businesses through Looped. ## Multiple payment integrations at once [#multiple-payment-integrations-at-once] You can have Stripe **and** Yoco **and** PayFast connected at the same time. The Pay portal shows whichever ones you've connected; the client picks one when paying. ## Alternatives [#alternatives] If Stripe isn't available in your region, see: * **[Yoco](/invoices/integrations/yoco)** — South Africa * **[PayFast](/invoices/integrations/payfast)** — South Africa ## Webhook details (for troubleshooting) [#webhook-details-for-troubleshooting] Looped registers one webhook endpoint per company, for the `payment_intent.succeeded` event, which records the payment and marks the invoice paid. Don't delete it: payments made while it's missing aren't recorded. If it's gone, Looped registers a new one the next time a client clicks *Pay now*, and removes any older Looped endpoints for your company. If you ever see Stripe payments succeed but Looped not flip the invoice to `PAID`, check your Stripe dashboard's *Developers* → *Webhooks* section — the endpoint should show recent events being delivered. If something looks off, drop us a line at [support@looped.sh](mailto:support@looped.sh). # Yoco (South Africa) (/invoices/integrations/yoco) Yoco is a South African payment processor. Connecting it to Looped Invoices lets clients pay you with a credit / debit card from any invoice you send. This integration is **per company** — different companies in your account can have different Yoco accounts, or only some companies can use Yoco at all. ## Prerequisites [#prerequisites] * A Yoco merchant account. Sign up at [hello.yoco.com/signup](https://hello.yoco.com/signup) if you don't have one. * An Owner, or someone with Manage Full, in the Looped company. ## Get your Yoco API keys [#get-your-yoco-api-keys] 1. Log in to your Yoco account at [portal.yoco.co.za](https://portal.yoco.co.za). 2. In the left sidebar, click *Sell Online* → *Payment Gateway*. 3. Scroll to **Your keys**. 4. Take note of: * **LIVE PUBLIC KEY** (starts with `pk_live_…`) * **LIVE SECRET KEY** (starts with `sk_live_…`) You'll paste these into Looped in the next step. Treat the **secret key** the same way you'd treat a password — never paste it into a public chat, email, or shared spreadsheet. Looped stores it encrypted. ## Connect Yoco in Looped [#connect-yoco-in-looped] 1. Open *Settings* → *Integrations* in Looped Invoices. 2. Click *Connect* next to **Yoco**. 3. Paste the **public** and **secret** keys you copied from Yoco. 4. Click *Save*. The badge flips to *Connected* and Yoco appears as a payment option on every invoice you send going forward. ## What clients see [#what-clients-see] When you send an invoice, the email and the [Pay portal](/pay/) include a *"Pay with Yoco"* button. Clicking it opens Yoco's hosted checkout where the client enters card details. After they pay: 1. Yoco posts a webhook to Looped at `app.looped.sh/invoices/api/yoco/notify/`. Looped registers this webhook the first time a client clicks *Pay with Yoco* and keeps it for every later payment. 2. Looped marks the invoice as `PAID`. 3. Funds settle into your Yoco account on Yoco's standard schedule. If the payment fails, the invoice stays `PENDING` and the client can retry from the same Pay link. ## Fees [#fees] Looped doesn't take a cut. Standard Yoco transaction fees apply — see [yoco.com/za/fees](https://www.yoco.com/za/fees/) for current rates. ## Disconnecting [#disconnecting] Open *Settings* → *Integrations* in Looped → click *Disconnect* next to Yoco. Past invoices that were already paid stay marked paid. Disconnection only stops new invoices from offering Yoco. If you reconnect with **different** keys later, future invoices use the new account; past invoices are unchanged. ## Multiple payment integrations [#multiple-payment-integrations] You can have Yoco connected alongside Stripe, PayFast — clients pick which to use on the Pay portal. Some companies enable just one; others offer multiple to give clients flexibility. ## Testing the integration [#testing-the-integration] The simplest end-to-end test: 1. Send yourself a small-value invoice (e.g. R10) to a personal email. 2. Open the Pay link. 3. Pay with a real card — small enough that you don't mind eating the fee. 4. Confirm the invoice flips to `PAID` in Looped within a few seconds of payment confirmation. You can refund yourself from the [Yoco portal](https://portal.yoco.co.za) afterwards. ## Troubleshooting [#troubleshooting] * **"Yoco not configured"** — check the connection in Looped settings; the keys may have been entered wrong or never saved. * **Payment succeeds in Yoco but Looped doesn't flip to PAID** — Yoco's webhook didn't reach Looped. Check Yoco's portal for webhook delivery logs and verify the webhook URL is `app.looped.sh/invoices/api/yoco/notify/`. Reach out to [support@looped.sh](mailto:support@looped.sh) if it's not. * **Pay button is missing on the Pay link** — the integration might not be enabled, or the invoice was sent before you connected. Re-send the invoice and the new Pay link will include Yoco. # Looped Financials (/financials) Looped Financials keeps your company's books. Open it at [app.looped.sh/financials](https://app.looped.sh/financials). It's a double-entry ledger: every amount is posted as a journal entry with equal debits and credits, and every report is worked out live from those entries. Most of the posting comes from your bank statements. You upload a statement, Financials proposes an account for each line, and you approve what's right. ## What's in it [#whats-in-it] The sidebar is split into four groups. | Group | Pages | What they're for | | -------------- | -------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Financials** | **Dashboard**, **Uploads**, **General journal**, **Chart of accounts**, **Expense receipts**, **Assets**, **Loans**, **Payroll** | Day-to-day bookkeeping: bank statements, manual entries, expense receipts, fixed assets and depreciation, loans, and the payroll journal | | **Suppliers** | **Suppliers**, **Supplier invoices**, **Supplier returns** | Who you buy from, what you owe them (a supplier debit note is a supplier invoice) and what they credit you for returns | | **Reporting** | **Reports**, **VAT**, **Annual statements**, **Tax**, **Deadlines**, **Notes** | The statements, VAT returns, the year-end pack and its notes, and filing dates | | **Settings** | **Company**, **Financial years**, **Reminders**, **Exchange rates**, **History**, **Audit log** | Company details and reporting framework, years and lock dates, which deadlines you track and how early you're reminded, exchange rates, archived years, and who did what | The financial year picker in the header decides which year the dashboard, reports and journal show. Every page is also in the ⌘K palette. Invoices you issue in [Looped Invoices](/invoices/getting-started) post to the books on their own, and so do the payments recorded against them. When the same receipt shows up on your bank statement, Financials matches it to that payment instead of booking it twice. Pay runs from Looped Payroll post the same way; see [Payroll in the books](/financials/payroll). Stock bought, sold and counted in [Looped Inventory](/inventory/) posts to the books at average cost. The default control accounts are called **Debtors control** (what clients owe you) and **Creditors control** (what you owe suppliers). Companies that still had the old default names, Accounts Receivable and Accounts Payable, were renamed; a name you chose yourself stays. ## Accounting and Financials [#accounting-and-financials] Looped's books come as two modules in this one app. **Accounting** is the books: uploads, the general journal, expense receipts, assets, loans, payroll, suppliers, supplier invoices and VAT. **Financials** is the statements: the dashboard, the chart of accounts, the reports built from balances such as the trial balance and income statement, annual statements, notes, tax and deadlines. Accounting includes Financials. It's one app, called Financials in the app switcher: the sidebar shows the pages your company's modules include. With Financials only, the bookkeeping pages are hidden; with Accounting, every page shows. Existing subscriptions include both. ## Expense receipts and petty cash [#expense-receipts-and-petty-cash] **Expense receipts** are till slips for spend with no supplier. When you confirm one, pick how it was paid: * **Business account or card**: it waits for the payment on the bank statement, then posts through that line with the slip attached. * **Personal card or cash**: it posts now, against what the company owes the director (the Director's Loan, or another account you pick). * **Petty cash**: it posts now, out of the **Petty Cash** account. The Petty Cash account's ledger is the petty cash book, and its balance is the float. To top it up, categorise the bank line for the cash you drew to Petty Cash. Each country's chart has the account already (Petty Cash, Kassa or Pokladna), and Looped keeps it, so it can't be deleted or archived. ## Countries and reporting frameworks [#countries-and-reporting-frameworks] The country you choose during [setup](/financials/getting-set-up) decides the ledger currency, the default chart of accounts, VAT rates, and which frameworks you can prepare your statements under. | Country | Currency | Frameworks | Default | | -------------------- | -------- | ----------------------------------- | ------------------- | | South Africa | ZAR | IFRS for SMEs, Full IFRS | IFRS for SMEs | | United Arab Emirates | AED | IFRS for SMEs, Full IFRS | IFRS for SMEs | | United Kingdom | GBP | FRS 102, FRS 105 (micro), Full IFRS | FRS 102 | | Ireland | EUR | FRS 102, FRS 105 (micro), Full IFRS | FRS 102 | | United States | USD | US GAAP, Management accounts | US GAAP | | Austria | EUR | Management accounts, Full IFRS | Management accounts | | Czech Republic | CZK | Management accounts, Full IFRS | Management accounts | In Austria and the Czech Republic, statutory accounts follow local law and are prepared by your accountant. Looped keeps the books and produces management accounts, or IFRS statements for reporting to a group. Some areas only exist for South African companies, and the sidebar leaves them out everywhere else: * **VAT**: VAT201 returns worked out from the ledger. * **Tax**: the SARS income tax computation and IRP6 provisional tax. * **Payroll**: the payroll journal and matching salary payments. * **Deadlines** and **Reminders**: SARS and CIPC filing dates. Who is reminded is chosen in [Manage](/manage/notifications). Companies in other countries still record VAT on their transactions where the country has VAT, and agree the VAT balances to the returns they file themselves. ## Who can use it [#who-can-use-it] Nobody gets into Financials just by being in the company. Owners can do everything; everyone else needs a Financials role, which you give on the **People** page in Manage. See [Roles & permissions](/manage/roles). | Role | What they can do in Financials | | -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- | | **Financials Admin** | Everything, including settings and setup, closing a year, VAT returns, paying supplier invoices and the payroll page | | **Bookkeeper** | Reviews bank lines, captures supplier invoices, posts journals and attaches documents. No settings, year end, VAT filing or paying supplier invoices | | **Auditor** | Sees the books and reports and changes nothing | Bookkeepers and auditors are free on every plan, so you can invite your accountant without paying for a seat. ## Free, trial and Financials [#free-trial-and-financials] Every new company gets a 30-day Accounting trial with everything included, and no card is needed. While it runs, a line at the top of each page shows how many days are left. After the trial, unless you subscribe to Financials, the app is read-only. Everything you entered stays visible, but you can't upload statements, post journals, enter supplier invoices or run payroll. A banner at the top of each page says so and links to **Start Financials**. Subscribing lifts the limit straight away. See [Purchasing a subscription](/purchasing-subscriptions) for prices. ## Where to start [#where-to-start] 1. [Get set up](/financials/getting-set-up): company, financial year, bank account and opening balances. 2. [Upload and review bank statements](/financials/bank-statements). 3. [Read the reports and file VAT](/financials/statements-and-vat). 4. [Close the year and compile the annual financial statements](/financials/year-end). # Getting set up (/financials/getting-set-up) Every app has **Set up** at the top of the Settings section in its sidebar, and the first time you open an app with nothing in it you land there. In Financials it opens **Set up Financials**, where you set up your books from whatever documents you have. You need to be an Owner or have Financials Admin to save the results. ## Set up from your documents [#set-up-from-your-documents] On **Set up Financials**, drop in whatever documents you have. We read them for your legal name, registration number, VAT number, year end and bank account, and show you what we found in **Check what we found**. Change anything that's wrong, untick what you don't want saved and click **Confirm**. Bank statements and last year's annual financial statements then go to the assistant in the chat: it imports the statements and captures your opening balances from the financial statements, and you review the lines before anything posts. You can also click **Start with the assistant** at the top of the page and have it do the whole setup in the chat. The page suggests documents for your country. None of them is required, and anything else that shows your company's details, like an invoice or a letterhead, helps too. | South Africa | Austria | Other countries | | ---------------------------------------------------------- | ---------------------------------------------------------------------- | ----------------------------------------------------- | | CIPC registration certificate (CoR 14.3) | Firmenbuchauszug, or a Gewerbeschein or GISA extract for a sole trader | Certificate of incorporation or business registration | | SARS income tax registration | Steuernummer and UID-Nummer notice from the Finanzamt | Tax and VAT registration | | VAT registration notice (VAT103), if registered | | | | SARS employer registration (EMP101e), if you employ people | | | | Bank statements for the current financial year | Kontoauszüge for the current financial year | Bank statements for the current financial year | | Last year's annual financial statements | Letzter Jahresabschluss | Last year's annual financial statements | The bank account's details come from the header of your bank statements, so you don't need a separate bank letter. ### Moving from another system [#moving-from-another-system] If your books are in Xero, Sage, Pastel, BMD, QuickBooks or a spreadsheet, click **Moving from another system?** and the assistant sends the Looped team a migration request. We bring your opening balances, open debtors and creditors and fixed assets across for you, free of charge for now. You can carry on with your company details and chart of accounts while you wait; leave the bank statements until the migration is done. ## Doing it yourself [#doing-it-yourself] You can set everything up by hand instead: * **Company details**: the country, name, registration and VAT details are on the **Company** page in Manage. The country sets the ledger currency, the chart of accounts, VAT rates and the reporting frameworks you can choose from. * **Financial year**: under **Settings → Financial years**, click **New financial year**. * **Bank account**: open **Chart of accounts**, click **New account** and tick **Bank account**, then upload statements as described in [Bank statements](/financials/bank-statements). ## Opening balances after setup [#opening-balances-after-setup] You can also capture opening balances later: open **Journal** and click **Opening balances**, or choose **Capture opening balances** in the ⌘K palette. Anyone who can post journals, Bookkeepers included, can use it. It lists every asset, liability and equity account with a box for its balance, and an **As at** date. The **Balancing entry** figure shows what will go to equity if the sides don't agree, and which account it goes to. Posting takes you to the balance sheet so you can check it. Dates before your first financial year can always be posted to, so opening balances never land in a locked period. ## The chart of accounts [#the-chart-of-accounts] Your chart of accounts is created from your country's defaults the first time you open **Chart of accounts**. Each account has a code, a name and a type (Asset, Liability, Equity, Income or Expense). Add your own with **New account**. You can archive accounts you no longer use, and **Show archived** brings them back into view. If your chart is missing some of the defaults, for example because it was created before they were added, **Add missing defaults** adds them without changing anything you already have. ## Reporting framework and preparer [#reporting-framework-and-preparer] Under **Settings → Company**, the **Financial statements** card holds: * **Statements prepared by**: printed on the cover of the annual financial statements. * **Reporting framework**: sets the statements' titles, which statements are included and the notes a new financial year starts with. The choices depend on your country; see [the list on the overview](/financials#countries-and-reporting-frameworks). Notes you've already edited are never replaced when you change framework, and a finalised pack keeps the framework it was prepared under. # Bank statements (/financials/bank-statements) Most of your books come from bank statements. You upload one, Financials proposes an account for every line, and nothing is posted until you approve it. Bookkeepers can do all of this; see [Roles & permissions](/manage/roles). ## Uploading a statement [#uploading-a-statement] 1. Open **Uploads**. 2. Under **Upload bank statement (CSV or OFX)**, choose the **Bank account** the statement belongs to. 3. Click **Choose file** and pick the CSV or OFX file your bank exported. QFX and QBO files work too. 4. Check the preview before anything is imported (see below). 5. Click **Upload**. Financials reads the file in your browser first and shows you what it found. For a CSV it maps the columns to **Date**, **Description**, **Amount** (or separate **Debit** and **Credit** columns) and **Balance**. Change any that are wrong, and set **Money out shown as** to **Negative numbers** or **Positive numbers** to match your bank. If the mapping isn't obvious, **Suggest mapping with AI** sends the column names and the first 10 rows to the assistant, which fills the mapping in for you to check. Nothing is imported until you click **Upload**. Some banks put a few lines above the transactions, like the account number and the statement period. Financials skips those until it finds the column headings or the first dated row. Commas and semicolons both work as separators, and dates like `02-Aug-21` or `02-Aug-2021` are read as day, month and year. Type a name into **Save mapping as…** to reuse the mapping. The next file with the same columns picks it up on its own. ### Checking the balances [#checking-the-balances] When the file has a balance column, the preview shows the **Opening** and **Closing** balances, **Money in** and **Money out**, and a **Statement check** that opening plus the transactions reaches the closing balance. **Books before statement** compares the statement's opening balance with what your books say the account held the day before. If it differs, a statement in between is probably missing or something was posted twice. ### Duplicates [#duplicates] Uploading the same lines twice is safe. Lines that were already imported are skipped, and the message after the upload says how many. If you upload the exact same file again, Financials warns you first and you can click **Upload anyway**. The list on **Uploads** shows each statement's period and balances, and a **Continuity** badge that compares it with the previous statement for the same account: | Badge | Meaning | | -------------- | ------------------------------------------------------------------------------ | | **follows on** | Its opening balance matches the previous statement's closing balance | | **gap** | The balances don't meet, usually because a statement in between is missing | | **overlaps** | It covers dates the previous one already did; the duplicate lines were skipped | ## Categorising [#categorising] After the upload you land on the statement's review screen. Click **Categorise *n* lines with AI** to propose an account for every line. It runs in the background, so you can leave the page and come back; the button shows its progress. Each proposal comes from one of three places, checked in this order: 1. **Rule**: one of your [categorisation rules](#categorisation-rules) matched the line. 2. **Memory**: you categorised a line like it before. Its tooltip says "Learned from your earlier choice". 3. **AI**: the assistant chose an account from your chart, with a confidence score. When nothing in your chart fits, it suggests a new account you can create in one click. Before any of that, money-in lines that match a payment already recorded in Looped Invoices are settled against that payment, so the receipt isn't booked twice. ## Reviewing and approving [#reviewing-and-approving] Approving a line posts it to the ledger. Until then it's only a proposal. * **Approve one line**: check the account, then press ⌘+⏎ (Ctrl+Enter), or use the row's menu. * **Approve the confident ones**: **Approve all ≥ 90%** approves every proposal the AI is at least 90% sure of. * **Approve a batch**: tick lines (or press Space on a row), pick an account in **Search an account to assign…** and click **Assign** if you want to change it, then click **Approve *n***. * **Exclude** a line that shouldn't be in the books, such as a transfer you post another way: press ⌘+⌫, or use **Exclude *n*** for a batch. * **Split across accounts…** posts one bank line to several accounts, for example a card payment that covers two kinds of expense. The review screen works from the keyboard. Click a row or press ↓ to start, use ↑ and ↓ to move, and just type to change the row's account to the best match. Enter opens the full account search. The filter above the table narrows the list to **To review**, **To review · under 90%**, **Matched a rule**, **AI suggested**, **Not categorised**, **Posted** or **Excluded**, and the search box finds lines by description, amount, date or account. ### Changing a posted line [#changing-a-posted-line] Pick a different account on a posted line and choose **Reclassify to the picked account**. Financials reverses the original entry and posts a new one, so the history stays intact. **Reverse and exclude** takes a posted line back out of the books. If a line falls in a VAT201 period that's already finalised, Financials won't approve it to an account that carries VAT until you reopen that return on the **VAT** page. ## Matches Financials offers [#matches-financials-offers] Some bank lines pay for something that's already in the books. For these the review screen offers a match instead of a new expense, and **Confirm** (or **Settle**) posts the payment against it. | Shown as | What it does | | ------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Matches** *invoice* | Money in for an invoice payment already recorded from Looped Invoices. No second entry is posted. | | **Payout of** *n* **sales** | A payout from Yoco, Stripe, PayFast or a card machine's acquirer that pays several payments at once. Confirming settles them all; for a card payout, the sales less what was paid out post to Bank charges as the acquirer's fee. | | **Pays supplier invoice** *supplier* | Pays an approved supplier invoice. Clears Creditors control; the expense was booked when the supplier invoice was approved. | | **Pays salaries (payroll)** | Pays the net pay owed on a payroll run. See [Payroll in the books](/financials/payroll). | | **EMP201 settlement** | South Africa only. Clears the month's PAYE, UIF and SDL. | A card payout is offered when its description names the acquirer (Yoco, iKhokha, a bank's merchant settlement and the like) and one run of whole days of card and Yoco sales in the week before it, less a fee of up to 4%, makes the amount, such as Friday to Sunday paid out on Monday. If two runs could fit, nothing is offered; categorise the line yourself. ## Categorisation rules [#categorisation-rules] Rules categorise the lines you see every month, like bank fees or a software subscription, without asking the AI. They're checked top to bottom on every categorisation run, and the first rule that matches a line wins. To create one: * From the review screen, open a line's menu and choose **Create rule from this line**. * Or open **Uploads → Categorisation rules** and click **New rule**. A rule has: | Field | Notes | | ------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- | | **Description contains** | Text to look for in the bank description, for example `UBER` | | **Direction** | **Either**, **Money out** or **Money in** | | **Amount from** / **Amount to** | Optional amount range | | **Account** | Where matching lines go | | **VAT** | The VAT treatment approving a matched line posts, or **Account default**. Lines dated before your VAT registration post without VAT either way | | **Supplier (optional)** | Makes matching lines payments to that supplier, so they can pay the supplier's open supplier invoices | | **Rule name** | Defaults to the description text | **Preview on this upload** (or **Preview on recent lines**) shows which lines the rule would catch before you save it. On the rules page you can move rules up and down to change their order, switch a rule off, test it against recent lines, or delete it. Deleting a rule doesn't change lines already posted. A new rule applies to future uploads. To run your rules over lines still open on a statement you're reviewing, click **Apply rules** on that statement. ## Deleting an upload [#deleting-an-upload] Open the statement, click the **⋯** menu and choose **Delete upload**. If any of its lines were posted, the button reads **Delete upload and entries** and removes those entries too. # Bank reconciliation (/financials/bank-reconciliation) The bank reconciliation compares the closing balance on your bank statement with the bank account's balance in the books at a date, and lists what explains the difference. Open it from **Reports → Bank reconciliation**. ## The statement [#the-statement] Pick the bank account (a ledger account marked as a bank account) and the statement date. * **Statement balance**: type the closing balance from the bank statement, or leave it blank to use the running balance of the last uploaded statement line on or before the date. * **Ledger balance**: the account's balance in the books at the date. * **Outstanding receipts**: money into the bank in the books that isn't on an uploaded statement line yet. * **Unpresented payments**: payments in the books that aren't on a statement line yet. * **Statement lines not in the books**: uploaded lines up to the date that haven't been approved into the ledger. Approve them under **Uploads**. An entry counts as on the statement once a statement line is approved against it, including lines matched to a client payment, a supplier invoice payment or a pay run. An entry and its reversal in the same period cancel out and aren't listed. The **difference** is the ledger balance less the statement balance adjusted for those items. It is zero when the account reconciles. ## Ticking items as cleared [#ticking-items-as-cleared] Some entries are on the bank statement but were never matched, such as an opening balance captured by journal. Tick them as cleared and they drop out of the outstanding items. Ticks on a finalised reconciliation carry forward to later dates. ## Saving and finalising [#saving-and-finalising] **Save draft** keeps the reconciliation for the account and date. **Finalise** (after you confirm) needs a zero difference; a finalised reconciliation can't be changed unless it's reopened. Saved reconciliations are listed under the statement; select one to open it. The PDF (Export PDF or Preview) is the reconciliation statement for the management pack or the annual financial statements file. # Suppliers and supplier invoices (/financials/suppliers) The **Suppliers** group in the sidebar holds **Suppliers**, **Supplier invoices** and **Supplier returns**. ## Suppliers [#suppliers] **Suppliers** lists who you buy from. A supplier's default account, VAT treatment and payment terms pre-fill its supplier invoices, and a [categorisation rule](/financials/bank-statements) can name a supplier so its bank payments settle the open supplier invoice. A supplier has a **Name**, a **Supplier code** (your account code for them, such as `ACTRAD`), **Email**, **VAT number**, **Default account**, **Default VAT** and **Terms (days)**. The code shows in the list, on the supplier's page, in pickers as "CODE · Name" and on their supplier invoices. * Search by code, name, email or VAT number. Every word you type has to match, in any order. * Filter by status (**Active**, **Archived**) and balance (**Owing**, **Nothing owed**). * Choose 25, 50 or 100 a page. Click a supplier to open their page. Edit, archive and remove are in the row's ⋮ menu. ### The supplier page [#the-supplier-page] A supplier's page has three tabs, each with search, filters and paging: | Tab | What it shows | | --------------------- | ----------------------------------------------------------------------------------------------------------------------- | | **Supplier invoices** | Every supplier invoice from them, with its status, due date and total | | **What you buy** | Items on approved supplier invoices from them: quantity, what you spent, the last unit cost and when you last bought it | | **Purchase orders** | Orders to them from [Looped Inventory](/inventory/purchase-orders) | ## Supplier invoices [#supplier-invoices] **Supplier invoices** are what you owe suppliers. Approving one books the expense and VAT input against **Creditors control**; the payment on the bank statement then clears it instead of being booked as an expense again. The list follows the financial year picked in the header, with **All years** for the rest. Search by supplier, number or reference, and filter by status: **Drafts**, **Awaiting payment**, **Paid** and **Void**. **Aged payables** shows approved supplier invoices that aren't paid yet, by how overdue they are. To capture one, click **Capture a supplier invoice** to type it in, or **Draft from document**: drop a PDF or image of the invoice and the assistant drafts it for you to check. A supplier debit note is captured as a supplier invoice. ### Stock on supplier invoices [#stock-on-supplier-invoices] If you use [Looped Inventory](/inventory/), a supplier invoice line can be an item. Approving it brings the stock in at that cost. **Record a purchase** in Inventory opens a new supplier invoice for an item. From a purchase order, **Create supplier invoice** opens one filled with what has arrived and isn't invoiced yet, at the order price. That stock is already on the shelf from its goods received note, so approving the supplier invoice only settles the price. See [Purchase orders](/inventory/purchase-orders#the-supplier-invoice). ## Supplier returns [#supplier-returns] **Supplier returns** are credits from suppliers for returns, discounts or overcharges. Applied to a supplier invoice, a return reduces what you owe on it; on its own it reverses the expense on one account. Stats show the **Total returned**, what's **Still to apply or refund**, and who you've **Most returned to**. Search by supplier or number, filter by status and date, and page through them. # Reports and VAT (/financials/statements-and-vat) Every report in Financials is worked out live from the ledger, so it's up to date the moment a line is approved or a journal is posted. Reports follow the financial year chosen in the header. Anyone with a Financials role can read them, Auditors included. ## Reports [#reports] Open **Reports**. **Display as** switches the list between **Cards** and **Table**. | Report | What it shows | | --------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Income statement** | Income, expenses and net profit for the year, with the prior year alongside when there is one | | **Balance sheet** | Assets, liabilities and equity at the year end. Profit not yet closed into retained earnings shows as **Current earnings**, so it balances before year end | | **Changes in equity** | Opening equity, profit for the year, contributions and distributions, and closing equity | | **Cash flow** | Operating, investing and financing movements, by the indirect method: profit adjusted for non-cash items and working capital | | **Trial balance** | Every account's debit and credit totals, as at a date you choose | | **Aged receivables** | What clients owe on Looped invoices, by how long it's been outstanding | | **Management report** | The monthly pack for a month you pick, on screen and as one PDF | Accounts with a zero balance are left off the statements but stay on the trial balance. Every report has the same export group: **Preview** shows the PDF as on screen, to print or download, and **Export CSV** and **Export PDF** download it. ### Trial balance as at a date [#trial-balance-as-at-a-date] The trial balance shows the year's income and expenses, with earlier open years' profit in retained earnings. Choose **As at** to see it on any date in the year: it starts at today for the current year and the year end for a past one. When entries later in the year aren't included, a hint says how many. Sub-accounts are listed under their account; **Collapse sub-accounts** shows one line per account instead. The cash flow statement places each account under operating, investing or financing on its own. If an account lands in the wrong place, open it in **Chart of accounts** and set its **Cash-flow section** to **Operating**, **Investing** or **Financing**. Interest received, interest paid and income tax paid have their own lines after cash generated from operations, worked out from the accounts on the finance and tax statement lines. A loan in financing shows the money raised and the repayments as separate lines, taken from the entries that moved it through a bank account. Interest charged to the loan without cash stays out of financing. When you revalue a foreign bank account, the exchange difference isn't a cash flow, so it's shown between the net movement in cash and the closing balance. Below the statement, **Liabilities from financing activities** takes each loan from its opening to its closing balance. The **Dashboard** shows the same figures in short: income, expenses and net profit for the year, whether the ledger balances, and where the money went. ### Management report [#management-report] The management report is the pack an accountant sends each month. Pick the **Month** and it shows, one section after another: * **Executive summary**: for the month, the month before and the last financial year, cash received and spent, the closing bank balance, income, direct costs, gross profit, other income, expenses and profit, debtors, creditors and net assets, the number and average value of invoices issued, margins, return on investment, debtor and creditor days and the current and term ratios. * **Profit and loss**: each income and expense account for the month, the month before and the last financial year. * **Balance sheet**: at the month end beside the end of the month before and the last year end, with this year's profit as **Current year earnings**. * **Aged receivables summary** and **Aged payables summary** at the month end. * **Trial balance** for the year to date, and the **Trial balance for the month**: income and expenses for the month only, every other account at the month end. Where an account sits (bank, current or non-current, cost of sales, other income) comes from its statement line in **Chart of accounts**. Direct costs are the cost of sales accounts, so creditor days show a dash without them. **Preview** opens the PDF and **Export PDF** downloads it, each section starting on a new page. Looped has no budgets, so the report compares months rather than budget against actual. ## Exports for your accountant [#exports-for-your-accountant] Under **Exports** on the **Reports** page: | Export | What it holds | | ------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- | | **Trial balance** | Every account's net balance as at the year end | | **General ledger** | Every posted line by account, with a running balance | | **Journal** | Every entry in date order, one row per line | | **Accountant pack** | One workbook: company details, the chart of accounts with where each account is presented, the trial balance and the year's journal with VAT | The first three come as CSV or XLSX. The accountant pack is an XLSX and needs a financial year picked in the header. Amounts are in the ledger currency with two decimals. ## VAT [#vat] When your company is VAT registered, amounts on bank lines, supplier invoices and journals are captured including VAT, and Financials splits out the VAT for you. Output VAT and input VAT post to their own control accounts. If you're not registered, everything posts without VAT. Set **Registered for VAT from** on the **Company** page to the date on your registration notice. Bank lines and journals dated before it post without VAT, because you couldn't charge or claim VAT then. If you pick a VAT treatment for one of those lines yourself, Financials uses the one you picked. Without a date, every line takes its account's VAT. ### VAT201 returns (South Africa) [#vat201-returns-south-africa] Open **VAT**. The **VAT registration** card shows whether you're registered, your VAT number (change it on the **Company** page) and the **Filing cycle**: * **Monthly (Category C)** * **Bi-monthly ending even months (Category A)** * **Bi-monthly ending odd months (Category B)** Below it is one row per VAT period in the selected financial year, showing what you'll pay or get back. Open a period to see the return: | Field | | | ----- | ----------------------------------- | | 1 | Standard-rated supplies (incl. VAT) | | 2 | Zero-rated supplies | | 3 | Exempt supplies | | 4 | Output VAT | | 14 | Input VAT — capital goods | | 15 | Input VAT — other goods & services | | 19 | Net VAT payable / (refundable) | Input VAT counts as capital goods when the line it belongs to was posted to an asset account. The return is worked out from the VAT lines on your transactions. If a manual journal posts straight to a VAT control account, the return shows it as a control-account variance rather than folding it in, so you can find and fix it. ### Finalising a return [#finalising-a-return] When the figures are right, click **Finalise VAT201**. This saves the return as it stands and posts the settlement: the period's output and input VAT move to **VAT Control (SARS)** as the amount payable or the refund due. You file the return with SARS yourself. Once a period is finalised, the review screen won't approve bank lines in it to accounts that carry VAT. If something posted since changes the figures, the return shows how much the live figure has moved. If you haven't submitted it yet, click **Reopen**, which reverses the settlement entry, and finalise it again. Finalising and reopening returns needs Financials Admin or an Owner. ### Outside South Africa [#outside-south-africa] For countries with VAT, Financials still records VAT on each transaction and keeps the input and output control accounts, but doesn't prepare the return. Agree the balances on the trial balance to the returns you file. The United States has no VAT, so nothing is captured. ## Tax and deadlines (South Africa) [#tax-and-deadlines-south-africa] * **Tax** holds the income tax computation for the year: add-backs, allowances such as wear and tear from the fixed asset register, and your own **Manual adjustments**. Tick **Small business corporation (SBC) rates** if they apply. **IRP6 provisional tax** estimates the first and second provisional payments. * **Deadlines** lists the SARS and CIPC filings worked out from your company's dates, as **Overdue**, **Coming up** or **Filed**. Overdue and upcoming ones also appear on the dashboard. * **Settings → Reminders** chooses which deadlines you track and how early the first reminder goes out: a morning reminder ahead of each deadline, and again on the day if it hasn't been filed. Who is reminded, including an outside accountant's email address, is chosen in Manage under [Settings → Notifications](/manage/notifications). # Budgets (/financials/budgets) A budget is set per financial year for each income and expense account. Open it from **Reports → Budget**; it follows the financial year picked in the header. Amounts are in each account's normal sign, so income and expenses are both entered as positive amounts. ## Annual figure and phasing [#annual-figure-and-phasing] In the **Year** view (the default), each account has an annual budget and a phasing that turns it into months: * **Even**: twelve equal months. * **Like last year**: the months follow last year's actuals for the account, so a seasonal account keeps its shape. An account with no history is spread evenly. * **By quarter**: four quarter shares (percentages or amounts), each spread evenly over its months. * **Custom**: whatever the months say. Editing any month makes an account custom. Cents left over from a split go on the last month of the period: the year, or each quarter. **Phase** sets the phasing for every account or a section (all operating expenses, say) in one go. Custom accounts keep their months. ## Quarters and months [#quarters-and-months] **Quarters** and **Months** show the same budget in more detail. Typing a quarter phases the account by quarter; typing a month makes it custom. Typing into **Total** spreads the year evenly. In **Months** you can paste a block of cells copied from Excel or Google Sheets into any cell. It fills right and down from that cell. Amounts like `1 250.50`, `1,250.50` and `(300)` are read; cells that aren't amounts are left out. **Copy last year's actuals** sets every account's annual budget to last year's actuals, raised or lowered by a percentage, phased like last year. Changes wait in a bar at the top until you **Save** or **Discard** them. ## Tracking [#tracking] The **Tracking** tab shows each account's and section's actual as a percentage of budget for a month, a quarter, the year to date or the full year. Income under budget and spending over budget show in the warning colour. Bars stop at 150%, and the number shows the rest. On the full year a dark line marks where you'd be by now if the year ran evenly. The dashboard shows an **Against budget** card when the year has a budget: net profit for the year to date against budget, with income and expenses as bars. ## Budget on the income statement [#budget-on-the-income-statement] **Income statement → Budget** lays out the statement with its sections, subtotals and gross and net profit, with **Actual**, **Budget**, **Variance** and **Variance %** columns for a month, a quarter, the year to date or the full year. Variance is favourable when positive: more income or less spending than budgeted. **Budgeted** shows the statement from the budget alone, the year as the plan sees it. Both export to CSV, PDF and Excel. The **management report** gets a "Budget and actual" section after the profit and loss when the year has a budget, for the report's month, the quarter to date and the year to date. ## With an AI assistant [#with-an-ai-assistant] Over MCP, `get_budget`, `set_budget` and `get_budget_vs_actual` read and save the budget and compare it with actuals. The **Draft a budget from last year** playbook builds a draft from last year's actuals and your growth assumptions for each section and shows it to you before anything is saved. # Year end and annual financial statements (/financials/year-end) At year end you bring the books up to date, close the year, and produce the annual financial statements (AFS). Financials walks you through it on the **Annual statements** page. Closing a year and finalising the pack need Financials Admin or an Owner. ## Lock dates [#lock-dates] You don't have to wait for year end to protect a period. Under **Settings → Financial years**, each year has a **Lock date**. Nothing dated on or before it can be posted, edited or deleted. Set it once a period is reconciled, and clear it to open the period again. Posted entries are never edited in place anyway. To correct one, reverse it from the **Journal** and post it again, or reclassify the bank line on its statement. ## The year-end checklist [#the-year-end-checklist] Pick the year in the header and open **Annual statements**. The **Year-end checklist** on the left lists what to do, with **Open** to go to the page for each step: 1. **Review imported bank statements**: every upload for the year reviewed. 2. **Run depreciation to year end**: on **Assets → Depreciation runs**, set the **Period start** and **Period end**, check the preview and post it. 3. **Reconcile VAT**: in South Africa, check and finalise each VAT201 period on **VAT**. Elsewhere, if you're VAT registered, agree the VAT balances on the trial balance to the returns you filed. 4. **Complete the tax computation**: South Africa only. Review add-backs and allowances on **Tax**, then post deferred tax. 5. **Close the financial year**: click **Do it**. 6. **Finalise the AFS pack**: click **Do it** once the year is closed. The steps that only apply to South African companies don't appear for other countries. ## Closing the year [#closing-the-year] Closing a year transfers income and expenses to retained earnings and locks the year, so nothing more can be posted into it. You can close it from the checklist or from **Settings → Financial years** with **Close year**. * Years close in order. If an earlier year is still open, Financials asks you to close that one first. * To undo a close, click **Reopen** on **Settings → Financial years** and give a reason. The reason is kept in the audit log. Years reopen newest first, and a year with a finalised AFS pack can't be reopened until the pack is unfinalised. ## Compiling the AFS pack [#compiling-the-afs-pack] The pack is one printable document with the statements your reporting framework includes, and the notes. Its cover title follows the framework: "Annual Financial Statements" under IFRS for SMEs and Full IFRS, "Financial Statements" under FRS 102, FRS 105 and US GAAP, and "Management Accounts" under **Management accounts**. See [Getting set up](/financials/getting-set-up#reporting-framework-and-preparer) for choosing the framework. 1. Check the **Cover page** card. The company name, registration and VAT numbers and **Prepared by** come from **Settings → Company**. 2. Tick **Include directors' responsibility page** if you want it. 3. Choose the assurance level under **Assurance stated on the cover**: **Audited**, **Independently reviewed**, **Independently compiled (not audited or reviewed)** or **Not audited or reviewed**. In South Africa the Companies Act requires the first page to say which, and who prepared the statements, so Financials reminds you if it's not set. 4. Fill in **Date authorised for issue** and **Authorised by**. They're printed at the top of the notes, and Financials reminds you if they're missing. 5. Describe what the company does under **Principal activities**. The general information page after the cover prints it with the country, the legal form, the registration number and the address from **Settings → Company**. 6. Click **Compile draft**. After changes, click **Save & recompile draft**. A compiled pack shows its version, the profit for the year and total assets, whether the balance sheet balances, and whether the cash flow reconciles. **check classifications** next to the cash flow means some accounts need a cash-flow section set in the chart of accounts. Any other warnings are listed underneath, including notes that still hold the prompt they were seeded with and loans from shareholders shown as non-current. A loan is only non-current if the company can defer repayment for at least 12 months after year end. If it can't, change the account's statement line to the current one in **Chart of accounts**. A loan with terms on the **Loans** page gets a more exact warning. Its instalment and rate say how much is repaid in the next 12 months, and that part is a current liability. Each account sits on one statement line, so add a sub-account under the loan on the current borrowings line, journal that amount into it at year end and reverse the journal the next day. Once the sub-account holds a balance the warning goes, and the maturity note reads the loan and its sub-account as one loan. Preview the pack in the browser or click **Download PDF**. Amounts are shown in whole currency units. ### Notes [#notes] The notes are on the **Notes** page in the **Reporting** group. A new financial year starts with the notes your framework calls for, such as accounting policies, property, plant and equipment, and taxation. The property, plant and equipment and tax notes fill themselves in from the asset register and the tax computation. There's a breakdown note for each balance a small company may have, such as inventories, share capital, loans from shareholders, borrowings and provisions. A breakdown note whose accounts have no balance in either year is left out of the pack and doesn't take a number, so the pack only lists what the company has. The **Notes** page still shows it, with a line saying it's left out. Writing text in it brings it back. The taxation note splits the tax expense into current and deferred tax and reconciles it to tax at the statutory rate. In South Africa it also shows the tax computation, and when the computation uses the small business corporation rates, what they saved against the statutory rate is its own line in the reconciliation. The trade receivables note gets an age analysis by how far past their due date the invoices were at year end, and after the cash flow notes there's a reconciliation of loans from opening to closing balance and a note of when the company's liabilities fall due. Loans with terms are split by their instalments; loans without terms show as due within a year when they're on a current line, or with no fixed date otherwise. Tables in the notes carry the year headings, such as FY2027 R and FY2026 R. Edit the wording as you need; changes save as you type, and the assistant can draft notes for you. If you change framework, **Refresh notes for framework** on the **Annual statements** page brings the notes in line with it. Notes nobody has edited take the new framework's wording, notes it doesn't use are removed and missing ones are added. Notes you've edited are kept as they are. ## Finalising [#finalising] Finalising freezes the pack as a permanent snapshot, so the PDF won't change even if something is posted later. You can only finalise a closed year. If you need to change a finalised pack, click **Unfinalise**. The finalised version is kept, and a new draft version is created for you to work on and finalise again. ## Archived years [#archived-years] Older closed years can be kept in an archive file instead of the live books, which keeps a company with a long history fast. **Settings → History** lists them, with each year's dates, its source (archived or migrated), size and **Verified totals**. Reports and comparatives still cover archived years, and the account ledger reads their lines when a date range reaches them, which takes a few seconds the first time. Archived years are read-only. Only the Owner can download an archive. Years whose archive was replaced by a newer one, or failed, are hidden behind **Show superseded and failed**. ## Asking the assistant [#asking-the-assistant] The assistant can prepare most of this for you, such as running depreciation or drafting notes. Closing and reopening a year are left to a person; see [The assistant](/manage/roles#the-assistant). # Payroll in the books (/financials/payroll) When a pay run is finalised in Looped Payroll, or you record one by hand on the **Payroll** page in Financials, one journal is posted on the pay date: | Account | Debit | Credit | | ------------------------ | ----------------------------------: | --------------------------------------------------------: | | Salaries & Wages | gross pay | | | Employer Contributions | employer UIF, SDL and contributions | | | PAYE Payable | | PAYE | | UIF Payable | | employee and employer UIF | | SDL Payable | | SDL | | Other Payroll Deductions | | other deductions and employer contributions owed to funds | | Salaries Payable | | net pay | Net pay goes to **Salaries Payable** because on the pay date you owe it to your employees. It hasn't necessarily left your bank yet, and it might leave on a different day or in several payments. ## Paying salaries from the bank statement [#paying-salaries-from-the-bank-statement] When you upload the bank statement that shows the salary payments, the review screen offers each one as **Pays salaries (payroll)**. It does this when a payment falls within five days of the run's pay date and is either the whole net pay still owed, or part of it for a line you'd have posted to Salaries & Wages, like one employee's EFT. Confirming the match posts the payment, dated the day it left the bank: | Account | Debit | Credit | | ---------------- | ----------: | ----------: | | Salaries Payable | the payment | | | Bank | | the payment | Nothing is posted to Salaries & Wages again, so the salaries aren't counted twice. You can match several payments to one run until its net pay is fully paid. Financials refuses a payment that's more than the net pay still owed. The **Payroll** page shows each run's net pay and how much of it is still to pay, and the **Net pay** figure at the top shows the total not yet paid. Unmatching a payment on the review screen reverses its entry, and that amount is owed again. ## When a run is reversed after it was paid [#when-a-run-is-reversed-after-it-was-paid] If Payroll reverses a run whose salaries were already paid, the run's journal is reversed but the payments stay, because the money did leave your bank. Salaries Payable then has a debit balance for that run, and the Payroll page marks it **Paid, run reversed**. That's usually the moment to post the corrected run, or to recover the money. ## Runs posted before September 2026 [#runs-posted-before-september-2026] Runs posted before 27 September 2026 credited net pay straight to the bank. They keep working as they did: matching the salary payment posts it against the run's own journal, with no new entry. The EMP201 payment to SARS works the same way for every run. # Payroll (/payroll) Looped Payroll runs a South African payroll. It works out PAYE, UIF, SDL and the Employment Tax Incentive (ETI) for each employee, produces payslips, and prepares your monthly EMP201 and UIF declaration and your EMP501 at year end. Open it at [app.looped.sh/payroll](https://app.looped.sh/payroll). Payroll prepares the figures and files. You still submit them yourself: the EMP201 and EMP501 on SARS eFiling and e\@syFile, the UIF declaration on uFiling, and the salary payments through your bank. ## Who can use it [#who-can-use-it] Payroll is for **South African companies** only. It checks the company's country on the **Company** page in Manage. If the country isn't South Africa, or isn't set, Payroll won't open and says why. Inside a South African company, who gets in depends on their access: | Person | What they see in Payroll | | ------------------------------------------------------------ | ---------------------------------------------------------- | | **Owner** | Everything, salaries, ID numbers and bank details included | | Someone with **Payroll Admin** | Everything, the same as an Owner | | Someone with a custom role that includes Payroll permissions | The parts of Payroll their role allows | | An employee linked to their employee record | **My pay** only: their own payslips and tax certificates | | Anyone else | Nothing. Payroll shows "You don't have access to Payroll" | Because Payroll shows everyone's salaries, only an Owner can give Payroll Admin or a custom role that includes Payroll. See [Roles & permissions](/manage/roles) for the details, including what a custom role can split out (such as seeing salaries, seeing ID and tax numbers, seeing or changing bank details, preparing, approving, finalising and reversing pay runs, and producing filings). Employees don't need a role to see their own payslips. See [My pay](/payroll/my-pay). ## What it costs [#what-it-costs] Payroll comes with Business, or with being a managed company or a company that pays for managed companies, including the 30-day Accounting trial. If the trial or plan ends, Payroll goes read-only: you can still open everything, but you can't change anything until an Owner subscribes under **Billing** in Manage. See [Purchasing a subscription](/purchasing-subscriptions). ## How it connects to the rest of Looped [#how-it-connects-to-the-rest-of-looped] * **Manage** holds the company's name, address, bank accounts and SARS registrations (PAYE, UIF and SDL reference numbers). Payroll reads them from there, so you keep them in one place. Manage also sends the invites for My pay. * **Financials** gets a journal for every pay run you finalise, and a reversing journal if you reverse one. See [Payroll in the books](/financials/payroll). The EMP201 and UIF declaration deadlines in Financials link to the matching pages in Payroll. * **Track** can supply hours for employees who are paid from the hours they log. See [Running payroll](/payroll/pay-runs#hours-from-track). ## Finding your way around [#finding-your-way-around] The sidebar groups Payroll's pages: | Section | Pages | | ------------- | ----------------------------------------------------------------------- | | **Payroll** | **Dashboard**, **Pay runs**, **Employees**, **Pay cycles** | | **Reporting** | **Filings**, **Reconciliation**, **Year end**, **COIDA**, **Audit log** | | **Settings** | **Setup**, **Move from Sage**, **Payroll settings**, **Pay items** | **Setup** and **Move from Sage** leave the sidebar once setup is finished. If you're on the payroll yourself and linked to your record, a **You** section with **My pay** appears at the top. The **Dashboard** lists what needs doing, such as preparing or finalising a run, adding missing bank details or tax numbers, and upcoming filing deadlines, next to the next pay day, last month's cost and what's due to SARS next. ### The tax year [#the-tax-year] A South African tax year runs from 1 March to the end of February. The tax year picker in the header sets which year every page shows. Past runs and payslips show exactly as they were finalised. Employee details always show as they are today. ## Next steps [#next-steps] 1. [Set up Payroll](/payroll/setting-up): company details, settings, a pay cycle and your employees. 2. [Run payroll](/payroll/pay-runs) each pay day. 3. [File the EMP201 and UIF declaration](/payroll/filings) each month. 4. [Do the year end](/payroll/year-end): the EMP501, IRP5s and the COIDA Return of Earnings. # Setting up Payroll (/payroll/setting-up) The first time you open Payroll, the **Set up payroll** page takes you through three steps: **Company**, **Settings** and **Pay cycle**. You can change any of it later, and you can click **Skip for now** and come back from **Setup** in the sidebar. Setting up needs the **Manage employees** permission. Owners and Payroll Admins have it. If you're moving from Sage partway through a tax year, see [Moving from Sage](#moving-from-sage) instead. ## 1. Your company [#1-your-company] Payroll uses the company details and SARS registrations kept on the **Company** page in Manage. This step shows what it found: the company **Name**, **PAYE reference**, **UIF reference** and **SDL reference**. Anything missing is flagged. You need them for the EMP201 and the IRP5s, but you can carry on and add them later with **Open the Company page**. ### The SARS contact person [#the-sars-contact-person] The Company page also has a **SARS contact person**: the person SARS and the Department of Labour contact about your payroll submissions. Payroll puts their name, phone and email on the EMP501 reconciliation file, and their name on the monthly UIF declaration. Nothing else in Looped uses it. It isn't required. You can leave it blank and fill it in before your first UIF declaration or EMP501. If the phone or email is blank, the EMP501 uses the company's general contact phone and email instead. ## 2. Payroll settings [#2-payroll-settings] These are Payroll's own settings. You can change them later under **Payroll settings**. | Section | Setting | What it does | | ---------------------------- | ----------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **PAYE registration** | **Registered for PAYE from**, **Registered until** | An EMP201 is due every month from this date, a nil one when nobody was paid. Left empty, returns start from the first month anyone was paid. Only fill in **Registered until** once SARS has cancelled the registration. | | **Skills Development Levy** | **SDL is due** | Switch it on once you expect to pay more than R500 000 in salaries over the next 12 months. Payroll suggests it when you get close. | | | **SDL is paid straight to a SETA** | Only for employers a SETA collects from directly. Most pay SDL to SARS with the EMP201. | | **UIF** | **UIF is paid straight to the Department of Labour** | Only for employers not registered with SARS for PAYE or SDL. | | **Employment Tax Incentive** | **We can claim ETI** | Payroll then checks each employee's eligibility every month. Further questions cover special economic zones, a National Minimum Wage exemption and public entities. | | | **These answers are right** | ETI isn't claimed until someone confirms the answers. Changing an answer asks you to confirm again. | | **Tax** | **How PAYE is annualised** | **SARS formula (recommended)** for new companies. **Sage's day factor (moving from Sage)** keeps payslips matching Sage to the cent; you can switch at the start of a tax year. | | | **Diplomatic indemnity** | Only for foreign missions whose employees have diplomatic indemnity. | | **Retirement funds** | **The pension and provident funds you contribute to** | **Defined contribution (most funds)** or **Defined benefit, or a mix**. Only matters if the company pays into a pension or provident fund. | | **Pay runs** | **A second person approves each run** | Someone other than the person who prepared the run has to approve it before it's finalised. | | **Salaries** | **Pays salaries from** | The company bank account the salary payment file pays from. The accounts come from the Company page in Manage. | Click **Save and continue**. ## 3. Your first pay cycle [#3-your-first-pay-cycle] A pay cycle is how often you pay. Most small companies need one monthly cycle. 1. Give it a **Name** (it starts as "Salaries"). 2. Choose **How often**: **Monthly**, **Fortnightly** or **Weekly**. 3. Choose the first month (or first day) it pays for. Monthly periods are calendar months. 4. Choose the **Pay day**. For a monthly cycle, a pay day on a weekend moves to the Friday before. For weekly and fortnightly cycles, you pick a weekday in the last week of each period. 5. Click **Create cycle and finish**. Payroll creates the cycle's periods for the tax year for you. To add another cycle later, open **Pay cycles** and click **New cycle**. ## Adding employees [#adding-employees] Open **Employees** and click **Add employee**. Fill in what you have; you can add the rest later from their page. The form is grouped into: * **Personal:** names, **Identity document** (SA ID, passport, asylum seeker permit or refugee ID), date of birth, **Email** (where payslips are emailed), **Job title** (shown on the payslip), **Tax number** and **Tax status** (**Employee** or **Director of the company**), and a home address. * **Employment and pay:** **Pay cycle**, whether they're paid a **Salary per period** or an **Hourly rate**, **Pay from Track hours**, hours per day and days per week, how part periods are paid, the minimum wage that applies, and **Payment method**. * **Tax and benefits:** **Medical aid members**, private medical aid and a private retirement annuity they pay themselves. * **UIF, SDL, COIDA and ETI:** the UIF exclusion, if one applies, and switches such as **Leave out of SDL**, **Leave out of COIDA**, **Independent contractor**, **Domestic worker** and **Connected person**. * **Bank account.** Click **Add employee** to save. ### Changing an employee's details [#changing-an-employees-details] Edit the fields on the employee's page. Nothing saves until you click **Review changes**, which lists each change before and after. Changes apply from the start of the current period unless you pick a later date under **Applies from**, which schedules the change. A change to pay needs a reason, such as "Annual increase". Each change is kept as a new version. Earlier payslips don't change, and **History** on the employee's page lists every version. Scheduled changes show as **Change scheduled from** on the employee's page until they take effect. Bank details change separately, with **Change bank details**, and need the **Change bank details** permission. You type the new account number twice, and the change is recorded in the audit log. Changing bank details is something only a person can do, never the assistant. ### Recurring pay items [#recurring-pay-items] Allowances, deductions, company contributions and fringe benefits that apply every period go under **Recurring pay items** on the employee's page. Click **Add a recurring pay item**, search the catalogue, enter the **Amount per period** (or **Rate per unit**) and the date it applies **From**, and click **Add item**. Changing an amount later also needs a reason. The catalogue under **Pay items** lists every item with its tax treatment and IRP5 source code. If you need one that isn't there, click **New pay item** and give it a **Name**, **Kind**, **IRP5 source code** and **Tax** treatment. Check the code with your accountant. ### Other sections on the employee's page [#other-sections-on-the-employees-page] Depending on your settings, an employee's page also has: * **Employment Tax Incentive:** the answers ETI needs for that person. Payroll doesn't claim ETI for them until these are answered. * **Fund certificates:** for a defined benefit retirement fund. * **Tax directives:** directives from SARS. * **Leave on the UIF declaration:** maternity, adoption or illness leave, which the UIF declaration reports. * **My pay:** invite them to see their own payslips. See [My pay](/payroll/my-pay). * **Leaving:** end their employment. See [When someone leaves](/payroll/pay-runs#when-someone-leaves). ## Moving from Sage [#moving-from-sage] If you're partway through a tax year on Sage, **Move from Sage** brings your payroll across instead of starting from nothing. It needs an Owner or someone with every Payroll permission. Nothing is saved until you confirm. The wizard's steps are **Cut-over**, **Files**, **Pay items**, **Review**, **Dry run** and **Confirm**: 1. **Cut-over:** choose the **First month in Looped** and the pay cycle to use. 2. **Files:** upload Sage's reports. **Employee Details**, **Employee Tax Certificate Recon**, the **EMP201** for each month before the cut-over, and the payslips or Pay Register for the cut-over month and every month before it are needed. The **Employment Tax Incentive Detail**, **Medical Aid Report**, **OID Return of Earnings** and e\@syFile export are optional. 3. **Pay items:** check the Looped pay item suggested for each of Sage's. 4. **Review:** check what was read. 5. **Dry run:** Looped works out the cut-over month the way your first run will and compares each payslip with Sage's. 6. **Confirm:** click **Confirm the take-on**. The months Sage paid come across as imported runs. Where you uploaded Sage's payslips, they're recreated in Looped so your employees see them in My pay. Imported months never post to Financials. ### Preparing the move with the assistant [#preparing-the-move-with-the-assistant] If you'd rather not export every report from Sage, you can ask the Looped assistant to key the take-on in for you from what you give it, such as a spreadsheet of employees or Sage's Employee Tax Certificate Recon. It can start the take-on with the cut-over month, add or update employees (names, ID or passport and tax numbers, start dates, pay, bank accounts, UIF and recurring pay items), set whether the company pays SDL and who's left out of it, and load each employee's year to date by IRP5 source code for the tax year of the cut-over. It reads back the take-on with anything still to fix, so it can correct a field before you look. Everything the assistant prepares goes into the same take-on as uploaded reports, held encrypted, and none of it affects a pay run, a payslip or a filing yet. You open **Move from Sage**, where **Review** marks what came **From the assistant**, and you click **Confirm the take-on** yourself. The assistant can't confirm or discard a take-on, and it can't change the cut-over month once you've chosen one. Preparing needs someone who can manage employees and see salaries, ID numbers and bank details, so an Owner's or Payroll Admin's assistant can do it. You can mix the two ways in; for example, the assistant adds the employees and year to date and you upload Sage's EMP201s so the months Sage paid come across as well. The assistant doesn't bring across EMP201 totals, ETI history or COIDA earnings; those still come from Sage's reports. ### Keeping Sage's past payslips [#keeping-sages-past-payslips] Once the take-on is confirmed, **Past payslips from Sage** on the take-on page keeps the payslips Sage issued, so each employee can still open them in My pay. Upload the payslip PDFs Sage prints, for a month or for each employee. Nothing is saved when you upload. Looped reads each file and lists one row per payslip: the pages, the employee, the pay date, the tax year, the net pay and how it was read. You can change the employee or the pay date, tick **Skip** for a row you don't want, or **Remove file**. **Keep** saves the payslips to each employee's record, with only their own pages. A payslip already kept for that employee and pay date shows as **Already kept** and isn't saved twice. Looped reads Sage's payslip layouts first. A page in a layout it doesn't know is read by AI, which takes only the employee code, name, pay date and net pay, and the row is marked **AI**. Looped checks the code is one of your employees, the name roughly matches theirs and the date falls in a tax year; if not, you pick the employee or date before you keep it. Nothing the AI reads is saved until you click **Keep**. Uploaded files are stored encrypted while they wait for review and are deleted once you keep or remove them. Recreating payslips for imported months (**Add Sage payslips to imported months**) only uses Sage's known layouts, never AI. # Running payroll (/payroll/pay-runs) Each pay period has one pay run. You prepare it as a draft, check it, and finalise it. Finalising locks the payslips, posts the run to Financials and adds it to the month's EMP201 and UIF declaration. ## Preparing a run [#preparing-a-run] 1. Open **Pay runs**. 2. Click **Prepare** and the period, for example **Prepare September 2026**. If you have more than one pay cycle, the button starts with the cycle's name. If the run is already started, the button says **Open** instead. The **Dashboard** also lists the run under **What needs doing** when it's time to prepare it. The draft works out a payslip for everyone in the cycle who was employed in the period. At the top you see the run's **Employees**, **Gross pay**, **PAYE** and **Net pay**, with the total cost to the company. Click **Recalculate** to work the draft out again, for example after changing an employee's details. ### Changes since the last run [#changes-since-the-last-run] This list compares the draft with the last finalised run and shows what's different. Changes that need a look carry a **Check** badge and a tick box. Tick each one once you've checked it. You can't finalise the run until every flagged change is ticked. If nothing changed, the list says **Nothing to review** and you can process the run in one step. ### Not supported yet [#not-supported-yet] If someone in the run has something Payroll can't calculate correctly yet, such as a pay item whose treatment isn't checked or pay below the minimum wage without an exemption, a **Not supported yet** card lists them with the reason and what to do. The run can't be finalised until the list is empty. ### Once-off adjustments [#once-off-adjustments] For a bonus, overtime, unpaid leave or anything else that's only for this period: 1. In the **Employees** table, click **Adjust** next to the person. This opens their draft payslip. 2. Under **Once-off adjustments**, click **Add a once-off adjustment**. 3. Choose the **Pay item**. For an earning, choose whether it **Adds to pay** or **Reduces pay**. 4. Enter the **Amount**, or for hourly items the **Hours**, **Rate per hour** and **Multiplier**. 5. Optionally add text under **Shown on the payslip**, and click **Add adjustment**. Payroll doesn't read leave from anywhere else. Enter paid and unpaid leave as once-off adjustments. ### Hours from Track [#hours-from-track] For employees set to **Pay from Track hours**, the draft reads their hours from [Track](/track). A **From Track** section on the run shows the hours it used. Payroll can only read hours for an employee who is linked to their Looped account, the same link that gives them [My pay](/payroll/my-pay). If someone changes their hours in Track after the draft read them, the new figure shows next to the one in use and nothing changes until you click **Use the new figures**. **Read again** checks Track for changes. Finalising reads Track again first, and refuses the run if Track can't be reached and someone is paid from Track hours. ### The payslip [#the-payslip] Click an employee's name to see their payslip: **Earnings**, **Deductions**, **Fringe benefits**, **Paid by the employer**, the totals, and **The full calculation** showing each step of how their tax was worked out. ## Finalising a run [#finalising-a-run] At the bottom of the draft, the button is **Process** when there are no changes since the last run, and **Finalise** when there are. 1. Tick every flagged change. 2. If your company has **A second person approves each run** switched on, someone other than the person who prepared the run clicks **Approve**. 3. Click **Finalise** (or **Process**). The dialog shows the run's totals. 4. Confirm. The payslips can't be changed afterwards, and the run is posted to Financials. See [Payroll in the books](/financials/payroll) for the journal it posts. Finalising a run with changes needs the **Finalise pay runs with changes** permission. The Looped assistant can process a run with no changes, but only a person can finalise a run with changes. ## After finalising [#after-finalising] A finalised run links to its **Bank payment file**, the month's **EMP201** and the month's **UIF declaration**. ### Paying your employees [#paying-your-employees] The **Bank payment file** lists each employee's net pay and account. Choose the format, **Standard Bank (Business Online)** or **Any other bank (CSV)**, and click **Download**. Then import the file in your bank's online banking and release the payments there. Accounts that changed since the last run, or that are being paid for the first time, are listed separately under **Changed since the last run**. Check them with each person before you release the batch: a changed bank account is the usual route for payroll fraud. Downloading the file needs permission to see both bank details and salaries. When the salary payments show on your bank statement, match them in Financials. See [Paying salaries from the bank statement](/financials/payroll#paying-salaries-from-the-bank-statement). ### Sending payslips [#sending-payslips] Click **Email payslips** on the run to email every employee their payslip, at the email address on their record. Payroll tells you how many went and how many were skipped for having no email address. Nothing is emailed until you click it. Employees linked to **My pay** see their payslip there as soon as the run is finalised, and get a **Payslip ready** notification if they've turned it on. See [My pay](/payroll/my-pay). ## Correcting a finalised payslip [#correcting-a-finalised-payslip] A finalised payslip is never edited. You correct it on a later run instead: 1. Prepare the next run in the same tax year, if you haven't already. 2. Open the finalised payslip and click **Correct this payslip** under **Corrections**. 3. Under **What happened**, choose **The payslip was wrong**. 4. Choose the draft run to **Pay it on**, **What was wrong** (a pay item, or nothing for a UIF-only correction), the amount, whether UIF applied, and a **Reason**. Payroll works the original month out again with the correction and pays the difference on the later run. The EMP201, UIF declaration and certificates count the correction in the original month. A correction on a draft run can be cancelled until that run is finalised. Payroll can't correct across tax years, and it can't record an employee paying back pay they received (such as a commission clawback). Record those with your tax practitioner. ## Reversing a run [#reversing-a-run] Reversing undoes a finalised run and opens its period again so you can run it afresh. Use it for a mistake you catch before the month is filed. 1. Open the finalised run and click **Reverse**. 2. Say **Why**, for example "The bonus belonged in the next month". 3. Click **Reverse run**. The run's journal in Financials is reversed. If the salaries were already paid, see [When a run is reversed after it was paid](/financials/payroll#when-a-run-is-reversed-after-it-was-paid). Payroll refuses to reverse a run when: * it isn't the cycle's latest finalised run; * the month's EMP201 or UIF declaration is marked as submitted (correct the payslips on a later run instead, or undo "submitted" on the filing if it wasn't); * someone in it was paid again later, in any cycle; * one of its payslips has a correction on a later run; * the next period's draft has once-off adjustments (remove them first); * its tax year is closed. Reversing needs the **Reverse pay runs** permission, and only a person can do it, never the assistant. ## When someone leaves [#when-someone-leaves] 1. Open the employee's page and, under **Leaving**, click **End employment**. 2. Enter their **Last day** and **Why they left** (the UI-19 reason code). 3. Enter any **Leave owed (days)**. It's paid out in the last run at their daily rate. 4. Check **Notice pay**. Payroll fills it in from the BCEA and their length of service; change it if their contract says more, or clear it if they work their notice. 5. Save. Their last run pays them to their last day, with the leave owed and notice pay. Once that run is finalised, you can preview or download their UI-19 from the same card, to sign and give them for their UIF claim. **Take back** undoes the ending if you recorded it by mistake. Ending someone's employment needs permission to change pay; the UI-19 needs permission to see salaries and ID numbers. # Monthly filings (/payroll/filings) Each month Payroll works out your EMP201 for SARS and your UIF declaration for the Department of Employment and Labour from the month's finalised pay runs. You submit them yourself, on eFiling and uFiling, and then mark them as submitted in Payroll. Open **Filings** to see every month in the tax year with its **PAYE**, **SDL**, **UIF**, **ETI used**, **Total payable**, the date the **EMP201** is due and the **UIF** declaration's status. The **Dashboard** also shows the next deadlines under **Filing deadlines**, and the EMP201 and UIF deadlines in Financials link to these pages. Downloading filings and marking them submitted needs the **Produce filings** permission, and only a person can do it, never the assistant. The UIF declaration also needs permission to see salaries and ID numbers, because the file names each employee. ## The EMP201 [#the-emp201] Open a month from **Filings**, or click **EMP201** on a finalised run. The page is titled **EMP201 for** the month and shows the due date. The figures are laid out in eFiling's order, so you can copy them across field by field: | Section | Fields | | --------------------------- | -------------------------------------------------------------------------------------------------------------------------------- | | **Payroll Tax Calculation** | **PAYE Liability**, **SDL Liability**, **UIF Liability** (employee and employer together), **Payroll Liability** | | **ETI Calculation** | **ETI Brought Forward**, **ETI Calculated**, **ETI Utilised**, **ETI Carry Forward** | | **Total Payable** | **PAYE Payable** (PAYE liability less ETI utilised), **SDL Payable**, **UIF Payable**, **Penalty & Interest**, **Total Payable** | **Penalty & Interest** is always 0 here. Add any SARS has charged, from your statement of account, when you file. The page also shows: * **Payment reference:** your PAYE reference and the payment period, for paying SARS. * **Employment Tax Incentive:** the EMP201's question "Do you have any outstanding returns or debt with SARS?". Answer **No, we're compliant** or **Yes, we have some**. Until it's answered, or if you answer yes, no ETI is used that month and it carries forward. * **Per employee:** each person's share. Click **Download figures** to keep a copy for filing. ### Nil returns [#nil-returns] Once your PAYE registration date is set in **Payroll settings**, Payroll expects an EMP201 for every month from then on. A month with no finalised run shows as a nil return: file it on eFiling with every amount as 0. ### Paying SARS [#paying-sars] Pay the total to SARS as usual. When the payment shows on your bank statement, match it in Financials. ## The UIF declaration [#the-uif-declaration] Open it from **Filings**, or click **UIF declaration** on a finalised run. It lists everyone employed in the month from their finalised payslips, with their **Gross taxable**, **UIF remuneration** and **Contribution**, and anyone who doesn't contribute with the reason. The UIF itself is paid to SARS with the EMP201. The declaration tells the Fund who you employed. It's due by the 7th of the following month on uFiling. 1. Click **Download a test file** to have uFiling check the file without storing it, if you want to. 2. Click **Download declaration** and upload the file on uFiling. Payroll reads every file back against the Fund's own checks before you download it. The page lists problems under **Fix these on uFiling** and **What the Fund's checks will flag**, and people left off under **Not on the declaration**. A problem that would get the file rejected stops the download until it's fixed. Maternity, adoption and illness leave recorded on an employee's page under **Leave on the UIF declaration** shows on the declaration for the months it covers. ## Marking a filing as submitted [#marking-a-filing-as-submitted] Once you've submitted the EMP201 or UIF declaration, open its page and click **Mark as submitted**. This clears the deadline and freezes the filed figures as the month's original return. **Undo** takes it back if you marked it by mistake. When SARS or the Fund answers, record it on the same page: choose **Accepted** or **Rejected** under **SARS said** (or **The Fund said**), add **Their reference**, and click **Record**. An accepted or rejected return can't be undone. If it was rejected, fix it, submit it again and mark it again. A month marked as submitted can't have its runs reversed. Correct the payslips on a later run instead. See [Correcting a finalised payslip](/payroll/pay-runs#correcting-a-finalised-payslip). ## When figures change after filing [#when-figures-change-after-filing] If a correction or a run changes a month you already downloaded or filed, the month's page says so: * **Downloaded, not yet filed:** a warning says the figures changed after they were downloaded. Download them again before you file. * **Filed EMP201:** a card lists each field that changed, with its **Filed** figure, the new one and the **Difference**, and the runs and corrections that explain it. Revise the EMP201 on eFiling with the new figures, then click **Mark the revision as submitted**. Payroll first asks **What eFiling shows for the month** (for example, **SARS audited or revised it** or **An agreed estimate**) and refuses a revision SARS wouldn't allow. * **Filed UIF declaration:** download the declaration again. It keeps the file name it was filed under, so it replaces the file you sent. If the runs and corrections don't account for the whole difference, check **Reconciliation** before revising. ## Reconciliation [#reconciliation] **Reconciliation** runs the checks SARS runs at the EMP501 every night, on each month so far, so a mismatch shows in the month it happens instead of at year end. Click **Run the checks now** to run them straight away. The **Dashboard** lists failed checks under **What needs doing**. # Year end (/payroll/year-end) A South African tax year runs from 1 March to the end of February. Twice a year you reconcile your EMP201s with your employees' tax certificates and submit an EMP501 to SARS through e\@syFile: | Reconciliation | Covers | Due | | -------------- | ----------------- | --------------------------- | | **Interim** | March to August | 31 October | | **Annual** | March to February | 31 May, after the year ends | Once a year you also submit a Return of Earnings to the Compensation Fund for COIDA. Pick the tax year with the tax year picker in the header before you start. ## The EMP501 [#the-emp501] Open **Year end**. The page is titled **EMP501** and the tax year, for example **EMP501 2026/27**. Choose **Interim (March to August)** or **Annual (March to February)** under **Reconciliation**. It opens on the one that's due. The page checks everything SARS will check before it lets you export: * **Each month:** the EMP201's **PAYE**, **Liability** and **ETI claimed**, against what was **Paid** according to your books in Financials, with the **Difference** and a **Result**. * **Certificates against the EMP201s:** the employees' certificates have to add up to the EMP201s. * **Certificates:** each employee's IRP5 or IT3(a), with its **Number**, **Taxable income** and **PAYE**. Numbers show as "Given on export" until the certificates are issued. Anything that would stop SARS accepting the file blocks the export until it's fixed. The [Reconciliation](/payroll/filings#reconciliation) page runs the same checks every night, so most problems show up in the month they happen. ### Exporting for e\@syFile [#exporting-for-esyfile] Both buttons stay unavailable until everything balances. 1. Click **Test file** to download a file you can import into e\@syFile to check it. A test file doesn't issue anything. 2. Click **Export for e\@syFile**, then **Export and issue**. 3. Import the file into e\@syFile and submit the EMP501 from there. **Export and issue** issues the certificates: each gets its certificate number for good, your employees see their IRP5s in [My pay](/payroll/my-pay), and the download is logged. The page lists every export you've made under **Exports**. Exporting needs the **Produce filings** permission and permission to see ID numbers, salaries and bank details, because the file carries all of them. Only a person can export, never the assistant. ## IRP5 details checked early [#irp5-details-checked-early] Payroll runs SARS's EMP501 rules that don't need the year's figures (home address, ID or tax number, contact numbers, the company's SIC7 and address) on every employee's record. Anything that would fail shows as a warning on the take-on Review step, beside the field on the employee's page, and on the dashboard ("2 employees are missing IRP5 details"). A warning stays until the details pass. It never holds up a pay run or the TEST export; only the LIVE export refuses. The company's SIC code is set in Manage and must be the five-digit SIC7 sub-class, like 62010. A four-digit code is refused. ## Correcting an employee's record [#correcting-an-employees-record] Pay details (salary, rates, cycle, medical aid, tax and UIF settings, payment method) change from the current period. Record details can be corrected from an earlier date, even inside a finalised month: home address, email and phone numbers, name spelling, job title, and ID, passport or tax numbers. Pick the earlier date under **Applies from** and give a reason. History shows it as "Record corrected", with who made it, when and from which date; the old value stays in History, and finalised payslips don't change. Tax certificates take the name and ID, passport and tax numbers from the corrected record. Contact details and the address are the latest you've recorded. When an ID, passport or tax number correction reaches a certificate already issued, the confirmation lists it: the next EMP501 for that year sends it again under the same number, and the employee should get the corrected copy. A change to the nature of person needs the certificate cancelled on e\@syFile first. ## COIDA Return of Earnings [#coida-return-of-earnings] Open **COIDA**. The **COIDA Return of Earnings** page shows what you paid employees and directors each month, for Section B of the Compensation Fund's CF-2A: * the number of **Employees** and their **Employees' earnings**; * the number of **Directors and members** and their earnings; * the totals for the year. Each person counts up to the year's maximum earnings, and only pay items marked for COIDA count. An employee set to **Leave out of COIDA** isn't counted. The page also shows your CF registration number from the Company page in Manage. The Compensation Fund doesn't take a file upload, so type the figures into its online Return of Earnings. You can preview or download the page as a PDF, or click **Download CSV**. ## Closing the tax year [#closing-the-tax-year] Once the annual EMP501 is exported and submitted, close the year from the card titled **Closing** and the year (for example **Closing 2026/27**) on **Year end**: 1. Check the card lists nothing still to do. The year can't close while any pay period isn't finalised, before the annual EMP501 is exported, or before next year's tax tables are available in Looped. 2. Click **Close** and the year, for example **Close 2026/27**, and confirm. Exporting the EMP501 doesn't close the year; only this button does. A closed year is read-only: its runs can't be reversed and its filings can't change. Closing the year needs the **Produce filings** permission. # My pay (/payroll/my-pay) **My pay** is where employees see their own payslips, how their tax was worked out, and their tax certificates, on their phone or computer. It's opened by linking a person to their employee record, not by a role, and it only ever shows that person their own records. ## Inviting an employee [#inviting-an-employee] 1. Open the employee's page in Payroll. 2. On the **My pay** card, click **Invite to My pay**. 3. Check the **Email** and click **Send invite**. Manage emails them an invite. When they accept, they join the company as a Member with no roles, so no other app opens for them, and they're linked to their employee record. They don't take a seat. See [Inviting team members](/inviting-team-members#inviting-employees-to-their-payslips). The **My pay** card shows where things stand: | Status | Meaning | | ----------------------- | ------------------------------------------------------------------------- | | **Not invited** | No invite sent yet | | **Invite sent** | Waiting for them to accept. **Revoke invite** cancels it | | **Invite expired** | Send it again with **Invite again** | | **Sees their payslips** | Linked. **Unlink** takes My pay away | | **No longer a member** | They've been removed from the company, so they can't open My pay any more | Inviting and unlinking needs the **Manage employees** permission. ### If you're on the payroll yourself [#if-youre-on-the-payroll-yourself] If you're already in the company, for example as an Owner, open your own employee record and click **This is me** on the **My pay** card. **My pay** then appears under **You** at the top of the Payroll sidebar. ### Emailing documents instead [#emailing-documents-instead] **Email payslips and IRP5 to this person** on the **My pay** card sends someone their payslips and IRP5 by email, including someone who has left the company. You can also email every payslip in a run with **Email payslips** on the run. See [Sending payslips](/payroll/pay-runs#sending-payslips). ## What employees see [#what-employees-see] An employee with only My pay who opens Payroll goes straight to **My pay**. It shows, for one tax year at a time: * **Year to date:** their **Taxable income**, **PAYE** and **Net pay** so far. * **Their payslips**, each with a PDF. Opening one shows the same lines, working and full calculation the company sees, exactly as it was finalised. * **Their tax certificates**, such as their IRP5, once the company has exported the EMP501 and issued them. * Payslips kept from Sage, if the company moved from Sage. If they have more than one tax year, they pick it under **Tax year**. **Download all my payslips** gives them a zip of every payslip and tax certificate, with a folder for each tax year. It's worth keeping: once someone is removed from the company, they have to ask their employer for copies. Until their record is linked, My pay says **Your payslips will be here**. Anything else in Payroll shows "This part of Payroll is for your employer". ## Payslip notifications [#payslip-notifications] When a run with their payslip is finalised, a linked employee can be told with a **Payslip ready** notification. It's off until they turn on push or email for it themselves, under **Profile** → **Notifications** in Manage. See [Notifications](/manage/notifications). # Looped Inventory (/inventory) Looped Inventory keeps track of what you buy and sell: how many you have, what they cost and what you charge for them. Open it at [app.looped.sh/inventory](https://app.looped.sh/inventory). Inventory works with the other apps rather than on its own: * **Invoices** picks items on quotes, sales orders, invoices and credit notes. Invoicing an item takes it off the shelf, and an open sales order reserves it. * **Financials** holds your suppliers. Approving a supplier invoice with items on it brings the stock in, and stock movements post to the books at average cost. ## What's in it [#whats-in-it] | Group | Pages | What they're for | | ------------- | ----------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- | | **Stock** | **Dashboard**, **Items**, **Purchase orders**, **Stock takes**, **Stock movements** (with **Adjust stock**) | Day-to-day stock: what to reorder, what's on its way, counting the shelf, every movement and bringing stock in or taking it out | | **Reporting** | **Reports**, **Client price lists** | Stock, purchasing and sales reports, and printable price lists for clients | | **Settings** | **Price levels**, **Opening stock**, **Audit trail** | Price tiers such as Trade or Retail, the stock you start with, and who changed what | The **Dashboard** is built around what to do today: **Reorder now**, **Deliveries due**, **Negative or uncosted stock**, stock health, stock value by category, and sales and purchases by month. Inventory follows the financial year chosen in the header. Every page is also in the ⌘K palette. ## Who can use it [#who-can-use-it] Owners can do everything. Everyone else needs an Inventory role, which you give on the **People** page in Manage. See [Roles & permissions](/manage/roles). | Role | What they can do in Inventory | | -------------------- | ---------------------------------------------------------------- | | **Inventory Admin** | Everything in Inventory, costs and settings included | | **Stock Controller** | Items, costs, stock takes and adjustments; no Inventory settings | | **Stock Counter** | Sees items and counts stock; no costs, and posts nothing | ## Where to start [#where-to-start] 1. [Add your items](/inventory/items), or have them brought across from your old system. 2. [Enter your opening stock](/inventory/stock#opening-stock). 3. [Order from suppliers](/inventory/purchase-orders) and receive what arrives. 4. [Set price levels and send client price lists](/inventory/prices). 5. [Count the shelf](/inventory/stock#stock-takes) and [read the reports](/inventory/reports). # Items (/inventory/items) **Items** lists what you buy and sell. Tracked items keep a count and a cost; the rest, such as services and fees, just fill in invoice and supplier invoice lines. ## The items list [#the-items-list] Each row shows the item's **SKU**, **Name**, **Category**, **Bin**, what's **On hand**, on **Sales orders**, **On order** and **Available**, its **Average cost** and the **Stock value**. Items you don't track say **Not tracked**. Click a column's heading to sort by it, and again to reverse it. Hover or tab to the ⓘ beside a heading to see what it means. Click a number to see what's behind it: **On hand** opens **Stock movements** for the item with its running balance, **Sales orders** its open sales orders and **On order** its open purchase orders. * **Search** matches the name, SKU or barcode. Every word you type has to match, in any order. * The first filter switches between **All items**, **Low stock** and **Archived**. * Filter by **Category**, or by **Supplier** to see only the items you've bought from that supplier. The supplier filter stays in the page's address, so you can bookmark it or share it. * Choose **Show 25**, **Show 50** or **Show 100** rows a page. * **Print** prints the list as filtered. Tick rows (or the box in the header for the whole page) to print only those. * With rows ticked you can also **Print labels**, **Generate barcodes** for the ones that have none, and **Archive** them (or **Restore** them in the Archived view). **Sales orders** is stock on open sales orders in Invoices that hasn't been invoiced yet. **Available** is on hand less what's on sales orders, and low stock is worked out from available stock. ## Adding an item [#adding-an-item] Click **Add item**. To copy another item's details, pick it under **Start from another item**: everything but its SKU, barcode and stock is copied. As you type the SKU and name, items with the same SKU or a similar name show under the field, so you don't add one twice. Then fill in: | Field | Notes | | ---------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **SKU** | Your code for the item, such as `MUG-350`. It shows first on document lines and in pickers | | **Name** and **Description** | The description is what shows on invoice lines | | **Barcode** | The code on the product, and its format: Code 128, EAN-13, EAN-8, UPC-A, Code 39, ITF-14, QR code, Data Matrix, GS1-128, GS1 DataMatrix or GS1 QR code. **Scan** reads it with the camera, or use a Bluetooth or USB scanner in the box; the format is worked out from what was read. **Generate** makes a new code. EAN and UPC check digits are checked, and added if you leave them off. If another item already has the code, it's named under the field | | **Bin** | Where it's kept, such as `Shelf A3`. Stock takes walk in bin order, and labels print it | | **Category** | Groups items in filters, reports and price lists | | **Unit** | Each, Box, Pair, Kilogram and so on | | **Selling price, excl. VAT** | The item's own price. [Price levels](/inventory/prices) can set others | | **VAT** and **VAT on purchases** | Standard rate, zero-rated or exempt. VAT on purchases can be the same as sales | | **Track stock** | Count what's on hand and move its cost to Cost of Sales as it sells. Turn it off for services and fees | | **Reorder level**, **Reorder quantity**, **Maximum level** | Drive the daily reorder digest, the reorder report and the dashboard | | **Minimum order** | The least the supplier sells. The reorder report rounds its suggestion up to it | | **Sales**, **Inventory** and **Cost of sales** accounts | Where the item posts in Financials | | **On hand**, **Unit cost** and **As at** | Optional, for tracked items and people who see costs: what's on the shelf when you start on Looped, what each cost excluding VAT, and the date. It goes in as the item's [opening stock](/inventory/stock#opening-stock). Stock bought after that comes in on a goods received note or supplier invoice | Once an item has stock movements it stays tracked. Archive it if you stop selling it; **Restore** brings it back. ## Suppliers [#suppliers] An item's **Suppliers** list says who you buy it from, **Their code** for it and their **Minimum order** if it differs from the item's. Tick **Usual** on the supplier you normally order from: the reorder report and purchase orders use it. The list saves with the item. Suppliers come from [Financials](/financials/suppliers). If Financials has none yet, add them there first. ## Barcodes and labels [#barcodes-and-labels] **Generate** (beside the barcode on an item, or **Generate barcodes** for ticked items on the list, which asks for the format) makes a new in-store number for your own labels, never the SKU: EAN-13 codes start with 04, UPC-A with 4 and EAN-8 with 2, the ranges GS1 keeps for a company's own use, so they never clash with a real product's code. GS1-128, GS1 DataMatrix, GS1 QR and ITF-14 carry a real GTIN, so Looped doesn't generate them: scan or type the code GS1 South Africa gave you. Codes for selling through other shops come from GS1 South Africa. **GS1 codes.** GS1-128, GS1 DataMatrix and GS1 QR code hold a GS1 element string: each part's application identifier in brackets, then its value, such as `(01)06001234567890(17)271231(10)ABC123`. The product's GTIN-14 in (01) comes first and is required. After it you can add a batch or lot number (10), an expiry date (17), a best-before date (15), a production date (11) and a serial number (21); dates are YYMMDD and batch and serial numbers take up to 20 characters. Type a plain EAN-13, UPC-A or EAN-8 and it becomes (01) and the GTIN-14. Check digits and dates are checked. **Generate** makes an in-store GTIN (starting with 2). Scanning a GS1 code finds the item by its GTIN, so a GS1 code on a product finds an item saved with the EAN-13, and the other way round. **Labels** (or **Print labels** on an item or the list) prints shelf and product labels: 1. Add items, and choose **One each**, **One per unit on hand** or your own count per item. 2. Choose the **Label size**: an A4 sheet of 24 (3 × 8) or 14 (2 × 7), or a 50 × 25 mm or 100 × 50 mm thermal roll, one label a page. 3. Choose what each label **Shows**: name, SKU, price (excluding VAT) and bin. On a sheet you've used before, **Skip labels** leaves the used ones blank. 4. Check the preview, then **Print** or **Download PDF**. Looped remembers the size and fields for next time. ## Packs [#packs] The **Packs** tab on an item lists the boxes and cartons it comes in: a **Name**, how many of the item it **Holds** (a carton of 12 boxes of 12 holds 144), an optional **Barcode**, and whether it's the default when buying or selling. Stock is always kept in the item's own unit, so packs never change costs or the books. * Scanning a pack's barcode finds the item and counts the whole pack: in **Adjust stock** and **Receive stock** it adds that many, and on the stock take count screen it asks how many packs and adds them to the count. * Purchase order and goods received lines can be entered in a pack: pick it beside the quantity. The unit cost stays per unit, and the line remembers the pack as it was. * **On hand** shows the largest whole packs beside the quantity, such as `144 each · 12 boxes`. * On **Labels**, choose a pack on a line to print its barcode instead of the item's. ## Products with variants [#products-with-variants] Clothing and anything else sold in sizes and colours can be one product with variants. Choose **Add product with variants** on the items list, give it a **Name**, a **Base SKU** and up to three **Options** (such as Colour and Size), and type each value with a short **Code**. Every combination becomes its own item, with a SKU made of the base SKU and the codes joined with a dash: `SW100-NAV-M`. * Each variant keeps its own stock, price, barcode and reorder level, so reordering stays per variant and invoices pick the variant. * The items list shows a product as one row with its totals; open it to see the variants. A search or a filter such as **Low stock** shows the product with only the matching variants. * On the product's page, **Edit all variants** (or tick some first) changes the selling price, reorder level, reorder quantity or category on all of them at once. * **Edit product** renames it or adds values: adding XL makes the missing XL variants. Values can't be removed once variants use them; archive the variant instead. * **Stock on hand** shows each variant's product with the product's total, and **Sales by product** totals each product's variants. * **Add existing items** on the product's page groups items you already have into it: pick each and give it a value per option. They keep their SKUs. The link icon on a variant's row takes it out of the product again; it stays an ordinary item. * Click the picture beside the product's name to give the product its own picture. Variants keep theirs. Each item has **Earns commission**, on by default, which the Commission by sales code report in Invoices uses. ## Prices by level [#prices-by-level] If you use [price levels](/inventory/prices), the item page shows **Prices by level**: the item's price on each level, excluding VAT. A price you set here wins over the level's rule. To price many items on one level at once, use **Edit prices by level** from **Items**. ## The item page [#the-item-page] Besides its details, an item shows: * **On hand**, **Sales orders**, **On order**, **Available**, **Average cost** and **Stock value**. Click a quantity to open what's behind it. * What's **On open purchase orders**, **On open sales orders** and **On open quotes**. * **Stock movements**: every movement, from opening stock, goods received notes, supplier invoices, invoices, returns, stock takes and adjustments. Years that have been archived load when you ask for them. * **History**: who added, edited, archived or restored the item, and each field they changed. When more was sold than you had, the item says so: Inventory doesn't guess a purchase that was never recorded. ## Pictures [#pictures] An item can have a picture. On the item page, choose **Add a picture** to upload a JPEG or PNG of up to 5 MB, or take a photo on a phone. **Change picture** replaces it and **Remove** takes it off. A price list prints each item's picture in a small column beside it whenever any item on the list has one. To print pictures on quotes, sales orders and invoices too, turn on **Show item pictures on documents** under Invoices › Settings › General. # Stock takes, adjustments and opening stock (/inventory/stock) ## Stock takes [#stock-takes] Count what's on the shelf. Looped compares it with what the books expect, and posts the differences once someone has reviewed them. Count everything at least once a year, and the fast movers more often. 1. On **Stock takes**, give the count a note and choose what it **Covers**: all items or one category. Under **Who counts what**, you can give categories (and everything else) to people who can count. Click **Start a stock take**. 2. Count. Type or scan a barcode or SKU and press Enter, or tap **Scan** to read barcodes with the device's camera where the browser supports it. Items are listed by bin, then name, so you can walk the shelves in order. Someone with a part sees only their part at first; untick **Only my part** to see everything. Scanning an item from someone else's part still opens it, with a note. A **Stock Counter** can count without seeing costs or posting. 3. Review. Each item shows its **Bin**, what was **On hand**, what was **Counted**, the **Difference**, its **Value**, and who counted it and when. Filter by whose part it is, change **Who counts what** while it's still counting, or **Download CSV**. 4. Someone who can post chooses **Post**, picks the **Post on** date and confirms. If everything matches, nothing changes and the stock take closes. A stock take that's no longer needed can be cancelled. The list searches by number or category and filters by status: **Counting**, **Posted** or **Cancelled**. ## Adjusting stock [#adjusting-stock] **Stock movements**, under **Stock**, lists everything that moved stock: purchases, goods received, sales, returns, stock takes and adjustments. Search by reference, item or person, and filter by **Item**, **Type** (including each adjustment reason) and **Dates**. Pick one item to see its balance after each movement, starting from what was on hand before the period. Export it as CSV or PDF. The **Activity** button on an item opens it for that item. **Adjust stock** on that page brings stock in or takes it out. Add items by searching, or scan them with a barcode scanner: each scan adds one, and scanning the same item again adds one more to its line. Set each line to **In** or **Out** with how many, then pick one reason for the lot (**Found**, **Shrinkage**, **Damaged** or **Other**) and a note if you like. It goes to Inventory Adjustments in the books. Stock going out comes off at average cost. Stock coming in goes on at the **Unit cost** on its line, which starts at the item's average cost and can be changed; an item with no average cost yet needs one. Only people who can see costs get the field; for everyone else stock comes in at average cost. Stock you bought isn't an adjustment. Receive it on a [goods received note](/inventory/purchase-orders#goods-received-notes), against its purchase order or without one, so the supplier invoice can be matched to it and isn't counted twice. Older adjustments with the reason **Received** still show in movements and reports. ## Locations [#locations] If you keep stock in more than one place (two stores, a warehouse, a van), add them under **Settings** › **Locations** with a name and a short code such as `DBN`. Every company starts with one location, **Main**, and while that's the only one Inventory doesn't mention locations at all. Costs stay per item: an item costs the same at every location. Once there's a second location: * **Transfer stock**, under **Stock**, moves stock from one location to another. Scan or search for the items, say how many and confirm. Nothing posts to the books, and a location can't be taken below zero. * Starting a stock take asks which **Location** to count; differences adjust that location only. * **Adjust stock** asks which location the stock is at. * The item page shows what's on hand at each location under **By location**, with a bin per location, and the items list shows each location's quantity under **On hand**. Goods received, sales and anything else that doesn't name a location go to the **Default location**. Change which one that is on the location. A location that still holds stock, or the default, can't be archived. ## Opening stock [#opening-stock] **Opening stock**, under **Settings**, is what was on the shelf on the day you start and what it cost. Choose the **Take-on date**, then enter a quantity and unit cost per item, or paste one item per line as `SKU, quantity, unit cost`. It goes into the books as one entry. Entering an item again replaces its figures. Add your items first; only tracked items take opening stock. A new item can take its opening stock on the **Add item** form too: fill in **On hand**, **Unit cost** and **As at**. Stock takes, adjustments and opening stock all show in the [audit trail](/inventory/reports#audit-trail). # Purchase orders (/inventory/purchase-orders) **Purchase orders** is what you've asked suppliers for, and what has arrived. ## The list [#the-list] Search by number, supplier or notes, and filter by status, supplier and order date. Open orders show whatever financial year is picked in the header; **All years** shows the rest. | Status | Means | | ------------------- | ----------------------------------------------- | | **Draft** | Still being put together. Its lines can change | | **Sent** | Emailed or marked as sent. The lines are fixed | | **Partly received** | Some of it has arrived | | **Received** | Everything has arrived | | **Cancelled** | Taken off what's on order. It stays in the list | ## Making an order [#making-an-order] Click **New purchase order**, or let the [reorder report](/inventory/reports) draft one order per usual supplier for everything that's running low. 1. Choose the **Supplier** first. Suppliers come from [Financials](/financials/suppliers). 2. Add lines from the product picker. It lists **This supplier**'s items first, then **Other items**; typing searches every item by code or name. Each row shows the code, cost, name and stock. 3. A line is a description with the item beside it, like an invoice line. The supplier's code for the item shows under it and prints on the order. The last price you paid fills in the **Unit cost**; add a **Disc %** and the **VAT %** if needed. A quantity below the supplier's minimum order shows a warning; you can still order it. 4. Fill in **Your reference**, the **Order date**, **Expected date**, **Payment terms (days)**, **Deliver to** and **Notes for the supplier**. **Deliver to** starts as your company's address and can be changed per order. VAT comes from your company's country. ## Sending it [#sending-it] **Send to supplier** emails the order as a PDF, with replies going to your company's email. If you sent it some other way, choose **Mark as sent** in the ⋮ menu. Either way the lines are fixed from then on: to change them, cancel the order and start a new one. **Preview** shows, prints and downloads the PDF. A draft can be deleted; its number isn't reused. A sent order with nothing received can be cancelled. ## Goods received notes [#goods-received-notes] When a delivery arrives, click **Goods received note**. Enter the **Date received**, the supplier's **Delivery note number** and how many you're **Receiving now** on each line. Partial deliveries are fine: the order shows what's still **To come**. Each goods received note puts its stock on the shelf at the order price, against a **Goods received not invoiced** account in the books. The order lists its goods received notes, and the **Not invoiced** report shows everything received that no supplier invoice covers yet. **Goods received**, in the sidebar, lists every goods received note (GRN-0001 and on): the supplier, date, delivery note number, the purchase order it was received against, and whether it's **Not invoiced** or **Invoiced**. ### Receiving without an order [#receiving-without-an-order] When a delivery arrives that nobody ordered in Looped, click **Receive stock** on **Goods received** (or **Receive without an order** on **Purchase orders**, or **Receive stock** on **Stock movements**). Choose the **Supplier**, then add the items by searching or scanning them: each scan adds one. Enter how many arrived and the **Unit cost** excluding VAT, which starts at the last price you paid that supplier, else the item's average cost. Add the supplier's **Delivery note number** and the date, check what's about to change, and save. It works like a delivery against an order: the stock goes on the shelf straight away, against **Goods received not invoiced**, and the GRN shows **Received without an order**. Anyone who can receive purchase orders can do this. ## The supplier invoice [#the-supplier-invoice] Choose **Create supplier invoice** in the ⋮ menu. It opens a supplier invoice in Financials, filled with what has arrived and isn't invoiced yet, at the order price. Approving it settles the price: no stock moves a second time, and any difference from the order price is corrected on the stock received. The order shows what's been billed. For a goods received note without an order, click **Create supplier invoice** on the GRN itself. It works the same way: the invoice is filled with what the GRN received at its unit cost, and approving it corrects the cost without moving stock again. Stock you buy with neither a purchase order nor a goods received note comes in when its supplier invoice is approved in Financials. **Record a purchase**, on **Items** and on an item's page, opens a new supplier invoice for it. ## History [#history] Every order has a history of who created, edited, sent, cancelled or received against it. # Prices and client price lists (/inventory/prices) Every item has its own **selling price**. Price levels add other tiers, such as Trade or Retail, for clients who pay something else. All prices are excluding VAT. ## Price levels [#price-levels] **Price levels** are under **Settings**. Click **New price level**, name it and, if you like, give it a **Rule for unpriced items**: | Rule | Works out the price from | | ---------------------------- | --------------------------------------------------- | | **No rule** | Nothing: unpriced items use their own selling price | | **Based on cost** | The item's cost | | **Based on selling price** | The item's own selling price | | **Based on** *another level* | That level's price | Then choose **Plus** or **Less** and a **Percent**, so a rule reads like "Based on cost plus 30%". A rule only prices items you haven't priced on the level: a price set on the item always wins. Levels you no longer use can be archived and restored. In Invoices, link a client or a client category to a level; see [Client prices](/invoices/clients#prices-for-a-client). ## Edit prices by level [#edit-prices-by-level] **Edit prices by level**, from **Items**, shows every item's price on one level, with its **Margin**. Pick the level, type prices in, and save. Items left blank follow the level's rule, or their own selling price. Tick **Show unpriced items** to price items that have nothing on the level yet. One item's prices on every level are on its page, under **Prices by level**. ## Dated prices and scheduled changes [#dated-prices-and-scheduled-changes] Under the level's prices, **Dated prices** holds specials and price changes with dates. Choose **Add dated price**, pick the item, type the price and a **From** date. Leave **To** blank for a change that stays; give it an end date for a special, and the usual price comes back the day after. A quote or invoice uses the price in effect on its date. A price that starts after today shows as **Scheduled**: nothing changes until that day. To change an item's own selling price from a date, schedule it on the **Default** level. Looped makes that level the first time it's needed, and a price on it in effect on a document's date takes the place of the item's sale price. ## Client price lists [#client-price-lists] **Client price lists**, under **Reporting**, are printable price lists to send to a client or a prospect. They print the prices you set on items; they don't change them. To make one, click **New client price list** and choose: * Who it's **Prepared for**: a client, or **No client** for a prospect or anyone. * The **Price level**, or **Items' own sale prices**. * What's on it: categories, items matching a search, sort order and columns. * The **Title**, **Effective** and **Valid until** dates, a message and terms. It's made from the live catalogue at today's prices, as a **Draft** you can adjust before it goes out: add headings and one-off lines, mark specials, reword a line, or set a line to **On request**. **Refresh prices** brings it back in line with the catalogue. Save your choices as a **Saved setup** to make the same kind of list again. Preview, print or download it as a PDF, export it as CSV, or email it. The list shows when it was **Last sent** and to whom. You can also start a client price list from the client's page in Invoices. # Reports and audit trail (/inventory/reports) ## Reports [#reports] **Reports** lists every report, worked out from your stock movements. Search it, and use **Display as** to switch between **Cards** and **Table**. | Group | Report | What it shows | | -------------- | ----------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ | | **Stock** | **Stock on hand** | What you hold and what it's worth, on any day | | | **Stock movements** | Every movement, by item, type and dates, with a running balance for one item | | | **Slow movers** | Items on hand that haven't sold in a while | | | **Write-offs** | Write-offs and stock-take variances, by reason | | | **ABC analysis** | Which items carry most of your stock value | | **Purchasing** | **Reorder** | Items at or below their reorder level, by supplier, with how many to order (at least the supplier's minimum order) | | | **Open orders** | Sales orders still to ship and purchase orders still to arrive, with back orders and late deliveries | | | **Not invoiced** | Goods received that no supplier invoice covers yet | | | **Purchases by supplier**, **Purchases by item**, **Purchase price history** | What you bought, from whom and at what price | | **Sales** | **Sales by item**, **Sales by client**, **Sales by client category**, **Sales by sales code**, **Sales by month** | Revenue, cost and margin from invoices with items on them | The **Reorder** report can **Create purchase orders**: one draft per usual supplier, at each item's last purchase price. ### The daily reorder digest [#the-daily-reorder-digest] Once a day, from 07:00, Inventory sends one message listing what needs ordering, such as "4 items need ordering": each item with what's on hand, its reorder level, how many to order and its usual supplier, and a link to the reorder report. Items already on order enough are left off, and nothing is sent on a day when nothing needs ordering. Choose who gets it under **Items to reorder** in Manage › Settings › Notifications; each person picks push, email or both in their profile. ### Views, comparisons and exports [#views-comparisons-and-exports] On the sales and purchase reports, choose the **Period**, **Group by** and columns, and **Compare with** **The period before** or **The same period last year** to add what each row, subtotal and total came to then and the change. **Save this view** keeps your choices under a name, listed under **Saved views**. Tick **Only me** to keep a view to yourself; it shows as "(only you)" and nobody else sees it. A saved view can be emailed **Every Monday** or **On the 1st of each month** to people in the company, and to addresses outside it, such as a rep or your accountant: type them under **Outside the company** and confirm they may get it. Cost and margin go to people in the company only when whoever scheduled it can see costs, and never to outside addresses, which also get no link into Looped. Every report has the same export group: **Preview** (to print), **Export CSV** and **Export PDF**. ## Audit trail [#audit-trail] The **Audit trail**, under **Settings**, shows who changed items, prices, price levels and purchase orders, and when, newest first. Stock takes, adjustments and opening stock are in it too, and so are changes made by a data migration or by Looped itself. Search by SKU, item, order number or supplier, filter by type, person and date, and export it as CSV or PDF. It needs **See the audit trail**, which Inventory Admin and Stock Controller have. # Looped Pay (/pay) When you send an invoice from [Looped Invoices](/invoices/getting-started), the email contains a unique **pay link** that takes the recipient to Looped Pay. They don't need a Looped account; the link itself is the credential. Pay lives at `pay.looped.sh/`. Each link is tied to a single invoice. ## What the recipient sees [#what-the-recipient-sees] * **Your branding** — logo and company name from your [company settings](/team-settings) * **The invoice** — line items, totals, currency * **Payment methods** — whichever payment integrations you've enabled (Stripe, Yoco, PayFast) * A **Download Invoice** button so they can save the PDF * After payment: a **"Paid"** badge replaces the payment buttons If you have no payment integrations connected and no bank details on file, the page just shows the invoice — your client falls back to whatever payment arrangement you have offline. ## The payment flow [#the-payment-flow] 1. Client clicks **Pay now**. 2. They're redirected to the chosen provider's hosted checkout (Stripe / Yoco / PayFast). 3. They enter card details and pay. 4. Provider redirects them back to the Pay page. 5. Provider sends a webhook to Looped → invoice flips to `PAID`. The Pay page polls the invoice's status when it loads, so a returning client sees the new `Paid` state immediately. ## Statuses the recipient might see [#statuses-the-recipient-might-see] | Status | What it means for them | | -------------- | ------------------------------------------------------------ | | `PENDING` | Default — payment buttons visible | | `PAID` | Done. Payment buttons hidden, "Paid" badge shown | | `PAID_PARTIAL` | Partial payment recorded — they'll see the remaining balance | | `OVERDUE` | Past due — payment buttons still work; this is cosmetic | ## Privacy [#privacy] The pay link is public — anyone with it can view and pay the invoice. There's no sign-in. The link contains a CUID2-format invoice id which is unguessable in practice, but treat it the same way you'd treat a payment slip: don't post it on social media, and if you sent it to the wrong person, **delete the invoice** ([Sending invoices](/invoices/sending-invoices)) so the link stops loading. ## Refunds [#refunds] Looped does **not** issue refunds. Refunds are processed from your payment provider's dashboard: * Stripe → [dashboard.stripe.com](https://dashboard.stripe.com) → invoice → Refund * Yoco → Yoco Business portal * PayFast → PayFast merchant portal After issuing a refund, you can [mark the invoice paid manually](/invoices/sending-invoices#recording-a-payment) again or [delete it](/invoices/sending-invoices#deleting-an-invoice) — Looped doesn't auto-revert payment status when a provider issues a refund. ## What's *not* on the Pay page [#whats-not-on-the-pay-page] * No account, no login, no order history. * No saved cards (Stripe handles this on its own checkout, not on Pay itself). * No installments / payment plans. * No support chat. (If a client has questions, they need to contact you directly.) The page is intentionally minimal — its job is to let your client pay quickly and get out of the way. # What Looped posts (/what-looped-posts) A lot of what lands in your books isn't typed in as a journal. You issue an invoice, record a payment, finalise a pay run or count stock, and Looped posts the double entry to Financials for you. These pages list every one of those journals, so you and your accountant can see exactly what each action does to the ledger. ## How to read the tables [#how-to-read-the-tables] Each journal is a small table of accounts with the debit and credit sides. Amounts are written as what they stand for ("the invoice total", "net pay") so the table holds for any invoice or pay run. | Account | Debit | Credit | | --------------- | ------------: | ---------: | | Debtors control | invoice total | | | Sales | | net amount | | VAT Output | | VAT | ## System accounts are found by their role [#system-accounts-are-found-by-their-role] The accounts in these tables are system accounts. Each one carries a role (Debtors control, VAT Output, Cash on Hand and so on), and Looped finds it by that role when it posts. This means that you can rename or renumber a system account and Looped keeps posting to it. The tables use the default South African names; your chart might call them something else, and in Austria or the Czech Republic they sit on different codes. System accounts are locked against archiving and deleting, because a journal would have nowhere to go. You'll see a lock icon next to them on the chart of accounts. ## Dates and corrections [#dates-and-corrections] A journal is dated on the business date of what caused it: the invoice's issue date, the day a payment was received, the pay date, the day stock moved. It's never dated on the day someone clicked the button. Looped doesn't edit a posted journal. When you undo something, such as reversing a payment or voiding a supplier invoice, Looped posts a reversal: the same lines with debit and credit swapped. Both journals stay in the ledger, so the history is there for an audit. ## Where to find each one [#where-to-find-each-one] * [Invoices](/what-looped-posts/invoices/) for invoices, credit notes, payments, refunds, write-offs and foreign currency. * [Cash](/what-looped-posts/cash/) for cash payments, the cash count and petty cash. * [Bank statements](/what-looped-posts/bank-statements/) for approving and matching statement lines. * [Suppliers and expense receipts](/what-looped-posts/suppliers-and-receipts/) for supplier invoices, their payments and credit notes, and receipts. * [Payroll](/what-looped-posts/payroll/) for pay runs, net pay and the EMP201. * [Inventory](/what-looped-posts/inventory/) for opening stock, sales, returns, adjustments and goods received. * [Assets, loans and year end](/what-looped-posts/assets-loans-and-year-end/) for depreciation, disposals, loan interest, revaluation, deferred tax and closing the year. # Invoices (/what-looped-posts/invoices) Every invoice in Looped Invoices is in the books from the moment it's issued. Paying it, crediting it or writing it off then moves the balance on Debtors control, so what Financials says a client owes always matches Invoices. ## Issuing an invoice [#issuing-an-invoice] Issuing posts the whole invoice on its issue date. Sales gets one line per VAT treatment on the invoice, and VAT Output gets the VAT on the standard-rated part. | Account | Debit | Credit | | --------------- | ------------: | -----------------: | | Debtors control | invoice total | | | Sales | | standard-rated net | | VAT Output | | VAT | | Sales | | zero-rated net | | Sales | | exempt net | Lines that don't apply are left out, so an invoice with only standard-rated lines has three lines. If the VAT split doesn't add up to the total, for example a discount taken after VAT, the difference goes to Sales with no VAT so the journal still balances to what the client owes. VAT is counted here, on the invoice date. Looped works on the invoice basis, so a payment later doesn't post VAT again. We don't support the payments basis yet. ## Issuing a credit note [#issuing-a-credit-note] A credit note is the invoice's journal turned around, dated on the credit note. | Account | Debit | Credit | | --------------- | ------------------------------: | ----------------: | | Sales | net credited, per VAT treatment | | | VAT Output | VAT credited | | | Debtors control | | credit note total | ## Recording a payment [#recording-a-payment] A payment clears what the client owes and puts the money in the account it was paid into, dated the day it was received. | Account | Debit | Credit | | --------------- | ------------------: | ----------: | | Bank | amount less any fee | | | Bank Charges | gateway fee | | | Debtors control | | amount paid | Bank is the account set for the payment's method under **Settings › General › Where payments land**, else the invoice's own bank account. A Cash payment set to land in Cash on Hand posts there instead (see [Cash](/what-looped-posts/cash/)). The fee line only appears for a gateway payment that settled net of its fee, such as Yoco, Stripe or PayFast. That fee is posted with no VAT today, which means a VAT-registered company doesn't claim the VAT in a Yoco or PayFast fee. We're fixing that. Reversing a payment posts its reversal, which puts the amount back on Debtors control. ## Refunding a client [#refunding-a-client] A refund paid out to a client is a payment the other way round, dated the day it was paid. | Account | Debit | Credit | | --------------- | -----: | -----: | | Debtors control | refund | | | Bank | | refund | ## Writing off an invoice [#writing-off-an-invoice] Writing off a debt you won't collect moves it to Bad Debts. When the invoice carried VAT, the VAT share of what's written off goes back to VAT Output instead of the expense, because the VAT Act lets you claim back the output VAT on a debt that can't be recovered. | Account | Debit | Credit | | --------------- | -------------------------------: | -----------------: | | Bad Debts | amount written off, less its VAT | | | VAT Output | the VAT share | | | Debtors control | | amount written off | ## Invoices in another currency [#invoices-in-another-currency] An invoice in USD or EUR posts in rand, converted at the rate it was booked at. The Debtors control line also keeps the foreign amount, so Financials knows the client owes USD 400 as well as the rand value. The payment is where the exchange rate moves. Debtors control is cleared at the invoice's booked rate, the bank gets the amount at the payment date's rate, and the difference is a realised gain or loss. | Account | Debit | Credit | | ----------------------- | --------------------------------: | ----------------------------------: | | Bank | amount at the payment date's rate | | | Debtors control | | amount at the invoice's booked rate | | Realised FX (Gain)/Loss | loss | gain | The bank's own conversion rarely lands on Looped's rate to the cent. When the bank statement line comes in a little different, matching it posts that last difference to Realised FX too (see [Bank statements](/what-looped-posts/bank-statements/)). # Cash (/what-looped-posts/cash) Cash moves through two accounts in Looped. Cash on Hand holds cash received against invoices until it's banked, and Petty Cash holds the float you pay small expenses from. ## A cash payment on an invoice [#a-cash-payment-on-an-invoice] With **Cash** set to land in Cash on Hand under **Settings › General › Where payments land**, a cash payment posts on the day it was received: | Account | Debit | Credit | | --------------- | ----------: | ----------: | | Cash on Hand | amount paid | | | Debtors control | | amount paid | The amount includes VAT, because it's the cash the client handed over. The VAT itself was counted when the invoice was issued. ## Counting the cash [#counting-the-cash] On the **Cash count** page you enter what you counted for a day. When it matches what was recorded, nothing posts. When it doesn't, the difference goes to Cash Over/Short, dated that day. Short, where you counted less than was recorded: | Account | Debit | Credit | | --------------- | ------------: | ------------: | | Cash Over/Short | the shortfall | | | Cash on Hand | | the shortfall | Over, where you counted more: | Account | Debit | Credit | | --------------- | ----------: | ----------: | | Cash on Hand | the surplus | | | Cash Over/Short | | the surplus | ## Banking the cash [#banking-the-cash] **Bank the cash** moves what you counted from Cash on Hand to the bank account you picked, dated the day you banked it. | Account | Debit | Credit | | ------------ | -------------: | -------------: | | Bank | amount counted | | | Cash on Hand | | amount counted | The deposit then shows up on your bank statement. We don't match that deposit line to this journal yet, so categorise it to Cash on Hand when you review it. If you approve it to Sales or Debtors, the cash is counted twice. ## Paying from petty cash [#paying-from-petty-cash] An expense receipt paid from petty cash posts as soon as you confirm it, dated on the slip. | Account | Debit | Credit | | ------------------- | ---------------: | ---------: | | The expense account | amount, less VAT | | | VAT Input | VAT | | | Petty Cash | | slip total | VAT Input only appears when the company is VAT registered and the receipt's VAT code is standard-rated. The VAT is worked out from the code's rate today, which can differ from the VAT printed on a slip that mixes zero-rated items. Check the VAT on those before you confirm. Topping up the float is a bank statement line you categorise to Petty Cash, which posts Dr Petty Cash / Cr Bank. The Petty Cash ledger is your petty cash book. # Bank statements (/what-looped-posts/bank-statements) Uploading and categorising a statement posts nothing. Each line only reaches the books when you approve it or confirm a match on the review screen. ## Approving a line to an account [#approving-a-line-to-an-account] Approving a line posts it against the account you chose, dated the line. Money out: | Account | Debit | Credit | | --------------------- | ---------------: | ----------: | | The account you chose | amount, less VAT | | | VAT Input | VAT | | | Bank | | line amount | Money in is the same the other way round, with VAT Output for a standard-rated line. VAT only splits out when the line's VAT code is standard-rated and the company is registered on the line's date. ## Matching a payment already in the books [#matching-a-payment-already-in-the-books] A money-in line that's a payment you recorded in Invoices is offered as **Matches INV-…**. Confirming links the line to the payment's journal and posts nothing new, because the payment already put the money in the bank. Approving the line to Sales or Debtors instead would count the income twice. When the payment was in another currency, the bank's rand amount can land a few rand off what Looped recorded. A line within 3% of the recorded amount is still offered, with the difference shown. Confirming it posts that difference, dated the line, so the bank account agrees with the statement. | Account | Debit | Credit | | ----------------------- | -------------: | -------------: | | Realised FX (Gain)/Loss | bank paid less | | | Bank | | bank paid less | When the bank paid more, the lines swap. ## Paying a supplier invoice [#paying-a-supplier-invoice] A money-out line that pays an approved supplier invoice posts the payment against Creditors control. See [Suppliers and expense receipts](/what-looped-posts/suppliers-and-receipts/). ## Paying salaries and the EMP201 [#paying-salaries-and-the-emp201] A salary payment or the SARS payment for an EMP201 clears what payroll owes. See [Payroll](/what-looped-posts/payroll/). ## Fixing a line approved to the wrong account [#fixing-a-line-approved-to-the-wrong-account] Reclassifying a posted line reverses its journal on the line's date and posts it again to the new account. The line stays linked throughout, so you don't need a correcting journal. The one exception is a line in a closed year, which needs an adjusting journal in the open year. # Suppliers and expense receipts (/what-looped-posts/suppliers-and-receipts) A supplier invoice is something you owe and pay later, so it goes through Creditors control. An expense receipt is a slip you paid on the spot, so it posts straight to where the money came from. ## Approving a supplier invoice [#approving-a-supplier-invoice] Approving posts the supplier invoice on its date, one debit per line. | Account | Debit | Credit | | ------------------- | --------------------------: | ------------: | | Each line's account | line amount, less VAT | | | VAT Input | VAT on standard-rated lines | | | Creditors control | | invoice total | A line that bills stock already received on a purchase order goes to Goods Received Not Invoiced instead of an expense, because the stock is already on the shelf (see [Inventory](/what-looped-posts/inventory/)). A supplier invoice in another currency converts at its date's rate, and Creditors control keeps the amount owed in that currency. ## Paying supplier invoices [#paying-supplier-invoices] Paying one or more approved supplier invoices posts a single journal, dated the payment. | Account | Debit | Credit | | ----------------- | ----------: | ----------: | | Creditors control | amount paid | | | Bank | | amount paid | When you pay from a bank statement line, the line is posted against this journal and nothing else goes to the bank. For a foreign-currency supplier invoice, a difference between its booked rate and the payment's rate goes to Realised FX. Voiding an approved supplier invoice reverses its journal. A paid one has to have its payment reversed first. ## A supplier credit note [#a-supplier-credit-note] Approving a supplier credit note posts the supplier invoice in reverse. | Account | Debit | Credit | | ------------------- | ----------------: | --------------------: | | Creditors control | credit note total | | | Each line's account | | line amount, less VAT | | VAT Input | | VAT | ## Expense receipts [#expense-receipts] How a receipt posts depends on how it was paid. **Business account or card.** The receipt waits for its bank line. Approving that line posts it with the slip attached: | Account | Debit | Credit | | ------------------- | ---------------: | ---------: | | The expense account | amount, less VAT | | | VAT Input | VAT | | | Bank | | slip total | **Personal card or cash.** It posts when you confirm it, because the business owes you the money: | Account | Debit | Credit | | ------------------- | ---------------: | ---------: | | The expense account | amount, less VAT | | | VAT Input | VAT | | | Director's Loan | | slip total | **Petty cash.** It posts when you confirm it, against Petty Cash. See [Cash](/what-looped-posts/cash/). A receipt keeps one account today, so a slip with stationery and cleaning supplies goes to one expense. Receipts with a line per category are planned. # Payroll (/what-looped-posts/payroll) A finalised pay run posts one journal on the pay date. Paying the salaries and paying SARS later clear the amounts that journal left owing. For more on how the review screen offers these matches, see [Payroll in the books](/financials/payroll/). ## Finalising a pay run [#finalising-a-pay-run] | Account | Debit | Credit | | ------------------------ | ----------------------------------: | --------------------------------------------------------: | | Salaries & Wages | gross pay | | | Employer Contributions | employer UIF, SDL and contributions | | | PAYE Payable | | PAYE | | UIF Payable | | employee and employer UIF | | SDL Payable | | SDL | | Other Payroll Deductions | | other deductions and employer contributions owed to funds | | Salaries Payable | | net pay | Net pay goes to Salaries Payable because on the pay date you owe it to your employees, and it might leave the bank on another day or in several payments. ## Paying salaries [#paying-salaries] Matching a salary payment on the bank statement to its run posts the payment, dated the day it left the bank. | Account | Debit | Credit | | ---------------- | ----------: | ----------: | | Salaries Payable | the payment | | | Bank | | the payment | Several payments can pay one run, and Looped refuses a payment for more than the net pay still owed. Nothing goes to Salaries & Wages again, so the salaries aren't counted twice. ## Paying the EMP201 [#paying-the-emp201] Matching the SARS payment for a month's EMP201 clears the PAYE, UIF and SDL the month's runs owe, dated the payment. | Account | Debit | Credit | | ------------ | ----: | ----------: | | PAYE Payable | PAYE | | | UIF Payable | UIF | | | SDL Payable | SDL | | | Bank | | the payment | # Inventory (/what-looped-posts/inventory) Looped Inventory keeps the value of your stock in Financials. Whenever stock moves, it posts the cost of that movement between Inventory and one other account, dated the day the stock moved. None of these journals carry VAT: cost of sales never reaches the VAT201, and the VAT on buying stock is on the supplier invoice. A movement with many items posts one line pair per account pair, so a stock take with fifty differences posts two lines. A batch that nets to nothing, such as a recount that matched, posts nothing. ## Opening stock [#opening-stock] | Account | Debit | Credit | | ----------------- | -----------: | -----------: | | Inventory | stock's cost | | | Retained Earnings | | stock's cost | ## Selling stock [#selling-stock] When an invoice for stock items is issued, the cost of what left the shelf moves to Cost of Sales. | Account | Debit | Credit | | ------------- | ---------------------: | ---------------------: | | Cost of Sales | cost of the items sold | | | Inventory | | cost of the items sold | A recost, when an item's cost changes after it was sold, posts the difference between the same two accounts. ## Stock returned by a client [#stock-returned-by-a-client] | Account | Debit | Credit | | ------------- | -------------------------: | -------------------------: | | Inventory | cost of the items returned | | | Cost of Sales | | cost of the items returned | ## Adjustments and stock takes [#adjustments-and-stock-takes] A stock take or an adjustment posts the difference between what the books held and what you counted. Found more: | Account | Debit | Credit | | --------------------- | ------------------: | ------------------: | | Inventory | cost of the surplus | | | Inventory Adjustments | | cost of the surplus | Found less: | Account | Debit | Credit | | --------------------- | --------------------: | --------------------: | | Inventory Adjustments | cost of the shortfall | | | Inventory | | cost of the shortfall | ## Goods received before the supplier invoice [#goods-received-before-the-supplier-invoice] Receiving stock on a purchase order before its supplier invoice arrives puts it on the shelf and records that you owe for it. | Account | Debit | Credit | | --------------------------- | ------------: | ------------: | | Inventory | cost received | | | Goods Received Not Invoiced | | cost received | When the supplier invoice is approved, its stock lines go to Goods Received Not Invoiced, which clears it (see [Suppliers and expense receipts](/what-looped-posts/suppliers-and-receipts/)). # Assets, loans and year end (/what-looped-posts/assets-loans-and-year-end) These journals post when you run them in Financials. Each run is dated on the period it covers, and running one twice for the same period doesn't post twice. ## Depreciation [#depreciation] Running depreciation posts the period's charge for each asset. | Account | Debit | Credit | | ------------------------ | ------------------------: | ------------------------: | | Depreciation expense | the period's depreciation | | | Accumulated Depreciation | | the period's depreciation | ## Disposing of an asset [#disposing-of-an-asset] Disposing first brings depreciation up to the disposal date, then takes the asset off the books and books the proceeds. Whatever is left over is a profit or loss on disposal. | Account | Debit | Credit | | -------------------------------- | -------------------------------: | ------------------: | | Accumulated Depreciation | accumulated to the disposal date | | | The account the proceeds went to | proceeds | | | Asset cost | | the asset's cost | | VAT Output | | VAT in the proceeds | | Profit on Disposal | loss | profit | VAT Output only appears when the company was VAT registered on the disposal date. The proceeds you enter include that VAT, and the profit is worked out on the amount without it. ## Loan interest [#loan-interest] Running loan interest posts each loan's interest and fees on the last day of the period. | Account | Debit | Credit | | ---------------- | -------: | ----------------: | | Interest expense | interest | | | Loan fees | fees | | | The loan account | | interest and fees | ## Revaluing foreign currency balances [#revaluing-foreign-currency-balances] At a period end, Looped can restate every foreign-currency balance at that day's closing rate. The difference between the balance at that rate and what the ledger holds goes to Unrealised FX. | Account | Debit | Credit | | ---------------------------- | ----: | -----: | | The foreign-currency account | gain | loss | | Unrealised FX (Gain)/Loss | loss | gain | The revaluation reverses the next day, so the new period starts from the original amounts. ## Deferred tax [#deferred-tax] At year end, Looped works out the deferred tax the company's assets and assessed loss call for and posts the movement needed to bring the balance to that amount, dated on the year end. | Account | Debit | Credit | | -------------------- | ------------------------: | ------------------------: | | Deferred Tax Expense | increase in the liability | decrease | | Deferred Tax | decrease | increase in the liability | Running it again posts only any further movement. Micro-entities on FRS 105 don't recognise deferred tax, so Looped refuses it for them. ## Closing the year [#closing-the-year] Closing a financial year zeroes every income and expense account into Retained Earnings, dated on the last day of the year. | Account | Debit | Credit | | -------------------- | ----------: | ----------: | | Each income account | its balance | | | Each expense account | | its balance | | Retained Earnings | net loss | net profit | A year with no activity posts nothing. Every earlier year has to be closed first. # Looped MCP (/mcp) Looped has an MCP server, so an AI agent can work in your Looped companies for you. You talk to Claude, ChatGPT, Codex or Cursor the way you'd talk to a bookkeeper, and the agent uses Looped's tools to do the work. For example, you can ask it to: * "Log three hours on the Acme website project for yesterday." * "Invoice Acme for everything logged on their project this month, and send it." * "Import this bank statement and propose accounts for every line." * "Capture these four supplier invoices from my downloads folder." * "Who owes us money, and how long has each invoice been outstanding?" * "Draft October's pay run and tell me what changed since September." * "Run month-end for Acme Trading." ## The agent works as you [#the-agent-works-as-you] When you connect a client, you sign in to Looped and approve it. From then on the agent acts as you, with the role and permissions you have in each company. If your role can't approve statement lines in a company, the agent can't either, and every change it makes shows in the audit log under your name. When you belong to more than one company, the agent asks which you mean before it acts. It never carries an action from one company over to another. ## You decide what reaches the books [#you-decide-what-reaches-the-books] An agent prepares work and you decide how far it goes. Ask it to "just show me" and it only reads and drafts. Ask it to "do it" and it does everything that can be undone, then stops and asks before anything that can't be, such as emailing an invoice to a client. Some things, like closing a financial year or filing a return, stay with a person in the Looped web app whatever you ask. [How far the agent goes](/mcp/how-far-it-goes/) has the full list. ## Pages in this section [#pages-in-this-section] * [Connecting an agent](/mcp/connecting/) for setting up each client and the Looped skill. * [How far the agent goes](/mcp/how-far-it-goes/) for what it does on its own, what it asks first and what it never does. * [Playbooks](/mcp/playbooks/) for the step-by-step jobs the agent knows, from onboarding a company to month-end. * [Working well with an agent](/mcp/working-well/) for memories, routines, files and what to do when something goes wrong. # Connecting an agent (/mcp/connecting) Every client connects to the same server: ```text https://api.looped.sh/mcp ``` It's a Streamable HTTP server that signs in with OAuth. The first time your client connects, it opens a Looped sign-in in your browser. You sign in the way you normally do, approve the client, and you're back in your agent. You don't need an API key. The **MCP** page in Manage (under your company settings) has each client's steps ready to copy. It also has a **Copy setup prompt** button: paste that prompt into any agent and it sets itself up, then checks the connection by listing your companies. ## Claude Code [#claude-code] Add the server: ```bash claude mcp add --transport http looped https://api.looped.sh/mcp ``` Then run `/mcp` in Claude Code, pick **looped** and sign in. Install the skill as well (see below). ## Codex [#codex] Add the server, then sign in when Codex asks: ```bash codex mcp add looped --url https://api.looped.sh/mcp ``` ## Claude.ai and the Claude apps [#claudeai-and-the-claude-apps] Open **Settings › Connectors**, add a custom connector, paste the server URL and sign in to Looped. The connector is then available in Claude on the web, desktop and mobile. Claude Duet uses the same connectors. ## ChatGPT [#chatgpt] Open **Plugins**, add a custom MCP server, paste the server URL and sign in to Looped. On a Business or Enterprise workspace, an admin might need to add it for you. OpenAI Dots use the same connection. ## Cursor, VS Code and other clients [#cursor-vs-code-and-other-clients] Add Looped to the client's MCP configuration: ```json { "mcpServers": { "looped": { "type": "http", "url": "https://api.looped.sh/mcp" } } } ``` For agents with their own connector screen, such as Grok, add a custom connector with the server URL and sign in, or send them the setup prompt from the MCP page. ## The Looped skill [#the-looped-skill] The skill is a page of instructions the agent reads before it works in Looped. It covers how Looped's amounts and dates work, which actions need your go-ahead, what the agent must never ask you for, and the [playbooks](/mcp/playbooks/) for longer jobs. Agents make fewer mistakes with it, so install it alongside the server wherever your client supports skills. For Claude Code: ```bash mkdir -p ~/.claude/skills/looped && curl -fsSL https://app.looped.sh/skills/looped/SKILL.md -o ~/.claude/skills/looped/SKILL.md ``` For Codex: ```bash mkdir -p ~/.codex/skills/looped && curl -fsSL https://app.looped.sh/skills/looped/SKILL.md -o ~/.codex/skills/looped/SKILL.md ``` The skill changes as Looped does, so run the command again now and then to pick up the latest. Clients without skills get the essentials from the server itself when they connect. ## Checking it works [#checking-it-works] Ask the agent "Which Looped companies can you see?" It should list every company you belong to. If it can't find any Looped tools, the client isn't connected yet: in Claude Code run `/mcp`, and in other clients check the connector is switched on for the chat you're in. # How far the agent goes (/mcp/how-far-it-goes) You set how far an agent goes each time you ask it for something, in plain words. The agent reads your request for that and follows it. ## Three ways to ask [#three-ways-to-ask] **"Just show me", "draft it" or "don't post anything".** The agent reads, works things out and prepares drafts: invoices, quotes, supplier invoices, receipts, pay runs and proposed accounts on a bank statement. Nothing reaches the books. **"Do it", "run month-end" or no instruction at all.** The agent does everything that can be undone inside Looped, then stops before anything that can't and lists it for you to decide. Things that can be undone include posted journals, approved statement lines, approved and paid supplier invoices, confirmed receipts, depreciation and loan interest runs, issued invoices and recorded payments, time entries and clients. **"Do everything", "send them" or "finalise it".** The agent also takes the steps that can't be undone, but only the ones you named. Whichever way you ask, the agent reads everything first and shows you one plan you can approve in one reply, then carries out all of it. ## What it always asks first [#what-it-always-asks-first] These can't be undone, so the agent names them back to you before it does them: * Sending an invoice, credit note or quote, because it emails the client. * Turning a quote into an invoice. * Processing a pay run. Looped also asks for the confirmed net total. * Finalising the annual financial statements. * Deleting anything, and voiding a supplier invoice. * Disposing of an asset. * Disconnecting an integration or deleting a bank statement upload. * Dismissing a payment that couldn't post. ## What only a person can do [#what-only-a-person-can-do] Some steps stay in the Looped web app however you ask. The agent prepares the work and gives you the link: * Closing or reopening a financial year. * Finalising or reopening a VAT201, and filing any return. * Changing bank account numbers or account holders. * Finalising a pay run that has changes since the last one, or reversing a pay run. * Confirming a payroll take-on, and completing an employee's identity, tax and bank details. ## What it never asks you for [#what-it-never-asks-you-for] The agent doesn't handle identity or bank details. It won't ask for ID or passport numbers, personal tax numbers, dates of birth, employee bank details, bank logins, one-time PINs or integration secrets. Payroll identifiers come back from Looped masked, and stay that way. When Looped refuses something, the agent tells you why and doesn't try to work around it. ## Looped does the accounting [#looped-does-the-accounting] The agent can read files on your computer, such as a bank statement or a folder of supplier invoices, but the accounting happens in Looped. It passes files to Looped as they are and lets Looped convert currencies, work out VAT and keep the balances. When Looped can't do something, the agent says so. To see what each action posts once you agree to it, see [What Looped posts](/what-looped-posts/). # Playbooks (/mcp/playbooks) A playbook is a set of steps the agent follows for a longer job, so it does the job the same way every time and doesn't skip a check. The playbooks come with the [Looped skill](/mcp/connecting/#the-looped-skill), and clients that show MCP prompts also list some of them as prompts you can pick. You don't need to name a playbook. Ask for the job and the agent picks the right one. ## Setting up [#setting-up] **Set up a new company.** Start here with a company that's new to Looped. The agent reads what you give it, such as registration documents or your website, fills in the company details, creates the financial years and the chart of accounts, and lists what's still missing. Try: "Set up Acme Trading in Looped. Its registration certificate is in my downloads folder." **Set up Financials from prior-year statements.** The agent reads last year's financial statements and captures the opening balances from them. **Set up invoicing.** Your company details, bank account, numbering and a first client, ready to send an invoice. **Payroll take-on from Sage.** Moving employees and their year-to-date figures across from Sage Payroll. ## Banking [#banking] **Import a bank statement.** The agent imports the file into the right bank account, checks the statement's opening balance against the ledger, then categorises the lines. Try: "Import the October statement for the FNB cheque account." **Review a bank statement upload.** The agent goes through the proposed accounts, confirms matches to invoices, supplier invoices and payroll you've already recorded, and brings you the lines that need a decision. ## Day to day [#day-to-day] **Capture bills and receipts.** Supplier invoices and slips read into drafts, each with a suggested account and VAT code, for you to check before they post. **Invoice from logged time and chase what is owed.** Turning a period's time into invoices, then finding who's overdue. **Quote, accept and invoice.** A quote from draft to sent, accepted, and on to an invoice or a sales order. ## Period end [#period-end] **Month-end close.** Bank statements reviewed, depreciation and loan interest run, foreign balances revalued, and what's still open listed for you. Try: "Run month-end for October." **Draft a budget from last year.** Next year's budget drafted from last year's actuals and your growth assumptions for each section, shown to you to check, and saved once you confirm. Try: "Draft FY2028's budget: income up 10%, expenses up 6%." **VAT201 and provisional tax.** The VAT201 prepared for you to check and finalise, and the provisional tax estimate. **Year-end and the AFS pack.** Year-end adjustments, deferred tax, the disclosure notes drafted from your figures, and the annual financial statements compiled. **Draft, explain and finalise a pay run.** The month's pay run drafted, with what changed since last month explained, ready for you to finalise. ## At the end of a job [#at-the-end-of-a-job] The agent replies once at the end with what it did, what's still open and any link you need to act on, such as the review screen for a statement or the VAT201 to finalise. # Working well with an agent (/mcp/working-well) ## Memories carry work between conversations [#memories-carry-work-between-conversations] An agent forgets everything when a conversation ends, so Looped keeps memories for it. When you make a decision or leave something open, such as "PAYE payments go to Salaries", a question for your accountant or a statement you haven't imported yet, the agent saves it as a memory in that company. The next conversation reads it, so you don't have to explain it again. You can ask for this directly: "Remember that Automators GmbH invoices are zero-rated." Important decisions and open items are pinned, which means every later conversation sees them straight away. When an item is settled, ask the agent to update or remove the memory. ## Routines run a prompt on a schedule [#routines-run-a-prompt-on-a-schedule] A routine is a plain-language prompt that runs on a schedule with the same tools, such as "every Monday, list overdue invoices for Acme Trading". The agent confirms the schedule and the exact prompt with you before it creates one, and you can pause or remove it later. ## Files and links [#files-and-links] The agent can read files on your computer and hand them to Looped: a bank statement, a supplier invoice to capture or a document to attach to a record. For a file it can't read directly, it gives you a short command to upload it. PDFs, statements and exports come back as links that expire after 15 minutes. If one has expired, ask the agent for it again and it fetches a fresh link. ## Amounts and dates [#amounts-and-dates] Most of the time you won't notice this, but it helps when you read the agent's working. Looped's tools take dates as `YYYY-MM-DD` in UTC and durations in seconds. Amounts in Financials, Payroll and invoice payments are in cents, so R1,250.00 is `125000`. Invoice line items and project rates are in rand or the invoice's currency, so the same amount there is `1250`. ## When something goes wrong [#when-something-goes-wrong] **The agent did something in the wrong company.** Ask it to undo it. Looped reverses a posted journal instead of editing it, so both stay in the ledger. Then tell it which company you meant, and consider asking it to save that as a memory. **A line went to the wrong account.** Ask the agent to reclassify it. That reverses the posting on the line's date and posts it again to the right account. **The agent says a payment or invoice isn't in the books.** Ask it to check `setup_status`, which lists postings that couldn't go through and why, such as a missing bank account. **The agent can't see Looped at all.** The client isn't connected for this chat. See [Checking it works](/mcp/connecting/#checking-it-works). **The agent is asking for something it shouldn't.** It should never ask for ID numbers, bank details or logins. If it does, don't give them, and let us know. ## What agents can't do yet [#what-agents-cant-do-yet] Agents can't connect an integration such as Yoco or Google Calendar; a person does that in Manage. They also can't do the steps listed under [What only a person can do](/mcp/how-far-it-goes/#what-only-a-person-can-do). # Public API (/api) Looped's public API is the same surface the apps and the [CLI](/cli/) use, exposed for external integrations. It lives at **[api.looped.sh](https://api.looped.sh)**. That URL renders the **interactive reference**: every endpoint, every parameter, every response shape, with a "Try it" panel you can run live calls from. For machine consumption, the OpenAPI spec is at **[api.looped.sh/openapi.json](https://api.looped.sh/openapi.json)**. Drop it into Postman, Bruno, or your codegen of choice. ## Authenticating [#authenticating] There are two ways in. Pick the first unless you are building something that signs in as a person. ### API key [#api-key] Generate a key from your company's [API keys page](/manage/api-keys) and send it in the `X-API-Key` header: ```bash curl https://api.looped.sh/v1/invoices \ -H "X-API-Key: looped_..." ``` The key carries the company scope, so you don't pass `teamId` separately. Each key also carries a set of **permissions**, such as `track:time.write` or `invoices:invoices.read`, picked when the key was made. See [API keys](/manage/api-keys/#permissions). ### Bearer token (sign in as a person) [#bearer-token-sign-in-as-a-person] A client that signs a person in through Looped's login, like the CLI does, sends their access token in `Authorization: Bearer ` plus an `x-team-id` header naming the company. The request then has that person's permissions in that company. `GET /v1/auth/teams` lists the companies the token's user belongs to. It is the one endpoint that takes a Bearer token without `x-team-id`, so a client can let the person pick a company first. ### Checking a key [#checking-a-key] `GET /v1/whoami` returns the key's user, company and permissions. Any valid key can call it, so it's the quickest way to prove a key works end to end. ## Status codes [#status-codes] | Status | Cause | | ------------- | ----------------------------------------------------------------------------------------------------------- | | `200` / `201` | Success | | `400` | Validation error. The body explains the offending field | | `401` | Missing, invalid, expired or revoked credentials | | `403` | Credentials are valid but don't include the permission this endpoint needs. The body names it in `required` | | `404` | Resource not found, or it belongs to a different company | | `409` | Conflict, such as deleting something that is still in use. The body says what is in the way | ## Endpoint surface (high-level) [#endpoint-surface-high-level] | Path prefix | Resource | | -------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------- | | `/v1/invoices` | Invoices: create, update, issue, send, mark paid, credit notes and refunds, PDFs | | `/v1/invoices/quotes` | Quotes: create, send, accept or decline, convert to an invoice, PDFs | | `/v1/invoices/clients` | Clients, the "billed to" side of invoices and quotes | | `/v1/invoices/statements` | Client statements | | `/v1/invoices/dashboard` | Invoicing totals for the dashboard | | `/v1/invoices/history`, `/v1/invoices/archives` | Archived years, and read-only documents from a closed financial year | | `/v1/track/time` | Time entries | | `/v1/track/projects` | Projects | | `/v1/track/sections` | Sections within a project | | `/v1/track/tags` | Tags on time entries | | `/v1/track/todos` | Todos | | `/v1/track/reports` | Saved reports, and running a report on demand | | `/v1/track/dashboard` | Today's and this week's time, for the dashboard | | `/v1/track/preferences` | The signed-in person's Track preferences | | `/v1/financials/accounts`, `/v1/financials/journal-entries` | Chart of accounts and the general journal | | `/v1/financials/imports`, `/v1/financials/statement-lines` | Bank statement uploads, categorisation and bank rules | | `/v1/financials/suppliers`, `/v1/financials/bills`, `/v1/financials/receipts` | Supplier invoices, supplier returns and expense receipts | | `/v1/financials/customers`, `/v1/financials/ar` | Customer balances, statements and aged receivables | | `/v1/financials/assets`, `/v1/financials/loans`, `/v1/financials/exchange-rates` | Fixed assets, loans and foreign currency | | `/v1/financials/reports`, `/v1/financials/exports` | Trial balance, income statement, balance sheet, cash flow, general ledger and their CSV and Excel exports | | `/v1/financials/afs`, `/v1/financials/notes` | Annual financial statements and their notes | | `/v1/financials/vat`, `/v1/financials/filings`, `/v1/financials/tax` | VAT201 returns, filing deadlines, income and deferred tax | | `/v1/inventory/items`, `/v1/inventory/stock-takes`, `/v1/inventory/adjustments` | Items, stock takes, write-offs and opening stock | | `/v1/inventory/purchase-orders` | Purchase orders, deliveries and reorder drafts | | `/v1/inventory/price-lists`, `/v1/inventory/price-list-documents` | Price levels, client prices and customer-facing price lists | | `/v1/inventory/reports`, `/v1/inventory/dashboard` | Stock on hand, movements, slow movers and the dashboard | | `/v1/team` | Members, invites, company settings, address and bank details | | `/v1/api-keys` | List, create and revoke API keys | | `/v1/whoami` | The current credentials' user, company and permissions | Payroll isn't in the public API yet. The exact list and response shapes are authoritative in [the live reference](https://api.looped.sh). ## Response shapes [#response-shapes] **Track** endpoints answer with one envelope. Success is `{ data, pagination? }`, where `pagination` carries `page`, `limit`, `total`, `totalPages`, `hasNextPage` and `hasPreviousPage` on list endpoints. Errors are `{ error: { code, message, details? } }`, with a machine-readable `code` such as `not_found`, `forbidden` or `validation_error`. **Invoices**, **Financials**, **Inventory** and **Team** endpoints return the resource directly. Lists are paged with `page` and `limit` and report `total`, `totalPages` and `hasMore`. Errors are `{ error, code }` with a sentence you can show and a code to branch on. Financials and Inventory validate the body themselves, so a `400` names the offending field in `details`. Amounts on invoices are in integer cents of the company's currency. Dates go in as `YYYY-MM-DD` and durations in seconds. ## Idempotency [#idempotency] Mutating endpoints (POST/PATCH/DELETE) are not idempotent. If a workflow might retry, dedupe on your side or use a deterministic id pattern in your application logic. ## MCP server [#mcp-server] AI agents don't need the REST API. Looped hosts an [MCP](https://modelcontextprotocol.io) server at `https://api.looped.sh/mcp` that exposes the same data as tools. Claude, ChatGPT, Cursor and any other MCP client can connect to it, sign in as you through OAuth, and act with your permissions in every company you belong to. An API key in `X-API-Key` works there too. Set it up from *Settings* → *MCP server* in Manage, which has the connect command for each client and an agent skill that teaches the assistant how to work in Looped. To set up a new company, ask your agent to run the `onboard-company` prompt (or just say you're new to Looped). It checks what's missing, asks a few questions, reads your registration certificate, VAT letter or last year's financial statements, and fills in the company's details before moving on to bank statements and invoicing. ## SDKs [#sdks] We don't ship official SDKs yet. The [CLI](/cli/) covers Track, Invoices and company admin from a terminal. For code, generate a client for your language from the OpenAPI spec with `openapi-generator` or a similar tool. ## Where to go next [#where-to-go-next] * Browse the [interactive reference](https://api.looped.sh) * [Create your first key](/manage/api-keys#creating-a-key) * Read the [OpenAPI spec](https://api.looped.sh/openapi.json) * Use the [CLI](/cli/) instead of writing a client # Looped CLI (/cli) The Looped CLI is a command-line tool called `looped`. It lets you log time, manage todos and projects, create and send invoices and quotes, and run company admin tasks from your terminal, without opening the apps. It talks to the same [public API](/api/) as any other integration, at `https://api.looped.sh`. You sign in as yourself, so the CLI can do exactly what your role lets you do in the apps, no more. The CLI covers three apps: | Command | App | | ----------------- | -------------------------------------------------------------------------------------------- | | `looped track` | Time entries, the timer, projects, sections, tags, todos, preferences, dashboard and reports | | `looped invoices` | Invoices, quotes, clients, statements and the invoice dashboard | | `looped manage` | Team members, invites, company settings, address, bank details and API keys | Financials and Payroll aren't in the CLI. See the [command reference](/cli/commands) for every command and flag. ## Installing [#installing] The CLI isn't published to npm, Homebrew or as a downloadable binary yet. For now it's built from source in the Looped monorepo, which needs Node.js and pnpm. From a checkout of the monorepo, with dependencies installed (`pnpm install`): ```bash pnpm --filter @looped/cli build node apps/cli/dist/index.js --help ``` The build writes the `looped` entry point to `apps/cli/dist/index.js`. To call it as `looped` from anywhere, link the package onto your path: ```bash cd apps/cli pnpm link --global looped --version ``` The examples in these docs use `looped`. If you didn't link it, use `node apps/cli/dist/index.js` in its place. ## Signing in [#signing-in] ```bash looped login ``` This opens your browser at Looped's sign-in page. Sign in with your normal Looped account. When you're done, the browser shows "Login successful" and you can close the tab. If the browser doesn't open by itself, the CLI prints the sign-in URL. Copy it into a browser on the same machine. A few things to know: * The CLI listens for the browser's reply on `http://127.0.0.1:8952`. If something else is using port 8952, `looped login` stops with an error. Close whatever holds the port and try again. * You have 5 minutes to finish signing in. After that, run `looped login` again. * Your session refreshes itself in the background. If it can't (for example, after a long time away), commands fail with an authentication error and you run `looped login` again. The CLI doesn't sign in with [API keys](/manage/api-keys). For scripts and CI jobs that need a key, call the [public API](/api/) directly. ## Choosing a company [#choosing-a-company] Everything in Looped belongs to a company, and the CLI works with one company at a time. After you sign in, the CLI lists your companies and your role in each: ```text Which company do you want to use? 1) Acme Studio (OWNER) 2) Personal (OWNER) Enter a number (1-2): ``` Type the number and press Enter. If you only belong to one company, the CLI picks it without asking. To switch companies, run `looped login` again and pick a different one. There's no separate command for switching. To check who you're signed in as and which company is selected: ```bash looped whoami ``` ```text User: Company: Key: bearer-token Scopes: track:time.read, track:time.write, invoices:invoices.read, ... ``` `Key` always reads `bearer-token` for a CLI session, because you signed in as yourself rather than with an API key. `Scopes` lists your [permissions](/manage/roles) in Track, Invoices and Manage for the selected company. If a command fails with a permission error, the message names the permission you're missing. Ask an Owner or Admin to change your roles. ## Signing out [#signing-out] ```bash looped logout ``` This removes the saved session from your config file. Any `apiUrl` setting stays. ## Config file [#config-file] The CLI keeps its settings in your home directory: | File | What's in it | | ---------------------------- | ---------------------------------------------------------------- | | `~/.looped/config.json` | Your session (tokens, selected company) and an optional `apiUrl` | | `~/.looped/track-timer.json` | The timer started by `looped track start`, while it's running | Both are plain JSON. `config.json` holds your sign-in tokens, so treat it like a password and don't share or commit it. The CLI talks to `https://api.looped.sh` by default. To point it somewhere else, set `apiUrl` in `config.json` or the `LOOPED_API_URL` environment variable. The environment variable wins if both are set. ```json { "apiUrl": "https://api.looped.sh" } ``` ## Getting help [#getting-help] Every command and command group has built-in help: ```bash looped --help looped track --help looped track todos create --help ``` Print the installed version with: ```bash looped --version ``` ## Output and scripting [#output-and-scripting] Most commands print a table or a short message. Add `--json` to print the API's response as JSON instead, which is easier to pipe into `jq` or a script: ```bash looped invoices list --status OVERDUE --json | jq '.[].serial' ``` When a command fails, the CLI prints a one-line error to stderr and exits with code `1`. ## Where to go next [#where-to-go-next] * [Command reference](/cli/commands) * [Roles & permissions](/manage/roles) * [Public API](/api/) # CLI command reference (/cli/commands) This page lists every command in the [Looped CLI](/cli/). Run any command with `--help` to see the same flags in your terminal. ## Conventions [#conventions] A few rules apply across all commands: * **Ids, not names.** Flags like `--project`, `--client` and `--section` take an id. Each app has a lookup command that shows ids: `looped track projects`, `looped track sections list`, `looped invoices clients`, `looped manage team list`. * **`--json`.** Most commands print a table or a short message. Add `--json` to print the API's response as JSON instead. * **`--confirm`.** Commands that delete something or can't be undone refuse to run without `--confirm`. There's no interactive prompt, so scripts pass `--confirm` too. Without it, nothing is sent to Looped. * **Dates.** Dates are `YYYY-MM-DD` unless a flag says otherwise. * **Comma-separated lists.** Flags that take several values, like `--status PAID,OVERDUE`, take them as one comma-separated value. * **Permissions.** Each command needs the matching permission in your [role](/manage/roles). If you don't have it, the command fails and the error names the permission. ## Account [#account] ### `looped login` [#looped-login] Signs in through your browser and asks which company to use. See [Signing in](/cli/#signing-in). ```bash looped login ``` ### `looped logout` [#looped-logout] Removes your saved session. ```bash looped logout ``` ### `looped whoami` [#looped-whoami] Shows your user id, the selected company's id and your permissions for that company. ```bash looped whoami ``` ## Track [#track] Commands for [Looped Track](/track/). All of them live under `looped track`. ### Time entries [#time-entries] #### `looped track list` [#looped-track-list] Lists your time entries for a day. Without flags, it shows today. | Flag | Description | | ------------------------- | ---------------------------------------------------------- | | `--date ` | The day to list (`YYYY-MM-DD`). Defaults to today | | `--frequency ` | `day`, `week` or `month`. Widens the range around `--date` | | `--project ` | Only show entries for this project | | `--json` | Print JSON | ```bash looped track list --date 2026-09-21 --frequency week ``` #### `looped track start ` [#looped-track-start-taskname] Starts a timer for a new time entry. The entry is created in Looped straight away with a duration of one second, and the CLI remembers it in `~/.looped/track-timer.json` until you stop it. Only one timer can run at a time. | Flag | Description | | ----------------------- | ------------------------------- | | `--project ` | Project to log the time against | | `--section ` | Section to log the time against | | `--description ` | A longer description | | `--json` | Print JSON | ```bash looped track start "Homepage redesign" --project ``` #### `looped track stop` [#looped-track-stop] Stops the running timer and saves the elapsed time on the entry. If the entry was deleted in the web app while the timer ran, `stop` fails but clears the timer so you can start a new one. | Flag | Description | | -------- | ----------- | | `--json` | Print JSON | ```bash looped track stop ``` #### `looped track time get ` [#looped-track-time-get-id] Shows one time entry. | Flag | Description | | -------- | ----------- | | `--json` | Print JSON | ```bash looped track time get ``` #### `looped track time update ` [#looped-track-time-update-id] Changes a time entry. Only the fields you pass change. | Flag | Description | | ----------------------- | ---------------------------------- | | `--task-name ` | New task name | | `--description ` | New description | | `--date ` | New date, as an ISO 8601 date-time | | `--duration ` | New duration, in seconds | | `--project ` | Move the entry to this project | | `--section ` | Move the entry to this section | | `--json` | Print JSON | ```bash looped track time update --duration 5400 ``` #### `looped track time delete ` [#looped-track-time-delete-id] Deletes a time entry. | Flag | Description | | ----------- | ----------- | | `--confirm` | Required | ```bash looped track time delete --confirm ``` ### Projects [#projects] #### `looped track projects` [#looped-track-projects] Lists projects. Use it to find the id to pass to `--project`. | Flag | Description | | ------------------- | ----------------------------------------------------- | | `--status ` | Only show projects with this status, such as `ACTIVE` | | `--search ` | Search by title or code | | `--json` | Print JSON | ```bash looped track projects --status ACTIVE --search website ``` #### `looped track project create ` [#looped-track-project-create-title] Creates a project. The CLI doesn't print the new project's id; run `looped track projects --search "<title>"` to find it. | Flag | Description | | --------------- | --------------------------------------------------- | | `--code <code>` | Project code. Generated for you if you leave it out | ```bash looped track project create "Website refresh" --code WEB ``` #### `looped track project update <id>` [#looped-track-project-update-id] Changes a project's title, code or status. | Flag | Description | | ------------------- | ---------------------------------------------- | | `--title <title>` | New title | | `--code <code>` | New code | | `--status <status>` | `PENDING`, `ACTIVE`, `COMPLETED` or `ARCHIVED` | ```bash looped track project update <projectId> --status COMPLETED ``` #### `looped track project delete <id>` [#looped-track-project-delete-id] Deletes a project. Looped only deletes a project that has no time entries. | Flag | Description | | ----------- | ----------- | | `--confirm` | Required | ```bash looped track project delete <projectId> --confirm ``` ### Sections [#sections] Sections split a [project](/track/projects) into parts. #### `looped track sections list` [#looped-track-sections-list] Lists a project's sections. | Flag | Description | | ----------------------- | --------------------- | | `--project <projectId>` | Required. The project | | `--json` | Print JSON | ```bash looped track sections list --project <projectId> ``` #### `looped track sections create <title>` [#looped-track-sections-create-title] Adds a section to a project. | Flag | Description | | ----------------------- | --------------------- | | `--project <projectId>` | Required. The project | | `--json` | Print JSON | ```bash looped track sections create "Design" --project <projectId> ``` #### `looped track sections update <id> <title>` [#looped-track-sections-update-id-title] Renames a section. | Flag | Description | | -------- | ----------- | | `--json` | Print JSON | ```bash looped track sections update <sectionId> "Discovery" ``` #### `looped track sections delete <id>` [#looped-track-sections-delete-id] Deletes a section. Looped only deletes a section that has no time entries. | Flag | Description | | ----------- | ----------- | | `--confirm` | Required | ```bash looped track sections delete <sectionId> --confirm ``` ### Tags [#tags] See [Tags](/track/tags). #### `looped track tags list` [#looped-track-tags-list] Lists your company's tags. | Flag | Description | | -------- | ----------- | | `--json` | Print JSON | ```bash looped track tags list ``` #### `looped track tags create <title>` [#looped-track-tags-create-title] Creates a tag. | Flag | Description | | -------- | ----------- | | `--json` | Print JSON | ```bash looped track tags create "billable" ``` #### `looped track tags update <id> <title>` [#looped-track-tags-update-id-title] Renames a tag. | Flag | Description | | -------- | ----------- | | `--json` | Print JSON | ```bash looped track tags update <tagId> "non-billable" ``` #### `looped track tags delete <id>` [#looped-track-tags-delete-id] Deletes a tag. Looped only deletes a tag that isn't on any time entries. | Flag | Description | | ----------- | ----------- | | `--confirm` | Required | ```bash looped track tags delete <tagId> --confirm ``` ### Todos [#todos] #### `looped track todos list` [#looped-track-todos-list] Lists todos. | Flag | Description | | ------------------- | ------------------------------------------------- | | `--filter <filter>` | `all`, `active` or `completed`. Defaults to `all` | | `--json` | Print JSON | ```bash looped track todos list --filter active ``` #### `looped track todos create <title>` [#looped-track-todos-create-title] Creates a todo. | Flag | Description | | ----------------------- | ------------------------------- | | `--description <text>` | A longer description | | `--project <projectId>` | Project | | `--section <sectionId>` | Section | | `--priority <priority>` | `P1` (highest) to `P4` (lowest) | | `--due-date <date>` | Due date, ISO 8601 | | `--json` | Print JSON | ```bash looped track todos create "Send wireframes" --priority P1 --due-date 2026-10-01 ``` #### `looped track todos get <id>` [#looped-track-todos-get-id] Shows one todo. | Flag | Description | | -------- | ----------- | | `--json` | Print JSON | ```bash looped track todos get <todoId> ``` #### `looped track todos update <id>` [#looped-track-todos-update-id] Changes a todo. Only the fields you pass change. | Flag | Description | | ----------------------- | ---------------------- | | `--title <title>` | New title | | `--description <text>` | New description | | `--completed` | Mark it done | | `--not-completed` | Mark it not done | | `--project <projectId>` | New project | | `--section <sectionId>` | New section | | `--priority <priority>` | `P1` to `P4` | | `--due-date <date>` | New due date, ISO 8601 | | `--json` | Print JSON | ```bash looped track todos update <todoId> --completed ``` #### `looped track todos delete <id>` [#looped-track-todos-delete-id] Deletes a todo. | Flag | Description | | ----------- | ----------- | | `--confirm` | Required | ```bash looped track todos delete <todoId> --confirm ``` ### Preferences [#preferences] These are your company's Track settings. `get` and `update` always print JSON. #### `looped track preferences get` [#looped-track-preferences-get] Shows the company's time-tracking preferences. ```bash looped track preferences get ``` #### `looped track preferences update` [#looped-track-preferences-update] Changes the company's time-tracking preferences. Only the flags you pass change. | Flag | Description | | ---------------------------------- | ------------------------------------------------------------ | | `--time-unit <unit>` | `HOUR` or `MINUTE` | | `--time-step <n>` | Rounding step in the chosen unit, or `none` to stop rounding | | `--ghost-text` / `--no-ghost-text` | Turn ghost-text suggestions on or off | | `--auto-log` / `--no-auto-log` | Turn logging time when a todo is completed on or off | ```bash looped track preferences update --time-unit MINUTE --time-step 15 ``` ### Dashboard [#dashboard] #### `looped track dashboard` [#looped-track-dashboard] Prints a weekly or monthly time summary as JSON. | Flag | Description | | ------------------- | ---------------------------------------------------------------- | | `--scope <scope>` | `me` or `team`. `team` needs a role that can see everyone's time | | `--period <period>` | `weekly` or `monthly` | | `--week-end <date>` | Any date inside the week or month you want (`YYYY-MM-DD`) | ```bash looped track dashboard --period monthly --week-end 2026-09-15 ``` ### Reports [#reports] Reports are pivot tables of time data, the same ones you build in [Reports](/track/reports). A report's definition (its schema) is JSON with `rows`, `columns`, `values` and `filters`. The easiest way to get one is to build the report in Track, then copy its schema from `looped track reports get <id> --json`. #### `looped track reports list` [#looped-track-reports-list] Lists the saved reports you can see. | Flag | Description | | -------- | ----------- | | `--json` | Print JSON | ```bash looped track reports list ``` #### `looped track reports get <id>` [#looped-track-reports-get-id] Shows one saved report. | Flag | Description | | -------- | ----------- | | `--json` | Print JSON | ```bash looped track reports get <reportId> --json ``` #### `looped track reports run` [#looped-track-reports-run] Runs a report without saving it. Unless your role lets you see everyone's time, the results only include your own time. | Flag | Description | | --------------------- | ---------------------------------------------------------------- | | `--schema <json>` | The full report schema as JSON | | `--rows <fields>` | Comma-separated row fields. Overrides `rows` in `--schema` | | `--columns <fields>` | Comma-separated column fields. Overrides `columns` in `--schema` | | `--start-date <date>` | Start date, ISO 8601 | | `--end-date <date>` | End date, ISO 8601 | | `--json` | Print JSON | ```bash looped track reports run --schema "$(cat report.json)" \ --start-date 2026-09-01 --end-date 2026-09-30 ``` #### `looped track reports save <name>` [#looped-track-reports-save-name] Saves a report definition so you and others can run it again. | Flag | Description | | --------------------------- | ----------------------------------------------------------------- | | `--schema <json>` | Required. The full report schema as JSON | | `--allowed-roles <roles>` | Comma-separated roles that can see it: `OWNER`, `ADMIN`, `MEMBER` | | `--allowed-users <userIds>` | Comma-separated user ids that can see it | | `--json` | Print JSON | ```bash looped track reports save "Hours by project" --schema "$(cat report.json)" \ --allowed-roles OWNER,ADMIN ``` #### `looped track reports update <id>` [#looped-track-reports-update-id] Replaces a saved report's name and schema. Only Owners, Admins and the report's creator can change it. | Flag | Description | | --------------------------- | ---------------------------------------- | | `--name <name>` | Required. The report name | | `--schema <json>` | Required. The full report schema as JSON | | `--allowed-roles <roles>` | Comma-separated roles that can see it | | `--allowed-users <userIds>` | Comma-separated user ids that can see it | | `--json` | Print JSON | ```bash looped track reports update <reportId> --name "Hours by project" \ --schema "$(cat report.json)" ``` #### `looped track reports delete <id>` [#looped-track-reports-delete-id] Deletes a saved report. Only Owners, Admins and the report's creator can delete it. | Flag | Description | | ----------- | ----------- | | `--confirm` | Required | ```bash looped track reports delete <reportId> --confirm ``` ## Invoices [#invoices] Commands for [Looped Invoices](/invoices/getting-started). All of them live under `looped invoices`. Invoice statuses are `PENDING`, `PAID`, `PAID_PARTIAL`, `EXPIRED` and `OVERDUE`. ### Invoices [#invoices-1] #### `looped invoices list` [#looped-invoices-list] Lists invoices. | Flag | Description | | --------------------- | ------------------------------------------------ | | `--status <statuses>` | Comma-separated statuses, such as `PAID,OVERDUE` | | `--client <clientId>` | Only this client's invoices | | `--from <date>` | Issued on or after this date | | `--to <date>` | Issued on or before this date | | `--json` | Print JSON | ```bash looped invoices list --status OVERDUE --from 2026-07-01 ``` #### `looped invoices get <id>` [#looped-invoices-get-id] Shows one invoice. | Flag | Description | | -------- | ----------- | | `--json` | Print JSON | ```bash looped invoices get <invoiceId> ``` #### `looped invoices create` [#looped-invoices-create] Creates an invoice. Invoices have too many fields for one flag each, so you pass the whole invoice as a JSON object, either inline with `--data` or from a file with `--data-file`. Pass one or the other, not both. The invoice needs a `clientId` (or a `client` object) and at least one line item. If the JSON doesn't match what Looped expects, the error says which field is wrong. The [API reference](https://api.looped.sh) lists every field. | Flag | Description | | -------------------- | ------------------------------------ | | `--data <json>` | The invoice as inline JSON | | `--data-file <path>` | Path to a JSON file with the invoice | | `--json` | Print JSON | ```bash looped invoices create --data '{ "clientId": "<clientId>", "lineItems": [{ "description": "Consulting", "unitPrice": 100, "quantity": 5 }] }' ``` #### `looped invoices update <id>` [#looped-invoices-update-id] Changes an invoice. Takes the same `--data` or `--data-file` JSON as `create`. | Flag | Description | | -------------------- | ------------------------------------ | | `--data <json>` | The changes as inline JSON | | `--data-file <path>` | Path to a JSON file with the changes | | `--json` | Print JSON | ```bash looped invoices update <invoiceId> --data-file invoice.json ``` #### `looped invoices delete <id>` [#looped-invoices-delete-id] Permanently deletes an invoice. | Flag | Description | | ----------- | ----------- | | `--confirm` | Required | | `--json` | Print JSON | ```bash looped invoices delete <invoiceId> --confirm ``` #### `looped invoices mark-paid <id>` [#looped-invoices-mark-paid-id] Marks an invoice as paid. | Flag | Description | | -------- | ----------- | | `--json` | Print JSON | ```bash looped invoices mark-paid <invoiceId> ``` #### `looped invoices send <id>` [#looped-invoices-send-id] Emails an invoice to its client. | Flag | Description | | -------- | ----------- | | `--json` | Print JSON | ```bash looped invoices send <invoiceId> ``` #### `looped invoices pdf <id>` [#looped-invoices-pdf-id] Downloads an invoice as a PDF. | Flag | Description | | ----------------- | ------------------------------------------ | | `--output <path>` | Required. Where to save the PDF | | `--download` | Ask the server to send it as an attachment | ```bash looped invoices pdf <invoiceId> --output invoice.pdf ``` #### `looped invoices dashboard` [#looped-invoices-dashboard] Shows a summary of revenue, outstanding invoices and top clients. | Flag | Description | | -------- | ----------------------------- | | `--json` | Print the full dashboard data | ```bash looped invoices dashboard ``` ### Statements [#statements] #### `looped invoices statements` [#looped-invoices-statements] Builds a statement for one client. By default it prints the statement as JSON. For a PDF, a CSV or a Xero-ready CSV, pass `--format` and `--output`. | Flag | Description | | --------------------- | ------------------------------------------------------------ | | `--client <clientId>` | Required. The client | | `--from <date>` | Start of the period. Defaults to the start of the year | | `--to <date>` | End of the period. Defaults to today | | `--status <statuses>` | Comma-separated invoice statuses to include | | `--format <format>` | `json` (default), `pdf`, `csv` or `xero` | | `--output <path>` | Where to save the file. Required unless `--format` is `json` | | `--download` | Ask the server to send it as an attachment | ```bash looped invoices statements --client <clientId> --format pdf --output statement.pdf ``` ### Clients [#clients] See [Clients](/invoices/clients). #### `looped invoices clients` [#looped-invoices-clients] Lists clients. Use it to find the id to pass to `--client`. | Flag | Description | | -------- | ----------- | | `--json` | Print JSON | ```bash looped invoices clients ``` #### `looped invoices client get <id>` [#looped-invoices-client-get-id] Shows one client. | Flag | Description | | -------- | ----------- | | `--json` | Print JSON | ```bash looped invoices client get <clientId> ``` #### `looped invoices client update <id>` [#looped-invoices-client-update-id] Replaces a client's details. This isn't a partial update: the JSON must include at least `name`, `email`, `line1` and `postalCode` every time. | Flag | Description | | -------------------- | ----------------------------------- | | `--data <json>` | The client as inline JSON | | `--data-file <path>` | Path to a JSON file with the client | | `--json` | Print JSON | ```bash looped invoices client update <clientId> --data-file client.json ``` #### `looped invoices client delete <id>` [#looped-invoices-client-delete-id] Permanently deletes a client. | Flag | Description | | ----------- | ----------- | | `--confirm` | Required | | `--json` | Print JSON | ```bash looped invoices client delete <clientId> --confirm ``` ### Quotes [#quotes] All quote commands live under `looped invoices quotes`. Quote statuses are `DRAFT`, `SENT`, `ACCEPTED`, `REJECTED`, `EXPIRED` and `CONVERTED`. #### `looped invoices quotes list` [#looped-invoices-quotes-list] Lists quotes. | Flag | Description | | --------------------- | ------------------------------------------------- | | `--status <statuses>` | Comma-separated statuses, such as `SENT,ACCEPTED` | | `--client <clientId>` | Only this client's quotes | | `--from <date>` | Issued on or after this date | | `--to <date>` | Issued on or before this date | | `--json` | Print JSON | ```bash looped invoices quotes list --status SENT ``` #### `looped invoices quotes get <id>` [#looped-invoices-quotes-get-id] Shows one quote. | Flag | Description | | -------- | ----------- | | `--json` | Print JSON | ```bash looped invoices quotes get <quoteId> ``` #### `looped invoices quotes create` [#looped-invoices-quotes-create] Creates a quote. Like `invoices create`, it takes the whole quote as JSON. | Flag | Description | | -------------------- | ---------------------------------- | | `--data <json>` | The quote as inline JSON | | `--data-file <path>` | Path to a JSON file with the quote | | `--json` | Print JSON | ```bash looped invoices quotes create --data-file quote.json ``` #### `looped invoices quotes update <id>` [#looped-invoices-quotes-update-id] Changes a quote. | Flag | Description | | -------------------- | ------------------------------------ | | `--data <json>` | The changes as inline JSON | | `--data-file <path>` | Path to a JSON file with the changes | | `--json` | Print JSON | ```bash looped invoices quotes update <quoteId> --data-file quote.json ``` #### `looped invoices quotes delete <id>` [#looped-invoices-quotes-delete-id] Permanently deletes a quote. | Flag | Description | | ----------- | ----------- | | `--confirm` | Required | | `--json` | Print JSON | ```bash looped invoices quotes delete <quoteId> --confirm ``` #### `looped invoices quotes send <id>` [#looped-invoices-quotes-send-id] Emails a quote to its client. | Flag | Description | | -------- | ----------- | | `--json` | Print JSON | ```bash looped invoices quotes send <quoteId> ``` #### `looped invoices quotes set-status <id>` [#looped-invoices-quotes-set-status-id] Marks a quote as accepted or rejected. A converted quote can't change status. | Flag | Description | | ------------------- | ---------------------------------- | | `--status <status>` | Required. `ACCEPTED` or `REJECTED` | | `--json` | Print JSON | ```bash looped invoices quotes set-status <quoteId> --status ACCEPTED ``` #### `looped invoices quotes convert <id>` [#looped-invoices-quotes-convert-id] Turns a quote into an invoice. The quote's status becomes `CONVERTED`. | Flag | Description | | -------- | ----------- | | `--json` | Print JSON | ```bash looped invoices quotes convert <quoteId> ``` #### `looped invoices quotes pdf <id>` [#looped-invoices-quotes-pdf-id] Downloads a quote as a PDF. | Flag | Description | | ----------------- | ------------------------------------------ | | `--output <path>` | Required. Where to save the PDF | | `--download` | Ask the server to send it as an attachment | ```bash looped invoices quotes pdf <quoteId> --output quote.pdf ``` ## Manage [#manage] Commands for your company's account. All of them live under `looped manage`. Most need an Owner or Admin; see [Roles & permissions](/manage/roles). ### Members and invites [#members-and-invites] #### `looped manage team list` [#looped-manage-team-list] Lists the company's members. The `ID` column is the member id that `remove` and `change-role` take. | Flag | Description | | -------- | ----------- | | `--json` | Print JSON | ```bash looped manage team list ``` #### `looped manage team invite <email>` [#looped-manage-team-invite-email] Invites someone to the company by email. | Flag | Description | | --------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `--role <role>` | `admin` or `member`. Defaults to `member` | | `--roles <ids>` | Comma-separated role ids they start with, such as `track.member,invoices.admin`, or a custom role's id. If you leave it out, a Member gets `track.member` and an Admin gets none | | `--json` | Print JSON | Built-in role ids include `track.admin`, `track.member`, `invoices.admin`, `financials.admin` and `payroll.admin`. See [Roles & permissions](/manage/roles). ```bash looped manage team invite sam@example.com --role member --roles track.member,invoices.admin ``` #### `looped manage team invites` [#looped-manage-team-invites] Lists pending invites. | Flag | Description | | -------- | ----------- | | `--json` | Print JSON | ```bash looped manage team invites ``` #### `looped manage team revoke-invite <inviteId>` [#looped-manage-team-revoke-invite-inviteid] Cancels a pending invite. | Flag | Description | | -------- | ----------- | | `--json` | Print JSON | ```bash looped manage team revoke-invite <inviteId> ``` #### `looped manage team change-role <memberId>` [#looped-manage-team-change-role-memberid] Changes a member's base role, their roles, or both. Pass at least one of `--role` and `--roles`. | Flag | Description | | --------------- | -------------------------------------------------------------------------------------------------------------------------------------- | | `--role <role>` | `owner`, `admin` or `member`. Only an Owner can make someone an Owner | | `--roles <ids>` | Their full list of role ids, comma-separated. This replaces the list they have. An empty string (`--roles ""`) removes all their roles | | `--json` | Print JSON | ```bash looped manage team change-role <memberId> --role admin looped manage team change-role <memberId> --roles track.admin,invoices.admin ``` #### `looped manage team remove <memberId>` [#looped-manage-team-remove-memberid] Removes a member from the company. They need a new invite to come back. | Flag | Description | | ----------- | ----------- | | `--confirm` | Required | | `--json` | Print JSON | ```bash looped manage team remove <memberId> --confirm ``` #### `looped manage team leave` [#looped-manage-team-leave] Removes you from the selected company. You need a new invite to come back. | Flag | Description | | ----------- | ----------- | | `--confirm` | Required | | `--json` | Print JSON | ```bash looped manage team leave --confirm ``` ### Company settings [#company-settings] #### `looped manage settings show` [#looped-manage-settings-show] Shows the company's name, VAT number, currency and other settings. | Flag | Description | | -------- | ----------- | | `--json` | Print JSON | ```bash looped manage settings show ``` #### `looped manage settings update` [#looped-manage-settings-update] Changes company settings. Only the flags you pass change; pass at least one. | Flag | Description | | ---------------------------------- | --------------------------------------------------------------------------------------------- | | `--name <name>` | Company name | | `--vat-number <vatNumber>` | VAT number | | `--currency <currency>` | Currency code, such as `USD` | | `--auto-add-members <true\|false>` | Whether new members are added to this company automatically. Takes the word `true` or `false` | | `--json` | Print JSON | ```bash looped manage settings update --currency ZAR --auto-add-members false ``` #### `looped manage settings friendly-id <friendlyId>` [#looped-manage-settings-friendly-id-friendlyid] Changes the company's friendly id, the short name used in its URLs. | Flag | Description | | -------- | ----------- | | `--json` | Print JSON | ```bash looped manage settings friendly-id acme-studio ``` #### `looped manage settings address show` [#looped-manage-settings-address-show] Shows the company's billing address. This is also the address on your invoices. | Flag | Description | | -------- | ----------- | | `--json` | Print JSON | ```bash looped manage settings address show ``` #### `looped manage settings address set` [#looped-manage-settings-address-set] Sets the company's billing address. Creates it if there isn't one yet, or replaces it. Lines you leave out are cleared. | Flag | Description | | ---------------------------- | ------------------------ | | `--line1 <line1>` | Required. Address line 1 | | `--line2 <line2>` | Address line 2 | | `--line3 <line3>` | Address line 3 | | `--postal-code <postalCode>` | Required. Postal code | | `--json` | Print JSON | ```bash looped manage settings address set --line1 "12 Long Street" --line2 "Cape Town" --postal-code 8001 ``` #### `looped manage settings bank show` [#looped-manage-settings-bank-show] Shows the company's bank account details. | Flag | Description | | -------- | ----------- | | `--json` | Print JSON | ```bash looped manage settings bank show ``` #### `looped manage settings bank set` [#looped-manage-settings-bank-set] Sets the company's bank account details. Creates them if there aren't any yet, or replaces them. All five details are required. | Flag | Description | | ------------------------------ | ----------------------------- | | `--account-holder <name>` | Required. Account holder name | | `--account-no <accountNo>` | Required. Account number | | `--account-type <accountType>` | Required. Account type | | `--bank-name <bankName>` | Required. Bank name | | `--branch-code <branchCode>` | Required. Branch code | | `--json` | Print JSON | ```bash looped manage settings bank set --account-holder "Acme Studio" --account-no 123456789 \ --account-type Cheque --bank-name "Example Bank" --branch-code 250655 ``` #### `looped manage settings delete-team` [#looped-manage-settings-delete-team] Permanently deletes the selected company. This can't be undone. Only an Owner can do it, and Looped refuses if the company has an active subscription or it's your only company. See [Danger zone](/manage/danger-zone). | Flag | Description | | ----------- | ----------- | | `--confirm` | Required | | `--json` | Print JSON | ```bash looped manage settings delete-team --confirm ``` ### API keys [#api-keys] These commands manage the company's [API keys](/manage/api-keys). They need the "Manage API keys" permission, which Owners and Admins have. #### `looped manage keys list` [#looped-manage-keys-list] Lists the company's API keys, with their permissions, whether they're revoked, and when they expire. | Flag | Description | | -------- | ----------- | | `--json` | Print JSON | ```bash looped manage keys list ``` #### `looped manage keys create` [#looped-manage-keys-create] Creates an API key. The CLI prints the raw key once. Copy it then: it can't be shown again. | Flag | Description | | ------------------------ | ----------------------------------------------------------------------------------------------------------------- | | `--name <name>` | Required. A label for the key | | `--scope <scopes>` | Required. Comma-separated [permissions](/manage/api-keys#permissions), such as `track:time.read,track:time.write` | | `--expires-at <isoDate>` | Expiry date, ISO 8601. Leave it out for a key that doesn't expire | | `--json` | Print JSON | ```bash looped manage keys create --name "Reporting service" \ --scope track:time.read,invoices:invoices.read --expires-at 2027-01-01 ``` #### `looped manage keys revoke <id>` [#looped-manage-keys-revoke-id] Revokes an API key. Anything using it stops working straight away. | Flag | Description | | -------- | ----------- | | `--json` | Print JSON | ```bash looped manage keys revoke <keyId> ``` # Moving from Sage Pastel (/guides/moving-from-pastel) If your company runs its books and stock in Sage Pastel Partner, Looped can bring it across with its history, and check that the numbers match Pastel before anyone starts working in Looped. The move is done with you by the Looped team; it isn't something you start from a settings page. Email [support@looped.sh](mailto:support@looped.sh) to plan one. ## What comes across [#what-comes-across] Looped reads the Pastel company folders directly, so nothing has to be exported by hand. Each financial year comes across on its own. | In Pastel | In Looped | | ---------------------------------------------------------- | ---------------------------------------------------------------------------- | | Chart of accounts and the general ledger | **Financials**: the accounts and every year's entries | | Customers, with their account codes and delivery addresses | **Invoices**: clients, keeping the Pastel code as the client code | | Sales reps and customer categories | **Invoices**: sales codes and client categories | | Open invoices and credit notes | **Invoices**: each as its own document, so statements and age analysis match | | Balance-forward customers | **Invoices**: their balance, brought forward | | Quotes and sales orders | **Invoices**: linked to the invoices they became | | Suppliers, with their account codes | **Financials**: suppliers, keeping the Pastel code as the supplier code | | Open supplier invoices and supplier returns | **Financials**: supplier invoices and supplier returns | | Inventory items, their suppliers and maximum levels | **Inventory**: items, with every supplier you've bought them from | | Stock on hand | **Inventory**: opening stock, already in the books | | Open purchase orders | **Inventory**: purchase orders, with what's still to come | | Sales and purchase history | **Inventory** and **Invoices** reports, for the years it covers | Invoice numbering carries on from Pastel's serials. ## How the numbers are checked [#how-the-numbers-are-checked] Before you switch, the move proves that Looped matches Pastel: * **Trial balance**: every account agrees with Pastel's trial balance, for each year. * **Debtors**: what each client owes in Looped agrees with Pastel, and in total with the Debtors control account. * **Creditors**: open supplier invoices and returns agree with the Creditors control account. Anything that doesn't match is looked at with you before the move is signed off. ## Your history [#your-history] The years you're still working in are live in Looped. Older closed years are kept as archives: reports, comparatives, statements and an item's stock history still reach them, and they load when a page asks for them. Archived years are read-only. You can see them in Financials under **Settings → History**; see [Archived years](/financials/year-end#archived-years). # Creating valid invoices (/guides/valid-invoices) In South Africa, there are two main types of invoices that are considered [valid by SARS](https://www.sars.gov.za/businesses-and-employers/government/tax-invoices/). These are full tax invoices and abridged invoices. In this guide, we will discuss the differences between these two types of invoices. ## Invoices vs Abridged Invoices [#invoices-vs-abridged-invoices] Full tax invoices are required for transactions with a value of R5000.00 or more (including VAT). Abridged invoices are permitted for transactions with a value greater than R50.00 and less than R5000.00 (including VAT). ### Full Tax Invoices [#full-tax-invoices] Full tax invoices are comprehensive documents that provide a detailed breakdown of a transaction between a buyer and a seller. These invoice are required to contain: 1. The words "Tax Invoice", "VAT Invoice" or "Invoice" 2. Name, address and VAT registration number of the supplier 3. Name, address and where the recipient is a vendor, the recipient’s VAT registration number 4. Serial number and date of issue of invoice 5. Accurate description of goods and /or services (indicating where applicable that the goods are second hand goods) 6. Quantity or volume of goods or services supplied 7. Value of the supply, the amount of tax charged and the consideration of the supply (value and the tax) ### Abridged Invoices [#abridged-invoices] Abridged invoices, on the other hand, are simplified versions of regular invoices. They are commonly used for transactions with lower values or for quick payment requests. Abridged invoices may contain less detailed information but still capture essential elements like: 1. The words "Tax Invoice", "VAT Invoice" or "Invoice" 2. Name, address and VAT registration number of the supplier 3. Serial number and date of issue of invoice 4. Accurate description of goods and /or services (indicating where applicable that the goods are second hand goods) 5. Value of the supply, the amount of tax charged and the consideration of the supply (value and the tax) ## Complying with SARS [#complying-with-sars] Understanding the distinctions between regular invoices, abridged invoices, and adhering to the SARS valid [invoice checklist](https://www.sars.gov.za/wp-content/uploads/Docs/Government/Tax-Invoice-Checklist-Version-2-29032016.pdf) is crucial for businesses to maintain transparency, ensure legal compliance, and streamline financial processes. ## We've got you covered [#weve-got-you-covered] By using invoicelink, you can rest assured that we will ensure that the invoices you produce are always valid. When you use our Quick Links feature, which is enabled for payment requests up to R5000.00, we automatically produce an abridged invoices for you. This means that the only information we need to collect from you is the description of the goods or services you are requesting payment for and the amount. For any other transactions, we allow you to generate comprehensive invoices that contain all the information required by SARS. We also allow you to customise the invoice according to your brand identity as well as turn them into templates that can be reused later. # Designing invoice templates (/tutorials) Coming soon!