Admin Setup and Monitoring

This page gives a quick overview of the main modules inside the Admin Portal Setup and Monitoring section.

These modules help office users prepare collection data, monitor daily SOA downloads, review customer SOA records, and track collected payments from MPOS.

What this section is for

The Admin Portal Setup and Monitoring section is used to make sure that:

• collectors are assigned to the correct collection area or code

• SOA and invoice data from PSCloud are properly downloaded into Clibase Tech

• customer SOA records are available and correct before collector download

• collected payments from MPOS are monitored and reviewed by the office team

Recommended daily check flow

A simple daily workflow for office users is:

1. Check SOA Daily Download to confirm that the latest SOA and invoice data were downloaded successfully.

2. Review the SOA Customer List to confirm that customer records are available and complete.

3. Verify that collector assignments are correct in Collector Code.

4. Monitor uploaded collections and payment transactions in Collection and Payments.

Why this matters

Using these modules properly helps ensure that:

• collectors receive the correct accounts for collection

• SOA data is updated and accurate

• customer records are ready before field collection starts

• collected payments are visible and easier to validate at the office

Quick summary

Module	Purpose
Collector Code	Assign collection area or collector codes
SOA Daily Download	Monitor daily SOA download from PSCloud
SOA Customer List	Review downloaded customer SOA records
Collection and Payments	Monitor and validate collected payments

Common Questions

1. Which module should be checked first every day? The SOA Daily Download module should usually be checked first to confirm that the daily sync from PSCloud was completed successfully.

2. Which module shows the actual customer SOA records available in Clibase Tech? The SOA Customer List module shows the downloaded customer SOA records stored in Clibase Tech.

3. Which module is used to control what a collector can download in MPOS? The Collector Code module is used to manage the codes assigned to collectors, which help determine which accounts they can download.

4. Which module is used to monitor payments collected by field collectors? The Collection and Payments module is used to review and monitor collected payment transactions.

5. Why is this section important? Because it helps office users verify that the correct data is downloaded, assigned, and monitored before and after daily collection activity.

If you want, I can also make this into a more polished GitBook landing page style with a short intro, module cards, and a “Start Here” flow.