Ask the local knowledge assistant
NSIPA knowledge library
Task guidance for each service and workflow stage. Local guides describe NSIPA; upstream references may describe other releases. Your account determines available actions.
531 published entries across 18 services · 64 source-linked guides
19 matching entries · Page 1 of 2
Correction reason · Programme management · all
NSIPA local workflow
Provisional guidance
Describe the reason for changing the amount or inclusion on the disbursement list. The reason is required to save the correction and is recorded in list history.
Published version 1 · public guidanceOpen this guide · Download plain text
Was this guide helpful?
Correction reason has been addressed · Registration review · all
NSIPA local workflow
Provisional guidance
Open Review history or the latest return reason when present. Compare the reason with the current case.
What you need
If any requested change remains unresolved, send the same case back with a specific reason.
Published version 1 · public guidanceOpen this guide · Download plain text
Was this guide helpful?
Complaints and enquiries · Beneficiary portal · all
Upstream reference — confirm feature availability
Provisional guidance
Submit a structured complaint for your own registered household and follow the case through the existing NSIPA staff review process.
What to do
- Select the complaint reason: payment delay, account issue, registration correction or service quality.
- Select Submit complaint once and wait for the case to appear in My cases. A retry of the same submission does not create a duplicate case.
- Open the case to read its reference, current status, submission date, response deadline and resolution deadline.
- Return to this screen or Notifications to check for staff acknowledgement, escalation or resolution.
What you need
Sign in with a beneficiary account that has a household registration. Use fictional information in this demonstration environment.
Next step
Keep the case reference for follow-up. NSIPA staff handle the case through their existing grievance workspace; a beneficiary cannot acknowledge or resolve their own case.
Common issues
Register a household first if submission is unavailable. This installed workflow accepts a structured reason and does not accept attachments or free-text descriptions. After a network error, refresh My cases before starting a new submission.
Published version 4 · public guidanceOpen this guide · Download plain text
Was this guide helpful?
Respond to a returned registration · Household registration · all
NSIPA local workflow
Provisional guidance
Use reviewer feedback to correct the original household submission.
What to do
- Open the returned record.
- Read the reason for correction.
- Update the relevant fields and check the household members and location.
- Resubmit through the form when the application allows it.
What you need
Access to the returned household and its feedback.
Next step
Track the new review status.
Common issues
Correct the original record instead of making a duplicate application.
References
Sources checked: 2026-10-05
Published version 3 · public guidanceOpen this guide · Download plain text
Was this guide helpful?
Coordinate reversal follow-up · Programme management · all
NSIPA local workflow
Provisional guidance
Connect the reported reversal to the original programme, cycle and approved list.
What to do
- Check the programme, cycle and revision against the submitted list and Verification history.
- Keep the original approved list and payment reference in the case record.
- Give Payment and Finance the list, envelope and batch references through the authorised follow-up process.
What you need
The submitted payment report supports refresh and download. List correction and sponsor bank routing are locked for this submission.
Next step
Coordinate supporting information for the reconciliation owner. Route any proposed corrective action through the authorised process. If this is a corrective payment that has also reversed, link both submitted lists, their revisions and both envelope and batch references in the existing case. Notify Payment and Finance that the case remains open. If the CEO authorises another payment, prepare a separate disbursement list and link it to the decision and both reversals. If the CEO closes the case, archive both submitted lists and their references with the closure record. If a reversal is recorded after case closure, request reopening under the same case reference. Link the newly reversed payment and the closure decision to the existing case. If a new payment is authorised after reopening, prepare a separate list for the authorised amount. Link the reopening, new authorisation and earlier reversal records to that list under the existing case reference. If that newly authorised payment also reverses, keep the reopened case active during review and link the new reversal and bank reason to its approval, envelope and batch. If the CEO closes the reopened case, archive all submitted lists and payment references with the new closure decision and retain the earlier closure and reopening records. If the bank reports a possible duplicate after closure, log the confirmed duplicate under the existing case reference and retain the closure decision. Send unmatched evidence to the reconciliation owner. If the amounts differ, log the amount discrepancy under the existing case reference. Attach both statements and the approved list, envelope and batch references.
Published version 9 · public guidanceOpen this guide · Download plain text
Was this guide helpful?
Correct a returned list · Programme management · all
NSIPA local workflow
Provisional guidance
Apply the authorised changes requested by the reviewer.
What to do
- Read the rejection reason for the current revision in Verification history.
- In Beneficiaries, choose Correct on the affected row.
- Update the authorised amount or inclusion, enter a Correction reason and choose Save correction.
- Check the saved change and list total before handing the list to Payment.
What you need
Use the assigned Programme Admin account.
Next step
The correction stays on the current revision. Payment resubmits the same list to create a new revision starting at Finance.
Published version 2 · public guidanceOpen this guide · Download plain text
Was this guide helpful?
Follow a returned disbursement list · Programme management · all
NSIPA local workflow
Provisional guidance
See why the current revision was returned and who acts next.
What to do
- Open Verification history and read the rejection reason for the current revision.
- Programme Admin reviews the reason and records any required correction in Beneficiaries.
- Payment resubmits once the return has been addressed.
What you need
Decision controls are unavailable while the list is Returned for correction.
Next step
Resubmission starts a new revision at Finance. Earlier decisions remain in Verification history.
Published version 1 · public guidanceOpen this guide · Download plain text
Was this guide helpful?
Hand over the corrected disbursement list · Programme management · all
NSIPA local workflow
Provisional guidance
Check the saved correction and hand the existing list back to Payment.
What to do
- Review the correction in Verification history against the rejection reason.
- Check the affected beneficiary row, inclusion and list total. If more changes are needed, open Beneficiaries and use Correct.
- Once the return is addressed, hand the programme, cycle and revision to the assigned Payment user.
What you need
The correction is recorded on the current revision. The list remains Returned for correction until Payment resubmits.
Next step
Payment uses Resubmit for approval. The new revision starts at Finance.
Published version 1 · public guidanceOpen this guide · Download plain text
Was this guide helpful?
Resubmit a corrected disbursement list · Programme management · all
NSIPA local workflow
Provisional guidance
Send the corrected list through a fresh approval chain.
What to do
- Compare the rejection reason and Programme Admin correction in Verification history.
- Review the affected beneficiaries, included count, amount and list total.
- Add a submission comment if needed, then choose Resubmit for approval.
What you need
Confirm all requested changes are addressed before resubmitting.
Next step
Check that the new revision shows Awaiting Finance. PBMS increases the revision number. Prior decisions remain visible under the earlier revision.
Published version 2 · public guidanceOpen this guide · Download plain text
Was this guide helpful?
Review the return before resubmitting · Programme management · all
NSIPA local workflow
Provisional guidance
Check what the reviewer requested and whether the return has been addressed.
What to do
- Read the current revision’s rejection reason in Verification history.
- Confirm with Programme Admin that each requested change or clarification has been addressed.
- Review the current rows and totals before using Resubmit for approval.
What you need
Use the same returned list. If a correction is still needed, ask Programme Admin to save it before you proceed.
Next step
Resubmission creates a new revision and moves the list to Awaiting Finance.
Published version 1 · public guidanceOpen this guide · Download plain text
Was this guide helpful?
Submission comment · Programme management · all
NSIPA local workflow
Provisional guidance
This comment is optional for Payment when initiating or resubmitting a list. On a return, you can summarise how the correction addressed the reviewer’s reason. PBMS records the comment with the submission in Verification history.
Published version 1 · public guidanceOpen this guide · Download plain text
Was this guide helpful?
Correct a returned import · Master Beneficiary Registry · all
NSIPA local workflow
Provisional guidance
Apply the reviewer’s requested corrections in the existing batch.
What to do
- Read the return reason above the batch totals.
- Open affected rows and correct or exclude values as authorised.
- Check validation counts and use Send for approval again.
What you need
The owner edits a returned batch.
Next step
Confirm it appears in the review queue after resubmission.
Published version 1 · public guidanceOpen this guide · Download plain text
Was this guide helpful?