Introduction: What does the Cameralistics App do?
The Cameralistics app extends Microsoft Dynamics Business Central 365 with functions needed in public institutions, universities/institutes, and comparable organizations when cameralistic reporting is required alongside double-entry bookkeeping (accrual accounting).
At its core, the app solves three tasks:
Planning (Business Plan/Budget)
- Planning is implemented via BC budgets – extended with the ability to plan at the budget item level.
Fund Commitment (Obligations & Earmarking)
- Open commitments from the purchasing process are managed as purchase obligations.
- Additionally, earmarking/pre-commitments can be recorded, even without a purchase order.
Cameralistic Accrual and Cash Accounting
- Postings are supplemented so that both the commercial view (accrual accounting) and the cameralistic view are available.
- Typical: An invoice is posted in December (accrual), payment occurs in January – the cameralistic cash accounting then falls in January.
Important Terms (Brief)
- Budget Item: Structural element for cameralistic reporting (comparable to title/appropriation logic); can be assigned to accounts.
- Business Plan/Budget: Planned values (BC Budget), optionally at budget item level.
- Purchase Obligation: Fund commitment from purchase orders (obligation before invoice/payment arises).
- Earmarking: Pre-commitment of funds (even without purchase order), optionally with cost center/cost object.
Typical Process for First-Time Users
Review/Build Master Data
- Mark accounts as cameralistic and assign budget items.
- Set up budget item plan and budget items.
Enter Business Plan
- Import and release budget values (possibly via Excel).
Start Purchasing
- Requirement → Purchase Proposal → Purchase Order: this creates purchase obligations.
- Upon release, optional budget verification occurs.
Post Invoices & Payments
- Invoices/payments automatically generate the entries needed for cameralistic accounting.
Evaluate
- Accrual and cameralistic views can be evaluated together or separately depending on the schema.