AWRA OpsHub Search
Intermediate Certificate on pass

Recurring Invoices & the Customer Portal

Bill retainers, rent and service contracts on a schedule with exactly one invoice per period, left as a draft, issued or issued and emailed — and give customers a passwordless portal to see their invoices, statement and quotes, answer quotes and pay by M-Pesa or card.

5 lessons 58 min 11-question assessment 70% to pass

What you’ll learn

  • Set up a recurring schedule with the right cadence, start date, delivery and pricing for each line
  • Explain how the daily run guarantees one invoice per period, catches up after downtime and retries failures
  • Use pause, raise next now and end schedule correctly, and know which of them skips periods
  • Set a schedule to charge a saved card or send an M-Pesa prompt, and explain the retries and the hand-off to dunning
  • Invite customers to the portal and explain how they sign in, what they see and how their payments are recorded

Course content

5 lessons · 58 min of reading
01
Lesson 1 of 5 Practice 9 min

Setting up a schedule

Recurring invoices are reached from the Recurring invoices link at the top of Sales → Invoices. A schedule names a customer, a set of lines and a cadence — weekly, monthly, quarterly or annually. You set First invoice on, the date of the first period, and optionally a last date; leave it empty and the schedule runs until you end it. Due after defaults to 14 days. If the lines include stock items, choose the warehouse to ship from and optionally a location in it. A user tied to one warehouse can only set their own. A recurring invoice is built by the same code as one you type, so it takes the same numbering, tax, credit check and eTIMS filing.

Two details shape what the invoices say. First, a line with a blank unit price is priced from the customer’s price list on each invoice date, while a typed price is fixed — so a price-list change reaches the next run only on lines left blank. Second, periods are counted from the first invoice date, not chained from the last run: a schedule that starts on the 31st bills on the last day of February and then on the 31st again, rather than drifting to the 28th. And a start date in the past back-bills: until a schedule has raised its first invoice, a past first date raises one invoice for every period from then to today, each dated to its own period. The form warns you how many before you save.

In practice: a property manager in Westlands sets up “Office rent — Block B” for a company leasing the floor, monthly, first invoice on 31 January 2026, due after 7 days, one service line typed at KES 85,000 plus 16% VAT — KES 98,600 an invoice. The invoices fall on 31 January, 28 February and 31 March. A colleague setting up a cleaning contract on 2 October with a first date of 1 January is warned that ten invoices will be raised, January to October, each dated to its own month — which is either exactly what she wants or a costly typo to catch before saving.

Key takeaways

  • Cadences are weekly, monthly, quarterly or annually; due after defaults to 14 days.
  • A blank line price is priced from the customer’s list on each invoice date; a typed price stays fixed.
  • Periods count from the first invoice date, so a 31st start returns to the 31st after February.
  • A past first invoice date back-bills every period to today, and the form warns how many.
02
Lesson 2 of 5 Reading 8 min

Draft, issued or emailed

Each schedule chooses how its invoices are delivered. With neither box ticked, each invoice is raised as a draft for someone to review and approve. Issue automatically approves each invoice as it is raised, which is when it files to eTIMS where that is switched on. Issue automatically and Email it to the customer also emails the invoice PDF to the customer’s address on file once it is issued. Emailing needs automatic issue, because a draft is not final, so a schedule with email ticked and issue unticked is refused.

Automatic issue never bills stock that is not free. If the goods for a period are short at the schedule’s warehouse after other orders’ reservations, the invoice is still raised on time but left as a draft, and whoever created the schedule is notified with what was short. An invoice that would take the customer over their credit limit goes on credit hold like any other and waits for an override. If an issued invoice cannot be emailed — the customer has no valid email address — the invoice stands and the creator is notified. On the ledger a recurring invoice posts exactly as a typed one: an invoice of services only books receivable, revenue and tax payable at issue; an invoice with stock lines books its whole revenue, and cost of sales, at checkout; a draft posts nothing until approved.

In practice: a water-dispenser company runs a monthly schedule for a school in Kisumu — a Dispenser rental service at KES 4,500 and a stock line for 20 bottles from the Kisumu depot, set to issue and email. In March the depot has only 12 bottles free after other orders are reserved. The March invoice is raised on its date but left as a draft, and the person who built the schedule sees a notification naming the bottles that were short. Once stock arrives they approve the draft by hand; the April invoice goes out on its own as usual.

Key takeaways

  • No box ticked raises drafts; issue automatically approves on raise, which files to eTIMS where enabled.
  • Email needs automatic issue; a schedule with email but not issue is refused.
  • Short stock leaves that period’s invoice as a draft and notifies the schedule’s creator.
  • A recurring invoice posts exactly as a typed one; credit limits put it on credit hold like any other.
03
Lesson 3 of 5 Reading 8 min

The daily run, catch-up and failures

Every morning the system raises the invoices that are due. Each schedule raises one invoice per period, ever: a second run, a retry or a double click cannot raise a duplicate. Periods missed while the system was down are raised when it is back, each dated to its own period, up to 12 per schedule per run, so a longer backlog finishes on the following mornings. A schedule also ends by itself once its last invoice date has passed.

A failure does not skip a month. If a period cannot be raised, the error is recorded on the schedule, the schedule stays where it was, and the same period is retried on the next daily run; the creator is notified the first time it fails, not every morning. Managing a schedule uses four actions. Raise next now raises the next period’s invoice today, whatever its date — the same period the daily run would have raised, so it is never raised twice. Pause stops billing, and periods that fall while paused are skipped, not billed; on resume it picks up at its next date from today. End schedule is final: an ended schedule cannot be edited or resumed. Editing changes lines, delivery and dates, and once an invoice has been raised a change of start date or cadence recounts the next date from the last invoice raised.

In practice: a monthly retainer bills on the 1st. The client asks for a break, so the account manager pauses it on 10 March and resumes on 20 May. The April and May periods are skipped, not stored up, and the next invoice is 1 June. Had she meant only to delay April’s bill, the right tool was to leave the schedule active and adjust the schedule instead. The schedule page lists every period raised with its invoice, total and status — and the error text for any period that failed, which is where to look when a customer says a month never arrived.

Key takeaways

  • One invoice per schedule per period, ever — retries and double clicks cannot duplicate.
  • Missed periods are caught up, each dated to its own period, up to 12 per schedule per run.
  • A failed period is retried daily from where it stopped; the creator is notified once.
  • Pause skips the periods inside it; raise next now bills the next period today; end is final.
04
Lesson 4 of 5 Practice 8 min

Collecting automatically: card and M-Pesa auto-charge

A schedule can also collect the money, not only raise the invoice. Collect payment on the schedule has three settings: Do not charge, Charge the saved card, and Send an M-Pesa prompt. Charge the saved card uses a card the customer has already paid with through Paystack: a card is saved when they pay one of the schedule’s invoices by card, or tick “save this card” when paying in the customer portal, and the customer page lists it under Collections. Send an M-Pesa prompt pushes a payment request to the M-Pesa number on the schedule or on the customer; nothing is taken until the customer approves it on their phone, so it is a prompt, not a debit. Auto-charge works in Kenyan shillings only, and only on a schedule set to Issue automatically, because a draft invoice is not final and is never charged.

The first attempt is made on the day the invoice is raised, and each later attempt comes from the next daily run, up to three attempts, one a day. An attempt still unanswered by the next run counts as failed, and the creator is told after each failure how many tries are left. A card charge that succeeds is settled straight away as a payment on the invoice, exactly as if the customer had paid it in the portal; an M-Pesa prompt is settled when M-Pesa confirms it. After the third failure the run is marked failed, the schedule’s owner is notified, and the invoice is handed to the dunning ladder, which leaves an invoice alone while its charge is still being tried. Each run’s charge status shows on the schedule page and on the invoice.

In practice: a fibre internet provider in Kilimani bills 600 home customers KES 3,999 a month on the 5th. Customers who paid once by card are charged automatically on the 5th, and the payment lands on the invoice before anyone looks. The rest get an M-Pesa prompt on the 5th; one customer is travelling and ignores it, is prompted again on the 6th and 7th, and on the 8th the invoice moves to the dunning ladder, whose day-1 reminder carries a pay link. Nobody in accounts had to chase the 594 who paid.

Key takeaways

  • Collect payment is Do not charge, Charge the saved card, or Send an M-Pesa prompt; KES only, with Issue automatically on.
  • A card is saved when the customer pays by card or ticks “save this card” in the portal.
  • Up to three attempts, one a day, starting the day the invoice is raised.
  • After the third failure the owner is told and the invoice goes to the dunning ladder.
05
Lesson 5 of 5 Practice 17 min

The customer portal: access, what customers see and pay

The customer portal is reached from the Customer portal link at the top of Sales → Quotes, which lists everyone with access, their customer, their last sign-in and whether access is active, and shows the portal address to share. Invite someone takes the customer, the person’s name and their email. Several people from one customer can each have access, but one email address belongs to one customer: an address with access for a different customer is refused, and re-inviting one for the same customer updates the name and sends a fresh link. There is no password. The customer enters their email and is sent a link that works once and expires in 30 minutes, finished with a button so email security scanners cannot use it up; the sign-in page answers the same for any address and limits link requests, so it cannot reveal who your customers are or flood an inbox. Revoke ends access at once and stops every link already sent. Inviting, resending and revoking sit behind one permission, managing the customer portal, on the web and in the mobile app.

Every page shows only that one customer’s records, under your name and logo. The overview shows the total owed, how much is overdue, recent invoices and quotes waiting for an answer. Invoices lists what you have issued — drafts and invoices on credit hold are hidden — with lines, payments and a PDF. The statement shows invoices, payments and credit notes with opening, running and closing balances, for the last six months by default. An open quote can be accepted or declined with a note, recorded under the signed-in person’s name. Customers can pay all or part of a balance by M-Pesa prompt or by card through Paystack, into your own accounts connected under Settings → Finance & Tax → Payment Settings. Each option appears only when that gateway is connected and active, for a Kenyan shilling invoice with a balance of at least 1, and a payment is recorded only when M-Pesa or the card network confirms it, not when the customer clicks pay. The portal itself posts nothing; a confirmed payment reduces the balance like any other customer payment.

In practice: an accounts officer invites the finance lead and the procurement officer at a Nakuru flower farm, each with their own email. The procurement officer opens his invitation the next day, after its 30 minutes are up, so she clicks Resend link. The finance lead signs in and sees KES 312,400 owing, KES 86,000 of it overdue; she pays KES 50,000 of the overdue invoice by M-Pesa, approves the prompt, and once M-Pesa confirms, the invoice shows KES 36,000 still due. She accepts a pending quote for cold-room packaging with the note “deliver after the 15th”. A USD invoice to the farm’s export arm shows no pay buttons, because the gateways take Kenyan shillings only — that one is paid by bank transfer and recorded by your staff. When the procurement officer later leaves the farm, Revoke ends his access at once; inviting the same email again would restore it.

Key takeaways

  • One email address belongs to one customer; sign-in is a one-time link that expires in 30 minutes, with no password.
  • Revoke ends access immediately and stops links already sent; re-inviting the same email restores it.
  • Each page shows one customer’s records only; drafts and credit-hold invoices are hidden, and the statement defaults to six months.
  • Pay buttons need an active gateway, a Kenyan shilling invoice and a balance of at least 1; a payment records only when confirmed.

Finished the material?

Take the 11-question assessment and earn your certificate — 70% to pass.

Take the assessment

Help Center

Need a quick answer while you read?

Run inventory, procurement, assets, sales, and field work with approved AWRA guidance for setup, migration, integrations, security, pricing, and support.

Search all approved AWRA public help articles.

Open Help Center