CentraPoint

Guides

Debit orders & reconciliation

How Netcash debit orders work in CentraPoint: mandates and online agreements, approvals, batches, action dates, unpaids, re-presentation and reconciliation.

On this page

Overview#

CentraPoint collects recurring bank debit orders in South Africa through Netcash, and reconciles money received against transactions by importing statements. The flow is:

  1. You create a mandate for a customer and obtain their authority (Netcash e-mandate, an online agreement signed in CentraPoint, or a signed mandate you already hold).
  2. Once authorised (and approved, if you require approval) the mandate becomes active with a next debit date.
  3. A scheduled run groups due mandates into a Netcash batch per action date and uploads it, or parks it for approval.
  4. Netcash's load report marks each line accepted or rejected; accepted debits are marked collected after the settlement period.
  5. Returned debits are marked unpaid and can be re-presented automatically. Reconciliation marks a debit unpaid only when the return fits exactly one debit, which for a monthly mandate is rarely the case after its first debit; otherwise you mark it (see Unpaids).

Everything lives under Debit orders in the dashboard, with tabs for Overview, Mandates, Batches, Agreements, Report and Settings (Settings needs the Change debit order settings permission, admins by default). The overview shows active mandates, upcoming collections for the next 45 days grouped by their weekend/holiday-adjusted debit date, 30 and 90 day success rates, recent unpaids and recent batches. Users with the same permission can also start a run immediately with Run now.

Requirements#

  • A plan that includes Debit orders and/or Reconciliation.
  • A Netcash account with the debit order and account services, configured as a Netcash Debit Orders provider under Settings → Payment providers (debit order service key and account service key).
  • For Netcash e-mandates, the mandate postback URL configured in Netcash so CentraPoint learns when a customer signs (see Gateway notifications).

Debit order settings#

Admins set these under Debit orders → Settings. Until you save them, the defaults below apply. Changes take effect from the next run.

Debit order settings
SettingDefaultWhat it does
Processing lead days2Business days (0-30) before the debit date that the batch is submitted. A mandate is batched once today reaches its submission date: the weekend/holiday-adjusted debit date minus this many business days. It also sets the earliest action date a new batch can use (see below).
Default debit day1Day of the month (1-31) pre-filled on new dashboard mandates, and used when an API request omits debitDay. Days past month-end use the last day of the month (31 becomes 28, 29 or 30).
Weekends and public holidaysNext business dayWhen a debit date is a Saturday, Sunday or South African public holiday, debit on the next business day or on the previous business day.
Re-present unpaid debits2How many times (0-10) a returned (unpaid) debit is submitted again in a later batch. 0 turns re-presentation off.
Require mandate approvalOffNew mandates stay pending until someone with the mandate approval permission (admins by default) approves them, even once the customer has signed. Existing active mandates are not affected.
Require a signed agreementOffOnly mandates with at least one signed online agreement are included in batches. Active mandates without one are skipped (the run reports how many) until the customer signs.
Require batch approvalOffEvery new batch waits in awaiting_approval for review instead of being uploaded to Netcash straight away.
First invoice is pro formaOffThe first invoice CentraPoint issues for a debit order subscription (normally its setup fee invoice, since the debits themselves are collected by the mandate without an invoice) is issued as a pro forma: it is titled PRO FORMA INVOICE on its PDF and printout. Later invoices of the subscription are normal invoices. The pro forma is not converted afterwards.

Action dates, weekends and public holidays#

All dates are South African calendar dates (Africa/Johannesburg). For each due debit CentraPoint works out:

  • Effective debit date: the mandate's next debit date, moved to the next or previous business day if it falls on a weekend or public holiday (your weekend and holiday setting).
  • Earliest action date: today plus the larger of your processing lead days and the instruction minimum (2 business days for Two-day, 0 for Same-day). After 10:00 SAST one extra business day is added.
  • Action date: the effective debit date, or the earliest action date if the effective date can no longer be met. Netcash's own calendar is then asked for the final action date; if that call fails, the South African calendar below is used.

Debits are grouped into one batch per action date. The Netcash instruction (Two-day or Same-day) and how far ahead to look for due mandates come from the Netcash provider configuration.

South African public holidays#

CentraPoint treats these days as non-business days, following the Public Holidays Act:

  • Fixed holidays: New Year's Day (1 Jan), Human Rights Day (21 Mar), Freedom Day (27 Apr), Workers' Day (1 May), Youth Day (16 Jun), National Women's Day (9 Aug), Heritage Day (24 Sep), Day of Reconciliation (16 Dec), Christmas Day (25 Dec) and Day of Goodwill (26 Dec).
  • Good Friday and Family Day (the Monday after Easter), calculated from the date of Easter each year.
  • Sunday rule: when a fixed holiday falls on a Sunday, the following Monday is also a public holiday.
  • One-off holidays declared by the President, such as election days.

Mandates#

A mandate is a customer's authority to debit their bank account. Create one under Debit orders → New mandate (or with the Mandates API) with the customer, Netcash account, optional product (pre-fills amount and frequency), account holder (2-30 characters), bank, branch code, account number and type (current, savings or transmission), amount (up to R 1,000,000), frequency (monthly, quarterly, bi-annually or annually), debit day, start date and optional end date, ID or passport number and internal notes.

Bank details are validated against the selected bank (a Netcash sandbox account only checks the format); problems that do not block the mandate are shown as warnings. South African ID numbers are checked for a valid date of birth and check digit.

Each mandate gets an account reference of the form DO followed by 10 upper-case hex characters, e.g. DO7F3A1C9B2E. Bank account numbers are stored encrypted and only the last 4 digits are displayed.

Debit order authority#

When you create a mandate you choose how the customer's authority is obtained:

Authority options
AuthorityWhat happens
emandateA Netcash electronic mandate is sent to the customer. When Netcash posts back that it is signed, the mandate is marked signed. If Netcash reports it declined or cancelled, the mandate is cancelled.
agreementCentraPoint emails the customer your debit order agreement to sign online (see Online mandate agreements). The mandate is marked signed when they sign.
offlineYou confirm that you already hold a signed mandate. The mandate is marked signed immediately and becomes active at once, unless mandate approval is required.

The dashboard and the API both default to agreement. Staff can also use Mark signed on a pending mandate to record that the authority has been received.

Mandate stages#

A mandate stays pending until it is both authorised and, when you require mandate approval, approved. Lists and the API show a more precise stage:

Mandate stages
StageMeaning
awaiting_signaturePending; the customer's authority has not been received yet.
awaiting_approvalPending; authorised, but mandate approval is required and nobody has approved it yet.
pendingPending with authority and approval in place (normally only momentarily, before activation).
activeHas a next debit date and is included in batches when due.
pausedSkipped by batching. Set manually, or automatically after 3 consecutive unpaids.
cancelledStopped permanently: cancelled by staff, the API or Netcash, or its end date has passed.
rejectedRejected during approval. The mandate's status is cancelled and the reason is recorded.

On activation the next debit date is the first debit day on or after the later of today and the start date, repeating every 1, 3, 6 or 12 months from the start month.

Mandate approval#

With Require mandate approval on, every new mandate notifies your team and waits for approval. A user with the Approve or reject new debit order mandates permission (mandates:approve, admins by default) opens the mandate and chooses:

  • Approve: records who approved it and when. If the customer's authority is already in, the mandate becomes active; otherwise it activates as soon as the authority arrives.
  • Reject (reason required): cancels the mandate and any open agreement. It shows as rejected.

Only pending mandates can be approved or rejected.

Changing, pausing and cancelling#

  • Amount and debit day can be changed on any mandate that is not cancelled. A new debit day applies from the month of the next scheduled debit, so a cycle that was already batched is not debited twice. If the customer must consent to the change, send them a new agreement.
  • Pause an active mandate to skip it; Resume sets it active again and resets its unpaid count.
  • Cancel stops the mandate permanently and withdraws any open agreement. A cancelled mandate cannot be changed; create a new one.

Online mandate agreements#

Instead of a Netcash e-mandate, the customer can sign your own debit order agreement online. An agreement is generated when you create a mandate with the agreement authority, or when staff use Send agreement on a mandate (or call POST /api/v1/mandates/{id}/agreement). Issuing a new agreement withdraws any open one for the same mandate. All agreements are listed on the Agreements tab with the statuses pending, amended, signed, expired and cancelled.

Agreement template#

Admins edit the agreement title and text under Debit orders → Settings → Mandate agreement template, with a preview using sample data and a Use default button that restores the built-in wording. Changes apply to new agreements only; agreements already sent keep their text. Placeholders are filled from the mandate when the agreement is generated:

Agreement placeholders
PlaceholderFilled with
{{customerName}}Customer company and name
{{idNumber}}ID or passport number on the mandate
{{bankName}}Bank
{{accountHolder}}Account holder
{{accountNumberMasked}}Account number showing only the last 4 digits
{{branchCode}}Branch code
{{accountType}}Current / cheque, Savings or Transmission
{{amount}}Debit amount
{{frequency}}Monthly, Quarterly, Every 6 months or Annually
{{debitDay}}Debit day
{{startDate}}Mandate start date
{{companyName}}Your company name (company settings)
{{companyAddress}}Your company address on one line
{{date}}Date the agreement is generated

Empty values print as a dash. Unknown placeholders are left as typed, and the editor warns you about them.

The signing page#

The customer receives an email with a link to /sign-mandate/…. The link is valid for 14 days and is single-use. On the page they read the agreement, enter their full name, draw their signature (mouse, pen or touch) and tick a box to confirm they agree.

When they sign:

  • the agreement is stored as signed with the signature image, signer name, date and IP address;
  • a pending mandate is marked signed and activates (unless it still needs approval);
  • the customer is emailed a copy of the signed agreement and your team gets a notification.

Staff can open a printable copy of any agreement, including the signature and signing details, from the mandate's Agreements card. Links that are signed, expired or withdrawn show a matching message instead of the form. Expired agreements are marked expired by the scheduled run.

Resending, amending and cancelling#

  • Resend issues a new 14-day link and emails it; the old link stops working. An expired agreement reopens as pending.
  • Amend lets staff edit the agreement text. An unsigned agreement is changed in place and re-sent as amended. A signed agreement stays on record and a new amended agreement is issued for signature.
  • Cancel withdraws the agreement and its link. Cancelling a signed agreement means that, if you require signed agreements, the mandate is skipped until a new one is signed.

Mandates and subscriptions#

A customer subscription with the collection method debit_order is collected by a linked mandate rather than by invoices or a card (see Packages, plans & subscriptions). Link one of the customer's mandates to the subscription; the mandate must not be cancelled or linked to another subscription, and its frequency must match. Linking sets the mandate amount to the subscription amount, and the mandate end date to the day before the subscription ends, if it has an end.

  • The mandate collects on its own debit day. Billing dates of a debit order subscription follow the mandate; edit the mandate to change them.
  • Changing the plan updates the amount of the linked mandate. Changing the frequency needs a new mandate.
  • Debit order transactions carry the subscription, so failed and collected debits update it.
  • While an unpaid debit is still due to be re-presented, dunning does not create a separate recovery invoice.

Batches and collection#

The scheduled run (weekdays at 06:00 and 13:00 South African time; it also polls Netcash for upload reports and settles collected debits) and Run now process each enabled Netcash account. It picks up active mandates that are due (see Action dates), cancels mandates whose next debit date is past their end date, adds unpaid debits due for re-presentation, and groups everything into one batch per action date. Each mandate is advanced to its next debit date when the batch is created, so a repeated run cannot debit it twice. The batch is then uploaded to Netcash, or parked for approval.

Depending on your Netcash profile, batches are authorised automatically or by you in the Netcash portal. CentraPoint then reads Netcash's load report to see which lines were accepted or rejected. Each batch page shows a timeline of everything that happened to it (created, flagged, approved, submitted, accepted, settled, entries removed, action date changes) and the submitted file with account numbers masked.

Batch statuses
StatusMeaning
awaiting_approvalCreated, waiting for review (Require batch approval).
uploadedSent to Netcash, waiting for the load report.
accepted / partially_acceptedAll / some lines were accepted by Netcash.
rejectedNo lines were accepted.
settledAccepted lines were marked collected after the settlement period.
failedThe file could not be built or uploaded. The mandates are put back so the next run retries them.
cancelledRejected during review, or all its entries were removed.

Batch approval#

With Require batch approval on, each new batch is set to awaiting_approval and your team is notified. The Batches tab shows how many are waiting. A reviewer with the Approve or reject collection batches permission (debit_orders:approve, admins and staff by default) can:

  • Approve and submit (optional notes): uploads the batch to Netcash. If its action date can no longer be met, it is first moved to the earliest possible action date and the change is logged.
  • Reject (reason required): nothing in the batch is collected. Tick Return mandates to the queue to put the mandates back so the next run batches them again; otherwise this cycle is skipped.
  • Remove a single entry (with a reason): that debit is skipped this cycle, or re-queued for the next run if you tick Re-queue for next run. The batch totals are recalculated, and a batch with no entries left is cancelled.

Removed and rejected debits have their transactions cancelled; a removed re-presentation returns to the unpaid queue only when re-queued.

Debit order transactions#

Every line in a batch creates a transaction with type: "debit_order", currency ZAR, and a reference made of the mandate's account reference and the action date:

  • DO7F3A1C9B2E-20261001
  • DO7F3A1C9B2E-20261103-R1 for a re-presented debit (see below)

The transaction starts pending, becomes failed if Netcash rejects the line, and becomes complete a configurable number of days after the action date ("Mark collected after" on the provider, default 3) unless an unpaid arrives first. A successful collection resets the mandate's unpaid count.

Unpaids#

When a debit is returned unpaid (found through reconciliation or marked with Unpaid on the mandate's Collections list), its transaction becomes failed, the return date and reason are recorded, and the mandate's unpaid count increases. After 3 consecutive unpaids the mandate is paused automatically.

Reconciliation finds a return by itself only when the statement line fits exactly one debit (see Reconciliation). A return that names only the mandate and fits several of its debits, which is the usual case from a monthly mandate's second debit on, goes to the reconciliation Needs attention queue and changes nothing: the debit stays (or, once settled, becomes) complete, with its invoice paid and its subscription active, until you mark it Unpaid here. Linking the reconciliation line to the debit does not mark it unpaid.

Re-presenting unpaid debits#

When Re-present unpaid debits is above 0, each run picks up unpaid debits whose mandate is still active (and has a signed agreement, if required) and submits them again:

  • The re-presentation uses the earliest possible action date, not the mandate's debit day.
  • It is a new transaction for the same amount, with the reference suffix -R1, -R2 and so on, linked to the same invoice and subscription as the original.
  • A debit is re-presented at most the configured number of times. Each re-presentation that is returned unpaid counts towards the limit and towards the 3-unpaid auto-pause.
  • At most one debit per mandate is re-presented per run, and never alongside that mandate's regular debit in the same run.
  • The original entry is marked represented so it is not picked up again.

Debit order report#

Debit orders → Report lists individual debits by action date (by default 30 days back to 30 days ahead). Filter by action date range, entry status (pending, accepted, collected, rejected, unpaid, represented, skipped, or any returned debit), batch, and a search on reference or customer. The page shows totals for all debits, collected, returned/unpaid and a success rate (collected out of settled, returned and rejected), a breakdown by status, and each debit with its batch, customer, amount, return date and reason.

CSV downloads the filtered rows (up to 50,000, at most about 13 months at a time) including customer code, bank, masked account, entry and transaction status, return reason, retry number and transaction reference.

Reconciliation#

Under Reconciliation in the dashboard, CentraPoint imports statement lines and matches them to transactions:

  • Netcash merchant statements are fetched automatically using the account service key, for every Netcash gateway that has one (Debit Orders, Pay Now and Creditor & Salary Payments). Gateways sharing a key share one statement. See Netcash accounts.
  • CSV statements from other gateways or your bank can be imported manually.
  • Lines are categorised as collections, unpaids, fees, refunds, disbursements (creditor / salary payouts), payouts (settlements) or other. Collections confirm the matching transaction; unpaids mark the debit order they fit unpaid (when exactly one fits, see below); fees are recorded on the payment they name; payout debits mark payouts paid and returns mark them failed; settlements are recorded for reporting.
  • Matching uses CentraPoint references found in the statement (CP-… payment references, legacy GSS-… references and DO… debit order references). Lines that cannot be matched go to a Needs attention queue. A debit order collection that names only the mandate's reference confirms a debit presented (action date) on or before the line's date, never a later one. A line dated up to 3 days before the next debit is presented is not given to the previous month's debit when no debit was presented in the 3 days before the line and that next debit is not collected yet (and was sent to the bank): it goes to the queue instead.
  • An unpaid marks a debit unpaid only when it takes money out, and never twice: a return for a debit whose return is already on a statement, or with the date and amount of such a return, goes to the queue. One that names only the mandate's reference marks a debit unpaid only when it fits exactly one debit presented on or before the line's date; otherwise it goes to the queue and no debit is changed (see How lines are matched). The batch file sends Netcash the mandate's reference, not one per debit, so returns can be expected to name only the mandate, and matching considers the debits of the last 60 days: from a monthly mandate's second debit on, practically every return fits more than one debit. Those returns are not marked unpaid, re-presented or chased automatically, and the debit stays complete (its invoice paid) until you mark it Unpaid on the mandate's Collections list. Linking the line in reconciliation records which debit it belongs to but does not mark the debit unpaid.
  • Re-importing the same statement does not create duplicate lines.
  • Results are available through the Reconciliation results API and the reconciliation.completed webhook.

Who can do what#

Debit order permissions (built-in roles)
ActionWho
View mandates, batches, agreements and the reportAll users, including viewers
Create and edit mandates, mark signed, pause, resume, cancel, mark unpaidStaff and admins
Send, resend, amend and cancel agreementsStaff and admins
Approve or reject mandates (mandates:approve)Admins
Approve, reject or trim batches (debit_orders:approve)Staff and admins
Change debit order settings and the agreement template, Run now (debit_orders:settings)Admins

These are the defaults of the built-in roles. Custom roles under Settings → Roles can grant or withhold each of these permissions separately (see Roles).

What you can do via the API#

API support for debit orders
TaskAPI
Create a mandate (emandate, agreement or offline authority)POST /api/v1/mandates
List mandates and get one, with its stage and agreementsGET /api/v1/mandates
Change amount or debit day; pause, resume or cancelPATCH /api/v1/mandates/{id}
Issue an agreement for online signing (optionally without emailing it)POST /api/v1/mandates/{id}/agreement
Check the outcome of a debit order collectionGET /api/v1/transactions/{reference} with the DO…-YYYYMMDD reference
Approve or reject mandatesDashboard only
Run batches, review batches, mark unpaidsDashboard only
Debit order settings, agreement template, debit order reportDashboard only
Read reconciliation results (totals, matches, exceptions)GET /api/v1/reconciliation/runs
Read statement lines and per-account reconciliation healthGET /api/v1/reconciliation/lines, /accounts
Import statements, resolve reconciliation exceptionsDashboard only