Business Process Consultant, Bahrain

Process before platform for Bahraini companies

Process work in Bahrain can start with a software question: should we move to a new ERP, or replace the spreadsheets around our accounting package? I turn that around. Until the business agrees how a sale becomes cash, how a purchase gets approved and who closes the month, any system choice is a guess, and the implementer ends up deciding your processes during configuration.

I begin with the flows that cross the most desks. For a trader that is order to cash and procure to pay. For a consultancy or advisory firm it is engagement to invoice, from signed proposal to collected fee. For a company with a Saudi sister entity it includes the handoffs between the two companies. I speak with the people who do each step, look at real documents such as delivery notes, quotations and payment vouchers, and draw the current flow with every handoff and wait marked.

The outputs are deliberately practical: a one-page map per process, a list of problems ranked by risk and effort, an agreed future design and a log of decisions still open. If a new system is then justified, those documents feed requirements work in Bahrain and the vendor demos that follow. If the better answer is a simpler process on the tools you already own, that is a valid result as well, and I will say so.

Approval limits, stamps and who may sign

Paper still carries authority in many Bahraini businesses. A purchase request is printed, signed, stamped and walked to accounts. Checks, including post-dated checks issued to landlords or suppliers, may need two signatures from a short list of people who are not always in the country. None of this is wrong in itself, but when the rules live in people's heads, approvals stall and nobody can show later who agreed what.

I document the delegation of authority as it really works, then help management decide what it should be:

• Which transactions need approval: purchases, discounts, credit limit overrides, write-offs, payroll changes and payments.
• Limits per role, set as bands by your finance head, and what happens above the top band.
• Who stands in when an approver travels, and when that cover ends.
• Which approvals must leave a signed or stamped record and which can be an electronic confirmation, subject to what your auditor expects.
• Separation between the person who requests, the person who approves and the person who pays.

The result is a matrix that fits on a page and is signed off by the owners. It works immediately as policy, and later it becomes the specification for approval workflows in whichever system you choose. Firms licensed by the Central Bank of Bahrain should have their compliance team check the matrix against their own obligations. For how approvals translate into system rules, see ERP approval workflows.

Order to cash in Bahrain and across the causeway

Order to cash can have two shapes inside one Bahraini company. Local customers pay by bank transfer, BENEFIT-linked services, card or check. Customers in Saudi Arabia receive goods by truck over the causeway, with delivery documents and customs paperwork that must come back before anyone can be sure the sale is complete. Mapping both paths side by side shows where they diverge and where the delays sit.

Questions I work through with sales, logistics and finance:

• Who confirms stock and price before an order is accepted, and from which list?
• Who checks the credit position, and can a salesperson release a truck for a customer who is over the limit?
• When is the invoice raised: on dispatch, on the signed delivery note or on clearance, and who tells finance?
• How do signed delivery notes travel back from the driver or the Saudi customer?
• How are receipts matched when the customer reference is missing or a check is post-dated?

The future design usually settles one trigger for invoicing, one owner for credit decisions and a short list of documents that must exist before a sale is closed. The VAT treatment of cross-border sales is for your tax advisor to settle; I focus on making sure the process captures the evidence they say is needed, at the moment it becomes available. Groups selling mainly into Saudi Arabia will find related context on the Manama ERP page.

Procure to pay and the paperwork VAT depends on

Purchasing problems in Bahraini companies tend to be noticed in finance rather than in purchasing. A supplier invoice arrives without a matching order, an import is booked before the customs papers reach accounts, or input VAT is claimed on an invoice that lacks the supplier's VAT number. Each is a process gap long before it is a software gap.

I map procure to pay from the first request to the payment, including the steps people skip under pressure:

• Requests and quotations: when one quote is enough and when a comparison is required.
• Purchase orders raised before the commitment, not after the invoice lands.
• Receiving: who signs the goods received note, and what happens to short or damaged deliveries.
• Matching the supplier's tax invoice to order and receipt, against a checklist your advisor approves.
• Imports: who collects the customs declaration and duty and VAT receipts, and when finance gets them.
• Payment runs: who prepares, who approves and who releases in the bank portal.

Firms with partly exempt income may need to split input VAT, and that coding choice belongs at a defined step in the process, not in a scramble before the return. Your tax advisor sets the rule; the process makes sure the right person applies it every time. The agreed design then becomes the basis for controls in whatever system follows, an approach outlined on procurement automation.

Payroll inputs, month-end and owners who keep processes alive

Hire to pay in Bahrain touches more paperwork than owners expect: offer letters, CPR and work permit details for expatriate staff, renewals, leave records and the salary data a payroll provider needs before wage protection payments go out. I map who starts each step for a joiner, a change and a leaver, and which document proves it happened. Statutory points such as permits and social insurance stay with your HR advisor and provider.

Record to report is where every other process arrives. With a small finance team, the close tends to wait on late delivery notes, unapproved expenses and bank lines nobody has matched. I build a close calendar listing each task, its owner and the input it waits for, so delays are traced to their source rather than absorbed by the accountant working late.

None of this lasts without ownership. Each process gets a named owner who approves changes, a short procedure written for the person doing the work, and a review whenever staff, products or regulations change. Procedures stay brief and sit where people already look, not in a binder on a shelf. Once processes are stable and the team wants to remove repetitive steps, my automation work in Bahrain picks up from here. The general method is on business process consulting, and the Bahrain hub and ERP consultant page for Bahrain cover the rest.