Paper OS: AI agents and decisioning for credit and onboarding
Applications arrive from your system with their documents. Paper OS checks the documents for fraud, analyses bank statements and applies your rules to recommend approve, decline or review. It decides by itself where you allow it, sends everything else to your analysts and returns the final decision to your system.
See it in action
From a bank statement in the case to a decision, with the agents working in the case chat.
Meet the agents
Specialist agents use Paperwork tools to check documents and company information. Other agents coordinate the work, assess credit terms and draft client emails.
@folio
CoordinatorReviews the documents in a case, assigns checks to the specialist agents and writes the case summary. Opens many cases at once and answers questions about past cases with links to the records.
@clip
DocumentsExtracts details from Emirates IDs, trade licenses and document packs. Runs the document workflows your team has configured.
Uses Document Automation
@seal
FraudUses Fraud Detection to flag signs of tampering, suspicious file metadata and inconsistent document details for your team to review.
Uses Fraud Detection
@ledger
Cash flowAnalyses bank statements to show business inflows and outflows, balances, overdrawn days and unusual transactions.
Uses Bank Statement Analysis
@atlas
Company checkChecks domain history and public news about a company. Screens crypto wallet addresses when you provide them.
Uses Company Intelligence
@quill
UnderwriterRecommends credit terms from the bank statement analysis and your guidelines when the data supports them. Flags missing information for your analyst.
@courier
Client outreachDrafts requests for missing documents with a secure upload link, or payment reminders using details you provide. Your team reviews and sends each email.
+ Your own agents
Create agents with your own instructions and checklists, and choose which tools they can use.
From application to decision
An application comes in
Your system sends the application, its documents and the data you already hold, such as bureau, screening and bank data, through the API. Your team can also open a case by hand.
The checks run
Review documents runs fraud detection, bank statement analysis and document extraction on every file. Folio and the specialist agents summarise the case.
Your rules recommend
Rules run in steps, knock-outs first, and give the case approve, decline or review. Why this result? shows the rule that matched and the source of every value.
The decision goes back
Paper OS decides by itself within the limits you set. Other cases wait in review queues for an analyst to confirm, and the webhook sends the final decision to your system.
What your team gets
Decision Engine
Write rules in steps with Decline if, Review if and Approve if. Edits stay a draft until you check the changes and publish, and a second admin can be required to approve them.
Automatic decisions
Approve and decline without a person, within a daily limit. An approval brake stops automatic approvals when their share of recent decisions rises above your threshold.
Versions and traffic tests
Every published version is kept. Compare two, restore an older one, or send a share of new cases to a challenger version before you switch.
Explained decisions
Each recommendation shows its decision path, the rules that did not match and the source and date of every value. Case history records every upload, check and decision.
Review queues
Route cases to the right people, for example screening hits to compliance and large amounts to senior credit, each queue with its own priority and SLA. Overdue cases are escalated.
Analytics and alerts
Applications, automatic decisions, approval rate and analyst time by period and policy version, with the reasons cases go to review. Ask a question in plain words. Monitors warn about approval drift, overdue reviews and failing webhooks.
API and webhook
Open applications, upload documents, add evidence and start checks through the REST API. Final decisions come back by webhook, or your system polls and acknowledges them.
Agents in your team chats
Write to Folio or @mention a specialist to check a client, analyse statements or explain a decision. Supported workspace changes made from the chat can be undone.
Client upload links
Courier drafts the request for missing documents with a secure upload link for your team to send. Clients need no account, and the link expires after seven days.
Built for credit and onboarding teams
For teams reviewing business applications, documents and credit risk.
Lending
Review SME and working capital applications with a credit recommendation based on your policy.
Banking
Keep onboarding documents, check results and credit reviews in one client case.
BNPL
Review merchant applications in batches, with document and cash flow checks for each case.
Fintech
Give your operations team one place to review documents, investigate findings and assess credit applications.
Runs on the Paperwork platform
Agents use Paperwork tools across these five areas. You can also use the tools through the API or dashboard.
How do you want to work with us?
Choose a cloud subscription, an annual software license or a custom implementation.
API Access
API, dashboard and Paper OS in our cloud. Monthly plan plus usage above the limit.
Learn moreSoftware License
Deploy on your servers. Annual license, no per-document fees.
Learn moreBuilt for You
We set the platform up for your documents, rules and systems, from pilot to production.
Learn moreFrequently asked questions
Have a question that is not here?
How do applications get into Paper OS?
Your system opens an application through the REST API with its own ID, uploads the documents and adds the data it already holds, such as bureau, screening and bank data. Each application becomes a case. Your team can also create a case by hand.
Can Paper OS decide without a person?
Yes, if you turn on automatic decisions. You choose whether it approves, declines or both, set a daily limit and an approval brake. Cases outside those limits go to a review queue, and every final decision is sent to your webhook.
How do we change the rules safely?
Edits to the rules stay a draft until you check the changes and publish them. Every published version is kept, so you can compare versions, restore an older one, or send a share of new cases to a challenger version first. A second admin can be required to approve each change.
Can we see why a case was declined?
Yes. Why this result? shows the rule that matched, the value it read and the rules that did not match, with the source and date of every value. Case history lists every upload, check and decision with who made it.
What do the agents do?
Folio reviews the documents in a case, runs the fraud, bank statement and document checks through the specialist agents and writes the case summary. In team chats you can ask Folio or @mention a specialist to check a client or explain a decision. You can also create agents with your own instructions and tools.
How do clients send missing documents?
Courier prepares an email with an upload link for your team to review and send. Clients upload without an account; the link expires seven days after it is sent.
See Paper OS on your own cases
We set up a workspace with your policy and a few real cases.