Separate review queue
Keep supported prepared results apart from approved operational records.
AI Inbox with human review
Keep prepared AI output separate from approved work.
When assisted document processing is configured, NIYAM can place supported prepared results in a review queue. People compare the source, correct the record and make every consequential decision.
The review gap
A suggestion becomes risky when it looks like an approved record.
Provider results can vary with the submitted source. Without a distinct review state, a prepared field or signal can be mistaken for verified project information.
A clear path from capture to responsible action.
Each step keeps the record, its context and the next responsibility visible.
- 01
Continue manually or submit a supported source
AI is optional; the canonical manual workflow stays complete.
- 02
Prepare when configured
A configured provider may return supported fields, status or review signals.
- 03
Review the source
An authorised person compares, corrects, accepts or discards the prepared result.
- 04
Move the verified record
Only the reviewed canonical record continues to submission or approval.
What ai inbox covers.
Focused capabilities for the complete workflow, described within their supported operating boundaries.
Source and status context
Show the information an authorised reviewer needs to evaluate the item.
Editable preparation
Allow supported prepared values to be corrected or discarded before use.
Complete manual path
Keep finance and report work available when AI is not configured or useful.
Manual-first proof
Finance and approval remain complete without an AI provider.
The approved current evidence shows the manual Finance Inbox and permission-controlled decision centre. It does not imply provider availability, a populated AI queue or extraction accuracy.
- No autonomous approval
- No accuracy promise
- No provider dependency for manual work
A useful record has a responsible next person.
The feature supports the handoff without blurring who records, reviews or receives the information.
Accountant
Review supported prepared fields against the source or continue with manual entry.
Project manager
Review supported prepared report information before it becomes shared output.
Owner or Admin
Keep AI optional and consequential decisions permission-controlled.
Human authority
The AI Inbox is a preparation queue—not an approval authority.
Actual results depend on the source and configured provider. Authorised people remain responsible for corrections, approvals, payments and client communication.
- Suggestions remain reviewable
- Manual work never blocks
- Canonical approvals stay authoritative
Questions about ai inbox.
Straight answers about scope, review and responsibility.
Is the AI Inbox required?
No. Supported finance and reporting workflows retain complete manual paths.
Does accepting a prepared item approve it?
No. Review prepares the canonical record; its supported submission and approval workflow remains separate and permission-controlled.
Why is there no populated AI Inbox screenshot?
No current populated capture is approved. This page uses current manual and approval evidence and states that proof boundary explicitly.