Payment vouchers connect contractor spending to accounts, projects and branches. A small validation gap can leave a voucher pending, misclassified or difficult to review. BlueberryERP documentation describes controls for voucher codes, dates, branches, payment types, account lines and settlement details.
What to check before saving a payment voucher
Start with the voucher header. The voucher code is required and must be unique across pending and approved transactions. The date must be valid, and closed financial years are not permitted. Branch and payment-for fields must contain valid selections. Remarks are required and limited to 400 characters. If the voucher records a received payment, the received date is required when the Received option is checked.
| Stage | Evidence to check | Why it matters |
|---|---|---|
| Header | Unique code, valid date, branch, payment-for value and remarks | Prevents incomplete or duplicate transaction records |
| Account lines | Valid account, positive amount, project and activity classification | Connects the payment to the correct financial and project context |
| Payment type | Configured cash, bank, transfer or PDC account | Ensures the selected payment method has supporting account setup |
| Settlement | Required cheque, transfer or received-date details | Supports review of payment status and related settlement evidence |
Review debit lines against the project
Each payment voucher can contain one or more debit lines. The selected account must be valid, and the debit amount must be greater than zero. Project and activity fields provide classification context: the project name can populate from the selected project, while activity selection is filtered by that project. Use these fields consistently when a payment belongs to a construction project or activity so later cost review has usable context.
Match the payment type to its supporting details
Payment-type checks differ. Cash requires a configured cash account. Bank and transfer payments require a bank account for the selected bank. PDC payments require a PDC payable account. For bank cheques, the cheque number is required and the date cannot be in the future. Transfer payments require a transfer number and cannot use a future date. These checks do not replace an accountant’s approval; they provide a documented pre-posting review.
A practical contractor review workflow
- Confirm the unique voucher code, date, branch and required remarks.
- Check each debit line, account, amount, project and activity classification.
- Verify that the payment type has the required cash, bank, transfer or PDC setup.
- Review cheque, transfer, received-date and settlement details before approval.
For UAE contractors, this workflow can help finance teams separate data-entry validation from approval judgment. It is a control checklist, not legal or tax advice. BlueberryERP supports construction finance workflows with project and account classification; implementation teams should confirm the organization’s own approval rules and chart of accounts.
See the construction project cost center accounting guide for related project-accounting context, or contact Blueberry to discuss an ERP workflow.
