Disbursements
Disbursements is where you pay people money that is not part of a payroll cut-off: monthly incentives, allowance runs, month-end cash and similar. Each payment batch is a run with its own list of employees and amounts, its own approval, and its own bank file, cash list and journal. Released amounts also feed each employee's yearly tax figures, and appear on the payslip. A run type can instead be paid through payroll: the run is then sent into an open payroll cut-off and paid with the salary, with no bank file of its own (see Pay Through Payroll below). Who must approve a run is set per run type (see Approvers below).
Opening Disbursements
- Open HR → Special Pay → Disbursements
The page has two tabs: Runs and Run types.
Access is controlled by permissions. Seeing the page needs Disbursement access; creating and editing runs, approving, releasing and exporting files are each separate permissions (Create/Edit Runs, Approve, Release, Export Files), so you can split the duties between people.
Run Types
A run type describes one kind of payment, for example a monthly incentive. Set the types up once, then start a run from the type each time.
Creating a Run Type
- Open the Run types tab and click New run type
- Fill in the dialogCodeA short unique code for the type.NameWhat people will see when picking the type.Computed sourceHow the amounts are worked out. Leave it as None (manual / import) if lines are typed in or imported from Excel. The built-in sources are Flat amount to a group of employees, Perfect Attendance incentive, and PQD reward. (Old Fringe benefit runs stay read-only; the fringe benefit is now paid as an allowance through payroll.)Default tax treatmentSee Tax Treatment below. For a type paid through payroll this also decides which allowance bucket the lines land in.How the run is paid (Paid through)Own bank file (default): the run has its own bank file, cash list and journal and is paid outside payroll. Payroll cut-off: the run is sent into an open payroll cut-off and paid as an allowance line on the payslip. Payroll cut-off is available for Flat amount, Perfect Attendance, PQD reward and Leave conversion types only; a Fringe benefit tax treatment cannot be paid through payroll. The choice is locked while live runs use the type.ApproversThe ordered approval stages for this type. Empty means computed runs approve themselves. See Approvers below. Changing approvers needs the Approve permission.Debit account / Credit accountThe accounts used in the journal, picked from the chart of accounts only. The debit side is split by cost centre. With no chart of accounts in Treasury, Accounting the pickers are disabled and the screen says to set the chart up first. A saved account that has since left the chart is flagged, and the journal is blocked until you pick another. A per-line override is held to the same rule.ActiveWhether the type is in use.
Starting a Run
- On the Runs tab, click New run
- Fill in the runRun type*The kind of payment.Title*A name for this batch.Period start / Period end*The period the payment is for. For incentive types the dialog pre-fills the most recent completed window; you can change it.Pay date*When the money is paid. (Not shown for a type paid through payroll: the pay date is the chosen cut-off's pay date.)Payroll cut-off*Only for a type paid through payroll. Lists the cut-offs that are still open (Time keeping or Pending), best match for the run's period first; Show older reveals earlier ones. The run is paid as allowance lines in this cut-off, so its pay date becomes the cut-off's pay date and it counts in that pay date's tax year. If no cut-off is open the field says so; generate or reopen one in Payroll Center first.Journal memo currency (optional)A second currency shown beside the journal amounts: a 3-letter code, a rate (company currency per 1 unit of memo currency) and the rate month. It is for the exported journal only.NotesFree text.
The Runs tab can be filtered by Pay year, run type and status, and lists each run's reference, title, type, pay date, number of lines, total, status and next step. The Run lifecycle strip above the list counts the runs at each step; click a step to list only those runs, and click it again to show all.
For Perfect Attendance and PQD types the dialog shows the scheme settings the run will use; Adjust for this run changes them for this run only. The memo currency fields show what ₱1,000.00 becomes in the journal at the rate you type.
Run Status
| Status | Meaning |
|---|---|
| Draft | Being prepared. Lines can be added, imported, edited and removed. |
| Computed | Amounts have been worked out and checked. The run waits for its approvers (or, with no approvers, is approved at once). Editing anything sends it back to Draft. |
| Approved | Locked for payment. The bank file, cash list and journal can be exported; a payroll-paid run is ready to be sent to payroll. |
| In payroll | Payroll-paid runs only. The lines are allowance earnings in the chosen cut-off and the run is paid when that cut-off is posted. It can be taken back while the cut-off is open. |
| Released | Paid. Amounts now count towards each employee's yearly tax figures and show on the payslip. A payroll-paid run becomes Released by itself when its cut-off is posted. |
| Cancelled | Voided, with a reason. |
Working a Run
Open a run from the list. The top shows where the run is in its lifecycle and the next step, with a button for it. Below are the total, how much goes to each bank, how much is paid in cash and any accrual-only amount, then four tabs: Lines (the employees and amounts, with a search box and a total), Assessment (the issues and, for incentive runs, each employee's verdict), Files (bank files, cash list and journal) and History (who approves, where the approval stands, and every event on the run).
The one big button at the top is always the next step (Compute, Approve, Release or Send to payroll). Everything else sits in the More actions menu: Edit run, Add line, Import Excel, Recompute, Send back, Take back from payroll, Reopen and Cancel run, each shown only when it applies to you and the run's status.
Adding Lines
While the run is Draft or Computed you can build the list three ways:
- Add line — pick the Employee and enter the Amount, Tax treatment, Memo, Reference and Cost centre (blank means the employee's department, else branch). Untick the paid-to-employee box to record an accrual-only journal line that is not paid out.
- Import Excel — download the template and fill in Employee Code, Amount, Tax Treatment, Memo, Reference and Cost Centre. If any row has a problem the whole file is rejected with the row numbers, so nothing is half-imported. You can choose to replace lines imported earlier.
- Compute — for types with a computed source, the system creates the lines for you. Changing a computed amount by hand asks for a reason, and the line is marked as overridden and keeps your amount when the run is recomputed.
Removing a line asks for confirmation. Lines of an old Fringe benefit run are read-only (only the memo and cost centre can change).
Checking Before Approval
Under the next step, red issues block approval and release (the Approve button stays disabled) and amber issues are worth checking. Each one says how to fix it.
- Blocking: no payable lines; an employee no longer in the company; the same employee already paid in another live run of the same type for an overlapping period.
- Warnings: an inactive employee; a possible duplicate line; incomplete bank details (paid through the cash list); de minimis lines treated as fully exempt; a taxable or Other benefit payment that no remaining payroll will withhold tax on.
A deliberate second payment can be accepted with Acknowledge duplicate (Approve permission, reason of at least 5 characters). The issue turns into a warning that records who acknowledged it and why.
Approving and Releasing
- Click Compute (if the type has a computed source)
- Review the lines and click Approve
Needs the Approve permission. The person who computed the run can never approve it; the page then says it is waiting for the approvers of the current stage (see Approvers below). Use Reopen in More actions to go back and change lines.
- Export the payment files
Once the run is Approved or Released, the page offers one bank file per bank (for example RCBC or BDO, one download button per file the bank uses; a payee whose bank is not chosen from the list is flagged and left out) for employees paid by bank, a Cash list for employees without a bank account, and the Journal, split by cost centre. The journal is an export for your accountants; nothing is posted to the ledger. It is produced only when the company has a chart of accounts and every account on it is still active in that chart.
- Click Release when the money has been paid (own-bank-file runs)
Needs the Release permission. A confirmation says what releasing does; afterwards the run can only be cancelled. A run paid through payroll has no Release button: you send it to payroll and posting the cut-off releases it (see Pay Through Payroll below).
Cancelling a Run
Click Cancel run and give a reason. If the run was already Released, the lines are removed from the employees' taxable income and the pay year's open payroll computations are flagged for recompute, but money that was already paid is not reversed. You must handle that separately.
Approvers
Every run type says who must approve its runs. You set this once on the run type, in the Approvers part of its dialog (changing approvers needs the Approve permission). A type has up to 5 approval stages, done in order; each stage is one of three kinds.
| Type setup | What happens when a run computes cleanly |
|---|---|
| No approvers | The run is approved automatically (status Approved, history says "Approved automatically: this run type has no approvers"). Nobody is asked. |
| One or more stages | The run stays Computed and the first stage's approvers each get a task in their inbox ("You have a new task to review: disbursement run ..."). When a stage is approved the next stage's approvers are asked; the run is Approved after the last stage. |
Approving or Sending Back
An approver opens the task from their inbox (it shows the run, its total, the payroll cut-off for a payroll-paid run and who computed it, with a link to the run) or opens the run itself. They choose one of two things.
The History tab shows each stage as Done, Current or Waiting, who decided it and when, or the names of the people who can ("Any of: ..."). Stages that were skipped are listed too.
The Person Who Computed Can Never Approve
The person who computed a run is removed from every stage of that run, whatever their permissions. A stage that is left with nobody else is skipped when other stages remain.
| Run type approvers | Computed by | Result |
|---|---|---|
| None | Maria | Approved automatically at once. |
| Stage 1: Maria and Joseph (people) | Maria | Stage 1 waits for Joseph only. Maria cannot approve her own run. |
| Stage 1: Maria (people) | Maria | Blocked: No one else can approve this run. Add another approver, then compute again. |
| Stage 1: Maria. Stage 2: Direct supervisor | Maria | Stage 1 is skipped (only Maria); the supervisor of Maria is the single stage. |
Pay Through Payroll
Some payments are better paid with the salary than in a separate payout: a monthly perfect-attendance incentive, a flat allowance, a leave conversion. Set the run type's Paid through to Payroll cut-off and its runs are sent into an open payroll cut-off. Each line becomes an allowance earning for that employee, payroll taxes it, pays it with the cut-off, and the payroll journal books it. There is no bank file, cash list or disbursement journal for the run.
Which Run Types Can Be Paid Through Payroll
Flat amount, Perfect Attendance, PQD reward and Leave conversion types can. The fringe benefit is not a run any more: it is an allowance paid in the payroll cut-off (see Set Up Fringe Benefit Tax), and the old Fringe benefit (employer-paid FBT) tax treatment has no allowance equivalent. The choice cannot be changed while live runs use the type.
How the Tax Treatment Becomes a Payroll Bucket
The type's Default tax treatment decides which allowance the lines become. All lines of a payroll-paid run must use the type's treatment; otherwise the run is blocked until you change the lines or use another type.
| Tax treatment | Becomes in payroll | Effect in the cut-off |
|---|---|---|
| Taxable compensation | Taxable allowance, regular compensation | Part of the cut-off's taxable pay; tax is withheld in that same cut-off. |
| Other benefit (shared 90,000 pool) | Taxable allowance, other benefits | Exempt only while the employee's 90,000 pool (13th month and other benefits) has room; the excess is taxable. |
| De minimis | De minimis allowance | Exempt, reported on the de minimis line. |
| Non-taxable | Non-taxable allowance | Added to gross but exempt. |
| Fringe benefit (employer-paid FBT) | Not allowed | Cannot be paid through payroll. |
The run type keeps its own hidden allowance type, named after the run type (for example "Perfect Attendance"); it is what the payslip shows as the earning's name. You never assign it to a plan.
Sending a Run to Payroll
- Pick the cut-off when you create the run
See Payroll cut-off in Starting a Run. A cut-off that is no longer open is a blocker (Payroll cut-off ... is no longer open): choose one that is still open.
- Compute, then get the run approved
Approval works as in Approvers above.
- Check the Assessment tab
Besides the usual issues, a payroll-paid run is blocked when no cut-off is chosen, when the cut-off is no longer open, when employees are not in that cut-off (the message names them: remove them or pick a cut-off that includes them), and when a line's tax treatment differs from the type's.
- Click Send to payroll (Release permission)
A confirmation says: "N line(s) totalling the amount go into payroll cut-off X. Each line becomes an allowance earning for the employee in cut-off X and the cut-off is recomputed. They are taxed as ... The run is marked Paid when the cut-off is posted. Until then you can take it back." The run becomes In payroll.
- Post the cut-off in Payroll Center
When the cut-off is posted the run becomes Released automatically ("Paid in cut-off X"). If the posted cut-off is later returned to pending, the run goes back to In payroll.
Take back from payroll (More actions, Release permission) removes the allowance lines from the cut-off, recomputes it and returns the run to Approved. It works only while the cut-off is open (Time keeping or Pending); once the cut-off is submitted for approval or posted, the run is committed. Cancelling a run that is In payroll withdraws its lines from the cut-off in the same step. If the cut-off has already been posted, first return it to pending (Cancel posted payroll); the run then goes back to In payroll and can be cancelled.
Where It Shows: Salary Detail and the Payslip
In Salary Detail the line sits under the allowance group of its bucket with a locked chip, From disbursement DISB-..., instead of the usual Manual chip. It cannot be edited or deleted there: clicking it opens the run, which owns the line. The payslip lists it among the allowances as Name (From disbursement DISB-...), and it counts in gross pay and net pay like any allowance.
| Run type | Perfect Attendance, paid through Payroll cut-off, tax treatment Taxable compensation | |
|---|---|---|
| Employee line | ₱200.00 | |
| Becomes in the cut-off | → | Taxable allowance (regular compensation) ₱200.00 |
| Employee earnings before the line (illustration) | ₱12,000.00 | |
| Gross pay in the cut-off | + ₱200.00 | ₱12,200.00 |
| Tax on the extra ₱200.00The payroll engine works it out with the rest of the pay; there is no year-end catch-up for this line | Withheld in this Oct 16 - 31 cut-off |
No Double Counting
A payroll-paid run is already inside the payroll rows, so it is left out of the places a separate payout would feed: it does not appear under Other payments this period on the payslip, and it is not added again to the year-end figures from Disbursements (annualization, alphalist, 2316). Those read the amount once, from payroll. It also needs no Release step and has no bank file or cash list; the payroll journal books the pay.
The Files tab of such a run says so: "Payroll pays this run inside the cut-off, so it has no bank file, cash list or journal of its own." To see the money, open the cut-off in Payroll Center (the run page links to it).
Tax Treatment of Lines
Each line carries a tax treatment that decides how it counts in the year-end figures:
| Treatment | Effect |
|---|---|
| Taxable compensation | Added to the employee's annualized taxable income (year-end true-up, alphalist, 2316). |
| Non-taxable | Exempt compensation, reported under other non-taxable. |
| Other benefit (shared 90,000 pool) | Exempt only up to the one annual 90,000 pool shared with payroll (13th month and other benefits); the excess is taxable. |
| De minimis | Exempt de minimis benefit, reported on the de minimis line. |
| Fringe benefit (employer-paid FBT) | The employer bears the tax; never part of the employee's taxable income. |
On the Payslip
(This section is about runs with their own bank file. A run paid through payroll shows as an allowance earning instead; see Pay Through Payroll above.) A payment released in a run shows on the employee's payslip, on the web and in the mobile app, under Other payments this period. It is shown for information and does not change gross pay, deductions or net pay. See Payslip Center.
Which payslip? The one for the cut-off period that contains the run's pay date, on each employee's own cut-off. The run list shows it in the Payslip period column (for example Oct 16 - 31, 2026), and the run dialog shows it under the pay date as you pick it. Before a run has lines, every cut-off of the company is checked; once it has lines, only the cut-offs of its employees count, so a run that pays a semi-monthly and a monthly employee shows both periods (+1 more).
Related Topics
- Run a Disbursement — the tutorial, with a worked example
- Incentive Schemes — Perfect Attendance and PQD
- Fringe Benefit Tax — the settings for the fringe benefit allowance
- BIR 1603Q Fringe Benefit Tax — the quarterly report
How It Connects
Set up first
- Incentive Schemes — the rules behind the Perfect Attendance and PQD run types.
- Cost Centres (Treasury) — every line carries an active cost centre, and the journal splits its debit side by it.
- Payroll Journal — its cost-centre mappings supply a line's cost centre when none is typed.
Gets its data from
- Employee Records — each employee's bank details decide whether a line goes to a bank file or the cash list.
- Payroll Center — a run paid through payroll needs an open cut-off to be sent into.
- Payroll Time Keeping — attendance-driven runs (Perfect Attendance, PQD) read the daily attendance results.
Feeds into
- Payslip Center — a released payment shows on the payslip under Other payments this period.
- Payroll Center — a run paid through payroll is paid when its cut-off is posted.
- Salary Detail — a run sent to payroll shows there as a locked allowance line.
- Annualization — released lines count in the December true-up by their tax treatment.
- Alphalist Report — released lines are folded into each employee's annual figures.
- BIR 2316 — the certificate reports released lines under their tax treatment.
- BIR 1603Q Fringe Benefit Tax — the quarterly return is built from posted payroll cut-offs (and, for history, Released fringe benefit runs).