Vendor bills are loaded by one person and approved by another
Who is involved
| Role | What they do |
|---|---|
| Accounts payable clerk | Imports the bills from scans and submits them. |
| Finance controller | Approves the batch, under the maker and checker rule when the company has switched it on. |
Step by step
- Accounts payable clerk
Uses Import from documents to extract this week's vendor bills from scanned invoices, reviews the rows and validates them.
What they see:The grid shows each bill with its confidence and source page, and Validate reports any that need attention.
- Accounts payable clerk
Commits the rows and asks the Copilot to submit them for approval, with a dry run first.
What they see:The dry run names any bill that would fail; the real run submits the rest.
- Finance controller
Asks the Copilot to approve all submitted bills under 10,000 AED, with a dry run first.
What they see:The report shows how many would be approved and which would be refused, by position in the list.
- Finance controller
Commits the batch.
What they see:Each bill is approved or refused on its own. When your company has turned on the maker and checker rule, a bill the controller entered or submitted personally is refused.
- Accounts payable clerk
Opens the bills list.
What they see:The approved bills show as approved and are ready for payment.
Who is told what
Notifications and events from a batch are held until the batch has really saved, so a dry run notifies nobody.
Related
- AI Copilot
- Accounting & E-Invoicing
- A heavy user hits the limit and an admin raises it
- A manager assigns work through the Copilot and the colleague is told
- A manager clears every queue waiting on them in one pass
- Ask company policy and get an answer from your own documents
- Ask questions no report answers, and export the result
- Team workflows