Why people switch
A calmer weekly ritual instead of receipt panic and year-end cleanup.Fiscello keeps imports, receipts, category review, and accountant handoff visible enough to trust before anything gets exported.Process walkthrough
One visible path from spend to accountant-ready records.
The product should feel structured enough to trust and simple enough to revisit weekly. Scroll through the four steps that turn loose documents into a clean handoff rhythm.
01
Pay at the merchant
A restaurant, supplier, or travel vendor gets paid in the ordinary flow of work.
02
Receive the receipt
The source document is issued and becomes part of the tax record.
03
Capture the record
The user uploads a photo, PDF, or text record and reviews the extracted fields.
04
Hand off cleanly
Spending records, supporting docs, and tax context are ready for the accountant.
Current product direction
Why this web app exists in this shape.
The first release is intentionally narrow: reduce document mess, keep review honest, and make the year easier to hand off when it matters most.
Start with trust
Explain permissions before asking for them, keep bank access read-only, and always offer a manual fallback.
Review before rely
Show potentially deductible transactions for review instead of pretending categorization is magically final.
Stay tax-ready all year
Turn bank activity, receipts, and quarterly estimate visibility into a calm weekly routine instead of a deadline panic.
Hand off cleanly
Package the year for an accountant with exports, supporting documents, and explanations that make sense.
Trust bar
What we must prove before asking for financial access.
The product has to make permissions legible, boundaries clear, and fallback paths visible before anyone trusts it with a real tax workflow.
Onboarding principles
- Say why each connection matters before showing a link button.
- Keep permission language clear, explicit, and close to the action.
- Offer statement import when direct linking is blocked or not trusted.
- Keep human support visible for high-stakes tax questions.
Claim boundaries
No exact refund promisesNo audit-proof languageNo AI accountant framingWeb app only for this phase
Document extraction posture
A production-minded document pipeline, not a black box.
The product turns messy documents into structured records you can inspect, correct, and trust before they affect the rest of the workflow.
Document extraction
Uploaded PDFs, images, and text files go straight into a multimodal extraction flow instead of a traditional OCR stack.
Confidence stays visible
Merchant, date, total, extracted preview text, and match confidence all stay inspectable so users can see when the model knows enough and when it still needs help.
Manual correction stays easy
Low-confidence results are suggested instead of forced, and users can edit the extracted preview or manually attach the right transaction without losing context.
What this prototype is testing
A web-first workflow, not a mobile capture story or full accounting suite.
The first launch stays narrowly focused: inputs come in, documents are reviewed, tax context is clarified, and the year becomes easier to hand off.
Own now
Linked accounts, imports, deduction review, receipt upload, estimate visibility, and accountant handoff.
Defer for later
Mileage automation, mobile-native receipt capture, payroll, and anything that promises audit outcomes.
Next step
Use the workspace prototype to validate onboarding, trust messaging, and the first weekly review loop.
