Operational knowledge for the full Datamonster document pipeline.
This knowledge center is built from the actual Datamonster application structure: upload intake, review detail, approval levels, payment readiness, AI prompt flows, business admin, users, permissions, and chart of accounts.
Search results
This is a finance-operations system with a document core, not a generic dashboard.
The codebase revolves around five document families, business-scoped access control, two-step approval, ready-for-payment queues, AI-assisted querying, and accounting structures linked into line items.
That is why the content architecture below is organized around operational journeys instead of superficial feature marketing.
Browse by bookkeeping domain
Getting Started
Onboarding flow, first login behavior, and the client starter journey.
Product Overview
Why teams adopt Datamonster, what the official site promises, and how trial signup works.
Document Operations
Upload, classify, review, and maintain invoices, claims, statements, suppliers, and vault records.
Approval & Payment
Two-level approval logic, rejection handling, and ready-for-payment prioritization.
Admin & Access
Business setup, packages, users, roles, permissions, and menu visibility.
AI & Automation
Prompt workflows, chat sessions, exports, and document retrieval behavior.
Accounting Structure
Chart of accounts templates, hierarchy rules, and per-business cloning behavior.
Start with the highest-signal guides
Why businesses adopt Datamonster
A reference summary of the official product positioning: AI bookkeeping, OCR automation, approval support, and reduced manual workload.
Starting a trial and choosing a plan
How the official trial flow works, what information a prospect needs to submit, and how the two public plan options differ.
Client onboarding and first login flow
How Datamonster decides whether a user lands on Get Started or Dashboard, and what the onboarding checklist actually tracks.
Uploading and classifying documents
What happens when a file is added, how business scoping works, and where the five document types appear across the product.
Approval levels and rejection logic
The real two-step approval model in Datamonster, including role separation, counts, pending queues, and reject officer visibility.
Using the AI prompt workspace
What the in-product prompt assistant can do, how sessions are stored, and why exports are part of the chat workflow.
Managing users, roles, and permissions
How access control works in practice, from role permissions to role-based menus and business-scoped data access.
Chart of accounts templates and business cloning
How account hierarchies are managed, why parent-child integrity matters, and how new businesses inherit COA templates.
All published guides
Why businesses adopt Datamonster
A reference summary of the official product positioning: AI bookkeeping, OCR automation, approval support, and reduced manual workload.
Starting a trial and choosing a plan
How the official trial flow works, what information a prospect needs to submit, and how the two public plan options differ.
Client onboarding and first login flow
How Datamonster decides whether a user lands on Get Started or Dashboard, and what the onboarding checklist actually tracks.
Uploading and classifying documents
What happens when a file is added, how business scoping works, and where the five document types appear across the product.
Reviewing document detail and line items
How detail view is structured, which accounting and payment fields matter, and how operators correct OCR output.
Document statuses, approvals, and archives
How list tabs and status mutations are wired, including processing, accurate, approval, and archive transitions.
Approval levels and rejection logic
The real two-step approval model in Datamonster, including role separation, counts, pending queues, and reject officer visibility.
Managing ready-for-payment priorities
How payment officers see urgent, medium, low, and unset queues after approvals are complete.
Working with Vault and cross-type moves
How the Vault behaves as an operational catch-all and when moving a document type is useful.
Using the AI prompt workspace
What the in-product prompt assistant can do, how sessions are stored, and why exports are part of the chat workflow.
Managing businesses, packages, and timezones
What super admins can configure at the business level and how those settings affect document operations.
Managing users, roles, and permissions
How access control works in practice, from role permissions to role-based menus and business-scoped data access.
Chart of accounts templates and business cloning
How account hierarchies are managed, why parent-child integrity matters, and how new businesses inherit COA templates.
Dashboard views by role
What each role sees on the main dashboard and why the dashboard is really a routing layer into operational queues.
Email workspace and sent history
How the app stores outbound email activity and where it appears in the UI.