Start with your own idea
Cookbook and llms-full.txt are enough to test the idea in an LLM.
Ready-made ideas, prompts, and technical recipes for PaperOffice.
Applications, IDs, and statements are checked for completeness. Gaps and risk notes are visible before approval.
Notices, evidence, and invoices are assigned. Missing files and approval stay visible.
Emails, PDFs, and scans are recognized, assigned to the client, reviewed, and provided as a structured accounting export.
Validity, batch, and hold status are clear before goods are accepted.
Waybill, delivery note, and customs file match the shipment, not the inbox.
Reading, amount, and exception come from the document, not from spreadsheets.
Findings reach the record only after classification and approval.
Deadlines, cost types, and open items sit on the lease, not in folders.
Application type, completeness, and case file are visible after intake.
Amount, vendor, and duplicates are caught before posting.
Obligations, deadlines, and risk clauses are extracted from the contract.
Exceptions become tasks. The decision stays auditable.
Email, PDF, and scan are split, recognized, and filed in the right record.
Rule gaps are recorded as evidence and as a task.
Suppliers upload evidence. Document type, validity, and missing files are detected and shown in the portal.
Missing signatures are visible before routing. No invented signature endpoint.
Personal fields are marked before an export leaves the organization.
Authorized people ask questions about the archive and receive answers with traceable document sources.
Contracts are checked regularly for deadlines, obligations, and renewals. Tasks appear in time.
A mixed stack is split into document types, page ranges, and workspaces.
Periods sit on the record. A task is created before expiry, not after deletion.
Photos are recognized by damage type and severity. Unclear images become a review task.
Fields are extracted via MCP. The source stays a PaperOffice document.
The browser uploads files, starts OCR, and shows job status — without a secret key.
An event starts OCR and IDP idempotently. No double processing.
Only exceptions reach people. Claim, decision, log.
One question hits permitted workspaces. The answer names source and POFID.
A schedule checks the archive and creates tasks on hits.
No recipes in this view.
Integrator and Reseller can be combined. The next step is the partnership — application and instant decision continue in the PaperOffice app.
Start partnershipNo matching recipe?
Cookbook and llms-full.txt are enough to test the idea in an LLM.
If the path is unclear, the use case can be sent to PaperOffice. Recipe and prompt are then shaped together.
Vetted partners in the region implement Document Operations.