NEBIS.AI / PLATFORM / DOCUMENT REQUESTS

The PBC list that chases itself.

Request lists built from the client's trial balance, a secure upload link the client opens without a login, and an agent that tracks what has arrived. Your team sees what is outstanding on every engagement, without keeping a spreadsheet.

What it does

Document requests, item by item.

/ 01

Request lists from the trial balance

The list is drawn up from the accounts in the client's trial balance, split per account where the evidence is per account, and re-tailored when a new trial balance is imported. Nothing is dropped without a reason. A manager or senior approves the first list.

/ 02

Your firm's own template first

If your firm has its own request template, it leads. The Nebis library only suggests items for the gaps.

/ 03

A client link with no login

The client sees that engagement's open requests, what is still missing on each, and uploads files or replies per item. Every file is kept as evidence with its fingerprint and lands in the audit trail.

/ 04

Requests that grow with the audit

Items are added as the work needs them, from sample selections, unanswered confirmations and review notes, each tagged to the working paper that needs it. The client never sees working paper references.

/ 05

Reminders and a daily digest

Reminders go out on the schedule your firm sets. The team gets one digest each morning with the exceptions only, and an immediate alert for a non-routine reply or a deadline at risk.

/ 06

Checked on arrival

At the Review level the agent checks that a document is the right one, for the right period and entity, complete, legible and signed, and compares its figures with the trial balance and lead schedules.

How it runs

Three levels. Each includes the one below.

Portal

The request register, the team panel, the client upload link and review notes passed on as requests. No AI involved.

Follow-up

The agent tracks what arrives without reading it, sends the reminders and routine client emails, and runs the digest and alerts. Received items show as received, not checked.

Review

The agent reads each document, checks it against the request and the figures, and marks it ready for audit or says exactly what is still needed.

“Ready for audit” means ready to start work. Sufficiency stays with your team.

Part of the Nebis audit workspace, a product of Nebis Technologies Pte. Ltd. (UEN 202646739Z)

Questions

What firms ask about it.

How do you automate a PBC request list? +
Build the list from the client's trial balance rather than a fixed template, link each item to the account and working paper that needs it, give the client one place to upload against each item, and let the reminders and status tracking run on their own. That is what this module does.
Does the client need an account to upload documents? +
No. The client uses a secure link for that engagement. It shows only that engagement's open requests.
Does the agent decide whether the evidence is sufficient? +
No. At the Review level the agent checks that a document is usable and agrees to the figures, so work can start. Whether the evidence is sufficient and appropriate under SSA 500 stays with your audit team.
Can we keep our own request template? +
Yes. Your firm's template leads, and the Nebis library only suggests items for gaps.

See a request list built from a trial balance.

A walkthrough on a sample engagement: the list, the client link, a reply arriving and the team's view of what is outstanding.

By submitting, you agree to our Privacy Notice.

For businesses

For audit firms

Guides

Company