Selling is half of it. The other half is knowing what you've actually been paid. Tabs keeps a running record of the money that has come in against each order, so at any moment you can see who has paid in full, who still owes you, and how each payment was made.

Recording a payment

Most of the time the customer pays the way they always do, and you record it. Where your business has connected Paystack, the customer can also pay the order from their own phone through a Paystack link or QR code, and where it has connected Moniepoint, on your Moniepoint terminal. Either way, Tabs records it for you. That's below.

Open the order and press Record payment. The Record a payment window opens on the balance still owed.

  1. Enter how much was paid, or press the button to pay the full balance.
  2. Under Paid by, pick how they paid: Cash, Transfer, POS or Other.
  3. Add a reference if you have one. For a transfer, the bank reference or the sender's name. For POS, the receipt number.

Once your business has accounts, Paid into asks where the money went, and the payment is written into Transactions against it.

The payment is recorded straight away and listed on the order.

Where the order's store takes Paystack or Moniepoint, one tile, Integration (a plug), sits beside the other ways. Tap it and a list called Pay through an integration opens, with a row for each way, with the gateway's mark and a tick on the one picked: Paystack, and each Moniepoint terminal by its name. Tap a row to pick it. The list closes, the tile shows that way's name, and a line under the tiles says its name and what happens. With no integrations for the store, the tile isn't shown. Nothing is picked until you tap one, and Tabs doesn't remember the last choice, so changing store never leaves a different gateway picked.

Picked, it doesn't record anything by hand. The button says what it does: Make a Paystack link shows a code to scan, and "Send ₦… to Front counter" sends the balance to that terminal. It's the same wherever Record payment opens: the order's page, a phone's bar at the foot of the order, or a row's menu on the Orders list.

On a swap deal, the credit you gave for the customer's old item is listed here too, marked as a trade-in credit that is not money. You don't record it yourself. Tabs adds it when the swap is confirmed, and it can't be voided on its own.

The reference is optional, up to 120 characters, and it's the field you'll be most glad you filled in. When a customer says "I sent it on Tuesday", the reference is how you find it on your bank statement.

A sale paid at the counter

For a simple counter sale you don't need this step at all. When you create the order, say how it was paid under How is it paid? and set it to Completed, and it's recorded as paid and completed in one go. See orders.

Taking a payment with Paystack

Once your business has connected Paystack, the customer can pay an order by card or bank transfer through Paystack. The money settles to your business's bank account, and Tabs takes no cut. Paystack takes naira only, and only the stores you picked take it.

Paystack is one way to pay: Paystack link or QR, "a code to scan or a link to send. They pay on their phone." Tabs makes a payment link, the customer pays on their own phone, and the order is marked paid when Paystack confirms it.

There are two places to start:

  • At the till. Tap the Integration tile, pick the Paystack row, and press Create and make a Paystack link. Tabs makes the order, then the link. A sale paid this way can't be marked Completed at the till. It stays pending, and the ticket says "Paid by link: mark it completed on the order once they've paid."
  • On the order. Press Record payment, tap the Integration tile, pick the Paystack row, and press Make a Paystack link.

If the order is for a walk-in, or a customer with no email on file, Tabs first asks for the payer's email in a window called "Make a payment link", and you press Make link. Otherwise it makes the link with the customer's email straight away. It shows Scan to pay: a code the customer points their phone camera at, with Copy link to send it to someone who isn't with you. Copying shows "Payment link copied".

Paystack needs an email for the payer. The Scan to pay screen shows the order and says "plus Paystack's fee at checkout": the customer pays Paystack's fee on top, and there's no choice to make. Only the order's amount goes on the order.

When the customer pays, it shows on the order by itself and the order is paid. If it isn't confirmed straight away, a payment still waiting has Check with Paystack beside it. Asking again for the same payer and balance gives the same link, so one customer isn't charged twice for the same balance.

If a payment lands that the order no longer owes, because it was paid in full meanwhile or cancelled, it isn't added to the order and the payment is voided. The order says why. What happens to the money is in Money that has to go back.

What the customer sees

A customer paying through Paystack sees "TabsHQ" on their bank statement, not your shop's name. The receipt Tabs emails them names your shop and says what the statement shows.

Paystack money that has to go back

A payment paid into your shop's own Paystack account (its subaccount) is never refunded by Tabs, because Paystack would take the refund from Tabs's balance, not yours. The money is in your account, so the shop gives it back. This covers a payment that is voided, and one that lands for an order that no longer owes it.

  • The owner is told in the bell: "Give back" the amount "paid by Paystack on" the order, with "Give the money back to the customer, then mark it returned."
  • While it is still to give back, the owner is reminded each day, until it is marked.
  • Once the customer has the money, open the order. The payment card says the amount is "to give back". Press Mark returned, say how it went back, and add a note. Marking it needs Void or change payments. Moniepoint terminals work the same way.

Only payments taken before shops had Paystack subaccounts are still refunded through Paystack.

When a customer disputes a payment

A customer can ask their bank to take back a payment they made through Paystack. This is a dispute, or chargeback. The bank raises it with Paystack, Paystack raises it with Tabs, and Tabs passes it to you.

  • On the order, the payment reads Disputed, with the amount in question and the time to answer by, such as "Answer by 30 Oct, 14:00 with your records". Anyone who can see the order sees it.
  • The owner is told in the bell and by email when a dispute is raised, when it still needs an answer, and how it ended. These can't be turned off: money is at stake, and the answer has a deadline.

To answer, reply to the email with what shows the sale was genuine: the receipt, proof that the customer collected or received it, and any messages with them. Tabs sends it to Paystack for you. A dispute that isn't answered in time is lost.

When it ends, the payment says so:

  • Dispute won: the payment stands, and there's nothing more to do.
  • Dispute lost: the money goes back to the customer. Paystack takes it from Tabs, and under the Terms your business pays it back. Tabs gets in touch about how. The order itself isn't changed. Tabs writes the amount into Transactions as money out, on the day the dispute ended, against the account Paystack pays out to.

Taking a payment on a Moniepoint terminal

Once your business has connected Moniepoint and set a terminal to the order's store, Tabs can send what the order owes to that terminal. The customer pays there by card or transfer, and the money settles to your Moniepoint account. Moniepoint takes naira only, at least ₦1.

  • At the till. Tap the Integration tile, then the terminal's row (each terminal has its own), and press Create and send to the terminal, such as Create and send to Front counter.
  • On the order. Press Record payment, tap the Integration tile, pick the terminal's row, and press "Send ₦… to" the terminal.

Tabs then shows "Waiting for the customer". The window updates by itself once they've paid, and you can close it: the payment shows on the order. Check again asks Moniepoint now. To stop it, cancel it on the terminal. A payment nobody pays within a day fails.

Moniepoint can't refund through Tabs. If the customer pays on the terminal after the order was cancelled or already paid, nothing is added to the order, the owner is told in the bell, and the shop gives the money back. Moniepoint POS terminals has the whole of it.

Part payments and money owed

A customer can pay in parts. This is how to handle deposits and credit sales.

Say a customer orders ₦60,000 of goods and pays ₦25,000 now. Record ₦25,000. The order shows as Part paid, with a balance due of ₦35,000. When she pays the rest next week, open the same order and record ₦35,000. The order now reads paid in full.

Each payment is listed on the order with its date, amount and method. That list is your record of the debt. Nobody has to remember it, and nobody can dispute it.

To see who owes you, look through the Orders page for orders marked part paid or still open. A part paid order shows how much has been paid and how much is still due under its Payment sticker.

Fixing a wrong payment

Mistakes happen. Someone records ₦15,000 when the alert said ₦1,500, or puts a payment on the wrong order.

Open the order, find the payment and choose Void payment. The amount comes off what's been paid, and the balance goes back up.

For cash, transfer, POS and other payments, voiding corrects the record only. It doesn't move any money. If cash actually changed hands and has to go back, give it back yourself. Voiding a Paystack payment is different. The window says "Paystack doesn't refund it to the card: the money is in your account, so give it back to the customer yourself, then mark it returned." Only an older payment, taken before subaccounts, is refunded to the customer through Paystack. See Paystack money that has to go back. Voiding a Moniepoint payment corrects the record only, like cash: give the money back yourself.

A voided payment isn't erased. It stays in the order's list of payments, crossed out, so a payment can't quietly disappear.

Editing a recorded payment

When the amount or the account was wrong but the payment itself was real, correct it instead of voiding it. Open the payment's menu on the order and choose Edit payment. The window, Edit this payment, says "Correct the amount or the account. The old figures stay on this payment and in Transactions."

  1. Change the Amount, and the Paid into account (Paid from on money going out).
  2. Under Why is it being changed?, say why, up to 1,000 characters. It is required: "Say why, so whoever reads the order later knows."
  3. Press Save changes. Tabs says "Payment edited".

The balance on the order moves with it. Tabs writes two lines into Transactions: one taking the old figure back and one with the new. The payment card shows the payment as it is now, and the order's Activity keeps the history, such as "edited a payment on" the order.

You can edit a payment on an order, on a reseller order and on a purchase. You can't edit:

  • a payment that came through Paystack or on a Moniepoint terminal. The window says "This payment can't be edited": its amount is what the gateway took, and its account is where the gateway pays out. If it shouldn't stand, void it.
  • a payment already voided, or a trade-in credit.

Editing needs the same permission as voiding: Void or change payments on orders and Void or change reseller payments on resellers. On a purchase it needs Change purchases and their dates and access to costs, and the purchase can't be a draft or cancelled.

Receipts

Press Print receipt on an order, or from the order's row on the Orders page.

A receipt is proof of money taken, so an order has one once a payment is recorded on it, in part or in full. Until then there's no Print receipt or Send receipt, on the order or in its menu. An order with nothing to pay, such as one a trade-in covers, has one straight away. A draft has none.

The receipt carries:

  • your business name and logo, in your brand colour
  • the items, with the size or colour of each
  • who served the customer
  • whether it was collected in store or is to be delivered
  • any discount: the lines' discounts as Discount, and money off the whole order or swap on a row of its own
  • the total, what's been paid, and either "paid in full" or the balance due

It's laid out 80mm wide, so it fits a thermal receipt printer. On an ordinary printer it prints centred on the page.

Your terms and your store's details

A receipt and an invoice both carry the store the sale was made at: its name, address and phone. They print for whoever makes the sale, a cashier included.

Your terms and conditions print at the foot of every receipt and invoice, above the thank-you line, and on the PDF you send by email or WhatsApp. Write them once for the whole business under business settings: returns, warranty, how long a price holds. With none written, nothing is printed there, not even the heading.

Each store can also have its own Note under the header, such as its opening hours, its own Closing line in place of the thank-you, and an Invoice prefix. Set them on the store.

A paper always prints with the terms as they are today. Reprinting an old order's receipt after you change them gives the new ones.

Sending a receipt by email or WhatsApp

Press Send receipt on the order's page, or choose it from the order's menu on the Orders page, then pick Email or WhatsApp. On a phone, the order's page also has a WhatsApp button after Print and Send receipt, which opens Send receipt straight on WhatsApp.

By email. Tabs fills in the customer's email if there's one on file. Change it for this send if they'd like it somewhere else, or type one in for a walk-in. When the address is new, a switch offers to save it to the customer for next time.

The customer gets an email from Tabs with the receipt attached as a PDF. It's the same receipt you'd print, with your logo and brand colour. The order's Activity records that a receipt was sent, and to which address. The order's notes also get a quiet line, "Receipt sent to" and the address, so anyone reading the notes can see it went.

On WhatsApp. The receipt always goes as its PDF, named with the order number and your business, such as "Receipt 1042 - Mama Ngozi Stores.pdf".

On a phone or a computer, the WhatsApp number box has the customer's number if there's one on file ("On file for" and their name), or type one in. A walk-in has none, so enter theirs or leave it empty. A note under it, What happens next?, says what pressing Send on WhatsApp will do:

  • With a number, the PDF saves, and WhatsApp (the app on a phone, WhatsApp Web or the desktop app on a computer) opens on their chat with a line saying "Here's your receipt for order" and its number. Attach the PDF there and press send. Where your phone or browser can share files, Share… beside it hands the PDF over through the share sheet instead.
  • With no number, on a phone, your share sheet opens with the PDF: pick WhatsApp, then who to send it to.
  • With no number, on a computer, the PDF saves and WhatsApp opens for you to pick who.

Three things to know:

  • Emailing needs a role that can email receipts. The owner and the built-in Staff role can. A role you made yourself needs it ticked. WhatsApp goes from your own phone or computer, so anyone who can see the order can use it.
  • A very long receipt can be too big to email. Tabs tells you, and you print it instead.
  • A website can't put a file straight into a WhatsApp chat, so unless your share sheet sends it, you attach the saved PDF yourself. Tabs reminds you: "Attach it in the WhatsApp chat, then press send."

Each item on a printed or PDF receipt shows its barcode under its name, when it has one, so you and the customer can tell which unit was sold.

Add your logo and brand colour under business settings. A receipt with your name and logo on it looks like it came from a proper business, because it did.

A payment's own menu on the order offers a receipt for that payment alone: Print receipt and Send receipt. Use it when a customer who paid in parts wants proof of one payment.

Invoices

A receipt says money was taken. An invoice asks for it. Every order that isn't a draft has an Invoice button on its page, with the same choices in the order's menu:

  • Print invoice
  • Send invoice, by email
  • Send invoice on WhatsApp, as a PDF
  • Download invoice

A reseller's order can print its invoice, send it, and send it on WhatsApp as a PDF.

The invoice is laid out on an A4 page, with your logo and brand colour. It carries:

  • Invoice no. and Issued
  • Status: Paid, Part paid, Unpaid or Cancelled
  • Bill to, the customer, or "Walk-in customer"
  • the items, each with Item, Qty, Price and Amount, and the item's barcode
  • the Total, what's been Paid, and the Balance due, or Owed to customer if they've paid more than they owe
  • a note, which starts as "Thank you for your business."

It has no due date. Use an invoice for a customer who is yet to pay, or who needs one for their own records, and a receipt once money has come in. Receipts work as they did.

Sending an invoice needs the same permission as sending a receipt, and invoices and receipts share one sending limit.

Returns

A return is a customer bringing back something they bought from you.

  1. Open the order and choose Start a return.
  2. Tick what's coming back, and how many of each.
  3. Add the reason, such as wrong size, damaged or changed mind.

A return takes back only what has been handed over. On a completed order that is everything on it. Before that, it is only what has been fulfilled, less anything that already came back. Each line says "up to" the number you can pick. If nothing is left, Tabs says "Nothing more has been handed over to come back yet.", or "Everything on this order has already come back." on a completed order. Until something is handed over, Start a return is off in the order's menu and reads "Nothing handed over to return yet".

When you save:

  • The return is recorded on the order, with the reason.
  • The goods go back into stock.
  • The order's figures update. If the customer has now paid more than they owe, the order shows the difference as owed to customer.

That last figure tells you what to refund. As with voiding, Tabs records it and you hand over the money.

A worked example

A customer bought 2 shirts at ₦9,500 each and paid ₦19,000. Two days later she brings one back because it doesn't fit.

Open her order, start a return, tick one shirt and write "wrong size". The shirt goes back into stock. The order now comes to ₦9,500 against ₦19,000 paid, so it shows ₦9,500 owed to customer. Refund her ₦9,500, or let her pick something else on a new order.

If the returned item can't be resold

A return puts the goods back into stock, whatever state they're in. If what came back is damaged, write that as the reason, so it's on record with the order, and keep the item apart from what you sell. If it's faulty and the supplier will take it, send it back to them as below.

Returns to your supplier are different

Sending faulty goods back to the business you bought them from is a separate thing. It's done from the product's page. See suppliers.

Every return in one place

Orders > Returns lists every customer return across the business, with its order, customer, units, refund and date. See orders.

A return is taken on the order it came off, in the store it was sold from. A member whose role doesn't have Work in every store only sees their own store's orders, so they take returns for their own store.

Cancelling an order that's been paid

If you cancel an order, everything on it goes back into stock, including items already handed over. Any payments recorded on it stay in its history. Void them if the money was returned, so the record matches what happened.

Who can do what

Taking payments (Take payments), voiding them (Void or change payments) and recording returns (Take returns) are separate permissions. Taking a payment with Paystack, or sending one to a Moniepoint terminal, needs Take payments too.

That lets you set things up sensibly. Sales staff record payments. Voiding, which is how money leaves the record, is kept to a manager or the owner. Returns can go to whoever handles customer complaints.

Set this under roles.