---
title: "Paying the salaries"
description: "Record where each person is paid, choose the account the wages leave from, and pay a closed month in one press — one payment per person in Treasury."
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.beelocity.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Paying the salaries

A month that is closed says what every person is owed. This page is what happens next: the money
leaves. You record where each person is paid, you tell Beelocity which account the wages come out
of, and then, on the closed month, you press **Pay the salaries** once. Beelocity records one
payment per person in Treasury, for exactly what their payslip says — so the cash ledger shows the
month's wages the way it shows every other outflow, and a transfer the bank sends back is one
person's to chase instead of a lump sum to unpick.

This page is for the owner, the clerk or the accountant who pays the month. The month itself —
opening it, working it out and closing it — is [Monthly payroll](payroll-run.html).

<a id="record-where-each-person-is-paid"></a>
## Record where each person is paid

Open **Human Resources › Employees**, open the person and click **Edit**. Under **Bank
details** there are two fields:

- **Bank** — the bank the account is at, or *Algérie Poste* for a postal account. Write it as the
  person's own paperwork spells it.
- **Account number** — the `RIB` at a bank, or the `CCP` at Algérie Poste. Copy it exactly as it
  is written on their paperwork.

Click **Save**.

Two things are worth knowing:

- **Beelocity does not check the number.** A `RIB` is twenty digits and a `CCP` is a different
  shape, and both are typed straight in. A number that is wrong comes back from the bank rather
  than being refused here — which is the safer of the two, because a check that refuses a correct
  account is invisible and gets blamed on the app.
- **Two people may share one account.** A household where the salary goes to one account is a real
  thing, and the register does not refuse the second person.

Leave both blank for somebody you pay in cash: you can still keep them on the register and in the
month's payroll. You just cannot include them when you pay — see
[When somebody has no account](#when-somebody-has-no-account).

<a id="choose-the-salary-account"></a>
## Choose the account the salaries leave from

Open **Payroll › Setup › Pay rules**, click **Edit**, and pick the **Salary account** under
**Payroll**. It is the Treasury account the month's wages come out of — your bank current account,
or your `CCP`. Click **Save**.

**It starts empty, and that is normal.** Beelocity creates no bank accounts for you: the accounts
your business has are ones you enter in Treasury, so there is no sensible account for it to guess.
Until you pick one, paying a month stops and tells you to set it.

**It is not the same as the account on your invoices.** The account whose `RIB` prints at the
bottom of a customer invoice is set on the **Organization profile**, and it answers a different
question: where your customers pay *you*. This one says where money leaves for your staff. Plenty
of businesses invoice from their bank and pay wages from their `CCP`, so keep the two apart.

<a id="pay-the-month"></a>
## Pay the month

Open the closed month under **Payroll › Months**, open **More actions** and
choose **Pay the salaries**. On a month that is not closed yet the action is greyed out, and pointing
at it says to close the month first. Beelocity asks one thing — the **Payment date**, the day the money leaves — and fills
in today. Click **Pay**.

That writes **one payment per person**, in Treasury, each for exactly the net pay on that person's
payslip, out of the salary account. Either all of them are written or none is: a month half paid is
the worst outcome there is, because nobody can see from the run which half went out, and the people
left out find out on payday.

The payments are recorded as **drafts**. They say what is owed and to whom; they do not yet move
the cash in your books. You confirm each one in Treasury when the transfer actually goes — which is
also what puts it in the cash ledger, on the day the money really left. If your business routes
large payments to an approver, that still applies: paying the month does not walk around it.

**The month's figures are never touched.** A closed month is a record, and paying it changes
nothing on it: no salary is recomputed, no payslip is renumbered. Whether the month has been paid
is read from the payments themselves.

<a id="see-whether-the-month-is-paid"></a>
## See whether the month is paid

The closed month's page shows a **Salaries** line under **Payment**:

- **Not paid** — nobody has been paid yet.
- **Paid** — everybody owed something has a live payment, and the line says how many people and
  how much.
- **Partly paid** — some do and some do not. Pressing **Pay the salaries** never leaves a month
  like this; it is what a month looks like after a transfer is cancelled or comes back from the
  bank.

The **Payments** tab lists the month's payments, one per person, with its number, the date, the
amount and its status. Click one to open it in Treasury.

**A returned transfer puts itself right.** Cancel the payment in Treasury, or mark it unpaid when
the bank returns it, and the month stops reading as paid on its own — you do not have to remember
to undo anything. Press **Pay the salaries** again and Beelocity writes a fresh payment for that
one person only; everyone already paid is left alone.

<a id="print-the-transfer-listing"></a>
## Print the transfer listing

Once a month has been worked out, **Print transfer listing** — or **Download transfer listing**,
under **More actions** on the run — gives you the paper
an Algerian bank's counter takes for a month of wages. It carries your own details and the account the money
leaves at the head, then one line per person with their bank, their account and their net, and the
total at the foot. The bank debits your account once and credits each line.

Print it in whichever of your languages the counter reads. The figures on it are the ones the month
settled: no salary is worked out again, and the total is the month's own.

**Print it before you pay, not after.** Somebody with no account number is on the listing with
their net and *No account on file* where the account should be — which is how you see, in one
glance, whom you still have to ask. Fill their details in on their record and print it again.

You do not have to wait until the month is closed. Print it as soon as you have computed it: that
is when the gaps are still cheap to fix, because closing a month cannot be undone.

<a id="when-somebody-has-no-account"></a>
## When somebody has no account

If anybody in the month has no account number, Beelocity refuses to pay the month and **names every
one of them**, not just the first — so you fix them in one pass. Add their bank details on their
record and press **Pay the salaries** again.

It refuses rather than skipping them on purpose. Recording a payment for somebody whose account
nobody knows would be recording something that cannot have happened.

<a id="what-stops-a-month-being-paid"></a>
## What stops a month being paid

| What you see | What to do |
|---|---|
| The month is not closed | Close it first. A draft's figures can still move, so there is nothing settled to pay. |
| No salary account is set | Pick one under **Payroll › Setup › Pay rules**. |
| No way to pay money out | Add a payment method in **Treasury › Setup › Payment Methods** — a bank transfer for wages paid by transfer, cash for wages paid at the counter. |
| Your organization has no default currency | Open the **Organizations** page, click your organization's **code** and pick a **Default currency**. A salary has to be written in one. |
| Somebody has no account number | Add it on their record; the message names everyone it is missing for. |
| The salaries have already been paid | Nothing to do. The **Payments** tab shows what went out. |
| This month owes nobody anything | Nothing to pay — everyone in the month nets zero, so there is no transfer to make. |

<a id="who-can-pay"></a>
## Who can pay

Paying the salaries takes a permission of its own. Somebody who may open a month, work it out and
even close it does **not** automatically get to pay it: closing settles what is owed, paying moves
real money, and an owner may well keep the second for whoever signs at the bank. Ask whoever looks
after roles for the payroll payment permission if the button is not there.

Source: https://docs.beelocity.com/en/payroll/payroll-payment/index.mdx