Record after confirmation
Tools
Supported tool items can create a tool record. Potential matches pause for a link-or-create decision.
Upload
Review each suggestion before it becomes financial data.
Upload one supported PDF or CSV. RunwayCal extracts readable financial details into reviewable suggestions, shows what needs attention, and waits for your approval before supported records are written.
- Input
- One text-based PDF or CSV
- System role
- Extract and suggest
- User role
- Review, route, and confirm
Conceptual workflowHuman-controlled write
- 01SourceReadable document
- 02SuggestionAI-extracted items
- 03ReviewEdit, route, approve, skip
- 04WriteApproved items only
Confirmation is the write boundary
Supported input
Start with readable text, not an arbitrary file.
Upload accepts one file at a time. It does not process screenshots, image-only statements, XLSX workbooks, or multi-file batches. The app shows plan-specific allowances, but the extraction service currently applies a 10 MB hard ceiling. PDF page limits still vary by plan, and CSV extraction reads up to 500 rows.
InputUsed forBoundary
Text-based PDFBank statements, invoices or receipts, payroll reports, and supported exportsNo image OCR. Scanned PDFs without readable text are rejected.
CSVFinancial rows read as document content, up to 500 rowsThis is not the destination-template workflow used by CSV Import.
RunwayCal extracts text from the file and sends that text to its AI provider for categorization. The source file is not retained; the staged extraction and approved records carry the review trail.
Controlled workflow
Uploaded is not verified. Extracted is not written.
The workflow keeps source, suggestion, review decision, and destination record distinct. Confidence helps focus attention, but it never turns a model suggestion into financial truth on its own.
- 01Upload
Choose one supported file
Select a document type, then upload one PDF or CSV. The file-size and PDF page limits shown in the app depend on the current plan.
- 02Extract
Turn readable source text into suggestions
RunwayCal reads the document text, uses AI to propose categorized items, and attaches confidence, currency, and a short source excerpt for review.
- 03Review
Inspect the exceptions and the confident items
Low-confidence, payroll, and unclassified items are called out. You can inspect source text, adjust supported values, edit supported descriptors, reroute an item, approve it, or skip it.
- 04Confirm
Save only approved items
The save action commits approved items to their supported destinations. Skipped and undecided items do not become records, and per-item failures remain visible.
Extraction mechanics
AI proposes the interpretation. Rules preserve the control points.
The model suggests categories and category-specific fields. Deterministic steps add stable identities, review flags, currency fallback, and replay protection. Unsupported or ambiguous output stays reviewable instead of being treated as fact.
- Document textDirect parse
- Readable PDF text or CSV rows
- Category and suggested fieldsAI suggestion
- Confidence and review state travel with each item
- Currency fallback and review flagsDeterministic rule
- Applied after extraction
- Name, description, date, amountUser correction
- Only supported edits are carried into the write
Product evidence
The proof should show a real review state and the confirmation boundary.
The existing upload image does not establish the current edit, routing, confidence, or save behavior. A current product capture is reserved here rather than presenting incomplete evidence as the workflow.
Current capture required
Upload: extraction review and approval
Capture the current review surface with representative confidence states, source-text access, one supported edit or routing choice, approved and skipped items, and the explicit save action. Use fictional data with no personal or customer information.
public/product/upload-review-approval.pngAfter confirmation
The destination still owns the financial record.
Upload can hand confirmed items to supported RunwayCal modules. It does not replace those Products, and different item types have different write semantics.
Record after confirmation
Cash Commitments
Recurring and supported one-time items can create commitments. Refunds and bank interest use the supported one-time path.
Link or create, then record
Deals and receipts
Revenue items can link to an existing deal or create a new one before the received amount is recorded.
Detection, not cash recording
Team payroll
A confirmed payroll line can be matched to an existing team member. The later payment action remains separate.
- Treasury
- A confidently identified closing balance can enter a separate reconciliation step. The extracted balance is not saved as a second record.
- Funding
- The extractor may identify it, but Upload does not create the funding round. The Funding area requires its own context.
- Deferred items
- Payroll batches, team-member creation, and tax-obligation creation point to their supported workflows instead of writing silently.
- Replay protection
- Exact file recognition and transaction-level identities help avoid repeat writes. Potential tool or commitment matches still ask for a decision.
Choose the right input path
Upload is not CSV Import or a live integration.
All three can bring supported financial activity toward RunwayCal, but they begin with different sources and keep different control points. Upload is a user-started, AI-assisted document workflow, not an accounting sync or autonomous bookkeeping.
PathSourceProcessingControl
UploadReadable financial documentsAI-assisted extractionItem-by-item review and routing
CSV ImportDestination templatesDeterministic row parsingRow validation before confirmation
IntegrationsConnected provider activityProvider-specific data flowPersistent connection, separate controls
Upload
Extract the details. Keep the write under your control.
Bring in one supported document, inspect the source-backed suggestions, and save only the items you are ready to use.
Start free