Bulk actions, without the risk
At month end you have 80 draft invoices to confirm. You open each one, review, confirm, go back to the list, and repeat 80 times. Two hours of mechanical work and a good chance someone slips or misses one. Bulk actions solve that — but the cure can be worse than the disease if it does something you did not intend to 80 records at once.
The idea in a minute
A bulk run in Zemam is literally successive presses of each row's own button — same permissions, same approvals, same rules. It is not a side road around the safeguards.
How it works
- 1
1. Tick what you want
You filter the list however you like — by status, date or customer — and tick the rows. An action bar appears showing how many you selected and which actions are available on them.
- 2
2. Each action says how many rows it can act on
Select 30 rows with 20 drafts and 10 confirmed, and the Confirm button shows 20 while Void shows 10. Because a document is a state: confirming applies to a draft, voiding to a confirmed one. A button with no eligible rows is disabled — so you never press, wait, then discover nothing happened.
- 3
3. You see what will happen before it does
Before anything runs you get the full list: the rows it will act on first, then the ones it will not, greyed out with the reason each was left out. So you know not only what will be done, but also why a particular row was skipped.
- 4
4. Ineligible rows are never sent
Skipped rows never reach the server at all. So there are no failed attempts cluttering your logs and no error messages about something you never intended to do in the first place.
- 5
5. Every row passes exactly the same safeguards
This is the key point. A bulk run is not a special command that routes around the rules — it calls each row's own action, one at a time. So every rule still applies: your permissions, your branch scope, the approval workflow, the customer's credit check, the closed-period guard. You cannot bulk-confirm anything you could not have confirmed on its own.
- 6
6. One failure does not stop the rest
If one row fails — a customer over their credit limit, say — the rest carry on. At the end you get a report with a line per record and its own reason. So you know precisely that 78 succeeded, two did not, and why — instead of a run stopping halfway with you unsure how many went through.
In short
Each button states how many of your selection it will act on, and is disabled at zero.
A full preview before running: what will be done, what will be skipped, and why each was skipped.
Exactly the same permissions, approvals and rules — there is no side road.
One failure never stops the rest, and you end with a line and a reason for every record.
Where you'll find it
Sales & purchases
Confirming or voiding invoices, quotes, purchase orders, returns and goods receipts in one pass — the month-end work that eats hours.
Inventory & manufacturing
Items, transfers, adjustments, bills of materials and work orders. Useful after a data import, when dozens of records all need the same step.
Treasury & accounting
Receipt and payment vouchers, cheques, journal entries, cost centres and fiscal periods — with the closed-period guard respected exactly as it is.
HR & CRM
Departments, job titles, leave requests and payroll runs, plus customers, suppliers, opportunities and activities.
Losing hours to repetitive work?
Talk to us and we'll show you bulk actions on your own screens, and how the preview protects you before you press.