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
15 matching entries · Page 1 of 2
List verification history · Programme management · all
NSIPA local workflow
Provisional guidance
Trace approval and correction decisions by revision.
What to do
- Check the Revision shown on the list.
- Read each event’s stage, decision and recorded comment.
- Open the attached evidence only if it is needed for an authorised review.
What you need
Earlier revisions can show decisions that belong to an earlier approval chain.
Next step
Use the current revision for approval and export checks.
Published version 1 · 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?
Disbursement list details · Programme management · all
NSIPA local workflow
Provisional guidance
Check the selected list before an operational decision.
What to do
- Read Status, Revision, NOB and Total NGN.
- Open Approval for the current decision, Beneficiaries for included rows, or Verification history for earlier actions.
What you need
Check the current cycle and revision.
Next step
Refresh the list when its status or actions appear out of date.
Published version 1 · public guidanceOpen this guide · Download plain text
Was this guide helpful?
Enrollment lists and workflow · Programme management · all
NSIPA local workflow
Provisional guidance
Inspect the enrollment settings and lists for one programme.
What to do
- Confirm the programme, frequency and required verification settings.
- Open the relevant list to see its result and history.
- Create a new list from its enrollment cycle when the workflow allows it.
What you need
Check the displayed automatic approval configuration.
Next step
Use the approved enrollment result when moving to disbursement.
Published version 1 · 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?
Record final list approval · Programme management · all
NSIPA local workflow
Provisional guidance
Record the final decision for the current disbursement revision.
What to do
- Confirm the current revision has Finance and Audit approvals in Verification history.
- Complete the approved final checks and enter Approval comment.
- Choose Approve and save or Reject and save.
What you need
Use the assigned final approval group. For a corrective payment, review the authorised case reference and the Finance and Audit evidence for this separate list. For a further payment after two reversals, check the escalation decision reference. This action approves the current list revision. After case reopening, confirm the separate payment authorisation and the Finance and Audit approvals for this revision. Payment submits the approved list after routing is ready.
Next step
Approval sets Fully verified. Rejection returns it to Programme Admin for correction.
Published version 4 · 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?
Verification queue · Programme management · all
NSIPA local workflow
Provisional guidance
Find lists requiring evidence or verification.
What to do
- Confirm the programme, cycle and list status.
- Open the list and compare the existing evidence with the approved checklist.
- Where available, record verification and check the history.
What you need
A completed verification and final approval are separate workflow steps.
Next step
Check the list’s next status after saving.
Published version 2 · public guidanceOpen this guide · Download plain text
Was this guide helpful?
Approval queue · Programme management · all
NSIPA local workflow
Provisional guidance
Find lists awaiting a decision and open the appropriate workflow.
What to do
- Check the programme, cycle and current status.
- Open the matching list and read the verification history before deciding.
- Use the controls shown for your assigned approval stage.
What you need
The approval flow and permitted actions depend on the programme and list state.
Next step
Open the programme approval flow to see sequential Finance, Audit and CEO stages where configured.
Published version 2 · 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?
Decide at Audit stage · Programme management · all
NSIPA local workflow
Provisional guidance
Record the Audit decision on the current revision.
What to do
- Check the Finance approval in Verification history for the same revision.
- Complete the approved Audit checks and enter Approval comment.
- Use the decision action shown to your account.
What you need
The current revision requires an independent approver at each level. For a corrective payment, verify that the case reference links the original reversal evidence and the separately reviewed list. After two reversals, trace the new list to both reversal records and the escalation decision reference. After case reopening, trace the closure, reopening and payment authorisation to the new list and its revision. Check both the Finance decision and the retained prior records.
Next step
Approval moves the list to Awaiting CEO. Rejection returns it for correction.
Published version 4 · public guidanceOpen this guide · Download plain text
Was this guide helpful?