Decisions, in order.
Set who reviews each claim. Sciro routes it step by step to the right people, and on to your books.
How it works
One claim, up the chain.
Step 1
Set the chain
Approvers in order, for expenses, invoices and card statements each.
Step 2
Or draw it from the org chart
Pick approvers in your HR tree. Each claim climbs to the nearest one.
Step 3
Finance signs off
One shared queue for the finance team, or a named final approver.
Step 4
Then it posts
Approved, the claim goes to your books as a draft bill, documents attached.
The chain
The right people, in order.
A claim goes to its reviewers one at a time, then to the finance team, then to your books.
- Tiers in the order you set, per claim type.
- An approver can edit, recode or send it back with a note.
- Finance gives final sign-off and the claim posts, already coded.
Your team
Drawn from the people you already have.
Staff, managers and the finance team, invited by hand or synced from your HR system.
- Reporting lines come from the org chart, so routing follows the business.
- Pick approvers in the tree. Claims climb to the nearest pick, or through every one.
- Leavers and joiners update the chains on the next sync.
Never stuck
A claim always has somewhere to go.
Holidays, slow weeks and one busy inbox stop being the month-end story.
Cover
A reviewer on leave is skipped or covered, your choice. A claim never waits on an empty desk.
Reminders
Nudge an approver from the tracker, or let Sciro remind them after a set wait.
Shared queue
The finance team works one pool, so a statement never sits in one person’s inbox.
Transparent
Everyone can see where it is.
The submitter, the approvers and finance look at the same record.
Your chain, before you submit
Everyone can see who will review their claims, and who is covering today.
Every step recorded
Who approved, who sent it back and why, kept with the claim for good.
Back to the right step
A rejected claim, fixed and resubmitted, returns to the step that rejected it, not the start.
Part of one workflow.
Everything in SciroThe same chain carries expenses, invoices and card statements, and the same finance team signs them off.
Common questions
How many levels can a chain have?
As many as you need, in order. Expenses, invoices and card statements can each have their own chain, or share one.
Can the org chart set the approvers?
Yes. Pick approvers in the HR tree and each person’s claims climb to the nearest one, or to every pick above them, as you choose.
What can an approver do?
Approve, edit the details, change the account coding, or send it back with a note. The submitter sees the note and resubmits.
What happens when an approver is away?
Your leave policy decides: skip them, hand the claim to a cover, or hold it. Leave comes from your HR system or is entered by hand.
What is the finance team’s shared queue?
Claims that have passed their reviewers land in one pool any finance member can take. Switch it on and off in settings.
Who sees the pending count?
Each approver sees one count of what is waiting for them, pooled claims included, the same everywhere in Sciro.
See a claim move.
Free for 30 days.
No card required · Up to 10 people