NGO Payroll Management in Pakistan: Grant Allocation and Currency Controls

01NGO payroll management needs two linked control systems

Payroll answers what an employee is due under the organisation’s approved employment terms. Grant accounting answers which funding source may bear an eligible share of that cost. Combining these questions into a single spreadsheet column makes both harder to verify. A clear handoff gives HR, programme staff and finance a shared basis for review.

For a practical starting point, connect payroll and accounting records without conflating them. PayPeople’s payroll software page describes payroll workflows; the organisation still needs its own donor eligibility review and finance controls. The organisation can also review its payroll compliance workflow as a separate operational control. An NGO may run one monthly payroll for employees working across projects, locations or funding streams. A salary is still calculated from approved employment records and payroll inputs. A project allocation is a subsequent accounting decision supported by the work performed, the grant agreement, the approved budget and the organisation’s documented method. A funding shortfall or a grant ending does not by itself change an employee’s agreed salary.

This distinction matters in Pakistan, where an organisation may have staff in different provinces, multiple donors and a mix of local-currency and foreign-currency budgets. Do not assume one payroll or reporting rule applies to every NGO, donor or employee. Verify current obligations and agreement-specific conditions with appropriate local advisers and the donor documentation.

Illustrative example: A Pakistan-based NGO employs a programme officer with an approved monthly salary in PKR. The officer records work for two grant-funded programmes and a small organisation-wide responsibility. After the time or other approved allocation evidence is reviewed, finance applies the organisation’s documented method to the eligible payroll cost. The pay calculation remains one employee-level calculation; the ledger may contain several funding shares. The example does not imply that every donor accepts timesheets or any particular percentage.

02Design a defensible grant-funded cost allocation

Start with the signed funding terms, not with the available budget balance. A sound allocation connects a real cost to the benefit received, uses a consistent and reviewable basis, and avoids charging the same cost twice. Apply the same documented logic consistently and retain enough evidence for another reviewer to reproduce the result.

For each grant, make a short reference sheet from the agreement and approved budget: eligible personnel categories, permitted budget lines, grant dates, required approval or notification for budget changes, reporting currency, reporting period and supporting documents. Flag ambiguous wording for clarification before charging. The project manager may explain the work, but finance should verify the funder’s restrictions and the organisation’s accounting policy.

Choose an allocation basis suited to the work and permitted by policy and agreement. Where staff split time between activities, contemporaneous time records may be relevant if required or accepted. For a role whose work is consistently dedicated to one project, a documented assignment and supervisory confirmation may be appropriate if the applicable rules allow it. Avoid an arbitrary equal split, a retrospective estimate made only to use a grant balance, or a percentage copied forward after responsibilities change.

Document the numerator, denominator and period for any calculation. For a time-based allocation, explain what constitutes total working time and how leave, holidays, training or organisation-wide duties are treated. Keep the evidence in proportion to the donor and internal requirements. Corrections should preserve the original record, show who changed it, when, why and who approved the correction.

The table is a control prompt, not a substitute for a donor’s format. If the grant specifies a different basis, document that requirement and align the internal workflow accordingly. When donor guidance conflicts with the organisation’s established process, escalate rather than quietly changing the allocation.

03Make currency handling explicit from budget to report

A salary paid in PKR and a grant budget presented in another currency are not interchangeable figures. The exchange-rate convention affects comparisons and reporting, so identify the governing instruction before building a conversion workflow. A written method makes reporting-period comparisons reviewable and prevents undocumented assumptions.

Confirm whether the agreement and reporting instructions specify the currency for budgets, expenditure, advances and final reports, and whether they prescribe a rate source or conversion date. Some arrangements may distinguish the organisation’s functional accounting currency from the donor’s presentation currency. Do not assume that a bank rate, invoice date rate, monthly average or receipt-date rate is universally correct.

Maintain the original payroll amount and currency, the accounting entry, the conversion method and any converted report figure as traceable fields or linked records. Note the source and date of the rate, the person who applied it, and any rounding convention. If funds arrive in instalments, do not treat each receipt as permission to recalculate an employee’s salary. Payroll commitments and donor-budget monitoring are separate.

When a report is prepared, reconcile the amount charged in the ledger to the amount presented in the donor currency. Explain timing or exchange differences using the prescribed method and keep calculations with the reporting pack. If instructions are silent, ask the donor or obtain documented professional advice; avoid inventing a policy after the reporting period has closed.

View Full Size

View Full Size

View Full Size

04A repeatable monthly workflow for HR and finance

A calendar with named owners makes it less likely that a grant allocation is improvised at the reporting deadline. Lock employee pay inputs first, then complete allocation, reconciliation and donor-ready review. Use dated cutoffs and preserve the version of each source record used.

1. 01
   1. Confirm the employee and payroll period

   HR checks active status, approved salary changes and relevant payroll inputs against authorised records. Preserve a dated record of approvals and changes.

2. 02
   2. Gather work and project evidence

   Project supervisors confirm assignments or review submitted activity records under the organisation’s approved policy. Return incomplete or inconsistent records for correction before finance allocates costs.

3. 03
   3. Run and review payroll

   Payroll calculates gross pay, deductions and net pay using the organisation’s reviewed settings and applicable requirements. An authorised reviewer checks exceptions before payment.

4. 04
   4. Apply grant eligibility and allocation

   Finance checks the agreement, budget and period; applies the documented basis to eligible costs; and records any unrestricted or non-chargeable share separately.

5. 05
   5. Post and reconcile

   Compare payroll totals to the payroll liability and expense entries, then compare project allocations with the payroll source total. Investigate differences rather than forcing the entries to agree.

6. 06
   6. Prepare donor reporting evidence

   Map ledger accounts and cost categories to the donor template, verify currency treatment and attach or retain requested supporting documentation under access controls.

7. 07
   7. Close, approve and archive

   A person independent of preparation reviews the reconciliation and report. Save the final schedule, approvals, source versions and submission confirmation in the correct grant folder.

Use approved attendance records where they form part of payroll inputs. Set practical cut-off dates for timesheets, payroll changes, supervisor approval, finance review and report preparation. Late changes should be handled through a documented correction process, not by editing a previously approved record without a trail. If the donor requires a report on a different timetable from payroll, identify the payroll periods included and avoid counting a cost twice across periods.

05Assign clear responsibilities and independent review

Segregation does not require a large finance department. It requires clarity about who supplies evidence, who calculates, who authorises and who verifies the final charge. Written ownership reduces the risk that an unsupported allocation passes because everyone assumes someone else checked it.

• HR maintains employee records, approved terms and authorised payroll changes; it does not decide grant eligibility alone.
• Employees submit accurate activity or time records where the policy requires them; supervisors review whether the evidence reflects work performed.
• Project leads confirm project activity and flag scope changes; they should not approve unsupported charges merely because a budget has room.
• Payroll prepares employee calculations and explains exceptions; a designated reviewer authorises the payroll run.
• Finance interprets budget coding, allocation method, exchange documentation and ledger reconciliation against written policy and grant terms.
• An authorised senior approver reviews material exceptions and donor reports; an independent checker tests traceability and completeness.

Record role substitutions for small teams. If the same person performs two steps, add a compensating review by a board-authorised or otherwise independent person as appropriate to the organisation’s governance. Keep approval evidence dated and attributable. A workflow is not controlled simply because several people can access the same spreadsheet.

06Common mistakes that undermine confidence

Most allocation problems are not complex arithmetic errors. They arise when a reasonable-looking figure cannot be connected to an approved method, evidence and grant instruction. A monthly close should surface these issues early enough to correct them before a report is submitted.

• Charging salary by remaining budget: available funds do not establish that a cost is eligible or attributable.
• Using one allocation percentage indefinitely: duties and grants change, so reassess the basis for each relevant period.
• Treating a budget currency as payroll currency: preserve the actual salary and separately document any reporting conversion.
• Using a retrospective timesheet without a correction trail: retain the original, reason for correction and approvals.
• Reporting gross salary as the full grant charge without considering policy: determine which payroll-related components are eligible under the agreement and accounting rules.
• Mixing employee records and donor-facing access: give each role access only to the information needed for its task.
• Failing to reconcile: tie donor totals to project ledger entries and payroll source records before submission.
• Assuming tax or statutory treatment is identical for every NGO: obtain current advice for the organisation, employee and location; do not rely on a generic article.

If an error is found after posting or reporting, follow the organisation’s correction and notification procedures. Assess whether the grant agreement requires donor disclosure or approval. Keep the correction visible and traceable; do not overwrite records to make a past report appear consistent.

07Put the process into operation without overcomplicating it

Begin with a small set of live grants and a defined payroll cycle. Test the handoffs and evidence before expanding the coding structure or introducing more detailed reporting. Make the first test small enough to investigate every exception and obtain feedback from users.

Create a grant register that records project code, funder, approved dates, budget version, permitted personnel categories, reporting currency and responsible staff. Link it to a controlled chart of accounts or project codes, but avoid creating so many codes that staff cannot select the correct one consistently. Restrict changes to authorised finance personnel and retain change history.

Run a parallel review for one closed payroll period: reconstruct the employee cost, allocation evidence, ledger postings and donor-report mapping. Ask an independent reviewer to trace a sample from employee record to report and back. Resolve inconsistent names, periods, rounding and missing approvals before the next close.

Payroll software can support consistent employee records, approved changes, payroll calculations and payroll reports. It does not automatically determine whether a donor accepts a cost, select the correct exchange-rate rule or replace agreement review. Evaluate whether the system exports information finance can map and reconcile, and whether access permissions and audit records fit the organisation’s controls.

Keep a written procedure concise enough to use: who acts, which evidence is required, by when, what exceptions trigger escalation, and where final records are stored. Review it when a grant agreement, reporting format, staffing arrangement or applicable requirement changes.

Summary

NGO payroll management starts with verified payroll records and a separate, documented grant-control process. Allocate eligible costs using agreement terms, evidence and a consistent method; document currency conversion, reconcile before reporting and assign named reviewers. Obtain current professional guidance for legal, tax, donor-specific or accounting questions, since requirements differ among organisations and grants. Match each charge to evidence and agreement terms, explain currency conversion, reconcile before reporting and assign named reviewers. For legal, tax, donor-specific or accounting questions, use current professional guidance rather than assuming one rule applies to every organisation.

Next step: see how this works in PayPeople Payroll Software.