QCollect — Government Collections

QCollect — Government Collections

QCollect is the QoinPay Enterprise module for public-sector revenue: it lets Ministries, Departments and Agencies (MDAs) and other collecting entities raise assessments, accept payment across every channel, reconcile receipts against bank settlement, and remit consolidated funds to the treasury with a complete audit trail. It is designed for the accountability requirements of government finance — every naira collected is traceable from the payer, through the settling bank, to the revenue head it lands in. Running on-premise keeps citizen and revenue data inside the government's own boundary.

Capabilities

QCollect models the collection chain with a few durable objects: the entity (an MDA or collecting body), the revenue head (a coded line of income, mapped to a treasury GL account), the assessment/bill (an amount due, carrying a unique payment reference), and the receipt (proof of a confirmed payment). A payment reference — often a Remita-style RRR or an internal invoice number — is the spine that links a bill to its payment and its reconciliation record.

Key capabilities include:

• Assessment and billing. Generate bills with unique references, due dates, and revenue-head coding, individually or in bulk.
• Multi-channel collection. Accept payment at bank branches, through internet and mobile banking, at POS and agent points, and online — all converging on the same reference.
• Reconciliation. Match collector-bank settlement files against issued bills automatically, surfacing under-payments, over-payments, duplicates, and unmatched credits for clerical resolution.
• Remittance and sweeping. Consolidate confirmed collections and remit to the Treasury Single Account (TSA) or designated sub-accounts on schedule, with remittance advice.
• Reporting. Revenue-head, entity, period, and channel breakdowns for management and audit.

Reconciliation and remittance

Reconciliation is where public collections most often fail, so QCollect makes it the centre of the workflow. Collecting banks deliver settlement files; the module ingests them, matches each credit to its bill by reference and amount, and classifies the outcome. Matched items are receipted automatically; exceptions queue for review with the reason attached. Once collections for a cycle are confirmed, the remittance engine nets them by revenue head and produces the payment instruction and advice for the treasury, closing the loop from citizen to consolidated fund.

Key modules

• Entity & Revenue Head Registry — the coded chart of collecting bodies and income lines, mapped to treasury GL accounts.
• Billing — assessment generation, bulk upload, and reference issuance.
• Collection Gateway — the channel-agnostic intake that records confirmed payments.
• Reconciliation Engine — settlement-file ingestion, matching, and exception management.
• Remittance & Sweeping — consolidation, treasury instructions, and advice.
• Reporting & Audit — revenue analytics and the immutable audit log.

API and integration

Bills and payment status are exposed through /api/v1, so portals, USSD front-ends, and bank channels can create bills and confirm payments programmatically:

POST /api/v1/collections/bills
Content-Type: application/json
Authorization: Bearer {token}

{
  "entity_code": "MDA-021",
  "revenue_head": "1201-LAND-USE",
  "payer": { "name": "Ada Ltd", "tin": "01234567-0001" },
  "amount": 250000,
  "due_date": "2026-09-30"
}

Payment confirmations from channels arrive as signed webhooks; verify the signature before receipting. See the API overview for signature and retry detail.

Editions

• Standard — single-entity billing, manual reconciliation, and core reporting.
• Professional — multi-channel collection, automated settlement-file reconciliation, and scheduled remittance.
• Enterprise — multi-entity and multi-tier government hierarchies, TSA sweeping, configurable revenue-head hierarchies, and extended audit retention.

Edition is carried in the entitlement and enforced by the license key.

Sizing metric — collecting entities

QCollect is licensed by the number of collecting entities (MDAs or bodies) configured in the registry, reflecting the administrative reach of the deployment rather than transaction volume. The license tier sets the maximum number of active entities; the console warns as the count approaches the ceiling and blocks new entity creation once it is exceeded. Size to the full set of bodies you expect to onboard, since revenue heads and bills within an entity are unrestricted.

Licensing and Software Subscription & Support

QCollect is perpetually licensed. The first year of Software Subscription & Support is included and covers regulatory updates (treasury and TSA circulars, reporting formats), security patches, and support. Public-sector reporting mandates change often, so current S&S is important for a live collection deployment.

Deployment

QCollect installs on the shared application tier and MariaDB instance and uses the standard license-activation flow. It requires scheduled jobs for settlement-file ingestion and remittance runs, and secure channels to your collecting banks for file exchange. For setup and integration, see the Getting Started, Licensing, and API overviews.