Across Finance Shared Services
One operating model across your finance operations.
Each area at a glance: the steps a piece of work goes through, from first request to recorded outcome. The recorded demonstrations follow below.
Procurement
From request to approval, with every level in view.
From a purchase requisition to an approved request: evidence attached, delegated authority checked and each approval level recorded, ready for the payment handoff.
- Request raisedA requisition draft is raised with the supplier, line items and justification.
- Evidence attachedSupporting evidence is attached before the requisition can be submitted.
- Authority checkedThe approval level and delegation of authority (DOA) limit are shown on the request.
- Manager approvalThe manager approves within delegated authority, and the decision is recorded.
- Finance approvalFinance approves and the payment handoff is prepared.
Accounts Payable
Invoice in. Decision out.
AI and invoice automation from inbox to approval: on-device OCR reads the invoice, an allocation rule codes it, a three-way match keeps exceptions in view, and every approval is explicit.
- CaptureA supplier invoice arrives by email or upload in one invoice inbox.
- ReadOn-device OCR reads the key fields beside the original document.
- Code and checkThe supplier allocation rule splits cost across GL accounts and cost centres, and checks run.
- MatchPurchase order, goods receipt and invoice are matched; a variance stays visible as an exception.
- ApproveThe invoice is approved from My Approvals, and every step is recorded.
Expenses
From receipt to approval, in one claim.
An employee expense claim from the first line to the manager’s decision: a receipt on every line, the claim locked while it is with the approver, and each step shown in its journey.
- Claim startedAn employee starts a claim, with the approval manager shown.
- Expense addedEach expense line has its type, purpose, description and total.
- Receipt attachedEvery line needs its own receipt before the claim can be submitted.
- SubmittedThe claim goes to the approval manager and is locked while it is with them.
- Manager approvalThe manager approves in Approvals, and the claim’s journey shows the step.
Master Data
One ticket. Clear ownership. Done.
From a supplier onboarding request to a completed ticket, with the requester and processing team kept informed.
- Request submittedA new supplier request is submitted through the guided form.
- Duplicate checkA warning shows when the name looks like an existing record.
- Picked up from the queueA processor picks the ticket up from the shared queue.
- Second approvalWhere configured, bank details are approved by a second person.
- CompletedThe processor records the outcome, and the requester sees the ticket completed.